Ghostrider

This is all I have in the relevant sections of Winnt.sif [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" AutomaticUpdates="yes" [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch="No" WaitForReboot="No" TargetPath=\WINDOWS DriverSigningPolicy=Ignore

just as you suggested, working from SP2XPCD folder, all new versions of packs/base downloaded this afternoon, still getting same errors as above ED: Just tried same process without mass storage, recieved same as 2nd error in my last post, the same as ghostrider had.. he didn't have this problem at home though, I tried changing my folder to SP2XPCD and I still get errors... gotta be more to it then path?? ED: Just been looking at the RUN_ME.CMD file, in the sections for chipset you have the following: <Snipped> are the highlighted %systemdrive% variables meant to be there, isn't this what will be causing the 2nd error I had, and the same for ghostrider previously? ← This made me think.... the XPCD folders i created are on D drive at work but are on C drive at Home.. The %systemDrive% i wonder if that's what's making it fail... ???? EDIT... Never mind... i moved XPCD folder to D drive and it still works...

Ok, home from work now so i tried it on my home computer.... this time i created 2 clean XP SP2 XPCD folders on drive C then removed everything from driverpacks folder leaving just the new DPacks and the BTS Driverpack base i also made sure that all files in the XPCD folders were NOT read only then i extracted Driverpack, ran the slipstreamer then copied files from UWXPCD_ROOT, ran Run_Me and all went well, NO ERRORS..!???? So now i have to figure out why exactly the same files and folder structures would make a difference between my work computer and my home computer.. To those others having trouble... please start with fresh SP2 XPCD folder and make sure all files are read/write also create a brand new driverpack folder, remove all previous files before downloading new DPacks and Base file...

Ok i ran the slipstream on an existing UWXPCD folder the 1st time, i just created a fresh UWXPCD folder and now i get this result, no Intel chipset cab this time Bashrat the Sneaky's DriverPacks Slipstreamer - STEP 3 BTS DriverPacks will be slipstreamed into your UWXPCD, using method 2. _ back-up of winnt.sif made... _ previously [method 1]-slipstreamed DiverPacks deleted... _ original SETUP.EX_ recovered... _ presetup.cmd deleted... _ back-up of txtsetup.sif made... _ back-up of dosnet.inf made... _ back-up of drvindex.inf made... _ DriverPacks slipstreamed... [method 2] _ replaced real setup by a fake one, copied presetup.cmd... _ txtsetup.sif file updated... The system cannot find the file specified. _ DriverPack MassStorage slipstreamed... _ commands added to winnt.sif to install DriverPacks control panels... ################################################################################ Press any key to continue . . . Edit.. I notice that Fedit.exe, Presetup2.cmd and SetupCopyOemInf.exe are all left in the root of the folder

I get this error on slipstreaming both XP Home and pro Bashrat the Sneaky's DriverPacks Slipstreamer - STEP 3 BTS DriverPacks will be slipstreamed into your UWXPCD, using method 2. _ previously slipstreamed DriverPack MassStorage removed... _ back-up of winnt.sif recovered... _ previously [method 1]-slipstreamed DiverPacks deleted... _ previously [method 2]-slipstreamed DiverPacks deleted... _ original SETUP.EX_ recovered... _ presetup.cmd deleted... _ back-up of txtsetup.sif recovered... _ back-up of dosnet.inf recovered... _ back-up of drvindex.inf recovered... _ DriverPacks slipstreamed... [method 2] _ replaced real setup by a fake one, copied presetup.cmd... _ txtsetup.sif file updated... The system cannot find the file specified. _ DriverPack MassStorage slipstreamed... 2005/04/19 16:48:21 ERROR 3 (0x00000003) Accessing Source Directory C:\D_C_TMP\D P\C\I\ The system cannot find the path specified. _ Intel Chipset .inf files copied to $OEM$\$$\INF... _ commands added to winnt.sif to install DriverPacks control panels... ################################################################################ Press any key to continue . . .

We believe you... and Yehhh!!! it works.. Now for more XP installs

LOL... Now he's really teasing...

404 error on base pack..???

Xplode should run at T12, xplode.exe will usually be in the $OEM$\install folder of your UWXPCD as will your XML file however you can put install programs in any folder as long as the XML file points to the right place i.e <item name='Adobe Acrobat 7'> <file name='Installing Adobe Acrobat 7...' command='execute' program='#systemdrive#\install\AdobeReader7\AdobeReader7.msi' arguments='/qb'></file> </item>

It's not a copy command that is being referred to, you need to create a $Docs\Default User folder in your $OEM$ folder and copy the files you need into there, then recreate your UWXPCD, they will then be copied to the My Docs folder on install, you don't need to copy anything...However if you want to do it that way then use COPY /Y "%systemdrive%\install\Docs\filename.ext" "%USERPROFILE%\My Documents. Just make sure you create a Docs folder in the $OEM$\install folder of your UWXPCD

I do agree, one check might be worth looking into though, if RunOnceEx exists, don't write guirunonce entries in winnt.sif.. Possible?

This is kinda a wishlist request, you add guirunonce entries to winnt.sif but i actually use runonceex so end up deleting the winnt.sif entries, is there a way to automate that process or not add them at all if runonce is used..? just a thought.

Contact Microsoft, they have been issuing replacement cd keys but you need to prove you made the original purchase

Don't rush to fix an error that may not be there, i have used 5048 and the OEM folder is there, it's in M2 folder, when you run slipstream it places the oem folder into the root with DPacks and Bin subfolder. I deleted my original UWXPCD root folder then slipstreamed.... worked for me. Just finished reburning a new Multiboot Cd so will test again soon

I have seen this many times, i would run all the adware/spyware and antivirus programs you can and hope that it's not one of those really nasty spyware programs that are almost impossible to remove without format c: reinstall OS. B)

I just slipstreamed 5048 ad got this message while it was processing, is it a bug.?

I hope you didn't take it as a critisism, it was not meant that way, it was just a factual report of my 1st 2 installs, however i was surprised it found and installed the audio component of the AC link modem/sound combo i didn't expect it to install either.

your right... i was running at 16 bit....

I checked again by uninstalling UA 1 and the icon is visible with the satellite ring around it, you can also see it on the all programs/IE shortcut but when i reinstall i get this Edit: Yes my video settings were at 16 bit....not 32 bit and now the black border has gone from computer management icon

I noticed that the IE icon on the quick launch bar has no transparent background, it's white or light colour. There is also a black aura around the compter icon in system properties also around the computer icon in computer management

Yep, just did a new slipstream and found the same thing, process appears to complete properly, but WatchDriver and SetDevice are not copied to the oem\bin folder, although the 7za file is...

Ok, having solved the D Packs in the root of C drive error (Sorry BTS, not your fault, mine ) I have now rebuilt the D packs with ver 504.6 method 2, multiboot cd, all went well, no errors in creating. Installed on HP Pavilion xt118 notebook with Radeon IGP 340M mobile video with Conexant Modem/Audio AC Link combo. - IGP video not recognised.. AC link audio detected and driver installed.. AC Link modem driver not installed. everything else installed, no errors... P4P800-se with Radeon 9250 AGP video, and Soundmax AD 1985, Yukon Nic etc... All detected and installed, no errors.. Now waiting for the next batch of XP installs... Thanks BTS, the Multiboot OEM setup also now works a treat..

Ok, downloaded and updated 5046, updated my clean SP2 source XP folders then checked my $oem$ folder... as i have not been changing anything in there i haven't checked the contents recently, so i was a little surprised to find DP, Bin and DPacks in the $1 folder next to my Install folder. it looks like 504 and 504.1 files were in there????. anyway that explains my Dpacks and bin folder in the root of c after installing. I'm creating a new install CD now so i will update you on the results... B)

Awesome... thanks. As soon as we get this setup thing resolved then i can get to testing the installs, i have access to all sorts of systems so it will get a good test.

Try LanNetScan from languard