Driver Packs

[heppers]

I use the powerpacker and it should b good, but it doesn't appear to integrate BTS Driverpacks.

here is my DP Base ini file:


[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "C:\Temp\xpsp2"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "RunOnceEx"


; you should only add this section if you've set [Settings]\finishMethod to "RunOnceEx"
[RunOnceExSettings]
; custom/default, if not specified: default
startID = "default"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "all"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "yes"
DP_CPU = "yes"
DP_Graphics_A = "yes"
DP_Graphics_B = "yes"
DP_Graphics_C = "yes"
DP_LAN = "yes"
DP_MassStorage = "yes"
DP_Sound_A = "yes"
DP_Sound_B = "yes"
DP_WLAN = "yes"
DP_MassStorage_textmode = "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl = "CCC"



Thanks

[Siginet]

I haven't used the latest DP Base yet with PowerPacker. I will run a test today though and see if I get any issues. What was your problem? Did you get any errors whatsoever?

[heppers]

No, no errors, just the Win XP directory didn't really change in overall size, i assume if all DP's have integrated fully the overall size will be a good 264MB larger.

[ProfessorCPU]

The xp directory shouldn't change much in size whatsoever because the OEM dir is moved to the root of your multiboot disc. ;)

[heppers]

The xp directory shouldn't change much in size whatsoever because the OEM dir is moved to the root of your multiboot disc. ;)

Yes but surely the folder size should increase by the 250ish Meg that are all the driverpacks, and the driver pack files should be located somewhere in the folders?

[dwschoon]

I am also having trouble with the driverpacks. Here is my ini file. So far Ive been extremely impressed with this softwar anyway though. Is there any downside to using the dp_base to integrate the drivers before using powerpacker?


[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "D:\Slipstreamed Windows\XPDELL\Working"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "all"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl = "CCC"

[dwschoon]

Ive done some experimenting with different configurations. Ive found that if i use the dp_base to integrate the driverpacks into the directory before using powerpacker, powerpacker will integrate 2 copies of the driverpacks into the destination directory. One copy is in an OEM directory in the root of the destination directory. The other is in an OEM directory under destination\root\packname\$OEM$\. This occurs when either driverpacks or no driverpacks is selected in powerpacker. If i dont use the dp_base to integrate the driverpacks first, no driverpacks are integrated with powerpacker with either the driverpacks or no driverpacks setting.

[Siginet]

That would be caused by using 2 different methods. PowerPacker will only integrate the driverpacks using method 2.

What file are you using for your settings file? Are you creating a custom settings file or using the main settins file that the DP_Base automatically creates? Because you must create a custom settings file.

[dwschoon]

Here is the ini that Powerpacker uses.


[InputOutput]
XPSource=D:\Slipstreamed Windows\XPVLK\Working Tiny
XPDestination=D:\Slipstreamed Windows\PowerPacker

[Exclusions]

[Extra Files]
ExtraPackDest=
ExtraRootDest=
ExtraPack=N
ExtraRoot=N

[Custom Options]
FileToRun=
RunParams=
Tri-Pack=N
PackNameOn=Y
PackName=VLK1
BootEntryOption=VLK XP WITH PROGRAMS & DRIVERS

[Unattended]
Winnt.sif=D:\Slipstreamed Windows\XPVLK\Working Tiny\I386
$OEM$=D:\Slipstreamed Windows\XPVLK\Working Tiny
Unattend=X

[DriverPacks]
DPSource=D:\Slipstreamed Windows\Addons\Driverpacks\DPs_Base.exe
DPSettings=D:\Slipstreamed Windows\Addons\Driverpacks\Settings\3rdPartyYes.in i
DriverPack=P

[WinXPVersion]
XPVersion=P

[WinXPEdition]
XPEdition=C

[Win2k3Version]
2k3Version=

[Boot Entry]


Here is the Driverpack ini.


[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "D:\Slipstreamed Windows\XPVLK\Working TINY"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "yes"
DP_CPU = "yes"
DP_Graphics_A = "yes"
DP_Graphics_B = "yes"
DP_Graphics_C = "yes"
DP_LAN = "yes"
DP_MassStorage = "yes"
DP_Sound_A = "yes"
DP_Sound_B = "yes"
DP_WLAN = "yes"
DPs_3rd_party = "yes"
DP_MassStorage_textmode = "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl = "CCC"


The source directory is about 370mb, but the destination directory ends up being 733mb.

[Siginet]

PowerPacker does not add Drivers to the $OEM$ folder whatsoever.

I don't have the code in front of me now... but I think your error is here:
$OEM$=D:\Slipstreamed Windows\XPVLK\Working Tiny

It should be:
$OEM$=D:\Slipstreamed Windows\XPVLK\Working Tiny\$OEM$


The way you have it your entire disk gets copied to the destination root twice. Once normally and once everything is copied into $OEM$ (Including I386).

I hope this clears things up for you.

[dwschoon]

PowerPacker does not add Drivers to the $OEM$ folder whatsoever.

I don't have the code in front of me now... but I think your error is here:
$OEM$=D:\Slipstreamed Windows\XPVLK\Working Tiny

It should be:
$OEM$=D:\Slipstreamed Windows\XPVLK\Working Tiny\$OEM$


The way you have it your entire disk gets copied to the destination root twice. Once normally and once everything is copied into $OEM$ (Including I386).

I hope this clears things up for you.

Thanks for that. That cleared some things since this install doesnt even have a $OEM$ directory in it. I removed that option and that reduced the size. It still doesnt incorporate any driverpacks though. Also, for some reason any cd i make gives me a BSOD when setup gets to the "Starting Windows" point. I dont know if it is because of the lack of text mode drivers, but i have tried several cd's on 3 different computers. Every windows version on every cd gives the same error.
SESSION3_INITIALIZATION_FAILED
Stop: 0x0000006F

[Siginet]

I don't know why you would be having any issues.

so you do not have an "OEM" folder at the root of your multiboot disk with the DriverPacks in it? You will not have an "OEM" folder in ROOT\PackName.

Do you see the DPs_Base gui log pop up during the powerpack process?

The DPs_Base will create a "$OEM$" directory at ROOT\PackName as well if you use the RunOnceEx feature... but it only creates a cmdlines.txt and an exe file.

[dwschoon]

No i dont get an OEM directory in the root of the disc. Ive never seen the dp_base log popup with powerpacker. I do get an $OEM$ directory under root\packname, but it is empty. I uploaded a screenshot of the directory structure. I used the ini files posted above, with the exception that i removed the grab $OEM$ directory option.
http://img373.imageshack.us/img373/9098/powerpackerlg4.jpg

[Siginet]

hmmm... try recreating your custom settings file with the dp base. And maybe even place the DP base in a directory with no spaces before you create the settings file.

[dwschoon]

Thanks for the reply. I renamed the folder "Slipstreamed Windows" to "Slipstream" and that fixed the driverpacks issue. I still get the BSOD however. I managed to get one good iso once when i opened a new ini with powerpacker and slected every option(including the ones that were defaulted). This only worked once though, and every other install gave me that same BSOD. Ive tried 2 different computers, plus running the iso in Virtual Server on my main machine. I got the same results with all 3. Is there some bug that doesnt like my configuration? Ive tried with and without driverpacks, unnattended, $OEM$, etc. I even tried the tri-pack option and got the same results. Ive even tried these options on the files of an untouched windows cd, so I know it isnt anything i do before packing. Plus if i create a regular iso with nlite on the files it works fine. It only breaks after I use powerpacker to pack it.

[Siginet]

PowerPacker would not be able to cause a bsod like that. Some hardware is difficult to use the driverpacks with. It's not very often but it does happen. PowerPacker does not edit any files which would cause what you explained... but bad media can cause this. When you use powerpacker it uses a special makeisofs.exe to find simular files to svae space on the disk. If you are using bad media it can cause an issue.

Have you tried making a powerpack disk without nlite or the driverpacks?

You may also have some bad memory in your computer. I have also seen some computers that don't let windows xp sp2 install very easily but they install sp1 or earlier just fine.

I'm not completley ruleing out powerpacker as the issue... but I am 95% positive it isn't the issue.

All powerpack does is copy the files to the correct place for your multiboot disk. Writes a boot menu and edits setupldr.bin so it can boot from it. Aside from that it let's you run the DriverPack Base in the middle of this process.

If it were an error caused by powerpacker it would most likley give you file copy errors durring txtsetup. BSODS are usually a sign of faulty hardware/media/ or memory (Which is hardware). at least that is what I have seen in my experiances.

I will however keep an eye on this issue and see what I can find out. I hope you keep trying and find the issue.

Please report here if you figure it out or if you get any more information.

[dwschoon]

Ive used nlited and non nlited disks as source. Ive used disks with and without sp2 and tried with and without the driverpacks. Ive even tried using an xp disk i have that doesnt have any hotfixes installed at all. I have tried each of these configurations on 2 different computers. I have also tried creating an iso and loading it in Virtual Server on the machine i built them with. I guess maybe my machine that is doing all the work could be corrupting it somehow, but other than that, I dont know what else to try. When I get home tonight, I will try creating some on my machine there and see what develops. I also put the powerpacker file in the same folder as the dp_base file. That wouldnt be a problem would it?

[dwschoon]

I think my problem may be solved. I discovered that after giving PowerPacker its own directory, it would work on everything except for a source that i had used nlite to remove some components. After i changed ini for nlite to not remove "Remote Installation Services (RIS)", the install worked after using PowerPacker to pack it. I will reply back if i find any more problems.

[Siginet]

I'm glad you found it. :) Let me know if that turns out not to be your issue.