Mail Archives: djgpp-workers/2001/05/04/03:28:13
> From: "The Owl" <theowl AT freemail DOT c3 DOT hu>
> Date: Thu, 3 May 2001 21:40:31 +0200
>
> DOS Version: 05.00h
> True DOS Version: 532h
> Windows Version: 00.16h
The last one puzzles me: is the major Windows version indeed zero?
What happens if you modify the last printf like so:
printf ("Windows Version: %X.%.2Xh\n", r.h.al, r.h.ah);
Can someone see what Windows version does that program print on NT4?
> this is on w2k/sp1 us-english. something you may be interested in
> is that i also have the following files in my winnt/system32 dir:
>
> NTDOS.SYS
> ntdos404.sys
> ntdos411.sys
> ntdos412.sys
> ntdos804.sys
>
> i'm not sure how i can get them to execute (load into a ntvdm process)
Try putting something in config.nt or autoexec.nt? Maybe search the
MS Knowledge Base for these names?
> but their mere existence suggests that one could get different DOS
> versions... could not tell you which of the above would be affected
I hope that the "True DOS Version" should remain unchanged. If it
does change, we are in trouble.
> perhaps you could try to getenv("OS") which under NT returns "Window_NT".
This is dangerous: someone could modify the OS variable with a simple
shell command.
> also, for the int 21/51 (getPSP) method i think there is no need for such
> detection, that code can be safely executed under any DPMI server.
Yes, I was planning to use these for 21/50.
- Raw text -