Linked by Thom Holwerda on Sat 9th Jan 2010 22:52 UTC, submitted by poundsmack
Thread beginning with comment 403763
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-12
The OS/2 CONFIG.SYS shares the name with the file used by DOS (mainly for historical reasons), but the contents are quite different.
AUTOEXEC.BAT is only used in OS/2 Virtual DOS Machines, which are independent processes running under the OS/2 kernel which emulator a DOS kernel and the core DOS device drivers (mouse, serial, and so on). It can be named anything, really, and each VDM can have its own.
Not that much different from running DOSEMU under Linux except for the fact that DOSEMU isn't as well integrated with the system in most Linux distros, and OS/2 VDMs are somewhat more flexible still.
The OS/2 Windows subsystem (WinOS2) also runs in a VDM. It isn't a Windows API translator ... it's a licensed and partially rewritten copy of Windows 3.11 with various fixes applied that runs as a DPMI client inside a VDM.