jaclaz

As said in the thread linked to by erpdude8, the Datapol NTFS4DOS is the only FREEWARE read/write tool available for NTFS drives. There are the commercial apps from www.wininternals.com too. abot ext2: The filesystem driver by John Newbigin prathapml linked to is very good under NT/2k/XP, whilst with win9x system is still a bit experimental. Also have a look at ltools: http://www.it.fht-esslingen.de/~zimmerma/s...are/ltools.html Other links (NT/2k/XP related): http://www.acc.umu.se/~bosse/ http://freesourcecodes.tripod.com/ext2.htm http://ext2fsd.sourceforge.net/ jaclaz

Yep, sorry, I meant SFCFILES.DLL. I am correcting my previous post, so that it does not make confusion. Here is where it is explained: http://www.vorck.com/2ksp4.html#8

@mouvda Please refrain from posting if you don't know about the matter. Hard links like you suggested are related to NTFS filesystems, NOT to ISO images. From http://www.interex.org/pubcontent/enterpri...01/ntgd1101.jsp : There are quite a bunch of similar utilities, see here: http://www.msfn.org/board/index.php?showtopic=46705 @Nepali There are some tools that make possible hard linking files inside ISO images. Read my post here: http://www.msfn.org/board/index.php?showtopic=49821 and related links. jaclaz

The list of files is INSIDE sfcfiles.dll. (NOT sfc.dll) thanks Toods. Read the links in my previous posts. jaclaz

From http://www.microsoft.com/resources/documen...t7/wrkappc.mspx Read the above reskit docs, + the others linked to in my posts here: http://www.msfn.org/board/index.php?showto...ndpost&p=280762 http://www.msfn.org/board/index.php?showto...ndpost&p=243188 jaclaz

Have a look at my post here (and related links): http://www.msfn.org/board/index.php?showtopic=50179 jaclaz

@dirtwarrior @Carmon Partition Magic does NOT repair damaged partitions. By using it on a drive with a possibly damaged partition you could make things MUCH worse. @Lost Soul HDD regenerator does NOT repair damaged partitions. By using it on a drive with a possibly damaged partition you could make things MUCH worse. @angel0104 Here you need a data recovery tool. The best FREEWARE one is TESTDISK: http://www.cgsecurity.org/index.html?testdisk.html Make sure you READ the docs before using it. Even if Testdisk fails in recovering the partition, the (included in the download) PHOTOREC might be able to recover most of the files in the partition. Read these too: http://www.msfn.org/board/index.php?showtopic=43132 http://www.msfn.org/board/index.php?showtopic=49303 jaclaz

Have a look at this: http://www.robvanderwoude.com/ Best reference on the web for .bat/.cmd files. jaclaz

http://www.ss64.com/nt/at.html I would go for SCHTASKS: http://www.ss64.com/nt/schtasks.html jaclaz

Read these: http://support.microsoft.com/default.aspx?...;309000&sd=tech http://www.microsoft.com/resources/documen...c_overview.mspx http://www.d-silence.com/feature.php?id=246 http://www.duxcw.com/digest/Howto/mb/abit/kx7-333/raid1.htm http://www.economicexpert.com/a/NTFS:junction:point.html jaclaz

NICE! jaclaz

The new one is quite strange, the old one is very possible. Did you try with some alternate tools, like makebootfat or manually like I hint in my tutorial? Also, did you try partitioning the key ? Is it possible that the problem is related to the known 2Gb FAT16 limit. Jaclaz

Nice idea. Only, where will the "filelist.txt" file be written to? Root (C:\) or C:\windows? jaclaz

@os2fan2 The c't article is this one: http://www.heise.de/ct/english/99/11/206/ BOTH these: http://www.lachiesadicristo.it/w98cd/page1.htm http://www.geocities.com/politalk/ are more recent and better explained. (there are more links in my previous posts) If you want to give a shot at it, please do keep us informed, here or better still, join this thread here: http://www.911cd.net/forums//index.php?showtopic=12326 The more info is kept together, the better results we will have. jaclaz

eidenk, don't want to be picky, but did you report it to an Admin ? (Press the button just below the post) The post was made yesterday at 4:06 AM (my time) Gape removed the link yesterday at 3:25 PM (my time), probably as soon as someone reported it or he saw it. Your post of today 5:01 PM (my time): seems to me a little out of date.... on a side note, if you think it why did you D/L it? (or your question on how to open those files was a purely theoretical one?) jaclaz

For win2K: pserv: http://p-nand-q.com/e/pserv.html jaclaz

There are quite a bunch of related thread/links both here and on the 911CD forum. Here are the most recent (and possibly useful) ones: http://www.msfn.org/board/index.php?showtopic=27296 http://www.msfn.org/board/index.php?showtopic=27354 I abandoned my (very primitive) project, mainly from lack of interest. I posted recently what remains of it here: http://www.911cd.net/forums//index.php?showtopic=12326 The most active project at the moment is the one from "winimize": http://winimize.com/ jaclaz

I posted some info here: http://www.911cd.net/forums//index.php?showtopic=12326 jaclaz

You could use this: http://home.eunet.no/~pnordahl/ntpasswd/bootdisk.html or this: http://www.d--b.webpark.pl/dreampackpl_en.htm DO READ instructions before using, you might render yur system inaccessible. jaclaz

It depends on the actual CONTENT of the AIO. There are utilities, namely CDIMAGE from Microsoft, cdrecord and mkisofs (FREEWARE) that can "hardlink" identical files, i.e. if a certain same file is present in the image in several different folders, those tools will substitute EVERY other occurence of the file but the first one with a link pointing to the first one. As the "link" takes just a few bytes, this can dramatically reduce the size of the ISO. See here: http://www.msfn.org/board/index.php?showtopic=39994 http://www.msfn.org/board/index.php?showtopic=30243 jaclaz

...hmmm, possibly the Iomega (ither drive or disk) fails to "detect" that the disk is in, thus not assigning a drive letter? RAWDISK and DSFOK should be able to connect to a device even if it is not "recognised" by windows. jaclaz

Looky here: http://www.msfn.org/board/index.php?showtopic=46964 (untested) B) jaclaz

The "feature" is called either WFP or SFC, it is (mostly) inside the SFC.DLL. Originally it was possible to enable/disable it changing a value in the Registry. Later it has been modified. Read here: http://www.vorck.com/remove-ie.html http://www.vorck.com/2ksp4.html#8 http://www.d--b.webpark.pl/reverse04_en.htm http://www.bitsum.com/aboutwfp.asp http://www.bitsum.com/index.asp#WfpAdmin jaclaz

Yep, I understand what you were asking, my remark was only aimed to avoid the kind of posts that nonetheless were made after it. I'll try to give you the best possible explanations I can (not necessarily complete): 1) Windows 98 SE requirements: http://www.computerhope.com/win98.htm 2) Windows XP requirements: http://www.microsoft.com/windowsxp/pro/upg...ng/sysreqs.mspx (the above are the MINIMUM requirements to barely boot an OS, don't even think to run ANY resource hungry application on that hardware) Processor speed: 486 DX2/66 vs. Pentium 233 the ratio is ROUGHLY 1:5 (486 has far less capabilities than a Pentium) Memory: 24Mb vs. 128 Mb the ratio is ROUGHLY 1:5 Occupied drive space: 300 Mb vs. 1500 Mb the ratio is ROUGHLY 1:5 So, if things were "linear", on the same minimal hardware, i.e. a Pentium I 233 Mhz with 128 Mbytes of memory, Windows XP should be ROUGHLY 5 times slower than Windows 98, in overall performance. Unfortunately (or fortunately) things are not "linear", and other components like hard disks, their controllers, motherboards, etc., have evolved. Windows XP (and I know I will be flamed for this) is actually FAR slower than 98 in some (very basics) tasks, i.e. booting up. On the other hand, it can do things that with Windows 98 you cannot even think of. DOS (and Windows 9x/ME) talk "directly" to hardware, whilst NT/2K/XP/2003 have an intermedate step, the "HAL" or Hardware Abstraction Layer in between. This effectively slows the connection between OS and hardware, but gives you some distinct advantages, like a FAR more stable system. Microsoft is perfectly aware of this and XP has been "tuned" as to give a better responsiveness to user's commands, thus "masking" partially the difference in speed. To this you must add that programs designed for XP have optimized code for newer processors, as they don't have to mantain "backwards" compatibility. (on the Linux side of the world, just compare the speed between a "general" distro and one like Gentoo optimized for i686 only) So the overall "impression" of speed (or responsiveness) is NOT 1:5 as expected. Nonetheless, expecially when direct or semi-direct access to hardware is needed, the difference in speed can be noticed. jaclaz

Ok, let's clarify things (in ten points): 1) Spinrite will ONLY run under DOS, being it either MS-DOS 6.22 or MS-DOS 7.1 (the one that comes with wndows 9x/ME), it will NOT run under ANY flavour of windows, be it 9x/ME or NT/2k/XP/2003 2) from the PHOTOREC documentation: So, if the files are NOT in the list above, PHOTOREC is of NO use.3) There are tens if not hundreds of Data Recovery programs out there that run from both DOS or NT/2k/XP, each of them has it's ups and downs, MOST are NOT freeware. 4) Sometimes a certain program will recover only a part of data, whilst another will recover another part. 5) There is no "best" program, as a rule of thumb, DOS based ones are better than NT/2K/XP based ones, due to the direct access DOS can provide to hardware (linux offers the same advantage), but a program run under NT/2K/XP could be more effective in some cases 6) Each and every program NEEDS to be used by a competent person to maximize results. 7) There are so many things that might have gone wrong on those disks that it is impossible to give specific advice, though I'll try to my best do so. 8) Theoretically it is POSSIBLE to use an USB ZIP drive under DOS, even if Iomega says it is not possible. There are reports on the net that this has been achieved, though there is no single way to do so, due to the incredible number of factors that might concur to success or fail (motherboard bus, BIOS, poorly implemented USB specs, Processor speed, etc.). NONE of the methods, EVEN if working are PROVED solutions safe enough to be used for such a delicate task as data recovery is. 9) As said before the MAIN thing in data recovery, EXPECIALLY if you are not an expert at it, is to NEVER work on original data, ALWAYS work on a copy (image) of the data. 10) If the data to be recovered is only "marginally" important, and you wish to make some experience, go ahead on a DIY job, being prepared to lose a LOT of time to study and learn how to do it; if data to be recovered is "important" you should evaluate the option to ask for professional help. Back to your problem what I would do (mind that this is my personal advice, no warranty implied): 1) Make TWO images of the disk, using the programs I linked to in my previous post (or use, if you have it, another imaging tool) 2) Mount the image as a Virtual drive under windows 2K/XP, by means of these: Driver: http://chitchat.at.infoseek.co.jp/vmware/vdk.html GUI (by yours truly): http://home.graffiti.net/jaclaz:graffiti.n...ts/VDM/vdm.html 3) Experiment freely with TESTDISK on it 4) If nothing comes out of it, try this FREEWARE: http://www.pcinspector.de/file_recovery/UK/welcome.htm 5) If nothing comes out of it, try with the evaluation versions of these (PAYWARE) apps (in order of my personal preference): File Scavenger: http://www.quetek.com/prod02.htm GetDataBack: http://www.runtime.org/ (as said above there are MANY more) There are even better (in my opinion) apps from x-ways: http://www.x-ways.net/ and DFSEE: http://www.dfsee.com/ but I would not use them if you are a beginner. Roadkil's DiskImage is a win32 GUI application, it "should" see your ZIP, maybe it does not. RAWDISK is a win32 CONSOLE application, you DO NOT start it by double clicking it, you must start it opening a console window, navigate to the directory where the exe is, the typing the name of the exe and hitting enter, it will give you basic help about the parameters you need to pass it. (btw, same applies to testdisk and photorec, though they can also start by double click, it is MUCH better to start them from console) Another FREEWARE GUI diskimaging solution is this one: editdisk/diskexplorer http://hp.vector.co.jp/authors/VA013937/ed...sk/index_e.html Another FREEWARE CONSOLE diskimaging solution is this one: dsfok: http://members.ozemail.com.au/~nulifetv/freezip/freeware/ (again these might work or might not) jaclaz