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

Points added/stressed on "read-me-first". jaclaz

I'll add a more explicit warning. Well, that is the problem if I would write that CA-42 cable doesn't work it would be a lie , they do work, most probably ALL of them, original and "fake", do work, IF: the cable is NOT damaged when opening the connector the CORRECT connections are found the cable is NOT damaged in attempts to find the righ connctions the PROPER driver is found the PROPER driver is PROPERLY installed We have reports of people trying as many as 4 or 5 "CA-42" cables from different sources before finding one that worked for them. As I see it, if you ALREADY have a CA-42 cable lying around in the "things that may be of use some day" drawer, you have nothing to lose in trying it , but if you have to buy one you'd better invest some more money in a "proper" TTL converter, known to be always working. I will try to add the above to hopefully better clear the situation. You are welcome. jaclaz

But is Isobuster a .iso EDITOR (which was the OP request)? Last time I checked it it was a CD recovery tool... Anyway, I would hope that in the 5 years since May 2005 OP has found a solution to his problems....:whistling: jaclaz

Well, you may have "skimmed" through the given thread, but probably NOT actually "read" it. Try again, expecially points: #5 (where it is said that firmware update can ONLY be applied on an unbricked drive) #10 (where it is said to "Please DO NOT use a CA-42 cable BECAUSE there are so many versions that it is unlikely that you get the right one at first attempt"): #10 (where it is said to "Please use ONLY a 3.3v TTL level interface") : #11 (where it is said to "Please search the main thread for links to converters that were reported to be working") : No, that converter you were talking about may work, but you are taking chances that the controller on board is "5v tolerant" something for which we do not have definitive evidence, in a nutshell: 3.3v will work 5v/3.3v may work 5v WON'T work Why taking chances with your data? We can put a link to a cable on e-bay , most probably you were looking at this: http://cgi.ebay.co.uk/USB-TTL-Serial-Cable-/290445149419?cmd=ViewItem&pt=UK_Computing_CablesConnectors_RL&hash=item439fe144eb For a couple of quids more, you can get this one: http://cgi.ebay.co.uk/USB-3V3-Logic-converter-3V3-regulated-output-/310151928700?cmd=ViewItem&pt=UK_BOI_Electrical_Components_Supplies_ET&hash=item48367edb7c which should be the "real thing". I tried my best to word that post as accurately as possible, but obviously being English not my mother tongue I may have created something that is not easy to understand, since you are from the UK, if you have any suggestion to make the above concepts more clear, you are welcome. jaclaz

Well, no. We can make a guess, point is whether it will be accurate... jaclaz

NTFS is a rather "bulky" filesystem for very little sized volumes. Strip from the file first 0x2000 or 8192 bytes and save as bottsdi.raw. Open this file with 7-zip and you will see the NTFS filesystem structures that occupy a lot of space. The problem was talked about many years ago when Mark Russinovich made possible to have NTFS formatted floppies: http://freewareapp.com/ntfsflp_download/ http://web.archive.org/web/20000511191617/www.sysinternals.com/ntfsflp.htm http://web.archive.org/web/20000511191617/http://www.sysinternals.com/ntfsflp.zip It seems like the Log file can be reduced from the current 524,288 bytes to 262,144, that at the time was found to be the bare minimum. Compare the NTFSIMG in the download with the bootsdi.raw file in 7-zip . jaclaz

What you report does not make (much) sense. Your drive is EITHER "bricked" OR NOT. (binary, 0/1, Yes/No, On/Off) I.e. it is EITHER seen and normally accessible AND THEN you can update it's firmware OR it is not (and then you simply cannot do ANYTHING to it). Please do read the read-me-first: It should (hopefully) clear your doubts about the symptoms you should have, the reason why you have them and the way to fix them (hopefully). Seagate has been VERY UNLIKE "linear" in it's approach to recovering data (for free or for a charge), but I doubt that ANYWAY it will cover "OEM" hard disks. Search the board for posts containing keyword "i365" (that's the name of the Seagate Recovery Company). It is against the Rules of the board to offer such services (see Rule #13): http://www.msfn.org/board/topic/18408-forum-rules-updated-must-read/ But the procedure is relatively easy, the cost of the interface is trivial and I am pretty sure you can find among your friends someone with an even minimal electric/electronic experience capable of following the needed steps, provided that the symptoms are the "right" ones and thus the solution is actually the "right" one as well. If you have no friends with such experience, most probably your local computer shop or maybe mobile phone repair shop can do the fix and already has the needed hardware. jaclaz

Qemu is free and small (even with Qemu Manager): http://www.davereyn.co.uk/download.htm it will be slightly slower than other Virtual Machines, but for a "once in a lifetime" use it will be more than enough AND it uses "standard" virtual hardware and installing XP on it needs NOT "fancy" drivers. jaclaz

LWD method: http://www.littlewhitedog.com/content-9.html Gallery: http://www.littlewhitedog.com/content-17.html My personal bootscreen : /noguiboot jaclaz

Murphy's Law is there EXACTLY to prove itself right in these occasions. If you connect the HD on both XP and Vista/7 AND you have a "particular" setup (but nothing too fancy) AND you used Disk Manager on it from XP, it is also possible that you fell in this problem: http://www.boot-land.net/forums/index.php?showtopic=9897&hl= It is not clear from your report if the problem is "partition related" or "filesystem related", if the latter it is possible that you have some strange "backup or replicating" service running (and badly configured) or that you somehow use a cache program and delayed writes failed (like switching off or disconnecting the thingy before changes were committed). Anyway, unlike the 7200.11 problems, your problems seem to derive NOT from hardware problems of the hard disk, whilst they may depend from a hardware problem of the USB controller inside the external case. jaclaz

Choosing a program (once decided if going "Freeware" or "Commercial") and actual probabilities of getting back the needed data depends by a couple of factors: HOW the drive was formatted "before" (which filesystem) AND IF the filesystem was defragmented recently HOW the drive has been formatted "after" General ideas are exposed here: Just as an example, if a drive was NTFS and has been re-formatted as FAT32, chances are that you can recover 100%. The actual Operating System used to format may (please read as "will") make the difference. If the drive was FORMATted as "Full" under Vista/7, probabilities are 0% (zero percent) as under these OS the Format command actually WIPEs the filesystem: jaclaz

For the record, your guess is wrong, the problem was that you initially failed to give out the needed details. And yes, removing the contents of your original post only makes the provided solutions more difficult to be of use to any other member. The original post was about a way to identify files with names in a format like: and delete latest (or the previous one). jaclaz

Only too happy to have contributed to another happy bunny : http://www.msfn.org/board/index.php?showtopic=128727&st=10 jaclaz

Yes, it is correct, provided that your USB floppy has Vid=0409 and Pid=0040, BTW it is one of the id's tested and reported as working (see post by MrRoberts): http://www.msfn.org/board/index.php?showtopic=82711&st=7 BUT your txtsetup.oem is a "multiple hardware choice" one, so that will ONLY work if your adapter is "PCI\VEN_8086&DEV_282A&CC_0104", and NOT if it is ANY of the other ones. In other words, unless you know for sure which PCI\VEN the board is, you should try adding the: line to ALL of HardwareIds.Scsi items: jaclaz

IF I actually understood what you are looking for , you want something that performs a Fourier transform analisys and comparison on the .wav's. See if these fit: http://www.primianotucci.com/default.php?view=77 http://sourceforge.net/projects/fourierrocks/ http://php.indiana.edu/~jhallida/spanform/spanform.htm jaclaz

There are several approaches to your problem, basically: have your USB floppy being recognized during setup: http://www.msfn.org/board/index.php?showtopic=82711 have a virtual floppy during setup: http://www.msfn.org/board/index.php?showtopic=137461&st=29 integrate your drivers to the XP source (on a new CD/DVD): http://unattended.msfn.org/unattended.xp/view/web/35/ http://unattended.msfn.org/unattended.xp/view/web/36/ (this is just one of the methods, if you are NOT in a Commerial environment you can use the nlite program) integrate your drivers to the XP source (on a USB device like a memory stick or external hard disk and install from it): http://www.msfn.org/board/index.php?showforum=157 (check FAQ's there is a link to BTS Driver Packs, possibly they already contain the right driver) Please take into account that - generally speaking - Dell's do have some quirks, BOTH in the XP CD's they ship with (but this is not your case) AND with USB support, so your mileage may vary. jaclaz