Does anyone have an eeprom programmer?

[Eli]

When I tried to flash the bios of my PCChips M765VMRT board around six months ago it seemed to go well, and even booted once. Since then there's been absolutely no signs of life. Obviously, the most likely cause is a bad flash. Does anyone have a programmer and would be willing to do me a favor? Would the old chip even be salvageable? I'd like to be able to breathe some life into it so I can give my ol M717 to my brother.

[Bsdboy]

Maybe you could try the RD1 BIOS Savior,flash it and then reflash your original chip.
http://www.ioss.com.tw/eg/index.html

Bsdboy

[BFlurie]

Search for the words "BIOS bad flash" on this site -- there's been a ton of posts on it & possible solutions.

However, if it booted even once, I wonder if the cause really is a bad flash, or a motherboard problem.

[This message has been edited by BFlurie (edited 09-07-2001).]

[Eli]

Believe me, I've looked at all of the options. I've tried everything I can think of (ISA video card and little else, different ram, pulled everything from the case, etc..) with no luck at all. The last thing I did was the flash so either that went wrong or the motherboard just happened to fail at almost the same time. Immediately after I flashed it, it booted to the W98 splash screen. I then powered down (can't remember why I didn't let it boot all the way) and that's all she wrote. The only options left are reflashing (a programer or a hotflash with an identical board) or eeprom replacement. Since I can't find an identical board, a programmer is the next best option. Surely someone has one...

Thanks for the link Bsdboy, but since the board could very well be toast I don't want to dump much money into it. Even the $20 US or so for a new chip seems a little much to risk on it.

[BFlurie]

Don't give up too quickly on the "hot" flash method -- I did it with a different type mobo which used a similiar BIOS chip (but had a different manufacturer's BIOS). The key is the BIOS chip similiarity. Also, the Flash program used may be critical for success.

[This message has been edited by BFlurie (edited 09-08-2001).]

[Eli]

Well I have considered trying to use the M717 to try and flash the M765VMRT's bios, but I don't really want to risk the working board. Although, I have seen M717s up on eBay pretty cheap...

[BFlurie]

If you follow the hot flash method precisely, it shouldn't be a risk to the working mobo. The risk is removing/installing the BIOS chips while the mobo is powered (shorting), and the fairly fragile pins on the chips. If a pin breaks, you're SOL.

I used a hemostat (scissors-like with tiny claws on the end) to grasp and "walk" out the chips.

[This message has been edited by BFlurie (edited 09-08-2001).]

[BFlurie]

Nope. As long as the chip's BIOS ROM is copied into RAM memory during posting, the "chip" is no longer used. Almost every mobo does that. However, if you're uncomfortable, don't do it.

[This message has been edited by BFlurie (edited 09-08-2001).]

[Eli]

Yah, but the thought of two useless motherboards isn't exactly compelling. Wouldn't the M717 refuse to flash the M765VMRT bios? I mean, after I swap chips and fire up the flashing program, won't it give an error because of the incorrect bios?

[Eli]

I tried the hotflash with the M717 last night. No good. It appeared to flash alright, but the dead motherboard still won't post. At least the M717 survived. I noticed that the M717 behaves exactly the same way as the M765 does when I turn it on without it's bios chip (it wasn't inserted far enough), ie. processor fan comes on and nothing else, no beeps. What do you think, a bad chip?

[thekingofpain]

Been to www.badflash.com (http://www.badflash.com) yet?

[Eli]

Yep, right after I screwed it up in the first place months ago.

[thekingofpain]

Couldnt you have fixed it months ago for 20$ in that case?

[BFlurie]

While off, set the "bad" box's "Clear CMOS" jumper to "clear" for a few minutes, then set back to "normal". Then try booting.

[jeffpapier]

hotflash that "bad" chip on your 717 board again, but with a m717 bios and reboot to test the chip...reflashing a chip has been known to burn out a bad one on occasion.

[Nathan G.]

I have a programmer and would be happy to help you. :-)
Please send me a email with the following:

1) Orginal EEPROM part number (on chip)
2) Link to the Bios you want installed, or the actual BIN would be nice too.
3) Info on where to send it.

All i ask is that you send back your old eeprom so i can have it for the next person.
Regards,
Nathan G.

[Eli]

thekingofpain, since I'm in Canada I might've wasted like $40 Canadian on a dead motherboard. That's what I'm trying to avoid, which is what this whole thread was about. It hasn't been bothering me sitting there over the past six months or so, but I could use it now.

I've tried clearing the cmos quite a few times, even pulling the battery for a couple of hours. No good, although I haven't tried recently.

Actually I did try testing the bios chip with the M717 bios, but it gave me an "incorrect size" error. Looks like I can't flash it properly on that board anyway. http://www.sysopt.com/forum/frown.gif

Nathan G, you sir have mail. http://www.sysopt.com/forum/smile.gif

[Eli]

Alright first off, I want to thank Mr. Nathan G. for helping out. He sent me a new bios chip flashed with the proper bios. Thanks a million man!

Unfortunately, it didn't help. The board still won't even post. The monitor quickly flashes once when the system is turned on and the processor fan comes on, but that's it. No beeps, no funny pictures, no screams of pain. Is there a small fuse or anything on the board somewhere that might cause this? A shot in the dark... What does everyone think, is it time to let this one go? Time to cover it with a clean white sheet and give it last rights? Please say it isn't so...

Live **** you, live!

[Nathan G.]

You are VERY welcome.... It was my pleasure!:)
Sorry it didn't help though. :(

Is there onboard video on that mb? Is it disabled?

Given the course of events with your board: a)board was working before Flash,
b)Failed moments after flash/reboot)
c)I flashed EEPROM with same version you did
d) still aint workin..lol

I would say your board just doesn't like that new BIOS for some reason. Do you have the old Bios that was on the board before you flashed it?( As saved to floppy during Flash, as everyone ALWAYS does...right? :rolleyes: )
When you say the screen "flashes"
Is there data on the screen or is it just a quick "glitch" type thing ? If it is a glitch that flash of the screen doesn't mean squat.
I think you need to put the OLD BIOS on the EEPROM and see if the board runs that way.

PCChips has bagged me like this once before.(Their Site (Tw) Suggested/Supplied Incorrect BIOS for My MB). YES, I did read the REV number next to the KB connector and YES I check the BIOS version # several times before the flash.
BTW- that was the first time I had to use a Chip programmer to recover from a bad flash. And yes, I now run the old BIOS in that PCChips board. lol

On the other hand, maybe the board just happend to have a Hardware failure at the time flash. But if i was betting on this (which i am not), I would bet it is that BIOS version...
Regards,
Nathan G.
:cool:

[Eli]

No sir, no onboard video. Just onboard sound and winmodem. Your course of events is just about right on, with the exception that I did try to hotflash my chip several times with several different bios versions on my (now my brother's) M717.

Umm, well, about the original bios... I didn't back it up first. Hey it was a learning experience. It wouldn't have helped anyway since it still won't even pretend to post. I practiced on the M717 first by flashing it to the newest version and it worked great, so I tried the M765VMRT. Everyone knows what happened from there... :(

The little flash from the screen is just a glitch, meaning that power is getting to the video card at least. The lights are on but no one's home. I figured it meant little, but it doesn't hurt to mention it. :confused:

I dunno, it did boot once (and only once) with the newish bios. I suppose I could try disabling the onboard sound and see what happens, although it never gave me a problem. I'd really hate to toss it... :(