1 Reply by Stiertje

(125 replies, posted in DriverPack Mass Storage)

Jaak wrote:

Hi

please all check WHICH BIOS this Sil 3112 chip uses.
I know 3112 was not tested enough. (for lack of people with that hardware).

Tried it on BIOS 4.2.83 and 4.2.84. Will try to downgrade further to see if it helps.

Go to forum: DriverPack Mass Storage

2 Reply by Stiertje

(125 replies, posted in DriverPack Mass Storage)

Hey guys, back from a long pause in driverpacks-fiddling. Busy at work and stuff ........


Anyway, this week I tried to make a new integrated XP CD, and I read the recent changes you guys made to the mass-storage packs, so I decided to give it a go again with the new driverpacks. With the new mass-storage driverpacks I again was greeted by the wellknown 0x0..7B BSOD, but the strange thing was that I got it instantly, even before initial copy of install files. Normally I would see files being copied to HD and the setup would BSOD while starting the GUI part, but now it already crashes BEFORE file-copy.

I did make a different kind of integrated cd, since I tried to integrate IE7 and WMP11 into it, so that may be the problem. I'm gonna make a vanilla SP2 cd with only the driverpacks again to try some things out. Hopefully work pressure will allow it.

Ow, BTW, SATA controler is a Silicon Image 3112 SATALink card with an Atmel AT49BV512 chip. May be usefull info ......

Go to forum: DriverPack Mass Storage

3 Reply by Stiertje

(36 replies, posted in DriverPack Mass Storage)

Gonna build a new cd with those goodies and hopefully I can test it in the evening. Will let you know the results.

Go to forum: DriverPack Mass Storage

4 Reply by Stiertje

(27 replies, posted in DriverPack Mass Storage)

Debugger wrote:

Jaak, do you release an experimental pack (with HWIDs tagged with &CC_0101 or &CC_0104) again?

Another question: how I can to determine sata bios version? (for SiI chip)

You can find the BIOS version in the properties of the Silicon Image Controler, which you can find under "hardware manager - SCSI controlers"

Go to forum: DriverPack Mass Storage

5 Reply by Stiertje

(27 replies, posted in DriverPack Mass Storage)

Ok, got some info out of the TXTSETUP.SIF that is different. nLite makes some additions to the SIF file that makes it work.

[SourceDisksNames.x86]
1984= %cdname%,%cdtagfilei%,,"\i386\NLDRV\001"

[WinntDirectories]
1984= NLDRV\001

[SourceDisksFiles.x86]
si3112.cat = 1984,,,,,,,1984,0,0
si3112.inf = 1984,,,,,,,1984,0,0
si3112.sys = 1,,,,,,4_,4,1,,,1,4
si3112.sys = 1984,,,,,,,1984,0,0
silsupp.cpl = 1984,,,,,,,1984,0,0
SiRemFil.sys = 1,,,,,,4_,4,1,,,1,4
siremfil.sys = 1984,,,,,,,1984,0,0
siwinacc.sys = 1984,,,,,,,1984,0,0

[HardwareIdsDatabase]
PCI\VEN_1095&DEV_3112&SUBSYS_31121095 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_34238086 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_311215D9 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_B0021458 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_01661028 = "Si3112"
PCI\VEN_1095&DEV_3112&SUBSYS_81E8104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_35121095 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_01661028 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_35121014 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_02B71014 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_B0021458 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_820B104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_145A1462 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_001F6409 = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_9003104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_35121A5F = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_000E182D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_901B104D = "Si3112"
PCI\VEN_1095&DEV_3512&SUBSYS_3512131F = "Si3112"
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 = "Si3112"
PCI\VEN_1002&DEV_4379&SUBSYS_43791002 = "Si3112"
PCI\VEN_1002&DEV_437A&SUBSYS_437A1002 = "Si3112"

[SCSI.Load]
Si3112 = si3112.sys,4
Si3112 = SiRemFil.sys,4

[FileFlags]
si3112.sys = 16
SiRemFil.sys = 16

[SCSI]
Si3112 = "Silicon Image SiI 3x12 SATALink Controller for Windows XP/Server 2003"

Of course almost all is in the file somewhere already, added by Driverpacks Base, and I don't know the significance of the [FileFlags] tab. Main thing is that the [SCSI.Load] additions are on top of the whole list. This means that they load before the rest, and I seem to recall some issue with SiI Raid devices where the solution was to let the Raid driver load before the Base driver

.......

Found where it was mentioned

7.04 (03 Apr 07)
Fixed
- ATI (Siliconimage) 3112 driver (Muiz)
- INI: [V-3] appeared twice (Jaak)
- INI: [H-1], fix for win2003 and XP. (also a Bart PE fix) (OverFlow & jtdoom)
- INI: make Silicon Image SiI3112r RAID mode drivers load before non-RAID (Jaak)
- INI: [IN-2-winnt-x86], added: "Intel ICP Vortex SCSI RAID" (Jaak)

.......

Anyway, 7.04 was the driverpack version where things were starting to go wrong, so it might be the problem.




Greetz

Go to forum: DriverPack Mass Storage

6 Reply by Stiertje

(27 replies, posted in DriverPack Mass Storage)

Debugger wrote:

Try to detalise a HWID for RAID, and same HWID for BASE:

PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0101 - for BASE
PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0104 - for RAID

I think it must to help.

I see what you mean. Didn't think about that.

Anyway, I integrated the latest drivers with nLite after the driverpacks integration, and that seems to work out fine. Maybe I can find out what exactly is different between my cd with only the driverpacks and my cd with manually integrated (well, nlited) si3112 driver. I hope to have some time tomorrow, so I will let you know if I see something different.



Greetz and goodnight.

Go to forum: DriverPack Mass Storage

7 Reply by Stiertje

(27 replies, posted in DriverPack Mass Storage)

Jaak wrote:

Stiertje, can you post the HWIDS of that silicon chip you have?
And... what BIOS does it have?

The problem was reported some time ago in this forum post:
http://forum.driverpacks.net/viewtopic.php?id=1676

Anyway, here are my HWID's

=========== 
PCI Devices 
=========== 
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_00F2&SUBSYS_98901462&REV_A2\4&102AC5BC&0&00F0: NVIDIA GeForce 6600 
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
18 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_C517\5&DF9F058&0&2                         : USB Composite Device
USB\VID_046D&PID_C517&MI_00\6&247A621&0&0000                : USB Human Interface Device
USB\VID_046D&PID_C517&MI_01\6&247A621&0&0001                : USB Human Interface Device
USB\VID_05E3&PID_0606\5&221832C9&0&2                        : Generic USB Hub
USB\VID_05E3&PID_0702\5&221832C9&0&3                        : USB Mass Storage Device
USBSTOR\DISK&VEN_TOSHIBA&PROD_MK4025GAS&REV_0811\6&38C08D00&0: TOSHIBA MK4025GAS USB Device
9 matching device(s) found.
 
============= 
Input Devices 
============= 
HID\VID_046D&PID_C517&MI_00\7&29B49A7B&0&0000               : Logitech HID-Compliant Keyboard
HID\VID_046D&PID_C517&MI_01&COL01\7&149ECB2&0&0000          : Logitech HID-compliant Cordless Mouse
HID\VID_046D&PID_C517&MI_01&COL02\7&149ECB2&0&0001          : HID-compliant consumer control device
HID\VID_046D&PID_C517&MI_01&COL03\7&149ECB2&0&0002          : HID-compliant device
HID\VID_046D&PID_C517&MI_01&COL04\7&149ECB2&0&0003          : HID-compliant device
HID\VID_046D&PID_C517&MI_01&COL05\7&149ECB2&0&0004          : HID-compliant device
6 matching device(s) found.
 
============ 
ACPI Devices 
============ 
ACPI\AUTHENTICAMD_-_X86_FAMILY_6_MODEL_8\_0                 : AMD Athlon(tm) XP 2400+
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\PNP0000\3&13C0B0C5&0                                   : Programmable interrupt controller
ACPI\PNP0100\3&13C0B0C5&0                                   : System timer
ACPI\PNP0200\3&13C0B0C5&0                                   : Direct memory access controller
ACPI\PNP0303\3&13C0B0C5&0                                   : PS/2 Keyboard
ACPI\PNP0401\3&13C0B0C5&0                                   : ECP Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0501\2                                              : Communications Port (COM2)
ACPI\PNP0700\3&13C0B0C5&0                                   : Standard floppy disk controller
ACPI\PNP0800\3&13C0B0C5&0                                   : System speaker
ACPI\PNP0A03\1                                              : PCI bus
ACPI\PNP0A06\3&473F1A46&0                                   : Extended IO Bus
ACPI\PNP0B00\3&13C0B0C5&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\3                                              : Motherboard resources
ACPI\PNP0C02\4                                              : Motherboard resources
ACPI\PNP0C04\3&13C0B0C5&0                                   : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0F13\3&13C0B0C5&0                                   : PS/2 Compatible Mouse
ACPI\PNPA000\4&5D18F2DF&0                                   : SCSI/RAID Host Controller
ACPI\PNPB006\3&13C0B0C5&0                                   : NVIDIA(R) nForce(TM) MIDI UART
ACPI\PNPB02F\3&13C0B0C5&0                                   : Standard Game Port
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : Advanced Configuration and Power Interface (ACPI) PC
26 matching device(s) found.

At the moment the BIOS version is 4.2.83. S\4\B does not have an entry yet for this HWID. S\4 does have an entry, but that one also didn't work. The problem still remains that the card is recognized in textmode as a Raid device instead of a Base device.

BTW, did some research:

- PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 is in both S-4 and S-5, though TXTSETUP.SIF only gives the non-raid version. Same counts for PCI\VEN_1002&DEV_4379&SUBSYS_43791002 and PCI\VEN_1002&DEV_437A&SUBSYS_437A1002
- PCI\VEN_1095&DEV_3112&SUBSYS_31121095 is in S-4, but not in S-4-B

Don't know if it is usefull information though.

Go to forum: DriverPack Mass Storage

8 Reply by Stiertje

(27 replies, posted in DriverPack Mass Storage)

I saw that there was an update for the Silicon Image 3112 cards. I tried the 7.09.4 MassStorage driverpack but it gives a 0x7B BSOD on both 4.x.79 and 4.x.83 BIOS regretfully. Text installation still recognizes the card as a SataRAID card.

Go to forum: DriverPack Mass Storage

9 Reply by Stiertje

(11 replies, posted in DriverPack Mass Storage)

Jaak wrote:

well, I had not noticed that.

http://www.siliconimage.com/support/sup … sid=4&
this says 4.x.84, and when you click the link, it leads to BIOS 4.3.84, but it then spcifies chip variant 3512...

but... huh?
When one looks for 3112 bios, you get bios 4.2.83.
small wonder there are always problems with silicon image.

Yup, I saw that too. And even the highest version of the 3512 chipset only goes to 4.3.83, so I have absolutely no idea where the 4.x.84 comes from. I think I'm going to try and contact Silicon Image about this thing, since I think programming the wrong BIOS in your card, if it even works, might not have desirable effects.

Also some typo's from me;
- SiI3112 has BIOS 4.2.xx
- SiI3512 has BIOS 4.3.xx

Go to forum: DriverPack Mass Storage

10 Reply by Stiertje

(11 replies, posted in DriverPack Mass Storage)

Got a little question here.

I've just finished testing the new MassStorage driverpack, and regretfully it still won't work with my SiI3112 SataLink card. Substituting the drivers from the SFXMiniPacks also doesn't work for me.

Now the funny thing is that in the MassStorage driverpack the newest BIOS is mentioned being 4.x.84. I've checked on the website of Silicon Image multiple times, and I also searched with Google, but the highest version BIOS I can find is 4.3.83. Where can I find this 4.x.84 BIOS that is mentioned?

Anyway, gonna try and downgrade my BIOS version to 4.3.79 to see if that one will work with the drivers from SFXMiniPack.

Go to forum: DriverPack Mass Storage

11 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

Fresh delivery of HWID's. Doesn't seem to be different though.

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 SERIES          
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce 6200 
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : Logitech QuickCam Express
4 matching device(s) found.
 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 SERIES          
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce 6200 
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : Logitech QuickCam Express
USB\VID_05E3&PID_0702\5&221832C9&0&3                        : USB Mass Storage Device
USBSTOR\DISK&VEN_TOSHIBA&PROD_MK4025GAS&REV_0811\6&38C08D00&0: TOSHIBA MK4025GAS USB Device
6 matching device(s) found.
 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 / RADEON VE Family (Microsoft Corporation)
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: SM Bus Controller
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: Standard Dual Channel PCI IDE Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: Ethernet Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Multimedia Audio Controller
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: PCI standard RAM Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: Video Controller (VGA Compatible)
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : USB Device
USB\VID_05E3&PID_0702\5&221832C9&0&3                        : USB Mass Storage Device
USBSTOR\DISK&VEN_TOSHIBA&PROD_MK4025GAS&REV_0811\6&38C08D00&0: TOSHIBA MK4025GAS USB Device
6 matching device(s) found.

It even recognized and had drivers for my Radeon 7000 graphics card. Go figure how old that crap card is tongue

Go to forum: DriverPack Mass Storage

12 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

Sorry bro, HWID overlap is still in the file "DriverPack_MassStorage_blablabla.ini". I even re-downloaded the pack to be sure.
And with the overlap I mean it's an overlap inside the INI file, not in the actual folders. I'm not sure if it matters, just thought you should know.

Well, I'm gonna try and get you that vanilla HWID of my card. Will let you know in an hour or so.

Go to forum: DriverPack Mass Storage

13 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

Darn, no luck.

When I only use Driverpacks and nothing else I still recieve the BSOD, but now before I even have the chance of choosing a partition.

BTW, I also found a HWID overlap between [S-4] and [S-5]

PCI\VEN_1095&DEV_3512&SUBSYS_02B71014

Go to forum: DriverPack Mass Storage

14 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

jtdoom wrote:

besides, I am a blonde..

You know what they say about blondes. tongue

Anyway, I still had no luck with the new MassStorage pack, so I'm going to try out some different angles.

- Slipstream an older pack, notably 7.04 which has worked before
- Only slipstream driverpacks and nothing else
- And if that doesn't help, only slipstream MassStorage driverpack

Will let you know what I find out.

Go to forum: DriverPack Mass Storage

15 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

jtdoom wrote:

hi
suppose you still needed a floppy because there is no good txtmode driver, then OemPreinstall=Yes says you cannot use the floppy.

I've made many disks with driverpacks, and just recently (after 7.04) it started BSOD'ing. Older builds worked like a charm.

Anyway, I don't think it is a faulty driver. My SATA card is recognized as an SiI3112r instead of the base SiI3112. This probably screws up the GUI mode setup because of the discrepancies between the Raid and the Base card drivers.

I'm going to make another build with the 7.07 MassStorage pack. /me is crossing his fingers.

Go to forum: DriverPack Mass Storage

16 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

jtdoom wrote:

hi
does it have  OemPreinstall=Yes  or     OemPreinstall=1 in winnt.sif ?

Here's my WINNT.SIF

[Data]
AutomaticUpdates="No"
Autopartition=0
MsDosInitiated=0
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
UnattendSwitch="Yes"
OemPreinstall="Yes"
OemSkipEula="Yes"
ComputerType="Advanced Configuration and Power Interface (ACPI) PC", Retail
FileSystem=*
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
Hibernation="No"

[Display]
Xresolution=1152
Yresolution=864
BitsPerPel=32
Vrefresh=75

[SystemRestore]
DisableSR=1
CreateFirstRunRp=0

[GuiUnattended]
EncryptedAdminPassword="No"
AutoLogon="Yes"
AutoLogonCount=1
AdminPassword="XXXXXXXXX"
TimeZone=110
OEMSkipRegional=1
OemSkipWelcome=1

[Shell]
DefaultThemesOff="Yes"

[Components]

[UserData]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
ComputerName=XXXXXX
FullName="XXXXXX"
OrgName="XXXXXX"

[RegionalSettings]
SystemLocale="0409"
UserLocale="0409"
UserLocale_DefaultUser="0409"
InputLocale="0409:00000409"
InputLocale_DefaultUser="0409:00000409"

[Networking]
InstallDefaultComponents="Yes"

[Identification]
JoinWorkgroup="XXXXXX"

So basically it's just a simple Unattended Answer file.

I've done simulated installations with this build, and installations on actual machines, and all were good.




BTW, what does the following line mean?

Signature = "$Chicago$"

The old driverpack has this signature, whereas the new driverpack has a different one

Signature="$Windows NT$"

I'm not sure if this signifies something. It probably has something to do with the dropped Windows 98/ME and NT4 support, but it's the only real difference I can see.

Go to forum: DriverPack Mass Storage

17 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

jtdoom wrote:

What brand and model (plus revision) motherboard do you have this problem on?

I've got an Asus A7N8X-X mobo and a SiI3112A PCI addin card for SATA disks. I also updated the bios of the Silicon Image card, to no avail.

I also checked your advice regarding the WINNT.SIF file. Driverpacks only adds "MsDosInitiated=No" to the WINNT.SIF file, and that line is also present in the nLite version. nLite only makes it "MsDosInitiated=0" which also works, since this value only tells setup to expect only a cd instead of floppydisks.

I've done installations with this disk, both on virtual machines as on real hardware, and none had problems. Only my own friggin' computer tongue

Anyway, I see that there is another update for the Mass Storage pack and I'm already building an image with it, so we'll see how it all works out. I'll ofcourse let you know how things worked out.

Go to forum: DriverPack Mass Storage

18 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

jtdoom wrote:

hi Stiertje,
you got on the NEWS page.  smile

This post was instrumental in finding the cause.
The new release should work for you.
It worked for other machines that would fail before this last update.

I saw I was on the front-page. What an honor tongue

Anyway, I've only had little time to try out a test cd, but that one still recognises my sata card as SATARaid instea of SATALink. I have only tested textmode though, so it might even be possible that the installation will continue without problems. Regretfully I haven't had time to test that.

It is also possible that nLite messes things up. At the moment I use the following sequence for my cd's

1st pass - nLite - Removing components and old drivers
2nd pass - RyanVM - Slipstream RyanVM Updates and Addons
3rd pass - nLite - Removing additional components (all regional settings and keyboards)
4th pass - nLite - Options and Tweaks (I like to keep them seperate)
5th pass - Driverpacks - Slipstream driverpacks (all packs + some 3rd party)
6th pass - nLite - Unattended settings + ISO

I hope it isn't nLite, but I'm going to try the driverpacks only and see what happens.




Anyway, many thanks for the effort.

[EDIT]
Typo
[/EDIT]

Go to forum: DriverPack Mass Storage

19 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

Tried again, and I see what the problem is. During textmode it selects the SATARaid version instead of the SATALink one

Darn, stupid Silicon Image, and I just have to have it tongue



Anyway, this is just the first time I've ever had major problems (apart from the JMicron problems) and I've installed many computers with these packs. Keep up the good work, and if you ever find a solution you want tested, I'm willing to try it out for ya.



BTW, download link for the HWID tool works again. Here's my HWID listing

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1002&DEV_5159&SUBSYS_7C02174B&REV_00\4&3B1D9AB8&0&4840: RADEON 7000 SERIES          
PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040: Silicon Image SiI 3112 SATALink Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EA&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: NVIDIA nForce2 400 Memory Controller
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: NVIDIA nForce2 Memory Controller
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&102AC5BC&0&00F0: NVIDIA GeForce 6200 
19 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&36CE346&0                                    : USB Root Hub
USB\ROOT_HUB\4&37090E00&0                                   : USB Root Hub
USB\ROOT_HUB20\4&B74B78&0                                   : USB Root Hub
USB\VID_046D&PID_0920\5&13E31E82&0&1                        : Logitech QuickCam Express
4 matching device(s) found.

Go to forum: DriverPack Mass Storage

20 Reply by Stiertje

(23 replies, posted in DriverPack Mass Storage)

Hmn, can't seem to find that file. I only find "DevCon.exe" which I already used. DevCon does the job, but is a little overabundant in its information.

Go to forum: DriverPack Mass Storage

21 Topic by Stiertje

(23 replies, posted in DriverPack Mass Storage)

Yay, I've got the good ol' SiI 3112 SATAlink controler which seems to be causing a lot of problems for a lot of people.

However, I've only experienced problems just last week, when I tried to make a nice new WinXP cd. I am now presented with a nice BSOD after textmode install, with a nice 0x0000007B stop error. This happens with the last 2 MassStorage packages. I have now installed an older version again, with MS_DP version 7.01.1, which installs just fine. On a sidenote, both images with the latest DP_MS packs work fine on a Virtual Machine and on an actual PC.

BTW, I tried to download the "save_hwids.exe" in Bashrat's sig, but that link is broken. I used DevCon instead, and that generated the following HWID for my Silicon Image controler.

PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02\4&3B1D9AB8&0&4040
    Name: Silicon Image SiI 3112 SATALink Controller
    Hardware ID's:
        PCI\VEN_1095&DEV_3112&SUBSYS_31121095&REV_02
        PCI\VEN_1095&DEV_3112&SUBSYS_31121095
        PCI\VEN_1095&DEV_3112&CC_018000
        PCI\VEN_1095&DEV_3112&CC_0180
    Compatible ID's:
        PCI\VEN_1095&DEV_3112&REV_02
        PCI\VEN_1095&DEV_3112
        PCI\VEN_1095&CC_018000
        PCI\VEN_1095&CC_0180
        PCI\VEN_1095
        PCI\CC_018000
        PCI\CC_0180

I checked both the MassStorage ini-files in my old and my new image, and the only difference in the Silicon Image 3112 SATAlink section is the addition of this puppy in the newest DP_MS driverpack ini-file. The rest is the same.

PCI\VEN_1095&DEV_3512&SUBSYS_000E182D

Also, in the DP_MS Storage pack, at location "\D\M\S\4", there is an extra file in the older file.
DPM7011.7z has a file "SiiSup.vxd" whereas DPM706.7z does not, but since Windows XP doesn't use .vxd's it can hardly be the problem.




I'm not sure if you need any more information, but if you'd like me to try certain things out I'm willing to spend some time into it.

Go to forum: DriverPack Mass Storage

22 Reply by Stiertje

(9 replies, posted in Feedback and Support - DriverPacks Base)

Hey guys.

I get the exact same error while using DBase 7.01.6 (newest)

I tried several things:
- Method 2, KTD for all, no QSC, RunOnceEx (default), 6 correct 3rdparty driverpacks: No problems, I used this all the time
- Method 1, no KTD, no QSC, RunOnceEx (default), 6 correct 3rdparty driverpacks: Error
- Method 1, no KTD, no QSC, RunOnceEx (###), 6 correct 3rdparty driverpacks: Error
- Method 1, no KTD, no QSC, GUIRunOnce, 6 correct 3rdparty driverpacks: Error
- Method 1, no KTD, QSC, RunOnceEx (default), 6 correct 3rdparty driverpacks: Is now CAB compressing the driverpacks so I guess it's alright.

Method 2 hasn't given me any problems ever, but now is the first time I used Method 1 (in the hope that I can use it as a driverdisc for new hardware when the drivers are CAB compressed). It seems it is indeed a combination of the 3rd-party driverpacks and the QSC, since the procedure throws the error when it begins to extract the 3rd-party driverpacks.

I have checked the MD5 hashes and found no corrupt files. The 3rd-party driverpacks I used were all downloaded from the sticky in the 3rd-party driverpacks forum.



I hope you can do something with this info. It's not a big thing since it works with QSC enabled.

Go to forum: Feedback and Support - DriverPacks Base