Case closed. I've got an INF file that works for the e6410 NIC in BartPE. I tried to post it, bu tit is too long.
2 2010-12-28 04:12:28
Re: [REQ] Intel 82577LM (48 replies, posted in DriverPack LAN)
No response yet? I am not sure where to go from here. i have tried everything in thsi post and still am not able to get e6410 network drivers working in BartPE
3 2010-12-24 07:42:19
Re: [REQ] Intel 82577LM (48 replies, posted in DriverPack LAN)
I don't know what i could be doing wrong. i have the same issue not being able to get a dell E6410 NIC driver loaded. I followed the fix above, but it is not working for me.
After placing the PRO1000\Win32\NDIS5x driver in the pebuilder drivers\net folder, and overwriting the inf file with the RIS one, here's the output from BartPE "Load Network Support (DHCP/auto)"
BARTPE: Starting Network Support (client)
BARTPE: Detecting/installing drivers
Found Device: PCI\VEN_1180&DEV_E822&SUBSYS_040A1028&REV_03\4&DBAB9B0&0&01E2
No DriverNodes found for device.
Found Device: PCI\VEN_14E4&DEV_4353&SUBSYS_000E1028&REV_01\4&1D521A10&0&00E1
No DriverNodes found for device.
Found Device: PCI\VEN_8086&DEV_0046&SUBSYS_040A1028&REV_02\3&11583659&0&10
No DriverNodes found for device.
Found Device: PCI\VEN_8086&DEV_10EA&SUBSYS_040A1028&REV_05\3&11583659&0&C8
No DriverNodes found for device.
Found Device: PCI\VEN_8086&DEV_3B30&SUBSYS_040A1028&REV_05\3&11583659&0&FB
No DriverNodes found for device.
Found Device: PCI\VEN_8086&DEV_3B56&SUBSYS_040A1028&REV_05\3&11583659&0&D8
No DriverNodes found for device.
Found Device: USB\VID_0A5C&PID_5801&MI_00\7&1EB0F4E8&0&0000
No DriverNodes found for device.
Found Device: USB\VID_0A5C&PID_5801&MI_01\7&1EB0F4E8&0&0001
No DriverNodes found for device.
4 2010-12-24 03:59:40
Re: [SLVD][10.10] "The file jraid.sys could not be found", Textmode Setup (16 replies, posted in DriverPack Mass Storage)
Just paste it in the message? How ugly 
.
But you can consider this issue solved. I am not getting that message anymore after correctly creating the ISO. My problem is I only get into driver packs stuff every year or so and have to relearn everything. I'll have to write myself some notes this time. Thanks for your patience and quick responses.
5 2010-12-23 01:28:06
Re: [SLVD][10.10] "The file jraid.sys could not be found", Textmode Setup (16 replies, posted in DriverPack Mass Storage)
I was trying to learn how to upload files and attach them to posts here, but I don't see a way.
Anyway, it is looking like the problem is due to the iso creation. I will research more and get back to you here.
6 2010-12-22 09:56:40
Re: [SLVD][10.10] "The file jraid.sys could not be found", Textmode Setup (16 replies, posted in DriverPack Mass Storage)
I am following the tutorial at http://users.telenet.be/jtdoom/basetute/Eng_tut6b.htm and i didn't see anything about removing drivers. i am not using an OEM install, but a standard Win XP install with SP3 slip streamed into it "manually". I successfully used the same source files about a year ago.
Please clarify your suggestion about removing drivers. Uncheck everything, slipstream, then run again with everything checked? I have done this and the result is the same: "The file jraid.sys could not be found." jraid.sy_ is in the i386 dir, and there are several references to jraid.sys in txtsetup.sif.
The PC is a Dell Latitude E6410 laptop.
I worked through the build using fresh source and the result is the same.
7 2010-12-22 06:21:43
Re: [SLVD][10.10] "The file jraid.sys could not be found", Textmode Setup (16 replies, posted in DriverPack Mass Storage)
Hey, I am having this exact problem: 'The file jraid.sys could not be found." which is odd because Mulgie said a month ago this was fixed. I am using Base 10.06 and Mass Storage 10.11. I do see jraid.sy_ in the i386 dir of my source.
I reverted to Mass Storage 10.09, and now I get: "The file nvrd325.sys not found." But I see nvrd325.sy_ in i386.
8 2009-05-21 05:41:56
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
OverFlow wrote:
then why didn't it work? you tell me...
I already know why
because backup files existed in your supposedly clean source.
if it was a clean source then the backups would not exist...
if they did not exist they could not be used to restore...IE txtsetup.sif cant be restored if its backup is not found...
If the backup is not found that will throw an error in DriverPacks BASE too...
Base knows if it has previously been run on a source and expects to find its backups if it has.so i know you made changes to a source that you had previously run DriverPacks on
- it's THE ONLY WAY lines could be removed from txtsetup.sif by DriverPacks BASE
since restoring a backup is the only way BASE will remove lines from txtsetup then you could not have possably started with a clean source...
Since I know changes were made to your source after you ran base the first time then you absolutely have orphaned files in your source and probably more corruption yet to be discovered.clean source means copy from OEM MS CD and start CLEAN... you absolutely have not done this, I can tell just by the results you are getting.
Well, I *thought* I had started from a clean source. Thanks for explaining how those lines were removed.
9 2009-05-21 05:19:19
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
OverFlow wrote:
wen you run driverpacks a second time... which you did...
it restores backups of files it creates when it was run the first time...
it did not remove the lines it restored the backupsBECAUSE YOU DID NOT USE A CLEAN SOURCE
The very first time I ran it I *did* use a clean source.
10 2009-05-21 02:32:50
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
OverFlow wrote:
I already answered your question... "you will need to start over with a clean source."! you ignored me. lol
you can NOT make any changes to your source after DriverPacks. (running nLite a second time counts as making a change)
BASE Tutorial(DriverPacks then nLite then DriverPacks a sceond time is really really bad!)
I run DriverPacks on a copy of my source for just this reason
your source is really, really corrupted now... PLEASE start over with a clean source.
I think you will find if you start over and do nLite then autoimage you will be fine!
No I did not ignore you. I know you are a VERY IMPORTANT PERSON. I wouldn't do that. 
Sorry if I put you on the wrong track by saying I "forced the recreation of nLite files". No files existed before they were created.
I did start with a clean source and ran DriverPacks last. It didnt' work. Now you want me to do that again. Definition of insanity, right?
Since I needed to move forward, I tried what made sense to me -- save a copy of TXTSETUP.SIF before DriverPacks removed the nLite lines, and then put them back in after DriverPacks is done, before burning my ISO. Guess what? It worked perfectly.
Since you are a code contributor to DriverPacks, I thought you might know why DriverPacks is taking the nLite (inf but non-driver) lines out of TXTSETUP.SIF. I caught it red handed.
11 2009-05-20 04:35:26
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
OverFlow wrote:
no... it is not confilcting with the finisher... they are unrelated
(hint: remark the call to the finisher and i belive you still have the problem)
it may be they are not referenced in the copy files section...Nlite works fine if you only want to add drivers for a single (or a few select) machine like a personal reload disc. nLite does not have the sophistication to deal with the entire set of DriverPacks. Although this may work in certian instances you will find that it is not reliable.
Keep in mind I am now using nLite only for configuration settings, not drivers. I made a new ISO forcing the recreation of nLite config files nLite.inf, nLite.cmd, and nhelper.exe which control things like such as autologon etc. Immediately before creating the ISO, I ran DPs_Base.exe pointed to my source folder.
What I've found is that prior to running DPs_Base.exe there are nLite entries in TXTSETUP.SIF that are no longer there after Running DPs_Base.exe. What's up with that? And how can I correct this situation?
12 2009-05-19 10:22:48
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
So now with a DVD unattended installation, XP Setup at first hung for over 10 minutes at "Setup is starting Windows". The hardware is an hp dc7900 Ultra-Slim Desktop. I restarted and tried again and this time it is working. Go figure...
But when it gets ready to do nLite config stuff, it can't find nLite.inf & and nLite.cmd. Hmmmm what's that about? I'm wondering if it is conflicting with DriverPacks finisher.
13 2009-05-19 09:38:06
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
OverFlow wrote:
if you use DriverPacks dont add drivers with nlite - one or the other... both is bad...
If you have already added drivers to your source with nLite then you will need to start over with a clean source.
I know. I am not now adding drivers with nlite --only with DriverPacks
Driverpacks does not directly support network installs (or any install that uses winnt32.exe)
if you wish to use DriverPacks with a network type install, you will need to get RogueSpears AutoImage
AutoImage will correctly configure DriverPacks for a network install.
Thanks. I had forgotten that. I did this before about 8 months ago and now remember that my need for a network install was why I went with nLite for driver slipstreaming. And it worked --just feeding dp folders into nLite. That method is not working now though and am not sure why. However, on the newer hardware with a DVD player I should be able to perform a DVD install with all dp drivers, so I'll try that.
you can not use F6 drivers with an unnattended OEM install (per microsoft)
One or the other not both... (unnattended or F6 you have to choose)
Thanks, I thought that was probably it.
the intermediate and advanced sections of this guide will provide the general install answers you need...
http://unattended.msfn.org/unattended.xp/
In fact all but one of your questions is answered in that guide...
I've used it as a reference before but haven't yet found the section on using dp to slipstream drivers . Remember I successfully built unattended installations before, but am having trouble slip streaming drivers with DriverPacks.
14 2009-05-19 07:39:07
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
kickarse wrote:
Why don't you try and start with a clean slate, virgin XP disc? Then you can find where the issue is coming from easier.
I went back to just after I manually slip streamed in SP3 and before nLite, and I am still getting the BSOD (STOP:0x0000007B). Keep in mind I successfully fed this into nLite before -- meaning my installation was functional but without using DPsBase slip streaming.
15 2009-05-19 06:02:33
Re: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
OK I figured it out. There were remnants of nLite driver installations (path: i386\NLDRV) in two files, DOSNET.INF and HIVSFT.INF. Once I reverted those files to their pre-nLite state, all went normally. That is until "Setup is starting Windows" after the first reboot. After a few minutes I get a BSOD. I am wondering why when I hit F6 at the prompt I don't gat a prompt to manually install drivers in text mode.
16 2009-05-19 04:23:41
Topic: "Setup was unable to build the list of files to be copied" (14 replies, posted in BartPE - UBCD4Win - WinPE)
"The system cannot find the path specified." That's the XP Pro Setup message I am getting, and I need to learn why and fix it.
I've prepared my network WINNT.SIF file installation via nLite and slipstreamed all DriverPacks drivers immediately prior to running the final nLite build step as recommended here. I boot via USB BartPE installing my C-drive SATA driver at the F6 prompt. I verify the C-drive is fine and give it a quick NTFS format before I begin my network install using the command line <mapped drive_networkpath>\i386\winnt32.exe /unattend:winnt.sif /syspart:C: /copydir:IT /copydir:i386 /copydir:ServicePackFiles .
Any ideas what to look for to determine why files cannot be copied? Is the path info in TXTSETUP.SIF? I don't see any issues there.
17 2008-06-27 02:39:29
Re: Using DriverPacks "fake" setup and other unattended.txt->winnt.sif (7 replies, posted in Feedback and Support - DriverPacks Base)
As of yesterday, I've gotten nLite to work with DriverPacks drivers. One thing I am concerned about is that using all the DriverPacks drivers --I am not quite there yet as I am adding them in stages-- I might be up against that path length limit for drivers and not know it until I run my unattended install on some hardware. So, my plan is to add the DriverPacks drivers via DPs_Base to my nLite customizations (without adding drivers) using the slipstream method two to avoid this potential problem.
18 2008-06-26 07:06:59
Re: Using DriverPacks "fake" setup and other unattended.txt->winnt.sif (7 replies, posted in Feedback and Support - DriverPacks Base)
Thanks. As I said above, we dont' have RIS server at this time. I looked for documentation, but couldn't find anything. By "well documented" are you refering to forum messages? I am starting to read a few RIS related forum messages, but I am beginning to think maybe others have only done a DriverPacks network installation with RIS and I am on my own... After DP Base, my windows XP setup "CD" will no longer fit on a CD, so its got to be network based.
19 2008-06-25 02:49:57
Re: Using DriverPacks "fake" setup and other unattended.txt->winnt.sif (7 replies, posted in Feedback and Support - DriverPacks Base)
Unfortunately we don't have a RIS server yet. And we aren't really motivated to get one soon since our strategy is that technicians build all PCs in our IT area.
I have looked into...
RyanVM -- I don't see any advantage over using /integrate, only the downside that we would be relying on another level of coding for integration.
nLite -- I was working with it until I found that 1) using it to slipstream SP3 broke it and 2) their license is quite clear that it is not to be used for corporate installations.
DriverPacks -- I am trying to get the DP_Base integrator working on XP Pro after integrating SP3. It seems to be a bit temperamental --crashing on the larger driver packs but making it through on their cached copy the 2nd time through, so it eventually finishes. (Yes I have the latest version, 8.05.) Running a winnt32.exe /unattend:winnt.sif Windows XP Pro installation on the latest output gives me an an error message that Setup cannot copy the file setupORG.exe. Then if I escape that it says it cannot copy presetup.cmd. Then after otehr files are copied, the installation fails. What is wrong? My log and INI files are included below.
As for WPI -- I hadn't heard of it. By the name I expect it will be useful for my many post install tweaks, and I'll look into it.
Here is my latest complete DPs_Base.log
2008-06-24 08:28:43 : <INIT> DriverPacks BASE 8.05 initialized.
2008-06-24 08:28:43 : <INIT> Host environment: WIN_XP Service Pack 3 on X86 CPU.
2008-06-24 08:28:43 : <INIT> Created temporary working directory.
2008-06-24 08:28:43 : <INIT> Imported proxy settings from Internet Explorer.
2008-06-24 08:28:43 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2008-06-24 08:28:43 : <INIT> Detected DriverPack Chipset 8.03!
2008-06-24 08:28:43 : <INIT> Detected DriverPack CPU 8.04!
2008-06-24 08:28:43 : <INIT> Detected DriverPack Graphics A 8.04!
2008-06-24 08:28:43 : <INIT> Detected DriverPack Graphics B 8.04!
2008-06-24 08:28:43 : <INIT> Detected DriverPack Graphics C 8.04!
2008-06-24 08:28:43 : <INIT> Detected DriverPack LAN 8.05.3!
2008-06-24 08:28:43 : <INIT> Detected DriverPack MassStorage 8.05!
2008-06-24 08:28:43 : <INIT> Detected DriverPack Sound A 8.05!
2008-06-24 08:28:43 : <INIT> Detected DriverPack Sound B 8.05!
2008-06-24 08:28:43 : <INIT> Detected DriverPack WLAN 8.06!
2008-06-24 08:28:43 : <INIT> Could not detect any 3rd party DriverPacks.
2008-06-24 08:28:43 : <INIT> Finished scanning.
2008-06-24 08:28:43 : <INIT> Detected settings file "C:\Program Files\DPs_Base\DPs_BASE.ini".
2008-06-24 08:28:43 : <INIT> No OS could be detected.
2008-06-24 08:28:43 : <INIT> Imported settings from settings file.
2008-06-24 08:28:43 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2008-06-24 08:28:43 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2008-06-24 08:28:43 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2008-06-24 08:28:43 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2008-06-24 08:28:43 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2008-06-24 08:28:43 : <GUI> Initialized GUI.
2008-06-24 08:28:43 : <GUI> Created a list of all available language files.
2008-06-24 08:28:43 : <GUI> Set the last used language, English, as the GUI language.
2008-06-24 08:29:09 : <GUI> Changed Windows installation files OR export (depending on the installation platform) location to C:\WinXPPro_keyed_IntegratedSP3_DriverPacks.
2008-06-24 08:29:09 : <GUI> Windows XP Professional - Retail SP3 detected.
2008-06-24 08:29:09 : <GUI> wnt5_x86-32_disc is the selected installation platform .
2008-06-24 08:40:16 : <GUI> Refreshed UpdateChecker with success.
2008-06-24 08:40:21 : <GUI> Saved settings!
2008-06-24 08:40:21 : <GUI> Closed GUI.
2008-06-24 08:40:21 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m2.
2008-06-24 08:40:26 : <PREP> Removed all attributes from \I386.
2008-06-24 08:40:26 : <PREP> Removing old M1 files from \$OEM$\.
2008-06-24 08:40:56 : <PREP> Deleting method 1 related files.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\makePNF.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\devcon.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\DPsFnshr.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\DPsFnshr.ini.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\DSPdsblr.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\mute.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\pmtimer.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\*.ini.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\DP_Install_Tool.cmd.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\DPINST.exe.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1\DPInst.xml.
2008-06-24 08:40:56 : <PREP> Deleted \$OEM$\$1
2008-06-24 08:40:56 : <PREP> \I386\winnt.org was not found, \I386\winnt.sif was not restored.
2008-06-24 08:40:56 : <PREP> Neither txtsetup.org or dosnet.org was found. The removal of
2008-06-24 08:40:56 : <PREP> any Service Packs we may have added with Driverpacks was skipped
2008-06-24 08:40:56 : <PREP> Mass Storage Removal was also skipped because no I386\DRIVERPACK_MASSSTORAGE_WNT5_X86-32.INI was found
2008-06-24 08:40:57 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.
2008-06-24 08:40:57 : <PREP> Deleted \$OEM$
2008-06-24 08:40:57 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2008-06-24 08:41:10 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2008-06-24 08:41:10 : <SLIP> C:\Program Files\DPs_Base\QSC\wnt5_x86-32_uni_DP_MassStorage_805_textmode\DriverPack_MassStorage_wnt5_x86-32.ini
2008-06-24 08:41:11 : <SLIP> Processing the files now. This may take a minute.
2008-06-24 08:41:35 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2008-06-24 08:41:35 : <SLIP> txtsetup.sif Backed-up Successfully
2008-06-24 08:41:35 : <SLIP> dosnet.inf Backed-up Successfully
2008-06-24 08:41:40 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2008-06-24 08:41:41 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2008-06-24 08:42:24 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2008-06-24 08:42:24 : <SLIP> Created necessary directory structure for method 2.
2008-06-24 08:42:24 : <SLIP> Copying files necessary for method 2.
2008-06-24 08:42:24 : <SLIP> Extracted additional files necessary for method 2.
2008-06-24 08:42:24 : <SLIP> expanded setup.ex_ to setuporg.exe
2008-06-24 08:42:24 : <SLIP> SETUP.EX_ Backed-up Successfully
2008-06-24 08:42:25 : <SLIP> Compressed setup.exe to SETUP.EX_.
2008-06-24 08:42:25 : <SLIP> Method 2 setup.ex_ installed
2008-06-24 08:42:25 : <SLIP> Created \I386\presetup.cmd file.
2008-06-24 08:42:25 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2008-06-24 08:42:25 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2008-06-24 08:42:25 : <SLIP> Copied DriverPack Chipset to \OEM.
2008-06-24 08:42:25 : <SLIP> Copied DriverPack CPU to \OEM.
2008-06-24 08:42:36 : <SLIP> Copied DriverPack Graphics A to \OEM.
2008-06-24 08:42:41 : <SLIP> Copied DriverPack Graphics B to \OEM.
2008-06-24 08:42:46 : <SLIP> Copied DriverPack Graphics C to \OEM.
2008-06-24 08:42:46 : <SLIP> Copied DriverPack LAN to \OEM.
2008-06-24 08:42:46 : <SLIP> Copied DriverPack MassStorage to \OEM.
2008-06-24 08:42:50 : <SLIP> Copied DriverPack Sound A to \OEM.
2008-06-24 08:42:54 : <SLIP> Copied DriverPack Sound B to \OEM.
2008-06-24 08:42:55 : <SLIP> Copied DriverPack WLAN to \OEM.
2008-06-24 08:42:55 : <SLIP> Copied DriverPacks to \OEM.
2008-06-24 08:42:55 : <SLIP> Will not slipstream patches, Service Pack 3 was detected.
2008-06-24 08:42:55 : <SLIP> WINNT.SIF Backed-up Successfully
2008-06-24 08:42:55 : <SLIP> Updated \I386\winnt.sif to support method 2.
2008-06-24 08:42:55 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2008-06-24 08:42:55 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2008-06-24 08:42:56 : <SLIP> DP_Install_Tool was copied successfully
2008-06-24 08:42:56 : <SLIP> Slipstream finished in 2 minutes and 35 seconds.
2008-06-24 08:43:07 : <CLNP> Temporary working directory successfully deleted.
2008-06-24 08:43:07 : Program terminated.
DPs_Base.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 = "C:\WinXPPro_keyed_IntegratedSP3_DriverPacks"
; 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"
DP_MassStorage_textmode = "yes"
20 2008-06-24 07:30:52
Topic: Using DriverPacks "fake" setup and other unattended.txt->winnt.sif (7 replies, posted in Feedback and Support - DriverPacks Base)
I am new to DriverPacks, and see great potential for automating build upgrades. I am using DP_Base v8.05.
I would like to be able to use slipstream method 2, as it sounds more robust. My installation files are on the network. I am booting the PC to be built to the network using a BartPE network boot-disk. Then I run a winnt32.exe /unattend:winnt.sif setup. If I use slipstream method 1, it finishes, but does not install drivers. If I use method 2 I get errors that it can't find setupORG.exe and presetup.cmd.
With either slipstream method, what is the best way to integrate other unattended settings into my build? Thanks!
--DLP (really my initials!)