1 Reply by Rambo

(9 replies, posted in Windows 7 Discussion)

Just a final update on this old question - it's been doing my head in a bit...

The combination of UEFI and mSATA was (is) causing confusion.

Essentially, it seems that disabling secure boot, and enabling CSM (BIOS) mode, plus making sure the Intel RST drivers were available (I stuck them in $WinPEDriver$ folder rather than integrate them) seems to resolve most of the issues I was having.

The only thing unresolved is that I'm almost certain that this machine would boot with the disks ID's different from one boot to the next. Unfortunately having resolved the other parts of this that were confusing me I no longer have access to these machines for testing. I'm certain that sometimes the main HD would be Disk 0, other times it would be Disk 1 which caused some issues with my unattended script.

Bottom line, is that the Driver Packs were not at fault (as usual!) and it was more about understanding the various hardware options on this new machine.

Thanks for your help,
Rod

Go to forum: Windows 7 Discussion

2 Reply by Rambo

(9 replies, posted in Windows 7 Discussion)

Sorry to take a while to update this and thank you for the replies so far.

mr_smartepants - this machine is a beast, and that is part of the problem.

I think the install needs driver packs chipset and mass storage, but also the Intel RST drivers as well. To be honest, though, I'm not absolutely sure. I'm almost there, and will update this post once I'm certain what's going on.

The reason for my confusion is the mSATA drive. This means that the main drive is disk 2, not disk 0 (or even one) so my unattend.xml needs adjusting, too. I've been confusing myself because of the variety of errors and continuing to get errors when everything looks right. Think I'm on top of it now, just got to sort it out.

Do you guys have any suggestions as to how I might create a single unattend.xml file that will always install to the largest available drive or similar no matter how many drives are in the system?

Regards,
Rod

Go to forum: Windows 7 Discussion

3 Reply by Rambo

(9 replies, posted in Windows 7 Discussion)

Happy New Year,
Struck a problem or two, was hoping you might be able to provide some pointers.

The integration process seems to go fine - drivers load with DISM successfully to both BOOT.WIM and INSTALL.WIM. I load them to image 2 in BOOT.WIM and image 3 in INSTALL.WIM (I'm installing Windows 7 Pro). When trying to boot, it gets as far as 'Starting setup' then I get a message about not having drivers for the CD/DVD. I assume that this is actually the USB thumb drive emulating a CD/DVD, but I'm unsure as to why I get the message.

The machine is a brand new Dell Vostro 3560 - USB 3 ports only. BIOS says that the SATA controller is in 'Intel Smart Response Technology' mode, but if I change to AHCI mode it also fails. I don't want to use IDE mode. HWIDs.txt is below, hope that helps.

Thanks,
Rod Clark

===========
PCI Devices
===========
PCI\VEN_8086&DEV_0154&SUBSYS_056E1028&REV_09\3&11583659&0&00: 3rd Gen Core processor DRAM Controller - 0154
PCI\VEN_8086&DEV_0151&SUBSYS_056E1028&REV_09\3&11583659&0&08: Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
PCI\VEN_8086&DEV_1E12&SUBSYS_056E1028&REV_C4\3&11583659&0&E1: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 2 - 1E12
PCI\VEN_8086&DEV_1E2D&SUBSYS_056E1028&REV_04\3&11583659&0&D0: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
PCI\VEN_8086&DEV_1E57&SUBSYS_056E1028&REV_04\3&11583659&0&F8: Intel(R) HM77 Express Chipset LPC Controller - 1E57
PCI\VEN_8086&DEV_1E14&SUBSYS_056E1028&REV_C4\3&11583659&0&E2: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 3 - 1E14
PCI\VEN_8086&DEV_1E26&SUBSYS_056E1028&REV_04\3&11583659&0&E8: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26
PCI\VEN_1002&DEV_6840&SUBSYS_056E1028&REV_00\4&222499E&0&0008: AMD Radeon HD 7670M
PCI\VEN_8086&DEV_1E20&SUBSYS_056E1028&REV_04\3&11583659&0&D8: High Definition Audio Controller
PCI\VEN_8086&DEV_0166&SUBSYS_056E1028&REV_09\3&11583659&0&10: Intel(R) HD Graphics 4000
PCI\VEN_8086&DEV_1E31&SUBSYS_056E1028&REV_04\3&11583659&0&A0: Intel(R) USB 3.0 eXtensible Host Controller - 0100 (Microsoft)


PCI\VEN_8086&DEV_1E3A&SUBSYS_056E1028&REV_04\3&11583659&0&B0: Intel(R) Management Engine Interface
PCI\VEN_8086&DEV_282A&SUBSYS_056E1028&REV_04\3&11583659&0&FA: Intel(R) Mobile Express Chipset SATA RAID Controller
PCI\VEN_8086&DEV_1E10&SUBSYS_056E1028&REV_C4\3&11583659&0&E0: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10
PCI\VEN_8086&DEV_0887&SUBSYS_44628086&REV_C4\4&39DE1E7E&0&00E1: Intel(R) Centrino(R) Wireless-N 2230
PCI\VEN_10EC&DEV_8168&SUBSYS_056E1028&REV_07\4&11540BE9&0&00E0: Realtek PCIe GBE Family Controller
PCI\VEN_8086&DEV_1E22&SUBSYS_056E1028&REV_04\3&11583659&0&FB: Intel(R) 7 Series/C216 Chipset Family SMBus Host Controller - 1E22
17 matching device(s) found.

===========
USB Devices
===========
USB\VID_8087&PID_0024\5&356A24C6&0&1                        : Generic USB Hub
USB\VID_138A&PID_0011\ED4EF930C5CC                          : Validity Sensor
USB\VID_1BCF&PID_2895&MI_00\7&5E81193&0&0000                : Integrated Webcam
USB\VID_8087&PID_0024\5&1C9C9BE1&0&1                        : Generic USB Hub
USB\ROOT_HUB30\4&27D251BD&0&0                               : USB Root Hub (xHCI)
USB\VID_8087&PID_07DA\6&2D3B92E5&0&5                        : Intel(R) Centrino(R) Wireless Bluetooth(R) 4.0 + High Speed Adapter
USB\ROOT_HUB20\4&A977F4A&0                                  : USB Root Hub
USB\ROOT_HUB20\4&58B0204&0                                  : USB Root Hub
USB\VID_1BCF&PID_2895\6&39DBDB0D&0&5                        : USB Composite Device
USB\VID_0BDA&PID_0129\20100201396000000                     : Realtek USB 2.0 Card Reader
10 matching device(s) found.

=============
Input Devices
=============
No matching devices found.

============
ACPI Devices
============
ACPI\PNP0C01\2                                              : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\2                                              : Motherboard resources
ACPI\INT0800\4&37011F08&0                                   : Intel(R) 82802 Firmware Hub Device
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\DLL056E\4&37011F08&0                                   : Dell Touchpad
ACPI\PNP0C09\4&37011F08&0                                   : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0100\4&37011F08&0                                   : System timer
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\PNP0103\0                                              : High precision event timer
ACPI\PNP0C0D\2&DABA3FF&1                                    : ACPI Lid
ACPI\INT3392\2&DABA3FF&1                                    : Intel(R) Rapid Start Technology Device
ROOT\ACPI_HAL\0000                                          : ACPI x64-based PC
ACPI\PNP0A08\0                                              : Pci Bus
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_1: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_2: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_3: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_4: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_5: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_6: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_7: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_8: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\PNP0B00\4&37011F08&0                                   : System CMOS/real time clock
ACPI\DLLK056E\4&37011F08&0                                  : Standard PS/2 Keyboard
ACPI\PNP0000\4&37011F08&0                                   : Programmable interrupt controller
ACPI\PNP0C0C\4&37011F08&0                                   : ACPI Power Button
ACPI\FIXEDBUTTON\2&DABA3FF&1                                : ACPI Fixed Feature Button
ACPI\INT3F0D\4&37011F08&0                                   : Motherboard resources
ACPI\PNP0200\4&37011F08&0                                   : Direct memory access controller
ACPI\ACPI0003\4&37011F08&0                                  : Microsoft AC Adapter
ACPI\INT340E\2&DABA3FF&1                                    : Motherboard resources
ACPI\PNP0C04\4&37011F08&0                                   : Numeric data processor
ACPI\SMO8810\1                                              : STMicroelectronics 3-Axis Digital Accelerometer
34 matching device(s) found.

============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_8086&DEV_2806&SUBSYS_80860101&REV_1000\4&1FF2F789&0&0301: Intel(R) Display Audio
HDAUDIO\FUNC_01&VEN_14F1&DEV_506E&SUBSYS_1028056E&REV_1000\4&1FF2F789&0&0001: Conexant SmartAudio HD
2 matching device(s) found.

============
RAID Devices
============
PCI\VEN_8086&DEV_282A&SUBSYS_056E1028&REV_04\3&11583659&0&FA
    Name: Intel(R) Mobile Express Chipset SATA RAID Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_282A&SUBSYS_056E1028&REV_04
        PCI\VEN_8086&DEV_282A&SUBSYS_056E1028
        PCI\VEN_8086&DEV_282A&CC_010400
        PCI\VEN_8086&DEV_282A&CC_0104
    Compatible ID's:
        PCI\VEN_8086&DEV_282A&REV_04
        PCI\VEN_8086&DEV_282A
        PCI\VEN_8086&CC_010400
        PCI\VEN_8086&CC_0104
        PCI\VEN_8086
        PCI\CC_010400
        PCI\CC_0104
1 matching device(s) found.

Go to forum: Windows 7 Discussion

4 Reply by Rambo

(9 replies, posted in Windows 7 Discussion)

Thanks for the quick and concise response, really appreciate the help you give.

Those answers confirm what I thought was the case so I'll:

1. Use DISM to add Mass Storage and Chipset to BOOT.WIM
2. Use DISM to add Mass Storage, Chipset, LAN and probably WLAN to INSTALL.WIM
3. Use you SAD2 script or manual downloads to handle the rest

That should be the most efficient in all respects for my needs.

Thanks again,
Rod

Go to forum: Windows 7 Discussion

5 Topic by Rambo

(9 replies, posted in Windows 7 Discussion)

Firstly, a Merry Christmas to all at DriverPacks.net

I'm about to update my Win 7 deployment DVD/USB and planning on using DISM to integrate drivers, rather the the $WinPEDriver$ method I've used in the past. I need to make sure that booting from a USB 3 attached thumb drive or DVD will work.

Looking around here, the advice seems to be to use DISM to add Mass Storage to BOOT.WIM, then others such as Chipset, LAN, WLAN (I think that's all I need) to INSTALL.WIM - I know about getting the indexes correct...

My questions are:
1. Since the Chipset drivers seem to be the ones that contain USB 3 drivers, won't I need to add those to BOOT.WIM as well as the Mass Storage ones?

2. Do drivers added to BOOT.WIM 'carry over' to INSTALL.WIM and the final installation, or is it necessary to add Mass Storage (and possibly Chipset) to both WIM files?

Thanks,
Rod

Go to forum: Windows 7 Discussion

6 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Interesting article - I'll read in detail later, but at first glance it does look to explain the possibility of problems.

I certainly agree with minimising the number of injected drivers for several reasons, but this is another one, too.

Really appreciate you remembering this old call and drawing the new information to my attention.

If only I could get service like that for the products I pay for.

Thanks,
Rod

Go to forum: Vista / 7 DriverPack Mass Storage

7 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Confirming that the DISM method works for both x32 and x64 bit, but I do get the problem referred to when added via $WinPEDriver$ folder.

I'm going to use DISM for now, at least, until or unless someone finds a solution.

Thanks mr_smarepants for your assistance.

Rod

Go to forum: Vista / 7 DriverPack Mass Storage

8 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

I love MS documentation, makes what sounds simple very complex, but there's usually good reasons for it that I wouldn't have thought of in a million years. Doesn't surprise me much that this is hard to replicate, remember it doesn't happen on every one of my test boxes and on the ones that it does, changing to ACHI instead of RAID mode in the BIOS 'fixes' it, too.

I've used DISM to add the drivers to my x64 BOOT.WIM (index 2), pointing it to the same source folder as I use for $WinPEDriver$. It integrated 91 drivers without problem and when I run setup from that, it works!

So this problem only happens for drivers loaded via $WinPEDriver$ and then only on quite specific types of hardware. If the DISM method works for x32, too, then I think I'll just do things that way, it's slower doing updates to drivers, but I don't typically have to do that too often.

Since DISM integration of drivers works, this will be my work around. I'm happy to try to help get to the bottom of this further, but it will get a little more difficult as I have to return the machine to my client.

I appreciate your efforts,
Rod

Go to forum: Vista / 7 DriverPack Mass Storage

9 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Thanks for your work on this - I think the problem is with the iastor.inf files, but not sure...

I'm going to try DSIM to integrate the drivers as they are and see if that resolves the issue. In the end, I'm happy to use that method if it works.

Will update here how I get on.

Rod

Go to forum: Vista / 7 DriverPack Mass Storage

10 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

I'd certainly appreciate it if you could do that.

Rod

Go to forum: Vista / 7 DriverPack Mass Storage

11 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Thanks,
Switching to 64-bit, then, I see similar behaviour. If I put the entire driver pack into $WinPEDriver$ then I get the 'unable to load boot-critical drivers' message.

I think what is happening is that Windows Setup is getting 'confused' have multiple versions of drivers for the same HWID. Perhaps this is unique to this method of integration rather than using DSIM? This method suits my situation as it is a little quicker/simpler to make quick changes (though I notice you've got some batch files for automating the DISM process).

If I make sure that there's no duplicate drivers/HWIDS by doing the below to the IaStor.Inf in the x64 or x32 driver pack:

All\M\Intel\1
[INTEL_HDC.ntamd64]
%PCI\VEN_8086&DEV_2682&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2682&CC_0104
;%PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C3&CC_0104
;%PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_27C6&CC_0104
;%PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2822&CC_0104
;%PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_282A&CC_0104

Then doing the below, depending on version:

x64\All\M\Intel\2
Delete

x64\All\M\Intel\3
Untouched...

x32\All\M\Intel\3
Delete...

x32\All\M\Intel\4
Untouched...

If I've done this correctly, this means that there is no duplicate drivers, but all the same devices are supported - do you agree?

Certainly after doing this, Windows Setup completes successfully on this machine (and in a VM, too) and all drivers appear load correctly.

Regards,
Rod

Go to forum: Vista / 7 DriverPack Mass Storage

12 Reply by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Thanks for the reply. I agree that it seems unusual to set the BIOS to RAID even though there is only one disk, nonetheless that is the way Dell shipped them (we bought eight at once, all the same). Ideally this should work either way.

Looking a little deeper, can you confirm that what happens is that there is a 'simple' match of HWID to string in INF file to determine the driver to use? If that is the case, is this a problem because the IaStor.inf in All\M\Intel\1, 3, and 4 are almost identical and contain essentially the same HWID's? They appear to be just later versions of the same thing and my HWID seems to match all of them...

I don't quite understand how you say my HWID matches 3, but not 4, when to me they look the same! You have way more experience at this than I do, have I missed something? What are the consequences of removing duplicates - all the same hardware should still be supported, shouldn't it?

Regards,
Rod

All\Intel\1\
; **    Filename:  iaStor.INF
; **    Revision:  Version 10.1.0.1008
DiskName                                    = "Intel Rapid Storage Technology Driver"
*PNP0600.DeviceDesc                         = "Intel RAID Controller"
PCI\VEN_8086&DEV_2682&CC_0104.DeviceDesc    = "Intel(R) ESB2 SATA RAID Controller"
PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc    = "Intel(R) ICH7R/DH SATA RAID Controller"
PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc    = "Intel(R) ICH7MDH SATA RAID Controller"
PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc    = "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller"
PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc    = "Intel(R) Mobile Express Chipset SATA RAID Controller"

All\Intel\3\
; **    Filename:  iaStor.INF
; **    Revision:  Version 10.8.0.1003
DiskName                                    = "Intel Rapid Storage Technology Driver"
*PNP0600.DeviceDesc                         = "Intel RAID Controller"
PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc    = "Intel(R) ICH7R/DH SATA RAID Controller"
PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc    = "Intel(R) ICH7MDH SATA RAID Controller"
PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc    = "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller"
PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc    = "Intel(R) Mobile Express Chipset SATA RAID Controller"

All\Intel\4\
; **    Filename:  iaStor.INF
; **    Revision:  Version 11.0.0.1032
DiskName                                    = "Intel Rapid Storage Technology Driver"
*PNP0600.DeviceDesc                         = "Intel RAID Controller"
PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc    = "Intel(R) ICH7R/DH SATA RAID Controller"
PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc    = "Intel(R) ICH7MDH SATA RAID Controller"
PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc    = "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller"
PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc    = "Intel(R) Mobile Express Chipset SATA RAID Controller"

============
RAID Devices
============
PCI\VEN_8086&DEV_2822&SUBSYS_047E1028&REV_04\3&11583659&0&FA
    Name: Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_2822&SUBSYS_047E1028&REV_04
        PCI\VEN_8086&DEV_2822&SUBSYS_047E1028
        PCI\VEN_8086&DEV_2822&CC_010400
        PCI\VEN_8086&DEV_2822&CC_0104
    Compatible ID's:
        PCI\VEN_8086&DEV_2822&REV_04
        PCI\VEN_8086&DEV_2822
        PCI\VEN_8086&CC_010400
        PCI\VEN_8086&CC_0104
        PCI\VEN_8086
        PCI\CC_010400
        PCI\CC_0104
1 matching device(s) found.

Go to forum: Vista / 7 DriverPack Mass Storage

13 Topic by Rambo

(14 replies, posted in Vista / 7 DriverPack Mass Storage)

Hi guys,
Thanks again for your hard work in creating the driver packs, your efforts are greatly appreciated.

I seem to have found a problem, not certain exactly where it lies. I'm installing Win 7 SP1 (doesn't matter if it's x64 or x32) onto a Dell Optiplex 990 using an automated installation. This problem is not limited to that hardware, though, as it happened at least once under VMWare Player, too. I've added the expanded Mass Storage drivers to the $WinPEDriver$ folder in the root of the boot media (either a DVD or USB thumb drive). The message 'Setup is starting' appears and after a lengthy pause a message box appears with the following text:

'Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.'

You can click OK, but the installation seems to just stop at that point with no further messages.

When setup stops, I examined setupact.log and the last line contains the error message and the lines before contain messages about loading various OEMxx.INF files:

2012-03-01 21:54:09, Info                         PnPIBS: Installing driver X:\windows\INF\oem23.inf ...
2012-03-01 21:54:09, Info                         PnPIBS: Installing driver X:\windows\INF\oem24.inf ...
2012-03-01 21:59:10, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]

On looking at OEM24.INF I see it is one of the Intel drivers from \All\M\Intel\3 renamed. I removed the 3 folder, and tried again, but then got the same message referring to the INF in \All\M\Intel\4. Removed that folder and the machine installed correctly. I also found that if I changed the BIOS of the machine from the default 'RAID' to ACHI that installation proceeded even with both 3 and 4 folders in place.

An earlier version of my installation disk had an earlier version of the driver pack (sorry not sure which one, but there was only a 1 and a 2 folder under Intel) works fine, too. I'm trying to support the widest range of hardware possible, so don't wish to remove these to sacrifice that support.

The relevant output from the HWID tool is below:

Any ideas or suggestions?
Rod

============
RAID Devices
============
PCI\VEN_8086&DEV_2822&SUBSYS_047E1028&REV_04\3&11583659&0&FA
    Name: Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_2822&SUBSYS_047E1028&REV_04
        PCI\VEN_8086&DEV_2822&SUBSYS_047E1028
        PCI\VEN_8086&DEV_2822&CC_010400
        PCI\VEN_8086&DEV_2822&CC_0104
    Compatible ID's:
        PCI\VEN_8086&DEV_2822&REV_04
        PCI\VEN_8086&DEV_2822
        PCI\VEN_8086&CC_010400
        PCI\VEN_8086&CC_0104
        PCI\VEN_8086
        PCI\CC_010400
        PCI\CC_0104
1 matching device(s) found.

Go to forum: Vista / 7 DriverPack Mass Storage

14 Reply by Rambo

(6 replies, posted in DriverPack Mass Storage)

I hardly use CD's these days, too. But that's another story.

Can confirm that 11.04 works fine for me in both VM and on this Toshiba Laptop.

Thanks again,
Rod

Go to forum: DriverPack Mass Storage

15 Reply by Rambo

(6 replies, posted in DriverPack Mass Storage)

It was definitely in the GUI phase (after T-39), during the driver scan, but I think I found the real cause and you'll be pleased to know - not the Driver Pack fault.

This is a CD build, and as you might imagine was very short on space - image size showed as 701MB. The problem didn't occur with a DVD build from the same source files. I removed a few files from the source to make the image size 699MB and it works. Seems that while I can burn a slightly oversized image, reading it back crashes the test machine when it tries to access the files. I think that when I rebuilt the driver pack after editing the INI that either the file was slightly smaller, or maybe the layout as burned to the CD changed.

Have undone the INI file change and reduced the size of the image and it seems completely reliable now. Now that I can see 11.04 is up, I'll try that too.

Sorry to waste your time on a red herring, and thanks again for all your great work.

Rod

Go to forum: DriverPack Mass Storage

16 Reply by Rambo

(6 replies, posted in DriverPack Mass Storage)

Ahh, yes, you're correct of course. Yet the only change I made was to the INI file (not the INF) and it was definitely getting past TXT mode. Most strange.

Just looking at Device Manager on the machine shows it is using the v10 drivers, which I believe means it is coming from I8.

Rod

Go to forum: DriverPack Mass Storage

17 Topic by Rambo

(6 replies, posted in DriverPack Mass Storage)

Firstly, thanks again for your efforts with these packs. It's a great testament to your hard work that this is the first time I've had a problem...

I am updating my install disk for what I hope is the last time as we move to Windows 7, and have found a problem with 11.01 (and 11.04r3 beta linked here: http://forum.driverpacks.net/viewtopic.php?id=5226). I'm installing onto a Toshiba Satellite Pro C650. It successfully gets through the text mode section, reboots into GUI and the next time it reboots, a blue screen happens and the it gets into a circular reboot cycle. I don't know of any way to get the details of the blue screen, but my guess is that it is a Stop 7B because it happens so early in the boot cycle.

Below is an extract from the SaveHWIDS utility identifying PCI\VEN_8086&DEV_2929 as the SATA controller (sorry, don't know how to do code blocks)
===========
PCI Devices
===========
PCI\VEN_8086&DEV_2930&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&FB: Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_293C&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&D7: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_2934&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&E8: Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_293E&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&D8: High Definition Audio Controller
PCI\VEN_8086&DEV_2935&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&E9: Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2940&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&E0: Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_168C&DEV_002B&SUBSYS_7159144F&REV_01\4&11D53223&0&00E1: Atheros AR9285 Wireless Network Adapter
PCI\VEN_8086&DEV_2936&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&EA: Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2942&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&E1: Intel(R) ICH9 Family PCI Express Root Port 2 - 2942
PCI\VEN_1969&DEV_2060&SUBSYS_FF1E1179&REV_C1\4&2BC30F68&0&00E0: Atheros AR8152/8158 PCI-E Fast Ethernet Controller
PCI\VEN_8086&DEV_2937&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&D0: Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2948&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&E4: Intel(R) ICH9 Family PCI Express Root Port 5 - 2948
PCI\VEN_8086&DEV_2448&SUBSYS_FF1E1179&REV_93\3&33FD14CA&0&F0: Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_2938&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&D1: Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2A40&SUBSYS_FF1E1179&REV_07\3&33FD14CA&0&00: Mobile Intel(R) 4 Series Chipset Processor to DRAM Controller - 2A40
PCI\VEN_8086&DEV_2919&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&F8: Intel(R) ICH9M LPC Interface Controller - 2919
PCI\VEN_8086&DEV_2939&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&EB: Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_2A42&SUBSYS_FDE01179&REV_07\3&33FD14CA&0&10: Mobile Intel(R) 45 Express Chipset Family (Microsoft Corporation - WDDM 1.1)
PCI\VEN_8086&DEV_2929&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&FA: Intel(R) ICH9M-E/M SATA AHCI Controller
PCI\VEN_8086&DEV_293A&SUBSYS_FF1E1179&REV_03\3&33FD14CA&0&EF: Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_2A43&SUBSYS_FDE01179&REV_07\3&33FD14CA&0&11: Mobile Intel(R) 45 Express Chipset Family (Microsoft Corporation - WDDM 1.1)
21 matching device(s) found.

I extracted the mass storage drivers and checked for a matching driver in the INI file, and found it occurs twice, once it the commented out [I4] section and once in the [I8] section. The files in I8 include a text file that clearly states that this driver should support that device. As a test, I thought I'd uncomment [I4] and all the lines in it. I then edited the ms_1_hwids line in [I4] so that my HWID is the only one on the line. Lastly, I edited the ms_1_hwids line in the [I8} section to remove this particular HWID. Re 7Zipped the file and built the ISO, burnt to CD and now it works!

I'm a little concerned that this might cause other problems, but I think that the change I made should only effect this particular hardware and that it should be reliable.

Any thoughts or comments? I'm happy to try any experiments you wish.

Regards,
Rod

Go to forum: DriverPack Mass Storage

18 Topic by Rambo

(2 replies, posted in DriverPack Mass Storage)

As a long time 'lurker' at Driver Packs, just wanted to say thanks to all that work on them, particularly the Mass Storage and Network ones.

They make my job easier every day.

I first started automating Windows v3.1 installations, adding specific video drivers to nearly silent installs so that large teams could roll out to hundreds of computers without imaging software (which cost too much). From there, I remember - in the days of Windows 95/NT - realising that the automation capabilities were much improved and began adding drivers for all the hardware (video and network mainly) in our company - about a thousand machines, probably 20 different models. In the end, though I realised the power of the process, the task of maintaining even that number of drivers was a real burden.

To think that you guys had the drive required to produce these packs, not only for your own hardware, but essentially for ALL hardware is beyond my comprehension. Since I started using these packs three or four years ago, they have save me hundreds of hours of hassle downloading drivers, worry about SATA text mode drivers on machines without Drive A:, etc. They have essentially worked flawlessy across my almost thirty clients of varying sizes with dozens of different machines.

I hope this little note helps keep you going when people hassle you about the next release taking too long. Your work is greatly appreciated.

Regards,
Rod Clark

Go to forum: DriverPack Mass Storage

19 Reply by Rambo

(32 replies, posted in Feature Requests)

See this for a really basic splash screen that works...

http://forum.driverpacks.net/viewtopic. … 5942#p5942

Go to forum: Feature Requests

20 Reply by Rambo

(10 replies, posted in Feature Requests)

I've seen the earlier posts regarding splash screens and how nobody seems to be able to get it working.

Most had tried AutoIt scripts (me too!) but I found that they simply exit with no message of any sort.

Seems that something about the environment at that point in the setup means that many programs simply don't work. Since AutoIt scripts don't work, I decided to try a VB 6 program - I'm not much of a coder, but wrote something quick to test. I was quite surprised when I could see my program run during the extraction.

Being VB6 this is a full GUI, but at at this time its a little 'dumb' in that it doesn't actually detect when the extraction process is complete. It only exits under three conditions.
1. Manually closed
2. When it detects that XCOPY.EXE is running
3. When Windows setup completes and restarts

If there is interest I'm happy to (and have just done so for firefox) send people source code. I plan to try to enhance it a bit, but don't have a huge amount of time (or great programming skills!). Just my small contribution to say a small thanks.

Rambo...

Go to forum: Feature Requests

21 Topic by Rambo

(10 replies, posted in Feature Requests)

Been playing with a program written in VB 6 that can run while the drivers are extracted (method 2).

Would be good if the DriverPack Base had an option to run a command after detection of the CD drive letter and before beginning the extraction process. It would save me from editing the PRESETUP.CMD as below every time I make a change:

*SNIP*
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:

::Below added manually to show some sort of progress
start c:\install\trtprog.exe Please wait while drivers are extracted...

REM +==========================================================================+
REM |   Decompressing the DriverPacks to the harddisk.               
*SNIP*

BTW, this program runs well and displays a progress bar and my company logo for the duration of the extraction. If someone can tell me how to attach the program and/or it's VB source to a forum message (or somewhere else) I'm happy to.

Go to forum: Feature Requests