Thanks john.

just 2 more questions.

How can i edit the Run1_XP-64.bat file? edit, just found out. 2 easy 2 be true

And is the addon to put in svcpack form or as exe?

November updates

Deletions:
Hotfix\190-WindowsServer2003.WindowsXP-KB936021-x64-ENU.exe
Hotfix\195-msxml4-KB936181-enu.exe
Hotfix\200-msxml6-KB933579-enu-amd64.exe


Additions:

Hotfix\
@ . . . 590-WindowsServer2003.WindowsXP-KB958644-x64-ENU.exe [1,288,568]
# ▼ 600-WindowsServer2003.WindowsXP-KB955069-x64-ENU.exe [4,885,552]
# ▼ 610-msxml4-KB954430-enu.exe [5,687,304] Optional, Microsoft XML Core Services 4.0 Service Pack 2
@ . . . 620-msxml6-KB954459-enu-amd64.exe [1,851,912] Optional, Microsoft XML Core Services 6.0 Service Pack 1, required if installing .Net 3.5
@ . . . 630-WindowsServer2003.WindowsXP-KB957097-x64-ENU.exe [1,214,000]

EDIT: Oops, forgot to mention there was a minor revision increment for the Windows update agent, far from critical though
RunOnce\# ▼ WindowsUpdateAgent30-x64.exe [7,040,352] updated 31 Oct 08


Johnhc:
Java VM installs just fine for me using the silent install switches in Run1_XP-64.bat, it shows in add/remove programs and Vuze bittorrent client will install and run. Sun's page with silent install instructions is here, but as you can see it doesn't go into great depth.

AmdM:
Unless otherwise noted, just place the original installer file at \AddOns for those applications that are supported. You can use the various addon .cab files that others have made (very useful for those programs without decent silent install options), but you will have to extract the actual executable and place that at \AddOns while adding the installation command (from entries*.ini within the .cab file) to Run*_XP-64.bat.

Kurt_Aust, thanks for the reply but it is really strange it works for you and not me. Since the install is silent, I see no error just no Java in Add/Remove or in the Control Panel.
Thanks, John.

Thanks for the fablious thread.
I got error message "integration faild" from nlite after integrating IE7 for several hotfixes eg. 040,...
Why does that happen?

esipoko,
We need more information. Please attach (not paste) your LastSession.ini and make sure you are not running nLite against a source that has been nLited before.
Enjoy, John.

At a guess, you list XP Media Centre edition as your OS, you cannot execute this guide under XP MCE as it is a 32-bit operating system.

You need to execute it under XP Pro x64 or Vista x64.

Microsoft has released a range of other non-critical updates for all versions of Windows. You can browse through the list here, or wait for them to become available via Windows Update.

http://www.microsoft.com/downloads/Browse....rtCriteria=date

As i'm editing my list on almost a daily basis, it's already updated. =)

December updates

Deletions:
Hotfix\380-WindowsServer2003.WindowsXP-KB948590-x64-ENU.exe
Hotfix\460-WindowsServer2003.WindowsXP-KB951072-x64-ENU.exe
Hotfix\580-IE7-WindowsServer2003.WindowsXP-KB956390-x64-ENU.exe


Additions:
Hotfix\
@ . . . 640-WindowsServer2003.WindowsXP-KB954600-x64-ENU.exe [817,016]
@ . . . 650-WindowsServer2003.WindowsXP-KB956802-x64-ENU.exe [1,344,888]
@ . . . 660-WindowsServer2003.WindowsXP-KB955839-x64-ENU.exe [737,656]
# ▼ 670-IE7-WindowsServer2003.WindowsXP-KB958215-x64-ENU.exe [37,197,176]

WMP11\
@ . . . WindowsMedia11-KB952069-x64-ENU.exe [1,865,616]

Could you comment on WindowsServer2003.WindowsXP-KB954600-x64-ENU.exe ? I already had the others.
Is it necessary if one do not even use the old media player 6.4 for streaming? I dont think i've ever used it for that. Just curious here.

WMP 6.4 is part of the default installation, hence the update is viewed as required. I suspect it is there mainly for compatibility reasons, although it's possible that other components call upon it in a manner invisible to the user.

Side note: WMP 6.4 is also the basis for the popular Media Player Classic.

Well they've been busy in the week leading up to Christmas over at the Redmond campus, since patch Tuesday the following updates have become available.

At \Hotfix (critical zero day Internet Explorer remote code execution exploit fix):
# ▼ 680-IE7-WindowsServer2003.WindowsXP-KB960714-x64-ENU.exe [8,686,968]

At \RunOnce (.Net Framework 3.5 Service Pack 2 wannabe):
% ▼ NDP20SP2-KB958481-x64.exe [19,282,272]
MD5: 37CD8D927566FCABF4DFFCBBE63D16EF
SHA1: 1392380EF7BAABD531F35EE5799C255A03B0DCBE
% ▼ NDP30SP2-KB958483-x64.exe [17,262,944]
MD5: 6B08400F889D7004E705363530C83E32
SHA1: 84062CF4C3F303F3641E3F730F60FDEA51BC776F
% ▼ NDP35SP1-KB958484-x64.exe [1,472,352]
MD5: 94E97AC8F788252BFF2704859CB5C737
SHA1: E69006433C1006C53DA651914DC8162BBDD80D41

So apart from putting out a real .Net 3.5 sp2 (and for goodness sake, drop Itanium support from the package, anyone who has one should know enough to download a separate package) they also need to put out service pack 1 for:
IE7 (installer=28.2MB, patches=45.1MB) &
WMP11 (16 patches according to Boooggy's list).

Kurt_Aust, is there any reason that .Net Framework and it's updates cannot be integrated with nLite. This might be faster and make the ISO smaller. Thanks, John.

.Net integration is something of a holy grail, OnePiece has apparently been able to get it to work with .Net 1.1 sp1 for XP (32-bit) and 2000, but nobody has been able to do the same for .Net 2.0 or later.

There are AddOns that install .Net 2.0 from SVCPACK at T-13, but unfortunately that won't make the install significantly faster or the ISO significantly smaller.

.Net 3.0 + still has to be installed after first boot.

OK, thanks Kurt_Aust, John.

how to bypass the popup "File is newer than the one integrating" and answer yes by default at "Do you want to keep the newer file" ?

so bad that there isn't something like a "Yes to all" button option...

i choose gui mode (not full auto) since i dont want to make a full silent install and add my name,...

btw how comes so many files are newer on the iso than on the patches?

ty

direct integration for patches bellow is not supported, do i have to force it and use the regular integration method for those hotfixes ?
are they still needed ?

190-WindowsServer2003.WindowsXP-KB936021-x64-ENU.exe
195-msxml4-KB936181-enu.exe
200-msxml6-KB933579-enu-amd64.exe
450-WindowsServer2003.WindowsXP-KB953839-x64-ENU.exe
480-WindowsServer2003.WindowsXP-KB946648-x64-ENU.exe

Please attach your "Last Session.ini" as all those hotfixes should integrate. Were you running nLite as an administrator?

EDIT: Looking back at the hotfix list, all those hotfixes except 480- are obsolete.

freshhh, I never get any of these messages, so no need to answer 'yes' always. All your listed hot fixes except 480 are no longer in Kurt_Aust's list. Please see the first page for an accurate list of the updates. Enjoy, John.

thank you both for your quick reply!

yes i'm running xLite as an admin (latest build but anyway, same case before with others builds)

well the truth is that i don't use regular sp1 or sp2 build but an already more recent one own made with nLite... so i guess this is why i've many popups... ;-) but i'd like to know if there is a workaround to accept all more recent files by default please?
i dunno if there is any advantages to use a more recent iso than the sp2 but i thought it should even be better (less operations/lighter) ;-)

yes i noticed all those hotfixes are not in the list but still wonder why coz it was there before and listed at windowsupdate.com , in my theory maybe more recent hotfixes do the same things , well i'll remove them from my dir...

what about 480 ? why is this hotfix listed if it cant be auto added, should i use the regular integration method to integrate it ?

last but not least... i'm using Sandboxie x64 (not anymore supported) and i know i should not install the following fix :

160 WindowsServer2003.WindowsXP-KB932596-x64-ENU.exe because of conflict with new Kernel Patch Protection...

but Microsoft has made another hotfix recently that causes also trouble with Sandboxie (BSOD) do u guys know what fix it is?

btw any alternative to Sandboxie that is not too big (like WMware) ? i heard of Shadow Defender but this is only available for x32 :-/

best regards

freshhh

freshhh, you cannot start with an ISO. You must start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please spend some time looking through the forum and you will see that many people violate these principles and have bizarre results. After you start over, please attach (not paste) your Last Session.ini if you still have problems. I have never heard of Sandboxie, but if it is a virtual system (WMware? -> VMware), then you can use VMware Server (free, but installer is almost 600 MB) and what I use with all Kurt_Aust's updates. I understand VirtualBox (free) also supports x64, but have not tried it.

weird because i did that before everytime (using custom iso extracted) and had no issue at all (the only thing is that during the process it tells more often that newer file is already on the iso) but after my os is perfectly stable !

i know about virtualbox / wmware but this is huge and not friendly enough for a basical use so i hope there is an alternative...

freshhh, you were lucky starting with an ISO and I suspect you would have run into more problems as time goes on. I tried QEMU and it worked (mostly) but was slow and did not have an accelerator for x64. It took me 1.5 hours to do an install and VMware Server takes less than 15 minutes. It is fairly easy to use as proved by my use. Enjoy, John.

Just grab the VMware 1.0.8 release, at 146MB it's 1/4 the size of the 2.0 release. If going for VirtualBox, grab the 2.0.6 release, the 2.1.0 release can cause BSOD's in combination with other programs.

My best guess is that 560-WindowsServer2003.WindowsXP-KB956841-x64-ENU.exe replaced KB932596, but this is only based on the similar size of the hotfixes. As KB932596 did not have an accompanying security bulletin, Microsoft does not list which hotfix replaced it.

well i guess i'll try to make some room for WMware again... but so sad there isn't currently a light alternative like Sandboxie for x64...

about space... i made a new custom XP but the size is now more than a classic 700MB cdrom can handle... is this normal?
i thought removing latest directx would have been enough but i still get the same size no matter if i put directx or not...
(i haven't put .NET Framework either... only all my current drivers)

is this a normal situation, have u all gone to dvd ?

SandboxIE is an application container, it is NOT a virtual machine.

If one skips step 9 (copy RunOnce / AddOns), then it will fit on a CD, but you'll be missing the latest versions of DirectX & .Net (might also have to leave off video drivers).

We've pretty much all gone to DVD as it would be extremely rare to find a computer with an x64 processor (2005+) that could only read CDs.

Kurt_Aust, I tried an install with ProfilesDir set to my D: partition. When your bat ran, the setting of the Windows Update short cut failed. How about using: Thanks, John.

It already does
I take it D: is recognised by textmode setup and is already formatted prior to install.

Oops! Sorry about that, Kurt_Aust, I should have looked before I posted. I have made so many changes to your original bat that I tend not to look at your current one. My D: was defined and formatted before my install. I don't think I will keep it that way, it was just an experiment. Thanks, John.

Hello

I installed XP x64 with the help of nLite as I did before but for some reason, this time only hotfixes have been installed correctly, drivers, directx, flash player, 7zip, kazaa lite,... none has been installed automatically... could you guess what ive done badly this time?

TY

see cfg attached :

freshhh, why do you have 680 IE7-WindowsServer2003.WindowsXP-KB960714-x64-ENU.exe first instead of last in your hot fix list? If you run Kurt_Aust's batch file, it will arrange the hot fixes in the proper order. You should move it to the bottom. It's hard to believe this is your problem, however. Have you run nLite more than once against the same source? Enjoy, John.

about 680 IE7-WindowsServer2003.WindowsXP-KB960714-x64-ENU.exe

i've no idea why it is listed at the top of the list, i didn't make that on purpose, all have been added at the same time and i correctly put the number at the beginning so all updates are done in the order... (well at least i thought it was that way)

i didnt run nlite more than once on the same source (anyway if u want to do that there is an alarm)

the only thing a bit unusual i've do is to slipstream wmp11 in the iso at first with the slipstream tool and not via nLite... and then i've used nLite with the modified iso...

still dont understand why nothing except hotfixes have been autoupdated...

is the section bellow correct?

[GuiRunOnce]
TimeOut /T 40
CMD /R %Source%Run1_XP-64.bat

not edited, i left the original unmodified...

freshhh, I know of no alarm that keeps one from running nLite multiple times on the same source. You can place your WMP11 in as a hot fix and nLite will integrate it for you. I just put it and its updates, in order, in my hot fix section. Please attach your Run1_XP-64.bat, so we can look at it. The RunOnce looks fine, exactly like mine. Do you see the Run1_XP-64.bat run? After the last reboot during setup, RunOnce is executed and you can watch it run. I don't understand the missing drivers. When you run nLite can you see the drivers integrating? Enjoy, John.

What can happen is that if you Ctrl-click on items, then the last one you clicked on ends up on top of the list, regardless of alphabetical/numerical sorting.


This is the manner described in the guide, move along, nothing to see here.


You did copy Run1_XP-64.bat and the RunOnce / AddOns folders into the root of your working directory before making the .iso?
Have you set an Administrator password?
You appear to be running OOBE, if you create accounts at that point and login to one of them (rather than the Administrator account) then Run1_XP-64.bat may not execute (untested guess).

First thanks all for trying to help me, I really appreciate!


Run1_XP-64.bat
I saw it running after the reboot (black dos screen) but i didn't watched carefully to see if all was fine at that time I thought everything was fine so far...

Error(s) listed in event viewer
After the installation, the only little error reported is a webcam driver VX3000 not installed in system32...
(weird that it tried & reported a failed attempt to install this particular driver coz anyway none of others (NVIDIA/Samsung monitor/...) have been correctly installed... only M$ generic)

Ctrl-click
I don't remember clicking on the list but I guess this is the best simple explanation, very dangerous feature btw ;-)

OOBE

The "Out of Body Experience" yeah I wish Hehe well ok OOBE mode is to bypass WGA verification right?
Yes this time I've disabled wga but I'm running in admin mode (no password for now) and no others accounts created...

ISO size
There is another tip to understand what's going wrong...
Before making the iso I made some tests (each time with a fresh source, not modified already) but the weird thing is that everytime the size remained the very same 780MB. No difference if DirectX or Microsoft .NET Framework 3.5 were integrated or not...
I was very suspicious about missing something...

Working directory
The runonce dir & Run1_XP-64.bat should be put in nLite root or in the same root than hotfixes?
I put them in the nLite dir... Hotfixes & drivers were in another dir...
Anyway why drivers haven't been added? (I browsed and added them in the nLite driver area like for hotfixes).
Do you guys put your drivers in the runonce dir?

Take a look at the version of the post over at PlanetAMD64. It has lots of pictures, check that you are copying the right folders and that your working directory looks correct.

Kurt_Aust, I am running OOBE (not skipped or removed) and auto login to my defined account and your bat runs fine under that account.

freshhh, It is hard for us to tell what you are doing. Are you running under VMware Server or VirtualBox? I see you have included files for both. I also see you have installed multiple versions of the same same programs (at least .NET and ThunderBird) - why? You are installing an awful lot of stuff. You probably need to pare it down until you are sure it is working and you also need to sit and watch it run and try to see any error messages that pass by quickly. With all the stuff in your bat, it should take a long time, perhaps an hour unless you have a really fast machine. I don't know why your drivers are not there unless they are not the correct drivers for your hardware. If you are running under a virtual system you will not see the drivers in Device Manager because the HW is not there and Windows will not install the drivers without the HW. Your driver files are processed by nLite into the source folder and you can see them in c:\NLDRV folder after installing (unless you selected to delete after install in nLite). The original driver files as well as the original hot fix files are not carried to the ISO. Hope this helps, John.

Call me crazy, but wouldn't it save you a LOT of time and trouble if you'd just offer an entirely up-to-date iso of Windows XP x64 Edition SP2 today, and then let people use nlite to strip that iso for their personal preferences?

I for example will remove (not need) IE and OE, nor will I need Windows Defender or many of those installs. Using these batch-files will be obsolete for the most part.

meowing:
First of, please dont ask Kurt or anyone else to share windows xp x64 iso or such online. That would be piracy, and is knocked back on pretty hard on such a forum.
No one is forcing your hand to install any software, if you dont have the software on the install media, it wont get installed regardless. Think of Kurt's batches as a how-to do it on your own.

A bit more gratitude instead of complaint would serve you better i'm sure.

January update:

Delete
Hotfix\570-WindowsServer2003.WindowsXP-KB957095-x64-ENU.exe

Add
@ Hotfix\690-WindowsServer2003.WindowsXP-KB958687-x64-ENU.exe [1,237,880]


After the excitement of December, rather a boring month, on the other hand I've added more supported applications (and notes to others):
Mihov Image Resizer
nLite
WMP11 Slipstreamer
AutoIt
ImgBurn
Virtual Box (v2.1.0 can result in NDIS.sys BSOD in combination with other programs, v2.0.6 here)
Daemon Tools Using JohnDoe74's Addon (v4303r needs a fix, only use if last updated Jan 15 or later)



Meowing:

As Trance pointed out, I can't for legal reasons link to a fully updated XP x64 .iso, of course if that is what you want you can search any number of torent sites, but can you trust what you download?

Even if if were not frowned upon, I'd then have to deal with any number of special requests (I want it IE7 but not WMP11 / I want it with WMP11 but not IE7 / I want IE8 beta 2 / etc.).

I fully expect that most of the executables mentioned in the batch files will not be installed on any one particular computer, for instance I've included support for Firefox, Thunderbird, Seamonkey & Opera in the alternate browsers section. Realistically only a web developer would need to install all of them.

The point being is that they are supported, if you don't want them then don't place them in \AddOns and the batch file will skip over them.

What's the difference between this one and the .msi file from Neosmart ?

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:

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.

Kurt_Aust, this looks really great for the guys moving from 32 to 64 bits. Thanks. I have a few of questions. I assume the 64 bit SP2 is extracted into the AMD64\Update folder? Should the .exe or the .msi be selected - I assume the .exe? What is the failure to integrate error? I assume you know you can create a log by specifying /log:path switch on the integration of the SP. Thanks much, John.

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.

Kurt_Aust, thanks. In Step B, why not say extract into AMD64\Update folder? BTW, it has a { instead of a ( like the rest. Why does this need to be done in the source folder? Are the files needed after the SP is installed? I assume the extracted SP2 is very large. I can't see the error messages since I don't have a sign-on for PlanetAMD64. Thanks, John.

\AMD64\Update exists in the extracted SP2, you can't extract it into itself.

It has } rather than ), because if I use ) I get .

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.

Kurt_Aust, thanks, I was erroneously thinking that the SP was being extracted into the source folder AMD64/Update folder. Enjoy, John.

Uploaded an archive of the screenshots to my eSnips page.

Thanks, Kurt_Aust, great set of screen shots. John.