jaclaz

I don't. @CrazyDoctor, you have already been told WHAT to look for to determine if a drive is compatible and WHERE to find the info. You have also been already told how switching a PCB should be done AND the procedure that is needed (soldering/desoldering, etc.). You have also been told that a Head swap is NOT something within your capabilities (yet). You cannot ask the same questions, every time you get a new dead hard disk, comeon... If the question is to be intended literally: The answer is NO, and additionally even if the PCB was compatible, I seriously doubt you would be able to do a proper PCB swap, and I am pretty sure you would be able to do a head swap. jaclaz

I see that it's useless trying to convince you that you have a dying hard disk suffering from intermittent problems and that you should start a new thread about the matter, in order NOT to clog this one, which is about a very simple kind of problem (BSY or LBA0) with a fix that invariably results in a binary ON/OFF, either UNbricked and fully functional or bricked. jaclaz

I may add that it is advised to do this with the Registry cleared (or a new installation). jaclaz

My knowledge may be a bit outdated, but in my day we used to CLEAN the contacts, by rubbing them with a contact cleaner, instead of fiddling with connectors pushing and pulling them "some twenty or thirty times in rapid succession" You must be living in a very humid environment if you experienced USB contacts oxidation however. jaclaz

I just checked in my crystal ball and found everything about your photographic needs/preferences, if you could also post your date of birth, I may be more accurate, but what I saw is enough to say: However even with my crystal ball I wasn't able to find a reason WHY you may think that advise about buying a camera has ANYTHING to do with "Hard Drive and Removable Media issues" (which is the Forum where you posted your request). jaclaz

I guess nothing special, but since this: Windows Vista Service Pack 1 All Language Standalone DVD ISO http://www.microsoft.com/downloads/details.aspx?FamilyID=a45652b1-e838-420a-b065-83960458e2ec&displaylang=en is 1418 Mb and this: Windows Vista Service Pack 1 Five Language Standalone (KB936330) http://www.microsoft.com/downloads/details.aspx?familyid=b0c7136d-5ebb-413b-89c9-cb3d06d12674&displaylang=en is "only" 435 Mb I find only human that anyone using one of the five "elected languages" will use the latter. Now if anyone could explain in layman's terms while the Italian MS KB points to the download of this latter version, which includes NOT italian, that would be "special". jaclaz

jaclaz

For the record, 7-zip has read-only access to WIM files ONLY. On XP you can use (if you also have a Windows 7) this tool: http://www.boot-land.net/forums/index.php?showtopic=9765 with this approach you need NOT the WAIK. jaclaz

Generally speaking, motherboards EITHER have USB 1.1 OR have 2.0 USB ports. BUT is a known fact that (and don't ask me WHY - I am just reporting what myself and a number of other people experienced) the ports on the back (the ones DIRECTLY soldered to the motherboard) usually perform MUCH better than "front" ones. It is probable that this is due to either the extension cable from the motherboard to the actual port or, maybe to a "different" USB controller used for the front ports, many may motherboards have problems booting off the front ports. The usual advice is to ALWAYS use a port in the back for "high speed" devices such as external hard disks. There are several tools to identify the bus/controller, a few are listed here: http://www.boot-land.net/forums/index.php?showtopic=4661 Tools like SIV or SIW: http://rh-software.com/ http://www.gtopala.com/ will also do, but even using Device Manager should be enough for a base view of how the buses are connected. This: http://www.nirsoft.net/utils/usb_devices_view.html may be useful to clear the Retgistry from obsolete entries. jaclaz

Your best bet is to inspect it with TESTDISK: http://www.cgsecurity.org/wiki/TestDisk Here is a sample thread about recovering an existing partition from an apparently UNpartitioned or bad MBR Table disk: http://www.msfn.org/board/index.php?showtopic=141687 The screenshot you posted is missing part of the information, but I'm pretty sure it looks like the one in the given link. jaclaz

abnfire, you are OUTSIDE the scope of this thread. Your drive has probably had some intermittent failure - completely unrelated to the actuall "base" issue - that by pure chance appears like solved by forcing the same "reset" as the BSY fix. Now you have an "unbricked" drive with possibly corrupt partitions/data on it, and you don't even know how long it will last. You should start a NEW thread, asking for help about attempting recovering your data. The general ideas are detailed here (examples): http://www.msfn.org/board/index.php?showtopic=138816 http://www.msfn.org/board/index.php?showtopic=144232 http://www.msfn.org/board/index.php?showtopic=144418 http://www.msfn.org/board/index.php?showtopic=141687 http://www.msfn.org/board/index.php?showtopic=141448 http://www.msfn.org/board/index.php?showtopic=138162 http://www.msfn.org/board/index.php?showtopic=84345 jaclaz

Make your choice : AFAIK GHOST is a COMMERCIAL software that uses a PROPRIETARY format, so you will probably need to restore/reimage the images to use them with another app. jaclaz

Maybe it is a good idea to READ FIRST the read-me-first sticky in this very sub-forum: It is there EXACTLY to avoid this kind of problems and reports! Points #7 and #11 deal EXACTLY with the "problems" you reported. jaclaz

...and? Are you going to sue the Win-2K forum mods for hiding info to the MSFN members? jaclaz

Just in case: http://www.softpedia.com/get/System/File-Management/MD5-Check.shtml (one of the many) jaclaz

Actually even TALKING about them is frowned upon and can lead you to a ban: http://www.msfn.org/board/topic/18408-forum-rules-updated-must-read/ But that shouldn't be a problem since you appear like having TWO accounts jtadeo51 jtadeo jaclaz

No that KB should not be related. (the error is different) This one may : http://support.microsoft.com/default.aspx?scid=kb;en-us;314106 But I would rather suspect a bad download "autofixed" by some AV utility: jaclaz

Which OS are you running? Open a command prompt and start nlite from it, this way you will have the complete error message (please post it). jaclaz

Actually you may find a more clear tutorial guide here (still in English): http://www.mapleleafmountain.com/seagatebrick.html (it is actually preferred - by me - as it is very well written and less "confusing" then summing up the original Gradius' guide + the Aviko's mods + the whatever came after it on the present "mega-thread") If you check these pictures: you will see how the connector on the right is the SATA power connector, you simply plug in it the cable coming from your PC (or from an external power supply, like one of these): http://www.msfn.org/board/index.php?showtopic=128807&view=findpost&p=890636 the connector is actually soldered to the PCB. Yes, I do know about the images in the italian version, I will see if I can talk a Mod into fixing them. jaclaz

If I may one of the strangest behaviour for a backup script I have ever seen, what happens if your PC crashes after the old backup has been deleted and before the new backup has been created? What happens if you run AT or SCHSTASKS? http://ss64.com/nt/at.html http://ss64.com/nt/schtasks.html If you know the name of the batch id run, you can anyway search the registry or the disk for it. jaclaz

Yep , I am sorry I mistook abnfire's post as coming from you, my bad. However the doctor joke is still valid. You did report that your BIOS did not detect the drive (which IS a symptom of BSY state and NOT of LBA0). Applying to the drive the fix for LBA0 would in the best case, do nothing, in the worst one create a worse situation. The "doctor" (VideoRipper ) may have worded it in a bit too "funny" way, but given the symptoms you reported, his diagnosis was correct. Thinking to apply a fix "because it's easier" sounds NOT logic (at least to me and to my Vulcan influenced mind) . I wouldn't be so sure about the HP24 firmware not being fixable, though of course NOT part of this thread original scope. I mean, the BSY caused by the stoopid firmware bug bricks the drive. A drive in BSY state can be re-vived by using the BSY (and NOT the LBA0 ) fix. Basically the fix is a "low-level" kind of re-set. It is possible that the reset will "unbrick" also a drive gone into BSY state for a different cause, jaclaz

Just for the record: http://www.boot-land.net/forums/index.php?showtopic=2325&st=22 jaclaz

A man goes to the Doctor.... Doctor: you have a rally bad pneumonia, you need to take these antibiotics thrice a day for one week. Patient: I'd prefer to take an aspirin once. Now seriously, if your drive is sometimes detected (even improperly) and sometimes not, your drive is NOT affected by ANY of the TWO problems this thread is about: BSY LBA0 so it is actually pointless to apply to it the (hopefully) cures for them. If you read attentively the read-me-first: you should be able to see in point #1 that this is pretty miuch a "non-target" of this thread. jaclaz

Well, NO. You have NO elements to backup the bolded statement, had you also tried ALL the other alternatives and ALL of them had failed, you may have a point. Anyway happy you succeeded. For the record and for future memory, this is related to this thread: http://www.msfn.org/board/index.php?showtopic=144754 jaclaz

Yep , but this is the SP1 Beta I do like the way it is worded: no new features and not supported ongoing improvements? jaclaz