Kurt_Aust

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.

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.

Is this good or bad? That's what I intended in the first place. No extra shortcuts or other useless crap. Just a basic installation. Well, as it means the end user has to navigate to "%ProgramFiles(x86)%\DAEMON Tools Lite\Daemon.exe" with either Explorer or the Run box in order to run Daemon Tools for the first time, I'd be inclined to say bad. Radix: Compiling the script on my XP x64 box resulted in it working, but does that mean that 2 versions of the AddOn would have to be offered, one for each of x86-32 and x86-64 ?

Atolica, with the notable exception of not creating start menu items, your script works with DT 4.30.3 under XP x64, I'll try it with Win2000 at a later date.

I get the following error in both XP x64 and 2000:

Have you tried pulling the power plug out of the back of the CD drive? Just wondering if the BIOS is only checking one optical drive for a bootable disk.

Welcome to the grand alliance of n00bs, I'm just a hobbyist myself. I certainly wouldn't call myself a service pack builder, I just maintain an easy to use hotfix list. I chose to use a .bat file to rename and hence force order as it's completely transparent, simply put I don't want to have to say "trust me", also it allows me to easily delete outdated hotfixes that retain the same name. Within the same general type nLite will slipstream (or add to SVCpack) in the listed order. As to a tutorial for creating a true AddOn (not switchless installer) for IE6, I think you're out of luck, for 2 reasons: 1. There are perfectly good methods out there already (HFslip, OnePiece's AddOn, Gurglemeyer's USP5) 2. With Win 2000 reaching end of support next year, interest has understandably died down. As for a Service Pack, well if Kelsenellenelvian couldn't do it even with access to the compiler, I don't like your chances.

No it can't, but you can use Gurglemeyer's unofficial service pack 5 to do so, guide here.

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.

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).

It already does rem fix Windows Update shortcut If Not exist "%AllUsersProfile%\Start Menu\Microsoft Update.lnk" Copy %Source%WinUp.lnk "%AllUsersProfile%\Start Menu\Windows Update.lnk" I take it D: is recognised by textmode setup and is already formatted prior to install.

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.

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.

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.

It's only for installation that one needs to use a IDE attached DVD drive, once installed SATA attached DVD drives work fine.

.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.

Cool, my motherboard is a Gigabyte GA-EP45-DS3R and I can tell you that it would NOT install from a DVD drive attached to the SATA controller. To get it to work I had to install from an IDE attached DVD drive, mind you I was doing a RAID 10 setup.

What popup? Please define as there has no mention of a popup previously. If the modified boot.ini file is working then you should: 1. get to select the level of DEP protection at boot and 2. this should be displayed at Control Panel >> System >> Advanced >> Performance >> DEP (alwayson & alwaysoff will result in neither option being shown as selected).

Try the following [boot loader] timeout=10 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Prof - DEP Always Off" /fastdetect /noexecute=alwaysoff multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Prof - DEP Opt In" /fastdetect /noexecute=optin multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Prof - DEP Opt Out" /fastdetect /noexecute=optout multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Prof - DEP Always On" /fastdetect /noexecute=alwayson That will put up an option screen where you can choose which level of DEP you wish to apply each boot. It will default to the top item of the list. You can of course remove any unwanted items. It has the additional benefit of giving you a couple of seconds (timeout setting) to hit F8 if you wish to access advanced boot options. boot.ini

Could you paste or attach your full boot.ini file?

Trust me, what could possibly go wrong ...

And now they've bumped it up to v4.30.3