• candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Topic: v1209 Pack issue with IASTOR and FST376XP

I took this post as inspiration to help me solve(ish) the following issue;

I initally had a problem recgonising the ICH5R chipset on a P4C800-E Deluxe (i875) motherboard using the latest Driverpack for MassStorage. It did recognise the Promise Controller, but when getting through to the WinXP Setup screen to choose a partition/disk to install on, I got only the following to choose from;

610486 Mb Disk 0 at Id 0 on bus 0 on Unknown [MBR]

** Note the "Unknown"

I didn't think much of the "Unknown" bit, but was concerned I couldn't see the HDDs connected to the Intel Controller...

After reading lots of posts here, I tried multiple things;
1. Disabling the Promise Controller - Result: Windows reported no available hard disks
2. Trimming down all Driverpacks to just MassStorage and Chipset - Result: Unknown Controller
3. Using older Driverpacks (every one sine 1108!) - Result: Unknown Controller
4. I then started taking the latest Driverpack apart to look for anything obvious - Nothing obvious, Result: Unknown Controller

I then started commenting out lines (;) in the SCSI.load part of txtsetup.sif, and narrowed it down to just one driver;

MegaINTL=MegaINTL.sys,4

Commenting (;) out this one line allows me to use my newly created XP disk.

Now looking at the HWIDs in the INFs, the above driver has something very similar to the iastor;

iastor - PCI\VEN_8086&DEV_24DF
MegaINTL - PCI\VEN_8086&DEV_24df&SUBSYS_34......

This is where my engine runs out of steam, got no idea how to fix it... Maybe I should try changing the order in the TXTSETUP.SIF file, ie. putting iastor above MegaINTL...?? Is there a proper fix to be able be added to the Official MassStorage pack??

As this is my first post, I thought I'd try and cover every angle as best I could, but I am sure I missed something, so if I have many apologies and hope you can see I have tried!!

I love these packs and up until now had no problems whatsoever for years - Thank you so much for all who have contributed to making this an amazing resource.

I also include a list of HWIDs below;

=========== 
PCI Devices 
=========== 
PCI\VEN_1002&DEV_4B49&SUBSYS_6186148C&REV_00\4&1A99067F&0&0008: RADEON X850 Series   
PCI\VEN_1002&DEV_4B69&SUBSYS_6187148C&REV_00\4&1A99067F&0&0108: RADEON X850 Series - Secondary   
PCI\VEN_105A&DEV_3373&SUBSYS_80F51043&REV_02\4&2E98101C&0&20F0: WinXP Promise FastTrak 378 (tm) Controller
PCI\VEN_1106&DEV_3044&SUBSYS_808A1043&REV_80\4&2E98101C&0&18F0: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1131&DEV_7133&SUBSYS_C900185B&REV_D1\4&2E98101C&0&68F0: VideoMate TV SAA7133/35, Hybrid Capture Device
PCI\VEN_8086&DEV_1019&SUBSYS_80F71043&REV_00\4&3B3CB9B1&0&0818: Intel(R) PRO/1000 CT Network Connection
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&267A616A&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&267A616A&0&F8: Intel(R) 82801EB LPC Interface Controller - 24D0
PCI\VEN_8086&DEV_24D2&SUBSYS_80A61043&REV_02\3&267A616A&0&E8: Intel(R) 82801EB USB Universal Host Controller - 24D2
PCI\VEN_8086&DEV_24D3&SUBSYS_80A61043&REV_02\3&267A616A&0&FB: Intel(R) 82801EB SMBus Controller - 24D3
PCI\VEN_8086&DEV_24D4&SUBSYS_80A61043&REV_02\3&267A616A&0&E9: Intel(R) 82801EB USB Universal Host Controller - 24D4
PCI\VEN_8086&DEV_24D5&SUBSYS_80F31043&REV_02\3&267A616A&0&FD: Digital Audio MB
PCI\VEN_8086&DEV_24D7&SUBSYS_80A61043&REV_02\3&267A616A&0&EA: Intel(R) 82801EB USB Universal Host Controller - 24D7
PCI\VEN_8086&DEV_24DB&SUBSYS_80A61043&REV_02\3&267A616A&0&F9: Intel(R) 82801EB Ultra ATA Storage Controllers
PCI\VEN_8086&DEV_24DD&SUBSYS_80A61043&REV_02\3&267A616A&0&EF: Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
PCI\VEN_8086&DEV_24DE&SUBSYS_80A61043&REV_02\3&267A616A&0&EB: Intel(R) 82801EB USB Universal Host Controller - 24DE
PCI\VEN_8086&DEV_24DF&SUBSYS_80A61043&REV_02\3&267A616A&0&FA: Intel(R) 82801ER SATA RAID Controller
PCI\VEN_8086&DEV_2578&SUBSYS_00000000&REV_02\3&267A616A&0&00: Intel(R) 82875P/E7210 Memory Controller Hub - 2578
PCI\VEN_8086&DEV_2579&SUBSYS_00000000&REV_02\3&267A616A&0&08: Intel(R) 82875P Processor to AGP Controller - 2579
PCI\VEN_8086&DEV_257B&SUBSYS_00000000&REV_02\3&267A616A&0&18: Intel(R) 82875P/E7210 Processor to PCI to CSA bridge - 257B
20 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&1C4B7D9B&0                                   : USB Root Hub
USB\ROOT_HUB\4&1FCB28C&0                                    : USB Root Hub
USB\ROOT_HUB\4&24D2BE59&0                                   : USB Root Hub
USB\ROOT_HUB\4&CB41D3B&0                                    : USB Root Hub
USB\ROOT_HUB20\4&F180E13&0                                  : USB Root Hub
USB\VID_046D&PID_C52B\5&200E9ECA&0&2                        : USB Composite Device
USB\VID_046D&PID_C52B&MI_00\6&820E117&0&0000                : USB Human Interface Device
USB\VID_046D&PID_C52B&MI_01\6&820E117&0&0001                : USB Human Interface Device
USB\VID_046D&PID_C52B&MI_02\6&820E117&0&0002                : USB Human Interface Device
9 matching device(s) found.
 
============= 
Input Devices 
============= 
HID\COMPROHIDDEVICE&COL01\1&2D595CA7&1&0000                 : HID-compliant device
HID\COMPROHIDDEVICE&COL02\1&2D595CA7&1&0001                 : HID-compliant consumer control device
HID\COMPROHIDDEVICE&COL03\1&2D595CA7&1&0002                 : HID-compliant device
HID\COMPROHIDDEVICE&COL04\1&2D595CA7&1&0003                 : HID-compliant device
HID\COMPROHIDDEVICE&COL05\1&2D595CA7&1&0004                 : HID Keyboard Device
HID\VID_046D&PID_C52B&MI_00\7&32D56798&0&0000               : HID Keyboard Device
HID\VID_046D&PID_C52B&MI_01&COL01\7&72A1E15&0&0000          : HID-compliant mouse
HID\VID_046D&PID_C52B&MI_01&COL02\7&72A1E15&0&0001          : HID-compliant consumer control device
HID\VID_046D&PID_C52B&MI_01&COL03\7&72A1E15&0&0002          : HID-compliant device
HID\VID_046D&PID_C52B&MI_01&COL04\7&72A1E15&0&0003          : HID-compliant device
HID\VID_046D&PID_C52B&MI_02&COL01\7&2F94CBDE&0&0000         : HID-compliant device
HID\VID_046D&PID_C52B&MI_02&COL02\7&2F94CBDE&0&0001         : HID-compliant device
HID\VID_046D&PID_C52B&MI_02&COL03\7&2F94CBDE&0&0002         : HID-compliant device
13 matching device(s) found.
 
============ 
ACPI Devices 
============ 
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_4\_0                : Intel(R) Pentium(R) 4 CPU 3.40GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_4\_1                : Intel(R) Pentium(R) 4 CPU 3.40GHz
ACPI\PNP0000\4&35F762C4&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&35F762C4&0                                   : System timer
ACPI\PNP0200\4&35F762C4&0                                   : Direct memory access controller
ACPI\PNP0700\4&35F762C4&0                                   : Standard floppy disk controller
ACPI\PNP0800\4&35F762C4&0                                   : System speaker
ACPI\PNP0A03\0                                              : PCI bus
ACPI\PNP0A06\3&473F1A46&0                                   : Extended IO Bus
ACPI\PNP0B00\4&35F762C4&0                                   : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C02\0                                              : Motherboard resources
ACPI\PNP0C02\10                                             : Motherboard resources
ACPI\PNP0C02\2E                                             : Motherboard resources
ACPI\PNP0C02\3F6                                            : Motherboard resources
ACPI\PNP0C04\4&35F762C4&0                                   : Numeric data processor
ACPI\PNP0C0C\AA                                             : ACPI Power Button
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
20 matching device(s) found.
 
============ 
 HDA Audio 
============ 
No matching devices found.
 
============ 
RAID Devices 
============ 
PCI\VEN_105A&DEV_3373&SUBSYS_80F51043&REV_02\4&2E98101C&0&20F0
    Name: WinXP Promise FastTrak 378 (tm) Controller
    Hardware ID's:
        PCI\VEN_105A&DEV_3373&SUBSYS_80F51043&REV_02
        PCI\VEN_105A&DEV_3373&SUBSYS_80F51043
        PCI\VEN_105A&DEV_3373&CC_010400
        PCI\VEN_105A&DEV_3373&CC_0104
    Compatible ID's:
        PCI\VEN_105A&DEV_3373&REV_02
        PCI\VEN_105A&DEV_3373
        PCI\VEN_105A&CC_010400
        PCI\VEN_105A&CC_0104
        PCI\VEN_105A
        PCI\CC_010400
        PCI\CC_0104
PCI\VEN_8086&DEV_24DB&SUBSYS_80A61043&REV_02\3&267A616A&0&F9
    Name: Intel(R) 82801EB Ultra ATA Storage Controllers
    Hardware ID's:
        PCI\VEN_8086&DEV_24DB&SUBSYS_80A61043&REV_02
        PCI\VEN_8086&DEV_24DB&SUBSYS_80A61043
        PCI\VEN_8086&DEV_24DB&CC_01018F
        PCI\VEN_8086&DEV_24DB&CC_0101
    Compatible ID's:
        PCI\VEN_8086&DEV_24DB&REV_02
        PCI\VEN_8086&DEV_24DB
        PCI\VEN_8086&CC_01018F
        PCI\VEN_8086&CC_0101
        PCI\VEN_8086
        PCI\CC_01018F
        PCI\CC_0101
PCI\VEN_8086&DEV_24DF&SUBSYS_80A61043&REV_02\3&267A616A&0&FA
    Name: Intel(R) 82801ER SATA RAID Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_24DF&SUBSYS_80A61043&REV_02
        PCI\VEN_8086&DEV_24DF&SUBSYS_80A61043
        PCI\VEN_8086&DEV_24DF&CC_01048F
        PCI\VEN_8086&DEV_24DF&CC_0104
    Compatible ID's:
        PCI\VEN_8086&DEV_24DF&REV_02
        PCI\VEN_8086&DEV_24DF
        PCI\VEN_8086&CC_01048F
        PCI\VEN_8086&CC_0104
        PCI\VEN_8086
        PCI\CC_01048F
        PCI\CC_0104
SCSI\DISK&VEN_PROMISE&PROD_2+0_STRIPE/RAID0&REV_1.10\5&11D7DDFD&0&000
    Name: Promise 2+0 Stripe/RAID0 SCSI Disk Device
    Hardware ID's:
        SCSI\DiskPromise_2+0_Stripe/RAID01.10
        SCSI\DiskPromise_2+0_Stripe/RAID0
        SCSI\DiskPromise_
        SCSI\Promise_2+0_Stripe/RAID01
        Promise_2+0_Stripe/RAID01
        GenDisk
    Compatible ID's:
        SCSI\Disk
        SCSI\RAW
SCSI\PROCESSOR&VEN_PROMISE&PROD_RAID_CONSOLE&REV_1.00\5&11D7DDFD&0&040
    Name: WinXP Promise RAID Console SCSI Processor Device
    Hardware ID's:
        SCSI\ProcessorPromise_RAID_Console____1.00
        SCSI\ProcessorPromise_RAID_Console____
        SCSI\ProcessorPromise_
        SCSI\Promise_RAID_Console____1
        Promise_RAID_Console____1
    Compatible ID's:
        SCSI\Processor
        SCSI\RAW
5 matching device(s) found.
  • Registered: 2012-09-13
  • Posts: 170

Re: v1209 Pack issue with IASTOR and FST376XP

Try switching off RAID in your BIOS

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Damnation wrote:

Try switching off RAID in your BIOS

I would love to, but that would mean no RAID for me!

I can completely confirm that by commenting out that one line in TXTSETUP.SIF, I can see both Promise and Intel controllers and attached RAIDed drives. I have just done a complete reinstall with only that change.

Which solves my problem, but not really "fix" the Mass Storage Driver pack for the masses (ahem...).

  • TechDud
  • Researcher & DriverPacks Moderator
  • Offline
  • From: Fraser Valley, Canada
  • Registered: 2010-11-23
  • Posts: 2,270

Re: v1209 Pack issue with IASTOR and FST376XP

Could you post your DP_BASE.log, please.

In the mean time, one could remove or rename  D\M\L\MegaINTL.INF  from MassStorage, then reintegrate with Chipset/MassStorage utilizing DP_BASE.

"LSI Logic Corporation.      Intel Embedded Server RAID Technology      06/30/2006,4.4.0630.2006"
Quoted from http://driverpacks.net/node/795/drivers

Although, i note that your RAID HWid is not present including the proper SUBSYS ID in that .Inf file.


After noting that this board came with "Trend Micro PC-cillin 2002 anti-virus software",
I'm sensing a hardware issue.

  Does it pass memtest? (use a non-contact Infrared thermometer to monitor thermals whilst 'memtesting'; anything above 65°C is cause for concern).


Since you are using a 3.4GHz chip, ensure that a quality power supply is used (not light-weight).  Quickly check the condition of the capacitors on the board (especially by the chipset, by the end of the AGP slot to the P/S connector, & beside the CPU), to ensure they are not bulging or leaking.  Power supplies are notorious for hiding blown capacitors, too; (warning High-Voltage inside, potentially even with power off).  It is easiest to replace the power supply with a known-good unit for testing.

  Ensure the CMOS battery is renewed, too.  Ensure that you are using the latest BIOS; do not attempt if you are unfamilliar - you could 'brick' your board!  Don't forget to load the defaults in BIOS afterwards.

Ensure the mobo is free of dust & detritus.  Dust harbors metallic particles, including some that generate static charges spontaneously; it is not your computer's friend, nor yours, really.

Hardware issues can spur weird consequences in software.

Last edited by TechDud (2012-10-03 17:46:19)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)
http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/5NQ1BpqvDa_0vDwtHeoZCcSJjOVNuvMXSp4i7SE7DQA/perpetual:forever/userbar/moderator-1.png
  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: v1209 Pack issue with IASTOR and FST376XP

Welcome to DriverPacks.
That's an excellent first post.  You posted nearly all the info we need.
That's an odd problem too.  Is your RAID controller an Intel-branded chip or Promise-branded?

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • Registered: 2012-09-13
  • Posts: 170

Re: v1209 Pack issue with IASTOR and FST376XP

I'm just wondering why is this HWID

PCI\VEN_8086&DEV_24DF

Is used for both

Intel 82801ER/6300ESB SATA RAID 5.5

as well as

LSI Logic MegaRAID IDE for INTEL

in the masstorage.ini
is this a driver conflict? or is there a reason for this?

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

TechDud wrote:

Could you post your DP_BASE.log, please.

In the mean time, one could remove or rename  D\M\L\MegaINTL.INF  from MassStorage, then reintegrate with Chipset/MassStorage utilizing DP_BASE.

"LSI Logic Corporation.      Intel Embedded Server RAID Technology      06/30/2006,4.4.0630.2006"
Quoted from http://driverpacks.net/node/795/drivers

Although, i note that your RAID HWid is not present including the proper SUBSYS ID in that .Inf file.

Thanks for the reply, I will add the logs at the bottom of this post.

With regards Hardware issues;


TechDud wrote:

  Does it pass memtest? (use a non-contact Infrared thermometer to monitor thermals whilst 'memtesting'; anything above 65°C is cause for concern).

It does pass memtest, sadly I don't have thermal montioring kit! - Here's a bit of backgroud - Funnily enough I was experiencing strange BSOD issues a while ago, hence the reason I was looking at reinstalling the OS, it did pass Memtest then and I ghosted an old image and the BSODs disappeared - but I still wanted to reinstall the OS with new Hotfixes/drivers/etc - So I started building a new XP installation disk a week ago using my tried and trusted method using APUP to download Hotfixes for XP SP3, nLite to slipstream HFs and customise the disk and Driverpacks to slipstream the Drivers. However, I ran into the problem above - so I changed to the basics, a standard XP SP3 disk and driver packs - No APUP and no nLite...

TechDud wrote:

After noting that this board came with "Trend Micro PC-cillin 2002 anti-virus software",
I'm sensing a hardware issue.

Not that I don't believe you - but could you help me make understand why a software bundle suggests a hardware issue!? wink I am guessing that you mean that the board is quite old!

TechDud wrote:

Since you are using a 3.4GHz chip, ensure that a quality power supply is used (not light-weight).  Quickly check the condition of the capacitors on the board (especially by the chipset, by the end of the AGP slot to the P/S connector, & beside the CPU), to ensure they are not bulging or leaking.  Power supplies are notorious for hiding blown capacitors, too; (warning High-Voltage inside, potentially even with power off).  It is easiest to replace the power supply with a known-good unit for testing.

The PSU is more than sufficient - when I built the box - I didn't scrimp on this (or any!) component! It has blue LEDs and funky sounding name and I am pretty sure it was an Enermax... other than that, I can't remember what it is off the top off my head! But good call...

Good call also for the capacitor condition - there was an issue with some of these boards with cheap capacitors (popping, leaking, bulges, etc) - but last check (relatively) recently showed they were still good.

TechDud wrote:

Ensure the CMOS battery is renewed, too.  Ensure that you are using the latest BIOS; do not attempt if you are unfamilliar - you could 'brick' your board!  Don't forget to load the defaults in BIOS afterwards.

CMOS battery, again, something I did change in the last round of BSOD screens... With regards the BIOS, the latest was a beta 1024.001 from memory - ASUS never released a "proper" one.

TechDud wrote:

Ensure the mobo is free of dust & detritus.  Dust harbors metallic particles, including some that generate static charges spontaneously; it is not your computer's friend, nor yours, really.

Always good advice, I am a clean freak, so this should be good too...

TechDud wrote:

Hardware issues can spur weird consequences in software.

I am not completely convinced it is a hardware fault. If I can resolve the issue by commenting out one line in TXTSETUP.SIF and consistantly show the fault with the offending line uncommented. If it were a hardware fault, I would see less consistancy in the behaviour of the box - this is very specific behaviour to Drivers and just happens to be very similar to the MegaINTL driver set as per your original observation.

Notwithstanding all of this, you are totally right, my above statement does not in any way disprove a hardware fault! However, I would say that reverting back to APUP, nlite, driver packs and commenting out that line has left me with a rock steady machine without BSODs and using quite apps that are CPU and mem intensive...

Thank you for your help so far!

This is the successful driver slipstreaming instance that I have used to create my "rock solid" system;

2012-10-02 15:24:58 : <INIT> DriverPacks BASE 10.06 initialized.
2012-10-02 15:24:58 : <INIT> Host environment: WIN_XP Service Pack 3 X86 on a X64 CPU.
2012-10-02 15:24:58 : <INIT> Created temporary working directory.
2012-10-02 15:24:58 : <INIT> Imported proxy settings from Internet Explorer.
2012-10-02 15:24:58 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Chipset 1209!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack CPU 1005!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Graphics A 1206!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Graphics B 1206!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Graphics C 1206!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack LAN 1205!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Mass Storage 1209!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Sound A 1111!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack Sound B 1111!
2012-10-02 15:24:58 : <INIT> 	Detected DriverPack WLAN 1202!
2012-10-02 15:24:58 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2012-10-02 15:24:58 : <INIT> 	Finished scanning.
2012-10-02 15:24:58 : <INIT> Detected settings file "C:\XP CD\Driverpack\DPs_BASE.ini".
2012-10-02 15:24:58 : <INIT> Windows XP Professional -  Retail SP3 detected.
2012-10-02 15:24:58 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2012-10-02 15:24:58 : <INIT> Imported settings from settings file.
2012-10-02 15:24:58 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2012-10-02 15:24:58 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2012-10-02 15:24:58 : <GUI>  Initialized GUI.
2012-10-02 15:24:58 : <GUI>  Created a list of all available language files.
2012-10-02 15:24:58 : <GUI>  Set the last used language, English, as the GUI language.
2012-10-02 15:25:03 : <GUI>  Refreshed UpdateChecker with success.
2012-10-02 15:27:09 : <GUI>  Saved settings!
2012-10-02 15:27:09 : <GUI>  Closed GUI.
2012-10-02 15:27:09 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2012-10-02 15:27:09 : <PREP> Removed all attributes from \I386.
2012-10-02 15:27:09 : <PREP> No previous DriverPacks installation found, Prep stage will be skipped
2012-10-02 15:27:09 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2012-10-02 15:27:09 : <SLIP> C:\XP CD\Driverpack\QSC\wnt5_x86-32_uni_DP_MassStorage_1209_textmode\DriverPack_MassStorage_wnt5_x86-32.ini
2012-10-02 15:27:11 : <SLIP> Processing Mass Storage files now. This may take a minute.
2012-10-02 15:27:19 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2012-10-02 15:27:19 : <SLIP> txtsetup.sif Backed-up Successfully
2012-10-02 15:27:19 : <SLIP> dosnet.inf Backed-up Successfully
2012-10-02 15:27:29 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2012-10-02 15:27:30 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2012-10-02 15:28:12 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2012-10-02 15:28:12 : <SLIP> Created necessary directory structure for method 2.
2012-10-02 15:28:12 : <SLIP> Copying files necessary for method 2.
2012-10-02 15:28:12 : <SLIP> Extracted additional files necessary for method 2.
2012-10-02 15:28:12 : <SLIP> expanded setup.ex_ to setuporg.exe
2012-10-02 15:28:12 : <SLIP> SETUP.EX_ Backed-up Successfully
2012-10-02 15:28:13 : <SLIP> Compressed setup.exe to SETUP.EX_.
2012-10-02 15:28:13 : <SLIP> Method 2 setup.ex_ installed
2012-10-02 15:28:13 : <SLIP> Created \I386\presetup.cmd file.
2012-10-02 15:28:13 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2012-10-02 15:28:13 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2012-10-02 15:28:13 : <SLIP> Copied DriverPack Chipset to \OEM.
2012-10-02 15:28:13 : <SLIP> Copied DriverPack CPU to \OEM.
2012-10-02 15:28:15 : <SLIP> Copied DriverPack Graphics A to \OEM.
2012-10-02 15:28:21 : <SLIP> Copied DriverPack Graphics B to \OEM.
2012-10-02 15:28:22 : <SLIP> Copied DriverPack Graphics C to \OEM.
2012-10-02 15:28:22 : <SLIP> Copied DriverPack LAN to \OEM.
2012-10-02 15:28:23 : <SLIP> Copied DriverPack Mass Storage to \OEM.
2012-10-02 15:28:25 : <SLIP> Copied DriverPack Sound A to \OEM.
2012-10-02 15:28:27 : <SLIP> Copied DriverPack Sound B to \OEM.
2012-10-02 15:28:28 : <SLIP> Copied DriverPack WLAN to \OEM.
2012-10-02 15:28:28 : <SLIP> Copied DriverPacks to \OEM.
2012-10-02 15:28:29 : <SLIP> Will not slipstream patches, Service Pack 3 was detected.
2012-10-02 15:28:29 : <SLIP> WINNT.SIF Backed-up Successfully
2012-10-02 15:28:29 : <SLIP> Updated \I386\winnt.sif to support method 2.
2012-10-02 15:28:29 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2012-10-02 15:28:29 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2012-10-02 15:28:29 : <SLIP> DP_Install_Tool was copied successfully
2012-10-02 15:28:29 : <SLIP> Slipstream finished in 1 minutes and 20 seconds.
2012-10-02 15:30:37 : <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:\XP CD\SOURCE"
; 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		= "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming Graphics DriverPack)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl		= "CCP"
Nvidia_cpl	= "2"
2012-10-02 15:30:37 : <CLNP> Create a DPs_Base.log backup @ C:\XP CD\Driverpack\LogFiles\DPs_BASE_12-10-02_15-30.log
2012-10-02 15:30:37 : <CLNP> Program terminated.

This is the log that I used to create ISOs of XP SP3 with just MassStorage, CPU and Chipset drivers - I then manually edited the TXTSETUP.SIF commenting out drivers in [SCSI.Load] to narrow it down to the MegaINTL.sys line;

2012-10-02 10:32:02 : <INIT> DriverPacks BASE 10.06 initialized.
2012-10-02 10:32:02 : <INIT> Host environment: WIN_XP Service Pack 3 X86 on a X64 CPU.
2012-10-02 10:32:02 : <INIT> Created temporary working directory.
2012-10-02 10:32:02 : <INIT> Imported proxy settings from Internet Explorer.
2012-10-02 10:32:02 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2012-10-02 10:32:02 : <INIT> 	Detected DriverPack Chipset 1209!
2012-10-02 10:32:02 : <INIT> 	Detected DriverPack CPU 1005!
2012-10-02 10:32:02 : <INIT> 	Detected DriverPack Mass Storage 1209!
2012-10-02 10:32:02 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2012-10-02 10:32:02 : <INIT> 	Finished scanning.
2012-10-02 10:32:02 : <INIT> Detected settings file "C:\XP CD\Driverpack\DPs_BASE.ini".
2012-10-02 10:32:02 : <INIT> Windows XP Professional -  Retail SP3 detected.
2012-10-02 10:32:02 : <INIT> wnt5_x86-32_disc is the selected installation platform .
2012-10-02 10:32:02 : <INIT> Imported settings from settings file.
2012-10-02 10:32:03 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2012-10-02 10:32:03 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2012-10-02 10:32:03 : <GUI>  Initialized GUI.
2012-10-02 10:32:03 : <GUI>  Created a list of all available language files.
2012-10-02 10:32:03 : <GUI>  Set the last used language, English, as the GUI language.
2012-10-02 10:32:05 : <GUI>  Refreshed UpdateChecker with success.
2012-10-02 10:32:32 : <GUI>  Saved settings!
2012-10-02 10:32:32 : <GUI>  Closed GUI.
2012-10-02 10:32:32 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2012-10-02 10:32:37 : <PREP> Removed all attributes from \I386.
2012-10-02 10:32:37 : <PREP> \I386\winnt.org was not found, \I386\winnt.sif was not restored.
2012-10-02 10:32:37 : <PREP> Restored \I386\txtsetup.sif.
2012-10-02 10:32:37 : <PREP> Restored \I386\dosnet.inf.
2012-10-02 10:32:37 : <PREP> C:\XP CD\SOURCE\I386\DriverPack_MassStorage_wnt5_x86-32.ini
2012-10-02 10:32:38 : <PREP> Restored \I386\DPTI2O.SY_.
2012-10-02 10:32:38 : <PREP> Restored \I386\adpu160m.SY_.
2012-10-02 10:32:38 : <PREP> Restored \I386\symc8xx.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\symc810.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\sym_hi.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\perc2.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\dac2w2k.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\dac960nt.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\mraid35x.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\ultra.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\ql12160.SY_.
2012-10-02 10:32:39 : <PREP> Restored \I386\viaide.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\3waregsm.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\3wDrv100.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\3wareDrv.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec6210.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec6260.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec6280.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec68x5.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec6880.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec6897.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec67160.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aec671x.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aar81xx.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\aar1210.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\adpu320.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\a320raid.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\cda1000.SY_.
2012-10-02 10:32:39 : <PREP> Deleted \I386\ASH1205.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\ADP3132.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\aacsas.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\aac.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\amdbusdr.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\amdide.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\ahci6xx.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\atiide.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\ahcix700.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\ahcix70r.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\ahcix80x.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\arcm_x86.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\asahxp32.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\m5228.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\m5281.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\m5287.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\m5288.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\m5289.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\cpqcissm.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\cpqarry2.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\hpcissm2.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\cercsr6.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\hpt3xx.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\rr62x.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\rr64x.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\hpt374.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\rr172x.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\rr174x.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\hptmv6.SY_.
2012-10-02 10:32:40 : <PREP> Deleted \I386\2310_00.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\rr232x.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\rr2340.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\272x_1x.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\274x_3x.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\rr276x.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\hptiop.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\hptmv.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\rr26xx.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\rr2644.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\rr2680.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\ipsraidn.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\nfrd960x.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\adp94xx.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\inic162x.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\iteraid.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\iteatapi.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\jraid.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\MegaIDE.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\symmpiv.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\megasr.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\megasas.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\MegaINTL.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\sas2xp86.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\symmpi.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\iastor.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\raidsrc.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\iastor2.SY_.
2012-10-02 10:32:41 : <PREP> Deleted \I386\iastor3.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\iastor6.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\iastor7.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mv61xxmm.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mv61xx.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mv614x.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mvsata.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mvxxmm.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mv91xx.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mv64xxmm.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\mv64xx.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvlegacy.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvatabus.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\NVATA.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvraid.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvatard.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvgts6r.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvgts6.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvgts7.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvgts7r.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\nvrd327r.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\fst376xp.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\ide376xp.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\fastsx.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\sptrak.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\fttxr52P.SY_.
2012-10-02 10:32:42 : <PREP> Deleted \I386\fasttrak.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\fast2xxp.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\s150sx8.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\ulsata.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\ulsata2.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\prfsx4xp.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\FTTXR5_O.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\FtTxR54P.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\ql2100.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\ql2200.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\si3114r5.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3124r5A.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3124R5A2.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3132R5C.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3132R5C2.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3132R5C3.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3132R5C4.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\3132R5C5.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\pnp649r.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\pnp680r.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\Si3112r.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\si3114r.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\si3124r.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\pnp680.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\si3531.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SI3112.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\si3114.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\si3124.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SI3132B.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SI3132B2.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SI3132B3.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SI3132B4.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SI3132B5.SY_.
2012-10-02 10:32:43 : <PREP> Deleted \I386\SISRAID2.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\siside.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\SISRAID.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\SISRAID4.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\viamraid.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\VIAPDSK.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\VSTXWDC.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\VMSCSI.SY_.
2012-10-02 10:32:44 : <PREP> Deleted \I386\DriverPack_MassStorage_wnt5_x86-32.ini.
2012-10-02 10:32:44 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2012-10-02 10:32:44 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.
2012-10-02 10:32:45 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2012-10-02 10:32:45 : <SLIP> C:\XP CD\Driverpack\QSC\wnt5_x86-32_uni_DP_MassStorage_1209_textmode\DriverPack_MassStorage_wnt5_x86-32.ini
2012-10-02 10:32:46 : <SLIP> Processing Mass Storage files now. This may take a minute.
2012-10-02 10:32:48 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2012-10-02 10:32:49 : <SLIP> txtsetup.sif Backed-up Successfully
2012-10-02 10:32:49 : <SLIP> dosnet.inf Backed-up Successfully
2012-10-02 10:32:58 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2012-10-02 10:33:00 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2012-10-02 10:33:44 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2012-10-02 10:33:44 : <SLIP> Created necessary directory structure for method 2.
2012-10-02 10:33:44 : <SLIP> Copying files necessary for method 2.
2012-10-02 10:33:45 : <SLIP> Extracted additional files necessary for method 2.
2012-10-02 10:33:45 : <SLIP> expanded setup.ex_ to setuporg.exe
2012-10-02 10:33:45 : <SLIP> SETUP.EX_ Backed-up Successfully
2012-10-02 10:33:45 : <SLIP> Compressed setup.exe to SETUP.EX_.
2012-10-02 10:33:45 : <SLIP> Method 2 setup.ex_ installed
2012-10-02 10:33:45 : <SLIP> Created \I386\presetup.cmd file.
2012-10-02 10:33:45 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2012-10-02 10:33:45 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2012-10-02 10:33:45 : <SLIP> Copied DriverPack Chipset to \OEM.
2012-10-02 10:33:45 : <SLIP> Copied DriverPack CPU to \OEM.
2012-10-02 10:33:45 : <SLIP> Copied DriverPack Mass Storage to \OEM.
2012-10-02 10:33:45 : <SLIP> Copied DriverPacks to \OEM.
2012-10-02 10:33:45 : <SLIP> Will not slipstream patches, Service Pack 3 was detected.
2012-10-02 10:33:45 : <SLIP> Will not slipstream KB888111 because no Sound DriverPack is being slipstreamed
2012-10-02 10:33:45 : <SLIP> Will not slipstream KB883667 because no Graphics DriverPack is being slipstreamed
2012-10-02 10:33:46 : <SLIP> Updated \I386\winnt.sif to support method 2.
2012-10-02 10:33:46 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2012-10-02 10:33:46 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2012-10-02 10:33:46 : <SLIP> DP_Install_Tool was copied successfully
2012-10-02 10:33:46 : <SLIP> Slipstream finished in 1 minutes and 13 seconds.
2012-10-02 10:34:45 : <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:\XP CD\SOURCE"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset	= "yes"
DP_CPU		= "yes"
DP_MassStorage	= "yes"
DP_MassStorage_textmode = "yes"
2012-10-02 10:34:45 : <CLNP> Create a DPs_Base.log backup @ C:\XP CD\Driverpack\LogFiles\DPs_BASE_12-10-02_10-34.log
2012-10-02 10:34:45 : <CLNP> Program terminated.
  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

mr_smartepants wrote:

Welcome to DriverPacks.
That's an excellent first post.  You posted nearly all the info we need.
That's an odd problem too.  Is your RAID controller an Intel-branded chip or Promise-branded?

Many thanks! Almost - I knew I would miss something!!

The motherboard comes with both. There is a Promise branded chip and the ICH5R resides on the intel i875 southbridge (I think!)...

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Damnation wrote:

I'm just wondering why is this HWID

PCI\VEN_8086&DEV_24DF

Is used for both

Intel 82801ER/6300ESB SATA RAID 5.5

as well as

LSI Logic MegaRAID IDE for INTEL

in the masstorage.ini
is this a driver conflict? or is there a reason for this?

Yep, that is my wonderings too... Commenting out the MegaINTL line and it then suddenly works suggests to me that it is a conflict... But I am not an expert in these matters by a long shot!

  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: v1209 Pack issue with IASTOR and FST376XP

candles wrote:
Damnation wrote:

I'm just wondering why is this HWID

PCI\VEN_8086&DEV_24DF

Is used for both

Intel 82801ER/6300ESB SATA RAID 5.5

as well as

LSI Logic MegaRAID IDE for INTEL

in the masstorage.ini
is this a driver conflict? or is there a reason for this?

Yep, that is my wonderings too... Commenting out the MegaINTL line and it then suddenly works suggests to me that it is a conflict... But I am not an expert in these matters by a long shot!

It's not used for both.  One ends in "CC_104" while the other ends in SUBSYS_xxxxxxxx.  Totally different.
None of your HWIDs match the [L] section entries anyway so I'm not sure why that's a problem.

[L]
; This section has to be placed before [I4]
LSI Logic MegaRAID IDE for INTEL"
PCI\VEN_8086&DEV_24df&SUBSYS_34348086,PCI\VEN_8086&DEV_24df&SUBSYS_34328086,PCI\VEN_8086&DEV_24df&SUBSYS_34368086,PCI\VEN_8086&DEV_24df&SUBSYS_34388086,PCI\VEN_8086&DEV_24df&SUBSYS_343a8086,PCI\VEN_8086&DEV_24df&SUBSYS_343c8086,PCI\VEN_8086&DEV_24df&SUBSYS_343e8086,PCI\VEN_8086&DEV_24df&SUBSYS_344d8086,PCI\VEN_8086&DEV_24df&SUBSYS_34558086,PCI\VEN_8086&DEV_24df&SUBSYS_34578086,PCI\VEN_8086&DEV_24df&SUBSYS_34618086,PCI\VEN_8086&DEV_24df&SUBSYS_34638086,PCI\VEN_8086&DEV_24df&SUBSYS_34658086


[i]
Intel 82801ER/6300ESB SATA RAID 5.5
PCI\VEN_8086&DEV_24DF&CC_0104
Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!
  • TechDud
  • Researcher & DriverPacks Moderator
  • Offline
  • From: Fraser Valley, Canada
  • Registered: 2010-11-23
  • Posts: 2,270

Re: v1209 Pack issue with IASTOR and FST376XP

candles wrote:

"The PSU is more than sufficient - when I built the box"

How old is the power supply?  Also, please clarify what you mean by "more than sufficient"?

Another thing i noticed; "2012-10-02 10:32:02 : <INIT>     Detected DriverPack CPU 1005!"
You can remove this pack from the list of those packs that you are integrating, as this pack is obsolete.
     see:  http://forum.driverpacks.net/viewtopic. … 384#p49384

"QSC        = "yes""

Please clear the DP_BASE's cache before doing your next integration.  smile


PS:  Aluminum Electrolytic capacitors can fail without showing any physical outward sign.
       You may not have spared any expense with that box, yet can you say the same for the P/S manufacturer (or the production manager, for that matter)?  I do not ask this to denigrate any particular brand.

steve from virginia wrote:

"Technological advancement is the essence of ‘ruinous competition’. "
http://www.economic-undertow.com/2012/1 … t-grinder/

  I truly wish that i could loan you my $30 IR thermometer.  You might be amazed to see how hot it gets around the CPU after several minutes running memtest.  I have a couple of similar ASUS boards with an 865P chipset that regularly get up to 85°C with a 3.0 GHz chip!  This is no guarantee that you will see the same results, just circumstantial evidence that you might.
  As capacitors are temperature-sensitive (as well as ripple-current sensitive - that's related to the P/S), if i do the math on a set of Uni-ChemiCon KZE series (Japanese); they should last 8000 hours (333 days) at that temperature (as long as Ripple-Current remains below it's maximum rating).  The math is much different for "Solid" electrolyte capacitors; they last much longer (this is one reason why they are more-widely used today).  Of course, once again, this is no guarantee that you are experiencing cap failure, just more circumstantial evidence.  Intermittent faults can be a symptom.  http://www.badcaps.net/pages.php?vid=5

   see also:   http://www.capacitorlab.com/basic/
                  http://www.capacitorlab.com/visible-failures/index.htm
                  http://www.capacitorlab.com/failure-modes/index.htm
                  http://www.motherboardpoint.com/asus-p4 … 51989.html
                  http://www.pcreview.co.uk/forums/black- … 41866.html

PPS:  Did you try removing (or renaming) the MegaINTL.INF file & repacking with 7-zip for a test integration?  I am assuming that you are indeed using a different machine to do the integrations.  yikes

PPPS:  Use anti-static measures to handle this board & USB pins (esp. FP header), as ICH5/ICH5R may be more sensitive to it.  If any of your front-USB connectors have damage, disconnect them to ensure your mobo is preserved.  The risk is "ICH5R latch-up".  I haven't experienced this myself, just 865 North-Bridges "shorting" out, just not as dramatically.

GMAN wrote:

"http://onfinite.com/libraries/179057/2ea.jpg"
from http://onfinite.com/libraries/179057/2ea.jpg
referenced:  http://www.pcreview.co.uk/forums/black- … 866p2.html

Last edited by TechDud (2012-10-06 15:19:11)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)
http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/5NQ1BpqvDa_0vDwtHeoZCcSJjOVNuvMXSp4i7SE7DQA/perpetual:forever/userbar/moderator-1.png
  • Registered: 2012-09-13
  • Posts: 170

Re: v1209 Pack issue with IASTOR and FST376XP

I made a test pack with Megaintel loading between I and I2

candles, can you try it out? (remove megaintl from filename before you integrate)

http://www.mediafire.com/?f5pzbxv2g82nrwt

Last edited by Damnation (2012-10-04 20:07:09)

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Damnation wrote:

I made a test pack with Megaintel loading between I and I2

candles, can you try it out? (remove megaintl from filename before you integrate)

http://www.mediafire.com/?f5pzbxv2g82nrwt

Downloading, will give it a go this afternoon! Got an important appointment this morning! smile

Many thanks!

  • TechDud
  • Researcher & DriverPacks Moderator
  • Offline
  • From: Fraser Valley, Canada
  • Registered: 2010-11-23
  • Posts: 2,270

Re: v1209 Pack issue with IASTOR and FST376XP

on the Promise PDC20378 front, i have found original driver links for this chip.
  here -->  http://www.asus.com/Motherboards/Intel_ … /#download
and duplicated here -->  http://www.tyan.com/archive/support/htm … pport.html  big_smile
   (noted for anecdotal reasons)
PBFSTTX2K.inf is {DriverVer=08/06/2003, 1.00.1.37} WHQL'ed for 2k, XP, xp64 & 2k3

They are contained in DP_MassStorage_wnt5_x86-32_1209\D\M\P\
WHQL has been broken for the .Inf to add "&CC_0104", denoting RAID.
I see in the same folder a batch file named "UnDo.cmd"

UnDo.cmd wrote:

"DEL /F /Q PBULSATA.inf
REN PBULSATA.inf.ORG1 PBULSATA.inf
DEL /F /Q PBULSATA.inf.ORG*
DEL /F /Q %0"

The signature may be from Microsoft, yet the embedded certificate is only signed using RSA (1024bit), which is obsolete (iirc).
  reference --> http://forum.driverpacks.net/viewtopic. … 251#p49251

Does it recognize any drives (set up as-SATA or RAID in BIOS) if you integrate with driver-signing disabled?

I note that the obsolete certificate may have been upgraded to RSA (2048bit) in v1.0.1.39
http://www.rioworks.com/Server/Download … romise.zip  big_smile
  This is from this download page --> http://www.rioworks.com/server/Product/ … View=HDAMB
  {DriverVer=10/11/2005, 1.00.1.39} probably WHQL'ed (despite the .cat file date) for Win 2k, XP, xp64, & 2k3!

These drivers do not appear to be in any of the MassStorage packs; it is possible that they work for NT6 too!

Last edited by TechDud (2012-10-07 10:58:12)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)
http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/5NQ1BpqvDa_0vDwtHeoZCcSJjOVNuvMXSp4i7SE7DQA/perpetual:forever/userbar/moderator-1.png
  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Damnation wrote:

I made a test pack with Megaintel loading between I and I2

candles, can you try it out? (remove megaintl from filename before you integrate)

http://www.mediafire.com/?f5pzbxv2g82nrwt

Many apologies for the delay - had to disassemble my entire setup due to housing issues on Friday afternoon... Long story and not the best place for me to go into detail - but rest assured, I will be up and running again soon!

With regards to TechDud and your post - Looks very interesting, not entirely sure I understand everything - but do you think the promise driver might actually be causing the issue?

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Damnation wrote:

I made a test pack with Megaintel loading between I and I2

candles, can you try it out? (remove megaintl from filename before you integrate)

http://www.mediafire.com/?f5pzbxv2g82nrwt

Congratulations Damnation, your test pack has sorted it!!

Many apologies for the delay!

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

TechDud wrote:
candles wrote:

"The PSU is more than sufficient - when I built the box"

How old is the power supply?  Also, please clarify what you mean by "more than sufficient"?

Another thing i noticed; "2012-10-02 10:32:02 : <INIT>     Detected DriverPack CPU 1005!"
You can remove this pack from the list of those packs that you are integrating, as this pack is obsolete.
     see:  http://forum.driverpacks.net/viewtopic. … 384#p49384

"QSC        = "yes""

Please clear the DP_BASE's cache before doing your next integration.  smile

The power supply is probably 6-8 years old. I can't remember exactly.

Ahhh, I didn't realise that pack was obsolete! I shall remove!

I was caught out today with the QSC when testing today! Timely advice wink

TechDud wrote:

PS:  Aluminum Electrolytic capacitors can fail without showing any physical outward sign.
       You may not have spared any expense with that box, yet can you say the same for the P/S manufacturer (or the production manager, for that matter)?  I do not ask this to denigrate any particular brand.

steve from virginia wrote:

"Technological advancement is the essence of ‘ruinous competition’. "
http://www.economic-undertow.com/2012/1 … t-grinder/

  I truly wish that i could loan you my $30 IR thermometer.  You might be amazed to see how hot it gets around the CPU after several minutes running memtest.  I have a couple of similar ASUS boards with an 865P chipset that regularly get up to 85°C with a 3.0 GHz chip!  This is no guarantee that you will see the same results, just circumstantial evidence that you might.
  As capacitors are temperature-sensitive (as well as ripple-current sensitive - that's related to the P/S), if i do the math on a set of Uni-ChemiCon KZE series (Japanese); they should last 8000 hours (333 days) at that temperature (as long as Ripple-Current remains below it's maximum rating).  The math is much different for "Solid" electrolyte capacitors; they last much longer (this is one reason why they are more-widely used today).  Of course, once again, this is no guarantee that you are experiencing cap failure, just more circumstantial evidence.  Intermittent faults can be a symptom.  http://www.badcaps.net/pages.php?vid=5

   see also:   http://www.capacitorlab.com/basic/
                  http://www.capacitorlab.com/visible-failures/index.htm
                  http://www.capacitorlab.com/failure-modes/index.htm
                  http://www.motherboardpoint.com/asus-p4 … 51989.html
                  http://www.pcreview.co.uk/forums/black- … 41866.html

Great info, I will definitely keep this in mind.

TechDud wrote:

PPS:  Did you try removing (or renaming) the MegaINTL.INF file & repacking with 7-zip for a test integration?  I am assuming that you are indeed using a different machine to do the integrations.  yikes

I commented out the MegaINTL.sys in the SCSI.load part of the TXTSETUP.sif of the resulting SOURCE files, which did the job, I assume this is something similar??

I was building on another machine - but as I wasn't fully running the setup to get the problem, it wouldn't have mattered - I am currently using the machine as a computational workhorse at the moment... (well, I was before I was uprooted!)

TechDud wrote:

PPPS:  Use anti-static measures to handle this board & USB pins (esp. FP header), as ICH5/ICH5R may be more sensitive to it.  If any of your front-USB connectors have damage, disconnect them to ensure your mobo is preserved.  The risk is "ICH5R latch-up".  I haven't experienced this myself, just 865 North-Bridges "shorting" out, just not as dramatically.

GMAN wrote:

"http://onfinite.com/libraries/179057/2ea.jpg"
from http://onfinite.com/libraries/179057/2ea.jpg
referenced:  http://www.pcreview.co.uk/forums/black- … 866p2.html

Again, this is amazing information! I will be putting this in my personal wiki!

Thanks for all your help and sharing all this info.

  • Registered: 2012-09-13
  • Posts: 170

Re: v1209 Pack issue with IASTOR and FST376XP

candles wrote:

Congratulations Damnation, your test pack has sorted it!!

Many apologies for the delay!

Glad to be of assistance.

So, should we have the ini changed for the next version of the mass storage driverpack?

or is there a better solution for this?

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Damnation wrote:
candles wrote:

Congratulations Damnation, your test pack has sorted it!!

Many apologies for the delay!

Glad to be of assistance.

So, should we have the ini changed for the next version of the mass storage driverpack?

or is there a better solution for this?

Can I vote yes?! wink

  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

Should I be raising a bug here?? Or is that just for the BASE?

Last edited by candles (2012-10-15 07:39:58)

  • TechDud
  • Researcher & DriverPacks Moderator
  • Offline
  • From: Fraser Valley, Canada
  • Registered: 2010-11-23
  • Posts: 2,270

Re: v1209 Pack issue with IASTOR and FST376XP

bump

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)
http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/5NQ1BpqvDa_0vDwtHeoZCcSJjOVNuvMXSp4i7SE7DQA/perpetual:forever/userbar/moderator-1.png
  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

TechDud wrote:

bump

Absolutely, well bumped... Thanks TechDud

  • TechDud
  • Researcher & DriverPacks Moderator
  • Offline
  • From: Fraser Valley, Canada
  • Registered: 2010-11-23
  • Posts: 2,270

Re: v1209 Pack issue with IASTOR and FST376XP

Efforting to fix this within the next beta.
It seems that you have been very patient.

Last edited by TechDud (2012-12-18 19:44:54)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)
http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/5NQ1BpqvDa_0vDwtHeoZCcSJjOVNuvMXSp4i7SE7DQA/perpetual:forever/userbar/moderator-1.png
  • candles
  • DriverPacks newbie
  • Offline
  • Registered: 2012-10-03
  • Posts: 15

Re: v1209 Pack issue with IASTOR and FST376XP

TechDud wrote:

Efforting to fix this within the next beta.
It seems that you have been very patient.

Sounds great!

I am pretty patient! Thankfully, I have managed to get things working for me and the work of Damnation and yourself hopefully have helped others! smile

A bit surprised that no-one else got involved - Because I am new to the forums, I am not sure who normally does the work?

  • From: Cambridgeshire, UK
  • Registered: 2007-01-27
  • Posts: 6,226

Re: v1209 Pack issue with IASTOR and FST376XP

Jeff and I were doing all the work for a while.  I've been ludicrously busy over the past few months, so luckily these guys have jumped in and have been doing a great job.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!