The console is created by the system NOT by command.com. Start a console
app in the back ground… code running… no console. A console is
simply a system created way to display and get standard io. Each one has
its own process context the same as each windows app does. It also
simulates a memory mapped character video buffer as well. If you excute a
16-bit app, windows spawns off a ntvdm.exe (Virtual Dos Machine) to run it
in. The VDM does not exist for 32 bit console apps. There is a whole
chapter in the SDK doc called “Consoles and Character-Mode Support”. For
a quick start see BOOL AllocConsole(VOID); function help in the Platfor
SDK help. It has links to that chapter. It is all 32 bit code (and most
certainly not DOS).
-Justin
At 04:00 PM 10/18/2002, you wrote:
> ----------
> From: zeppelin@io.com[SMTP:zeppelin@io.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Saturday, October 19, 2002 3:42 AM
> To: xxxxx@lists.osr.com
> Subject: [ntdev] Re: Why not use BUILD [was Re: Errors while
> building samples of DriverStudio in Windows XP]
>
> You are correct that command.com is 16-bit, BUT the console is not. You
> can run 4nt in a win9x / me console.
>
What do you mean by “console” in this context? If it is DOS window, it is
command.com running in V86 mode. Sure, win32 processes can be started there
but is doesn’t mean console itself is 32-bit.I tried using 4NT there but it was too slow for some reasons. 4DOS as main
shell worked better (hopefully won’t need it anymore :).Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]
You are currently subscribed to ntdev as: zeppelin@io.com
To unsubscribe send a blank email to %%email.unsub%%