Article View: comp.sys.intel
Article #1508Re: BIOS recovery : D845GVSR mobo
From: VanguardLH
Date: Mon, 15 Nov 2010 17:51
Date: Mon, 15 Nov 2010 17:51
71 lines
5172 bytes
5172 bytes
ClueLess wrote: > Intel D845GVSR motherboard > > Ok, this board was having problems with the mouse and I wanted to > upgrade the bios, from the original version 3 to the latest version 20 > at Intel site. The upgrading went ok and everything worked well but no USB under Win > XP SP3! (I need it to copy stuff from one machine to another). Was USB support working before? If USB support was not there before with the old v3 BIOS, perhaps the chipset drivers weren't installed into Windows XP to afford that support. Did you follow with an install of the Intel chipset drivers? > I thought of going back and tried the bios version 5 (which said the > mouse problem has been corrected). The Intel bios burning program > asked me to confirm I really wanted to flash an older version and when > I hit ok the bios was flashed. When you did the first BIOS flash update, did the writer program not first offer to save a backup of the existing BIOS code to a .bio file? I don't recall ever doing a BIOS update where either the program did not ask me to backup the existing code or the instructions told me how to do it using that same writer program. Do you have the old v3 .bio file to flash into your BIOS so you are back to square one? > Now the computer does not boot. When I set the jumper to the > maintenance setting the bios settings screen comes up and it shows the > bios version as 5. But any change in the settings are not saved. What does "not boot" mean? That you don't even get to the POST screen? Or that the hardware boot actually completes and it is the load of Windows XP that halts, errors, or something else yet to be described? > According to Intel, in the recovery mode the system is supposed to > read the *.bio file in a floppy or CD will be written to the bios. I > have tried *.bio files from nay versions both in CD and floppy but > have failed. What does "failed" mean? That your host won't boot using a bootable floppy or CD? Or that the .bio file gets rejected as incompatible with your hardware? The writer program can't find the storage media on which the .bio file exists? > If any of you know a method to flash the bios please let me know. The > mobo is not dead as the bios settings do display in the maintenance > mode. After flashing the BIOS, did you short the "CMOS clear" 2-pin header on the motherboard? The settings saved in the CMOS may not match those now in the EEPROM for the BIOS. They may not even align to the same byte positions in the BIOS table to those that are saved in CMOS for the old table. If you have customized the BIOS (in the CMOS copy), write down all the settings that were modified from their defaults. After doing the flash update to the BIOS, clear the old CMOS copy by shorting the 2-pin jumper for clearing the CMOS. Then do a *cold* reboot. If the "failed" problem is that the writer halted or errored during writing the new/replacement code into the EEPROM for the BIOS then it sounds like the prior flash was incomplete or corrupted. This can even result in not being able to boot using floppy, CD, USB drive, or other storage media to do another flash attempt. The only recourse at that point is to buy replacement EEPROMs for your motherboard (which requires extremely good soldering skills and the requisite soldering tools since I saw no socketed chips in the mobo pic at http://tinyurl.com/2b335nu). You might also try calling Intel support to find out how much it would cost to have them replace the EEPROM chips for BIOS (and put in the latest *applicable* version for that mobo). From their web site, it looks like support has been discontinued for this legacy product so you'll probably have to pay them to do the repair.
Technical Details
Message-ID:
<ibrrti$sr8$1@news.albasani.net>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!feeder.news-service.com!newsfeed.straub-nv.de!news.albasani.net!not-for-mailReferences:
<1bf2e6h3g3kqpjgjs3cbhv2h1qkr37ioor@4ax.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 4e777fa27a,fd6fc6d222f2988d X-Google-Attributes: gid4e777fa27a,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!feeder.news-service.com!newsfeed.straub-nv.de!news.albasani.net!not-for-mail From: VanguardLH <V@nguard.LH> Newsgroups: comp.sys.intel,24hoursupport.helpdesk Subject: Re: BIOS recovery : D845GVSR mobo Date: Mon, 15 Nov 2010 11:51:28 -0600 Organization: 0.35MOA sniper at loose in Usenet Lines: 71 Message-ID: <ibrrti$sr8$1@news.albasani.net> References: <1bf2e6h3g3kqpjgjs3cbhv2h1qkr37ioor@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net Xz0Iqcc08afpPuHDvKVACvCWCTxQ5474f+axOjWIpX4sb/UPKtyH0DF/bT4B8fE919PJH1WSHB0ok0QUMpMLTfqh4Bf8watprN3JCLcwQc3z4lNkXek8xGBQj8hO3t9Y NNTP-Posting-Date: Mon, 15 Nov 2010 17:50:42 +0000 (UTC) Keywords: VanguardLH VLH811 Cancel-Lock: sha1:z8bhj1EQii+c9mka2NMyvx52abE= User-Agent: 40tude_Dialog/2.0.15.41 Injection-Info: news.albasani.net; logging-data="iPmdr2zD6aLYm5ZnwQAvm8EeYcUrI+ibFd1v3kZ9ygCAlWvxpdiYBUzXssbUW0/bPXgeYumrtlhsHA9ebSU8zIzcdu+S//zWbXv+MYPoRbe64BdkPRx+ESTanMfDn2YE"; mail-complaints-to="abuse@albasani.net" X-MOTD: It is wiser to remain silent and let others ponder your ignorance than to speak and remove all doubt