Sysprep mass storage section with DriverPacks Mass Storage (Page 1 of 2)

Am I the only one looking for a solution for this? Is this something already in the works? Did I post this in an improper manner or in the wrong section?

Here is what I write in my sysprep to use the DP's Intel SATA drivers:

[Sysprep]
BuildMassStorageSection=Yes

[SysprepMassStorage]
PCI\VEN_8086&DEV_2652&CC_0106=C:\D\M\IN\1\iaahci.inf
PCI\VEN_8086&DEV_2653&CC_0106=C:\D\M\IN\1\iaahci.inf
PCI\VEN_8086&DEV_27C1&CC_0106=C:\D\M\IN\1\iaahci.inf
PCI\VEN_8086&DEV_27C5&CC_0106=C:\D\M\IN\1\iaahci.inf
PCI\VEN_8086&DEV_2681&CC_0106=C:\D\M\IN\1\iaahci.inf
PCI\VEN_8086&DEV_2821&CC_0106=C:\D\M\IN\1\iaahci.inf

PCI\VEN_8086&DEV_2822&CC_0104=C:\D\M\IN\1\iaStor.inf
PCI\VEN_8086&DEV_27C6&CC_0104=C:\D\M\IN\1\iaStor.inf
PCI\VEN_8086&DEV_2682&CC_0104=C:\D\M\IN\1\iaStor.inf
PCI\VEN_8086&DEV_27C3&CC_0104=C:\D\M\IN\1\iaStor.inf
PCI\VEN_8086&DEV_2652&CC_0104=C:\D\M\IN\1\iaStor.inf

The main thing is to extract the HWID from each .inf file and put in the sysprep.inf file before you run it. Make sure you tell sysprep to build mass storage drivers -bmsd I believe is the option.

I don't have any method for automatically extracting the HWIDs, I do it manually.

Ok, I'm currently trying to get this working by trial and error and these are my ideas:

First of all I'm using http://dev.driverpacks.thesneaky.com/dr … _test_4.7z this beta massstorage package which containes the Intel SATA drivers.

I'm following these steps: http://forum.driverpacks.net/viewtopic. … 9420#p9420
BUT not the line at the end telling me to run "c:\sysprep\sysprep.exe -bmsd" to build the massstorage.

For that I've created "HWIDS.CMD" with the following code: (found this on MSFN forum, great job!!!)

rem %1 is path to MassDriverPacks Folder
IF "%1"=="" GOTO EOF
IF NOT EXIST %1 GOTO EOF

SETLOCAL ENABLEDELAYEDEXPANSION
SET STDOUT=%cd%\HWIDS.TXT
TYPE>%STDOUT% 2>NUL

::traverse drivers path
CALL :TRAVERSAL %1

GOTO EOF

:TRAVERSAL
PUSHD %1
for /f %%f in ('Dir /b *.inf') do (
 for /f "eol=- tokens=2 delims=," %%i in ('find /i "pci\ven" %%f') do (
  for /f "tokens=*" %%j in ("%%i") do (
    for /f "tokens=1* delims=_" %%k in ("%%j") do (
      if /i "%%k" EQU "PCI\VEN" (
        for /f "usebackq tokens=1* delims=; " %%a in ('%%j') do (
          echo %%a=%cd%\%%f>>%STDOUT%
        )
      )
    )
  )
)
)

FOR /F %%I IN ('DIR /AD /OGN /B') DO (
CALL :TRAVERSAL %CD%\%%I
)
POPD
GOTO EOF

:EOF

If you run this batch from "C:\" (if you followed the steps above!) by using this command: "HWIDS.cmd D\M" it will build
"HWIDS.txt" containing all the massstorage lines needed for the [SysprepMassStorage] section in sysprep.inf.

I noticed not all the lines are build the right way, scroll in HWIDS.txt to check if there are some lines which look like this

PCI\VEN_8086&DEV_1960&SUBSYS_0466101E=    C:\Sysprep\D\M\L\2\OEMSETUP.INF (notice the space between the "=" and "c:\.."
and correct these by deleting the space.

After that select all lines, copy it and paste them in the sysprep.inf under [SysprepMassStorage]

!!! I'm still testing this and hopefully it will work !!!

I did come accross some errors while running sysprep:

"elxtor driver error" --> seems like a driver problem, I deleted the "C:\D\M\E" folder and deleted the lines
in the [SysprepMassStorage] section linking to that folder.

"silsupp.cpl" error" --> seems like a driver problem, I deleted the "C:\D\M\E" folder and deleted the lines
in the [SysprepMassStorage] section linking to that folder.

"qlsdm.dll error" --> seems like a driver problem, I deleted the "C:\D\M\E" folder and deleted the lines
in the [SysprepMassStorage] section linking to that folder.

!!! It might be wise to perform the steps mentioned above BEFORE you run sysprep !!!

I also got alot of pop-ups asking me to allow unsigned driver install (eventho I put the driversigning on "Ignore") and pop-ups asking me if I wanted to overwrite files (I selected "yes" on all). I tried using "WatchDriverSigningPolicy.exe" from MSFN forum to surpress the unsigned driver install popups, but doesn't seem to work.

At one time you will get ALOT of popups when it reaches "M\S\4\Silsupp.cpl", keep selecting "yes" and it will continue after a while (it seems to not continue, but it does!)

!!! Right now I'm doing this as a test, don't even know if it will work, so please keep that in mind !!!

I'm also thinking of minimizing the massstorage drivers to a minimum, just using the ones I need, but I'm curious if the whole (or at least most of the) package will work

I'll keep u updated...

question: Is running "sysprep -bmsd" still needed after filling the [SysprepMassStorage] section in sysprep.inf by hand?

Last edited by Skillz (2007-06-14 19:29:46)

The -bmsd switch is only used to create the sysprepmassstorage section in the sysprep.inf. It would probably be best to use that switch first, then add the additional entries that your script creates, then run sysprep without the -bmsd switch.

Last edited by johnk963 (2007-06-15 01:20:53)

In my tests, these drivers' IDs' needs to be excluded from sysprep.inf:

AD\4
IN\1\O
L\2, L\3
P\1, P\2, P\5
Q\
S\4
all other 'older' versions, like IN\1\O - out

With such set, SYSPREPed image boots ok.

But, I'v built sysprep.inf from DriverPack_MassStorage_wnt5_x86-32.ini,  not from  *.inf files.

AFAIK sysprep, all mass storage drivers, pointed in sysprep.inf, are loaded during next boot time. And then, during boot, each driver will seek for supported hardware and still working or die.

In case of three different drivers for Intel storage controllers,  ... hmm survive the last! Last, who be really last in sysprep.inf. In case of UNsigned drivers, of course.
Signed drives ... I don't know exactly, it's seems to be what Windows keep latest version.

//off topic - how do you edit Intel *.inf files and keep Microsoft HW compatibility sign?

So, it's a sad. While some Intel HW supported by MS drivers, MS drivers can save us. And, of course, only one Intel driver can be used in sysprep. IMO, even we rename drivers and try to load all three at once, they are can interfere each other and crash. So, sysprep-er need to choose Proper Driver for his hardware. And pray.

Universal sysprep image for Intel storage controllers is impossible. Just use latest driver. Or (and) build different images.
I'm sad.

Hi

far as I know, limiting a driver to make it support fewer hwIDs does not break WHQL.
And, faik, changing the name o/t SYS, does not break WHQL either.

I am fairly sure that we can make a pack with three different aahci.sys and three different iastor.sys, with the inf files in accord with those names, and internally edited so the calls and references in those INFs are for the files they use.

if there are syspreppers who want to have a go at a testversion with such a change in it, say so.
I can make the testpack..

updated the syspreptestfiles
REASON; there are errors in the current release, and these have to be fixed for you guys as well.

this is a beta.. apart from the experiment with the three iastor files,  there is also a change in
[AT]
ATI's AHCI is probably not a bus extender, but the INI said it was.

http://rapidshare.com/files/38806149/DP … eptest2.7z
--------------------------------

'Overlapping HWIDs can cause crashes. Reducing overlap in Mass Storage.',
FIXES
  'INI: [S-7] duplicate HWID VEN_1095&DEV_3114&SUBSYS_81361043 removed, covered by [S-7-A]'.
'| [S-4] removed ATI HWIDs covered by ATI variant in [S-5-A]'.
'| fixed errors like ms_2_exc_ which is incorrect for single driver',

Updates
  'SiS 180/181/182/1182 RAID Controllers drivers from 01/05/2005,5.1.1039.2030 to 01/11/2007,5.1.1039.2110'.
  'JMicron JMB36X Processor from 04/10/2007, 1.17.17.00 to 06/13/2007, 1.17.20.03',

New
  'SiS 1184 RAID/AHCI & 1185 AHCI Controller 01/17/2007,5.1.1039.3020'.
'|VIA SATA Port & busextender (Via Hyperion Pro) 03/23/2007,6.0.6000.212'.

Last edited by jtdoom (2007-06-23 13:37:26)

Has anyone solved how to stop the continual popups about unsigned drivers in MassStorage section of sysprep when loading in drivers from driverpack?

http://forum.driverpacks.net/viewtopic.php?id=1682
I posted a script in this thread about quickly extracting the device id codes from the inf's and adding to the sysprep.inf file. - but alas 1 million popups when running final sysprep

Last edited by chud (2007-07-03 04:41:03)

Does anyone have sysprepmassstorage section with more entries than skinlayer's list? I have no problem with a similar list of Intel HIDS but adding just a few others from the mass storage driverpack cause sysprep to hang.

Ideally I'd like as many of the mass storage drivers as possible but even just this list fails, what is the problem with this?

PCI\VEN_1039&DEV_0181=C:\D\M\SI\1\SISRaid1.INF
PCI\VEN_1039&DEV_0180=C:\D\M\SI\2\SISRaid.INF
PCI\VEN_1039&DEV_0181=C:\D\M\SI\2\SISRaid.INF
PCI\VEN_1039&DEV_0180=C:\D\M\SI\3\SISRaid2.INF
PCI\VEN_1039&DEV_0181=C:\D\M\SI\3\SISRaid2.INF
PCI\VEN_1039&DEV_0182=C:\D\M\SI\3\SISRaid2.INF
PCI\VEN_1039&DEV_1182=C:\D\M\SI\3\SISRaid2.INF
PCI\VEN_1039&DEV_1184=C:\D\M\SI\4\sisraid4.inf
PCI\VEN_1039&DEV_1185=C:\D\M\SI\4\sisraid4.inf
PCI\VEN_1106&DEV_3349&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_6287&CC_0106=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_0591&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_3249&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_3149&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_3164&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_0581&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_7372&CC_0104=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_3249=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_3149=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_3164=C:\D\M\V\1\VIAMRAID.INF
PCI\VEN_1106&DEV_4149=C:\D\M\V\2\viapide.inf
PCI\VEN_1106&DEV_0571=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3149&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_0591&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_5337&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3349&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_5287&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3164&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_0581&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_5324&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_0571=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3149&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_0591&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_5337&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3349&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_5287&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3164&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_0581&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_5324&CC_0101=C:\D\M\V\3\vminiide.inf
PCI\VEN_1106&DEV_3149&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_3349&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0581&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0591&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5287&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5324&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5337&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5372&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_3149&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_3349&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0581&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_0591&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5287&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5324&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5337&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_1106&DEV_5372&CC_0101=C:\D\M\V\4\ViPrt.inf
PCI\VEN_104B&DEV_1040=C:\D\M\VM\vmscsi.inf

I've tested 'syspreptestfiles' with renamed Intel drivers.
Bad news:
1. during system reseal, sysprep ask about every HWID entry (pointed to renamed driver)  three times, and in log file there are smth about 'improper signed' driver. So, renamed drivers' signing goes off.

2. it's not works at all. All drivers are installed in 'iastor' driver entry in Services, and iastor's imagepath points to the last installed driver. In my case, it was iastor75.sys

3. I've changed *.inf fiels, so drivers' entries are names isator55, iastor62, iastor75. In such case, when sysprep seals system, iaStor75 doesn't install at all. So, I change display names of all three drivers. And drivers are installed and, when system boots, loaded and work. (but! I haven't real Intel devices to test...)

So, think, think.... drivers can be loaded in sysprep process, but driver signing is big trouble, I think... Can anybody (with MS driver toolkit) sign driver with self issued certificate and test to install?

Last edited by torrero (2007-07-12 07:59:12)

above post was edited..
NOTE; That test-sys-prep-file was pulled long ago.
It probably has errors.