Articles

Bad command or file name

Packard Bell
December 30, 2007 at 07:27:02
Specs: 98, 1gb

When starting the PC I get a list of 'Bad command or file name' messages.

I have done 'step-by-step confirmation' and found that the error is:

The following file is missing or corrupted:
C:\OEMCUST\TOOLS\DOS\HIMEM.SYS
There is an error in your CONFIG.SYS file on line 1

Can you tell me how to repair/replace this file.

Thanks



See More: Bad command or file name

Report •


#1
December 30, 2007 at 10:00:27

... read (me being chastised lol):

http://www.computing.net/windows31/...

How To Fix This Error

you could change that line to read:

device=C:\WINDOWS\HIMEM.SYS

OR just copy himem.sys to the folder C:\OEMCUST\TOOLS\DOS\HIMEM.SYS


Grrrr
wat do I know?
... got brain freeze


Report •

#2
December 30, 2007 at 19:25:18

Unless you run DOS programs, such as DOS games, you don't need config.sys to run W98.

In which case, shut down and restart in MS-DOS, then at the C prompt type:

ren c:\config.sys config.old

Hit Return key after above command.

This will disable config.sys and the system should boot up fine. If you ever want to run programs in pure DOS, rename it back again then fix the problem with the config.sys file.

If you can't get to DOS the way I suggested, then tap F8 key during bootup and choose one of the command prompt options. Another way is to use a boot floppy then switch to the C drive by typing c: (then hit Return).

some other bloke...


Report •

#3
December 30, 2007 at 20:27:02

The 'bad command or file name' errors are coming from autoexec.bat. The misplaced himem.sys is a separate problem.

You may want to post back the contents of both config.sys and autoexec.bat. You can access them by running SYSEDIT and copy and paste them to your next posting.


Report •

Related Solutions

#4
December 30, 2007 at 22:52:29

... config.sys kicks in before autoexec.bat
@boot-up.

... "There is an error in your CONFIG.SYS file on line 1"
... points to himem.sys

... sorry for being pedandic on this matter.


Grrrr
wat do I know?
... got brain freeze


Report •

#5
December 31, 2007 at 12:46:27

"Bad command or file name" is a command line error message. Go to a dos prompt, type in some gibberish and hit 'return'. You'll get 'bad command or file name'. Config.sys items don't load from a command prompt; autoexec lines do.

The error displayed by a bad config.sys line is as already stated 'there is an error in your config.sys file on line. . .' You DON'T get a 'bad command or file name' error from a bad config.sys line. If you want to verify that for yourself just edit a bad line into your config.sys and see what happens.

Both config.sys and autoexec.bat are messed up on icebreaker's PC. As Derek says, they may not be needed anyway but it wouldn't hurt to have a look at them.


Report •

#6
December 31, 2007 at 15:57:23

DAVEINCAPS

... "HAPPY NEW YEAR"

Grrrr
wat do I know?
... got brain freeze


Report •

#7
December 31, 2007 at 16:59:30

Thanks. Happy new year.

Report •


Ask Question