jaclaz

Of course. Can you tell me how to write double quotes in Italic on command prompt? (unless you use ALT+0147 and ALT+0148 - and that's NOT "italic") No, it is NOT. Copy and paste the following in a new, empty Notepad window: BAD QUOTES :“” GOOD QUOTES :"" Save the file. Open it with a hex editor: You will see how the double quote is character 22 whilst left and right quotes are character 93 and 94 hex Exactly. jaclaz

An only seemingly unrelated consideration: http://www.pcguide.com/ref/hdd/file/partFAT32-c.html Such a big partition with smallish cluster size may have different performance with different amounts of available RAM. jaclaz

Sure , google-fu is behind the green glass door, but peeps in it do not master it, nor get the hang of it.... They should really double and triple their efforts, actually progress to attain and accomplish threefold current awareness of this matter . jaclaz

Just to try and understand, the "right" things are the plain "double quotes", so if you TYPE the commands given in the Tutorial they will work BUT if you attempt a copy and paste it will fail? jaclaz

Well, it depends on which version of *anything* you are using, I presume. Quantum compression has been discussed here: jaclaz

...and in the wrong place. See here : Install Windows from USB http://www.msfn.org/board/forum/157-install-windows-from-usb/ jaclaz

Connect the hard disk. Boot and get to the BIOS setup. Can BIOS see the disk? Yes/No If No it's probably in BSY state If Yes, then does it show it's size in BIOS as LBA 0? Yes/No If Yes it's definitely in LBA0 state. WHAT caused the BSY or LBA0 state? Will the proposed fix work on the particular BSY or LBA0 state? ...the answer my friend, is blowing in the wind.... jaclaz

MInd you the following is my PERSONAL opinion. There are reports of the i365 guys to be either extremely correct and honest or completely nuts and false (up and beyond the border of "robbery") I suspect that this may depend on several factors including: the actual "channel" through which your drive was sent to them the actual "operator" that actually puts his/her hands on your drive Point is whether your drive was originally affected by either LBA0 or BSY problem, what we commonly define as "bricked" as in: For what we know: it is NOT possible to upgrade the firmware UNLESS the drive is "unbricked" first. once the drive is unbricked (and WITHOUT ANY firmware upgrade) it won't re-brick itself spontaneously for at least three months of daily use (six to twelve month being proven to be the most likely cases) logically NO data recovery service would (though it is possible) re-brick the drive after the firmware upgrade actually upgrading the firmware has NO (immediate) consequence to the actual "brick status" of the drive If I were you (and mind you - AGAIN - this is just my PERSONAL take on the matter), if you are sure enough of the symptoms your drive had when it failed, i.e. you are confident enough that it was in a LBA0 or BSY state, I would call the bluff and get the drive back. Mind you also that there is a line that is quite "elastic" between "recovering a drive" and "recovering the filesystem", and even another elastic line between "recovering the filesystem" and "recovery of MOST contents of it". PLEASE go to "Search" and search for "i365" make sure you select "Show results As posts" and take some time reading the results (you'll get two pages of results): http://www.msfn.org/board/index.php?app=core&module=search&search_in=forums Come back when you have read ALL those posts and have a better idea of the past experiences of the other members, as said quite contrasting. jaclaz

Dear user , you have probably been pointed here because you completely failed to read the FGA's and particularly FGA #1: You also completely failed to read the main thread, where very often a new member, just like you, thinks to be smart and that he can get away with a PCB swap, a few examples: http://www.msfn.org/board/index.php?showtopic=128807&st=1821 http://www.msfn.org/board/index.php?showtopic=128807&st=2173 http://www.msfn.org/board/index.php?showtopic=128807&st=2240 http://www.msfn.org/board/index.php?showtopic=145290 Now, swapping PCB's is in this case a very bad idea, and deemed to failure. It is NOT new, and it´s offending the intelligence of the people who found/developed the methods to recover from a BSY or LBA0 error, and a kind of lack of respect towards the ones that try to help others in following that procedure, and that spent a lot of time in wording both the read-me-first (which should be read FIRST): and the FGA's: It also does not stand a logical verification. You had this great new idea, allright : since it's new, then noone has ever tested it, thus noone can possibly tell you if it will work or it won't. On the other hand, asking if it will work on the main thread dedicated to bricked 7200.11, implies that you presume that peeps in there do know where their towel is, and know more (or better) than you on this specific topic. So, these guys/gals are recommending a rather complex procedure, involving a data converter and issuing a set of commands to the drive, and you come to ask them if a much simpler procedure (swapping PCB's) will work? What do you think they will answer you? A typical answer would be: [sarcasm] Sure it will work, the reason why we use and advice another and much more complex and error prone procedure is basically because we like deceiving other people and make things that are completely unneeded, and besides we are covertly financed by the USB-to-TTL and RS232-to-TTL sellers lobby, we already tricked several hundreds people into buying this completely unneeded hardware, so we are pretty good at it. [/sarcasm] As a known shoe manufacturer would say: Just do it! Only, please don't come here whining it didn't work. jaclaz

For NO apparent reason : jaclaz

Oh, my ! Do you mean that the battery actually (when tested with a voltmeter/multimeter) does give 3 V (or whatever it should give) BUT that the BIOS cannot hold the settings? Have you tried ACCURATELY cleaning contacts on the motherboard's battery holder/connector? jaclaz

Well, for the record the "initialize disk" is there since at least Win2K (really cannot remember NT 3.51/4.0 had the same , but I would think yes). JFYI : http://reboot.pro/12253/page__st__8 jaclaz

Pheew. But you have the screenshots, and you can manually add new partitions: http://www.cgsecurity.org/wiki/Data_Recovery_Examples#Two_FAT32_partitions_to_recover Only, it is not advised (better wait a few hours and avoid a possible mistake) jaclaz

Sure , guess WHY the drivespack were developed? http://driverpacks.net/ jaclaz

Sorry, but NO (meaning that you did *something* before thoroughfully checking, as you were told it would be needed). You write what you see. If the partitions were not listed when you hit Write they won't be there, that is essentially the meaning of my previous post. You might have deleted them accidentally before the disk scan, but if you did so, they were NOT there when you hit the Write. jaclaz

Specific to the CONTROLLER (not on the disk model). Also, performance advantages depend on hardware. If you have "old" hardware it is likely you won't have any. JFYI: jaclaz

You are welcome (and deserve a place in the basket ): I try my best at it, thanks. jaclaz

Leave them alone. Mark ONLY the partition you want to undelete with L. Go back to the partition view, and it should contain the SAME partitions as in the Log you posted+the one you just marked. If it is so THEN write the new partition tables. Compare with point "Partition table recovery" in the given: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step In other words, BEFORE you WRITE you need to make sure that everything is EXACTLY as you wish it to be. If in doubt DO NOT write the partition tables. Until you hit the "write" and confirm with "y" everything is "virtual" and you can easily start again. jaclaz

Wait before doing something you may later regret. Data gathered needs to be analyzed BEFORE deciding WHAT to do (and doing it). The Log has this data: Analyse Disk /dev/sdc - 1000 GB / 931 GiB - CHS 121601 255 63 Geometry from i386 MBR: head=255 sector=63 NTFS at 0/32/33 NTFS at 4171/87/13 NTFS at 82496/120/57 Current partition structure: 1 * HPFS - NTFS 0 32 33 4171 87 12 67010560 [Windows 7] 2 P HPFS - NTFS 4171 87 13 17225 129 56 209715200 [Ebooks n Pictures] 3 E extended LBA 82496 88 25 121601 25 24 628217856 5 L HPFS - NTFS 82496 120 57 108604 206 18 419430400 [Software Music n Gamez] The "deep scan" screenshot has found more partitions than the one(s) you apparently deleted. Can you couple the drive letters in your first post to the actual volume labels as found by testdisk? If you are positive that the drive was a logical volume inside Extended, mark it as Logical. From what you posted, it seems like the one you deleted is the one with label "[backup n Workshop]", which yes, it's a Logical drive inside Extended, but double check, see if you can see through testdisk the actual files that were in it before writing the partition table: http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step jaclaz

Refer to this thread: Why it is so difficult? (No, don't reply it is a rhetorical question) jaclaz

Just for the record, the "calendar" in the Board Search "Find by date" only goes back to 2005, though it is possible to manually set back the date by correcting the year value entered in the text box, it would be nice if it could be made to start on 2001, jaclaz

I guess it's all about each app doing what it is supposed to do. RMPREPUSB is designed (and has quite a bit of tricks up it's little sleeves), to properly partition and format a USB stick and optionally install to it the grub4dos grldr.mbr to the MBR (and a few hidden sectors). Normally WinsetupfromUSBwithGUI can replace the normal 2K/XP MBR (written to the stick by RMPREPUSB or another utility) with the grldr.mbr. In some particular cases it cannot. This may due to a number of reasons, my guess is that it more or less it is a timing problem of some kind when accessing the \\.\PhysicalDrive (when running XP) or running Windows Vista or 7 that have *enhanced* (ahem) protection schemes. There could also be some hardware dependant causes, but I personally doubt it. The proposed solution/workaround is nothing but "common sense" , imagine that every time you would print a document you would: print a random different document erase completely the printed document re-use the blanked sheet of paper to finally print the "good" one jaclaz

If all you did was to delete the partitions on disk management, (or diskpart) you can probably get them back in a relatively easy manner. Get TESTDISK and run it (with a LOG file): http://www.cgsecurity.org/wiki/TestDisk Take some time to read the documentation BEFORE running it. DO NOT write anything to the disk. Post the log after you have done a Search for lost partition AND a "deep scan". jaclaz

NO. Why people don't READ BEFORE asking over and over the same questions? FGA's<. Frequently Given Answers: It is friggin' FGA #1: 1. I have exactly the same HDD in my other computer. Will a PCB swap work? No. Although that used to work on some older models, in newer HDD's like the Seagate 7200.11, the PCB is specific to the drive and you risk frying both if you try that. Is there something difficult in the above? Read here: AND here: jaclaz

Welcome, au3fan . Why not adding something like "established since 200x (and still going strong...." ? Should be 2001, right? jaclaz