Jump to content

VideoRipper

Member
  • Posts

    329
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Everything posted by VideoRipper

  1. The only thing I can think of is to make sure that the generated HTML-pages point to the same flash-object in the address-space. After that you'll have to make sure the server returns a 304 ("Not Modified") status when the object is retrieved for a second (or more) time. Greetz, Peter.
  2. Can't you simply setup an (encrypted) VPN-connection to a server in the "Free" world? Or are VPN's also blocked? Just a thought. Peter.
  3. I was already planning on that, though I haven't experienced any performance issues (yet) Already backed up the entire drive... now I'm looking for a lean way to brick it again without raising suspicion (these guys at the shop always check things before they'll swap them) Greetz, Peter.
  4. It took some more effort than I expected. For some reason the DOS-version of SeaTools can't see my drive while it's on a Promise SATA-controler and the Windows version does detect it, but can't do any tests on it So I had to connect it to another PC with another type of controler and tried the short DST test... which failed.. But a long DST test could be done (it took about 90 minutes to do) and it was able to detect a number of errors that could be fixed. Don't know if this is of any interest, but here's the log-file created: --------------- SeaTools for DOS v2.17 --------------- Device 0 is Seagate Device ST3500320AS 9QM22HVN On Intel ICH5 Max Native Address 976773167 Device is 48 Bit Addressed - Number of LBAs 976773167 ( 500.108 GB ) This drive supports Security Features SMART Is Supported And ENABLED SMART Has NOT Been Tripped DST Is Supported Logging Feature Set Is Supported POH 5994 Current Temp 23 Started Short DST 2/12/2010 @ 11:37.4 DST -- FAILED - Read Element LBA = 0 Your SeaTools Test Code: A7E7D56A Short DST FAILED 2/12/2010 @ 11:37.16 --------------- SeaTools for DOS v2.17 --------------- Device 0 is Seagate Device ST3500320AS 9QM22HVN On Intel ICH5 Max Native Address 976773167 Device is 48 Bit Addressed - Number of LBAs 976773167 ( 500.108 GB ) This drive supports Security Features SMART Is Supported And ENABLED SMART Has NOT Been Tripped DST Is Supported Logging Feature Set Is Supported POH 5994 Current Temp 23 Started Long Test 2/12/2010 @ 11:38.8 Your SeaTools Test Code: A7E7D55A DST -- FAILED - Read Element LBA = 963648851 Short DST FAILED 2/12/2010 @ 13:20.9 [ 963580219 -- Repaired ][ 963581115 -- Repaired ] [ 963582011 -- Repaired ][ 963628659 -- Repaired ] [ 963629555 -- Repaired ][ 963631507 -- Repaired ] [ 963632403 -- Repaired ][ 963633299 -- Repaired ] [ 963634195 -- Repaired ][ 963635091 -- Repaired ] [ 963635987 -- Repaired ][ 963636883 -- Repaired ] [ 963638835 -- Repaired ][ 963639731 -- Repaired ] [ 963640627 -- Repaired ][ 963641523 -- Repaired ] [ 963642419 -- Repaired ][ 963643315 -- Repaired ] [ 963645267 -- Repaired ][ 963646163 -- Repaired ] [ 963647059 -- Repaired ][ 963647954 -- Repaired ] [ 963647955 -- Repaired ][ 963648851 -- Repaired ] [ 963649747 -- Repaired ][ 963650643 -- Repaired ] [ 963652594 -- Repaired ][ 963652595 -- Repaired ] [ 963653490 -- Repaired ][ 963653491 -- Repaired ] [ 963654386 -- Repaired ][ 963654387 -- Repaired ] [ 963655282 -- Repaired ][ 963655283 -- Repaired ] [ 963656178 -- Repaired ][ 963656179 -- Repaired ] [ 963657074 -- Repaired ][ 963657075 -- Repaired ] [ 963659026 -- Repaired ][ 963659027 -- Repaired ] [ 963659922 -- Repaired ][ 963659923 -- Repaired ] [ 963660818 -- Repaired ][ 963660819 -- Repaired ] [ 963661714 -- Repaired ][ 963661715 -- Repaired ] [ 963662610 -- Repaired ][ 963662611 -- Repaired ] [ 963663507 -- Repaired ][ 963664402 -- Repaired ] [ 963664403 -- Repaired ][ 963666355 -- Repaired ] [ 963667251 -- Repaired ][ 963668147 -- Repaired ] [ 963669043 -- Repaired ][ 963669939 -- Repaired ] [ 963670835 -- Repaired ][ 963671731 -- Repaired ] [ 963673682 -- Repaired ][ 963673683 -- Repaired ] [ 963674578 -- Repaired ][ 963674579 -- Repaired ] [ 963675474 -- Repaired ][ 963675475 -- Repaired ] [ 963676370 -- Repaired ][ 963676371 -- Repaired ] [ 963676372 -- Repaired ][ 963980854 -- Repaired ] [ 963980855 -- Repaired ][ 963981750 -- Repaired ] [ 963981751 -- Repaired ][ 963982646 -- Repaired ] [ 963982647 -- Repaired ][ 963983542 -- Repaired ] [ 963983543 -- Repaired ][ 963985494 -- Repaired ] [ 963985495 -- Repaired ][ 963986390 -- Repaired ] [ 963986391 -- Repaired ][ 963987286 -- Repaired ] [ 963987287 -- Repaired ][ 963988182 -- Repaired ] [ 963988183 -- Repaired ][ 963989078 -- Repaired ] [ 963989079 -- Repaired ][ 963989975 -- Repaired ] [ 963990870 -- Repaired ][ 963990871 -- Repaired ] [ 963990872 -- Repaired ][ 963992822 -- Repaired ] [ 963992823 -- Repaired ][ 963992824 -- Repaired ] [ 963993718 -- Repaired ][ 963993719 -- Repaired ] [ 963993720 -- Repaired ][ 963994614 -- Repaired ] [ 963994615 -- Repaired ][ 963994616 -- Repaired ] [ 963995510 -- Repaired ][ 963995511 -- Repaired ] DST -- FAILED - Read Element LBA = 964028566 Short DST FAILED 2/12/2010 @ 13:21.0 Long Test PASSED After Repair 2/12/2010 @ 13:21.0 Thanks again for all your help and greetz, Peter.
  5. @Gradius2 (and everyone else that contributed): thanks for this great solution to the BSY/LBA0-problem! Two weeks ago, I had this aweful BUSY-problem, but didn't know it was a known flaw in the HDD's firmware. So after consulting Seagate, I sent my drive to the i365-branch here in The Netherlands (Europe). Not long after, I roamed around the internet using Google (with the description of my problem) and found that other post ("Seagate Barracuda 7200.11 Troubles") and discovered I wasn't the only one and soon saw this thread ("The Solution for...")... ...but I'd already sent in my drive and when the guy of i365 rang me, I explained I wanted my drive to be "Unlocked" so my BIOS would see it again and, if possible, to update its firmware (not telling him I'd read your very informative posts) So I built the RS232 <-> TTL interface from spare parts I had lying around and tested it on some other drives I have in my collection, to be sure it worked properly (even PATA drives work nicely). Because I didn't have to rush things (my drive was already away...) I even made it super-deluxe by putting it into a small enclosure and separate switches for the drive's power and to disable the MAX-232 inside. B) A few days after I received an e-mail with a price estimate for retrieval of my data (I'm a programmer, so I badly wanted my latest source-codes back) and it shocked me quite a bit So I returned the e-mail by stating that I didn't want my data recovered and asked him to return the drive. Well... today the doorbell rang and a courier handed me a nice box with in it... my precious drive. I immediatly went upstairs (to my study) and connected my proudly made interface to the drive on one end and the other end to my test-computer... performed your instructions (I only needed to unlock it from the BSY- state) and... it was working again! It's now busy copying everything to a backup, but I'm sure it will work flawlessly again (though I'm considering updating my firmware to SD1A... but I've heard that version didn't solve the BSY-problem...) Gradius2... you really saved my day (or actually the last two weeks) and I'm forever in your debt It saved me E900 excluding VAT and it puzzles me they actually try to charge you for something that can be done by someone with a little bit of electronics knowledge for around E10 (if you don't already have the parts lying around like I had). I'm even under the slight impression that they just have a template e-mail with some difficult phrases and random numbers to let n00bs believe the drive really is damaged... Maybe I should start my own "Seagate 7200.11 Recovery Service"? Thanks again and greetz, Peter.
×
×
  • Create New...