Kurt_Aust

John, as I don't get the problem, I can't really help you. As I see it the only way forward is to follow the guide exactly as written, see if you still get the problem and then start diverging until you hit the error. On another note here is the code for silent install of VMware server: %Source%AddOns\VMware-server-installer-1.0.8-126538.exe /a /s /v"/qb TARGETDIR=%Temp%\VMwareServer" msiexec /I "%Temp%\VMwareServer\VMware Server Standalone.msi" ALLUSERS=1 ADDLOCAL=ALL SERIALNUMBER=XXXXX-XXXXX-XXXXX-XXXXX /Passive /NoRestart rem msiexec /I "%Temp%\VMwareServer\VMware Management Interface.msi" ADDLOCAL=ALL /Passive /NoRestart msiexec /I "%Temp%\VMwareServer\VMware VmCOM Scripting API.msi" ADDLOCAL=ALL /Passive /NoRestart msiexec /I "%Temp%\VMwareServer\VMware VmPerl Scripting API.msi" ADDLOCAL=ALL /Passive /NoRestart RmDir /S /Q %Temp%\VMwareServer Obviously you will have to supply your own serial number. The VMware Management Interface is remarked out as it is not supported on XP x64 (you'll get an error). Do NOT install VMware Server within VMware Server (it will go boom once you connect the ethernet cable). As I don't have a spare real machine for testing at the moment, if anyone does use this code please post the results.

MD5 is a match. Integrating IE7 required special modifications being made within the nLite process, similarly the required modifications changed between each version of the IE8 betas. I can't see that it will hurt to allow IE8 to be out in the wild for a couple of months before adding it to the guide as that should lead to the discovery of any missed bugs and/or compatibility hiccups.

I'd suggest trying again without removing any components, KB967715 is the autorun update which affects (amongst other things) USB devices and network shares and there are some items in the removed list that (admittedly at a stretch) could affect it. I will move the guide onto IE8 when IE8 direct integration is officially supported by nLite.

Weird, KB967715 works fine for me. As for how I determine needed hotfixes, it's depressingly basic. I've created a fully unattended .iso with just IE7 & WMP11 integrated, I simply install it in VMware server and point it at Windows Update. I then check the results against this month's security releases .iso.

If you (for security reasons?) prefer not to have an account called "Administrator" then I think the easiest way would be to deactivate the account in nLite. Obviously you will need at least one Administrator class account, so set the install to auto-login to that account twice and modify the SchTasks command in Run1_W2Ksp5.bat to match the new account name and password. This is just a suggestion, I haven't tested the described scenario

As stated above "use the DriverPacks BASE program to integrate them (do not extract the .7z archives) after nLite has finished its processing, but before creating the .iso". It cannot be done before nLite makes its modifications. You'll have to give us a link to the HP/Compaq files in question.

March updates Deletions: Hotfix\230-Windows2000-KB935840-x86-ENU.EXE Hotfix\590-Windows2000-KB954211-x86-ENU.EXE Hotfix\670-msxml4-KB954430-enu.exe Additions: Hotfix\760-Windows2000-KB960225-x86-ENU.EXE [561,192] Hotfix\770-Windows2000-KB958690-x86-ENU.EXE [1,312,296] Hotfix\780-Windows2000-KB967715-x86-ENU.EXE [1,243,704] RunOnce\msxml.msi [2,434,048] Optional, Microsoft XML Core Services 4.0 Service Pack 3

March updates Deletions: Hotfix\130-WindowsServer2003.WindowsXP-KB935840-x64-ENU.exe Hotfix\520-WindowsServer2003.WindowsXP-KB938464-x64-ENU.exe Hotfix\530-WindowsServer2003.WindowsXP-KB954211-x64-ENU.exe Hotfix\610-msxml4-KB954430-enu.exe Additions: @ . . . Hotfix\720-WindowsServer2003.WindowsXP-KB960225-x64-ENU.exe [1,034,640] # ▼ Hotfix\730-WindowsServer2003.WindowsXP-KB958690-x64-ENU.exe [8,420,744] # ▼ Hotfix\740-WindowsServer2003.WindowsXP-KB967715-x64-ENU.exe [24,187,280] @ ▼ WMP11\WindowsMedia11-KB959772-x64-ENU.exe [5,936,008] @ ▼ RunOnce\WindowsServer2003.WindowsXP-KB938464-v2-x64-ENU.exe [4,386,696] @ . . . RunOnce\msxml.msi [2,434,048] Microsoft XML Core Services 4.0 SP3 @ . . . RunOnce\WindowsServer2003.WindowsXP-KB961118-x64-ENU.exe [872,312] (only if installing .Net 3.5 sp1) Added application install support for: Vdownloader (as it no longer installs eBay shortcuts) Comodo Firewall, in the absence of useful silent install switches the following options are provided: A) Use the older stable firewall only v3.0.25.378, it will default to safe mode on both firewall and defence+ B} Use the current version with default settings, firewall, defence+ and anti-virus will be installed. C) Use the current version with a very basic, push the buttons, AutoIt script for firewall only, no AV, D+, ThreatCast or toolbars. and more info on Sun VirtualBox: In order to have a usable VirtualBox when you first logon to each account you should go [start >> Control Panel >> System >> Advanced >> Performance Settings] and deselect the three options under Visual Effects that begin with "Fade ...".

You have extracted the DriverPacks and integrated them with nLite, this is incorrect. Rather you must use the DriverPacks BASE program to integrate them (do not extract the .7z archives) after nLite has finished its processing, but before creating the .iso (obviously).

February updates: Deletion Hotfix\620-Windows2000-KB956391-x86-ENU.EXE Addition Hotfix\750-Windows2000-KB960715-x86-ENU.EXE [493,608] Also added a screenshot archive to my eSnips page.

Probably better off using Strel's continuation of Tomcat's script: http://www.msfn.org/board/index.php?showtopic=127790 The topic linked to in Gkar's post hasn't been updated in quite some time.

February updates Deletions: Hotfix\670-IE7-WindowsServer2003.WindowsXP-KB958215-x64-ENU.exe Hotfix\680-IE7-WindowsServer2003.WindowsXP-KB960714-x64-ENU.exe RunOnce\WindowsServer2003.WindowsXP-KB956391-x64-ENU.exe Additions: @ . . . Hotfix\700-IMAPI_SRV2003_x64.exe [2,370,504] Optional, Blu-Ray image mastering support # ▼ Hotfix\710-IE7-WindowsServer2003.WindowsXP-KB961260-x64-ENU.exe [37,213,048] @ . . . RunOnce\WindowsServer2003.WindowsXP-KB960715-x64-ENU.exe [673,144] Meowing: I prefer giving the user feedback as to how the installation is progressing, hence you will see that I use /Passive rather than /Quiet and /Silent rather than /VerySilent. It saves them from wondering if the process has hung. Anthonyaudi: As Johnhc noted you can add the MSRT to Run1_XP-64.bat, I don't include it for 2 reasons: 1. There's no point checking your system until you've installed all your applications & 2. Not including it allows you to check that Windows Update is working correctly. EDIT: I've uploaded Radix's fixed script for Deamon Tools lite v4303 to the eSnips page, just place it at \AddOns without renaming if you want to use the latest version.

Meowing: My best guess is some sort of sequencing problem, maybe related to the reason why using ProgramAddons is problematic (failure to register file associations being the most obvious symptom). The replies I got when querying that strange behaviour suggested that it is due to the registry not being fully formed prior to the final reboot. \$OEM$\cmdlines.txt [Commands] "rundll32 advpack.dll,LaunchINFSection nLite.inf,U" \AMD64\NLITE.CM_ TimeOut /T 40 for /f "tokens=3" %%i IN ('reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v "SourcePath" ^| findstr "REG_SZ"') do set SOURCE=%%i CMD /R %Source%Run1_XP-64.bat "%windir%\daemon\dt410x64.exe" EXIT The "%windir%\daemon\dt410x64.exe" bit is from JohnDoe74's 2-part Daemon Tools installer, but I have to put it before Spybot: S&D in the batch file.

If people would prefer it faster, they can use sysinternals' Sync for that. Like so:%WINDIR%\sync (and then of course have it as \$OEM$\$$\sync.exe or something..) Make sure you register it, or it asks for eula acceptance. [HKEY_CURRENT_USER\Software\Sysinternals\Sync] "EulaAccepted"=dword:00000001 You appear to have misunderstood the TimeOut's purpose, it's not there to flush the cache. It's there to allow time for system services and other applications to fully initialise before proceeding with the next round of installations.

Well I'm back and had a great (if somewhat cold) time. While this is not the place to comment on my travels I just had to share one thing. This photo was taken on a 10 hour flight from Beijing to Sydney, the user in question was told several times to fasten his seat belt and stow his laptop for takeoff. While still climbing he pulled it out again and started gaming then settled down for a movie, when dinner came around most people would take a break, not this guy: One has to wonder if he paid for it himself.

Hello John, you're right. This problem is resolved. Do you have some ideas for: KB960714 KB958215 KB956391 ?? First two are hotfixes for IE7, the last one is Killbit hotfix. POPRZEDNIA_SESJA.INI Best regards, Looking at your preset file, you are using the IE6 rather than the IE7 specific versions of KB960714 & KB958215. Do a search under the hotfix number and use the version with a similar name to: IE7-WindowsXP-KB958215-x86-PLK.exe IE7-WindowsXP-KB960714-x86-PLK.exe

.Net 2.0 SP2 standalone installer has been released, so you can now install .Net 2.0 SP2 rather than .Net 2.0 SP1. From Microsoft you want (▼ is a direct link to the executable): ▼ .Net framework 2.0 service pack 2, save it to \RunOnce. MD5: C64FD1F972822ED84378C7058FEA0744 SHA-1: 22D776D4D204863105A5DB99E8B8888BE23C61A7 ▼ NDP20SP2-KB958481-x86.exe (.Net 2.0 SP2 compatibility update) save it to \RunOnce MD5: CCD59228523CC8720452625FE04EE14A SHA-1: 04FCDE4B28DD4F6DB7548831D35D1C6BF38E1335 You will no longer need: RunOnce\NetFx20SP1_x86.exe RunOnce\NDP20SP1-KB947748-x86.exe Hopefully by patch Tuesday, Strel will have updated the "Build your own .Net" script and I'll be able to offer a .Net 2.0 SP2 AddOn that should save about 8MB on your install media. Lastly, a housekeeping note, I'm on vacation from 24 Jan to 2 Feb, so the tracker will be down.

.Net framework 2.0 SP2 standalone has been released, main post & batch file updated to support. If you only want/need .Net 2.0 SP2 & update % ▼ NetFx20SP2_x64.exe [48,524,296] MD5: AD55AD64B69FED73807429859291DB8C SHA-1: A7CC6C6E5A4AD9CDF3DF16A7D277EB09FEC429B7 % ▼ NDP20SP2-KB958481-x64.exe [19,282,272] MD5: 37CD8D927566FCABF4DFFCBBE63D16EF SHA-1: 1392380EF7BAABD531F35EE5799C255A03B0DCBE Advance notice, I will be out of contact and the tracker will be down from 24 Jan to 2 Feb inclusive, I'm trading in the 38C of Sydney for the -15C of Harbin.

The machine name is generated randomly if you did not specify one. However, if you specified a company name, the computer name will take the form: CompanyName-RandomString

Uploaded an archive of the screenshots to my eSnips page.

\AMD64\Update exists in the extracted SP2, you can't extract it into itself. It has } rather than ), because if I use ) I get B). It doesn't need and should NOT be done in the source folder. After SP2 is integrated you no longer need the extracted files. 451MB extracted vs 350MB for original executable.

I figured I'd have to rewrite that section for greater clarity, so here goes: Special note for users of 32-bit operating systems. You cannot slipstream Service Pack 2 as is (due to it being a 64-bit executable), instead you must do the following: A) First check that the files in your nLite working directory do NOT have their Read-Only attribute set, if so clear it. B} Extract WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe with 7-zip or WinRAR. C) Download from my eSnips page the Update.7z archive (contains files from the 32-bit version of Service Pack 2 for Windows Server 2003). D) Extract Update.7z into the \AMD64\Update folder of the extracted x64 Service Pack 2, replacing the existing files. E) nLite will warn that you cannot integrate 64-bit service packs from within a 32-bit enviroment, proceed anyway (just say no). F) Finally when integrating the Service Pack you need to navigate to the AMD64\Update folder and select the Update.exe file. And of course over at PlanetAMD64, there are pictures, the error & select update, as one can see the screenshots are very different. I tested the build method on an early Pentium4 (1.5 GHz, PC133 RAM) running Windows 2000.

The only thing that doesn't work under a 32-bit environment is slipstreaming service pack 2, hence: Special note for users of 32-bit operating systems: You cannot slipstream Service Pack 2 as is due to it being a 64-bit executable, instead you must extract it with 7-zip or WinRAR. Next download from my eSnips page the Update.7z archive and extract the contained files (from the 32-bit version of Service Pack 2 for Windows Server 2003) into the \AMD64\Update folder of the extracted service pack replacing the existing files. Finally under nLite when integrating the Service Pack you need to navigate to the AMD64\Update folder, you will get a warning about being unable to integrate, just ignore it.

Apparently absolutely nothing, the base executable is exactly the same. The only difference is in the packaging, the one in my guide is the original digitally signed Microsoft installer. It's also smaller (161 v 673KB) meaning I can attach it within the 200KB limit. However, the digital signature does make Neosmart's claim a bit dubious:

January updates Deletions: Hotfix\024-Windows2000-KB914389-x86-ENU.EXE (only for users of old version of USP5) Hotfix\630-Windows2000-KB957095-x86-ENU.EXE RunOnce\dotNET11sp1b.exe Additions: Hotfix\740-Windows2000-KB958687-x86-ENU.EXE [617,512] Download from eSnips the 990-dotNET11sp1b.7z file save it to \Hotfix (see notes part 4 for other options). MD5: F02CBBB4F6B72257B0A7B456F5502193 SHA-1: AE2FEA8ADA2544362070C4D2B7BA80E27EE82DD0 Changed .Net11sp1 from a silent installer to an AddOn created using Tomcat76/Strel's script. The old silent installer is still supported. Also added support for last version of QuickTime Alternative Lite (with directshow filters) to Run2_W2Ksp5.bat.