VMWare / 2003 Server / Config.NT / 1992 Dos App
-
Hi I am trying to run Clipper, an ancient compiler, on a VM 2003 server. I am getting
16-bit MS-DOS Subsystem c:\windows\system32\cmd.exe - clipper.exe C:\WINNT\system32\config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
I've also tried launching Command.Com with the same error. I've checked the MS KB[^] for this and modified the Config.NT to the same as it was on the original NT4 box we're porting from, but still get the same error.**CONFIG.NT** dos=high, umb device=%SystemRoot%\system32\himem.sys files= 255
The KB talks about setting the Config.NT on a 2003 server, but as I am a total newbie where VMWare is concerned, do I have to do anything special when running under a virtual machine? Cheers MalcolmSmall angry dogs
-
Hi I am trying to run Clipper, an ancient compiler, on a VM 2003 server. I am getting
16-bit MS-DOS Subsystem c:\windows\system32\cmd.exe - clipper.exe C:\WINNT\system32\config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
I've also tried launching Command.Com with the same error. I've checked the MS KB[^] for this and modified the Config.NT to the same as it was on the original NT4 box we're porting from, but still get the same error.**CONFIG.NT** dos=high, umb device=%SystemRoot%\system32\himem.sys files= 255
The KB talks about setting the Config.NT on a 2003 server, but as I am a total newbie where VMWare is concerned, do I have to do anything special when running under a virtual machine? Cheers MalcolmSmall angry dogs
my app uses the tmp / temp environment settings. Obviously (doh!) dating back some 10-15 years, only 8.3 filenames were allowed. Changing temp from
c:\documents and settings\on and on and on\tmp
toE:\tmp
worked a treat.Small angry dogs