Old 486 system help

[iHardware Shelden]

So I am working on a very important computer for a client at work that needs some data taken off of it. What's the problem? Well the system won't pass post after the memory test, this is what it does;

 

I don't know if anyone knows what the cause of this is but help is well needed! Worst case I guess is there any way of getting the data off the drive via IDE to USB if we can't get this to boot or possibly even throwing the drive in another 486 based system? (Running some form of DOS) Thanks!

 

@tmcclelland455 @ 

[Dabombinable]

I'm not sure-I never used my 486 for that long when I found out that it was far worse than my 386-and my 386 never had that as a problem. I'd recommend putting the HDD in any computer that can boot off USB, and using a live Ubuntu USB to copy the files from the HDD to what ever was going to be used to store it.

[iHardware Shelden]

I'm not sure-I never used my 486 for that long when I found out that it was far worse than my 386-and my 386 never had that as a problem. I'd recommend putting the HDD in any computer that can boot off USB, and using a live Ubuntu USB to copy the files from the HDD to what ever was going to be used to store it.

Alright I might give it a try

[Guest]

Oh joy! 

 

Let's start with worst case scenarios: 

 

Yes, you'll be able to get the data via USB/IDE bridge or by plugging it to another PC. It doesn't have to be another 486 PC, any PC with IDE port will do, as long as the drive is in good shape.

 

However, if I remember correctly, you might have a problem with IDE drive/cable, as that's the common reason why POST might act like that. Try POSTing it without a hard drive and see if it completes POST and throws the non-system disk or disk error message. If it POSTs without HDD - do a 1:1 binary copy of the drive ASAP, because you're about to lose it. Or you lost it already. 

 

Let us know what happens next

[Dabombinable]

Alright I might give it a try

I've had Linux recover data of a 120GB HDD that I had dropped and badly damaged-unless the surface on all of the platters are damaged (or the spindle is shattered-easy to do on early 2.5" Seagate HDD), the data will be easy to recover. And if a HDD is inaccessible in Windows due to permissions, Linux will ignore them all.

[iHardware Shelden]

Oh joy! 

 

Let's start with worst case scenarios: 

 

Yes, you'll be able to get the data via USB/IDE bridge or by plugging it to another PC. It doesn't have to be another 486 PC, any PC with IDE port will do, as long as the drive is in good shape.

 

However, if I remember correctly, you might have a problem with IDE drive/cable, as that's the common reason why POST might act like that. Try POSTing it without a hard drive and see if it completes POST and throws the non-system disk or disk error message. If it POSTs without HDD - do a 1:1 binary copy of the drive ASAP, because you're about to lose it. Or you lost it already. 

 

Let us know what happens next

Thanks! Yea I will make sure to do that, drive sounds good but might not be, we shall see when I work on it Friday I guess 

[iHardware Shelden]

I've had Linux recover data of a 120GB HDD that I had dropped and badly damaged-unless the surface on all of the platters are damaged (or the spindle is shattered-easy to do on early 2.5" Seagate HDD), the data will be easy to recover. And if a HDD is inaccessible in Windows due to permissions, Linux will ignore them all.

Wow ok that is good, I hope our conversation last night about old drives holds true in this case

[Dabombinable]

Wow ok that is good, I hope our conversation last night about old drives holds true in this case

Well if I was able to get a 1.2GB Seagate ST51270A working for long enough to copy all of the data off it (it had some important documents on it that were urgently needed), you should be able to recover the data off the HDD.

[iHardware Shelden]

Well if I was able to get a 1.2GB Seagate ST51270A working for long enough to copy all of the data off it (it had some important documents on it that were urgently needed), you should be able to recover the data off the HDD.

Sweet, I guess we will see 

[flibberdipper]

Bad cable, incorrect jumper settings, dead drive...

[iHardware Shelden]

Bad cable, incorrect jumper settings, dead drive...

Yea seems like it

[watts300]

Too bad it's not a 2.5" parallel ATA hard drive. I have a never used, still in the package enclosure that I accidentally bought at Fry's a couple years ago because it doesn't say anywhere on it that its for those old-ass drives. Just a cheap $7 enclosure any way that I'd have given, gratis. I have no use for it. Never will.

[iHardware Shelden]

Too bad it's not a 2.5" parallel ATA hard drive. I have a never used, still in the package enclosure that I accidentally bought at Fry's a couple years ago because it doesn't say anywhere on it that its for those old-ass drives. Just a cheap $7 enclosure any way that I'd have given, gratis. I have no use for it. Never will.

Guess you can always find a 80gb ATA drive and use it as a USB drive  B)

[watts300]

Guess you can always find a 80gb ATA drive and use it as a USB drive  B)

True, but I've already got more hard drives than I know what to do with. Hah

[SansVarnic]

Loved the vid, it has been a looong time. 

 

I found this for you if it helps.

http://www.amazon.com/C2G-Cables-30504-Serial-Adapter/dp/B000UO6C5S/ref=pd_sim_147_4?ie=UTF8&dpID=413IkBXm4%2BL&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&refRID=1XQEGPE6AFYABHAX40S3

 

Honestly I agree it might be a mobo issue, southbridge died, the drive controller is dead or the drive itself is dying.

But seeing that the post stops after the mem test I would hazard a southbridge issue.

It looks as if you have several great suggestions from others so I leave there.

 

Hope all goes well for you. 

Let us know what you find.

 

[SkilledRebuilds]

Why has no mentioned removing ram sticks yet to see if there is a fault with them causing this..?

[Dabombinable]

Why has no mentioned removing ram sticks yet to see if there is a fault with them causing this..?

The faulty sticks of RAM that I have, and the motherboard with a faulty slot, only cause issues when you boot into an OS.

[SkilledRebuilds]

The faulty sticks of RAM that I have, and the motherboard with a faulty slot, only cause issues when you boot into an OS.

On older machine's in the past that I've worked on when first using 486's this is not the case. Fault ram can cause the bios memory test to falter/halt altogether. It has happened to me.

[SansVarnic]

Why has no mentioned removing ram sticks yet to see if there is a fault with them causing this..?

 

If you see the video the mem test sees the memory. So I would say its seated. 

[Dabombinable]

On older machine's in the past that I've worked on when first using 486's this is not the case. Fault ram can cause the bios memory test to falter/halt altogether. It has happened to me.

My 386 board is the one with the faulty slot.

[SkilledRebuilds]

If you see the video the mem test sees the memory. So I would say its seated. 

Means nothing really, I've had fault ram count it fully, 64Mb of Ram, then just flatout freeze afterwards completely as soon as the number is reached.

This was personally experienced on 486's, its also quite common as a fault.

[iHardware Shelden]

Loved the vid, it has been a looong time.

I found this for you if it helps.

http://www.amazon.com/C2G-Cables-30504-Serial-Adapter/dp/B000UO6C5S/ref=pd_sim_147_4?ie=UTF8&dpID=413IkBXm4%2BL&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&refRID=1XQEGPE6AFYABHAX40S3

Honestly I agree it might be a mobo issue, southbridge died, the drive controller is dead or the drive itself is dying.

But seeing that the post stops after the mem test I would hazard a southbridge issue.

It looks as if you have several great suggestions from others so I leave there.

Hope all goes well for you.

Let us know what you find.

Hey thanks, ya it might also be the CMOS battery since I remember on these older systems they start leaking when they go bad and eat through the motherboard (I feel you know what I'm talking about more than I do) so ill check that also

[iamdarkyoshi]

JGCertified needs an account here.

[Dabombinable]

Means nothing really, I've had fault ram count it fully, 64Mb of Ram, then just flatout freeze afterwards completely as soon as the number is reached.

This was personally experienced on 486's, its also quite common as a fault.

Well my older motherboards only use 30pin 1MB SIMM (8MB total installed per board) and the only time the board freezes is when I deliberately install the module with 2 of its chips missing-modules that are just faulty aren't recognised and I'm stuck with 4MB RAM.

[iHardware Shelden]

Ok got another system to boot into Windows 3.1, only problem is it says monitor I out of range now when it starts 3.1, any thoughts?