Ms Dos will not respond to the edit command. However it will respond to other commands. At the c:/> I type edit config.sys and it responds bad command or file name. It did work prior to editing config.sys files and autoexec.bat files. I made a mistake of not putting rem in front of some lines that were corrupted, instead i removed those lines. does this affect how ms dos opperates? Any help would be appreciated.

You should be asking in the DOS or Win98 forum. Placing REM in front of the line prevents it from loading. Deleting the line obviosly prevents it from loading too. The advantage to using REM is that you don't lose the line & can re-enable it at a later date (if necessary) simply by removing the REM. If you're asking about Win98, there are several ways to edit. Try going to Start > Run, type in SYSEDIT, then click OK.

Yeah, I'm not sure if you're asking a pure dos queston or a 98 question. In 98, EDIT is located in c:\windows\command. On a dos-only system, likely 6.22 and less, it's going to be in c:\dos. When you get a 'bad command or file name' it means the command is not in the current directory nor in the path. The path statement is located in autoexec.bat. 98 has a default dos path of c:\windows;c:\windows\command so EDIT should run even without a path statement. However if you messed with that line in autoexec.bat you may have no path now. If you want to run a command not in the path, or if there is no path, you need to preface the command with the path to the file. So from a 98 c:\> prompt you'd type c:\windows\command\edit config.sys and enter. From a dos-only install you'd type c:\dos\edit config.sys and enter. Editing autoexec.bat would work the same way.

Thanks. We Have a old custom build computer with 98 on it. But when you start it up it says flopy disk(s) fail F1 to continue. You press f1 and it goes on to have some options they are Normal, Boot log, step by step confirmation, safe mode, command prompt, And command prompt safe mode. I have tried to boot normally but it doesn't work saying that it found problems and has the option of restarting only. The same thing happens with safe mode. When you do command prompt it does a scan on config.sys saying that files are missing or corrupt then comes to a stop at c:\>. We tried many things to get it working like bootdisks and bootcds but they dont work saying they cant find some files. This is why i went to edit config.sys and autoexec.bat trying to find the missing files this is what i found in autoexec.bat C:\PROGRA~1\TRENDP~1\PCSCAN.exe C:\ C:\ WINDOWS\COMMAND\ /NS /WIN95 (IS THE FIRST LINE). SET PATH=C:\CBTALK;C:\DOS;C:\PCUNIX. (THIS IS SECOND LINE). SET TEMP=C:\TMP (IS THE LAST LINE). IN CONFIG.SYS THERE IS DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.exe NOEMS FILES=40 BUFFERS=15,0 FCBS=4,0 STACKS=9,256 DEVICEHIGH=C:\DOS\ANSI.SYS DEVICEHIGH=C:\DOS\RAMDRIVE.SYS 16 /E I renamed these files how this web site told me http://www.computerhope.com/ac.htm so as you can see i cant start windows only get into dos can annyone tell me what autoexec.bat and config.sys should look like on windows 98. Thanks

When it get to the c:\> prompt type DIR/P and enter. That will scroll through the contents on the root (C:\) directory. Is there a dos directory? Is there a windows directory? You're loading most of the stuff out of the dos directory. Even if it's there you're probably loading files that are the wrong version. If you're running 98 you need to use 98 files. You can run windows with no config.sys and autoexec.bat so that's always an option. But it should be easy to fix them if you post back the above info. Also, even if config.sys and autoexec.bat are screwed up that shouldn't stop windows from loading so the main problem is probably elsewhere.

Hi. There is windows in the directory but no dos. what now.

"But when you start it up it says flopy disk(s) fail F1 to continue" Do you even have a floppy drive installed in your system? Does it light up when you attempt to boot? Does the light stay on? If so, the data cable is connected incorrectly. If you don't have one, disable it in the BIOS. BTW, Win98 doesn't even need autoexec.bat or config.sys. IO.sys basically replaced them. "The 32-bit IO.SYS is really a combination of DOS’s IO.SYS, MSDOS.SYS, CONFIG.SYS, and AUTOEXEC.BAT files. The new IO.SYS contains all the instructions the operating system needs to initially interact with your hardware. IO.SYS also loads some default CONFIG.SYS and AUTOEXEC.BAT commands, and it controls much of the remaining boot sequence. Windows 95 can run without a CONFIG.SYS or an AUTOEXEC.BAT file. That’s because these files are built into IO.SYS, which automatically executes a set batch of commands." Try renaming config.sys & autoexec.bat to config.old & autoexec.old & see what happens. If that doesn't work, try running scanreg /restore from the DOS prompt & choose a date before you began having problems