I believe that did the trick - Buslogic worked, and switching the controller to LSI is (so far) successful (its past where it would normally hang).
1 2009-05-15 03:15:01
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
2 2009-05-12 04:51:04
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Good morning.
9.05r1 works with BusLogic, but not LSI. Same issue as before (setup unable to find any disks).
Thanks,
Tim
3 2009-05-12 02:32:06
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
OverFlow wrote:
Off Topic...
Does it work if you select BusLogic... ? ? ?
May not be of much value considering newer posts, but yes - DP 9.03r1 does see a BusLogic device.
GOing to test the 9.05r1 next.
Thanks,
TIm
4 2009-05-09 13:41:12
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Ya know, I never even tried 
If I get to working on this this weekend (might sink time in on Ryan's packs), I'll test. Otherwise.. I'll let you know Monday.
Thanks
5 2009-05-09 00:48:23
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Sure - been sub'd all along.
The whole ESX vs VMWare has been a bit of a learning curve for us as well...
I'll continue to use pack 805 - works for everything we've come across... just thought it was strange the "newer" version failed while the older version succeeded.
Then again.. Visa, XP.. Office 2007, Office 2003.. MS is rife with examples of an old product working better ;-)
Thanks again, OverFlow - You guy and your team are doing good work
6 2009-05-08 01:55:55
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Good morning
903r1 generates the same error:
2009-05-07 07:54:40 : <INIT> DriverPacks BASE 8.12.4 initialized in API mode by AutoRIS v0.1.9.8.
2009-05-07 07:54:40 : <INIT> Host environment: WIN_2003 Service Pack 2 on X86 CPU.
2009-05-07 07:54:40 : <INIT> Created temporary working directory.
2009-05-07 07:54:40 : <INIT> Imported proxy settings from Internet Explorer.
2009-05-07 07:54:48 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-05-07 07:54:48 : <INIT> Detected DriverPack Chipset 902!
2009-05-07 07:54:48 : <INIT> Detected DriverPack CPU 804!
2009-05-07 07:54:48 : <INIT> Detected DriverPack Graphics A 8121!
2009-05-07 07:54:48 : <INIT> Detected DriverPack Graphics B 8121!
2009-05-07 07:54:48 : <INIT> Detected DriverPack Graphics C 8121!
2009-05-07 07:54:48 : <INIT> Detected DriverPack LAN 8121!
2009-05-07 07:54:48 : <INIT> Detected DriverPack MassStorage 903r1!
2009-05-07 07:54:48 : <INIT> Detected DriverPack Sound A 805!
2009-05-07 07:54:48 : <INIT> Detected DriverPack Sound B 805!
2009-05-07 07:54:48 : <INIT> Detected DriverPack WLAN 806!
2009-05-07 07:54:48 : <INIT> Detected 3rd Party DriverPack Dell630 08.08.12!
2009-05-07 07:54:48 : <INIT> Detected 3rd Party DriverPack IntelDP43TF 08.11.19!
2009-05-07 07:54:48 : <INIT> Detected 3rd Party DriverPack Modem 80327!
2009-05-07 07:54:48 : <INIT> Detected 3rd Party DriverPack toshiba2450 08.05.07!
2009-05-07 07:54:48 : <INIT> Finished scanning.
2009-05-07 07:54:48 : <INIT> Detected settings file "D:\DriverPack\DPs_BASE.ini".
2009-05-07 07:54:49 : <INIT> Windows XP Professional - Retail SP3 detected.
2009-05-07 07:54:49 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2009-05-07 07:54:49 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-05-07 07:54:49 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2009-05-07 07:54:49 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2009-05-07 07:54:49 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-05-07 07:54:49 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-05-07 07:54:49 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2009-05-07 07:54:49 : <INIT> Imported settings from settings file.
2009-05-07 07:54:49 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-05-07 07:54:49 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-05-07 07:54:49 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m2.
2009-05-07 07:54:49 : <PREP> Removed all attributes from \I386.
2009-05-07 07:54:49 : <PREP> No previous DriverPacks installation found, Prep stage will be skipped
2009-05-07 07:54:56 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2009-05-07 07:54:56 : <SLIP> D:\DriverPack\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2009-05-07 07:54:57 : <SLIP> Processing the files now. This may take a minute.
2009-05-07 07:55:17 : <SLIP> Slipstreamed DriverPack MassStorage text mode driver files.
2009-05-07 07:55:17 : <SLIP> txtsetup.sif Backed-up Successfully
2009-05-07 07:55:17 : <SLIP> dosnet.inf Backed-up Successfully
2009-05-07 07:55:23 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2009-05-07 07:55:24 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2009-05-07 07:56:02 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2009-05-07 07:56:02 : <SLIP> Created necessary directory structure for method 2.
2009-05-07 07:56:02 : <SLIP> Copying files necessary for method 2.
2009-05-07 07:56:02 : <SLIP> Extracted additional files necessary for method 2.
2009-05-07 07:56:02 : <SLIP> expanded setup.ex_ to setuporg.exe
2009-05-07 07:56:02 : <SLIP> SETUP.EX_ Backed-up Successfully
2009-05-07 07:56:02 : <SLIP> Compressed setup.exe to SETUP.EX_.
2009-05-07 07:56:02 : <SLIP> Method 2 setup.ex_ installed
2009-05-07 07:56:02 : <SLIP> Created \I386\presetup.cmd file.
2009-05-07 07:56:02 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2009-05-07 07:56:03 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2009-05-07 07:56:03 : <SLIP> Copied DriverPack Chipset to \OEM.
2009-05-07 07:56:03 : <SLIP> Copied DriverPack CPU to \OEM.
2009-05-07 07:56:07 : <SLIP> Copied DriverPack Graphics A to \OEM.
2009-05-07 07:56:14 : <SLIP> Copied DriverPack Graphics B to \OEM.
2009-05-07 07:56:24 : <SLIP> Copied DriverPack Graphics C to \OEM.
2009-05-07 07:56:25 : <SLIP> Copied DriverPack LAN to \OEM.
2009-05-07 07:56:26 : <SLIP> Copied DriverPack MassStorage to \OEM.
2009-05-07 07:56:27 : <SLIP> Copied DriverPack Sound A to \OEM.
2009-05-07 07:56:30 : <SLIP> Copied DriverPack Sound B to \OEM.
2009-05-07 07:56:31 : <SLIP> Copied DriverPack WLAN to \OEM.
2009-05-07 07:56:36 : <SLIP> Renamed DriverPack DP_Dell630_wnt5_x86-32_08.08.12.7z to DP_Dell6.7z in \OEM.
2009-05-07 07:56:36 : <SLIP> Renamed DriverPack DP_IntelDP43TF_wnt5_x86-32_08.11.19.7z to DP_Intel.7z in \OEM.
2009-05-07 07:56:36 : <SLIP> Renamed DriverPack DP_Modem_wnt5_x86-32_80327.7z to DP_Modem.7z in \OEM.
2009-05-07 07:56:36 : <SLIP> Renamed DriverPack DP_toshiba2450_wnt5_x86-32_08.05.07.7z to DP_toshi.7z in \OEM.
2009-05-07 07:56:36 : <SLIP> Copied DriverPacks to \OEM.
2009-05-07 07:56:36 : <SLIP> Will not slipstream patches, Service Pack 3 was detected.
2009-05-07 07:56:37 : <SLIP> Updated \I386\winnt.sif to support method 2.
2009-05-07 07:56:37 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2009-05-07 07:56:37 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2009-05-07 07:56:38 : <SLIP> DP_Install_Tool was copied successfully
2009-05-07 07:56:39 : <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:\AutoImageTmp"
; 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 = "no"
2009-05-07 07:56:39 : <CLNP> Create a DPs_Base.log backup @ D:\DriverPack\LogFiles\DPs_BASE_09-05-07_07-56.log
2009-05-07 07:56:39 : <CLNP> Program terminated.the "Code Tag fairy" visited this post too
7 2009-05-08 01:06:09
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Good morning
I've downloaded the 903r1 pack - will try it shortly.
As far as IDE vs SCSI - Note that I'm not using VMWare Server (the free server that runs on Windows), but the ESX server which (can) run on a bootable flash drive and is a plain jane text console. The string of screen shots is the walk-through I get when I create a new disk - noting the absence of an IDE option.
8 2009-05-07 05:33:14
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
The VM's disk settings are currently "LSI Logic" SCSI. My only other option is Bus Logic.
9 2009-05-07 04:40:02
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Humm..
The results listed are from running SaveHwid's on the VM (after it's up and running with mass storage 805).
The host under the VM is an VMWare ESX box - I'd have to pry the box open and find out what devices are in it... the ESX console doesn't tell me much about the hardware.
10 2009-05-07 04:11:56
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Results from SaveHwid's:
===========
PCI Devices
===========
PCI\VEN_1000&DEV_0030&SUBSYS_00000000&REV_01\3&61AAA01&0&80 : LSI Adapter, Ultra320 SCSI 2000 series, w/1020/1030
PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10\3&61AAA01&0&88 : AMD PCNET Family Ethernet Adapter (PCI)
PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\3&61AAA01&0&78 : Video Controller (VGA Compatible)
PCI\VEN_8086&DEV_7110&SUBSYS_00000000&REV_08\3&61AAA01&0&38 : Intel 82371AB/EB PCI to ISA bridge (ISA mode)
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\3&61AAA01&0&39 : Intel(R) 82371AB/EB PCI Bus Master IDE Controller
PCI\VEN_8086&DEV_7190&SUBSYS_00000000&REV_01\3&61AAA01&0&00 : Intel 82443BX Pentium(R) II Processor to PCI Bridge
PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_01\3&61AAA01&0&08 : Intel 82443BX Pentium(R) II Processor to AGP Controller
7 matching device(s) found.
===========
USB Devices
===========
No matching devices found.
=============
Input Devices
=============
No matching devices found.
============
ACPI Devices
============
ACPI\ACPI0003\1 : Microsoft AC Adapter
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_37\_0 : AMD Opteron(tm) Processor 250
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\PNP0001\4&5289E18&0 : EISA programmable interrupt controller
ACPI\PNP0100\4&5289E18&0 : System timer
ACPI\PNP0200\4&5289E18&0 : Direct memory access controller
ACPI\PNP0303\4&5289E18&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0400\5&324D5432&0 : Printer Port (LPT1)
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0501\2 : Communications Port (COM2)
ACPI\PNP0700\5&324D5432&0 : Standard floppy disk controller
ACPI\PNP0800\4&5289E18&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0A05\4&5289E18&0 : Generic Bus
ACPI\PNP0B00\4&5289E18&0 : System CMOS/real time clock
ACPI\PNP0C02\1F : Motherboard resources
ACPI\PNP0F13\4&5289E18&0 : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Uniprocessor PC
19 matching device(s) found.
============
HDA Audio
============
No matching devices found.
============
RAID Devices
============
PCI\VEN_1000&DEV_0030&SUBSYS_00000000&REV_01\3&61AAA01&0&80
Name: LSI Adapter, Ultra320 SCSI 2000 series, w/1020/1030
Hardware ID's:
PCI\VEN_1000&DEV_0030&SUBSYS_00000000&REV_01
PCI\VEN_1000&DEV_0030&SUBSYS_00000000
PCI\VEN_1000&DEV_0030&REV_01
PCI\VEN_1000&DEV_0030
PCI\VEN_1000&DEV_0030&CC_010000
PCI\VEN_1000&DEV_0030&CC_0100
Compatible ID's:
PCI\VEN_1000&CC_010000
PCI\VEN_1000&CC_0100
PCI\VEN_1000
PCI\CC_010000
PCI\CC_0100
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\3&61AAA01&0&39
Name: Intel(R) 82371AB/EB PCI Bus Master IDE Controller
Hardware ID's:
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD
PCI\VEN_8086&DEV_7111&CC_01018A
PCI\VEN_8086&DEV_7111&CC_0101
Compatible ID's:
PCI\VEN_8086&DEV_7111&REV_01
PCI\VEN_8086&DEV_7111
PCI\VEN_8086&CC_01018A
PCI\VEN_8086&CC_0101
PCI\VEN_8086
PCI\CC_01018A
PCI\CC_0101
2 matching device(s) found.Edited silently, almost, by the forums resident "code tag" fairy. 
11 2009-05-07 04:01:39
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
I haven't removed any drivers or software using any other tool.
I create a basic RIS image using the Server 2003 tools, then run Autoimage on the RIS installation point with the DP enabled.
12 2009-05-07 00:24:44
Re: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Well, yeah - the mass storage text mode driver from 805 works, but if I use 901, Setup can't find any HDD's
I should mention that I'm using RIS to install this system.
I'll post again with HWIDs and log files.
13 2009-05-06 07:09:41
Topic: [SLVD] DriverPack MassStorage 9.01 - ESX VMWare - LSI Adapter, Ultra320 SCSI 2000 series (31 replies, posted in DriverPack Mass Storage)
Good afternoon
I upgraded DP_Base and a handful of DriverPacks before I started working on an image...
Imagine my surprise when I couldn't run the install in a VM - Windows Setup couldn't find any disks
Downgrade to DriverPack MassStorage 8.05, and installation continues as expected (well, it find the HDD - there's other issues along the way unrelated to DP).
Any thoughts? I can't remember the name of the tool to get all the hardware IDs or I would post.
Installing XP SP3.
Thanks.
----------------- edit
PCI\VEN_1000&DEV_0030&SUBSYS_00000000&REV_01
14 2008-08-13 08:08:43
Re: Not sure how to do this... Install appication pending driver install (14 replies, posted in Other)
Yergh, I gotta be missing something big...
I build the computer, ground up from RIS. C:\ has all the .INI files. No .7z, but C:\D\ still exists.
If I manually run dpsfnshr.exe, it all goes away. Revert (yay VMs), and run dp_install_tool.cmd, and get:
"Searching current drives..
Searching all drives...
The DriverPacks were not found ???
Press any key to continue"
and it exists, without calling dpsfnshr.exe.
so... during the initial installation of the computer, is there any process running that looks at the INIs?
I think I need to go back to basics a bit... seems like I'm missing something pretty basic here.
15 2008-08-12 04:16:16
Re: Not sure how to do this... Install appication pending driver install (14 replies, posted in Other)
OverFlow wrote:
are you sure the exe is getting called?
Well, no, I'm not. I don't know if msiexec is available to the operating system at that point during install... and I don't know if setup.exe just calls msiexec, and subsequently fails.
OverFlow wrote:
did you try it without the command line switches? IE "%DPSROOT%\D\3\BT\setup.exe" to see if it launched in attended mode?
lol good idea. Noob moment, I suppose. I've got a build going with that right now, and I'll see what happens.
OverFlow wrote:
did you try running "c:\D\3\BT\setup.exe" /S /v/qn from a command line?
did you try "%DPSROOT%\D\3\BT\setup.exe" /S /v/qn from the finisher?
or """%DPSROOT%\D\3\BT\setup.exe"" /S /v/qn" ?
or ""%DPSROOT%\D\3\BT\setup.exe" /S /v/qn" ?
or """%DPSROOT%\D\3\BT\setup.exe"" /S /v/qn" ?
Er.. Yes, first one does work (and installs the software).
2nd one (from the finisher) fails - and maybe I am in the wrong place to test, because %DPSROOT% isn't set when I am finally at a point where I can use a command line.
OverFlow wrote:
you can run the finisher over and over - simply use the directions for a SAD disk and only put your BT 3rd party DriverPack in the OEM folder instead of all the packs
IE copy your OEM folder to the Local HDD (creating C:\OEM\) delete the main packs... except your BT Pack
and run the DP_Install_Tool.cmd as many times as neccessary till you got it workinhow about that for a shortcut to test the finisher ?
INI University - classes starting daily!
Fantastic I didn't know. I keep going back to this post because, so far, its the best page for consolidated information on the finisher. You guys need a wiki or something...
OverFlow wrote:
i also am not sure that /v/qn is a valid switch for a normal msi installer.
It's not, but that's how Setup.exe wants to see it...
7yler - Thanks! I will gladly try it out, but I have my doubts - this is a Dell laptop... my experience with Dell so far is that they tend to "brand" their stuff somehow so you need to use their device drivers. A bit of a pain, but thanks to the flexibility of AutoImage and DriverPacks, its eeeeaaaasyyyy. I will certainly give the pack a shot. And I completely agree with you on the simplifying work - I'm in a shop with AMD, Intels from PIII to Core 2 Duo's and all the peripherals in between.. and boy does deploying a machine go nice n easy and hardly any issues. Its just these silly laptops that have their custom stuff on them!
16 2008-08-09 02:10:15
Re: Not sure how to do this... Install appication pending driver install (14 replies, posted in Other)
Resurrecting an old thread...
Has INIU been opened up yet? The pack I'm working on doesn't seem to work
What I've got....
A Dell Latitude D630 laptop with a Dell Wireless 360 Bluetooth module in it. I think it's basically a USB device at the end of the day.
The drivers are recognized, as the device shows in your Computer Management window. So I took the driver paths from the devices, and created a .INI for it, called "DriverPack_dell630_wnt5_x86-32.ini"
[DriverPack]
platform = "wnt5_x86-32"
name = "Dell 630"
rootDir = "D\3"
; OPTIONAL
classes = "Bluetooth"
driverCount = 4
[BT]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 1
exc_1_tagFile1 = "%SystemRoot%\system32\DRIVERS\tosrfbd.sys"
; exc_1_tagFile2 = "%SystemRoot%\system32\drivers\tosrfusb.sys"
; exc_1_tagFile3 = "%SystemRoot%\system32\drivers\tosrfhid.sys"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\3\BT\Drivers\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\3\BT\setup.exe /S /v/qn"So from what I've seen in other DriverPacks, and from the documentation.. it's pretty straightforward.
The driver path (in tagFile1) is found in the device properties: [url]http://www.timatlee.com/sites/timatlee.com/files/MWSnap 2008-08-08.png[/url] (weird, IMG bbcode wasn't working...)
Does the character case of paths and whatnot matter in the file system paths?
setup.exe I think basically calls msiexec. I don't know if that's available when the the ini file is getting parsed. Thoughts?
Is there an easier way to test .INIs instead of reinstalling a PC each time? Gets a little.. er, tedious and time consuming?
Thanks again...
Tim
17 2008-06-05 05:47:51
Topic: How to integrate *ALL* MassStorage drivers? (1 replies, posted in Universal Imaging)
Hello.....
We are using RIS to install our desktops. The installation works fine, drivers are loaded, etc... However, if we try to ghost the machine to a new piece of hardware, the system gets stuck in a reboot loop. From what we're able to determine, its due to the old machine not having the device information loaded for the new hardware. Make sense?
This was attainable using Sysprep in an old image we've been using (DriverPacks were 5x series). There were a handful of batch files that would generate the content for [MassStorage] section of Sysprep... and when Windows was loading, it would load each device driver. This would allow the ghost image, and even a working OS (one that a user had been using for a period of time, then ghosted to new hardware) to be reasonably portable.
Is there a way I can automate the inclusion of the MassStorage drivers for every boot? Or maybe a way of loading all the drivers once the OS is up (since the machine can be installed RIS, the problem is moving the installation to a different piece of hardware)?
Am I even asking this the right way?
Thanks...
18 2008-05-29 14:28:54
Re: Not sure how to do this... Install appication pending driver install (14 replies, posted in Other)
Wow. That's awesome. Makes it so easy, I almost can't wait to test it in the morning. I was getting ready to write something that would look to see if the device existed on the system, then check that the driver was installed (wasn't certain how on that point.. heh, I'm no coder), then run the install. Thanks for taking all the guess work out of it though!
I apologize for not searching it out on the forums; wasn't certain what wording to use.
Thanks again, and keep up the great work
19 2008-05-29 03:36:00
Topic: Not sure how to do this... Install appication pending driver install (14 replies, posted in Other)
Good morning...
I've got a Dell Latitude D630 laptop. It came with a Dell Bluetooth module. I've been able to get the device to be recognized (no longer showing up as an error or warning in the device manager) by packing up a 3rd party driver, however it seems to need the Dell software to actually work (the device is recognized, but no Bluetooth control panel is available, etc).
Is there any way I can tweak the INF, or use some post-install hook to install the associated software? It would seem to me that this has been done with NVidia video stuff and their control panel, but I've got no clue where to begin looking to see how that was handled.
I don't particularily want to put it in CMDLINES.TXT or some other location, as the application should only get installed when a specific device is present. Unless there's a way I can check that the device is there, then install.. from a .CMD script...
Thanks,
Tim
20 2008-05-24 04:58:05
Re: [TESTPACK] Dell D630 Video Driver (nVidia Quadro NVS 135M) (7 replies, posted in DriverPack Graphics)
Hello again
I packaged up the Dell drivers as a 3rd Party Pack, and was met with success when I rebuilt the laptop in question.
I know RIS isn't technically supported... as far as I can see, the key difference is how the installation media gets on the client machine - either by DVD or via the network. The machine still boots into the typical Windows setup routine - after unpacking the drivers.
Thanks again for your help,
Tim
21 2008-05-24 03:04:46
Re: [TESTPACK] Dell D630 Video Driver (nVidia Quadro NVS 135M) (7 replies, posted in DriverPack Graphics)
Nngh I apologies for double-post. Got a blank screen after posting, hit refresh. Sorry...
22 2008-05-24 03:01:23
Topic: [TESTPACK] Dell D630 Video Driver (nVidia Quadro NVS 135M) (7 replies, posted in DriverPack Graphics)
Good morning
I have received a new Dell Latitude D630 laptop. I am installing a standard image using RIS. Most devices installed correctly except for a "PCI Device" (probably Bluetooth driver) and the video driver.
After a brief search on these forums, I found one reference to a similar configuration: http://forum.driverpacks.net/viewtopic.php?id=2162.
However, unlike "sheetzdw" I was unable to get the device to install by updating the driver.
I'm using Graphics pack A, B and C version 8.04. Have not verified the MD5 sum, but the archives are "good" (can be opened with winrar without error; dp_base handles without error).
I've created a 3rd party pack based on the Dell supplied driver, but the test is still underway.. and if it's already included in one of the existing graphics pack, I don't want to duplicate work.
Thanks in advance,
Tim
Driver for the device: http://support.dell.com/support/downloa … eid=246636
HWID:
===========
PCI Devices
===========
PCI\VEN_10DE&DEV_042B&SUBSYS_01F91028&REV_A1\4&15F4A1BE&0&0008: NVIDIA Quadro NVS 135M
PCI\VEN_1217&DEV_00F7&SUBSYS_01F91028&REV_02\4&28D6DE3B&0&0CF0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1217&DEV_7135&SUBSYS_01F91028&REV_21\4&28D6DE3B&0&08F0: Generic CardBus Controller
PCI\VEN_14E4&DEV_1673&SUBSYS_01F91028&REV_02\4&1E93A591&0&00E5: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_14E4&DEV_4328&SUBSYS_000A1028&REV_03\4&AB208E&0&00E1: Broadcom 802.11n Network Adapter
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_F2\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_2815&SUBSYS_00000000&REV_02\3&61AAA01&0&F8 : Intel(R) ICH8M LPC Interface Controller - 2815
PCI\VEN_8086&DEV_2828&SUBSYS_01F91028&REV_02\3&61AAA01&0&FA : Intel(R) ICH8M 3 port Serial ATA Storage Controller - 2828
PCI\VEN_8086&DEV_2830&SUBSYS_01F91028&REV_02\3&61AAA01&0&E8 : Intel(R) ICH8 Family USB Universal Host Controller - 2830
PCI\VEN_8086&DEV_2831&SUBSYS_01F91028&REV_02\3&61AAA01&0&E9 : Intel(R) ICH8 Family USB Universal Host Controller - 2831
PCI\VEN_8086&DEV_2832&SUBSYS_01F91028&REV_02\3&61AAA01&0&EA : Intel(R) ICH8 Family USB Universal Host Controller - 2832
PCI\VEN_8086&DEV_2834&SUBSYS_01F91028&REV_02\3&61AAA01&0&D0 : Intel(R) ICH8 Family USB Universal Host Controller - 2834
PCI\VEN_8086&DEV_2835&SUBSYS_01F91028&REV_02\3&61AAA01&0&D1 : Intel(R) ICH8 Family USB Universal Host Controller - 2835
PCI\VEN_8086&DEV_2836&SUBSYS_01F91028&REV_02\3&61AAA01&0&EF : Intel(R) ICH8 Family USB2 Enhanced Host Controller - 2836
PCI\VEN_8086&DEV_283A&SUBSYS_01F91028&REV_02\3&61AAA01&0&D7 : Intel(R) ICH8 Family USB2 Enhanced Host Controller - 283A
PCI\VEN_8086&DEV_283E&SUBSYS_01F91028&REV_02\3&61AAA01&0&FB : Intel(R) ICH8 Family SMBus Controller - 283E
PCI\VEN_8086&DEV_283F&SUBSYS_00000000&REV_02\3&61AAA01&0&E0 : Intel(R) ICH8 Family PCI Express Root Port 1 - 283F
PCI\VEN_8086&DEV_2841&SUBSYS_00000000&REV_02\3&61AAA01&0&E1 : Intel(R) ICH8 Family PCI Express Root Port 2 - 2841
PCI\VEN_8086&DEV_2849&SUBSYS_00000000&REV_02\3&61AAA01&0&E5 : Intel(R) ICH8 Family PCI Express Root Port 6 - 2849
PCI\VEN_8086&DEV_284B&SUBSYS_01F91028&REV_02\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_2850&SUBSYS_01F91028&REV_02\3&61AAA01&0&F9 : Intel(R) ICH8M Ultra ATA Storage Controllers - 2850
PCI\VEN_8086&DEV_2A00&SUBSYS_00000000&REV_0C\3&61AAA01&0&00 : Mobile Intel(R) PM965/GM965/GL960/GS965 Express Processor to DRAM Controller - 2A00
PCI\VEN_8086&DEV_2A01&SUBSYS_00000000&REV_0C\3&61AAA01&0&08 : Mobile Intel(R) PM965/GM965/GL960/GS965 Express PCI Express Root Port - 2A01
23 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&139B5C82&0 : USB Root Hub
USB\ROOT_HUB\4&291EE475&0 : USB Root Hub
USB\ROOT_HUB\4&31D948AA&0 : USB Root Hub
USB\ROOT_HUB\4&36706929&0 : USB Root Hub
USB\ROOT_HUB\4&CE55D9D&0 : USB Root Hub
USB\ROOT_HUB20\4&18F00B04&0 : USB Root Hub
USB\ROOT_HUB20\4&3B65BF0F&0 : USB Root Hub
USB\VID_0B97&PID_7761\5&4589DBC&0&1 : Generic USB Hub
USB\VID_0B97&PID_7772\6&C4C946D&0&2 : O2Micro CCID SC Reader
USB\VID_413C&PID_8140\5&11246E2F&0&2 : USB Device
10 matching device(s) found.
=============
Input Devices
=============
No matching devices found.
============
ACPI Devices
============
ACPI\ACPI0003\2&DABA3FF&0 : Microsoft AC Adapter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_0 : Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_15\_1 : Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz
ACPI\PNP0000\4&2F94427B&0 : Programmable interrupt controller
ACPI\PNP0100\4&2F94427B&0 : System timer
ACPI\PNP0103\4&2F94427B&0 : High Precision Event Timer
ACPI\PNP0200\4&2F94427B&0 : Direct memory access controller
ACPI\PNP0303\4&2F94427B&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0501\4&2F94427B&0 : Communications Port (COM1)
ACPI\PNP0800\4&2F94427B&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0B00\4&2F94427B&0 : System CMOS/real time clock
ACPI\PNP0C01\1 : System board
ACPI\PNP0C01\2 : System board
ACPI\PNP0C01\3 : System board
ACPI\PNP0C01\4 : System board
ACPI\PNP0C01\5 : System board
ACPI\PNP0C04\4&2F94427B&0 : Numeric data processor
ACPI\PNP0C0A\1 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0 : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0 : ACPI Sleep Button
ACPI\PNP0C14\0 : Microsoft Windows Management Interface for ACPI
ACPI\PNP0F13\4&2F94427B&0 : PS/2 Compatible Mouse
ACPI\THERMALZONE\THM_ : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
28 matching device(s) found.Next time use code tags please
23 2008-05-08 06:46:14
Re: [solved] Issue with a Toshiba Satellite notebook (2 replies, posted in DriverPack Graphics)
That did the trick, thank you. I never would have checked that, given that BASE was reporting nothing new. Now on to the audio driver...
Thanks again!
24 2008-05-07 08:44:41
Topic: [solved] Issue with a Toshiba Satellite notebook (2 replies, posted in DriverPack Graphics)
Hello
I have a Toshiba Satellite 2450 notebook that I'm trying to automate a Windows install on. So far, everything is working great - except the video and sound drivers.
The video device is an NVidia GeForce4 420 Go - which I would expect to find in Graphics pack A.
However, during setup (after the drivers get extracted), I start seeing messages about "Application or DLL nvcpl.dll/nvmctray.dll is not a valid Windows image" and so on.
From what I've read at http://www.laptopvideo2go.com/, NVidia does some funny stuff with their mobile drivers, presumably to keep the customer going back to the vendor (instead of NVidia). I couldn't get the stuff at laptopvideo2go.com to work either, so I moved on.
Now I'm left with drivers right from Toshiba. This is the only laptop I have of this configuration, and it's a loaner - so having it completely automated is ideal
The drivers for this laptop are available from Toshiba - I've downloaded them and installed them manually, and they work without a hitch.
So my question here is: These Toshiba drivers .. should I make them a 3rd party driver pack, or set the drivers up manually in the OemPnpPath and hope dp_base works? I don't really fancy the idea of breaking the rest of the drivers just for one device. If I make the Toshiba drivers a 3rd party pack, how do I get Windows to pick the Toshiba drivers instead of the ones bundled with Graphics A?
Open to any suggestions...
Thanks,
Tim