jaclaz

Well, jds has the right attitude to be our lab rat and report. Since the "high encryption packs": http://www.microsoft.com/windows/ie/ie6/downloads/recommended/128bit/default.mspx Contain: ADVPACK.DLL enhsig.dll ie5dom.inf rsaenh.dll sch128c.dll W95INF16.DLL W95INF32.DLL I would suspect a check for one of the bolded files (or a specific version of them), but let's wait for test results. jaclaz

This "new" theme (being very similar to default ones) is IMHO, MUCH, MUCH better than the AWFUL ORANGE/BLUE one (which was the only GUI actually worse than LCARS to non-vulcan eyes ever seen on any planet of the confederation, probably Vogons or Klingon may have appreciated that). If I may the colour of text is a bit too light to make adequate contrast with the background, a "full black" as in this sentence is more readable. (and a dark blue like in this sentence would give even better readability) Can I ask if links syntax is finally "stable"? It seems like my half a§§ed converter needs again a revision, and I would hope this to be last one. jaclaz

I guess that the actual explanation comes hear-hear from the NSA: http://www.nsa.gov/ia/_files/os/win2k/w2k_winnt_9x_clients.pdf (page 9) That would explain everything nicely. The actual file on the Server 2000 CD should be the one available also here: http://www.xlightftpd.com/faq.htm It also seems like the good MS guys have of course managed to make an incompatible (with their OWN product) .dll : http://kbalertz.com/278243/Error-Default-Start-Outlook.aspx This should mean that the install routine *somehow* detects *something* and patches on-the-fly the "Export" .dll to the "U.S. and Canada Only" version. jaclaz

What filesize, what version? jaclaz

Either lots of people send e-mails to you or you really like to be hassled very often...... (or you actually have a very strict amti-spam policy and then you will get the actually important messages only once a week ) Murphy's Law applies to e-mail anti.spam filters too. jaclaz

You mean you didn't trust my word for it? Current question is: would the "other" download and the 2K .dll work on windows 9x? jaclaz

On average, before the expected six months : possibly depending on the number of boots/reboots you made, but the "expected" is just a probability of winning throwing a coin.... jaclaz

Only for the record, here is the stupid unavailable update page: http://web.archive.org/web/20040302004257/http://support.microsoft.com/?kbid=323466 @triger49 Seemingly the file at: http://support.microsoft.com/kb/q267972/ http://download.microsoft.com/download/win98/update/9766/w98/en-us/266772usa8.exe contains two different versions of the "Export" version also, renamed as secur32.98g and secur32.98s jaclaz

Then go here: http://www.boot-land.net/forums/index.php?showforum=71 read, and learn. I personally find grub4dos: http://www.boot-land.net/forums/index.php?showforum=66 (please READ ALL the stickies in the above FIRST THING) more flexible/logic than Syslinux/Isolinux/Memdisk: http://www.boot-land.net/forums/index.php?showforum=92 but since they can be easily cross-chainloaded, the best choice is to choose whichever you like best (and use the other only for something fro which the one you chose is not working). Please, do not use that bolded character, it''s not needed, won't grant you ANY more attention, and will soon make someone fed up, compare with Rule Guideline #11: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules 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