jaclaz

WHY? Meaning that your problem is that you ran it, most probably without knowing what you were doing and for NO apparent reason. jaclaz

NO prob, BUT : sure it works, if you have the "right" Nokia cable and you find the "right" pinout. AGAIN, READ the read-me-first FIRST, it is there to avoid having yet ANOTHER POST in this thread with the SAME questions, ALREADY answered n times. : Point #10 covers EXACTLY your question. jaclaz

I thought it was a 98SE vs. Me thread, and that you were talking of an updated 98SE. 98SE2Me is a "hybrid", with a "base" 98SE BUT with transplanted relevant parts of Me. (nothing to do with a "plain" 98Se updated) It requires TWO licenses to be "kosher", and is of course not supported by MS, (pleae note the difference between "not anymore supported" and "never supported"). If I am allowed a comparison : 98(SE):XP=Me:Vista The only good thing one can say about Vista is that it somehow forced MS to produce 7 (which is not that bad ). We miss a mature evolution of the DOS based branch, and the thing that mostly resembles it (though of course NOT completely) is 98SE2Me, IMHO. Still IMHO, XP could have been much better had they simply evolved 2K keeping the separation between DOS based (home/fun/single user) and NT based (office/work/multi user) instead of making the one-size-fits-all XP. jaclaz

First: Try opening logical sector 63 of your physical hard disk or sector 0 of the logical drive. Check that it's contents loosely resemble the one on the given page: http://thestarman.pcministry.com/asm/mbr/MSWIN41.htm (in other words check that you can read "FAT32" in it) Select it's contents. (one sector) Copy them. Create a new file. Paste to it the contents. Save the file somewhere as "bootsector.dat" Second: Try opening sector 63+6=69 of your hard disk or sector 0+6=6 of the logical drive. Check that it's contents loosely resemble the one on the given page: http://thestarman.pcministry.com/asm/mbr/MSWIN41.htm (in other words check that you can read "FAT32" in it) Select it's contents. (one sector) Copy them. Create a new file. Paste to it the contents. Save the file somewhere as "backup_bootsector.dat" Then: Compare the two files "bootsector.dat" and "backup_bootsector.dat": IF no differences are found, the message is related to something else IF any difference is found the two sectors are "out of sync" jaclaz

Neither. 98SE2Me http://www.msfn.org/board/index.php?showtopic=46349 jaclaz

Well, your search-fu is very low. Otherwise you would have found this: http://www.msfn.org/board/index.php?showtopic=145751 Right know all we know is probably how to kill for good a 5400.6 jaclaz

The whole idea of a read-me-first: is to actually READ it BEFORE posting yet another time the same question, ALREADY answered n times.: WHAT is the difficult part in the above? In other words, this thread is ONLY for 7200.11 and ONLY for the 7200.11 affected by this specific problem. It is not a "miracle cure" for ALL hard disk. It is not a "miracle cure" for ANY problem on ANY hard disk. Will it work on your 7200.12 affected by whatever problem originated by whatever cause? Yes/No. (or if you prefer the answer is "a suffusion of yellow") Start a new thread if you want (hopefully) some support for your problem, but DO NOT expect anything actually tested, reliable or accurate, noone here is a "Hard Disk Expert". Had you spent two minutes in SEARCHING for 7200.12, you would have seen these: http://www.msfn.org/board/index.php?showtopic=145646 http://www.msfn.org/board/index.php?showtopic=134961 And also had taken the time to read just five posts above yours, in this same page .... jaclaz

With all due respect, doing this: after having been suggested to: Sounds a lot like: after: Or: Let's start again from the basics, OK? Do you know what a disk editor or viewer is? Have you got one? If not get one from here: http://thestarman.pcministry.com/asm/mbr/BootToolsRefs.htm You want a disk editor, NOT a partition manager. HXD is a disk editor (and runs on 9x also): http://mh-nexus.de/en/hxd/ PTS is a disk editor and works in DOS: http://thestarman.pcministry.com/tool/de/PTS-DE.htm Do you know what a bootsector is? Do you know where you can find it on your disk? jaclaz

I did re-read it, but still it seems to me like some vague reference to re-installing a directory is present: jaclaz

JFYI : http://www.marriedtothesea.com/041808/this-is-what-i-get.gif jaclaz

Waiter, come taste this soup.... http://www.imdb.com/title/tt0094898/crazycredits Ahaaa... jaclaz

Normally a "wiped" hard disk is ALL 00's, as well a "pristine one" contains in non-used sectors 00's (and NOT FF's). When there is "localized" problems (like a bunch of bad sectors, like the ones you seem to have around sectors 1600400) usually other parts of the hard disk remain readable/are untouched. But it could well be a defective head. Unfortunately it is not easy to even diagnose it "remotely". You can try opening the \\.\physicaldrive in a disk editor (tiny hexer suggested): http://www.boot-land.net/forums/index.php?showtopic=8734 and search for the first occurrence of 0000. File->disk->Open drive->(choose correct \\.\PhysicalDriven Then Edit->Find/Replace->0000->Find Press "yes to all" to continue scanning past the first sector. jaclaz

From "common sense" (not having the faintest idea what diskminder is or how it works ) it could be that the partition (which should be formatted with the FAT32 filesystem, from it's size) has the backup bootsector (sector 6) out of sync from the main one (sector 0). http://thestarman.pcministry.com/asm/mbr/MSWIN41.htm Just check them with any disk editor. If you did NOT reformat the partition under WIN9x, and simply exchanged the previous bootsector invoking NTLDR with one invoking the IO.SYS (by using bootpart, or a similar utility, possibly even SYS.COM behaves like that ), the backup will still contain the "old" bootsector. jaclaz

Check GROUNDING. "random" characters may come from that. CHECK the read-me-first, point #7: EVERYTHING should be GROUNDed. CHECK the RS-232->TTL converter: is it at 3.3V levels? (or post a link to where you got it from) jaclaz

I have serious doubts about your command line. -eltorito-boot and -no-emul-boot look a lot like fighting each other.... The: -hide-joliet-trans-tbl is essentially pointless: http://en.wikipedia.org/wiki/TRANS.TBL The: -duplicates-once should be of scarce utility in a build such as these PE3 thingy The: -force-uppercase is a choice , but shouldn't actually be used normally, as it can create other kind of problems on certain builds. This is known to be working for grub4dos: http://www.boot-land.net/forums/index.php?showtopic=9696&st=26'>http://www.boot-land.net/forums/index.php?showtopic=9696&st=26 Read the whole thread, you may need to check the case of grldr: http://www.boot-land.net/forums/index.php?showtopic=9696 jaclaz

cuudulieu already tried his luck with the friendly guys over at hddguru : http://forum.hddguru.com/seagate-barracuda-7200-cc44-t15592.html http://forum.hddguru.com/7200-erorr-firmware-cc38-t16552.html http://forum.hddguru.com/seagate-7200-st31000333as-cc1f-clicks-during-post-t14997.html from the general tone of his posts: he has NOT a good familiarity with English (apparently he is from Vietnam) he is not an "innocent" home user with a problem caused by the morons at Seagate: he looks a lot like a wanna-be-pro attempting to run a business out of HD recovery he even appears to own a PC-3000 (real or fake) <- this is specialized hardware costing a few thousands bucks (real) or several hundreds (clone) Maybe he needs a more explicit text: @cuudulieu WE ARE NOT HD HARDWARE SPECIALISTS WE DO NOT KNOW ANY ANSWER TO YOUR QUESTIONS STOP POSTING YOUR PROBLEMS EVERYWHERE IT WILL ONLY MAKE BOARD MEMBERS ANGRY AT YOU Please, DO NOT DOUBLE POST (see Rule #2.a): http://www.msfn.org/board/topic/18408-forum-rules-updated-must-read/ jaclaz

Hmmm, I presume the drive has already died. The file contains ONLY FF's. No way out "from a distance", unless a pro has a look at it and diagnoses what the problem is. Several things may have happened, some easily fixable, some fixable but out of your reach (even if guided) and some stil fixable but only by a pro with the adequate hardware and software, plus a limited number of things that could have made the disk completely unrecoverable. Any "strange" noise coming from the disk when it spins up? Like a vibration or repeating attempts to read (click/click/click)? jaclaz

Yep, it's just a "half a**ed" htm page with a bunch of javascript in it, really not my field, it was intended as a quick and dirty tool for internal use, but since it ended up as being only dirty (and not quick at all ) I put it online so that othere people may use it. It is intended ONLY for links to posts (and forums) and is VERY far from being complete, or "fully functional", but it (sometimes) works, even when it doesn't, it mostly works, i.e. with a minimal manual correction to the result it can be made working. If anyone with a better knowledge of javascript is willng to give suggestions, provide better code, etc. I'am all for it. @Fredledingue Link in my signature. The matter was discussed here: Oops, I mean here : http://www.msfn.org/board/index.php?showtopic=137119 jaclaz

*usually* yes. Mainly, TESTDISK, but in some occasions manual intervention is faster/better (and even easier ). Two threads about similar issues solved: http://www.msfn.org/board/index.php?showtopic=145574 http://www.msfn.org/board/index.php?showtopic=141687 Generally speaking the RAW filesystem (provided that the partition is still actually seen) is due to a missing or plainly wrong bootsector or to a pointer in the partition table misplaced/pointing to the wrong address, the two given threads show the two mentioned different problems leading to the same effect. Particularly I would appreciate this occsion to contradict you : Actually the probabilities of recovering a NTFS partition that became "RAW" is very, very HIGH (nearly 100% if the problem is one of the mentioned ones or a similar one). The problem of the OP may however come from other reasons: It could well be a dying hard disk.... Call me any name you want , but in my book anyone who somehow escaped from the 7200.11 BSY or LBA problem and does still rely on the fixed drive (and has not a proper, Full backup) *deserves* NOT any help with data recovery... jaclaz

"shooting one's foot, but programmatically": http://www.kirchwitz.de/~amk/shoot_foot.shtml jaclaz

Problem is that we DO NOT know what the problem is, nor if a solution exists at all. Similar messages on the 7200.11 mean that the drive is in BSY or LBA0 state. So you can try the "7200.11" fix, but there is NO guarantee whatsoever that it will help you recover the drive (or the DATA in it). For all we know those sets of commands applied on a 7200.12 could also put the drive on fire or make it blow up. JFYI: http://webcache.googleusercontent.com/search?q=cache:VhOffLbD30QJ:www.salvationdata.com/forum/download/file.php%3Fid%3D494 What this means, if it applies to your particular drive or case, etc. etc., we cannot say. The command: [quote]F3 T>m0,2,2,0,0,0,0,22 (enter)[/quote] appears like being a "general reset" of some kind, but there is NO way to know if it is applicable to your situation, compare with point #1 of the read-me-first for the 7200.11: jaclaz

I don't want to seem more grumpy that I really am, but evidently you completely failed: to read the stickies and, expecially, the read-me-first: to take some time browsing and searching on the "main" thread: NO. (please note how the last character in the above line is a "dot" or "full stop" or "period") JFYI : http://www.msfn.org/board/index.php?showtopic=128807&st=3063 jaclaz

Unfortunately I doubt this will happen. This: appears like a question aimed to telepaths or clairvoyants, that usually do not post on the board.... With reference to this: http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html We are right now at the "I'm ill, doctor. Help!" stage. Please provide some meaningful details, as-is the question is not understandable, let alone answerable. jaclaz

The read-me-first covers this topic nicely IMNSHO: Point #5. Please read it attentively. Updating the firmware is the LEAST and LAST of the problems. Forcing an update is NOT adviced. Also review the conversation with Falcon7, some 25 posts starting from here: Take your time reading the thread, most of the answers are ALREADY in it. jaclaz

What the heck are you running? That screenshot tells you that you have I/O errors around sector 1600400 hex, which means around sector 23,069,696 which means around bytes: 23,069,696x512=11,811,684,352 i.e aroud 12 Gb! You need first 51,200 bytes or 51,200/512=100 sectors. You told the program to image first 51,200 Mbytes! http://www.datarescue.com/photorescue/v3/drdd.htm In the LOWER set of boxes SECTORS, you want to have 0-100-100 (in the UPPER set of boxes, Mbytes, you will see 0-1-1 which is a rough approximation of the very small amount of needed sectors) jaclaz