[Bâshrat the Sneaky] The proposed solution of using the ich7*, ich4core.* and 945.* files from the 6.05 with the rest of 6.09.1 does NOT work.
26 2006-09-30 06:13:43
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
27 2006-09-23 06:50:04
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
I performed a comparison of intel drivers that are included with 6.09.1 against 6.05.
Based on the hwids, the Dell OptiPlex GX520 uses the following:
6.05 6.09.1 Compare
====== ====== ======
ich7ide.inf ich7ide.inf Same version number
ich7id2.inf ich7id2.inf Same version number, except that 6.09.1 has moved the ich7id2.inf and ich7id2.cat file to \SP subfolder
ich7core.inf ich7core.inf Same version number
dmi_pci.inf dmi_pci.inf Same version number
ich4core.inf ich4core.inf Same version number
ich2br.inf ? ich2br.inf and ich2br.cat are no longer included in 6.09.1 (They are not part of the Dell or Intel download)
945.inf 945.inf Different version numbers, 6.09.1 uses 8.1.0 and 6.05 uses 7.2.2
I found it strange that the files ich2br.inf and ich2br.cat are no longer included in the dell and intel downloads. The hwids in the system refer to DEV_244E, which is referenced in ich2br.inf, dmi_pci.inf and ich4core.inf
Out of curiousity, I created another tiny driverpack that only included the 6.09.1 intel chipset drivers AND I added the ich2br.inf and inch2br.cat. It still fails.
Dell OptiPlex GX520 current status:
----------------------------------------
Success -> Only install Driverpack Chipset 6.05 (no other driverpacks used and no text mode mass storage drivers)
Success -> Only install Intel Driver that was included in Driverpack Chipset 6.05
Failure -> Only install Driverpack Chipset 6.09.1
Failure -> Only install Intel Driver that was included in Driverpack Chipset 6.09.1
Failure -> Only install Dell chipset driver (created tiny chipset driverpack that only contained this)
Failure -> Only install Intel Driver that was included in Driverpack Chipset 6.09.1 plus ich2br.inf and ich2br.cat
28 2006-09-23 04:56:06
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
I created a driverpack that only contained the Dell version 7.0.0.1019, which was downloaded using your link.
The problem still exists. I'm surprised.
On the failing systems, I am able to boot into "Safe mode with command prompt"
29 2006-09-22 08:47:07
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
I created an unattended install CD of Windows XP SP2 and only slipstreamed the ChipSet driverpack 6.09.1. I did not slipstream the text mode MassStorage drivers and did not slipstream any other driver packs.
Unfortunately, it still fails. The text mode portion of Windows XP install is successful. All of the T-minutes steps are also successful. When the system reboots, the Windows XP logo is presented and the three blue dots move across the screen, then the dots freeze and the computer automatically reboots. Upon reboot, Windows XP informs us that a prior reboot failed and we have the option to continue booting normally (which simply causes the failure and automatic reboot) or we have the option to boot into safe mode (which works).
Since I did not slipstream the MassStorage text mode drivers, I had to modify the Dell Optiplex GX520 BIOS setting for the SATA controller so that it will function in compatibility mode.
30 2006-09-20 11:53:30
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
I will attempt to narrow down the cause.
31 2006-09-13 06:00:18
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
HWIDS for Dell OptiPlex GX520
===========
PCI devices
===========
PCI\VEN_14E4&DEV_1677&SUBSYS_01AD1028&REV_01\4&117729E2&0&00E0: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_E1\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_02\3&172E68DD&0&00: Intel(R) 945G/GZ/P/PL Processor to I/O Controller - 2770
PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&172E68DD&0&08: Intel(R) 945G/GZ/P/PL PCI Express Root Port - 2771
PCI\VEN_8086&DEV_2772&SUBSYS_01AD1028&REV_02\3&172E68DD&0&10: Intel(R) 82945G Express Chipset Family
PCI\VEN_8086&DEV_2776&SUBSYS_01AD1028&REV_02\3&172E68DD&0&11: Intel(R) 82945G Express Chipset Family
PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01\3&172E68DD&0&F8: Intel(R) 82801GB/GR (ICH7 Family) LPC Interface Controller - 27B8
PCI\VEN_8086&DEV_27C0&SUBSYS_01AD1028&REV_01\3&172E68DD&0&FA: Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
PCI\VEN_8086&DEV_27C8&SUBSYS_01AD1028&REV_01\3&172E68DD&0&E8: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27C9&SUBSYS_01AD1028&REV_01\3&172E68DD&0&E9: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27CA&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EA: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27CB&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EB: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_27CC&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EF: Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&172E68DD&0&E0: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&172E68DD&0&E1: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D2
PCI\VEN_8086&DEV_27DA&SUBSYS_01AD1028&REV_01\3&172E68DD&0&FB: Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
PCI\VEN_8086&DEV_27DE&SUBSYS_01AD1028&REV_01\3&172E68DD&0&F2: SoundMAX Integrated Digital Audio
PCI\VEN_8086&DEV_27DF&SUBSYS_01AD1028&REV_01\3&172E68DD&0&F9: Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
18 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&19F1AF77&0 : USB Root Hub
USB\ROOT_HUB\4&2F60F7EA&0 : USB Root Hub
USB\ROOT_HUB\4&32C41A52&0 : USB Root Hub
USB\ROOT_HUB\4&4FC3F26&0 : USB Root Hub
USB\ROOT_HUB20\4&4F1A976&0 : USB 2.0 Root Hub
USB\VID_046D&PID_C016\5&345F6DD7&0&2 : USB Human Interface Device
USB\VID_04B4&PID_6560\5&2416E801&0&3 : Generic USB Hub
USB\VID_413C&PID_2005\5&345F6DD7&0&1 : USB Human Interface Device
8 matching device(s) found.
===========
PCI devices
===========
PCI\VEN_14E4&DEV_1677&SUBSYS_01AD1028&REV_01\4&117729E2&0&00E0: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_E1\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_02\3&172E68DD&0&00: Intel(R) 945G/GZ/P/PL Processor to I/O Controller - 2770
PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&172E68DD&0&08: Intel(R) 945G/GZ/P/PL PCI Express Root Port - 2771
PCI\VEN_8086&DEV_2772&SUBSYS_01AD1028&REV_02\3&172E68DD&0&10: Intel(R) 82945G Express Chipset Family
PCI\VEN_8086&DEV_2776&SUBSYS_01AD1028&REV_02\3&172E68DD&0&11: Intel(R) 82945G Express Chipset Family
PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01\3&172E68DD&0&F8: Intel(R) 82801GB/GR (ICH7 Family) LPC Interface Controller - 27B8
PCI\VEN_8086&DEV_27C0&SUBSYS_01AD1028&REV_01\3&172E68DD&0&FA: Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
PCI\VEN_8086&DEV_27C8&SUBSYS_01AD1028&REV_01\3&172E68DD&0&E8: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
PCI\VEN_8086&DEV_27C9&SUBSYS_01AD1028&REV_01\3&172E68DD&0&E9: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C9
PCI\VEN_8086&DEV_27CA&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EA: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CA
PCI\VEN_8086&DEV_27CB&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EB: Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27CB
PCI\VEN_8086&DEV_27CC&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EF: Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host Controller - 27CC
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&172E68DD&0&E0: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&172E68DD&0&E1: Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D2
PCI\VEN_8086&DEV_27DA&SUBSYS_01AD1028&REV_01\3&172E68DD&0&FB: Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
PCI\VEN_8086&DEV_27DE&SUBSYS_01AD1028&REV_01\3&172E68DD&0&F2: SoundMAX Integrated Digital Audio
PCI\VEN_8086&DEV_27DF&SUBSYS_01AD1028&REV_01\3&172E68DD&0&F9: Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
18 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&19F1AF77&0 : USB Root Hub
USB\ROOT_HUB\4&2F60F7EA&0 : USB Root Hub
USB\ROOT_HUB\4&32C41A52&0 : USB Root Hub
USB\ROOT_HUB\4&4FC3F26&0 : USB Root Hub
USB\ROOT_HUB20\4&4F1A976&0 : USB 2.0 Root Hub
USB\VID_046D&PID_C016\5&345F6DD7&0&2 : USB Human Interface Device
USB\VID_04B4&PID_6560\5&2416E801&0&3 : Generic USB Hub
USB\VID_413C&PID_2005\5&345F6DD7&0&1 : USB Human Interface Device
8 matching device(s) found.32 2006-09-09 05:41:41
Re: [FIXED in 7.06] Chipset 6.0.8 locks up Dell Optiplex GX520 (84 replies, posted in DriverPack Chipset)
I have also experienced the same problem with Dell OptiPlex GX520. The 6.05 version of the chipset driver pack worked correctly. However, 6.08 and 6.09 cause problems.
I can also help out in exploring a possible solution.
33 2006-08-17 03:26:12
Topic: Support for SYSPREP by splitting DPsFnshr.exe in two parts (1 replies, posted in Feature Requests)
I have been using version 6.07 and earlier with great success. The great success is because I have been able to perform unattended installs on just about any piece of hardware.
As you know, the downside of unattended installs is the time required. Thus, I have been creating SYSPREP ghost images for rapid deployment on just about any piece of hardware (Great thing is that you only need two images to support a lot of hardware....One of the images is constructed on a legacy ACPI HAL and the second one on a MULTIPROCESSOR ACPI HAL).
For SYSPREP'ing, I have been using the following procedure:
1) Create an unattended install with KTD enabled that only includes the driver packs for CPU, Chip Set, Mass Storage
2) Copied the remaining driver packs to \OEM2 (Graphics, Sound, LAN, WLAN)
3) Split the 6.07 "DPs_fnsh.cmd" command into two separate parts: "DPs_fnsh1.cmd" and "DPS_fnsh2.cmd"
DPs_fnsh1 would move all of the \OEM2 files to the \OEM folder
DPs_fnsh1 would integrate all of the driver packs located in \OEM
4) Modify GUIRunOnce or cmdlines.txt to only execute DPs_fnsh1.cmd
5) Load the modified unattended install on a donor computer. The donor computer will only have drivers for CPU, ChipSet and MassStorage.
6) The donor computer has SYSPREP tools installed.
Modify SYSPREP CMDLINES.TXT that would also execute DPS_fnsh2.cmd at the end of SYSPREP
Modify SYSPREP.INF that has BuildMassStorage=Yes
7) Execute SYSPREP.EXE with the options to use mini-setup, redect pnp, regen SID, shutdown
8) After shutdown, capture GHOST image
9) Load GHOST image on target computer
10) Start the target computer, which executes the SYSPREP mini-setup
The detection of plug-n-play hardware occurs during the mini-setup and all of the integrated driver packs are used.
At the end of mini-setup, DPSFnsh2 would install the graphics control panel and sound control panel based on the hardware of the target computer.
This was easily accomplished with 6.07 and earlier because the source for DPs_fnsh.cmd was available.
Is it possible to achieve this behavior the new 6.08 DPsFnshr.exe? Maybe DPsFnshr.exe can be split into two sections... or add a parm to DPsFnshr.ini and allow for an option to indicate which ini file to use (DPsFnshr.exe -inifile=filename).
Thanks again and great work!
34 2006-06-28 04:43:46
Topic: SOLVED: ATI CCC/CCP not installed due to problem in DPs_fnsh.cmd (1 replies, posted in DriverPack Graphics)
The Graphics_A ATI Mobility Radeon & Mobility FireGL device driver is located in D\G\A\2.
The folder contains CX_32468.inf and it specifies that the following devices will load atioglgl.dll.
ATI Mobility FireGL T2/T2e PCI\VEN_1002&DEV_4E54
ATI Mobility FireGL V3100 PCI\VEN_1002&DEV_5464
ATI Mobility FireGL V3200 PCI\VEN_1002&DEV_3154
ATI Mobility FireGL V5000 PCI\VEN_1002&DEV_564B
ATI Mobility FireGL V5200 PCI\VEN_1002&DEV_71C4
ATI Mobility Radeon 9500 PCI\VEN_1002&DEV_4E52
ATI Mobility Radeon X1600 PCI\VEN_1002&DEV_71C5
ATI Mobility RADEON X300 PCI\VEN_1002&DEV_3152
ATI Mobility RADEON X300 PCI\VEN_1002&DEV_5460
ATI Mobility RADEON X600 PCI\VEN_1002&DEV_3150
ATI Mobility RADEON X600 SE PCI\VEN_1002&DEV_5462
ATI Mobility RADEON X700 PCI\VEN_1002&DEV_5653
ATI Mobility RADEON X700 PCI\VEN_1002&DEV_5652The current version of DPs_fnsh.cmd checks for the existence of certain ATI DLLs inorder to install the appropriate ATI control center/panel.
DPs_fnsh.cmd has a problem because it simply checks for the existence of atioglgl.dll and it installs the Graphics_C control center/panel. This is a problem because the Graphics_A devices listed above should have the Graphics_A controa center/panel installed and NOT the Graphics_C version.
The previously listed devices should not use the Graphics_C control panel. Since they load atioglgl.dll, the DPs_fnsh.cmd forces the install of the Graphics_C control panel.
Instead, they should have the Graphics_A control panel ATICCC/ATICCP loaded.
Unfortunately, installing the Graphics_C control panel causes a memory error that causes an error popup message at logon.
The other 12 devices listed in CX_32468.inf specifies that they will load atioglxx.dll, atioglx1.dll.
Maybe the logic in DPs_fnsh.cmd should be changed to perform a DEVCON for all the Graphics_A related devices and load the ATICCC/ATICCP.
35 2006-06-07 13:14:34
Topic: [IMPLEMENTED] updated: Intel Matrix Storage Manager: 6.0.0.1002 (4 replies, posted in DriverPack Mass Storage)
Intel has released version 6.0.0.1002 of the "Intel Matrix Storage Manager". released June 6, 2006
The new text-mode install version (floppy version) is available at
http://downloadfinder.intel.com/scripts … p;lang=eng
The current MassStroage Driver pack needs to be updated to include the new driver files and also integrate the following devices ids into txtsetup.sif and dosnet.inf
"PCI\VEN_8086&DEV_2681&CC_0106 = \"iastor\""
"PCI\VEN_8086&DEV_2821&CC_0106 = \"iastor\""
"PCI\VEN_8086&DEV_2822&CC_0104 = \"iastor\""
"PCI\VEN_8086&DEV_27C6&CC_0104 = \"iastor\""
"PCI\VEN_8086&DEV_2682&CC_0104 = \"iastor\""With the new GUI, I don't know how to easily perform the integration. In the older .cmd file versions, you could have added the previous lines to SlipStream_DPM.cmd file and updated DriverPacks_Massstorage_###.7z so that the D\M\IN\1 folder is replaced with the new driver.
The latest driver supports the following hardware:
PCI\VEN_8086&DEV_2652&CC_0104.DeviceDesc = "Intel(R) 82801FR SATA RAID Controller"
PCI\VEN_8086&DEV_27C3&CC_0104.DeviceDesc = "Intel(R) 82801GR/GH SATA RAID Controller"
PCI\VEN_8086&DEV_2682&CC_0104.DeviceDesc = "Intel(R) 631xESB/632xESB SATA RAID Controller"
PCI\VEN_8086&DEV_27C6&CC_0104.DeviceDesc = "Intel(R) 82801GHM SATA RAID Controller"
PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc = "Intel(R) ICH8R/DO/DH SATA RAID Controller"
PCI\VEN_8086&DEV_2652&CC_0106.DeviceDesc = "Intel(R) 82801FR SATA AHCI Controller"
PCI\VEN_8086&DEV_2653&CC_0106.DeviceDesc = "Intel(R) 82801FBM SATA AHCI Controller"
PCI\VEN_8086&DEV_27C1&CC_0106.DeviceDesc = "Intel(R) 82801GR/GH SATA AHCI Controller"
PCI\VEN_8086&DEV_27C5&CC_0106.DeviceDesc = "Intel(R) 82801GBM SATA AHCI Controller"
PCI\VEN_8086&DEV_2681&CC_0106.DeviceDesc = "Intel(R) 631xESB/632xESB SATA AHCI Controller"
PCI\VEN_8086&DEV_2821&CC_0106.DeviceDesc = "Intel(R) ICH8R/DO/DH SATA AHCI Controller"36 2006-06-07 07:06:40
Re: IMPLEMENTED: Finishing scripts feature requests (5 replies, posted in Feature Requests)
The current DPs_fnsh.cmd performs two major tasks in one command file:
1) Install the graphics and sound control panels
2) KtD (Keep the drivers)
Is it possible for you to break these 2 steps into individual "finishing command" files. One for installing control panels and another for KtD.
If they are split into two files, we could execute the following steps for a clean sysprep process:
1) Run "KtD" finish command file at the end of the unattended install (For syspreping, you will want to keep the drivers).
2) Follow this with silent installation of applications.
3) Perform a SYSPREP (which would leverage all of the KtD drivers).
4) At the end of the sysprep setup, run the "Install Control Panels" by adding the command to the Sysprep RunOnceEx.
5) An optional final cleanup step can be added to end of the sysprep RunOnceEx which would either KtD keep or remove the drivers.
As a result, we can install the unattended on "any" hardware and capture the sysprep'ed image. Once the sysprep'ed image is loaded on the new target hardware, the proper control panels will be installed based on the loading of certain devices.
Thanks
P.S. I put "any" in quotes because you can only use the sysprep'ed image on a target machine with a similar HAL.
37 2006-06-07 06:52:56
Topic: SOLVED BUG #66: DPS_fnsh.cmd: missing a "(" in the cleanup section (1 replies, posted in Feedback and Support - DriverPacks Base)
The DPs_fnsh.cmd file currently contains
IF method==1 then
DEL /F /Q %SystemDrive%\CloseDSP.exe
DEL /F /Q %SystemDrive%\hideMakePNF.exe
DEL /F /Q %SystemDrive%\robocopy.exe
DEL /F /Q %SystemDrive%\WatchDSP.exe
IF EXIST %SystemDrive%\KTDpaths.cmd DEL /F /Q %SystemDrive%\KTDpaths.cmd
IF EXIST %SystemDrive%\KTDpatterns.cmd DEL /F /Q %SystemDrive%\KTDpatterns.cmd
)It is missing a ( after the 'then" statement.
If should contain
IF method==1 then (
DEL /F /Q %SystemDrive%\CloseDSP.exe
DEL /F /Q %SystemDrive%\hideMakePNF.exe
DEL /F /Q %SystemDrive%\robocopy.exe
DEL /F /Q %SystemDrive%\WatchDSP.exe
IF EXIST %SystemDrive%\KTDpaths.cmd DEL /F /Q %SystemDrive%\KTDpaths.cmd
IF EXIST %SystemDrive%\KTDpatterns.cmd DEL /F /Q %SystemDrive%\KTDpatterns.cmd
)