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. 



franklink

Member
  • Content count

    4
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About franklink

Profile Information

  • OS
    Windows 7 x64
  1. Waiting for the prompt to come back did it! Thanks a TON guys! TWO 500GB drives recovered thanks to this thread!
  2. After I issue the m0,2,2,0,0,0,0,22 I need to wait for a prompt?
  3. As a follow up, I just realized my bios is detecting this drive as 0MB. LBA fix doesn't seem to be helping. I don't think it's the same as the LBA problem since I started out with the BSY problem, and created this 0MB problem after the fact.
  4. I have two of these drives. I screwed up and used someones post here, which left out the REBOOT AFTER N1 step on the first one. For the second one I went back to page one and used those steps. Thanks! That drive is fine now. My question is about the first drive. The mis-step I took was issuing these two commands with no hdd reboot in between. N1 F3 1>m0,2,2,,,,,22 The disk now detects. I can see it in windows, but in disk management it shows up as an uninitialized drive. Is there anyway I can recover data from it now? What exactly did I do with the F3 1>m0,2,2,,,,,22? ANY help is appreciated!!!
×