Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Bios prob IBM Netvista 8305

Status
Not open for further replies.

garebo

Vendor
May 29, 2002
3,428
CA
I built this system and all was well. Its an IBM netvista with win xp pro, NTFS, west dig 60 gig h drive, 512 mb ram, Phoenix bios 4.0 release 6.0.I might have or must have changed something somewhere but now i have a prob.
I am fairly knowledgeable and have done most or all standard troubleshooting, i think.
Heres the prob. Whenever I boot up i get an error message, i think its IBM or Phoenix code 1269, anyway it means it cant find the hard drive. All i have to do is reboot and enter the bios and save and it will boot up fine. I dont even have to go to the area in the bios where the hard drive is reconized, it will be recognized. All i have to do is save and exit.
I have re-set the bios by removing power plug and battery and moving the jumpers to pin 2 and 3 on the cmos pins on the mobo. I didnt start it up this way, i only left it for a few hours and then put the jumper back to pins 1 and 2 and then booted. That didnt work, so i wonder if I should try booting with the cmos pins set to 2 and 3 and then try to boot and then remove power and put jumper back to pins 1 and 2. Would that fix my prob? Is that dangerous to do?
I know that this method removes password in an old packard bell mobo i had at one time and so it didnt hurt that mobo.
Anyone?
thanks

 
When you try this does the bios get reset? Why I'm asking is, just because you still have the problem does not mean the bios was not reset. You should have to short the pin for a couple of seconds and if you do it that way you don't have to take out the battery.
 
What you are doing will not hurt. But, I think you are on the wrong track. I think it is the Hard drive. It is not spinning up fast enough when you first boot. So, you go into the bios, play around for a minute then reboot. By this time the drive is spun up and all is fine. I'll bet if you do a restart from Windows all is fine right? It is only when the drive first starts up isn't it?

There used to be a setting in the bios to wait for the hard drive to spin up before trying to continue. I am not sure if it is there any more but you could look.

Jon

There is much pleasure to be gained from useless knowledge. (Bertrand Russell)
 
you know, i thought of that and then forgot, so thanks!!
I will try and see what i can find on that.
That is likely the whole prob right there, so thanks again!!
 
As well, the error message of 1269 is that it cant find the os, but i still think it might be the finding the hard drive prob anyway.
I might even try fiddling with the jumper setup on the west dig h drive, maybe bios will like a different setting?
 
At one time I had an ultra 100 controller on this setup and bios kept wanting to boot to the controller no matter what i did, finally i took the controller out. That is when i thought of the fact that the bios is having trouble finding the hard drive and/or the hard drive is not spinning up fast enough, but still i cannot seem to find a cure for it.
 
There is a "single" setting for western digital hard drives, when you dont have anything installed on the other connector and I had the drive set wrong so the bios was recognizing the h drive fast enough. I moved the jumper to where its supposed to be for a single drive and now it boots fine.
I usually use maxtor and seagate, dont get a lot of western digital h drives and i forgot!
Thanks for the help!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top