Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Name: shakushinnen
I tried upgrading my bios. Everything seemed to go well, except that I got the message, "Error-Flash memory unknown" Anyone know what this means?
Thanks,
John
Can't elaborate on your error message but is the computer still booting? If so, unless you have very good reason to Flash your BIOS I would leave well alone. It is very rarely necessary and a bad flash can mean you need a new motherboard.
DerekW
0 
Very possibly you tried to flash with the wrong file and the file checked first.
I echo Derek's comment. Don't flash the bios unless you need to fix something.
0
Often the bios may be write protected with a jumper, I have seen that error before because of this.
Check with the motherboard manufacturer if
the bios has that feature.
I'd also reccommend using the latest version
of uniflash to flash your bios rather than
either the award or ami utilities as some
chips - ( 29C020 ) & similar have boot block
protection, all seems to go well except for
the last sectors, which is the boot block.
Uniflash can now unlock the bootblock &
flash chips that all too often are left dead
by awdflash.
Download the latest uniflash & run it from a
bootdisk, if it is write protected then
uniflash wont detect the chip type...
Unless of course it's a 27 series chip, To
which you should'nt be attempting to flash...
0
Gentlemen,
I wouldn't normally flash the bios either, except that I'm trying to install a Katmai 450 PIII into an AsusP2B and I "think" the bios needs to be upgraded. I'm not sure. It will run happily at 504 (112x4.5) but when I kick it up to 133 it won't go past POST, asking me for the location of my command interpreter (command.com). Do you think this is a bios upgrade problem??
Thanks,
John
0
I quite understand - obviously my warning was totally unecessary.
I think it might be worthwhile making a new post describing what you are trying to do and the symptoms you got (as per #4). Someone might have some thoughts on it. I've certainly run into requests from the system to give the path/name of the command interpreter.
This raises an interesting aside for me because I have command.com in both the C root and in c:\windows
DerekW
0
Hi Derek,
Yes, I also have command.com in my root and windows directories, but the system doesn't seem to see it at 133mhz, 112 - no problems. Right now I'm trying to figure out whether my memory is the problem, by running memtest.
I'll let you know how I make out.
John
0
Put "type name of command interpreter" in the Go Search box at top right of this page. Quite a lot of hits but tread carefully because some apply to a newly formatted HD and you don't want to loose anything.
Boot floppy in the drive and type sys c: seems popular if you've tried all the paths suggested.
DerekW
0
Hi Derek,
I think I've pretty much come to the conclusion that this message (type the location of the command interpreter) is the result of trying to clock my cpu too high. It runs well at 504 (112mhz), but it doesn't like 598 (133mhz), and I have no way of increasing the vcore, short of taping contacts, and that seems to be a risky business. I think I'll just leave it. By the way I'm using a Katmai PIII 450mhz, with an Asus P2B. I apologize if the Cpu/ram mislead you. I have several machines and sometimes forget to update this information.
Thanks for your help,
john
0
No problem. Overclocking forum might be able to help on this if you decide to look further.
Not sure how much RAM you have but W98 has problems above 512M. Probably nothing whatever to do with it but if you need the fiddle for this then shout back.
Good luck
DerekW
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
