Tip: Run a free scan for common Windows errors ad

re: autoexec.nt and config.nt problems Saturday, January 22, 2005 at 12:18 pm Posted by DEX (11847 messages posted) Walter Copy both files from the c:\winnt\Repair folder and put them in the winnt\system32 folder then wowexec.exe will find them and use them and let you run your DOS base program.. Also a note about the autoexec.bat win2k will NOT use it because it's a DOS command.. XP will some times because XP is base on DOS On Saturday, January 22, 2005 at 11:30 am, Walter Johanson wrote: >Why did autoexec.nt and config.nt not configure my DOS invironment in W2000 and XP? > >When I moved my DOS program to W2000 and XP platforms, I also moved lines from config.sys >to config.nt and autoexec.bat to autoexec.nt. The DOS program worked for a while. > Months later, I stopped working ... as though the *.nt files were not configuring >the DOS environment. > >Has anyone a clue about what happened and how to fix the problem (fix meaning to >have the *.nt files configure the DOS environment)? > >Cheers! >Walter [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Saturday, January 22, 2005 at 8:25 pm Posted by Dan (32 messages posted) Just a little Info....... Windows 2000 is built on the NT (New Technology) File System. It's basically an extension on Windows NT Operating System(hence c:\Winnt). Windows XP is also built on the NT file System. XP is just windows 2000 taken to the next step. It has integrated much more multimedia, simplified users with welcome screen etc., easier setup and a slash of color to the user interface. Windows 3.1 was built on the DOS operating system and carried over to Win 95, Win 98 and Win ME. In my humble opinion Windows 2000 is the most stable and fastest system Microsoft has created. I will never give it up. You can add a new interface to windows 2000 to give it a more modern look, change of all system icons. If you research the look, most icons can be changed in the registry. On Saturday, January 22, 2005 at 12:18 pm, DEX wrote: >Walter >Copy both files from the c:\winnt\Repair folder and put them in the winnt\system32 >folder then wowexec.exe will find them and use them and let you run your DOS base >program.. >Also a note about the autoexec.bat win2k will NOT use it because it's a DOS command.. >XP will some times because XP is base on DOS > > [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Saturday, January 22, 2005 at 9:08 pm Posted by DEX (11847 messages posted) http://www.techspot.com/tweaks/win2k_compatiblity/index.shtml On Saturday, January 22, 2005 at 8:25 pm, Dan wrote: >Just a little Info....... > Windows 2000 is built on the NT (New Technology) >File System. It's basically an extension on Windows NT Operating System(hence c:\Winnt). >Windows XP is also built on the NT file System. XP is just windows 2000 taken to >the next step. It has integrated much more multimedia, simplified users with welcome >screen etc., easier setup and a slash of color to the user interface. Windows 3.1 >was built on the DOS operating system and carried over to Win 95, Win 98 and Win >ME. >In my humble opinion Windows 2000 is the most stable and fastest system Microsoft >has created. I will never give it up. You can add a new interface to windows 2000 >to give it a more modern look, change of all system icons. If you research the look, >most icons can be changed in the registry. > [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Sunday, January 23, 2005 at 9:36 am Posted by Walter Johanson (4 messages posted) Thank you, but... The files were already there. However, I did as you said and copied them from winnt\repair, then added the two lines I needed for each. The problem persists. It is as if the files weren't run. Cheers! Walter. [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Sunday, January 23, 2005 at 9:52 am Posted by DEX (11847 messages posted) Walter You should NOT edit the files. What lines did you put in ?? Wowexec.exe will not run right if the files have more than they should have...(file size)(CNC Check) On Sunday, January 23, 2005 at 9:36 am, Walter Johanson wrote: >Thank you, but... > >The files were already there. > >However, I did as you said and copied them from winnt\repair, then added the two >lines I needed for each. The problem persists. It is as if the files weren't run. > >Cheers! >Walter. [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Sunday, January 23, 2005 at 10:26 am Posted by Walter Johanson (4 messages posted) Autoexec.nt: REM LCIS2000 setup path c:\lcis2000 set clavmo=c:\lcis2000,80 Config.nt: buffers=20,0 files=100 These are from the old dos files which are needed to run the app. On Sunday, January 23, 2005 at 9:52 am, DEX wrote: >Walter >You should NOT edit the files. >What lines did you put in ?? [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Sunday, January 23, 2005 at 10:39 am Posted by DEX (11847 messages posted) Walter Drop the > buffers=20,0 > files=100 and it may run... ------------------------ path c:\lcis2000 remove also /maybe/because of the shortcut will take care of it. -------------------------- you may also need to drop the path just make a shortcut to the exe file (that runs the program) and put it on the desktop and then right click on it and select Prop. and then set it up..(with the folder Opt.) The new shortcut in win2k is like the old pif file setup.. in win3./3.1/95/98 just quicker way to set it up.. (not to sure about the SET command) good luck On Sunday, January 23, 2005 at 10:26 am, Walter Johanson wrote: >Autoexec.nt: > REM LCIS2000 setup > path c:\lcis2000 > set clavmo=c:\lcis2000,80 > >Config.nt: > buffers=20,0 > files=100 > >These are from the old dos files which are needed to run the app. > > [Reply or follow-up to this message] re: autoexec.nt and config.nt problems Sunday, January 23, 2005 at 11:58 am Posted by Walter Johanson (4 messages posted) Thanks for your interest. Unfortunately, it doesn't work with the edited files. History: First, didn't work with edited files. Second, did work for a couple of months with edited files. Third, for no apparent reason stopped working. The editing worked. The problem appears to explain why it stopped working. Cheers! Walter. [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows 2000 Discussion Forum