Hi everybody,
I've been thinking about getting a license of an English Windows Server
2003 Standard 32-Bit for the project.
It could be installed on one of our servers and be made available over
RDP. This would enable project members to do development and testing
work on our actual target platform. Considering that some developers
even use a non-Windows platform for development work, it might simplify
their work as well.
We may as well use the license for other purposes (Buildslave,
Testslave, whatever), but at least native building could be done by any
Windows version. And in this case, I might be able to donate an XP Pro
license myself (German though).
As I don't know about the needs of the other members, I'd like to hear
your opinion about my idea. It would also be nice to hear if anybody
knows a cheap (but legal!) way to get such a license or can even donate
one (e.g. unused OEM license shipped with a server, unused license after
getting Server 2008, etc.)
English Windows licenses are rare/expensive on German eBay, so this
would only be a last resort :-)
Cheers,
Colin
P.S.: If you have the opposite problem and actually need a Linux VM
available over SSH/RDP (e.g. for testing build system changes), just let
me know and I could set it up.
Shouldn't that work the same way (at least if there is any hbmColor)?
Cursors can have a different size as well, so maybe we should rather
query the hbmMask, if hbmColor is 0(=) I didn't bother reading the
context of the function though.
Am 16.01.2011 13:51, schrieb mkupfer(a)svn.reactos.org:
> Author: mkupfer
> Date: Sun Jan 16 12:51:14 2011
> New Revision: 50398
>
> URL: http://svn.reactos.org/svn/reactos?rev=50398&view=rev
> Log:
> - Fix draw of cursors in static controls
> - Last part of fix for bug #4874
>
> Modified:
> trunk/reactos/dll/win32/user32/controls/static.c
>
> Modified: trunk/reactos/dll/win32/user32/controls/static.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/user32/controls/…
> ==============================================================================
> --- trunk/reactos/dll/win32/user32/controls/static.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/user32/controls/static.c [iso-8859-1] Sun Jan 16 12:51:14 2011
> @@ -863,7 +863,15 @@
> else
> {
> BITMAP bm;
> - if (!GetObjectW(info.hbmColor, sizeof(BITMAP),&bm)) return;
> + if (info.fIcon)
> + {
> + GetObjectW(info.hbmColor, sizeof(BITMAP),&bm);
> + }
> + else
> + {
> + bm.bmWidth = GetSystemMetrics(SM_CXCURSOR);
> + bm.bmHeight = GetSystemMetrics(SM_CYCURSOR);
> + }
> if (style& SS_CENTERIMAGE)
> {
> iconRect.left = (rc.right - rc.left) / 2 - bm.bmWidth / 2;
>
>
>
Am 13.01.2011 10:58, schrieb gadamopoulos(a)svn.reactos.org:
> Author: gadamopoulos
> Date: Thu Jan 13 09:58:04 2011
> New Revision: 50381
>
> URL: http://svn.reactos.org/svn/reactos?rev=50381&view=rev
> Log:
> [rosautotest]
> -Implement closing any dialog that shows and stays visible for some time. This way rosautotest can now continue if a test application crashes or asserts.
>
Seems it causes a regression in testbot:
*http://www.reactos.org/testman/compare.php?ids=4355,4356
*
Hi,
I'm currently working on the coordinate transformation code in win32k.
While Windows does this in win32k, I wonder why its not done in user
mode and if we could depart from windows design here.
The advantages would be decreased complexity in the kernel and no use of
floating point emulation on x86 (better performance).
Are there any things that would make it unreasonable?
I don't plan to go and change this now, I just like to discuss whether
we might or might not do that at some point.
Timo
I didn't know about this feature.
Will this help the effort towards a minwin effort in fixing the
dependency hierarchy (mess)?
Ged.
On 31 December 2010 16:49, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Fri Dec 31 16:49:49 2010
> New Revision: 50243
>
> URL: http://svn.reactos.org/svn/reactos?rev=50243&view=rev
> Log:
> [CMAKE]
> Add generation of a depencency graph for shared libraries.
> The output is a graphml file. Can be enabled with GENERATE_DEPENDENCY_GRAPH
> switch.
>
>
I have asked several times in #reactos and in #reactos-dev channels, so now time to ask again here: What happens with the server?
We are commiting a lot ( more than 25 commits/days last days) and we dont know if:
1)One of those commits (hopefully not) has broken building..
2)One of those commits (hopefully not) has broken booting..
Both of these are pain in the a...if regtesting is needed.
So: Can anyone fix this situation asap?
Merry Thanks and Many Christmas ;)
tkreuzer(a)svn.reactos.org wrote:
> LD is stupid and doesn't handle stdcall decoration as proper as
> dlltool does (after we provided a patch) [...]
Wouldn't it have been easier to just provide a similar patch for LD
then? It was a matter of changing a strchr() call to strrchr()...
(http://sourceware.org/bugzilla/show_bug.cgi?id=9766)
We can always use a patched binutils version in the next RosBE if the
patch is not applied to the upstream source in time.
Cheers,
Colin
Hi,
> Author: cgutman
> Date: Tue Dec 21 04:35:12 2010
> New Revision: 50077
>
> URL: http://svn.reactos.org/svn/reactos?rev=50077&view=rev
> Log:
> [USBDRIVER]
> - Fix a bug that resulted in us only copying half of the old keyboard data
> - CID 10402
>
> Modified:
> trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c
>
> Modified: trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/usb/nt4compat/usbd…
> ==============================================================================
> --- trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/usb/nt4compat/usbdriver/keyboard.c [iso-8859-1] Tue Dec 21 04:35:12 2010
> @@ -277,7 +277,7 @@
> }
>
> // Save old keyboard data
> - RtlCopyMemory(pdev_ext->kbd_old, data, sizeof(data));
> + RtlCopyMemory(pdev_ext->kbd_old, data, 8);
>
> // resubmit the urb
> status = usb_submit_urb(pdev_ext->dev_mgr, purb);
This change is really dangerous and should be changed to a correct fix. Using magic values on memory copying is a bad idea. Using magic values (in general) is a bad idea.
Please provide a better fix without magic value.
Regards,
P. Schweitzer