On Sun, Jul 17, 2011 at 01:05:59AM +0200, Mathias Panzenböck wrote:
On 07/17/2011 12:43 AM, Michael Fox wrote:
You Couldn't be furthur from the truth, comparing win2k and XP is like
comparing apples and oranges, they are vastly different internally,
win2k is 16bit OS winXP in 32Bit, with different calls to different
systems, may seem the same on the surface but underneith where we work,
is 2 different worlds. Hence support for win2k was dropped
Are you sure you don't confuse Win2k with Win9x/Me? After all Win2k is NT based and the direct
predecessor of XP. (2k = Win NT 5.0, XP = Win NT 5.1)
You might want to read what Mike Erwin said earlier in the thread:
The current keyboard code (by jesterking I think) and upcoming 3D
mouse support (by me) both rely on the Windows RawInput API, which
only works on XP or newer. Far as I know, that is the only hard
technical reason blocking a Win2000 build.
That sounds like a bit of a show stopper.
I'm pretty sure the Linux version doesn't rely on the Windows RawInput API.
Speaking of which, I'm just trying to work out why anyone would be
running Windows 2K rather than Linux. Has someone implemented a
distributed Blender rendering engine that runs on botnets? There's a
good reason right there to maintain the W2K build.
853 New Cleveland Rd
Gumdale, Qld 4154