msconfig ghost in MS-DOS batch file

#1 joebloc

Group: Members
Posts: 1
Joined: 16-May 06

Posted 16 May 2006 - 01:43 PM

Hi!

I had two of these "C:\>" show up on screen during the WIN98 boot. They are from the MS-DOS batch file. The autoexec.bat is the gizmo that puts stuff in there. But the autoexec.bat file is empty. Nothing there. So I put two REMS in the autoexec.bat file thinking that would clear up the two C:\>'s. Naw, no good. Four showed up. And when I deleted the REMs, four were still there. How can I get that MS-DOS batch file cleaned up so that none of those "C:\>'s" are present.

Anybody? Yeah, I know this aint important compared to the hassles other folks are having, but the unknown can drive you crazy, too.

Has anybody ever used the microsoft backup program to "replace files" instead of "restoring files"? Because I have a backup but it didn't fix the problem by "restoring" and so I'm thinking "replace" but they don't recommend that. Why?

Anybody?

Joe Bloc

#2 janus zeal

Group: Members
Posts: 239
Joined: 09-January 06

Posted 16 May 2006 - 02:05 PM

most likely blank lines in autoexec.bat
did the same thing on my computer, till i opened autoexec in metapad(notepad replacement) and went to the end of the last line and pressed delete a few times...

#3 LLXX

MSFN Junkie

Group: Banned
Posts: 3,399
Joined: 04-December 05

Posted 16 May 2006 - 05:25 PM

As above... trailing linefeeds can cause that.

#4 charles__

Junior

Group: Members
Posts: 87
Joined: 08-July 05

Posted 16 May 2006 - 08:56 PM

Might go to run and type sysedit and check the autoexec.bat there. There could be a space somewere.

#5 CLASYS

Windows installer, chief cook and bottlewasher

Group: Members
Posts: 218
Joined: 29-November 04

Posted 23 May 2006 - 02:28 AM

Just make sure your AUTOEXEC.BAT file ends with:

CLS <make sure no CR and LF here!>

This solves the entire problem. Use notepad or whatever to ensure there is no trailing CR or LF past the CLS

cjl

MSFN Forum: msconfig ghost in MS-DOS batch file - MSFN Forum