Martin H

Hi g-force Sorry if I wasen't clear enough, but I wasen't reffering to the issue in that thread i.e. if nLite's license approves using VL media together with nLite, but I was rather saying that the term "Corporate edition"(or VLK edition) and "Student edition" is mislabeled terms comming from the warez-scene, and hence, asking for help on such releases, in my book atleast, is refering to pirated material... CU, Martin.

Please don't talk about pirated material here... "Corporate" and "VLK" edition is what the warez-scene(and ignorants!) call Volume License(VL) media with a Volume License Key(VLK), and "student edition" is again pirated and mislabeled Volume License media with a certain VLK. Actual and legal "student editions" is MSDN-AA media with MSDN-AA Product-Keys, and that isnt Volume License media!

For ppl that want's direct-integration, and want's exactly the components/changes that an update-pack includes, then i think that it's a very nice option to have, since doing it yourself, when another pack author allready does it too, is pretty much reinventing the wheel IMHO. Of course if one cannot find such a pack that suits one perfectly, then it's another story... I myself use xable´s XP SP3 pack, since it only includes high-priority updates with binaries from the GDR branch, and no tweaks, changes or anything else... I fully understand that ppl wants to do their own thing, but also keep in mind that for most ppl, then what they're doing is not the same as what the update-pack authors are doing i.e. directly integrating updates... Also downloading from msft and integrating the updates with nLite/hfslip/integrate switch, is also not doing it "yourself", as that's nLite/hfslip/msft doing all the "hard" work for you... Btw, when integrating msft downloaded XP updates through nLite or hfslip, then the QFE branch is used, whereas if installing them manually on a freshly installed system, then the GDR branch would have been used instead...

No offence, but that's a personal-preference and not related to the issue, though (I use the built-in admin as primary account too...) @ericl23 Just set the computer-name as i said and you'll be fine...

If you're refering to "during installation" and not "logon", then it's because you haven't defined a computer-name; you can e.g. use '*', which sets a random generated name(which is the owner first-name with a random number after)

which I had already mentioned before:[] You mentioned it was a hacked msft codec, and so for added discriptiveness to the OP, i added which msft codec it was hacked from, and what the hack consisted of...

@winforever DivX :-) v3.11a(msft's MPEG-4v3 codec hacked to allow AVI and other containers instead of just msft's ASF container) is from 2001 and can e.g. be downloaded here: http://www.divx-digest.com/software/divxcodec.html. To get the best results out of this anchient codec, then i would recommend using Nandub(offers 2-pass Smart Bitrate Control for DivX :-) v3.11a, which isn't possible from it's VFW interface). Nandub is also included in Gordian Knot.

The biggest hogs are services and other components with dlls in memory at run-time... Anyway, here's a quote from nuhi about this: Emphasis is mine. Source: http://www.msfn.org/board/index.php?s=&amp...st&p=626226 I can't say for the newest boxes(as i don't own one), but on the mid-range/old systems, i would say that there defenetelly is something to archive with reducing the OS performance-wise... As for updates, i have always just found it to be easier and much less of a hassle to just download and archive/use all the Windows core updates... However, i don't have that issue anymore, as i now prefer to just use an update-pack instead(since nLite uses the QFE branch for direct integration, whereas i want the GDR branch, and also nLite can't directly integrate all the updates and for those it can't, then it instead uses the updates own bloated '/integrate' switch method)...

There's no reason to reinvent the wheel and do it manually IMHO, but nonetheless, run the following command-line from your XPCD folder to retrieve and expand all the infs from I386 into a _infs folder: for /f %g in ('dir /b /a-d /on I386\*.in_') do expand -r I386\%g _infs Then for starters open sysoc.inf and syssetup.inf and comment out unwanted infs or blank them, and comment out there referenced files in txtsetup.sif and dosnet.inf(only needed if doing network/dos installs), and you need a patched syssetup.dll to remove the signing... for doing further reduction, then go though the rest of the infs... I just use nLite though

It shouldn't be set if wanting auto-logon always I couldn't really tell exactly from the OPs post if that's what he wanted or not...

nLite supports app-addons, so you can either make them yourself, or download pre-made ones. They are then inserted through nLite's 'Hotfixes/Addons' section. Then as HØLLØW also stated, you can use nLite's RunOnce tab, to insert commands for installing your apps at first logon. For that you then need to add the apps to a folder in your install-source, either before you run nLite or just before you make the ISO. You can e.g. make a folder named 'Software', in the root of your install-source, and then place all your apps in there(in subfolders maybe), and then either insert commands in nLite's RunOnce tab for all the apps to install silently(the path to that folder is then: %source%Software), or you could just add a batchfile in that folder which installs all the apps, and then call it from nLite's RunOnce tab, like e.g. %source%Software\install.cmd. That is then the same as adding a batchfile to winnt.sif's 'GuiRunOnce' section, but the advantage with doing it through nLite, is that nLite provides a %source% variable for you, which is dificult to do from winnt.sif's 'GuiRunOnce' section... Other than that, then check out the MSFN Unattended guide, for methods to install apps manually without nLite...

Then you used the wrong command syntax; it dosen't matter where the file is placed for registering it... If the file to register/unregister is in a location defined in your %path% environment variable(google it, if you don't know what that means), then you don't need to add a path to the regsvr32 command(or any others for that matter). By default, then '%windir%\system' and '%windir%\system32' is defined in the %path% environment variable...

nLite has an addon section, where people can e.g. make or use others ppl's app-addons, and the people that make those app-addons, ussually makes them so that the apps install from svcpack.inf at T-13, and that's not nLites fault... Many ppl prefer to install apps at T-13, but nonetheless, if you don't(like me), then nLite also has a RunOnce tab, where you can add commands to be run at first logon to e.g. install your apps, but you need to add the apps to your install source yourself(before you start nLite, or just before you make the ISO). If you always install to the same box, then you could use nLite's RunOnce tab to call an INF or batchfile from a second partition on your HDD, which then installs all your apps from there. That's what i do...

If wanted, then for disabling the installation of unwanted components, then for starters, exchange syssetup.dll with a hacked one(unsigned) and then expand syssetup.inf and sysoc.inf from the I386 folder, and comment out what you don't want(or clean out the referenced INFs) + comment out those INFs referenced files from textsetup.sif(and layout.inf if first removing the signing...) and if you're installing from network/dos also dosnet.inf... You can look up more details on the net...

No reason to do that IMHO... It dosen't hurt anything, and they're there if you need them later on...

As has been allready stated, then nLite cannot do this... HFSLIP can however, and as HFSLIP is both open-source and written in plain cmd-syntax, then you can study how it's done and do it manually(or use HFSLIP of course)... I used to do this, but then instead changed to using the "drivers from CD" method, which i've now ammended to install from a second HDD partition instead of the CD now(as that's even faster). The downside to doing what you wan't, is that it can only be done by changing each install-INF's SourceDisksFiles section to look for the source files into driver.cab, instead of the current folder, and this means that you're breaking driver signing by doing that!(as the INF's checksum changes, and hence doesen't match the checksum stored in the catalog file).

Huh! Of course you can still get trojans and other malware even though IE isn't installed! You're protected against IE exploits(and OE/JScript exploits etc.), but not against all possible windows exploits, or of course your own stupidity either i.e. downloading and running unknown and suspecious files... Windows isn't bullet-proof with fdv's fileset, but is just more secure than by default!

I don't think so... There is allready a solution for using it in this thread, and i don't see the reason for bloating hfslip further by adding support for yet another(and third!) image making utility... Just my oppenion of course

I image and restore my system-partition with the DOS version of Norton Ghost 2003 from an unattended boot-floppy... If interrested, then here's the instructions for making such an unattended boot-floppy or boot-cd: Make a Norton Ghost boot-floppy from the GUI of Norton Ghost 2003(latest build is build 793), and uninstall Norton Ghost 2003 afterwards(i simply restore my system-partition back instead). Use an app like WinImage, to extract the boot-floppy into a boot image and open the image afterwards. The boot image is based on PC-DOS, so add an empty file named '_BOOT_HD.NOZ' to it, which will give you a "Press any key to boot from CD or DVD" option during startup. I also move ghost.exe into the root of the image instead of having it in the 'ghost' folder, and then i delete the 'ghost' folder afterwards. Now make a file named autoexec.bat with the following, and add it to the image(and overwrite the old one): @echo off cls echo. echo 1. Backup echo 2. Restore echo. choice /c:12 /n cls echo. echo Loading... if errorlevel 2 ghost.exe -clone,mode=pload,src=1:2\Backup\image.gho:1,dst=1:1 -sure -rb ghost.exe -clone,mode=pdump,src=1:1,dst=1:2\Backup\image.gho -sure -rb Then write the image to a floppy with e.g. WinImage, or to a CD-R with e.g. ImgBurn under 'Build mode > Advanced > Bootable disc', and when you then boot from the boot-floppy or boot-CD, then press any key when the "press any key to boot from CD or DVD" message appears, and then press 1 to unattended image your system-partition to D:\Backup\IMAGE.GHO(it's overwritten if present) and auto-reboot, or press 2 to unattended restore D:\Backup\IMAGE.GHO onto your system-partition and auto-reboot. Change the image path to your own liking...

Please see this thread: http://www.msfn.org/board/index.php?showtopic=133709

Hmm, i just looked at the code quickly, and i don't understand why you have boot.bin in SOURCESS, since that shouldn't be possible: HFTOOLS\mkisofs.exe %MKISSW% -b %BBIN% -o "%TEMPISO%" -V "%ISOTITLE%" %SOURCE% DEL/Q/F SOURCESS\BOOT.BIN

They mostly use the same switches, but cdimage.exe has alot more of them, and hence, the default switches hfslip uses will not work, as -j1 and -m isn't valid switches in oscdimg.exe, or atleast not in the version from this posts screenshoot: http://www.msfn.org/board/index.php?s=&amp...st&p=118148

First, hfslip should be run on a fresh/clean source every time. Second, please use the latest hfslip beta, which can be obtained from the stickied "test releases" thread, as there's been alot of changes/fixes... Third, if you are having trouble with fdv's latest fileset(set-9), and still wants to give it a shoot, then PM me, and i'll send you fdv's previous fileset(set-8j), which i currently use on two boxes without any problems(it's very stable and has no issues), untill fdv has ironed everything out in set-9... If you're not into fdv's fileset anymore, but still want's a leaner install, then i would highly recommend TommyP's(and Oleg II's) hfcleanup reducers, which also makes for a really nice and lean Win2k install, where you also can opt to leave in the IE core, or even the full IE. If not reducing IE at all with hfcleanup, then either delete Service_ErrorReporting.rem and Service_ErrorReporting.inf, or open Service_ErrorReporting.rem in notepad and make an underscore infront of DWIL1033.DL i.e. _DWIL1033.DL, as else there will come a file-copy error about that file not being present at about T-13(from hfslipwu.inf). Note, there isn't even an error reporting service in Win2k, and it's related to XP(and maybe 2k3?)

I did a quick google search, and boot.catalog is related to mkisofs, and so you have the option of using cdimage.exe instead, and with that, then hfslip dosen't add anything extra into the sourcess folder for making an iso(however, mkisofs just writes the file to the first sector of the iso, which becomes the boot-block when burned to disc, and dosen't add it into the main root of the iso, just like cdimage.exe)... (Personally, then i feel that there's no reason to use a non-win32-native tool compiled with mingw or cygwin, when theres a perfectly fine native win32 tool available in cdimage.exe; but that's just me, and not that there's anything wrong with Jörg Schilling's cdrecord suite of tools at all...)

@TommyP: Thanks my friend Nitpick: The removed IE5 update: KB969897, has a wrong KB article listed/linked: KB969879... CU, Martin.