Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mrlondon

  1. OK... having finally got my drive spinning up properly again (little bit of stiction it seems)... I ran through the procedure again and success.... well nearly Now recognised correctly by the BIOS, I hooked it up as a slave and powered up. I've been using Win2K on an old 20GB HDD in the short-term, which came up fine but recognised the drive as only 128GB "Healthy" with a 128GB partition but unformatted (it's a 500GB drive). So I set the EnableLargeLba registry flag and rebooted. Again the BIOS sees it fine, but Win2K does not see the drive at all. So removed the reg key and rebooted... and Win2K still does not see the drive at all now. So in slight despair I hooked up the drive as the only drive (it should be bootable)... the BIOS sees it, POST passes fine then I just get a black screen with a white cursor in the top left. Is it time to get a liveCD version of TestDisk and see what that makes of it? edit - update Sooo.. I grabbed the Frenzy ISO, burnt it and booted up from that. The boot up sequence messages are very informative... basically the drive is not responding in a timely manner to transfer mode, read cache and write cache parameter requests so it gets ignored in the end. Needless to say TestDisk could not see the drive. Next step is to redo the whole sequence again to reset things (as that is what made the drive appear to W2K for 1 boot) and boot straight to Frenzy and try to use TestDisk. Fingers crossed but I'm not hopeful - still I'm learning some stuff along the way
  2. I used Sellotape on mine to stop them touching as I'd run out of proper insulating tape...... but.. um yeh... I'm probably not the best person to advise lol That said I can still get the serial connection to work.
  3. On that connector of yours - you should (in theory) be able to push down on the visible metal pieces in the 5/6 way connector and whilst doing that pull on the wire to extract it from the black plastic. It's basically just a spring clip. Easier said than done and a sharp knife (little swiss army or scalpel) used carefully to just cut the plastic away would probably be quicker. You'd then need to make sure to use some tape or something on the exposed contacts before connecting them to the HD so they don't short. Not sure but from what I've read, that looks like you will have to supply power to the cable. Does your PC recognise a new device if you just plug the USB end in?
  4. Before powering on. I think it's properly goosed now... the motor is doing the same thing on power up whether I have the heads isolated or not. I tried it 2 other ways now - isolating the motor contacts instead of the heads and taking the PCB off completely to start the process.... as soon as I take that step to spin up the regular noises start.
  5. Oh dear... I followed the instructions but I seem to have made things a lot worse. Maxtor DiamondMax 22 (STM35000320AS) with the BSY problem, not recognised by the BIOS at all but was spinning up fine. Used a CA-42 and got the terminal working fine I used a piece of card to isolate the heads contact and all seemed fine until the step to spin back up and I got this: F3 2>U Error 1009 DETSEC 00006008 Spin Error Elapsed Time 13.550 secs R/W Status 2 R/W Error 84150180 So I shut down hyperterm and the PC at that point thinking I didn't have something connected right.... Next attempt, get to the same point but this time I am getting odd regular noises from the motor (about a second apart and a second each in duration), as though it is attempting to spin up but failing... on the 3rd attempt I decided to leave it trying and eventually it gives up of its own accord... Error 1009 DETSEC 00006008 Spin Error Elapsed Time 7 mins 17 secs R/W Status 2 R/W Error 84150180 F3 2> Before I started the drive was spinning up fine, just not seen by the BIOS. I have a horrible feeling I've flexed the controller board or something and totally bricked a semi-brick Any suggestions before I launch this thing binwards? Thanks