"Bad command or file name"

[Jamtheram]

Hi folks,

Upon boot-up (when you see the black screen w/white lettering) I have noticed a line that reads "Bad command or file name".
This line is on the same screen as "Verifying DMI pool data" and "Updating ESCD....Success".
Any ideas what may cause this?



P3 500mhz.
Win.98 sec.ed.

[ski]

If the system boots up ok, then just ignore it.
It's left over from a previous unsuccessful boot due to a bad command entry.

[Jamtheram]

Thank you for your response Ski!:) It boots up fine.Just wanted to be sure all is ok...

[classicsoftware]

Please check your autoexexc.bat file located in the root C:\> directory.
There may be the remnants of a trojan or virus infection post the contents of the autoexec.bat file and let us look it over.

[Paleo Pete]

classicsoftware is correct or close. It's a line in either autoexec.bat or config.sys pointing to an application that doesn't exist. Could also be in win.ini or system.ini but usually not.

I've had that happen with commands to set CD ROM drivers, sound card drivers, and other things. Can also be caused by malware, putting a command in to run a program that is then deleted but the command in autoexec.bat is not.

[classicsoftware]

I don't want to contradict the master, but I'M pretty sure bad command or file name is from the autoexec.bat file. Config.sys does not acutally rune executable programs as musch as it loads certain kinds of programs into memory, If something is wrong n config.sys you usually get an invalid command in config.sys and it will point out what line of the file caused the error. I am pretty sure bad command or file name is an autoexec.bat problem.

Pete, BTw, is it a function of age we are aware and remember the workings of autoexec.bat and config.sys?

[Jamtheram]

Thanks guys for steering me in the right direction.It was a leftover Virus program in the autoexec.bat.Deleted it,no more message....:)

[Paleo Pete]

classicsoftware:

I think you're right, config.sys is used for configuration files, like loading pointers to I/O addresses and IRQs for sound cards etc, rather than exe files. I didn't stop and think it through completely...

Pete, BTw, is it a function of age we are aware and remember the workings of autoexec.bat and config.sys?

I'm not going to answer that question on the grounds it may tend to incriminate me. :D