• 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.

Gah, build problem

G

Gurck

Banned
So I built an Athlon XP system for an aunt, but when attempting to install Windows, upon booting up I get "Could not load biosinfo.inf, press any key to continue", which reboots the machine. It posts fine, the bios sees the ram & chip, I can go in & change settings, etc. I know for a fact the hard drive works - it's my old one. Any ideas? I was considering flashing the bios, but that makes me kinda nervous so I want to keep it a last-ditch thing.
 
I had a similar issue recently. I was freaking out thinking my system was unstabe; bad ram, etc. Turns out my CD-ROM crapped out on me.
 
I assume you got a disk with that motherboard. Reinstall it. If nothing changes, you have some real problems. It is then time to install the downloaded BIOS. Who made the motherboard. ASUS and a couple of others have been dealing with some quality control issues, bad capacitors, etc.

Then go back to fundamentals: Power supply. Motherboard. Video card. One memory module. floppy disk. Does it boot now? No? replace memory module? No? Take motherboard and power supply out of the case, and lay everything out on a small sheet of raw plywood. If no plywood, use thick cardboard. Still no work? RMB your motherboard.
 
Well, I tried transplanting the hdd to my own rig to troubleshoot, and got the same thing when I booted up from a windows cd to test it, so I'm guessing it has to do with the hard drive. It's not surprising really, I know windows likes to make hard drives give people trouble... Basically, when switching to my current 120gb drive, I put this 40gb drive in slave mode so as to transfer stuff to the new drive, then formatted & partitioned it, as it is to be (hopefully) the main drive in the rig I'm building. After getting this error, I deleted the partition and am still getting it. What do I have to do to make windows stop being so anal about using the drive? The drive is fine, btw. It worked flawlessly as the main drive in my rig for a few months, and is only a few months old.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top