Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I'm working on an old 95 system...cleaned out some old files...now when I reboot the system I receive a bad command or file name for device.himem.sys....I did an edit on config.sys and I have it listed on the first line as device=himem.sys...I've also tried device=c:\windows\himem.sys since that seems to be where the file resides..
I've tried utlizing a boot disk, still no luck..when I type win at the C: prompt I get to windows fine and everything is functioning...just when I re-boot I get this bad command or file name everytime. Any suggestions?
http://freepctech.com/articles/articles.php?ArticleId=38
Missing Himem.sys or A20 error in Windows95 or 98
0 
Was that the exact error message?
That's not the error message you'd get if himem.sys was missing - normally you'd see 'the following file is missing or corrupted: c:\windows\himem.sys
Error in config.sys on line#'.
The 'bad command or filename' error is likely generated from autoexec.bat - either a command has a spelling mistake or refers to a nonexistent file.Maybe post your autoexec.bat?
0
You are right...it is coming from the autoexec.bat file...when I went to edit the path it brought new command line up on the reboot indicating "bad command of file name"...so now that I know it is coming from autoexec, what should the command line be for Dos 4.xx win '95? right now the file has the following: device=himem.sys
When I run the autoexec.bat file I receive a bad command or file name. Thanks for your patience and assistance.
0
I edited the autoexec file...placed rem in front of the device=himem.sys which bypassed this file upon re-boot, then it would not boot to windows. I received no errors just a dos prompt. Edited the autoexec file again and added win to the bottom of the script....all seems to be working now!!
Now I know why I'm on XP at home..these old system drive me crazy...I'm still a novice!! Thanks for the input everyone!
0
No problem - device= statements should only be in config.sys, autoexec.bat won't know what to make of them, so you could safely delete the line.
Win9x only needs autoexec.bat & config.sys for DOS setup - What's in them depends largely on just what you need to do from the DOS prompt.
That's a little odd that you need to start Windows from the command line. Several startup options under Win9x are controlled by the textfile, MSDOS.SYS, which acts like an old 'ini' file. Can be edited, although you'd need to remove the 'hidden' & 'system' attributes under properties in order to save any changes.
0
jboy,
I wonder what Dana means with:
"...what should the command line be for Dos 4.xx..." (response #3)
Could it mean that DOS 4.xx was installed prior to install Windows 95?Greetz from The Netherlands,
The Count
0
Hi Count!
Naw (or at least, I doubt it), comes up a lot over on the DOS boards - when you type 'ver' on a Win9x system you get something like 'Windows 95. [Version 4.00.950]' which is the Windows build, not the actual DOS version.
I blame Micro$oft ; )
I don't think I've ever seen DOS4 on an old machine - it's either 3.xx, 5 or 6.xx - I have heard that 4 was pretty buggy.
0
Hi jboy,
I've should have known!
It's a ought thing that Micro$oft did that, instead of simply increasing the DOS version.
Personally, I've never seen DOS 4 and DOS 3 for that matter. I do have DOS 3.01 (or 3.03) laying around somewhere on 5¼" floppy's, but never installed it.
I started with DOS 5.0 and Windows 3.0Thanks for the reply and re-arranging my thoughts. :-)
Greetz,
The Count (February 9th, 17:03 hours)P.S.: Wonder what DOS command Zeb was on to.
0
Yeah, once upon a time 'ver' would report the DOS version, but M$ saw fit to confuse the issue.
I started on IBM DOS3.21 on my first (XT) machine... and promptly went to 622. Squirrelled away quite a few versions - but that was before the internet became so darn handy.
Zeb's question is similar to the one he posted earlier, concerning drive assignments & booting from a zip-drive. Not so sure I have the solution (or if there is one).
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
