What-o-ever. In some way I like the cluttered way ntvdm is implemented. Looking forward on coming PC hardware and back to old DOSware and forward to processor portability, I'd vote for DOSbox* as ROS's dos-box. CPUs get faster and faster and evolution is going away from ia32 (With vx86-mode). Thus a solely software implemented DOS-Box is more appropriate, now. Can we fix this theme somewhere? Steven? Jason?
*DOSbox = Freedos+bochs(win32)
Alex Ionescu wrote:
Filip Navara wrote:
- 16-bit virtual DOS machine (VDM)
CSRSS is involved here, but the main VDM process is NTVDM.exe which executes Win16/DOS programs and uses special kernel calls (NtVdmControl or how is it called). The emulated devices are handled by special device drivers (see DDK for details, there's special section about VDD drivers and DDK Graphics Drivers section has some info about VDM graphics handling)
Is in the csrss.exe (from ReactOS) the VDM process inluded?
No.
I read in the old forum that someone spoke about an DOS/win16 subsystem. Should the DOS (virtual maschine) be a part of the csrss.exe?
See above.
Just to add some information, CSRSS is quite more involved then Filip would make it seem :). Although NtVdmControl is used for hardware kernel calls, almost all the 1) Console and 2) VDM Emulation is passed back through CSRSS. CSRSS is the one who executes the loops to get the newest emulated commands to do, and who handles all the I/O.
Best regards, Alex Ionescu
Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev