• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BIOS Flash on Shuttle HOT661 v31 issue?

J

Jeff H

Golden Member
Guys,

I'm partially rebuilding a system for a friend, w/ the above board. It has the original BIOS on it, and I want to get the current one on there, due to some HD issues. I made a clean DOS boot floppy, and put AWD776.EXE and 661VS155.BIN on the disk. If, at the A: prompt, I type "awd776 661vs155.bin" (minus the quote marks) I get to the BIOS flash screen, it asks for the name of the file to flash (which is already filled in the blank space), and waits for input. I hit the enter key and nothing happens. The floppy light remains lit, and that's the end of the process. I can reboot the machine multiple times w/o any impact on the BIOS, so it's not doing any writing.

I also tried "awd776 661vs155.bin /py/sy." This gets me to the BIOS flash screen where I can assign a name to the BIOS file I want to save. It proceeds to save the file, and then the same as above.

Any suggestions on what I'm missing here?

TIA,

Jeff

 
Well I just went to the spacewalker web site and I am somewhat confused.

First off there appear to be two versions of this motherboard. HOT661 v3.1 and HOT661V v3.1. Both BIOS files are listed as .exe files and yet you are referring to a .bin file.

Is it downloading as an executable or as a .bin? If it's an executable, then the advice from the website is as follows;


"If the bios file has the .EXE file extension, you can directly save it to a bootable floppy (without further extraction), restart, boot from Drive a: and at DOS prompt type in the bios name to initiate the auto Bios flash procedure".

I hate these conflicting instructions like I'm seeing at their website. As you know, I didn't cut and paste everything that is written there. It can be interpreted several ways.

I wish you good luck. 🙂
 
boomerang, thanks for the comeback. Why is it always the simple things? Your reply got me to look more closely, and I had downloaded the file for the V board, and I should have tagged onto the non-V file. I d/l'ed the zip file. As I looked more closely at the files, the BIOS that's currently on the board is 6610S115, and now it makes sense that I should get 6610S164. Thanks again for loosening the cobwebs in my head.
 
FYI I did the BIOS flash this morning and it went w/o a hitch. I only had one BIOS flash go bad that I can remember, and that was on a Shuttle HOT-541 board that Shuttle admitted had a problem. They offered to reprogram the chip if I'd send it in. They turned it around in a couple of days. Good service!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top