Extra "C:\" during boot??

[Nathan Gleit]

I have noticed several "C:\" with nothing behind them during the boot of my system. I just disabled the windows boot splash screen and noticed error message "Invalid setting in MSDOS.SYS file" during boot.
Tried changing most fields in the C:\msdos.sys file (no luck)
system seems to runs fine ( i think hehe) http://www.sysopt.com/forum/redface.gif
just dont like error messages.Windows 98 OS
Any suggestions?
Nathan G.



[This message has been edited by Nathan Gleit (edited 07-18-99).]

[Nathan Gleit]

I looked in autoexec.bat and didnt see any extra lines.. I am running Norton Sysworks, which has a line there, but i believe that is for AV scan on startup.... any other ideas? I get 8 lines of "C:\>" with nothing behind them during boot, after sound card intilizes.hmmm where do they come from?

[This message has been edited by Nathan Gleit (edited 07-18-99).]

[BBA]

Ok, it's not Autoexec.bat if it says it's MSDOS.SYS.


You can remove the read only/hidden attributes from MSDOS.SYS and open it and edit it.

Here is my MSODS.SYS, it is normal with no problems. Overwrite yours with this:


[Paths]
WinDir=C:\WINDOWS
WinBootDir=C:\WINDOWS
HostWinBootDrv=C

[Options]
BootDelay=0
BootMulti=1
BootGUI=1
DblSpace=0
DrvSpace=0
DoubleBuffer=1
AutoScan=1
WinVer=4.10.1998
;
;The following lines are required for compatibility with other programs.
;Do not remove them (MSDOS.SYS needs to be >1024 bytes).
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxa
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxb
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxc
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxd
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxe
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxf
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxg
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxh
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxi
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxj
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxk
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxl
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxm
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxn
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxo
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxp
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxq
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxr
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxs


Then add the hidden/read only attributes back.

Note: To see it you have to go to the explorers view tab and select options/view and check the "show all files" and uncheck the "hide file extensions for known file types"

Note also that it pooints to drive C for everything. Make sure this is accurate for your system.

This should cure your MSDOs.SYS error

BBA


[This message has been edited by BBA (edited 07-18-99).]

[Nathan Gleit]

Thanks BBA !!! Yeap, you were correct I had some garbage lines on bottom of MSDOS.SYS file.deleted garb line and no more error...
thank you! it was starting to bother me http://www.sysopt.com/forum/smile.gif
any clues on the mystery C:\> lines?,this isnt quite as bothersome since it doesnt involve words like Invalid,Error,Critical..etc http://www.sysopt.com/forum/wink.gif

Nathan G

[This message has been edited by Nathan Gleit (edited 07-18-99).]

[AuraEdge]

I think those are just empty lines in the autoexec.bat
I had them beforeand after i took out the empty lines in thge autoexec.bat, They went away..and no problems like that msdos.sys thing you have....

[Petec]

echo off
at the top of yer autoexec.bat fie

[Nathan Gleit]

AuraEdge you were correct also!!
Turns out there were some blank lines( Carriage return) at bottom of autoexec.bat file.. I didnt notice them last time i looked ..Duuuhhh, Boy do I feel silly!!..Thanks for the help.
I wish to leave ECHO on , i like to see what system is doing during boot.
BTW=If i did turn ECHO off at beginning of autoexec, shouldnt i turn it back ON at the last line of autoexec.bat?
Thanks again.
" All is well in the Binary Village"
Nathan G.


[This message has been edited by Nathan Gleit (edited 07-20-99).]

[800XL]

Echo off does not need to be turned back on at the end of a batch file. Every time a new batch file runs, echo defaults to on.

It also does not mask everything that comes up on the screen, only the commands that call each thing that runs. So if your autoexec.bat file has "copy file1 file2" you will see the copy command with echo on, with it off, you will only see the "1 file(s) copied" output of the copy.

[Steve R Jones]

You can add CLS (clear screen)at the bottom of your autoexec.bat file.