DriverPacks.net Forum - Trying to understand Massstorage slipstreaming process

Re: Trying to understand Massstorage slipstreaming process

2008-05-15T09:23:27Z

the problem is that not all drivers are the same so even if you were to learn how to add your single driver
when you try to do it again it may not be the same method. We call these "exceptions"
There are may different types of exceptions and we have spent years addressing them and tweaking our method

so there is not a simple list of instructions to follow that will yeild success in every case.
(if it were that easy who would need us )

have a great day!

Re: Trying to understand Massstorage slipstreaming process

2008-05-15T00:08:36Z

hi
Like Jeff says, there is more to it.

you may want to learn what changes are made.
1; get winmerge or araxis and install it (a comparison tool)
2; make a copy of a XP CD to a folder
3; copy that folder (so you can later compare)
4; run base with DriverPack MassStorage and txtmode in M1 to one of those folders.
5; compare
--------
you will see where the files where added and replaced files will also show.

you will see that dosnet.inf is also changed
compare it
you will see that txtsetup.sif was changed
compare it

--
I think that since you can do this manually, you could learn how to add your drivers to DriverPack MassStorage.
two important rules:
unique tagnames in INI
no duplicate HWIDs in INI

you could link to the exotic drivers we do not have, and show us how you try add those.
(like an academy..)

Re: Trying to understand Massstorage slipstreaming process

2008-05-14T21:50:26Z

http://unattended.msfn.org/unattended.xp/view/web/36/
Right there...

Re: Trying to understand Massstorage slipstreaming process

2008-05-14T08:27:44Z

Thanks for your reply. I already read the FAQ and in this particular case it seems better to just manually slipstream the SATA drivers instead of using driverpacks.

I'm very curious which specific entries are missing from the ones mentioned above. Could you provide me THE link to MSFN.org as I think I already read most of them. I must be a glutton for punishment and i definately would like to know how this can be done..

Many thanks!

Re: Trying to understand Massstorage slipstreaming process

2008-04-25T18:57:40Z

well you did this the hard way and you are missing more than a few entries.

please see our FAQ about making a custom mass storage pack.

prune all drivers except iastor from the pack and the ini then slipstream - bam your done.

If you are a glutton for punishment the instructions to do this correctly are to be found over at MSFN.org

Trying to understand Massstorage slipstreaming process

2008-04-25T07:34:01Z

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.