jaclaz

Both the 4.10.2226 contained in: http://download.microsoft.com/download/0/0/a/00a7161e-8da8-4c44-b74e-469d769ce96e/dsclient9x.msi and the newer 4.10.2228 version contained in: ftp://ftp.catalyst.com/pub/cstools/support/dsclient.exe appear like being the "export" version. I have seen a few references to IE 6 connected with the encryption, maybe there is an updated "non-export" version of SECUR32.DLL in it's install? Or maybe the trick is in "money"?: http://articles.techrepublic.com.com/5100-10878_11-5035024.html OT, but not much, and JFYI: http://support.microsoft.com/dllhelp Mdgx site is back online. jaclaz P.S.: What about this one?: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7c219dcc-ec00-4c98-ba61-fd98467952a8&displaylang=en It contains a Windows 2000 version of SECUR32.DLL. From the .chm inside the download:

YES. But you need to take your own choices, since you are a newbie, probably a good start would be to forget about syslinux and grub4dos "direct use" (BCDW is not anymore supported/developed since years and is NOT the "right" choice - though it still can be useful from time to time) and go for a pre-made tool: SARDU http://www.sarducd.it/ seems like the right one for you (and it uses both Syslinux and grub4dos - so that you can analyze what it does and learn from it) Version 2 was just released: http://www.boot-land.net/forums/index.php?showtopic=12986 jaclaz

Yep, so it is ALSO a failing drive. The general idea of that app is to image in segments, stopping when you hit a "non accessible" set of sectors, skipping some, try getting to them backwards.... In other words, trying to get the most data WITHOUT insisting on "bad sectors", as they tend to "spread" (if coming from a mechanical problem ). If *ALL* sectors behave like that, it is likely that there is some other (still hardware) problem, nothing you can fix "at home", unfortunately. jaclaz

Just to keep things as together as possible : http://www.boot-land.net/forums/index.php?showtopic=8043&st=131 http://sites.google.com/site/rmprepusb/tutorials/multi_boot-wim jaclaz

I seem to remember that it is DUN reinstalling needed. Mdgx's site down? http://webcache.googleusercontent.com/search?q=cache:TC689xZY1OcJ:www.mdgx.com/web.htm+/search%3Fhl%3Dit%26q%3D%2Bsite:mdgx.com%2Bmdgx%2Bdun%2Bweb&cd=2&hl=it&ct=clnk&gl=it Links: KB: http://web.archive.org/web/20050316085327/http://support.microsoft.com/?id=285189 Direct download: http://www.am.net/lib/TOOLS/Microsoft/Win98/se/dun14-SE.exe jaclaz

Try the chkdsk /X on the Volume I:\ If it can work on it, it will do "something more" (or attempt to), otherwise it will set the "dirty" flag on the volume and will do a /F chkdsk at next reboot. jaclaz

Logic check : Since "many has told" AND broken link was NOT fixed/alternate file uploaded, WHAT makes you think that your appeal will have ANY different result from the "many" ones before? WHAT is the problem in downloading the given files/tools then simply copying and pasting the posted batch listing to a new file naming it setup.cmd? jaclaz

Splitting single tasks can be done, but as you have seen is troublesome. A better approach is to split the task, like: N° WBS Description Predecessor 1 1.0 JOB X 2 1.1<indent>Job X (first phase) 3 1.2<indent>Job X (second phase) 2FS+y days 4 1.3<indent>jJob X (third pjhase) 3FS+z days jaclaz

Forget anything else. Check if it has an ATA/ATAPI block password (likely). Read here: http://www.rockbox.org/lock.html http://web.archive.org/web/20020807003206/http://www.upsystems.com.ua/support/alexmina http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml A Secure Erase pre-made is part of the UBCD: http://www.ultimatebootcd.com/ jaclaz

@Sp0iLedBrAt Let's clear things. One thing is a hardware problem, ANOTHER one is a filesystem/partitioning one. DysfunktinaL's one is seemingly a filesystem/partitioning one. @DysfunktinaL you are in a condition similar to the ones discussed in these two threads: http://www.msfn.org/board/index.php?showtopic=141687 http://www.msfn.org/board/index.php?showtopic=145574 Please take your time reviewing them to see what will likely be the needed steps and tools used. Then start posting the needed files (MBR+PBR of each partition) and give some details, OS originally used, etc. Since you are at WD, I guess you have NO problems in getting a new hard disk, a 320 Gb will suffice to dd image (or forensically sound imaging) the problematic drive BEFORE fiddling with it ANY more. This app is suggested (for Windows based PC's): http://www.datarescue.com/photorescue/v3/drdd.htm jaclaz

If you don't mind following some instructions : http://www.msfn.org/board/index.php?showtopic=120444&st=589 http://forums.pcper.com/showthread.php?t=444831 jaclaz

I know I am grumpy, but what the heck! I am completely failing to communicate, evidently. Try reading AGAIN, the read-me-first, point #1 WHAT is the problem with: I won't transform the present thread in "question time about anything connected to a 7200.11", or next one will be some crazy peep wanting to change the preamp or transplanting a platter. You missed also the CATCH 22 issue I exposed: if you cannot find yourself this kind of info, you CANNOT replace a ROM. Maybe I'll make it clearer : I WON'T DISCUSS IN THIS THREAD ANYTHING BUT THE SUGGESTED METHODS TO RECOVER FROM THE MENTIONED TWO ERRORS ON THE SPECIFIC DRIVE. Advice: start a new thread go on a dedicated board: http://forum.hddguru.com/ learn to search the internet please stop going OFF TOPIC in THIS thread. jaclaz

If you want to use a .iso, easiest would be using a known grub4dos+IMDISK method and simply chainload grub4dos from the Isolinux/Syslinux .cfg. http://www.boot-land.net/forums/index.php?showtopic=9038 Otherwise, you can use a "flat" directory structure on the DVD and chainload BOOTMGR from the Isolinux .cfg "directly". jaclaz

WHAT kind of question is it? The method by cdob works. You can use it or avoid using it. (IF this is the actual question) The first post explains HOW it works: The link in it has become "wrong" because the stoopid developers of the board software changed the way they parse links. Here is a working link: http://www.msfn.org/board/index.php?showtopic=12566&st=84 WHAT are you asking? jaclaz

We could make another thread with FGA's: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/fga-not-faq.html If you can suggest me the most recurring FAQ's via PM, I will try to put together a FGA post... jaclaz

EXACTLY. Since FDISK DOES NOT "fix" ANY bad drive sectors and NOT even the MBR, your sentence is perfectly correct. FDISK /MBR (that may be the thing you were thinking about ) doesn't "fix" ANYTHING, it simply rewrites the MBR booting CODE, leaving the DATA exactly as it was before (correct or not). CHKDSK, however, won't even access the MBR. I may be far less authoritative than the guys that actually wrote CHKDSK , but you can read what they write about it : http://support.microsoft.com/kb/314835/EN-US/ jaclaz

Yep. Traditionally using "standard" software on "non-standard" setups has rarely turned out as successful. jaclaz

Expanding on this: MOST modern hard disks have a small "ROM" where parts of the firmware AND specific to the single hard disk "tuning" and "factory assigned" DATA is stored. on these hard disks does not actually mean: it actually means but, since we are talking of SMD components, doing this de-soldering/re-soldering (I mean doing it "right", without burning the chip or the board, or both and or "zapping" it in the process) is WELL ABOVE the reach and abilities of MOST people that ask the question: Moreover you have to find an EXACT (and when I say EXACT, I mean EXACT match) and anyway it is risky, even if properly done, by an expert professional. It's a nice Catch 22: People that know how to swap a PCB may ask if it is possible to do the swap. People that ask if it is possible to do the swap CANNOT do it. @BlouBul I refuse to put in the "read-me-first" such info , following this line of reasoning, I should also put in it : DON'T EVEN THINK to use a chisel and hammer if you don't have an appropriate torx screwdriver DON'T EVEN THINK to open the hard disk DON'T make a voodoo rite to revive the brick NO, dropping it from 1.12 m of height on a concrete surface won't help NO, connecting the mains to Rx and Tx won't work NO, immersing the hard disk in 12 years old whisky (single malt) overnight won't work DO NOT insert the Tx or Rx (or GND) terminals of the adapter up your nose or inside your ears etc., etc. Maybe we could make a separate sticky titled "Things that you should NOT do as they are pointless, futile or potentially dangerous" ? @momo2011 You didn't even state if you were initially affected by the LBA0 or by the BSY problem. Easy decisions path: if it is BSY do the BSY fix if it is LBA0 do the LBA0 fix (please note that the LBA0 normally means that the drive is FUNCTIONAL) if the LBA0 fix doesn't work, try doing the BSY fix first, then MAKE SURE you are in a LBA0 situation and try again the LBA0 fix If #3 above doesn't work, you are most probably in a DIFFERENT situation that is NOT (and will NOT) be covered on this thread, as it is a "non-target" (see point #1 of read-me-first) and most probably well above our heads and experience/knowledge. jaclaz

Your google-fu is low.... http://www.bttr-software.de/forum/board_entry.php?id=4713 Also Rom-Dos Defrag is claimed to be FAT32 and LFN compatible: http://web.archive.org/web/20080502215925/http://ms-dos7.hit.bg/doskbc3.htm Have you tried the FreeDOS version: http://savannah.nongnu.org/projects/free-defrag/ http://download.savannah.gnu.org/releases/free-defrag/DFRAG131.ZIP http://www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.Gall-DEFRAG OT , but not much , Partition Logic has also Defrag capabilities (on FAT filesystems): http://partitionlogic.org.uk/index.html jaclaz

It must be tough living with a broken google , see if you can find something yourself: http://tinyurl.com/23sa46w But, no , I don't think we have a "solution" or a "definite" one for it. You may try to use google translate on these: http://people.overclockers.ru/showman/record1 http://forums.overclockers.ru/viewtopic.php?t=295009 there may be something of relevance. Please, STOP multiposting, this thread is ALREADY filled with an excessive number of postings and NO you cannot SWAP a PCB, and NO you can NOT normally "fix" a PCB (exception made perhaps for a shot TVS diode). This is not "question time", MOST of your questions have ALREADY been asked and replied to, please TAKE YOUR TIME READing what has ALREADY been posted. IF your post is last one in a thread, ALWAYS edit it adding to it new text and NEVER make ANOTHER post just below your preceding one. jaclaz

@h2ofun Please READ before posting. momo2011 posted in this same page he self-built his converter. @momo2011 You got WHAT? jaclaz

YOU CANNOT. CHKDSK checks the filesystem, NOT the partitioning. If you have a MBR/partition table problem you may try using TESTDISK: http://www.cgsecurity.org/wiki/TestDisk Make SURE you read and learn HOW to use it before actually using it. More generally, instead of asking help for the actual problem you are having, you are currently asking help for the way you think your problem should be solved, which may or may not be the right one . Compare with these: http://homepages.tesco.net/J.deBoynePollard/FGA/problem-report-standard-litany.html http://homepages.tesco.net/J.deBoynePollard/FGA/put-down-the-chocolate-covered-banana.html jaclaz

Typically (and that is one of the reason why I won't touch ANY Symantec piece of software released in the last, say, twelve years ) Norton apps tend to write a few hundreds keys in the Registry .... There is a specific tool to remove that huge piece of bloat, if I recall correctly it is Symnrt: ftp://ftp.symantec.com/public/english_us_canada/linked_files/tsgen/ I doubt it. Another thingy worth a shot http://web.archive.org/web/20020121062439/http://powerdefrag.com/ http://web.archive.org/web/20020207182945/http://powerdefrag.com/download/PD0210B2.exe Another known "facilitator" for Win9x is "EnditAll", you can find it here: http://www.compu-docs.com/links.htm Yet another "candidate": http://www.ylcomputing.com/content/view/342/150/ jaclaz

Yes, it happened before, expecially if the paper slip is thick and or screws were tightened too much, see here: Read ATTENTIVELY point #10 of the read--me-first: Guess WHY it was written that way? In a nutshell it says: See if anything here helps: http://buffalo.nas-central.org/wiki/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation @rmg See this report: jaclaz

Go by steps. Open a command prompt. Run in it MOUNTVOL [ENTER] How does the output look? Now run MOUNTVOL | FIND ":\" [ENTER] How does the output look? Now run FOR /F "tokens=1 delims=:" %A in ('MOUNTVOL ^| FIND ":\"') DO ECHO x%Ax [ENTER] How does the output look? Now run FOR /F "tokens=1 delims=: " %A in ('MOUNTVOL ^| FIND ":\"') DO ECHO x%Ax [ENTER] please note how the above has a [sPACE] between "tokens=1 delims=: and the closing double quote: " How does the output look? jaclaz