gosh

If you can't make the boot folders you might want to skip this process, it's not for the faint of heart. -gosh

Forgive my ignorance, but i don't see how installing hotfixes via GuiRunOnce is any faster than installing hotfixes via svcpack.inf or cmdlines.inf? Either way you'll have to wait as the hotfixes are extracted and installed. Or am i missing something? You don't say exactly where to put these batch files. All the %1 does is put the files on the system drive if im not mistaken. Why does that make this any better than any other method? <lost> -gosh

You don't have to cab svcpack.inf. You can if you want, but you'll only save like 1k. -gosh

Either way folder name should be $OEM$ as in Original Equipment Manufactor. -gosh

You might want to use a variable just in case you want to use a cd based install in the future Set Source=D:\Backups ECHO. ECHO Installing AIM 5.2 ECHO Please wait... start /wait %Source%\AIM\Install_AIM.exe /s -gosh

If you want that message copy bootfix.bin into your VOL1 or boot folder. If you cannot see the ~LS and ~BT folders, make sure you can see hidden files and folders. It doesn't matter where systemfileprotection is, because it's it's own seperate catagory. -gosh

My first step is always to delete the vmware profile and make a new one from scratch. If xp setup is hanging at the logo, that's usually a bad version of ntoskrnl.exe. See if it's the right version, see if you can go into safe mode. Try the latest version of vmware. Make sure you have enough free space and do a chkdsk. -gosh

You cannot slipstream the rollup, just like you couldn't slipsteam the win2k security rollup. The reason you can slipstream a service pack is because it has IP and IC folders that contain the slipstream files. IP is for xp pro, IC is for XP Home. If you look at these folders you will see they have files such as txtsetup.sif, dosnet.inf, hivedef.inf, and others. The rollup doesn't have any IP or IC folders, and it has none of these files, so you cannot slipstream it. I guess you could manually make these files for the rollup, but that seems really complicated. As i mentioned i gave up on trying to truely slipstream the rollup because it works good enough for me. The update folder is less than a meg, and the install takes about the same time with the rollup as without the rollup, so im happy with that. To truely slipstream the rollup all you need to do is find a way to register KB826939.cat and import the registry keys. The registry keys wouldn't be an issue, but the catalog file would be. XP setup installs the catalog files first, at the 33 min mark using syssetup.inf. Syssetup.inf is digitally signed and there's no way to modify this. I do have one interesting idea to "bypass" this microsoft crap. One idea i had is to rename KB826939.cat to tabletpc.cat and put it into the i386 folder, deleting the old one. Even if you don't have a tablet pc, xp sp1 will register the catalog file. I'm thinking all xp setup does is look for a valid digital signature, i don't think xp setup really cares if tabletpc.cat is the real one or not. Also, xp sp1 setup processes tabletoc.inf. You might be able to install the catalog by renaming it to tabletpc.cat, and you might be able to import the rollup registry keys by putting them into tabletpc.inf. If anyone wants to try it go for it, i never attempted this. -gosh

This installs recovery console and a flat silently, but you could easily modify it to do other things such as saved the cdrom drive letter as a variable. source.bat -gosh

Install the XP Application Compatibily toolkit 3.0. It'll let you disable that. http://www.microsoft.com/downloads/details...&DisplayLang=en Just download and install it. Open it up and where it says win2k, just disable it. -gosh

Well does KB822603.log exist? Does it have errors? Can you install the hotfix using the same parameters are your svcpack.inf? -gosh

I posted how to do this in my reduce size of source thread http://www.MSFN.org/board/index.php?showto...opic=9478&st=80 -gosh

So far i've shown how to reduce size of i386 folder, make a multi-os cd, and include xp and winpe on the same cd here. The steps i've already shown can be applied to make much more fancy, and complicated cd's. Let's take the cd process further and make a cd with: winxp home winxp pro win2k pro sp2 win2k server sp2 win2k advserver sp2 (and win2k datacenter if it really makes you happy) Back when xp came out i made a cd called XP2K that had all these os' on a 700 meg cd, all unattended. These instructions can be applied to the latest service packs, but when i originally made the cd i used the original versions of xp and win2k with sp2 slipstreamed. First, follow my previous directions to make a cd with XP Pro on it. You should have VOLx folders for the boot files, and XP in the WinXPPro folder. On the root of the cd should be the ident files - win51, win51ip, win51ic, etc. Next, we're gonna add xp home to the cd. Follow the same directions to put xp home on the cd. 1 - run winnt32.exe /noreboot, and make sure under Advanced Options "make local source" is checked or grayed out. 2 - rename c:\$Win_NT$.~LS\ to c:\XPHome 3 - rename the c:\$Win_NT$.~bt\ folder to HOM1 4 - delete the size.sif file in the XPHome folder 5 - Hex c:\HOM1\setupldr.bin, replace i386 with HOM1 (all capital letters) 4 times 6 - Edit c:\HOM1\txtsetup.sif and change SetupSourcePath to \XPHome\ 7 - Delete any unneeded files in the c:\HOM1\ folder such as winnt.sif, migrate.inf, bootsect.dat. If you want to do an unattended install, put your unattend file as winnt.sif into the c:\HOM1\ folder8 - Now make the boot sector. If you still have VOL1.DAT copy it as HOM1.DAT, and hex it and change VOL1 to HOM1, such as: Now let's copy the c:\XPHome and c:\HOM1 folders to our xp install source. On our cd now we should have the following folders: Now we're gonna add win2k to the cd. Follow the 8 steps above for win2k pro, win2k server, win2k adv server. Just replace XPHome and HOM1 with the following table:Rename the c:\$WIN_NT$\~LS\ folder to the following: win2k pro = Win2kPro win2k serv = Win2kSrv win2k adv srv = Win2kAds Rename the c:\$WIN_NT$\~BT\ folder to the following: win2k pro = PRO1, PRO2, PRO3, etc win2k serv = SRV1, SRV2, SRV3, etc win2k adv srv = ADS1, ADS2, ADS3, etc So now your cd should have the following folders: Now we need to add the cd idents and other files. On the root of the cd, make sure you have the following: WIN51 WIN51IP WIN51IC WIN51IP.SP1 (only if using sp1) WIN51IC.SP1 (only if using sp1) SPNOTES.HTM CDROM_IA.5 CDROM_IP.5 CDROM_IS.5 CDROM_NT.5 CDROMSP2.TST DISKEMU.CMD LOADER.BIN DISKEM1X.BIN DELOAD.BIN VOL1.DAT VOL2.DAT (optional) VOL3.DAT (optional) HOM1.DAT PRO1.DAT SRV1.DAT ADS1.DAT Now copy the following files to the XPHome, WinXPPro, Win2kPro, Win2kSrv, Win2kAds folders: WIN51 WIN51IP WIN51IC WIN51IP.SP1 (only if using sp1) WIN51IC.SP1 (only if using sp1) SPNOTES.HTM CDROM_IA.5 CDROM_IP.5 CDROM_IS.5 CDROM_NT.5 CDROMSP2.TST That's it. You now have a bootable cd with xp home, xp pro, win2k pro, win2k server, win2k adv server. You should have around 40 megs to add other stuff such as software. -gosh

@ Beppe XP/2k/2003 have hidden settings for Encryption and System file protection. You could put the value as such in your unattend file: [systemFileProtection] SFCQuota=0 SFCDisable=ffffff9d That disables simple file sharing and doesn't make a dllcache folder -gosh

To make a cd with win9x you just make a bootdisk as bootdisk.ima and put it into your menu. If you wanted to you could edit the config.sys and autoexec.bat files on the bootdisk to have it auto start setup. To automate it just put msbatch.inf into the win9x folder. If you have an oem cd, the boot disk it makes auto starts oemsetup.exe Making an all in one cd isn't hard, it just takes a high level of skill to pull it off. All it takes is a mispelled file or missing ident files and it won't work. I spent 6 months troubleshooting one all in one cd i made. You have to have a firm grasp of how the xp boot process works to fix any problems. -gosh

ya Alanoll is right, it's the oemskipwelcome. If you don't have that in Gui mode you;ll get the welcome to setup screen, but if you continue you won't see anything else. -gosh

I thought this was a site to share tips on unattended installs? I don't see how bashing me is going to help anything. -gosh

I made this last night. It's very buggy but appears to work ok. Use at own risk. I thought i would show it in case anyone wants a look at what im working on. I'll explain more about it later when it's closer to being done. -gosh Install.inf

If you double click on a theme or msstyle and it loads as windows classic, the only possible cause would be an unpatched uxtheme.dll, it's not a .theme problem. -gosh

bored: you didnt mention if youre using xp home or pro, the command wont work on xp home. Also, are you literally putting the command into guirunonce, or using guirunonce to call a batch file with the command? Numinous: sos displays the drivers for troubleshooting, but more times than not it's worthless because xp freezes on a driver before it's shown on the screen. If you want to bypass the boot logo try /noguiboot -gosh

Did you do an OEMPreinstall? Do the basics. First run setup and make sure the $OEM$ folder is being copied. During the install do shift + F10 and makes sure the files are all there. See what happens when you run your batch file from the cmd window. Check the log files. -gosh

It amazes me the comments by some people. All i see is comments like "it isnt a true slipstream" and "just use -x to extract it". I'm willing to bet the people making these comments haven't even tried the rollup slipstream guide. And yes, it isn't a "true" slipstream because update.exe is run, but it's as close as you'll get. I spent several hours and 5 installs to get the method right, and i really didn't see anything to be gained spending another 5 hours just to bypass update.exe. As Aaron mentioned, with this method the xp install takes about the same time as without the rollup. To me, that's good enough. I had some ideas on how to truely slipstream this. But does it really matter if the catalog file is registered by update.exe or syssetup.inf? Either way the catalog file gets registered, who cares how it's done. Update.exe only takes less than a meg anyway. A true slipstream would only save you less than a meg of space. So again, who cares? It would be nice if rather than complaining there could be some "thank you's". Aaron took time to make a nice guide with pictures and explanations for you guys, saving you guys some work. I also spent some time finding this method and testing it. -gosh

It's the full thing. The 9 megs turns into 54 megs when you run it. -gosh

The reason i don't have ntoskrnl.exe in dosnet.inf is because it's already there. Here is the default ForceCopyDriverCabFiles for dosnet.inf (for xp sp1, without sp1 it might NOT be there. But my guide was only written and tested for xp sp1): As you see ntoskrnl.exe is first, so i didn't put it again. As long as update.exe is run, you won't have any problems. If for some reason update.exe isn't run, xp won't boot up because it's using an older version of ntoskrnl.exe from driver.cab. the rollup will work fine with my method. -gosh

Yup, i was right. Digital certificate is Monday, September 22, 2003 5:40:38 PM, so this is the same file as the beta one. -gosh