Ghostrider

If it's any help i get 1ms to router, 58ms to ISP and 106ms to google and i was downloading at around 700 kb's via shareaza at the time.

I agree, i use this to install in library's and once you are happy with the settings you can export them and import on a new install, cutting down time on new computer installs. get at http://www.fortres.com/

Thanks... eagerly awaiting the release date...

I second and third that.. :-D. i have a question though, version 2.5 has an update facility, does that just update the icons in the file or does it replace the file itself, say after a critical update from MS, i ask for reasons of security, no point replacing new files with older version...

Are you using a M/Board with a SIS chipset. i have come across some boards that will not shut off if power management is enabled in the bios. turn it off and the computer should power off

I have working partial unnattended XP OEM, Retail and Corp installs which are slipstreamed, then I use xpinstall to install apps, hotfixes etc and then runonceex for final apps, batch and hotfix installs. part of this final phase i use a batch cmd to ask if oem files are to be installed and if so by whom and on what date, however i cannot think how i can add a machine serial number to install into the oeminfo file during install. I have winnt.sif on the cd but i also have a floppy version i can input user info and cd key etc. Can anyone help me, my mind has gone blank..

source I'll remove all drivers that are natively supported by Win XP and see what the result is... EDIT: without result.... :'( I'm losing hope... ← Now we know why Ryan gave this project up.. .. Don't give up yet, it sounds like you might be on track with windows included drivers thingy..

Ok, i'm using XP home and pro, driverpack update 5026 method 2 and have checked with 2 clean XP sources and made multiboot and standalone versions, i still get a BSOD, if i don't use a winnt.sif floppy then i get txtsetup.oem cannot be found, if i use the floppy then i get the BSOD stop error chkdsk/f version...?!?!? EDIT: i also noticed that there is a $oem$ folder in the i386 folder...is that supposed to be there..? Also can you impliment a check for runonceex instead of creating a guirunonce entry by default, i use runonceex... also i already have a winnt.sif file with a msdosinitiated entry and the script created a 2nd entry that i have to delete. just some thoughts... thanks again for the great effort. Sorry to be blunt but i'm working and doing these checks at the same time

Ok, did another build, multiboot, copy files than BSOD chkdsk error no other info, did not even get to setup stage..!!

Ok, works now... i'll do a new build and test the install later.. thanks

Ok, this sent me crosseyed trying to find the problem... method 2 would not slipstream mass storage, the screen always displayed like this This is the RunMe.cmd entry referring to mass storage slipstreaming :DriverPack_MassStorage GOTO DP_M_%M% :DP_M_1 %INE% $OEM$\$1\DP\M ( ECHO _ DriverPack MassStorage NOT slipstreamed! DEL /Q txtsetup.oem GOTO Control_Panels ) START /WAIT sysfiles_M1.cmd START /WAIT slipstream_DPM.cmd IF EXIST $OEM$\$1\DP\G\%G%_Control_Panels.cm_ EXPAND -R $OEM$\$1\DP\G\%G%_Control_Panels.cm_ > nul DEL /Q $OEM$\$1\DP\G\%G%_Control_Panels.cm_ IF EXIST $OEM$\$1\DP\S\%S%_Control_Panels.cm_ EXPAND -R $OEM$\$1\DP\S\%S%_Control_Panels.cm_ > nul DEL /Q $OEM$\$1\DP\S\%S%_Control_Panels.cm_ GOTO DP_M_done :DP_M_2 %INE% OEM\%D%_%M%_V*.* ( ECHO _ DriverPack MassStorage NOT slipstreamed! DEL /Q txtsetup.oem GOTO Control_Panels ) ECHO COLOR FC >>extract.cmd ECHO OEM\bin\7za.exe x -y -bd OEM\DriverPack_MassStorage_V*.7z -aoa -o$OEM$\$1 >>extract.cmd ECHO EXIT >>extract.cmd START /WAIT extract.cmd DEL /Q extract.cmd START /WAIT CABfiles_DPM.cmd START /WAIT slipstream_DPM.cmd RD /S /Q $OEM$\$1\DP GOTO DP_M_done :DP_M_done DEL /Q I386\3w*.??_ I386\SIWinAcc.sy_ I386\aaatimeo.sy_ I386\bb-run.sy_ I386\DontGo.sy_ I386\amdeide.sy_ I386\videbus.sy_ I386\hptpro.sy_ ECHO. ECHO _ DriverPack MassStorage slipstreamed... GOTO Control_Panels The blue bit is where the trouble is, the script ignores the variable thinking the file is not there so therefore does not slipstream, i replaced the text as below and it slipstreams.... now i have to create a cd to test... :DriverPack_MassStorage GOTO DP_M_%M% :DP_M_1 %INE% $OEM$\$1\DP\M ( ECHO _ DriverPack MassStorage NOT slipstreamed! DEL /Q txtsetup.oem GOTO Control_Panels ) START /WAIT sysfiles_M1.cmd START /WAIT slipstream_DPM.cmd IF EXIST $OEM$\$1\DP\G\%G%_Control_Panels.cm_ EXPAND -R $OEM$\$1\DP\G\%G%_Control_Panels.cm_ > nul DEL /Q $OEM$\$1\DP\G\%G%_Control_Panels.cm_ IF EXIST $OEM$\$1\DP\S\%S%_Control_Panels.cm_ EXPAND -R $OEM$\$1\DP\S\%S%_Control_Panels.cm_ > nul DEL /Q $OEM$\$1\DP\S\%S%_Control_Panels.cm_ GOTO DP_M_done :DP_M_2 %INE% OEM\DriverPack_MassStorage_V*.7z ( ECHO _ DriverPack MassStorage NOT slipstreamed! DEL /Q txtsetup.oem GOTO Control_Panels ) ECHO COLOR FC >>extract.cmd ECHO OEM\bin\7za.exe x -y -bd OEM\DriverPack_MassStorage_V*.7z -aoa -o$OEM$\$1 >>extract.cmd ECHO EXIT >>extract.cmd START /WAIT extract.cmd DEL /Q extract.cmd START /WAIT CABfiles_DPM.cmd START /WAIT slipstream_DPM.cmd RD /S /Q $OEM$\$1\DP GOTO DP_M_done :DP_M_done DEL /Q I386\3w*.??_ I386\SIWinAcc.sy_ I386\aaatimeo.sy_ I386\bb-run.sy_ I386\DontGo.sy_ I386\amdeide.sy_ I386\videbus.sy_ I386\hptpro.sy_ ECHO. ECHO _ DriverPack MassStorage slipstreamed... GOTO Control_Panels

I got that too, but i inadvertantly re-applied the driverpack install to a folder i had already applied it to. i started with a fresh XP source, slipstreamed SP2, copied my $oem$ folder then applied the driverpacks, worked Ok then.. !@><!<!<?? Still didn't install mass storage though, i think it must still be disabled in the cmd files somewhere, i should look..

I'm in a corporate environment so everything has to point to our name and be editable in some way or can't use it.. thanks.!! P.S Downloaded and attempted to integrate all driverpacks via method 2... mass storage does not integrate...

This is what i get... i want to be able to edit the blue bar and the look of the message if it'spossible but i can't find the file or i have already and resource hacker will not load it..

I already have a custom setup, that wasn't what i was referring to, i was under the impression that nircmd was what showed the 'Please Wait updates in background" or words to that effect, i wanted to know how to change that box..

I don't completely understand what you're saying... What message bar heading? ← Sorry, when the computer 1st starts to run in gui mode a box appears saying please wait etc, i want to change this, the text layout and the heading i would like to change from ilo (i think it is) to our corporate name

Is there a way to access the file to change to message bar heading, i tried resource hacker but it says it's a non standard format and res edit just crashes.

Great Thanks...

There was a mention Here about potential problems with older SIS chipsets, although the file actually fails to copy during text install, it maybe just a corrupt file, i'll test and let you know

Is there an interim fix for the SISIDE.SYS error when using the mass storage driverpack on a SIS chipset M/B, i unfortunartly keep falling foul of this with older ECS based MB's and some laptop boards too

...with my alternative method you will only one $OEM$ folder thus it is very easy to maintain. I saw your version, not a bad way to go, i have to use CD's at the moment so method 2 is the easiest with the space i have..

I find method 2 best for that, just change the relevant compressed file, BartPe has a different method of integration see other post. in the multiboot environ' there is a folder for each install O/S so you have to move drivers from the i386 folder to the folder above i386 in each install i found that ryans pack did not work in the multiboot disks, something to do with the changes in txtsetup.sif

if you have lots of room then 1 is best, but if like me you are trying to fit 2 OS's on one CD then 2 is best

in your example you need to copy or move the files from the i386 to the professional folder and up one folder in all the other multiboot cd folders..

Version 2.5 has an installer with updater so i want to use it, it can also be uninstalled if required, the older manual way you can't... but thanks for the reply anyway