Thinkpads Forum

Hello,

I recently bought a second hand T60 which was running fine until today when the following happened:

1. (Not sure if this is relevant) Within 10 Minutes as my wife was checking her Yahoo mail Internet Explorer shut down three or 4 times ("...has encountered problems")

2. Later when I came on explorer shut me down once and I tried to open Thinkvantage to set a restore point. But pressing the thinkvantage button would only take me to the start up interrupt menue. (Maybe the guy who sold me the t60 deleted the rescue and recovery...?)

3. So I went to Bios, I pressed F9 to set default values

4. Then I pressed F12 and the following boot sequence would show:
- 2: ATAPI
- 4: ATA HDD
- 5: PCI LAN

I tried to start from the hard drive directly and then windows startup was interrupted because "a problem has been detected"

Now I cannot startup windows at all, not in safe mode either, I ran a diagnostic check from BIOS , but didn't come up with anything.

I have a second T60 here, so I could exchange parts to try things out, but if it is a virus I don't want to mess up the other t60.

Any suggestions what I could do?

Thanks

Michael

It sounds like you hard drive is corrupt. You can verify that by swapping hard drives with your working unit. As long as they're both similarly-configured T60 machines, you should have no problems doing that.

Sounds like you need to run PC Doctor and check the hard drive.
http://www-307.ibm.com/pc/support/site. ... html#modem

I am sorry it took so long to reply...I'll do what you recommended, downloading PC doctor right now. If that doesn't do anything I'll switch the drives.

I'll post the results. Thank you very much.

Got it fixed!!!

Guess what I did... resetting BIOS I - not knowingly - changed the SATA controller mode option back to AHCI mode and since the drive doesn't have an SATA driver it did not start up anymore.

So I changed it to compatibility mode and it's working again.

(a guy from www.thinkpad-forum.de gave me the hint)

Thanks for all your help in finding the cause.

you might want to run a chkdsk /f on the HD as well