17 replies
by syscokid
by syscokid
OK, how stupid can I be! You can't use Windows Explorer so you can't do what I suggested.
Do what Chipmunk said, type win at the prompt and press enter. If this starts up Windows for you, THEN do what I said to fix the problem permanently.
If Windows doesn't start, then I agree with the suggestion to reinstall.
by chipmunk
If you have Windows 9x. When you get to C:\ type in win then hit enter, if that don't work, then I recommend to reinstall Windows 9x. This should keep all your settings the way it was, just be sure that you install it into the same Windows fold, example: default is C:\Windows. That should bring you back to where you were.
Alvin
by tbradley
When you get to the C:\ prompt
type in "ver" without the " " and hit enter
the screen will show you what operating system is loaded. If win 95, or win 98,
type in "dir" without the " " and hit enter
if you see a directory {windows} with brackets, type in path=c:\windows\command
at the c:\prompt, type in edit c:\msdos.sys
change the bootgui to =1
save the file, and re-boot.
If you don't see win95/98, or there are no windows directories on your c: drive, then you have no choice but to reload.
good luck
by jnicks
There is one other thing you can do to get yourself booted into windows if you are using windows 9x. At your C:\ prompt, type the following commands.
ren autoexec.bat autoexec.old
ren config.sys config.old
That will rename your Autoexec.bat and Config.sys files. Neither of these files are required to boot into windows, but they can contain entries which prevent it. This usually occurs after loading legacy software or hardware, but not always. If you have any important drivers loadingin those lines, you'll want to consult your manuals and perhaps reinstall those to get new, cleaner config.sys and autoexec.bat files.
by jnicks
by tuqan
by bww5195
I have seen this twice.
Check the CONFIG.SYS for a line that says:
DOS=SINGLE
Rem out the line and reboot. Other than that I agree with the guy that said to rename the AUTOEXEC.BAT and CONFIG.SYS to see if it is either of those causing theproblem.
(When I saw this, the impatient user had double-double clicked a shortcut to a dos app. That supposedly caused the o\s to add the line mentioned above to the CONFIG.SYS. I've tried to duplicated the double-double click to reproduce theproblem but was unsucessful. The DOS=SINGLE line does cause the same thing that you are experiencing though.)
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending