after 5 yrs my 8KHA+ won't boot?

Yes. It's acting as it should. You have a bad hard drive.

DaveL


"finding z0" <> wrote in message
news: ups.com...
>I tried booting the win98se drive to a floppy and it got to a naked
> prompt. Didn't try to type anything like A: Thought it should have
> given me some options. Or it may just be frozen. Disconnected the HD
> and got the error message to boot from a CD as the boot drive was
> (bad,evil, not there, corrupted, can't remember). Moved the ram around.
> It recognized it wherever i put it. Tried to boot with one stik in
> different slots, no change. I removed each pci card and tried to boot.
> No change. I did this one card at a time, then replaced it. Didn't take
> them all out at once. I was afraid I'd forget where they came from.
> The led does a complete cycle b4 it gets to FF (i.e. working its way up
> the alphanumeric stairway). Most times. I took out the main Winxp drive
> to get a buddy to try and boot it but he said he'd look at it to see if
> it's readable, but not try to use it to boot because it could mess up
> his rig (he does PC repair as a retired avocation). It the MB were
> trashed would the LED cycle so nicely? I wonder if it's my mildy O'c'd
> cpu ath 2400xp running at 16x (2.1G) partially failing?
>

Weird.
I recovered my crashed drive by repartitioning, reformating, etc. All
the files were corrupted (by what)? 1.Virus? (my freebie defs were up
to date), my firewall was working, etc.
2. cpu having a stroke? 3. MB dying? The second backup drive
(disconnected a year ago) was really trashed with a bad sector(s) in
the boot partition. Suspicious. The system seems to be running stable
for the moment. There still is the occassional hi/lo post beep and shut
down on startup (MB misreading a temp sensor, bad part, capacitor (none
visually arthritic). I was all set to build a new system. Perhaps I
still should. Cheers all.

Well,
If you would like to try and pull data from that drive.
go grab this handy tool..
http://www.pcinspector.de/file_recovery/uk/welcome.htm

Works wonders on drives that mess up..

"finding z0" <> wrote in message
news: oups.com...
> Weird.
> I recovered my crashed drive by repartitioning, reformating, etc. All
> the files were corrupted (by what)? 1.Virus? (my freebie defs were up
> to date), my firewall was working, etc.
> 2. cpu having a stroke? 3. MB dying? The second backup drive
> (disconnected a year ago) was really trashed with a bad sector(s) in
> the boot partition. Suspicious. The system seems to be running stable
> for the moment. There still is the occassional hi/lo post beep and shut
> down on startup (MB misreading a temp sensor, bad part, capacitor (none
> visually arthritic). I was all set to build a new system. Perhaps I
> still should. Cheers all.
>

thanks, too late, maybe next time.

Before reloading an OS on that drive you should have downloaded the disk
manufacturer's utility and run full diagnostics on it. You may have merely
put all your new data at risk again.

DaveL


"finding z0" <> wrote in message
news: oups.com...
> Weird.
> I recovered my crashed drive by repartitioning, reformating, etc. All
> the files were corrupted (by what)? 1.Virus? (my freebie defs were up
> to date), my firewall was working, etc.
> 2. cpu having a stroke? 3. MB dying? The second backup drive
> (disconnected a year ago) was really trashed with a bad sector(s) in
> the boot partition. Suspicious. The system seems to be running stable
> for the moment. There still is the occassional hi/lo post beep and shut
> down on startup (MB misreading a temp sensor, bad part, capacitor (none
> visually arthritic). I was all set to build a new system. Perhaps I
> still should. Cheers all.
>

i did that with the older drive and found bad sectors. The newer drive
that crashed is running fine for the moment. I still get the hi-lo
beep/shut down occassionally on boot up, but not often. I beleive it's
hardware related. I was going to build a new rig when I have time.
Thanks for the suggestions everyone.

still running!

I seem to have the same problems. had to reset corrupted bios. seems I problem solved.
needed a new battery!

Graham