Kurt_Aust

No new updates this month. KB943729 (Group Policy Preference Client Side Extensions) still doesn't work properly with Windows Update, if it's still not working next month it will be dropped. Added information on testing: I use VMware Server for testing purposes, it's free but has some limitations (no sound for one) and requires registration. Before downloading and installing, use this tool to ensure that your processor will support 64-bit guests. Silent installation of Virtual Machine extensions is supported, there is a file "windows.iso" at "\Program Files (x86)\VMware\server" extract its contents and save them to \AddOns\VMware. The good news for the month is that there is a new version of the WMP11 slipstreamer out (v1.2) that fixes the problems with XP x64 integration. So you can once again get your Boooggy on. JohnHC: 1. Visual C++ is entirely optional, just like .Net, Defender, et al. I've restructured the download list to make this clearer. 2. You are correct in that neither Virtualbox nor VirtualPC support 64-bit guests. They are supported for installation in Run1_XP-64.bat because compared to VMware server they are about 1/5 the size, take about 1/10 the time to install and do not require registration. The most useful O.S. for a user of XP x64 to virtualize is Win 98se, for this VirtualPC 2007 is best (VirtualBox doesn't properly support 98se). 3. As TranceEnergy noted, you missed the part about EXTRACTing the DirectX redistributable, again I've made it clearer. Trance Energy: I haven't included .Net 1.1 because it isn't officially supported on XP x64, yes I know it can be made to work but as far as is feasible this guide will use only those programs / runtimes that are officially supported. I was going to include the Visual C++ 2008 runtimes, but Microsoft brilliantly decided to give the file the exact same name as the Visual C++ 2005 SP1 runtimes. As I've come across a program that requires the 05 version (and won't work with the 08 one), guess which version gets the slot? As I've never encountered your double entry problem (even on my ATI chipset laptop I use for testing), I don't think I'll be able to help you.

Johnhc: Your example is correct. TranceEnergy: I don't entirely understand your problem, could you post a screenshot?

491MB for the beta? Yipe!! To think that Virtual PC 2007 is only 30.5MB and Virtual Box is only 20.6MB. Even allowing for debugging code, there's got to be some serious bloat in there. I didn't bother installing VMWare tools as it is unnecessary for testing purposes. There is a file "Windows.iso" located at "Program Files (x86)\VMWare\VMWare Server" that includes the drivers. Some can probably be integrated, but I haven't actually tested this. IIS is installed in the guest OS as I have to ensure no updates for it are needed. Note that if you choose to install IIS from the nLite option box in the unattended section, it's only partially installed.

Yes I'm running XP x64 (as listed under my name to the right). As for CPU support, it won't host XP x64 on my desktop (Athlon 64 3200+ Skt 754), but will on my laptop (Turion 64 ML-34), this tool should help. I don't believe IIS is necessary (at least not for a local host, which is all I've ever used). I took a look at the comments and as I noted elsewhere one really should only virtualize XP x64 for testing purposes. It's simply too painfully slow to actually use, W2K & 98se are about the limit for a usable virtual machine (at least on my equipment). Inertia goes a long way to explain why I'm still on version 1.0.4, I know of no particular reason not to use the beta. In VMWare server, the guest's clock always falls behind. QuickTime Alternative light (as Media Player classic is already included in the K-Lite mega codec pack). I don't know why the Java control panel wouldn't show (since it does for me), but running a Java app as a test can't hurt.

Java control panel shows up fine for me and the Java virtual machine works as Azureus works. As you can see from the screenshot I use VMWare server for testing. Not perfect perhaps, but one is prepared to go without some niceties in order to save $180+. I'm at GMT+10 (Australian eastern seaboard), at least 85% of our population will fall in this time zone. Most updates will not show in add/remove programs as they are directly integrated into the CD, replacing existing files. If you take a look the \Hotfix directory is 193MB, but your .ISO only grows by about 20MB and I'm afraid it's not the TARDIS. The only hotfixes available for removal will be those that don't integrate (found at \AMD64\SVCPACK) and those installed by Run1_XP-64.bat, mind you almost all the others will be security updates and hence you really wouldn't want to remove them. Bartgrefte: Buggered if I know when the issue with KB943729 will be fixed. I called MS technical support about it and a few other issues with this month's Windows Update service but just got the company line. All I can say for sure is that the problem has nothing to do with nLite as if I run the installer manually after installation has completed, it still shows up on Windows Update.

This is expected behaviour and nothing to worry about. It happens due to the task scheduler starting other processes (in this case account initialization) even though it has received a shutdown command. If and when you next log into the Administrator account, the system will perform/complete account initialization. As it is a 32 bit virtual environment, the Java control panel doesn't show up in the normal Control Panel, you have to double click "View x86 Control Panel Icons" (found in the normal Control Panel). You should (as a general rule) always try to use the latest version of any software as security bug fixes are the most common reason for updated releases. When uploading the config file, I write Run1_XP-64.bat to support the latest versions available, this should not be taken as a requirement to use that version if a newer one has come out. Rather you should rewrite Run1_XP-64.bat to support the updated version (or if lazy, rename the updated installer). The only proviso is that I won't have tested the updated software. As noted in your other post, try VMWare server if you find QEMU too slow.

My last look found VMware cheapest license to be $180 and Virtual PC did not support XP x64. I do appreciate your response and I am glad to answer you questions but I think your are a bit quick to judge my efforts and environment. I have looked high and low for a virtual system for running XP x64 as both host and guest (including asking in this forum), finding only QEMU so far. If you have a legitimate recommendation I will be glad to check it out. The main question I am trying to get answered is why does an nLited system with SP2 run so much slower than the original system (only SP1). See my description of the Start menu problem. Thanks again. John Actually, VMWare server is free and supports XP x64 as a guest. Mind you there are limitations, most obviously no sound, but then only a complete masochist would run XP x64 in a VM for anything other than testing purposes.

Well I haven't really had much of a chance to check it out, but so far it's a definite improvement over previous versions. First up, it actually runs on my laptop now (previous versions failed due to video driver issues). From zero points to some points, % improve -> /0 error Secondly, I've been able to install it and more importantly GRUB on a USB HDD attached to the Lappy (mind you, I had to edit the GRUB config file for it to load partitions correctly).

In the root directory of your created CD (and also in the nLite working directory) there should be a file "LAST SESSION.INI", we want to see that in order to work out what you've done. Do NOT post the file "LAST SESSION_U.INI" as that contains your personal details (registration key et al).

Maybe reading through this thread (which mostly uses original Microsoft files) will help. As would posting your failed session files.

Obviously (blows the laptop I run VMWare testing on out of the water). That solved it As long as you understand the security implications of turning off device driver signing enforcement (I prefer not to, but then I'm paranoid). The original Microsoft files are not slipstreamable, this guide uses Run1_XP-64.bat to silently install them on first Logon. Some people have repackaged the files so they can be added as AddOns at step 4 of the process (e.g. HJW's posts in this topic), but this guide will be written to use the original files whenever possible. No, I hadn't noticed (my x64 hardware is all AMD), but as it is a hardware item and hence not applicable for all users, it will not be added.

Strange, I don't get that, mind you I only tried in VMWare (320GB IDE), I don't have a real machine with a SATA2 HDD. Your up-to-date method includes large disk support (>137GB) I presume? (USP 5.1 includes it)

SPTD is definitely installed, if I run \daemon\dt123.exe and complete the installation manually, Daemon Tools works.

April Hotfix Updates Deletions: Hotfix\290-Windows2000-KB938829-x86-ENU.EXE Hotfix\430-IE6.0sp1-KB944533-Windows2000-x86-ENU.exe RunOnce\Windows2000-KB917344-56-x86-enu.exe (only applies to older 5.1.2195.21 version of the USP) Additions: Hotfix\315-msxml4-KB936181-enu.exe [5,652,328] Optional, Microsoft XML Core Services 4.0 Service Pack 2 Hotfix\430-Windows2000-KB941693-x86-ENU.EXE [1,314,672] Hotfix\440-Windows2000-KB944338-x86-ENU.EXE [832,368] Hotfix\450-Windows2000-KB945553-x86-ENU.EXE [575,856] Hotfix\460-Windows2000-KB948590-x86-ENU.EXE [618,864] Hotfix\470-IE6.0sp1-KB948881-Windows2000-x86-ENU.exe [498,248] Hotfix\480-IE6.0sp1-KB947864-Windows2000-x86-ENU.exe [4,210,248] RunOnce\vcredist_x86.exe [2,723,264] Optional, Visual C++ 2005 SP1 runtime

I'm afraid it still doesn't work. Is the "dt4123.exe" file supposed to instantly delete itself? When running it manually dt4123.exe vaporizes and then the language selection box appears.

Additions: Hotfix\195-msxml4-KB936181-enu.exe [5,652,328] Optional, Microsoft XML Core Services 4.0 Service Pack 2 Hotfix\365-WindowsServer2003.WindowsXP-KB944338-x64-ENU.exe [3,866,672] dotNET\vcredist_x64.exe [3,200,960] Optional, Visual C++ 2005 SP1 runtime It seems that the Windows Update logic is a bit twitchy this month (nothing unusual there), KB944338 should have shown but didn't and KB943729 still shows up even after being installed. I'm still including KB943729 in the list as they'll probably fix it by next month. Bartgrefte this thread might have the information you seek. From memory all of the default settings you mentioned can indeed be changed with nLite.

Tragically no, it remains open waiting for user input and as I force a reboot (due to installing a heap of stuff via RunOnce) it doesn't install at all.

Note to Windows 2000 users: Use the older 4.10 version, the newer 4.12.3 version doesn't install silently. The latest version throws up a box asking you to choose a language, almost certainly indicating that the cause is that the autoit script isn't compatible with Win2K.

Optional hotfix KB943729 (Group Policy Preference Client Side Extensions for Windows XP x64 Edition) is set for silent installation via svcpack by nLite. However it still shows up on Windows update, any thoughts? EDIT: Further investigation reveals that nLite has nothing to do with this problem. I can manually execute the hotfix after Windows installation and it still shows up on Windows Update. So it's either a flaw in the hotfix itself or an error in the Windows Update logic.

April updates: Deletion Hotfix\350-IE7-WindowsServer2003.WindowsXP-KB944533-x64-ENU.exe Additions Hotfix\350-Windows-en-US-KB943729-x64.exe [889,912] This one does not seem to install, fault has been reported Hotfix\360-WindowsServer2003.WindowsXP-KB941693-x64-ENU.exe [8,403,504] Direct link to .exe Hotfix\370-WindowsServer2003.WindowsXP-KB945553-x64-ENU.exe [1,048,112] Hotfix\380-WindowsServer2003.WindowsXP-KB948590-x64-ENU.exe [1,330,224] Hotfix\390-WindowsServer2003.WindowsXP-KB948881-x64-ENU.exe [670,768] Hotfix\400-IE7-WindowsServer2003.WindowsXP-KB947864-x64-ENU.exe [37,178,416] Direct link to .exe

Well it's not an AddOn as the script just calls the standard end-user installer with the appropriate silent install commands. It doesn't require that the Open Office installer be repacked into a .cab file with an entries.ini section. It's also installed on first Logon rather than at T13. When an updated version of Open Office comes out, you just have to change the filenames to match. You add the script to RunOnce in the unattended section, I find it easier just to edit & load a previous preset rather than copying it into nLite.

Not technically an AddOn, but if you use a 7-Zip AddOn (both Rado354 and JohnDoe74 provide one, it's a good utility, you really should have it) you can add the following code to RunOnce. rem install & configure Open Office, requires 7-Zip for configuration options "%ProgramFiles%\7-Zip\7z" X %Source%AddOns\OOo_2.4.0_Win32Intel_install_en-US.exe -O"%ProgramFiles%\OpenOffice24InstallFiles" msiexec /I "%ProgramFiles%\OpenOffice24InstallFiles\openofficeorg24.msi" ALLUSERS=1 SELECT_WORD=1 SELECT_EXCEL=1 SELECT_POWERPOINT=1 ADDLOCAL=ALL /Qr rem RmDir /S /Q "%ProgramFiles%\OpenOffice24InstallFiles" If Not exist "%ProgramFiles%\7-Zip\7z.exe" %Source%AddOns\OOo_2.4.0_Win32Intel_install_en-US.exe /S This will give you more install options (such as whether to open MS Word files with Open Office by default). NB: Above code assumes the installer is located in a folder \AddOns on the install media, the /S switch will do a silent install (no need for 7-Zip) but you don't get the configuration options.

Sorry to say, but XP SP3 includes neither IE7 nor WMP11, so you'll still have to integrate them with nLite and the WMP11 slipstreamer respectively. Mind you, I'd have to agree it would be nice if they could put out 2 versions of the service pack, one vanilla (as currently planned) and one with the kitchen sink: IE7, WMP11, DirectX updates & .Net 2.0

Your file structure should look like this after extracting the config archive (where Drive:\Path is where you extracted it): Drive:\Path . . . . . . . . \Win2000_sp5+ . . . . . . . . . . . . . . . . . . . \AddOns\ . . . . . . . . . . . . . . . . . . . \DirectX_9c\ . . . . . . . . . . . . . . . . . . . \Hotfix\ . . . . . . . . . . . . . . . . . . . \Misc\ . . . . . . . . . . . . . . . . . . . \RunOnce\ . . . . . . . . . . . . . . . . . . . \InstallWin2000sp5.txt . . . . . . . . . . . . . . . . . . . \Run1_W2Ksp5.bat . . . . . . . . . . . . . . . . . . . \Run2_W2Ksp5.bat If you also extract the hotfix archive to Drive:\Path then the files should end up in the appropriate folders (Hotfix, RunOnce & AddOns). At step 1 in the procedure nLite will prompt you to locate or create an empty folder as your working directory, this is where the files are copied to, you should end up with something like this (many files & directories left out): Drive:\nLite_working_directory . . . . . . . . . . . . . . . . . . . . . \$OEM$\ . . . . . . . . . . . . . . . . . . . . . \AddOns\ . . . . . . . . . . . . . . . . . . . . . \DirectX_9c\ . . . . . . . . . . . . . . . . . . . . . \I386\ . . . . . . . . . . . . . . . . . . . . . \RunOnce\ . . . . . . . . . . . . . . . . . . . . . \Autorun.inf . . . . . . . . . . . . . . . . . . . . . \InstallWin2000sp5.txt . . . . . . . . . . . . . . . . . . . . . \Run1_W2Ksp5.bat . . . . . . . . . . . . . . . . . . . . . \Run2_W2Ksp5.bat . . . . . . . . . . . . . . . . . . . . . \Setup.exe

March updates: New version of the DirectX redistributable (Mar 08), extract it to \DirectX_9c [67,196,968] Direct link to .exe MD5: E1E85376D4F03072B99FF0E9ED5DDE36 SHA1: 21AA91CA8E0CBB5FBB986F47A1CCDAD5D2984CAE No other hotfix changes (so no change in the torent or 7-zip package either).