Thanks so much for your help and quick response.  I'll give it a shot later today.

On a side note... I've been trying to fill in some holes missing for drivers on my work side of things when it comes to driverpacks.  I've got a few drivers that are not standard, run of the mill for Intel chipset so I've made a 3rd party driverpack for them and it installs and registers fine. smile

My only question is how would I go about adding the SOFTWARE to go with the drivers?  Here is an example - http://support.dell.com/support/downloa … eid=438093

The SOL driver I can create a 3rd party package for and install the driver, but the intel software isn't coming across.  I'm sure it is something to do with my folder structure.  I could do a silent install of the software with a /S command (which does work).  I'd just like to know how to build it into the base driverpack option so I don't need to do more work smile  I know it's possible based off of the audio and video packages that are on the site.  Just curious smile

I've been following this guide which has served me well - http://forum.driverpacks.net/viewtopic.php?id=5

What am I missing?

Question for you smile

Could you point me to the right direction on how to make the script automated?  I'd like to add this to my Windows 7 image and have it auto run after first boot without having to hit enter to confirm the request to begin.

Thanks.

Just wanted to say that this works great! smile

Out of curiosity... any suggestions on how to incorporate this into a Windows XP HII (hardware independent image).  I'd love for this .cmd to run after sysprep on first login.   Any ideas where to stick the files so that after the command is run and the files extract the base .7z files are deleted?

I think I have a simplified process for running Sysprep with Driverpacks now smile

So simple in fact that even a non techie could do it!  I'll post more later, but for now I'm doing a test to see if everything is working as intended.

Let me rephrase that a bit overflow... smile

I'm a newb when it comes to integrating both systems together.


Here is my standard procedure for my DVD installs of XP

XP PRO + SP3 Slipstreamed
1 Piece Update Pack (for updates beyond SP3)
Make .ISO
Add my OEM Scan project to the source
Make .ISO
Add Driverpacks to the Source
Add modified WINNT.SIF and Custom WINNTBBU.DLL theme
Make .ISO

Test the living h*ll outta it smile

The reason I make so many .iso's is so I can easily go back and change something if I want.  If I go from SP3 base to Driverpacks and miss a step somewhere it's a pain in the @#$ to fix. =/

I've done sysprep before and had no problems.  If I had a choice, I'd make a base HII of XP + SP3 + Updates and include only Mass Storage and LAN drivers in the base image.  Once it loads XP after the mini setup I'd run Method 2 of the Driverpacks, but I still haven't found a way to do this.

I'm also wanting to run oemscan via the runonce command as well.  This is because I want to sysprep an HII for systems that come in the door for repair, but don't use VLK's.

I know I'm on the right path, and I know method 2 can be used for after sysprep..... but with the current guide it includes Method 1 which is a bit less than friendly.

=/

I guess I would consider myself inexpierenced when it comes to sysprep I suppose, perhaps this is 1/2 my problem.

I've done sysprep for years, I've done driverpacks for years, but I've never combined them.

If Detard or someone else can point me in the right direction it would be greatly apprecated.  Perhaps we need a wiki of some sorts?

Same thing can be said for the Windows Vista / 7 Driverpacks.

If we can just get a nice quick and dirty how to for the new DP 8.X it would be amazing.  Glad to know I'm not the only one!

Let mek now how I can help.

Thanks in advance!

Nope no dice.... close but no dice.

I need some more help on this topic please.


I plan on using Fog to do my imaging (although any imaging software would work... but bartPE is out of the question)


For Windows XP I'll be using the Multi Core HAL because I no longer have any single core systems.

What I want to do is build a Windows XP Universial Hardware Independent Image, but I need some help getting off the ground if you don't mind.


I know that the last few posts here were helpful, but I don't use offline sysprep for several reasons.

What I want to do is this.

1.  Run Sysprep with just the mass storage drivers.

I know that using the sysprep driver scanner, it can definably help - http://www.vernalex.com/tools/spdrvscn/index.shtml  Does anyone have experience using this?

2.  After the sysprep runs I want to use the Driverpacks to run method 2 using the DP_Install_Tool.cmd which shouldn't be too hard, but i've run into a few snags

Do I need to extract all the drivers to c:/D first?  Can I leave them compressed as .7z?  I know that in your guides you mentioned previously to have them already extracted so they get auto detected with Sysprep runs.

Just looking for some clarification please.  i'd love to write and updated guide on this for people that come after me.

thankx

Ok I need to ask the mass brain a quick question here if you don't mind smile

I know that the guide written here is a bit oudated, and I have read though all 8 pages about how to do this... and I'm 95% of the way there.


I know it was mentioned that you can do a runonce command to pull the dp_install_tool.cmd and use method 2 for installing all the needed drivers.  This seems like the best method for what I am wanting to do, but at the same time I do not see (or didn't see) any guide or walkthough for doing this.

I know I need to add the mass storage drivers to my sysprep.inf, and that's not a problem.

I was just looking for confirmation that what I am wanting to do is possible without extracting all the .7z files to c:\D and pointing the dpfinisher to it like previously mentioned in the 1st post.

smile

Thanks for your help.

**edit**

I digress... I think I was up too late last night and missed something.  Hold off on your "wtf read the topic" replies.

thx.

Hey overflow thanks for getting back to me.   Yea it was a 7b error.  I decided to figure it was something I did so I re-packaged my XP disk from scratch using the latest drivers and decided not to use the manual DPINST tool and it worked flawlessly.

Go figure smile

All is fixed smile  Thanks!

So I picked up a discount HP laptop during Black Friday and I'm looking to install Windows XP on it.  Default install of XP does not work and blue screens.  Slipstreamed SP3 + Driver Packs mass storage installs xp but blue screens on first boot.

I'm also not able to change any of the HDD settings in the bios (ACHI vs. SATA vs. Legacy ).

I'll have a .dump file of the blue screen when I get home, but here is a Find HWID output for the system

=========== 
PCI Devices 
=========== 
PCI\VEN_8086&DEV_2919&SUBSYS_360B103C&REV_03\3&33FD14CA&0&F8: Intel(R) ICH9M LPC Interface Controller - 2919
PCI\VEN_8086&DEV_2938&SUBSYS_360B103C&REV_03\3&33FD14CA&0&D1: Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2A42&SUBSYS_360B103C&REV_09\3&33FD14CA&0&10: Mobile Intel(R) 4 Series Express Chipset Family
PCI\VEN_8086&DEV_2929&SUBSYS_360B103C&REV_03\3&33FD14CA&0&FA: Standard AHCI 1.0 Serial ATA Controller
PCI\VEN_8086&DEV_2939&SUBSYS_360B103C&REV_03\3&33FD14CA&0&D2: Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_2A43&SUBSYS_360B103C&REV_09\3&33FD14CA&0&11: Mobile Intel(R) 4 Series Express Chipset Family
PCI\VEN_8086&DEV_2930&SUBSYS_360B103C&REV_03\3&33FD14CA&0&FB: Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_293A&SUBSYS_360B103C&REV_03\3&33FD14CA&0&EF: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_2932&SUBSYS_360B103C&REV_03\3&33FD14CA&0&FE: Intel(R) ICH9 Family Thermal Subsystem - 2932
PCI\VEN_8086&DEV_293C&SUBSYS_360B103C&REV_03\3&33FD14CA&0&D7: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_2934&SUBSYS_360B103C&REV_03\3&33FD14CA&0&E8: Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_293E&SUBSYS_360B103C&REV_03\3&33FD14CA&0&D8: High Definition Audio Controller
PCI\VEN_10EC&DEV_8136&SUBSYS_360B103C&REV_02\01000000FFFF000000: Realtek RTL8102E/RTL8103E Family PCI-E Fast Ethernet NIC (NDIS 6.20)
PCI\VEN_8086&DEV_2935&SUBSYS_360B103C&REV_03\3&33FD14CA&0&E9: Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2940&SUBSYS_360B103C&REV_03\3&33FD14CA&0&E0: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_168C&DEV_002B&SUBSYS_303F103C&REV_01\001517FFFF24141200: Atheros AR9285 802.11b/g WiFi Adapter
PCI\VEN_8086&DEV_2936&SUBSYS_360B103C&REV_03\3&33FD14CA&0&EA: Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2942&SUBSYS_360B103C&REV_03\3&33FD14CA&0&E1: Intel(R) ICH9 Family PCI Express Root Port 2 - 2942
PCI\VEN_8086&DEV_2448&SUBSYS_360B103C&REV_93\3&33FD14CA&0&F0: Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_2937&SUBSYS_360B103C&REV_03\3&33FD14CA&0&D0: Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2A40&SUBSYS_360B103C&REV_09\3&33FD14CA&0&00: Mobile Intel(R) 4 Series Chipset Processor to DRAM Controller - 2A40
21 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\VID_090C&PID_1000\A500000000025553                      : USB Mass Storage Device
USBSTOR\DISK&VEN_CORSAIR&PROD_FLASH_VOYAGER&REV_1100\A500000000025553&0: Corsair Flash Voyager USB Device
USB\ROOT_HUB\4&1467AF13&0                                   : USB Root Hub
USB\ROOT_HUB\4&2358AA65&0                                   : USB Root Hub
USB\ROOT_HUB\4&25ECDD44&0                                   : USB Root Hub
USB\ROOT_HUB\4&2B1D3536&0                                   : USB Root Hub
USB\ROOT_HUB\4&6EC8CD3&0                                    : USB Root Hub
USB\ROOT_HUB\4&DE961F2&0                                    : USB Root Hub
USB\ROOT_HUB20\4&1B239DB7&0                                 : USB Root Hub
USB\ROOT_HUB20\4&2E635FD&0                                  : USB Root Hub
10 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\PNP0B00\4&5DE3981&0                                    : System CMOS/real time clock
ACPI\PNP0C02\4&5DE3981&0                                    : Motherboard resources
ACPI\PNP0C04\4&5DE3981&0                                    : Numeric data processor
ACPI\PNP0C09\4&5DE3981&0                                    : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\ACPI0003\5&B6EFCB6&0                                   : Microsoft AC Adapter
ACPI\PNP0C0D\2&DABA3FF&1                                    : ACPI Lid
ACPI\FIXEDBUTTON\2&DABA3FF&1                                : ACPI Fixed Feature Button
ACPI\PNP0C0E\2&DABA3FF&1                                    : ACPI Sleep Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23_-_INTEL(R)_CELERON(R)_CPU__________900__@_2.20GHZ\_1: Intel(R) Celeron(R) CPU          900  @ 2.20GHz
ACPI\PNPA000\4&5D18F2DF&0                                   : AT34G6YQ IDE Controller
ACPI\SYN0158\4&5DE3981&0                                    : Synaptics PS/2 Port TouchPad
ACPI\THERMALZONE\TZS0                                       : ACPI Thermal Zone
ACPI\THERMALZONE\TZS1                                       : ACPI Thermal Zone
ACPI\INT0800\4&5DE3981&0                                    : Intel(R) 82802 Firmware Hub Device
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ACPI\PNP0000\4&5DE3981&0                                    : Programmable interrupt controller
ACPI\PNP0100\4&5DE3981&0                                    : System timer
ACPI\PNP0103\4&5DE3981&0                                    : High precision event timer
ROOT\ACPI_HAL\0000                                          : ACPI x86-based PC
ACPI\PNP0200\4&5DE3981&0                                    : Direct memory access controller
ACPI\PNP0303\4&5DE3981&0                                    : Standard PS/2 Keyboard
ACPI\PNP0A06\3&473F1A46&0                                   : Extended IO Bus
ACPI\PNP0A08\2&DABA3FF&1                                    : PCI bus
25 matching device(s) found.
 
============ 
 HDA Audio 
============ 
HDAUDIO\FUNC_02&VEN_14F1&DEV_5067&SUBSYS_103C360B&REV_1003\4&2EE99FA4&0&0002: HDA CX20583 Soft Modem
HDAUDIO\FUNC_01&VEN_14F1&DEV_5067&SUBSYS_103C360B&REV_1003\4&2EE99FA4&0&0001: High Definition Audio Device
HDAUDIO\FUNC_01&VEN_8086&DEV_2802&SUBSYS_80860101&REV_1000\4&2EE99FA4&0&0201: High Definition Audio Device
3 matching device(s) found.
 
============ 
RAID Devices 
============ 
PCI\VEN_8086&DEV_2929&SUBSYS_360B103C&REV_03\3&33FD14CA&0&FA
    Name: Standard AHCI 1.0 Serial ATA Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_2929&SUBSYS_360B103C&REV_03
        PCI\VEN_8086&DEV_2929&SUBSYS_360B103C
        PCI\VEN_8086&DEV_2929&CC_010601
        PCI\VEN_8086&DEV_2929&CC_0106
    Compatible ID's:
        PCI\VEN_8086&DEV_2929&REV_03
        PCI\VEN_8086&DEV_2929
        PCI\VEN_8086&CC_010601
        PCI\VEN_8086&CC_0106
        PCI\VEN_8086
        PCI\CC_010601
        PCI\CC_0106
1 matching device(s) found.

Yes I know XP is old, yes I know it's only 32bit.... I don't need a question of why. wink

Any help in narrowing down what I can do to get the laptop running XP would be greatly appreciated.  I'm thinking the wrong HAL?  I used my custom Windows XP disk that uses DPINST to select which driver packs I want to extract into the install, and I selected none.... other than the Mass Storage which loaded on the pre-setup.

Thanks in advance!

--ssx--

p.s. this works great.

Please add it to the new versions

Can we pull this pack out of beta and make it official?

14

(0 replies, posted in Hardware)

Our new Optiplex 960's purchased for work have been having some strange issues with streaming audio / playing audio / etc. since we picked em up.  Turns out that we needed to disable the C State control on all of the systems to fix this.

I know there are a lot of dell shops out there, so thought I would pass the word onto you if you run into anything similar.

http://www.google.com/search?hl=en& … tnG=Search

^_^

I can vouch that the 745/755/760 series work with the DP_sound

I guess you answered my question, but you also kinda agreed with me on this one tongue

17

(15 replies, posted in News)

I totally agree on this one as far as Windows 7 support growing and XP support dwindling.   Any chance we can see some additional features in the dp_base.exe ?  Such as manual selection of which drivers to install (version 2)

Any chance we can get an updated revision on this project?  I really really like it... just wish that the files weren't limited to 8 characters.  Even better, could this be added to the DP_Base.exe as a function you can enable in the settings?

Being able to do a blanket install of all drivers is nice, but on some hardware you might only want the Lan / Wlan / Sound / etc.

Also is there a way to hide the dos window on the decompression and use the default (extracting 1 of 4) window.

Thanks smart!  I'll have an update for you by tomorrow.

I'm also getting this.... http://forum.driverpacks.net/viewtopic.php?id=3543

ideas?

21

(1 replies, posted in Software)

I've been tooling around with DriverUpdater-v0.3.5 and it's working great, I just had 2 quick questions



#1.  After selecting the drivers I want to extract I get this window.  Is this normal?  Can I hide it?

http://img6.imageshack.us/img6/5928/14128252sq4.jpg


#2.  After that window I get this.  I assume it's because the application has the ability to install after setup... and can not find the .exe    Just wanted to make sure though.

http://img5.imageshack.us/img5/7540/56385942vn5.jpg

Any ideas?

Thanks!

Any ideas what I can do to help on this?

Thanks RS!

I'll build a new windows disk and give this a shot on Monday.

--ssx--

Sata mode is needed for XP from what I understand.... at least that is the case with our HII using Altiris R-Deploy.

I noticed this as well.... kinda annoyin.