> Compile for w2k only, these binaries work fine on XP and 2003.
Can’s you also compile for WNET and use them on W2K? Maybe there are issues that I am not aware of, that’s why I ask. I’ve tried it with some of my drivers and it worked flawlessly (of course only if you use functions available on the respective OS versions).
May the source be with you, stranger 
ICQ: #281645
URL: http://assarbad.net
> Can’s you also compile for WNET and use them on W2K?
Sometimes. No guarantees at all, often it will not even load due to missing
“_except_handler3” export from the kernel.
The DDK build env version can generally produce binaries for its target OS and
for newer OSes. Running the binary on older OS is not supported, though can
work by mere luck.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
> Sometimes. No guarantees at all, often it will not even load due to
missing “_except_handler3” export from the kernel.
That makes sense. I am using SEH only sparely and have not got this problem yet.
Thanks for the input, Maxim.
Regards,
Oliver
May the source be with you, stranger
ICQ: #281645
URL: http://assarbad.net
“Oliver Schneider” wrote:
> > Sometimes. No guarantees at all, often it will not even load due to
> > missing “_except_handler3” export from the kernel.
>
> That makes sense. I am using SEH only sparely and have not got this problem yet.
>
> Thanks for the input, Maxim.
By compiling for Windows 2000, ideally you get a compile-time error
for anything done in code that would have required a later platform.
i.e. By having WINVER and the LIBs appropriately targeted, you’ll get
undefined references by trying to use functions, information level
constants, etc., that are not supported by this least common
denominator platform.
As opposed to the same condition being exhibited either silently or
grotesquely at runtime by compiling for XP/2003 and then trying to
execute on 2000.
Alan Adams