VTshadow

Got a question for you guys. Suppose I setup my xpcreate with a fresh source, all the hotfixes and Service packs, and add a few files to the FILESCD folder, such as an answer file to do an unattended installation. Run XPCREATE, slipstream all the patches, remake all the cabs, repackage into CDROOT, and create the .iso file to be burned to cd. That works great. Now, after all of that work, I want to go back and change a few files in FILESCD to be included in the CD. How can I, if it is even possible, have XPCREATE just repackage the new files in FILESCD without having to go through all the trouble of redoing the cabs and slipstreaming the patches. Basically, all I want to do is make a few changes in CDROOT\$OEM$ and remake the .iso file. Are there any settings in the INI file that I can turn off to just do this? Or do I need to run CDIMAGE.exe and point it to the updated CDROOT? I would look in xpcreate.cmd and just rerun that command, but the EULA.txt doesn't allow that, so what's a guy to do? Thanks for the help VTShadow

@koszopal Thank you, I know quite well what xpcreate does, I've been using it for about a year and a half now.

So what you are trying to do is create a cd that will patch an already installed machine, not create a slipstreamed cd that is used to completely reinstall a new machine?

While I haven't had a chance to try your fix yet Greenmachine (still working on getting SP2 to work) I'll try it when I have some time. In the meantime, I found another way to "slipstream" SP2 into an image without using XPCreate. It turns out that SP2 comes with a spiffy little command line option called integrate, and it works like this. Copy your XP cd to your harddrive, and type "SP2.exe -integrate:<Full Path to Image>" and it will sit there and slipstream itself. I've test this with the Remote Install Server and it works just fine. Now just to get everything else to work with SP2. While this is only a temp fix if XPCreate is not working for you, as for now SP2 is the only hotfix one needs, I hope I can get future attempts with XPcreate to work, when I need it to slipstream more than 1 hotfix. Thanks for the help guys.

Greetings. First off, would like to thank Greenmachine and all others who have helped this project be as great as it is. Keep up the good work. I've been using XPCreate for months now, and have had not a problem until now, with Service Pack 2. While I understand it's not fully supported yet, I thought I'd pass this along and see what you guys think. During the processing, I received this error in the .cmd prompt. -- 12:15:23 --> Files already in CABs are not new. File Not Found File Not Found -- 12:15:25 --> Files already in I386 are not new. File Not Found -- 12:15:25 --> Add list of New Files to [Files] in DOSNET.INF. File Not Found -- 12:15:25 --> Checking sub-directories. -- 12:15:25 --> RoyalBox's SVCPACK.INF Creator File Not Found File Not Found File Not Found File Not Found File Not Found File Not Found File Not Found File Not Found File Not Found When I try to integrate the final result into my Windows 2003 Remote Install Server, he complains that the SVCPACK folder can't be found...I check back to CDROOT and sure enough, no SVCPACK folder in I386, yet on a previous XPCreation using SP1 and hotfixes, I can find a SVCPACK folder in the I386. Here is my XPCREATE.log...couldn't find anything totally amiss, but then I didn't look too terribly hard. Thanks for the help. XPCREATE.LOG

okay...little clarification on that. Can I add drivers in the same folder. Say I have [unattended] OemPnPDriversPath=%Path%\Chipset;%Path%\Video;%Path%\Moniter;ETC and in each of those folders I have all of my Chipset drivers, in the next folder is all of the video drivers, etc. Will Windows still manage to get the right driver, or do I need to create a seperate folder for each driver.

Here is a general Driver question that some of you might know. In the answer file, you can include drivers using the [unattended] OemPnPDriversPath= and include drivers for the computer that you are installing. Now, what if I want to install on 2 different types of computers with different drivers? Can I include all of the drivers for both machines on the same "OemPnPDriversPath" line in the same answer file, or do I have to make up a different answer file for each machine. What I'm looking at trying to do is install several different machines from the same answer file/image. Is windows going to automatically pick the right driver from the "OemPnPDriversPath" list and discard the rest or do I have to lead it by the hands by using a different answer file with each type of machine?