jaclaz

Well, you are also probably pretty wrong, as the announcement was given on May 27: http://chrome.blogspot.ca/2014/05/protecting-chrome-users-from-malicious.html jaclaz

What I ALREADY suggested you, and that you completely failed to read or decided to ignore. Try re-reading, slowly this time the read-me-first (which you should have read first), particularly point #5: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ And this post: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-121#entry932258 Try also reading this one: http://www.msfn.org/board/topic/155484-seagate-barracuda-es2-hp-branding/#entry1003378 I doubt I can be more explicit without offending someone. WHAT is the difficult part in them? You were EXTREMELY LUCKY in succeeding to recover whatever you recovered from a defective disk. Now you test it with BOTH the Seagate Short and Long test. If it passes both, then the disk drive is as reliable as it was before the bricking (very little). <- it is of course entirely up to you to decide if you want to continue using it, keeping on it not backed up data, I have a word to define people which will take this decision, but I won't use it as I don't want to offend you . If it fails to pass even only one of the two tests, the disk is gone forever and it should actually be thrown away, or used as a doorholder (or similar). You ALREADY did a BIG mistake in not having those data backed up (before the disk bricked itself) data (if it has any value) should exist ALWAYS on at least two separate media. Like most people you never considered the possibility of a disk failing (this is normal, both that you were not aware of the risk and that a disk actually failed) but now that you know that this possibility exists and you actually already experienced it, you are going to insist on it? I mean: http://en.wiktionary.org/wiki/errare_humanum_est jaclaz

Well, no, no. Meaning: 1) that those articles are seemingly "generic" and NOT specific to "OEM System Builder Kit" or "Enterprise" 2) I can see nothing "wrong" in what is described in http://technet.microsoft.com/en-us/library/hh825089.aspx or in http://technet.microsoft.com/en-us/library/hh825041.aspx BUT if you have found something "wrong" in them, please tell us WHAT EXACTLY it is. jaclaz

http://forum.wordreference.com/showthread.php?t=1056284 jaclaz

Sure jaclaz

DO NOT EVEN THINK of updating the firmware, that is point #5 of the read-me-first: http://www.msfn.org/board/topic/143880-seagate-barracuda-720011-read-me-first/ See also: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-121#entry932258 Try making a DISK image (from Linux and using ddrescue from it). You were ALREADY told what the suggested procedure was, the idea is to start a new thread to get help if you have problems following THAT suggested procedure, not to propose alternate (BTW wrong ) procedures. That disk clearly has a number of issues (of unknown nature) that most probably were the causes that made it a "brick". The fact that you unbricked it successfully has not "fixed" the other (previous and underlying) issues that caused the bricking. Your ONLY chance is to manage to image as many sectors as possible to a disk image residing on a new disk (or however a surely working one), and to do this you need to use tools (such as ddrescue) intended for this type of imaging from defective media. jaclaz

Well, the pins circled in that last image are strangely similar to those in the original post by johnmar http://www.msfn.org/board/topic/129551-unlocking-terminal-of-seagate-es2-in-bsyled000000cc-state/ BTW, re-checking the above, it seems that my memory is not as good as it used to be: the PCB needs to be CONNECTED AND the shortcircuit made, I am correcting my previous post. jaclaz

The $OEM$ folder is the "traditional" way to do this manually, like: http://www.ehow.com/how_7475136_slipstream-drivers-windows-xp.html the reason why very often nlite is (or the driverpacks or both): http://driverpacks.net/ are used is because the procedure is complex and prone to errors. But HFSLIP will also do nicely: http://www.msfn.org/board/topic/63302-integrating-drivers-with-hfslip/ though still some manual intervention/work is needed. jaclaz

You seem like forgetting a lot of passwords (besides forgetting to reply to threads you started ): http://www.msfn.org/board/topic/171838-big-problem-hdd-password-locked/ jaclaz

Not a smart move , Veronica is ugly :, her cousin Victoria is much cuter , check her instead . I'll check the pictures and let you know. jaclaz P.S.: NO you have circled in yellow the WRONG traces. Follow me please. You have 4 sets of 5 contacts at the corners of a rectangle at the center of which there is a hole. Something that can be represented as: 00000 00000 O00000 00000 The read channel is (at least on the other motherboards we have seen till now) the first and second rightmost pins of the top left group of 5 contacts (when, like in your pictures the connectors are on the bottom), i.e.: 000XX 00000 O00000 00000 If you check them, they are connected to 12th and 13th pin (from top to bottom) of the largish IC on the left.I thought that the post here: http://www.msfn.org/board/topic/157329-barracuda-lp-no-not-a-720011-nor-a-720012/?p=1003759 was clear enough

I don' think that lifting the head (or the motor) contact may work on an ES2 drive. AFAIK/AFAICR the PCB needs to be detached connected AND the shortcircuit be made. If it is a BSY or a LBA0 kind of error you can determine by what the BIOS of the machine "sees" (or fails to see). If it cannot detect the disk at all, it is likely that it is a BSY error (but - with all due respect I don't care what you have handy - you may want to procure yourself a suitable OS and run a suitable tool to verify this). If the disk is seen by the BIOS byt with 0 size it is a LBA0 kind of error. If you post two CLEAR pictures of the PCB (one of each side of th ePCB) usually it is possible to identify the two pins to be shorted (the READ channel) see also: http://www.msfn.org/board/topic/157329-barracuda-lp-no-not-a-720011-nor-a-720012/ http://www.msfn.org/board/topic/157329-barracuda-lp-no-not-a-720011-nor-a-720012/?p=1003759 jaclaz

Are they? In any case the procedure is the same. jaclaz

Well, what you should attempt doing is to image the DISK (NOT the drive or partition or volume, NOR "files" inside them) "as is", using an appropriate tool. You will need another hard disk, same size or bigger. Under Linux the suitable tool would be ddrescue (actually it is advised to use Linux and ddrescue), as in the thread you mentioned: http://www.msfn.org/board/topic/170881-seagate-720011-malediction/ and see also this: http://www.msfn.org/board/topic/170938-damaged-logical-structure-of-seagate-720011/ The idea is that ddrescue attempts to read "good" data and keeps a log of what it managed to read, so that access to not read parts can be re-attempted later. Once you have an "as good as possible" image on a surely working disk, then we can attempt recovering data. No, not here (this is an international board and the "common" language is English) In any case. now that the disk is not "bricked" anymore, if you need assistance start a NEW thread (as opposed to continuing here on the "megathread"). jaclaz

Re: the cloud AND NSA This is an interesting article (though a bit longish/needing some time to read): http://www.theguardian.com/technology/2014/may/27/-sp-privacy-under-attack-nsa-files-revealed-new-threats-democracy Among the many arguments touched, I would like to highlight this: I like the idea of a mail server device similar to a phone answering machine. jaclaz

What do you mean "not recognized by windows"? I.e. is the DISK device seen in Disk Manager BUT NO DRIVE letter appears in Explorer? The actual original issue may have been: 1) a BSY the disk is NOT seen/detected by the BIOS 2) a LBA0 the disk is seen/detected by the BIOS Is the disk now seen by the BIOS? If yes, it should also be detected in Disk Manager and this means that it is not "bricked" anymore (i.e. the fix was successful ). Still it is possible that further steps are needed to recover the pre-existing partition(s) or, should this fail, only the recoverable data, see: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=1078040 (for the record , not hidden a zillion pages back in the megathread, it is last post before your original one) jaclaz

Type SLOWLY , AFTER having waited 15 or 20 seconds after having powered the PCB: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=841755 There isn't a "lower" or "upper" side (it depends on the way you look at it), there are the "motor" contacts (which are near the motor) and the head contacts (which are the other set), the recommended guide: http://www.mapleleafmountain.com/seagatebrick.html suggests to try insulating the "motor" contacts, but it may depend on the actual disk and the situation in which it is "bricked", just like the Tx/Rx (if it doesn't work invert the wires), if one sets of contacts does not work, try again insulating the "other" one. jaclaz

Yes. The articles you reference seem to me well detailed, but seemingly your scope is different. The idea of those is to: create a "reference" machine install to it Windows add apps/settings/whatever generalize the image deploy the image to a number of other PC's finish the configuration on the single machinesImagine that you are in the IT of a company and you get 20 laptops for the company's salesforce, instead of installing (or only configuring) and configuring 20 times, you setup a "reference" PC and then replicate it 20 times. In your case: It would IMHO make more sense (since the source and target are the same) to simply have (once the PC is configured) a "bare-metal recovery" capable image (i.e. it makes little sense to generalize the setup, since the scope is to "restore" and not to "deploy"). See (just to get familiar with the slight differences in the terms used) this thread: http://www.msfn.org/board/topic/157634-hard-disk-cloningimaging-from-inside-windows/ Then DISM is as good as anything else to do this, see: http://www.msfn.org/board/topic/153742-dism-improvements-in-windows-8/ All you have to do is: Setup your PC the way you like it Capture an image of it and store it somewhere In case of need boot to the PE, re-apply the image, if needed after having (say on a new disk or if the old disk partitioning was corrupted) create the partition(s) and run BCDBOOT to recreate the \boot\BCD. See: http://wiki.beyondlogic.org/index.php/Imaging_of_Windows_Based_Computers_using_DISM Please understand how this won't be anyway an "exact" copy of the original, and some programs (as an example those that use volume data or disk signature to verify/authenticate) might need to be re-activated. In your case I would prefer a "real" image of the disk (though .wim technology has some advantages, like a high compression and usually it is pretty fastish), or additionally and besides the .wim image, backup/store the relevant data. jaclaz

NO, if a virtual COM port is created and the loopback test works then the driver is fine. Have you checked ALL the points I listed in my previous posts? Have you double-checked them? Have you also double checked the speed/parity/etc? JFYI, by convention when I terminate a sentence with that little "hook" which is called a "question mark", it means that the sentence is a question, for which I would like to have an answer. There are cases where the PCB needs to be completely detached from the disk (as in the first original attempts/tutorial). jaclaz

AND http://reboot.pro/topic/19828-win8pese-wireless-aerthos/ jaclaz

What is the booting sequence in the BIOS? Set hard disk as first device. jaclaz

Try RunAsSystem: http://www.msfn.org/board/topic/155910-taking-back-the-registry-from-trustedinstaller/ http://reboot.pro/files/file/237-runassystem-and-runfromtoken/ jaclaz

Yep. The idea is (generically) to have a way back and "infinite chances", if chkdsk works on the disk, good, if it doesn't you restore the image to that disk (or to a new one) and try another program/method, if it works good, otherwise you restore the image .... jaclaz

Yes. No. No. Yes. It may be wise, but won't change the current status (botched/unknown) of your curret file system. Yes, I would say it is a symptom, not necessarily when you start sneezing you get a cold and this develops into pneumonia , but taking a couple of aspirins and going to bed won't do any harm . Make an image of the disk, NOW! No. jaclaz

Yeah. Type in it: jaclaz

For the record, in my understanding, this: http://www.landesk.com/migrate/xp-support.html Translates to: i.e. it is an added service, besides the need for paying MS for extended support... jaclaz