Delprat

That's a common mistake. I have CD-R, first generation (when CD burners were at least as costly as BD burners now) that proven to be more robust than HD bought within the same period (it were old HD... less than 500 MB). Noticeable thing is that both CD-R and HD were "low-cost" ones ! I presume that this year's HDs are more robust ; but optical discs are also. Who wants to burn slow ? I burn slow and leave comp away. Especially for something like a backup ! Again, you're making strange comparisons... neglicting that HD heads read/writes operations are far more complex than optical read/write ! Imagine that each time the HD needs to read a bit, it must re-write it after (including error correction bits) ! It involves MUCH more operations than for an optical disc, thus dramatically increasing the risk of error (this is meaning that checking if a HD has errors can create errors, whereas checking if a CD has errors won't). Indeed, no optical burn is ever perfect. Same thing for magnetic write. Indeed, optical drives have lots of error correction features. But no more than HD. You're talking a lot about disc manipulation : this has nothing to do with its reliability ! Can you imagine manipulating a magnetic plate by hand ? No ? So keep the disc in its box, and you avoid half of these problems. Use a drive that accept optical cartdriges, and you avoid half of the rest. Store you disc in an appropriate place, and you avoid half of the rest. What remains ? well... you'll need a lot of imagination to find, and even more malchance to do ! Here comes an enormous misconception ! Imagine that a car, a train, an elevator are faraday cages. But you can use your cell phone when you're into. Easy for a car or a train, a bit tricky for mosts elevators. Nearly no faraday cage is perfect (never "took electricity" when trying to open your car in a windy day ?). http://en.wikipedia.org/wiki/Faraday_cage (read the part about microwave oven, it's the more interesting in this case) Obviously, the HD box is robust. But if the disk stay (like backup disks usually do), errors can occur. (did you noticed that most backup software adds software error correction checks ?)

ow ! That grey menu look so oldish !

i didn't realized it was the same thing

Nice wall ! It fits well with Luna Element 5 Black VS... (well, every wall fits well with this VS ) my wall (first & last warn : don't click ! ) +

That's a good app if you know : - ver 3.0.116 (latest stable) is 20 monthes old - needs .NET 1.0 or 1.1 : slower than nero 5, comparable to nero 6 (but there's no flickering in the UI like in nLite) - relies on IMAPI (edit: seems like i'm wrong here - see Camarade_Tux posts) Once familiarized with, it's easier than nero : there isn't lots of "compilation types" to start with : you start with a Data CD which is by default multi-session unless you finalize it, if you have a non-finalized disc in drive, it will continue it automatically, etc... I found this design very intuitive ++

crahak > reading a so long post is a PITA. after doing it, buying a HD and backup 50GB on it is a good enjoyment (just listen to the seller's speech ). I didn't read every word, but you're writing at least one strange thing : "Magnetic storage is far more stable"... why ? 'coz you think there's no "error correction bits" ? if that were the case, HD will always send random bytes ! Plus, magnetic storage, as the name suggest, is subject to magnetic sensivity ; where optical storage is not (or far less). JoeMSFN > if one HD crashes, its backup has nearly no chance to crash at the same moment. Following widespread SETI rules to define the probability of the existence of an extraterrestrial intelligence, you are more likely to see an OVNI crashing on your car than having both the original HD and the backup HD crashing in a reduced time (a week or so) footnote > RAID is not meant for backups It's either a spray to eradicate bugs ; either a storage solution to eradicate bugs.

I've searched in hfslip code and it uses DDFs only to create cabinets. If you look in makecab.doc around your screenshot, you'll see example showing how to compress like you want : in each one there's at least one file not compressed : .Set Compress=OFF .Set Cabinet=OFF setup.exe setup.inf .Set Compress=ON .Set Cabinet=OFF .Set CompressionType=LZX .Set CompressionMemory=21 .Set SourceDir=d:\temp\WORK .Set DiskDirectoryTemplate=D:\VIP accwiz.exe ahui.exe appwiz.cpl ... Also, hfslip uses DiskDirectory1 instead of DiskDirectoryTemplate, and no SourceDir but a relative path on each file. ++

Whoops... Before or after don't changes anything. I never saw this question (i don't have non-MS AB). What you label "far reach" is based on my expericence. I had a backup of my WAB file, and after restoration i saw it not working (my file was renamed to .bak, and a new was created). I don't remember if it was a OE4 or OE5 file, but i needed hotfixes to read the WAB file... (and you ignored my comparison with GRPConv... again, there's no .GRP file on a fresh new install of windows, but GRPConv is ran by windows setup... guess this tool, like WabMig i suppose, does more than what it claims) ++

Why not making a little step-by-step how-to ? It will be only a few KB, maybe a few MB if you add images... but it will be very little compared to a hundred of MB ISO ++

I do not recommend to use things like "SafeXP"... Windows security takes far more than clicking on a few tenth checkboxes. And windows provides ALL the needed tools to configure it... just look at the included "help center" (but not in XP Home) ++

Did you checked the "description" field in the properties of wabmig.exe ? Mine shows "Microsoft ® Address Book Import Tool". It seems OK to see this one running after a SP/hotfix install... Just imagine this SP/Hotfix updates the WAB (Windows Adress Book) binaries... WabMig.exe is then ran to MIGrate the old address books (files with .wab extension) to a somewhat updated form... or to check if there's no error/flaw in them... That's like the GRPConv.exe utility ran during windows setup, where there is no GRP file... ++ PS: w2ksp51 is not made by MS ; it's an *unofficial* service pack made by Gurgulmeyer

Virtual drive emulation + Daemon tools or Alcohol makes me thinking about cracking games protections. It seems a good idea (it will reduce piracy), but they are ignoring people who buy their games, but don't want to have the disc in the drive (there's at least two very good reasons to do that : 1. optical drives makes noise ; 2. having a disc in makes the drive used for nothing, reducing its life). Windows is a "gamer" system, and we can take for sure that a windows that do not allow gamers to play like they want will not reach any public. It seems like MS decided that XBox is enough to play... ++

What's the problem then ? this is an error on your side : either you didn't named it correctly (that's Winnt.sif), either it's really a html file that will be ignored by windows setup. AFAIK These files are ignored by HFSLIP and can be removed. :woot: You have 4 useless "Windows2000" updates (i didn't checked each kb #) and 2 "WindowsMedia9". All seems fine for IE6, OE6, MDAC, rootsupd, scripten. You should check you list and compare with this topic ; or TomCat's site. ++

Right, it's a wrong syntax To get what you were thinking about, replace ",4" by ",,6" (two comas, 6 instead of 4 to make it silent) Another detail PROBLEMCHYLD, you posted a batch a few posts ago with multiple COPY then REGSVR /U then REGSVR /I on the same fileset : you should change the order to be REGSVR /U then COPY then REGSVR /I. It becomes : regsvr32 /u /s %windir%\System\browseui.dll regsvr32 /u /s %windir%\System\browselc.dll regsvr32 /u /s %windir%\System\CTL3D32S.DLL regsvr32 /u /s %windir%\System\CTL3D.DLL regsvr32 /u /s %windir%\System\CTL3DV2.DLL regsvr32 /u /s %windir%\System\gdiplus.dll regsvr32 /u /s %windir%\System\HLP95EN.DLL regsvr32 /u /s %windir%\System\HOTPLUG.DLL regsvr32 /u /s %windir%\System\IOSCLASS.DLL regsvr32 /u /s %windir%\System\LAYOUT.DLL regsvr32 /u /s %windir%\System\MARSCORE.DLL regsvr32 /u /s %windir%\System\MMCI.DLL regsvr32 /u /s %windir%\System\MYDOCS.DLL regsvr32 /u /s %windir%\System\Psapi.Dll regsvr32 /u /s %windir%\System\SETUP4.DLL regsvr32 /u /s %windir%\System\SETUPX.DLL regsvr32 /u /s %windir%\System\SHDOCLC.DLL regsvr32 /u /s %windir%\System\SHELL32.DLL regsvr32 /u /s %windir%\System\STI_CI.DLL regsvr32 /u /s %windir%\System\SYNCUI.DLL regsvr32 /u /s %windir%\System\unicows.dll copy browseui.dll %windir%\System copy browselc.dll %windir%\System copy CTL3D32S.DLL %windir%\System copy CTL3D.DLL %windir%\System copy CTL3DV2.DLL %windir%\System copy gdiplus.dll %windir%\System copy HLP95EN.DLL %windir%\System copy HOTPLUG.DLL %windir%\System copy IOSCLASS.DLL %windir%\System copy LAYOUT.DLL %windir%\System copy MARSCORE.DLL %windir%\System copy MMCI.DLL %windir%\System copy MYDOCS.DLL %windir%\System copy Psapi.Dll %windir%\System copy SETUP4.DLL %windir%\System copy SETUPX.DLL %windir%\System copy SHDOCLC.DLL %windir%\System copy SHELL32.DLL %windir%\System copy STI_CI.DLL %windir%\System copy SYNCUI.DLL %windir%\System copy unicows.pdf %windir%\System copy unicows.dll %windir%\System regsvr32 /i /s %windir%\System\browseui.dll regsvr32 /i /s %windir%\System\browselc.dll regsvr32 /i /s %windir%\System\CTL3D32S.DLL regsvr32 /i /s %windir%\System\CTL3D.DLL regsvr32 /i /s %windir%\System\CTL3DV2.DLL regsvr32 /i /s %windir%\System\gdiplus.dll regsvr32 /i /s %windir%\System\HLP95EN.DLL regsvr32 /i /s %windir%\System\HOTPLUG.DLL regsvr32 /i /s %windir%\System\IOSCLASS.DLL regsvr32 /i /s %windir%\System\LAYOUT.DLL regsvr32 /i /s %windir%\System\MARSCORE.DLL regsvr32 /i /s %windir%\System\MMCI.DLL regsvr32 /i /s %windir%\System\MYDOCS.DLL regsvr32 /i /s %windir%\System\Psapi.Dll regsvr32 /i /s %windir%\System\SETUP4.DLL regsvr32 /i /s %windir%\System\SETUPX.DLL regsvr32 /i /s %windir%\System\SHDOCLC.DLL regsvr32 /i /s %windir%\System\SHELL32.DLL regsvr32 /i /s %windir%\System\STI_CI.DLL regsvr32 /i /s %windir%\System\SYNCUI.DLL regsvr32 /i /s %windir%\System\unicows.dll And i removed the regsvr lines on unicows.pdf... ++

I saw your other thread. If i were you (sic), i would not use a DDF 'coz it will create a RPT and a LOG. (plus, it's not working ) Nooooo ? Again, take a look at XPize. There's some mysterious thing called "autoreloader" that update hotfixed files unattended on reboot I learnt that ICLs are not PE but NE (older). Okay, now i know (singing) something that i didn't know five minutes before. Thank you very much. But that's not related to what i said... the mess is the PE (or NE) format itself. Well, it works very well for the end-user, but it's original purpose was to make portable executables... and look, ten years after, you need to install whole operating system and to bother helpful people on forums to execute a single PE ++

Buy a harddisk... I don't think you'll find a smaller ("physically" speaking) way to backup 50GB ++

okay, sorry for the late. First, some comments : 1/ the "bootdisk" folder and files allow you to create a set of floppies to start the install, for old computers not able to boot from CD. You can delete the folder if you need some space on your CD. 2/ the bootsector is not a "classical" file on your CD : windows can't let you see it. You succeed with BBIE manually, i don't understand why HFSLIP fails ???? 3/ you don't need to create an ISO file if you plan to burn a CD. With Nero (i never used roxio), drag & drop the contents of the SOURCESS folder in a new compilation, then set the boot options. Look at this page (just skip the second screenshot 'coz you already have the bootsector file) FYI, ISO files are only "raw" copies of CD/DVD (nothing to do with the contents of the CD) Now, your last question : Can you post here (as an attachement, or in [ CODEBOX ] [ /CODEBOX ] tags) your HFSLIP.LOG file ? And did you copied those missing files/folders in the SOURCE folder ? (the files you're talking about are not required to initiate the install if you boot from the CD ; nor the "other folders" which contains additional components) ++

This thing is far more than a UBCD with a gui !!! Here's a list of some possible uses ++

To make the ISO, you need the bootsector extracted from the original windows disc. HFSLIP does it automagically (with BBIE.EXE) only if the CD is in one of your optical drives. I can't see anything else wrong in what you've tried, so there's two solutions : you have the bootsector file from a WinNT 5 disc (win2000, winxp, win2003) : name it "BOOT.BIN" and place it in HFTOOLS you don't, but you have one WinNT 5 disc (hopefully this Win 2K you're playing with) : place the disc in the drive Then, you can try again to make the ISO with HFSLIP : run the script, and when you're asked to type "i have read the instruction", type "MAKEISO" instead. As you stated you got Nero 6, you can make this iso with it (or burn a CD), but Nero will also ask you for the bootsector. Options to define in Nero are : No Emulation / load @ 07C0 / nb of sectors 4. And a boot message, if you want. ++

[DELETED] Did you benchmarked that ? I'm pretty sure that the executable remains in the disk cache between runs ?

MakeCab ?... or ModifyPE ? Take a little look at Xpize, you'll see the solution about hotfixes : slipstream the ressources in the files in i386, and keep them separetely with a "updater" script. (and you'll understand why the PE format, mixing binary code and ressources is a.... well, in fact there's no word to describe this mess) If there's a better solution, i hope you'll find it : this one takes lots of space (not so much if compressed, but even some nuclear plants don't have duplicated security systems... and most of them don't explode with a Blue Storm Of Death ) ++

If you don't want to use CD-R nor CD-RW, simply don't make an ISO. You'll need to keep the "installation manuelle et mise à jour" component. Then, when nlite has finished, open a command prompt, go to the source folder (ex: X:\CDXP\i386) and type : winnt32 /makelocalsource /noreboot On the next reboot, you'll get a new entry in the boot menu : "Installation de windows"... (you can ommit the "/noreboot" swith : it will reboot & run the install immediately) ++

This method rocks. AFAIK, Norton Ghost is able to compress imaged partition, to split it on multiple media (ex. CDs), and to explore it. And it works with partitions, not files, so you don't have to worry about the MBR (maybe the "active" bit). btw, why are you willing to re-invent the wheel ??? To get back on topic, there's tools to save/restore MBRs. But i'm not sure that "compression utilities" can save ALL informations of a NTFS partition : there's security attributes, alternate data streams, hard links, ... I believe that ZIP doesn't support ACLs. RAR have it, but i don't know about ADS or hard links. ++

Of course it takes time, but it's no more than copy/pasting files with explorer and copy/pasting INF files contents with notepad. Don't say it's hard... The easier way to go is to take an update pack (RyanVM one or another), and look into it (enties.ini & RVMUpPk.inf), following explanations on RyanVM's forum. When basic structure is understood, simply try to add one hotfix. Then another. Then you'll be smart enough to start a new update pack. But these "UpdatePacks" will never be "service pack" (even with a "custom" prefix) : microsoft's SP contains a powerful engine (update.exe) able both to install on existing systems (with an optional backup) and to slipstream to an install source. Plus it checks if you are applying the good SP on the good OS. All this power is absent in RVMIntegrator (and in nLite, which is even less powerful)... Thus, take care... you should end up with an alert before logon saying you can't use your OS ++

You're lucky to be australian... Here that's nearly summer, and overclocking is a winter sport Athlon 2600+ are likely to go up to 3200+, with a good mainboard, and a very good cooling. ++