Computing.Net > Forums > Windows 95/98 > bad command or file name on startup

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

bad command or file name on startup

Reply to Message Icon

Name: elknarps
Date: June 5, 2003 at 10:49:44 Pacific
OS: 98se
CPU/Ram: 512
Comment:

When I start windows 98se the windows 98 screen appears then I receive the black screen with flashing cursor in upper left corner as always, but below the cursor it reads:

c:\>uwboot
Bad command or file name

What does this mean and how can I fix it?

Thank You in advance



Sponsored Link
Ads by Google

Response Number 1
Name: DAVEINCAPS
Date: June 5, 2003 at 11:18:26 Pacific
Reply:

That's coming from autoexec.bat. Once windows loads you can go to start-run and type in sysedit. Then either remove that line in autoexec.bat or type REM (followed by a space) in front of it so it's not processed.


0

Response Number 2
Name: RayMan
Date: June 5, 2003 at 11:19:07 Pacific
Reply:

reinstall the operating system.


0

Response Number 3
Name: beama
Date: June 5, 2003 at 12:28:31 Pacific
Reply:

Rayman A bit extreme maybe,
as well as looking in the autoexec.bat check the win.ini file look for a line that may read load=uwboot if its there dont delete it rem it out and reboot see if the meassage comes back.
if windows does not load use a boot disk then type in this at the coomand prompt path=c:\windows\command
then type edit autoexec.bat check for the line there if not there then type
edit c:\windows\win.ini (i think thats the correct path) and check for it there remember though its better to rem lines than to delete easier to recover from a rem than a delete. this error message is common if you have done a incomplete unistall I have come across a simular error message when a printer is not unistalled completly and i have found the program concerned in the win.ini load=etc

good luck



0

Response Number 4
Name: elknarps
Date: June 5, 2003 at 13:11:21 Pacific
Reply:

First Reply to DAVEINCAPS, I did remove the line as you said. This removed it from coming up and also removed a issue that I had on my desktop where the internet connect would appear after my system tray loaded (that was annoying).

I noticed though on the black screen when windows starts that I now have three "3" of c:\> under each other as shown below.

c:\>
c:\>
c:\>

How do I get rid of these?

Second Reply, RayMan... that's just a little extreme for this issue!

Third Reply to beama, I guess I jumped the gun before you responded. But I do have a question for you.

As you noted in your response... look for a line that may read load=uwboot in win.ini tab in msconfig.

I did look in the win.ini tab and found that if you open up the + beside the windows folder there is what is labeled: load= (without the uwboot after the = mark) is this the way it should be, or do I need to do something with this since I am receiving the "3" c:\> on black startup screen (as noted above)?

Thanks again for the replies


0

Response Number 5
Name: RayMan
Date: June 5, 2003 at 14:19:04 Pacific
Reply:

bottom. if you can cursor down below the last I like extreme, extreme works for me:-)

I assumed it wasn't completing the boot sequence. apparently it can't find "uwboot". I did searches and found no reference to it anywhere.


but anyway, the 3 C:\> are probably cartridge returns in the autoexec.bat file. they wouldn't show up as anything but blank lines at the line then that's where they are. They could also be blank lines inside the bat file as well.


0

Related Posts

See More



Response Number 6
Name: DAVEINCAPS
Date: June 5, 2003 at 15:27:09 Pacific
Reply:

Anytime you get a 'bad command or file name' it's coming from a dos command line attempt. For example if you enter some gibberish at the c:\> prompt and hit enter you'll get that response. And a batch file is just a way to run several commands or files without having to enter them individually at the prompt. It wouldn't have been in the system.ini or win.ini as the error message would have been different.

The 'load=' line in win.ini is OK. Win 3.1 often loaded stuff there but 9x hardly uses it.

As RayMan the extra prompts are probably carriage returns or ECHO lines. Although some files or commands seem to generate them automatically.

You might want to post back the contents of your autoexec.bat and we'll see if we can edit out some of the unneeded stuff.


0

Response Number 7
Name: elknarps
Date: June 5, 2003 at 18:11:21 Pacific
Reply:

DAVEINCAPS,

This is what is in my autoexec.bat first line:

rem - By Windows Setup - lh C:WINDOWS\COMMAND\mscdex /d:mscd001 /l:m

the letter "l" within above just looks like a straight line up-and-down instead of the letter "l" in "lh" and "l:m" (there is also NO check mark to put in or take out in front of what is listed above).

The autoexec.bat also has this in the second line:

SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

This one has a check mark in front of it.

THE THIRD LINE JUST SHOWS A CHECK MARK (with no description) THAT CAN EITHER BE PUT IN OR TAKEN OUT.

Sorry I didn't get back to you sooner!



0

Response Number 8
Name: DAVEINCAPS
Date: June 5, 2003 at 19:05:45 Pacific
Reply:

Does the character look like this--|--? It should be an 'l' as in lower case 'L' The 'lh' stands for load high meaning mscdex is to be loaded in upper memory. But that doesn't matter as the line is rem'd out anyway and it's not being processed.

The next line modifies the path. The path is where the OS is to search for a command or file name that is not in the default directory. Windows automatically has a path to look in c:\windows and c:\windows\command. This line adds a third directory to search.

The check marks are windows' way of indicating whether or not the line should be processed. The REM in front of the line is dos' way of not processing the line.

I don't know about the blank third line. I would think you could go ahead and remove the entire line. At the very least you could uncheck it.


0

Response Number 9
Name: elknarps
Date: June 5, 2003 at 19:55:03 Pacific
Reply:

I figured out why I had "3" c:\>

I checked within sysedit and just clicked in the inside of the autoexec.bat box

I then noticed that once I clicked in the center of the box that my cursor was "3" spaces ahead of the type in the second line.

I backspaced "3" spaces then saved it. Restarted windows and the c:\> are gone.

I guess you learn something everday!
I do want to Thank All who helped me with this problem, elknarps


0

Response Number 10
Name: beama
Date: June 6, 2003 at 03:38:27 Pacific
Reply:

daveincaps response number 6 got it load =
is ok it was just another place to look as I have found in the past some installs still use it. especially when a reboot is requiried to finish a installation and the setup does not clean up after inself well.

I am glad to see your problem is cured


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 95/98 Forum Home


Sponsored links

Ads by Google


Results for: bad command or file name on startup

Bad command or file name on start-up www.computing.net/answers/windows-95/bad-command-or-file-name-on-startup/29343.html

Bad command or file name at startup www.computing.net/answers/windows-95/bad-command-or-file-name-at-startup/168317.html

Bad command or file name www.computing.net/answers/windows-95/bad-command-or-file-name/143351.html