Running CG-DOS in Windows 2000

[Jess Loetz]

I am in the process of upgrading from WIN98 SE to WIN2000 and am running CG-DOS Ver 4.41.13. After loading CG on a single machine, I noticed no differences from using WIN98 (except that with WIN2000, you can transfer without a reboot to DOS!). However, after connecting the computer into a peer-peer WIN2000 network, a 5-6 second lag is introduced between the execution of CG's main menu screen (SU.EXE) and any of the programs (CG.EXE for example). I have tried removing the computer from the local network and removing the 3COM 10/100 network card, however the 5-6 second lag seems to be permanent now, even when not connected to a network. Has anyone else been experiencing similar problems with WIN2000? Please let me know if you have any information. Thanks

[Richard Henline]

Yes, the lag time is common in Windows 2000 and is something you will just have to live with. You must remember you are running a DOS program in a NON-DOS operating system. Windows 2000 is emulating DOS in a DOS SHELL not running it in a true DOS environment like it was meant to be. For everyone out there, everything above Windows 3.11 in not a true Dos operating system, this includes Windows 95, 98, ME, NT and 2000 and yes even the proposed Windows XP. My suggestion to everyone who plans on continuing to run a DOS based program is to set your computer up to duel boot in DOS and what ever other operating system you want. You can’t have the best of booth worlds DOS died around 1995 and you can’t expect to keep up with technology and continue to run a dos program

[Duncan Telfer]

With all due respect to Richard Henline in his memo of 10/10/2001, his approach to running DOS in windows 2000 (or any other 'higher level' operating system) appears to be rather like the guy who said 'now that we have automobiles, who needs feet?' Except, of course, that DOS based application software can run much faster, being closer to the PC's machine architecture. You also have the added option of more control over what you are programming. In my view, Windows
2000 'policy' is a rather unfortunate kick in the butt to DOS users and programmers, of which there are many [not the first time, I think, that Microsoft have sawn off the branch they were sitting on]. Surely any higher-level (GUI-oriented)operating system with profesional pretensions should be expanding the user's options, not straight-jacketing them?

Microsoft, for Windows 2000 I would give you 6/10 with an opportunity to re-submit your assignment for a better grade.

<br