I submitted a bootup problem: "When I start up the system it tries to networkboot (4th in the boot up sequence). Using F2 for system utilities shows that the system doesn't think that it has a Primary master drive. Persevering with multiple starts, the system then boots up and works flawlessly until I shut down, pack it away and then bring it out the next time when the problem recurrs. Once running the system correctly identifies the hard drive." I should have added that using F2 to get system utilies shows the primary master as "none". Highlighting this + "enter" shows that the detect method is set at "auto". Continually rebooting eventually starts windows and the hard drive is correctly identified. If the system is not plugged into the net-work the the Intel Boot Manager error message says to check the cable etc, no system disk found. I tried the hard disc in another laptop and it booted up with no problem. Annoyingly a different hard disc booted up OK first time in the NEC and, when replaced by the original disc, the system also booted up first time. Later I shut the NEC down, left it for a couple of hours without moving it and tried starting it - same boot error messages as before. It started up after 6 reboots. Once started, the sytem runs flawlessly as long as I keep it switched on. In searching for I solution I have already updated the BIOS but it has made no difference. Before I lose all my hair can anyone throw any light on the problem?
An expert who has achieved level 3 by getting 1000 points
I have had this problem many many times at the Lab over the years, in fact I have even owned a PC that did exactly as you describe! ... What I found out was... SOME hard Drives seem to work OK, others??? It seems to be a "Timing" issue with the Hard Disk Controller.. There is NO FIX as such.. that I have ever found, Sometimes ya can find a brand of Drive that will work with.. ALWAYS.. but for the most part.. it's either put up with it.. OR get a new motherboard/PC. I have torn my hair out more than once as I said.. But essentially it is a Motherboard fault, specifically, the Hard Drive Controller, thats is at fault..
Posted on Aug 17, 2007
128 views
Usually answered in minutes!
×