OS compatibility

When building the samples for W2K I get warnings telling that certain
drivers are not compatible with W2K. Is there an easy way to find out
why they are not compatible? I have searched the documentation for a
table showing the differences between the various OSes but I can't
find one.

Don
Wed Mar 08 11:40:17 CST 2006

Typically they use one of more kernel service routines that are not
supported. Also, depending on the example there are some that expect other
OS capabilities that were not supported in Win2k.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply



"Stephen W Boyd" <sboyd@nospam.amtelecom.net> wrote in message
news:v74u02d790qdc1vaobc1elq4bkslaorbak@4ax.com...
> When building the samples for W2K I get warnings telling that certain
> drivers are not compatible with W2K. Is there an easy way to find out
> why they are not compatible? I have searched the documentation for a
> table showing the differences between the various OSes but I can't
> find one.
>

Stephen
Wed Mar 08 12:38:57 CST 2006

I had sort of deduced that much. I was hoping that I wasn't going to
have to go through the sample program line-by-line and read the manual
for each function to find out which wasn't support by W2K. It would
seem as though if build.exe is smart enough to know it isn't supported
it should be smart enough to tell me why.

Ah well, enough rant. It is the bitmap sample that I am interested
in. You happen to know why in this particular case?


On Wed, 8 Mar 2006 12:40:17 -0500, "Don Burn" <burn@stopspam.acm.org>
wrote:

>Typically they use one of more kernel service routines that are not
>supported. Also, depending on the example there are some that expect other
>OS capabilities that were not supported in Win2k.