Topic: Trying to understand Massstorage slipstreaming process
Hi,
I'm trying to understand in which way exactly mass-storage drivers are slipstreamed (method 1) by DPBase.
When slipstreaming manually Textmode part is working smooth, but when the XP installation starts in GUI mode problems arise right away -> BSOD! (Right after mup.sys).
This is what I did (using IASTOR):
Copied the following files to \i386:
IASTOR55.SY_
IASTOR70.SY_
IASTOR.SY_
Changes to DOSNET.INF:
[FloppyFiles.2]
d1,iastor.sys
d1,iastor70.sys
d1,iastor55.sys
[FILES]
d1,iastor.sys
d1,iastor70.sys
d1,iastor55.sys
Changes to TXTSETUP.INF:
[SourceDisksFiles]
iastor55.sys=1,,,,,,4_,4,1,,,1,4
iastor70.sys=1,,,,,,4_,4,1,,,1,4
iastor.sys=1,,,,,,4_,4,1,,,1,4
[HardwareIdsDatabase]
PCI\VEN_8086&DEV_24DF&CC_0104="iastor55"
PCI\VEN_8086&DEV_25B0&CC_0104="iastor55"
PCI\VEN_8086&DEV_2652&CC_0104="iastor70"
PCI\VEN_8086&DEV_2652&CC_0106="iastor70"
PCI\VEN_8086&DEV_2682&CC_0104="iastor"
PCI\VEN_8086&DEV_27C3&CC_0104="iastor"
PCI\VEN_8086&DEV_27C6&CC_0104="iastor"
PCI\VEN_8086&DEV_2822&CC_0104="iastor"
PCI\VEN_8086&DEV_282A&CC_0104="iastor"
PCI\VEN_8086&DEV_2653&CC_0106="iastor"
PCI\VEN_8086&DEV_2681&CC_0106="iastor"
PCI\VEN_8086&DEV_27C1&CC_0106="iastor"
PCI\VEN_8086&DEV_27C5&CC_0106="iastor"
PCI\VEN_8086&DEV_2821&CC_0106="iastor"
PCI\VEN_8086&DEV_2829&CC_0106="iastor"
PCI\VEN_8086&DEV_2922&CC_0106="iastor"
PCI\VEN_8086&DEV_5029&CC_0106="iastor"
PCI\VEN_8086&DEV_2923&CC_0106="iastor"
[SCSI.Load]
iastor55=iastor55.sys,4
iastor70=iastor70.sys,4
iastor=iastor.sys,4
[SCSI]
iastor55="Intel 82801ER / 6300ESB SATA RAID v5.5.0.1035"
iastor70="Intel 631x/632x ESB, 82801HGM/HH/HO/HR SATA, AHCI/RAID v7.0.0.1020"
iastor="INTEL 82801HEM/HBM, ICH9 SATA, AHCI/RAID V7.8.0.1012"
That's it.. Nothing else.. No references in WINNT.SIF, no $OEM$\TEXTMODE folder, nothing.
But it doesn't work.. I've been trying for a long time to get this working manually. Why? Simple, I need to modify an existing XP image with a huge custom-driverbase. I've been trying to replace this pile of trash by using driverpacks but this didn't cover the full monty, not surprised since this specific driverbase contains some pretty exotic stuff. It's not anywhere near as structured as the Driverpacks.. It will take too much time to figure out which drivers need to be fixed!
All I want is integrating the IASTOR Sata drivers..
Since it does work PERFECT when using DPBase Driverpacks I'm obviously missing something here.. If anyone could help me out here it would make my week!!!
Many thanks for your time.
G