Topic: driverpacks with unattended

Hello. I'm trying to setup unattended (unattended.sourceforge.net) with driverpacks. The Unattended part works well, I can boot and install windows from network. To integrate Drivepacks, I follow these instructions. The cd I'm using is original XP SP2 Corp. I integrate SP3 with nlite, then slipstream DP with DP Base. All packs and driverpack Base are latest versions as of now.
Installation starts ok, 9 archives with driverpacks unpack, and this is where the fun begins:
1) "dspdsblr.exe could not be found" - I unpack dpsfnshr.7z to i386/$oem$/$1 - passed
2) "setup.exe cannot be launched, because Normaliz.dll was not found" - I find normaliz.dll, put it into i386/$oem$/$$ - passed
3) "setup.exe cannot be launched, because iertutil.dll was not found"  - I find iertutil.dll from IE7, put it into i386/$oem$/$$ - "iertutil.dll Ordinal 685 could not be located". Search more, take iertutil.dll from IE8, put it into i386/$oem$/$$ - passed
4) now setup.exe launches and windows says there's not enough space on hdd (there's enough, same installer without DP installs just fine)

Greatly appreciate any pointers, except for bashing the head against the wall - already done.

update: here's the DP Base log

2010-11-06 22:40:32 : <INIT> DriverPacks BASE 10.06 initialized.
2010-11-06 22:40:32 : <INIT> Host environment: WIN_VISTA Service Pack 2 X86 on a 

X64 CPU.
2010-11-06 22:40:32 : <INIT> Created temporary working directory.
2010-11-06 22:40:32 : <INIT> Imported proxy settings from Internet Explorer.
2010-11-06 22:40:32 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 

platform.
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Chipset 1009!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack CPU 1005!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Graphics A 1009!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Graphics B 1009!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Graphics C 10091!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack LAN 1009!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Mass Storage 1010!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Sound A 1009!
2010-11-06 22:40:32 : <INIT> 	Detected DriverPack Sound B 1009!
2010-11-06 22:40:32 : <INIT> 	Could not detect any 3rd party DriverPacks for 

wnt5_x86-32.
2010-11-06 22:40:32 : <INIT> 	Finished scanning.
2010-11-06 22:40:32 : <INIT> Detected settings file 

"C:\Programs\DriverPacks\DPs_BASE.ini".
2010-11-06 22:40:32 : <INIT> Windows XP Professional -  Retail SP3 detected.
2010-11-06 22:40:32 : <INIT> wnt5_x86-32_disc is the selected installation 

platform .
2010-11-06 22:40:32 : <INIT> Imported settings from settings file.
2010-11-06 22:40:32 : <GUI>  Initialized GUI.
2010-11-06 22:40:32 : <GUI>  Created a list of all available language files.
2010-11-06 22:40:32 : <GUI>  Set the last used language, English, as the GUI 

language.
2010-11-06 22:40:55 : <GUI>  Refreshed UpdateChecker with success.
2010-11-06 22:41:30 : <GUI>  Changed Windows installation files OR export 

(depending on the installation platform) location to C:\Programs\win\sp3-dp-2.
2010-11-06 22:41:30 : <GUI>  Windows XP Professional -  Retail SP3 detected.
2010-11-06 22:41:30 : <GUI>  wnt5_x86-32_disc is the selected installation 

platform .
2010-11-06 22:42:57 : <GUI>  Exported settings to C:\Programs\DriverPacks\win-dp

-2.ini.
2010-11-06 22:43:02 : <GUI>  Saved settings!
2010-11-06 22:43:02 : <GUI>  Closed GUI.
2010-11-06 22:43:02 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2010-11-06 22:43:03 : <PREP> Removed all attributes from \I386.
2010-11-06 22:43:03 : <PREP> No previous DriverPacks installation found, Prep 

stage will be skipped
2010-11-06 22:43:08 : <SLIP> Extracted DriverPack MassStorage to a temporary 

working directory.
2010-11-06 22:43:08 : <SLIP> 

C:\Programs\DriverPacks\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2010-11-06 22:43:09 : <SLIP> Processing Mass Storage files now. This may take a 

minute.
2010-11-06 22:43:24 : <SLIP> Slipstreamed DriverPack MassStorage text mode driver 

files.
2010-11-06 22:43:24 : <SLIP> txtsetup.sif Backed-up Successfully
2010-11-06 22:43:24 : <SLIP> dosnet.inf Backed-up Successfully
2010-11-06 22:43:28 : <SLIP> Removed entries from \I386\txtsetup.sif that will be 

updated.
2010-11-06 22:43:29 : <SLIP> Removed entries from \I386\dosnet.inf that will be 

updated.
2010-11-06 22:43:51 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to 

support DP MassStorage text mode drivers.
2010-11-06 22:43:51 : <SLIP> Created necessary directory structure for method 2.
2010-11-06 22:43:51 : <SLIP> Copying files necessary for method 2.
2010-11-06 22:43:56 : <SLIP> Extracted additional files necessary for method 2.
2010-11-06 22:43:56 : <SLIP> expanded setup.ex_ to setuporg.exe
2010-11-06 22:43:56 : <SLIP> SETUP.EX_ Backed-up Successfully
2010-11-06 22:43:56 : <SLIP> Compressed setup.exe to SETUP.EX_.
2010-11-06 22:43:56 : <SLIP> Method 2 setup.ex_ installed
2010-11-06 22:43:56 : <SLIP> Created \I386\presetup.cmd file.
2010-11-06 22:43:56 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2010-11-06 22:43:56 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2010-11-06 22:43:56 : <SLIP> Copied DriverPack Chipset to \OEM.
2010-11-06 22:43:56 : <SLIP> Copied DriverPack CPU to \OEM.
2010-11-06 22:43:58 : <SLIP> Copied DriverPack Graphics A to \OEM.
2010-11-06 22:44:03 : <SLIP> Copied DriverPack Graphics B to \OEM.
2010-11-06 22:44:06 : <SLIP> Copied DriverPack Graphics C to \OEM.
2010-11-06 22:44:08 : <SLIP> Copied DriverPack LAN to \OEM.
2010-11-06 22:44:08 : <SLIP> Copied DriverPack Mass Storage to \OEM.
2010-11-06 22:44:13 : <SLIP> Copied DriverPack Sound A to \OEM.
2010-11-06 22:44:16 : <SLIP> Copied DriverPack Sound B to \OEM.
2010-11-06 22:44:16 : <SLIP> Copied DriverPacks to \OEM.
2010-11-06 22:44:16 : <SLIP> Will not slipstream patches, Service Pack 3 was 

detected.
2010-11-06 22:44:16 : <SLIP> Updated \I386\winnt.sif to support method 2.
2010-11-06 22:44:16 : <SLIP> Updated DPsFnshr.ini to enable KTD for all 

DriverPacks.
2010-11-06 22:44:16 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2010-11-06 22:44:17 : <SLIP> DP_Install_Tool was copied successfully
2010-11-06 22:44:17 : <SLIP> Slipstream finished in 1 minutes and 15 seconds.
2010-11-06 22:44:19 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[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:\Programs\win\sp3-dp-2"
; 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		= "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		= "no"


; 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_MassStorage_textmode = "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel 

(only relevant when slipstreaming Graphics DriverPack)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl		= "CCP"
Nvidia_cpl	= "None"
2010-11-06 22:44:19 : <CLNP> Create a DPs_Base.log backup @ 

C:\Programs\DriverPacks\LogFiles\DPs_BASE_10-11-06_22-44.log
2010-11-06 22:44:19 : <CLNP> Program terminated.

Last edited by burn (2010-11-09 17:02:53)

Re: driverpacks with unattended

please see read before you post linked in all our signatures (and was in the popup you agreed to when you signed up)

most of your details and process were very clear and inclusive, almost a perfect score. However we are missing quite a few details that would be (or would have been) included in your DPs_BASE.log. Please tack that on to your post and not only will it be a perfect first post... but we might be able to give you a helpful answer. 

help us to help you, please.

Jeff

PS your link is a dead end. 404

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: driverpacks with unattended

I fixed my post.

Re: driverpacks with unattended

Um looks like DriverPacks BASE ran normally... that's good.

I belive your network install is based on winnt32.exe ... (although i could not access the instructions you linked to)

DriverPacks is designed to be run from CD/DVD useing setup.exe localy... and has known issues with winnt32 installs.

the only way DriverPacks was ever supported with network installs was with RogueSpears AutoImage. RS has retired and is now a linux guy. however his app is still available. RS made DriverPacks compatable with winnt32 installs... at least for RIS installations. the best i can do is to suggest that you use autoimage to integrate DriverPacks into your source. I know that it will work with RIS if you do that. Im not sure how compatable that is with what you are doing but it is the best support that i personally have to offer you. Based on you trying to integrate all the packs with your network install.

Some of our crazy sysprep guys have other methods of integrating the packs for network installs the "universal imaging" forum here may also prove useful and those crazy's may also have some insight tongue.

If I were you i would integrate Mass Storage textmode (Only the textmode drivers) and use the DriverPacks SAD (Stand Alone Drivers) method of updating the machine (post installation update or  what MS calls a "Software First" install method).

Please ask whatever you like somebody will certainly have been in your shoes in the past.

here is a link to AutoImage in case you decide to try that route http://www.doitrightconsulting.net/forum/
RogueSpear is an old and dear friend of the DriverPacks and AutoImage and DriverPacks BASE were designed to work together.

We will see what we can do to help but network installation is not "technically" supported big_smile

PS there is absolutely NO reason to EVER use KTD ALL... that is insane and it won't do whatever you were hoping it would. Not only that but the path length of the full set of DriverPacks far exceeds the max size of a single registry entry, IE even if it might do what you were hoping ... it won't work. KTD is good for modems and monitors and USB devices etc... simple devices that might be attached to a fully installed and working machine. big_smile Complicated devices like printers or sound cards or video cards that require a setup.exe to be run will never install with KTD (since the DriverPacks Finisher is not called, they will therefore not have their setup.exe called and of course will then fail to install properly)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: driverpacks with unattended

I fixed the link as well, you can try and see it. It's a second google link for 'unattended drivepacks'
Actually, I've already tried AutoImage. I think it has some problems with Vista, because when I select DP Base in Autoimage, it says "The Driverpacks BASE utility must be executed at least once before it can be used with AutoImage". Close Autoimage, run DPBase, close DPDase, run Autoimage - same answer.

Re: driverpacks with unattended

that makes sense... the last update to autoimage was long before Vista hit the scene. (that version of AutoIt is not vista compatable) either run it from XP or use Win7 with XP support. (Vista is garbage)

Or you could just use SAD (What i would do) big_smile.

I updated my last post read the PS

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: driverpacks with unattended

those instructions are over three years old (june of 2007) and not accurate or useful.
because it is based on false assumtions about KTD.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: driverpacks with unattended

OverFlow wrote:

those instructions are over three years old (june of 2007) and not accurate or useful.
because it is based on false assumtions about KTD.

yes, but it looks like they worked, and I couldn't find anything more relevant.

Last edited by burn (2010-11-10 01:56:06)

Re: driverpacks with unattended

nope... i am CERTAIN that it did not work, and for the reasons stated previously, add to that your personal experience you just shared with us. The reason no other related posts are found is BECAUSE it won't work wink. Any driver that has a pack INI entry will fail to install from a KTD folder. This means that at least 20 percent of the drivers will fail to install, and once the max registry entry size is exceeded... then NONE of the drivers will install (100% failure).

I took over the authoring / programming of DriverPacks BASE before that was written...
I know a little about how installing drivers works tongue

SAD will work for your needs with over 99% success.
Beat your head against the wall, or let me (or us) help... It's up to you big_smile.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: driverpacks with unattended

ok, I figured it out... most of it. The DP Base needs to be launched with administrator privileges at least once, then Autoimage can detect it. And the reason why windows says there's no space is because there's actually no space. Unattended uses a 4Gb fat32 partition as an intermediate step in installation, and apparently it is not enough for windows+DP. To fix that, one needs to adjust 'fdisk_cmds' parameter of [_meta] section in unattend.txt file.

fdisk_cmds = "fdisk /clear 1;fdisk /pri:100,100;fdisk /delete /pri:1;fdisk /pri:8000;fdisk /activate:1"

- that doubles the partition and allows windows to install successfully (at least, on a KVM machine).

Now, one last problem I have is that during installation on real hardware there was some problem with nvidia videocard, windows said the driver could not be installed and will be rolled back to previous version. Maybe I should've disabled nvidia control panel in DP.

I'd really like to be over with it already. How'd I use this SAD with network installation? Do I need to integrate network drivers, too?

Re: driverpacks with unattended

you are getting close now.

that nvidia problem was reported by another user you should be able to search our forum for that fix.

yes if you use SAD from a network location you will need the mass chipset and LAN drivers included with autoimage. if you can get autoimage to work then don't sweat the SAD method big_smile. Although SAD over the network will work great for updating a running machine if you are serviceing a unit big_smile. you may also find that it will take less total time to deploy by adding mass lan and chipset with AI, then calling SAD over the network for the remaining drivers, this would also avoid the 4 gig limit issue you fixed above (well done)

Check out the universal imageing forum  http://forum.driverpacks.net/viewforum.php?id=30  for some ideas about how to attack this issue there are several really good methods to choose from... the first one is very similar to your attempted KTD method BUT it calls the DriverPacks Finisher which makes a day and night difference for success. It also removes all the unneeded drivers from the machine after the deplyment big_smile. other posts explore SAD. SAD is also outlined in the FAQs.

if you have AutoImage working then you have the best solution for your needs in place... no need to over think it from there. I just tossed some other alternate options as an FYI in case you don't feel AI is the right fit for you.

No matter what you will need AutoImage to at least kick start your deployment.

Looking forward to seeing how this turns out...
Please let us know how you're progressing!
you may save many other people countless hours of work! big_smile

HINT: you wont need to reinstall driverpacks (except mass storage) after you get this working. You can simply substitute packs to update them big_smile.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: driverpacks with unattended

ok, it took me several days to find that I should simply ignore the error back then. I forgot to leave the feedback, and remembered just now. The system works flawlessly, for anyone interested. Follow instructions in the maillist, adjust the partition size as I did and you'll get get Unattended + DriverPacks.