Old computer problems...

[Brasou]

Well I tried to setup one of my old computers that has just been collecting dust for the last few years, and iv got some problems. Woo

So yeah, I set it all up, turn it on and it runs fine. Then I turn it off and put in a wireless linksys card, turn it back on...runs for a few mins then bluescreen...Boo.

Try to restart, nothing. goes to a solid black screen after the post(But the computer still responds to alt-ctrl-del(restarting it, so it doesnt seem to be frozen)

I open the case, take out the new link sys card. Still the same problem. After examining the inside of the case trying to find a problem I notice one of the hard drives is unpluged, along with the floppy drive. Odd thing is they are setup in raid0. I know I didnt unplug the hard drive, and after pluging the HDD back in the wires are connected rather solidly....werid. So after disconnecting a HDD in raid then running the computer would that reset the array somehow? or cause some sorta setting to be reset? that was the first computer I had ever had with raid0 in it.

Any ideas as what I should try to fix it? (checked all the resisters and stuff on the mobo thinking maybe I bent/broke somthing by hitting it with the wireless card...but that doesnt seem to be the case).

[mtnlion]

That's odd that it wouldn't give you an error before booting. Every raid card I've had has always warned me about an incomplete array, usually with loud beeps and noises.

Generally, a striped drive with an incomplete array (meaning a disc missing) will not show up at all in Windows as accessible. Usually shows up as a RAW file system. Unless you formatted or used the drive though, the array should still be intact. As for why it won't boot, have you tried something as simple as clearing the cmos? Another thing to remember -- if a power supply has been sitting inactive for many years, the caps will usually dry up a bit, and not be able to supply proper amounts of power, which would lead to your BSoD, and now a non-booting situation.

I would suggest trying another PSU if you've got one kicking around.



mtn

[Kesarra]

Disconnecting HDs will mess with BIOS settings. If you messed with a RAID array, that can be much worse. You'll need to get into the BIOS and redo some settings.

[Tonk]

I have only done raid setups with asus boards so this may be different for you. But i have booted many time with 1 drive unplugged by accident and nothing happened. I have even run the same array through different sata ports on the mobo and the array stays intact. But to me this sounds the board has died. Since it is old try cleaning all the dust off, i have fixed some older boards by just giving them a spray with one of those air can thingys.

[Brasou]

I have only done raid setups with asus boards so this may be different for you. But i have booted many time with 1 drive unplugged by accident and nothing happened. I have even run the same array through different sata ports on the mobo and the array stays intact. But to me this sounds the board has died. Since it is old try cleaning all the dust off, i have fixed some older boards by just giving them a spray with one of those air can thingys.

Well, it occured to me last night that both the hard drives are 60gb each, but I remember from the first time it did boot that it olny listed 60gb inside Windows, not the 120 expected. apparently what seems to have happened is one of the drives failed along time ago, and as a quick fix I simply set the raid array to use the 1 hard drive and just unpluged the dead one but didnt bother taking it out of the case. (Funny cause I dont really remember any of this...but its the only thing that really makes sence)

So after unpluging and removing the 2nd hard drive the computer still does the same thing. But it doesn't make nearly as much sound(im guessing that was the 2nd HDD trying to spin up?)

after leaving the computer on for about 30mins I came back to it and there was an error! Appearntly somehow a hal.dll is missing or corrupted. So I found a program that was ment to solve and repair this problem from a boot disk. Ran said program Anddd!!......Nothing. same error *sigh*

But atleast by the sounds of it being able to detect a windows install, and start loading the OS the MOBO/power supply seem fine....Right?

[mtnlion]

I would say so, unless it keeps BSoDing, then I would investigate further.

Why not try doing a fresh install of Windows?

Or, how about something like this: http://www.kellys-korner-xp.com/xp_haldll_missing.htm



mtn

[Kesarra]

The hal.dll issue could be software or hardware related.

[Drewdle]

Find the newest version of hal.dll, and install it (copy it to the /windows/system32 directory). It should prompt you to overwrite the old one. That might help. I would totally recommend doing a fresh reinstall of Windows. Something else to try is get the mobo's model number and search online for BIOS updates. If there's newer ones available, flash it in there. Depends on how old the computer is as to how it does this, whether from inside Windows or at a DOS prompt before Windows boots. The reason I suggest it is my parent's old computer had an ABIT KT7 in it, and for two years, I had nothing but freezing and BSOD issues, in Windows 98 and Windows XP. I replaced everything in the computer except the hard drive and the mobo over the course of this time, with little avail. When someone suggested I look for a BIOS update, I found one, installed it, and the machine was solid as a rock for another SIX years, most of them spent overclocked.

[Tonk]

Is the system functioning fine until you try to boot from the drive? If it is just do a reformat and windows install. If this fails it is almost 100% hardware related.
If a fresh install/reformat fails i personaly would first try a new harddrive. Second try a new mobo and third try a new PSU.