MSFN Forums > Integrating SATA and RAID drivers with HFSLIP

Full Version: Integrating SATA and RAID drivers with HFSLIP

MSFN Forums > Member Contributed Projects > HFSLIP

Pages: 1, 2, 3, 4

iTwins

Oct 27 2006, 09:30 AM

QUOTE (TAiN @ Oct 27 2006, 10:09 PM)

@iTwins: Yeah, I tried that one already. That is the BusLogic driver, not the LSI Logic one. I also tried drivers from the LSI Logic site just for giggles. No luck.

heh...now you had me worried. Although I use VMware everyday and I have written VMware installation guides (for work) and RAID Slipstreamer Installation Guide (for work), one can never be too sure about anything. Therefore, I had to test it out immediately to make sure I wasn't BS-ing myself, BS-ing my colleagues, and BS-ing everyone whom I made the tool available on MSFN, that my RAID Slipstreamer supported VMware's SCSI controller.

My conclusion...phew...

.... I am happy to say I was able to unattendedly build Windows 2000 Professional successfully using LSI Logic and set to use SCSI HDD.

I used my RAID Slipstreamer v2.0 to slipstream all drivers into the Windows 2000 SP4 i386 source. I then setup VMware Workstation v5.5.1 Build 19175 using the following settings:

...and the final result and proof:

BTW, you know why I say the VMware SCSI Controller is an LSI Logic 1020/1030 SCSI Controller? The reason was because when I attempted to add the LSI 1020/1030 into RAID Slipstreamer v1.1.0 (2 years ago), I realized both VMware v4.x SCSI Controller and LSI Logic's 1020/1030 have exactly the same vendor and device codes:

CODE

PCI\VEN_104B&DEV_1040

tain

Oct 27 2006, 09:46 AM

That is awesome! So why doesn't this work for me? Here is my experience:

1) When I try to build Win2K with the LSI Logic device (as in your screenies), VMWare explicitly warns me that the driver will not work with Win2k.

2) I tried it anyway using the driver method in this thread. I had the same driver as you posted previously as well as the drivers from the LSI Logic site all in STORAGE with the corrected storage.ini. Windows was unable to install because it couldn't access the storage device. The LSI Logic driver I used from their site was not the 1020/1030 driver that you mention but that shouldn't matter as the stock VMWare driver appears to work for you anyway.

I don't actually need this for myself; I just wanted to help test the method by running it through VMWare

iTwins

Oct 27 2006, 09:53 AM

I saw that message too but I ignored it by clicking OK.

Well, blame it VMware. It is one extremely problematic program regardless of what version you use, hence the reason why I had to write Installation and Usage Guides for the guys at work to teach them how to workaround to building my Standard Builds.

btw, Win98SE's EMM386.EXE crashes VMware's virtual LSI Logic SCSI driver and when booting up with WinME's DOS bootdisk, setting up Windows 2000 Pro could give tons of installation errors. Yup! VMware is so problematic! When using VMware's LSI Logic driver, I had to resort to using Uwe Sieber's UMBPCI.SYS memory manger to workaround this problem.

tain

Oct 27 2006, 09:55 AM

QUOTE (iTwins @ Oct 27 2006, 10:53 AM)

I saw that message too but I ignored it by clicking OK.

As do I, but Windows cannot install for me whether or not I use this thread's driver method.

Not sure what the problem is. Maybe my VMWare installation has a problem?

iTwins

Oct 27 2006, 10:37 AM

QUOTE (TAiN @ Oct 27 2006, 11:55 PM)

QUOTE (iTwins @ Oct 27 2006, 10:53 AM)

I saw that message too but I ignored it by clicking OK.

As do I, but Windows cannot install for me whether or not I use this thread's driver method.

Not sure what the problem is. Maybe my VMWare installation has a problem?

Everybody has a different way of building Windows. Maybe that has something to do with it

I use DOS, run WINNT.EXE with lots of parameters and give it an answer file for installing unattendedly. If you also use this method then you might need to use UMBPCI.SYS to workaround this VMware / LSI Logic issue.

Most people I see use WINNT32.EXE or simply booting up to CD and install step by steps, but I don't have much experience to this methods on VMware - I have not use step-by-step methods of many many years already.

If you use Windows 98 SE DOS Bootdisk (MSDOS v7.10) to install any Windows using VMware's LSI Logic controller, you will get this error and VMware crashes:

tain

Oct 27 2006, 11:19 AM

QUOTE (iTwins @ Oct 27 2006, 11:37 AM)

I use DOS, run WINNT.EXE with lots of parameters ...

I don't think very many people here are doing it that way.

Yzöwl

Oct 29 2006, 10:23 AM

Small problem! -(click me)

Here's my relevant sections in TXTSETUP.SIF

CODE

[SourceDisksFiles]
SPX.CAB = 1,,,,,,_x,39,0,0
iaahci.cat = 1,,,,,,,2,0,0,,1,2
iaahci.inf = 1,,,,,,,20,0,0,,1,20
iastor.cat = 1,,,,,,,2,0,0,,1,2
iastor.inf = 1,,,,,,,20,0,0,,1,20
iastor.sys = 1,,,,,,3_,4,1,,,1,4
jgogo.sys = 1,,,,,,3_,4,1,,,1,4
jraid.cat = 1,,,,,,,2,0,0,,1,2
jraid.inf = 1,,,,,,,20,0,0,,1,20
Jraid.sys = 1,,,,,,3_,4,1,,,1,4
si3132r5.cat = 1,,,,,,,2,0,0,,1,2
SI3132r5.inf = 1,,,,,,,20,0,0,,1,20
Si3132r5.sys = 1,,,,,,3_,4,1,,,1,4
SilSupp.cpl = 1,,,,,,,2,0,0,,1,2
SIPPD.inf = 1,,,,,,,20,0,0,,1,20
SiWinAcc.sys = 1,,,,,,3_,4,1,,,1,4

[SCSI.Load]
iastor = iastor.sys,4
jgogo = jgogo.sys,4
Jraid = Jraid.sys,4
Si3132r5 = Si3132r5.sys,4
SiWinAcc = SiWinAcc.sys,4

[SCSI]
iaAHCI   = "Intel® SATA AHCI Controller (32bit)"
iaStor   = "Intel® SATA RAID Controller (32bit)"
Jraid    = "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
Si3132r5 = "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"

[HardwareIdsDatabase]
PCI\VEN_1095&DEV_3132&SUBSYS_71321095 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_81771043 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_71001462 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_B0031458 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_902C1695 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_056EA0A0 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_0CAA105B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105B147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105C147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105D147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105E147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_300A148C = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_197B&DEV_2360 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2361 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2363 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2365 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2366 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"

Here's my storage.ini

CODE

[HardwareIdsDatabase]
PCI\VEN_1095&DEV_3132&SUBSYS_71321095 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_81771043 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_71001462 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_B0031458 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_902C1695 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_056EA0A0 = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_0CAA105B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105B147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105C147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105D147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_105E147B = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_1095&DEV_3132&SUBSYS_300A148C = "Si3132r5", "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
PCI\VEN_197B&DEV_2360 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2361 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2363 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2365 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_197B&DEV_2366 = "Jraid", "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor", "Intel® SATA RAID Controller (32bit)"
PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor", "Intel® SATA AHCI Controller (32bit)"

[SCSI]
iaAHCI   = "Intel® SATA AHCI Controller (32bit)"
iaStor   = "Intel® SATA RAID Controller (32bit)"
Jraid    = "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
Si3132r5 = "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"

Any help appreciated!

iTwins

Oct 29 2006, 11:58 AM

Yzöwl:

Try removing "@" from "Intel@" under the SCSI header

Yzöwl

Oct 29 2006, 12:44 PM

My files do not contain a @ symbol!

The ® is a forum code rendering /display problem, my actual file content is (R)

Tomcat76

Oct 29 2006, 02:26 PM

There is no "SiWinAcc" line under the [SCSI] section. Could that be the reason?

Yzöwl

Oct 29 2006, 04:51 PM

Here is the TxtSetup.OEM, what do you think?

CODE

; This file installs the SiI 3132 Serial ATA Soft RAID 5 and non-RAID driver as part of
; text mode setup on Windows 2000, Windows XP and Windows 2003.
;
; Copyright © 2005 by Silicon Image, Inc.
; All rights reserved


[Disks]
disk1 = "Silicon Image SiI 3132 RAID Driver Installation Disk",\RAID\Si3132r5.sys,\RAID\
disk2 = "Silicon Image SiI 3132 SATA Driver Installation Disk",\SATA\si3132.sys,\SATA\

[Defaults]
SCSI = Si3132r5_XP


[SCSI]                  ; HwComponent section
Si3132r5_XP = "SiI 3132 SATA RAID Controller for Windows XP/Server 2003 (32bit)"
Si3132r5_2K = "SiI 3132 SATA RAID Controller for Windows 2000 (32bit)"
Si3132_XP = "SiI 3132 SATA IDE Controller for Windows XP/Server 2003 (32bit)"
Si3132_2K = "SiI 3132 SATA IDE Controller for Windows 2000 (32bit)"


[Files.SCSI.Si3132r5_XP]
driver = disk1,Si3132r5.sys, Si3132r5
driver = disk1,SiWinAcc.sys, SiFilter
inf = disk1,Si3132r5.inf
dll = disk1,SilSupp.cpl
inf = disk1,SIPPD.inf
catalog = disk1, Si3132r5.cat


[Files.SCSI.Si3132r5_2K]
driver = disk1,Si3132r5.sys, Si3132r5
inf = disk1,Si3132r5.inf
dll = disk1,SilSupp.cpl
inf = disk1,SIPPD.inf
catalog = disk1, Si3132r5.cat

[Files.SCSI.Si3132_XP]
driver = disk2,si3132.sys, Si3132
driver = disk2,SiWinAcc.sys, SiFilter
inf = disk2,SI3132.inf
dll = disk2,SilSupp.cpl
catalog = disk2, Si3132.cat

[Files.SCSI.Si3132_2K]
driver = disk2,si3132.sys, Si3132
inf = disk2,SI3132.inf
dll = disk2,SilSupp.cpl
catalog = disk2, Si3132.cat


[HardwareIds.SCSI.Si3132r5_XP]
id = "PCI\VEN_1095&DEV_3132&SUBSYS_71321095", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_81771043", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_71001462", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_B0031458", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_902C1695", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_056EA0A0", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CAA105B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105B147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105C147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105D147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105E147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_300A148C", "Si3132r5"

[HardwareIds.SCSI.Si3132r5_2K]
id = "PCI\VEN_1095&DEV_3132&SUBSYS_71321095", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_81771043", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_71001462", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_B0031458", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_902C1695", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_056EA0A0", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CAA105B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105B147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105C147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105D147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_105E147B", "Si3132r5"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_300A148C", "Si3132r5"

[Config.Si3132r5]
value = ProblemDevices, "", REG_SZ, ""
value = ProblemDevices, "Maxtor 4D060H3                          DAK05GK0", REG_SZ, "MaxMode = UDMA-5"

[HardwareIds.SCSI.Si3132_XP]
id = "PCI\VEN_1095&DEV_3132&SUBSYS_31321095", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_710A1462", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_B0021458", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CA9105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_3009148C", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_88881019", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_819F1043", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_09781019", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_716A1462", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_715A1462", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CAB105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CAD105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C8F105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C8D105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C8B105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C89105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C87105B", "Si3132"

[HardwareIds.SCSI.Si3132_2K]
id = "PCI\VEN_1095&DEV_3132&SUBSYS_31321095", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_710A1462", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_B0021458", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CA9105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_3009148C", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_88881019", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_819F1043", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_09781019", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_716A1462", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_715A1462", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CAB105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0CAD105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C8F105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C8D105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C8B105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C89105B", "Si3132"
id = "PCI\VEN_1095&DEV_3132&SUBSYS_0C87105B", "Si3132"

[Config.Si3132]
value = ProblemDevices, "", REG_SZ, ""
value = ProblemDevices, "Maxtor 4D060H3                          DAK05GK0", REG_SZ, "MaxMode = UDMA-5"
value = ProblemDevices, "HDS724040KLSA80                         KFAOA32A", REG_SZ, "DisableAtaQueueing"
value = ProblemDevices, "HDS722525VLSA80                         V36OA6MA", REG_SZ, "DisableAtaQueueing"
value = ProblemDevices, "HDS722516VLSA80                         V34OA6MA", REG_SZ, "DisableAtaQueueing"

Obviously I had no need for the 2k stuff.

iTwins

Oct 29 2006, 09:51 PM

QUOTE (Yzöwl @ Oct 30 2006, 12:23 AM)

CODE

[SCSI.Load]
jgogo = jgogo.sys,4
SiWinAcc = SiWinAcc.sys,4

[SCSI]
iaAHCI = "Intel® SATA AHCI Controller (32bit)"

[HardwareIdsDatabase]

As Tomcat76 pointed out, there is no "SiWinAcc"...among other problems too. I've list out the problematic entries (see above)

The strings from all 3 sections MUST MATCH. Yours don't:

1) jgogo is defined in [SCSI.LOAD] but missing in [SCSI] and [HardwareIdsDatabase]
2) SiWinAcc is defined in [SCSI.LOAD] but missing in [SCSI] and [HardwareIdsDatabase]
3) iaAHCI is defined in [SCSI] but missing in [SCSI.LOAD] and [HardwareIdsDatabase]

Take a look at the structure of the VMware driver (the simplest of all drivers) and see what you did wrong with yours:

-------------------------------------------------------
[SCSI.Load]
vmscsi = vmscsi.sys,4

[SCSI]
vmscsi = "VMware SCSI Controller"

[HardwareIdsDatabase]
PCI\VEN_104B&DEV_1040 = "vmscsi"
-------------------------------------------------------

Yzöwl

Oct 29 2006, 10:26 PM

I didn't write the SCSI.Load section, HFSLIP did.

Since those entries are missing in SCSI and HardwareIdsDatabase in my original Txtsetup.oem I didn't think they needed creating as additional entries.

Are you sure that they aren't just 'required' based purely on their extension and not on whether they are needed?

Yzöwl

Oct 31 2006, 09:10 AM

Bump!

Here is the content of the other 2 txtsetup.oem files, as you can see there are no entries in my oem files for jgogo iaAHCI or SiWinAcc. Could you therefore tell me what I need to add that the oem files didn't require.

CODE

; ****************************************************************************
; ****************************************************************************
; **    Filename:  TxtSetup.OEM
; ****************************************************************************
; ****************************************************************************

[Disks]
disk1 = "JMB36X", \x32\jraid.inf, \x32
disk2 = "JMB36X", \amd64\jraid.inf, \amd64

[Defaults]
scsi = JMicron_I386

;----------- Component Section -----------

[scsi]
JMicron_I386     =  "JMicron JMB36X RAID Controller (Windows 2K/XP/2003)"
JMicron_Amd64    =  "JMicron JMB36X RAID Controller (Windows XP/2003 64bit)"

;-------------------------------------------

[Files.scsi.JMicron_I386]
driver  = disk1, jraid.sys, Jraid
driver  = disk1, Jgogo.sys, Jgogo
inf     = disk1, jraid.inf
catalog = disk1, jraid.cat

;-------------------------------------------

[Files.scsi.JMicron_Amd64]
driver  = disk2, jraid.sys, Jraid
driver  = disk2, Jgogo.sys, Jgogo
inf     = disk2, jraid.inf
catalog = disk2, jraid.cat

;-------------------------------------------

[Config.Jraid]
value = parameters\PnpInterface,5,REG_DWORD,1

;--------------------------------------------

[HardwareIds.scsi.JMicron_I386]
id = "PCI\VEN_197B&DEV_2360", "Jraid"
id = "PCI\VEN_197B&DEV_2361", "Jraid"
id = "PCI\VEN_197B&DEV_2363", "Jraid"
id = "PCI\VEN_197B&DEV_2365", "Jraid"
id = "PCI\VEN_197B&DEV_2366", "Jraid"

[HardwareIds.scsi.JMicron_Amd64]
id = "PCI\VEN_197B&DEV_2360", "Jraid"
id = "PCI\VEN_197B&DEV_2361", "Jraid"
id = "PCI\VEN_197B&DEV_2363", "Jraid"
id = "PCI\VEN_197B&DEV_2365", "Jraid"
id = "PCI\VEN_197B&DEV_2366", "Jraid"

CODE

; ****************************************************************************
; ****************************************************************************
; **    Filename:  TxtSetup.OEM
; ****************************************************************************
; ****************************************************************************

[Disks]
disk1 = "Intel Matrix Storage Manager driver for 32bit", \32bit\iaStor.sys, \32bit\
disk2 = "Intel Matrix Storage Manager driver for 64bit", \64bit\iaStor.sys, \64bit\

[Defaults]
scsi = iaStor_32bit

;----------- Component Section -----------

[scsi]
iaStor_32bit = "Intel® SATA RAID Controller (32bit)"
iaAHCI_32bit = "Intel® SATA AHCI Controller (32bit)"
iaStor_64bit = "Intel® SATA RAID Controller (64bit)"
iaAHCI_64bit = "Intel® SATA AHCI Controller (64bit)"


;-------------------------------------------

[Files.scsi.iaStor_32bit]
driver = disk1, iaStor.sys, iaStor
inf    = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_32bit]
driver = disk1, iaStor.sys, iaStor
inf    = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_64bit]
driver = disk2, iaStor.sys, iaStor
inf    = disk2, iaStor.inf
catalog = disk2, iaStor.cat

[Files.scsi.iaAHCI_64bit]
driver = disk2, iaStor.sys, iaStor
inf    = disk2, iaAHCI.inf
catalog = disk2, iaAHCI.cat



;-------------------------------------------

[Config.iaStor]
value = "", tag, REG_DWORD, 1b
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "SCSI miniport"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1

;-------------------------------------------------------

[HardwareIds.scsi.iaStor_32bit]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"


[HardwareIds.scsi.iaAHCI_32bit]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"


[HardwareIds.scsi.iaStor_64bit]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"


[HardwareIds.scsi.iaAHCI_64bit]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"

Also I'm assuming that adding multiple drivers to the txtsetup.sif will not cause any problems; only the required files will load will they?

Oleg_II

Oct 31 2006, 10:54 AM

Sorry gentlemen I can't follow your discussion right now (just came back from a small trip). Will try to concentrate tomorrow.

Can't be 100% sure but just adding drivers to TXTSETUP.SIF shouldn't cause any problem.

Oleg_II

Nov 1 2006, 04:49 AM

Yzöwl
I may be wrong but I think there should be 4 entries into TXTSETUP.SIF and according to the content of OEM files you provided they should be:

CODE

[SourceDisksFiles]
Si3132r5.sys = 1,,,,,,3_,4,1
SiWinAcc.sys = 1,,,,,,3_,4,1
Si3132r5.inf = 1,,,,,,,2,0,0
SilSupp.cpl = 1,,,,,,,2,0,0
SIPPD.inf = 1,,,,,,,2,0,0
Si3132r5.cat = 1,,,,,,,2,0,0
si3132.sys = 1,,,,,,3_,4,1
SI3132.inf = 1,,,,,,,2,0,0
Si3132.cat = 1,,,,,,,2,0,0

[SCSI.Load]
Si3132r5 = Si3132r5.sys,4
si3132 = si3132.sys,4
SiWinAcc = SiWinAcc.sys,4 ; THIS ENTRY IS PROBABLY WRONG! HFSLIP SHOULD MAKE IT AUTOMATICALY FOF ALL SYS FILES.

[scsi]
"si3132" = "Silicon Image SiI 3132 SATA IDE Controller"
"Si3132r5" = "Silicon Image SiI 3132 SATA RAID Controller"

[HardwareIdsDatabase]
PCI\VEN_1095&DEV_3132&SUBSYS_71321095 = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_81771043 = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_71001462 = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_B0031458 = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_902C1695 = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_056EA0A0 = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_0CAA105B = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_105B147B = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_105C147B = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_105D147B = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_105E147B = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_300A148C = "Si3132r5"
PCI\VEN_1095&DEV_3132&SUBSYS_31321095 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_710A1462 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_B0021458 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0CA9105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_3009148C = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_88881019 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_819F1043 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_09781019 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_716A1462 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_715A1462 = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0CAB105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0CAD105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0C8F105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0C8D105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0C8B105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0C89105B = "Si3132"
PCI\VEN_1095&DEV_3132&SUBSYS_0C87105B = "Si3132"

CODE

[SourceDisksFiles]
jraid.sys = 1,,,,,,3_,4,1
Jgogo.sys = 1,,,,,,3_,4,1
jraid.inf = 1,,,,,,,2,0,0
jraid.cat = 1,,,,,,,2,0,0

[SCSI.Load]
jraid = jraid.sys,4
Jgogo = Jgogo.sys,4 ; THIS ENTRY IS PROBABLY WRONG! HFSLIP SHOULD MAKE IT AUTOMATICALY FOF ALL SYS FILES.

[scsi]
jraid = "JMicron JMB36X RAID Controller"

[HardwareIdsDatabase]
PCI\VEN_197B&DEV_2360 = "jraid"
PCI\VEN_197B&DEV_2361 = "jraid"
PCI\VEN_197B&DEV_2363 = "jraid"
PCI\VEN_197B&DEV_2365 = "jraid"
PCI\VEN_197B&DEV_2366 = "jraid"

CODE

[SourceDisksFiles]
iaStor.sys = 1,,,,,,3_,4,1
iaStor.inf = 1,,,,,,,2,0,0
iaStor.cat = 1,,,,,,,2,0,0
iaAHCI.inf = 1,,,,,,,2,0,0
iaAHCI.cat = 1,,,,,,,2,0,0

[SCSI.Load]
iaStor = iaStor.sys,4

[scsi]
"iaStor" = "Intel Matrix Storage Controller"

[HardwareIdsDatabase]
PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"

PS I'm still not sure about adding other (not SYS files) to TXTSETUP.SIF ( = 1,,,,,,,2,0,0) - I've read again today that Windows will look for drivers on CD anyway

Yzöwl

Nov 1 2006, 07:59 AM

Thanks for the response, it does appear, both from my 'guesstimation' and your information, that HFSLIP does indeed create the wrong settings, certainly based upon what I was led to believe was the correct storage.ini data. It not only uses all sys files, but the SourceDiskFiles, data is also different from what you've just given!

Oleg_II

Nov 1 2006, 10:34 AM

Well, this feature is experimental at this stage. Probably there are some problems in it yet.

Could you please help us with coding?

Sorry if I'm too humdrum, repeating just in case:

1. All SYS files from STORAGE folder should be cabbed and listed in TXTSETUP.SIF under SourceDisksFiles sectition like *.SYS = 1,,,,,,4_,4,1,,,1,4 for XP source or *.SYS = 1,,,,,,3_,4,1 for W2k and W2k3.

2. All other files except OEM cabbed and listed under the same sections like * . * = 1,,,,,,,2,0,0

3. Under SCSI.Load section goes the first part of each SYS file (without that extention) and in full like * = *.SYS,4 (no problem if there will be some not needed files here too like with SiWinAcc.sys in your case - nothing bad will happen).

4. All content of STORAGE.INI is written into TXTSETUP.SIF without any changes.

There is still a possibility that if even all additions are made by HFSLIP correctly but there are no corresponding info in STORAGE.INI under SCSI.Load and HardwareIdsDatabase sections. In this case if something is missing or wrong in STORAGE.INI it can be added or corrected. That is why we need testers

Tomcat76

Nov 1 2006, 01:02 PM

Yzöwl...

Are jgogo.sys and SiWinAcc.sys required files? Check if they exist on your system. If they do, there's an easy way to test if you should add extra stuff into STORAGE.INI or not: put both files in the FIX folder instead and run HFSLIP again. If this works and the drivers are installed correctly, you can keep doing this. Otherwise, you'll have to edit STORAGE.INI to add the missing info.

The iaStor/iaAHCI problem is a bit more complex. There are two installation INFs but they refer to the same SYS file. To my knowledge, this can't be done from TXTSETUP.SIF because of the way [SCSI], [SCSI.Load] and [HardwareIdsDatabase] communicate with each other, unless you duplicate iaStor.sys to iaAHCI.sys and edit iaAHCI.inf so it looks for the "new" SYS file instead.

Oleg_II

Nov 1 2006, 01:20 PM

Tomcat76

I don't think it is a problem if jgogo.sys and SiWinAcc.sys are listed in TXTSETUP.SIF even if they are not needed. Anyway the driver installation will need other info that is in STORAGE.INI.

As for two or more INF that are using the same SYS file and having the same ID database I think it also needs chipset supporting INF files like with iaAHCI.inf case (maybe compare installation INF first? if they are the same it is not a problem at all).

But there also could be some preparation work like you suggested with renaming files and editing INF (in this case renamed and edeted files should be included into prepared downloadable package along with STORAGE.INI file).

Yzöwl

Nov 1 2006, 02:19 PM

QUOTE (Oleg_II @ Nov 1 2006, 05:34 PM)

1. All SYS files from STORAGE folder should be cabbed and listed in TXTSETUP.SIF under SourceDisksFiles sectition like *.SYS = 1,,,,,,4_,4,1,,,1,4 for XP source or *.SYS = 1,,,,,,3_,4,1 for W2k and W2k3.

Are you sure about that?

Check out my posted sif, my WXP source is using the data you've stated for W2k3!

Tomcat76

Nov 1 2006, 02:39 PM

QUOTE (Oleg_II @ Nov 1 2006, 08:20 PM)

I don't think it is a problem if jgogo.sys and SiWinAcc.sys are listed in TXTSETUP.SIF even if they are not needed.

Well... Apparantly it is because that's Yzöwl's problem. I'm trying to figure out if he needs those entries in TXTSETUP.SIF or not. But IF they are needed, they should be in all three sections involved.

QUOTE (Yzöwl @ Nov 1 2006, 09:19 PM)

QUOTE (Oleg_II @ Nov 1 2006, 05:34 PM)

Are you sure about that?

Check out my posted sif, my WXP source is using the data you've stated for W2k3!

HFSLIP is using "1,,,,,,3_,4,1,,,1,4" for every OS. Some people say it's like this, others say it's like that... Let's first see if this works out. There's no need for extra coding if it isn't necessary to use different settings per OS.

Oleg_II

Nov 2 2006, 05:00 AM

Tomcat76

QUOTE (Tomcat76 @ Nov 1 2006, 02:39 PM)

QUOTE (Oleg_II @ Nov 1 2006, 08:20 PM)

I don't think it is a problem if jgogo.sys and SiWinAcc.sys are listed in TXTSETUP.SIF even if they are not needed.

Well, these SYS files should be added by HFSLIP automatically to SourceDisksFiles and SCSI.Load section anyway by now (see my examples for his OEM files). I don't think there is a need to add these files to scsi and HardwareIdsDatabase sections as there are no such entries in OEM files. But if I'm wrong we can add these enrties into STORAGE.INI file manually, no need for hard-coding this part.

Yzöwl
I can't even test SATA/RAID drivers. I'm using explanations by others found here and there. We discussed it on previous pages. If your tests prove it is not "1,,,,,,3_,4,1,,,1,4", let us know what settings are working for you, maybe your settings will be more convinient. The more universal it will be the better.

Tomcat76

Nov 2 2006, 09:56 AM

QUOTE (Oleg_II @ Nov 2 2006, 12:00 PM)

Well, these SYS files should be added by HFSLIP automatically to SourceDisksFiles and SCSI.Load section anyway by now

They are

Oleg_II

Nov 2 2006, 11:49 PM

I can't think of anything better

Maybe iTwins is right: probably if a SYS file (in our case SiWinAcc) is listed in [SCSI.LOAD] section it also should be listed in [SCSI] section too? Maybe a dummy line should be created in STORAGE.INI for it? Something like:

QUOTE

SiWinAcc = "Helper for Silicon Controller"

If this statement is true and dummy line is not working there is a work around about this but it will take some more efforts to edit STORAGE.INI in order to add [SourceDiskFiles] section with only needed SYS files with "1,,,,,,3_,4,1,,,1,4". And when HFSLIP runs all files from STARAGE folder including all SYS files will be written into TXTSETUP.SIF with "1,,,,,,,2,0,0". That way some SYS file will be dublicated in System32\Drivers and in System32 folders.

In my opinion there shouldn't be any entries about iaAHCI - there is no corresponding SYS file exectly for it.

[SourceDiskFiles] section may be different because it depends on what files are in STORAGE folder (HFSLIP should list in TXTSETUP.SIF only the files that exist in this folder).

iTwins

Nov 3 2006, 07:54 AM

QUOTE (Oleg_II @ Nov 2 2006, 07:00 PM)

I can't even test SATA/RAID drivers....

Actually, that is not a valid excuse.

Simply load up VMware / Virtual PC and try the installation (even if you don't have the RAID controller), if it didn't show any errors and you can complete the whole Windows installation from beginning to the end, then the driver is most likely working.

QUOTE (Yzöwl @ Oct 30 2006, 12:26 PM)

Are you sure that they aren't just 'required' based purely on their extension and not on whether they are needed?

If I am sure, I will be developing Windows for Microsoft instead

My goal is to make sure the methods I used is a standard and can be repeated on all other drivers. Whether I was overdoing it or not is not as important. As long as it meets my needs and it works, that's all it matters.

QUOTE (Yzöwl @ Nov 2 2006, 04:19 AM)

Are you sure about that? Check out my ...

haha...the guy's a tough one. He reminds me of the top honchos at work who always asks "Are you sure this? Are you sure that?" whenever you try to explain things to them, as if they don't trust you. Normally I would snap back, "If I know everything I wouldn't be working for you!" or "I don't have answers to every question. Trust me or fire me!" Of course, in this case, I would say "Take it or leave it!"

No offense, Yzöwl, just teasing.

QUOTE (Oleg_II @ Nov 3 2006, 01:49 PM)

I am always right!

Actually, simply try it out and see. Like I mentioned earlier, load it up in VMware or Virtual PC. Don't include in [SCSI.LOAD] and/or [SCSI] and see how it goes. If it doesn't errs during installation, then you don't need it. Otherwise, live with it!

My apologies, I haven't had the chance to lend a hand with the testing yet. I'm on vacation mood and I'll be off to Bangkok for a couple of weeks - food, spa, massage, food, spa, massage, food, spa....

Tomcat76

Nov 3 2006, 08:46 AM

My point was that if the "dummy entries" aren't needed when TXTSETUP.OEM is used but they are when TXTSETUP.SIF is used, then there might still be an easy way out: put the SYS files which aren't supposed to be parsed by HFSLIP in the FIX folder. That way, HFSLIP doesn't add the unnecessary entry into the [SCSI.Load] section, and as a consequence you don't need to add dummy entries into STORAGE.INI.

Oleg_II

Nov 3 2006, 05:07 PM

Tomcat76
You are absolutely right. But for those who know which SYS is needed and which is not

it's not difficult to add all files to TXTSETUP.SIF manually

It would be great to do it as much automatical as possible

iTwins

Nov 4 2006, 06:27 AM

I ran v1.0.1 with storage.ini in VMware Workstaiton v5.5.2 and I encountered this error:

..and teh following were added into the TXTSETUP.SIF

CODE

[SourceDisksFiles]
HFSLIPWU.INF = 1,,,,,,,20,0,0
A320RAID.CAT = 1,,,,,,,2,0,0,,1,2
A320RAID.INF = 1,,,,,,,20,0,0,,1,20
A320RAID.SYS = 1,,,,,,3_,4,1,,,1,4
AACCIN.DLL = 1,,,,,,,2,0,0,,1,2
AACMGT.INF = 1,,,,,,,20,0,0,,1,20
AACSAS.CAT = 1,,,,,,,2,0,0,,1,2
AACSAS.INF = 1,,,,,,,20,0,0,,1,20
AACSAS.SYS = 1,,,,,,3_,4,1,,,1,4
COCPYINF.DLL = 1,,,,,,,2,0,0,,1,2
DELPSEUD.INF = 1,,,,,,,20,0,0,,1,20
IAAHCI.CAT = 1,,,,,,,2,0,0,,1,2
IAAHCI.INF = 1,,,,,,,20,0,0,,1,20
IASTOR.CAT = 1,,,,,,,2,0,0,,1,2
IASTOR.INF = 1,,,,,,,20,0,0,,1,20
IASTOR.SYS = 1,,,,,,3_,4,1,,,1,4
MPIXP32.CAT = 1,,,,,,,2,0,0,,1,2
QL2300.CAT = 1,,,,,,,2,0,0,,1,2
QL2300.SYS = 1,,,,,,3_,4,1,,,1,4
QL2X00.INF = 1,,,,,,,20,0,0,,1,20
QL2XHAI2.DLL = 1,,,,,,,2,0,0,,1,2
QLPSEUDO.INF = 1,,,,,,,20,0,0,,1,20
QLSDM.DLL = 1,,,,,,,2,0,0,,1,2
SYMMPI.CAT = 1,,,,,,,2,0,0,,1,2
SYMMPI.DBG = 1,,,,,,,2,0,0,,1,2
SYMMPI.INF = 1,,,,,,,20,0,0,,1,20
SYMMPI.PDB = 1,,,,,,,2,0,0,,1,2
SYMMPI.SYS = 1,,,,,,3_,4,1,,,1,4
SYMMPI.TAG = 1,,,,,,,2,0,0,,1,2
SYMMPO.INF = 1,,,,,,,20,0,0,,1,20
ULTRA.CAT = 1,,,,,,,2,0,0,,1,2
ULTRA.INF = 1,,,,,,,20,0,0,,1,20
ULTRA.SYS = 1,,,,,,3_,4,1,,,1,4
VMSCSI.CAT = 1,,,,,,,2,0,0,,1,2
VMSCSI.INF = 1,,,,,,,20,0,0,,1,20
VMSCSI.SYS = 1,,,,,,3_,4,1,,,1,4

[SCSI.Load]
A320RAID = A320RAID.SYS,4
AACSAS = AACSAS.SYS,4
IASTOR = IASTOR.SYS,4
QL2300 = QL2300.SYS,4
SYMMPI = SYMMPI.SYS,4
ULTRA = ULTRA.SYS,4
VMSCSI = VMSCSI.SYS,4

;--------------------------------------------------
;VMWARE

[HardwareIdsDatabase]
PCI\VEN_104B&DEV_1040 = "vmscsi", "VMware SCSI Controller"

[SCSI]
vmscsi = "VMware SCSI Controller"

;--------------------------------------------------

The reason?

If you look in DOS, you will notice that the files A320RAID.SY_ and all other .SY_ files that are declared in [SCSI.LOAD] are missing in the $WIN_NT$.~BT directory. To correct that, you need to match those files into DOSNET.INF's [FILES] and [FLOPPYFILES.2] sections as well.

Sadly, in this case, even if you fixed the DOSNET.INF issue, you still get a BSoD.

I am still investigating...

A proprosal

Rather than using STORAGE.INI, is it possible to get HFSLIP to do everything intelligently and automated. To do that, follow these steps:

*** I use QLOGIC's driver because its one of the more complicated ones

1) scan for each INF file within HKEXPERT\STORAGE for the string under the [Manufacturer] header. There can only be one string in [Manufacturer].

Example:

CODE

[Manufacturer]
%QLOGIC%=QLOGIC,NT.5.2

Watch out though, not all drivers include a comma. Most drivers look like this:

CODE

[Manufacturer]
%ADP%= ADAPTEC

2) Skip the value name but keep the value. In the above example, rename the comma in ",NT 5.2" and replace it with a period. ex ".NT.5.2"

3) Search for the [QLOGIC.NT.5.2] header and scan all the PCI\VEN entries.

Example:

CODE

[QLOGIC.NT.5.2]
%ql2300.DeviceDesc% = ql2300_Inst, PCI\VEN_1077&DEV_2432&SUBSYS_01371077

extract the vendor and device codes

CODE

PCI\VEN_1077&DEV_2432&SUBSYS_01371077

4) Take the code and intelligently place it into TXTSETUP.SIF as:

CODE

[HardwareIdsDatabase]
PCI\VEN_1077&DEV_2432&SUBSYS_01371077 = "qlogic", "????"

5) Finally, search for the value name "Floppy_Desc" under the [STRINGS] header and you can find the device name. Stick the device name into these two areas in TXTSETUP.SIF:

CODE

[HardwareIdsDatabase]
PCI\VEN_1077&DEV_2432&SUBSYS_01371077 = "qlogic", "QLogic Software Diskette"

[SCSI]
qlogic = "QLogic Software Diskette"

Oh. Be sure to declare in DOSNET.INF as well.

If you can succeed here, then you are home free.

Tomcat76

Nov 4 2006, 01:26 PM

Can't be done. The biggest hurdle is that DOS can't parse sections of a file... like search for the header [Whatever] and output anything below it until the next header.

iTwins

Nov 4 2006, 06:28 PM

QUOTE (Tomcat76 @ Nov 5 2006, 03:26 AM)

Can't be done. The biggest hurdle is that DOS can't parse sections of a file... like search for the header [Whatever] and output anything below it until the next header.

Pure batch programming cannot but 3rd party DOS programs can. It's not like HFSLIP is purely batch file only so using 3rd party programs doesn't break that rule. I think I have such a program tucked away somewhere here...CHGINI16.EXE and INIFILE.EXE (attached)

I don't remember what are the differences between the two but...

Sample commandline:

CHGINI16 C:\UNATTEND.TXT "GuiUnattended" "TimeZone" %TIMEZONE% > nul

INIFILE SET C:\UNATTEND.TXT -s"params.MS_TCPIP.Adapter1" -kDHCP -vYES > nul

If push comes to shove, you can always get HFSLIP to call up a VBScript or Kixtart script. Either one of them can be easily done. Both compilers can be run in XP/2000/2003/Vista.

Cheers.

Oleg_II

Nov 5 2006, 02:33 AM

Less universal but easier to implement: HFSLIP will write all entries into TXTSETUP.SIF only from prepared STORAGE.INI and won't write anything else by itself. Files from STORAGE folder will only be cabbed and added to i386 folder.

STORAGE.INI will contain ALL four sections to include into TXTSETUP.SIF for all known drivers.

If needed there should be one more helper file like STOREDOSNET.INI that will aslo include some settings for DOSNET.INF.

That way it should be easier to integrate and it should work for all existing drivers but it will need regualar updating of these helper INI files cause some new storage drivers may be introduced.

Yzöwl

Nov 13 2006, 10:16 AM

I have made some changes to the STORAGE DRIVERS section of the HFSLIP file in order to rid myself of the error I was getting.

Basically what I am doing is putting the emphasis on having correct storage*.ini(s).

The procedure parses the ini file(s) and only puts existing files mentioned under its [SCSI] section under the [SCSI.Load] section of TXTSETUP.SIF.

Here is the code:

CODE

REM ======================STORAGE DRIVERS=================================================
:HFSTOR
TITLE %T1% - Processing Storage Drivers
:: THANKS TO OLEG II FOR ANOTHER GREAT IDEA
>HFSTOR.TXT DIR/B HFEXPERT\STORAGE
>HFSTORI.TXT DIR/B HFEXPERT\STORAGE\STORAGE*.INI
FOR /F %%I IN ('FINDSTR/VG:HFSTORI.TXT HFSTOR.TXT') DO (
	MAKECAB /D CompressionMemory=%COMPMEM% /D CompressionType=LZX HFEXPERT\STORAGE\%%I /L SOURCESS\I386 >NUL
	>>SOURCESS\I386\DOSNET.INF ECHO/d1,%%I
	IF /I "%%~xI"==".SYS" (
		>>SOURCESS\I386\TXTSETUP.SIF ECHO/%%I = 1,,,,,,3_,4,1,,,1,4) ELSE (
			IF /I "%%~xI"==".INF" (
			>>SOURCESS\I386\TXTSETUP.SIF ECHO/%%I = 1,,,,,,,20,0,0,,1,20) ELSE (
				>>SOURCESS\I386\TXTSETUP.SIF ECHO/%%I = 1,,,,,,,2,0,0,,1,2)))
>>SOURCESS\I386\TXTSETUP.SIF (ECHO/&ECHO/[SCSI.Load])
FOR /F %%I IN (HFSTORI.TXT) DO (CALL :DOINIS %%I)
FOR /F %%I IN (HFSTORI.TXT) DO (>>SOURCESS\I386\TXTSETUP.SIF (ECHO/&TYPE HFEXPERT\STORAGE\%%I&ECHO/))
ECHO/>>SOURCESS\I386\TXTSETUP.SIF
DEL/Q/F HFSTOR*.TXT
GOTO EOF
:DOINIS
FOR /F "EOL=[ DELIMS== " %%I IN ('FIND /V "\" ^<HFEXPERT\STORAGE\%1') DO (
	IF EXIST HFEXPERT\STORAGE\%%I.SYS (>>SOURCESS\I386\TXTSETUP.SIF ECHO/%%I = %%I.SYS,4))
GOTO EOF
REM ======================================================================================

One last thing you may notice from it, is that you can have multiple ini files in your \STORAGE directory.
(if you find it easier to manage that way)
e.g.

storage_ibm.ini
storage_adaptec.ini
storage_intel.ini
storage_sii.ini
storage_jmicron.ini

I have as yet been unable to test the results of this on my particular machines, it does get rid of the error and allows a full install in my virtual machine.

Hope it helps a little!

Oleg_II

Nov 13 2006, 08:39 PM

Yzöwl

Thank you very much! Some people agree that it would be easier to have a few STORAGE*.INI files according to manufactories. I've got a copy of Universal Installation Utility that should contain a lot of them. When I have some free time I'll make a couple of these INI

glentium

Nov 13 2006, 09:26 PM

Count me in. I agree that it's easier to have few STORAGE_*.INI files.. It's much simpler that way, I think.

Tomcat76

Nov 14 2006, 09:39 PM

Multiple STORAGE*.INI files are supported since version 61014c... That's about a month already...

I'll check out the other suggestions...

Tomcat76

Nov 14 2006, 09:58 PM

OK... It's done. Version 1.0.4rc2. Thanks, Yzöwl...

Tinnitus

Nov 24 2006, 12:47 PM

Hi there. After reading many threads about how to do the integration (other forums, too) I must admit that I am quite like

.

I want to integrate the drivers for the Controllers on the Asus P5W DH Deluxe (mainboard popular with many gamers) in order to avoid pressing F6 (I don't have a floppy drive). Actually it contains 3 Controllers, the ICH7R Southbridge, Jmicron JMB363 SATA, Silicon Image 4723 Hardware RAID Controller (EZ Backup). For the JMicron Controller there is a folder for the disk to be created on the support cd, containing these files:

jgogo.sys
jraid.cat
Jraid.sys
jraid_finf (attached)
txtsetup.oem (attached)

I was editing the storage.ini like the following, but got stuck with the first value. However, you were diskussing a different method.

[HardwareIdsDatabase]
PCI\VEN_197B&DEV_2360&CC_0104 = "

", "JMicron JMB36X Controller"
...

The ICH7R Southbridge RAID Controller drivers are included in the chipset drivers. I attached the corresponding inf-file, too.

Could anyone help me integrating these drivers? I could test the result for you

Oleg_II

Nov 24 2006, 10:26 PM

Tinnitus

I had a quick look at the provided files. Try this (copy, past into Notepad and save as STORAGE.INI):

CODE

[scsi]
jraid = "JMicron JMB36X Controller"

[HardwareIdsDatabase]
PCI\VEN_197B&DEV_2360&CC_0104 = "jraid"
PCI\VEN_197B&DEV_2361&CC_0104 = "jraid"
PCI\VEN_197B&DEV_2363&CC_0104 = "jraid"
PCI\VEN_197B&DEV_2365&CC_0104 = "jraid"
PCI\VEN_197B&DEV_2366&CC_0104 = "jraid"
PCI\VEN_197B&DEV_2360&CC_0106 = "jraid"
PCI\VEN_197B&DEV_2361&CC_0106 = "jraid"
PCI\VEN_197B&DEV_2363&CC_0106 = "jraid"
PCI\VEN_197B&DEV_2365&CC_0106 = "jraid"
PCI\VEN_197B&DEV_2366&CC_0106 = "jraid"

After running HFSLIP check (open with Notepad and look at the end of the file) if the lines above are included into TXTSETUP.SIF along with these few lines:

CODE

[SourceDisksFiles]
jraid.sys = 1,,,,,,3_,4,1
Jgogo.sys = 1,,,,,,3_,4,1
jraid_f.inf = 1,,,,,,,2,0,0
jraid.cat = 1,,,,,,,2,0,0

[SCSI.Load]
jraid = jraid.sys,4
;Jgogo = Jgogo.sys,4; This entry is made automatically and probably wrong!

You aslo can add your ich7core.inf into STORAGE or DRIVER folders.

If you have any other questions I'll try to help you (if I can).

Tinnitus

Nov 25 2006, 04:28 PM

That did not work

I connected the drives to the ICH7R Controller and configured them as a RAID 1 Volume, but the created installation CD will not detect the drive.

I edited the storage.ini (which I took from the first post) and added what you told me (concerning the JMicron controller). Also, I copied all .cat and .inf from the Chipset driver (ICHxx.inf ICHxx.cat) to the STORAGE-Directory. I guess I have to add something for the Chipset driver, too.

Tinnitus

Nov 25 2006, 04:51 PM

Okay

I found out that I did not use the right folder for the ICH7 controller. There is a folder for a driver disk containing:
iaahci.cat
iaahci.inf
iastor.cat
iastor.inf
iastor.sys
textsetup.oem

Looks like the info contained in these .inf files is already in the storage.ini provided in this thread. Ill give it another try WITH the correct files.

(switching back to JMicron controller)
Maybe I should write Jraid instead of jraid?

Tinnitus

Nov 26 2006, 01:18 AM

Now he found the driver on the CD and detected my RAID 1 Volume. I installed Windows and rebooted and get a message that Windows could not access the hardisk folders for some reason.

Update: Started Rescue mode and did a bootcfg /rebuild which correctly adds a multi(0)... boot entry to boot.ini. Afterwards he searches for iastor.sys or iastor.sy_ and I have to select the i386 folder manually. Cannot this be done automatically?

Oleg_II

Nov 26 2006, 03:14 AM

Have to look into installation INF. I'm going to the airport in a few minutes. Come back in a few hours or tomorrow (hopefully my flight won't be delayed - it's raining here).

You can try without chipset drivers in STORAGE folder first (or place them into OEM folder on CD or into DRIVERS folder before HFSLIPing).

A quick look (try this STORAGE.INI):

CODE

[scsi]
iastor = "Intel SATA RAID Controller"

[HardwareIdsDatabase]
PCI\VEN_8086&DEV_27C6&CC_0104 = "iastor"
PCI\VEN_8086&DEV_2682&CC_0104 = "iastor"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iastor"
PCI\VEN_8086&DEV_2652&CC_0104 = "iastor"
PCI\VEN_8086&DEV_2682&CC_0104 = "iastor"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iastor"
PCI\VEN_8086&DEV_2652&CC_0104 = "iastor"

Check if there are lines in TXTSETUP.SIF (or they a bit different):

QUOTE

[SourceDisksFiles]iaahci.cat = 1,,,,,,,2,0,0
iaahci.inf = 1,,,,,,,2,0,0
iastor.cat = 1,,,,,,,2,0,0
iastor.inf = 1,,,,,,,2,0,0
iastor.sys = 1,,,,,,3_,4,1

[SCSI.Load]
iastor = iastor.sys,4

My flight was delayed

x-pert

Dec 4 2006, 12:14 PM

Oleg_II

If I'll extract the Sneaky's MassStorage driver pack to STORAGE folder will be OK for HFSLIP or anyway I must put only binaries without folders?

Oleg_II

Dec 4 2006, 11:50 PM

x-pert

I think HFSLIP won't work with folders.

By the way, I was on the computer market in GZ last weekend trying to buy a motherboard with a controller which needs a floppy during install. I coundn't find one

All new motherboards support SATA drives during installation without using floppy. I even found one with a couple of floppies but XP installedj fine on it without using them

I learnt that drivers should be installed after system installation in order to use all potential of SATA drives.

Tomcat76

Dec 5 2006, 12:01 AM

Oleg!

Welcome back...

Go in the BIOS and see if you can set the controller to RAID. Normally, this should configure the controller for JBOD mode if you only have a single drive connected to it. I think Windows will require a floppy then...

Oleg_II

Dec 5 2006, 12:17 AM

I suspected something about RAID. That is why I stated only SATA

But as I know nearly nothing about this. I didn't buy the motherboard I just tried to install XP with SATA by default in one friend's shop.

Ausmith1

Dec 7 2006, 11:28 AM

I'm having a problem integrating the IBM ServerRAID 8 SAS RAID drivers into a Windows 2003 SP1 install.
The slipstreamed install picks up the SAS controller just fine during textmode install but when the OS is fully installed no RAID device shows up in the Device Manager.

The file ARCSAS.SYS is in my HFSlip\HFEXPERT\STORAGE folder and the following is in my storage.ini file:

CODE

;--------------------------------------------------
; Adaptec RAID controllers Storport miniport for IBM SAS based ServeRAID HBAs

[HardwareIdsDatabase]
PCI\VEN_9005&DEV_0285&SUBSYS_02f21014 = "arcsas", "IBM ServeRAID 8i Controller"
PCI\VEN_9005&DEV_0285&SUBSYS_02989005 = "arcsas", "Adaptec SAS RAID 4000SASx Controller"
PCI\VEN_9005&DEV_0285&SUBSYS_02999005 = "arcsas", "Adaptec SAS RAID 4800SAS Controller"
PCI\VEN_9005&DEV_0285&SUBSYS_029A9005 = "arcsas", "Adaptec SAS RAID 4805SAS Controller"
PCI\VEN_9005&DEV_0285&SUBSYS_02A49005 = "arcsas", "ICP SAS RAID ICP9085LI Controller"
PCI\VEN_9005&DEV_0285&SUBSYS_02A59005 = "arcsas", "ICP SAS RAID ICP5085BR Controller"
PCI\VEN_9005&DEV_0286&SUBSYS_95801014 = "arcsas", "IBM ServeRAID 8k/8k-l Controller"
PCI\VEN_9005&DEV_0286&SUBSYS_95401014 = "arcsas", "IBM ServeRAID 8L Controller"
PCI\VEN_9005&DEV_0286&SUBSYS_02A29005 = "arcsas", "Adaptec SAS RAID 4810SAS Controller"
PCI\VEN_9005&DEV_0286&SUBSYS_02A39005 = "arcsas", "ICP SAS RAID ICP5085AU Controller"

[SCSI]
arcsas = "IBM ServeRAID SAS Controller"

;--------------------------------------------------

Running "DEVCON hwids * " shows none of the PCI ids of the ServeRAID HBA and without the ability to check if a ServeRAID card is in the system I can't really determine if I should install the ServeRAID Manager application.
I've attached the original inf file for the arcsas driver.

Any ideas?

Oleg_II

Dec 8 2006, 04:54 AM

Ausmith1
Do you also have ARCASAS.INF in HFSlip\HFEXPERT\STORAGE? Because after installing Windows needs to install the driver also and it needs installation INF.

Ausmith1

Dec 8 2006, 09:36 AM

No, I don't have that INF there. Let me try that...
Thanks!

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.