Thanks Graham,
That was my post... you can blame him if it doesn't work, though.
Thanks Graham,
Question: Shouldn't it have asked me if I wanted to overwrite "msdos.---" ?? I get the feeling that the .--- file extension is a wildcard of some sort?
Using "Dir" command shows that the "msdos.---" file is there. Not msdos.sys or ANY other msdos files.... yet I know for a fact that there was an "msdos.sys" and a 3rd "msdos. " file in the root before this "event" occurred.
It wouldn't of asked you to overwrite MSDOS.---, since the file obviously didn't exist. No it is not a wildcard char, only ? and * are wildcard characters.
MSDOS.--- is likely a system-created backup of MSDOS.SYS, MSDOS.SYD (my guess as to the third filename extension) is created god knows when, and isn't used to begin with... MSDOS.SYS is hidden, and will only show up with a dir switch:
dir C:\ /ah
anyway- MSDOS.SYS is always hidden on drive C:, which makes me wonder how you deleted it in the first place. I don't see how that caused a problem. instead, you might have an easier time editing your existing MSDOS.SYS file, to check for the existence of the BOOTGUI option. booting from the C:\ drive into the command line and running EDIT MSDOS.SYS should enable you to view the current settings. If BOOTGUI=0, change it to 1, and your problem should be solved. Otherwise, we'll try replacing it with a known-good version (the one I provided, assuming your Windows dir is C:\WINDOWS).
first, you'll need to make the MSDOS.SYS file on C:\ non hidden. It's also set to System, so we'll need to do it in one fell swoop, otherwise the attrib command will whine:
attrib C:\msdos.sys -s -h
(I'm a bit rusty, but if it says "not resetting ...." just flip around the -s and -h in that command.)
now that MSDOS.SYS is visible, you can rename it (say, MSDOS.OLD) and copy over the MSDOS.SYS file from the floppy. With any luck, that will work.
Somehow your MSDOS.SYS file that is currently on your HD possesses the "BOOTGUI" option set to 0, or at least that is my guess.
EDIT: patio's suggestion might help, if we forget that the machine is actually running windows 98SE which uses MSDOS.SYS for configuration data, as opposed to MS-DOS 6/6.2's MSDOS.SYS file that contains machine code.