View Single Post
Unread 11-16-2004, 11:30 PM   #18
dtkempii
Cooling Neophyte
 
Join Date: Nov 2004
Location: Manassas, Va.
Posts: 9
Default

I had the same results as noted earlier by jhuehne. I could unlock the bios, set the version, run an upgrade, then it would state that it was successful and needed to reboot...however, it would show "Processing file MOAI110.HEX 1 of 846 files (0% processed)", and just seem to sit there. I did find, however, that at this point...or soon after this page came up...the Hardware version returned to 0.0.0. My assumption is that it had rebooted, and simply failed to load the upgrade because of this hardware mismatch again.

Because of this, I decided to switch to my other window that was in the debug mode, re-write the bios version to 1.1.0. again, then jump to the window that was stuck in the midst of the upgrade and press 'F5' (refresh). Well...what do you know...it went through the percentiles until it had completed 100%. It claimed at this point to be successful. However, the bios version didn't reflect it.

At this point I restarted my snap server and rechecked it's settings. It, again, reverted back to the original version of OS and hardware versions. This time I went back to the page where it was stuck before, and hit 'F5' (refresh) to see if it would happen again. It failed to find the downloaded file...which simply says to me that it was deleted upon assumed completion of install.

Changing the hardware version definitely makes the difference between OS upgrades failing immediately due to hardware/OS mismatches and actually attempting to upgrade. If we could only get past this apparent write-protection on the eeprom I think we'd be able to upgrade these boxes!
__________________
Tom Kemp
MCSE/CCNA/A+
dtkempii is offline   Reply With Quote