Official BTS Driverpack Support, ONE Year later... Options

[hilander999]

UBCD4WIN.COM PROUDLY PRESENTS....
OFFICIAL SUPPORT FOR BTS DRIVERPACKS.

The UBCD4WIN Development team has been working directly with the BTS team to make this possible.
In November of 2005 first contact was made about this and have been working in the background for more
then a year now doing all the background work on what the true requirements for supporting all drivers
in a bartpe environment, which supports all varieties of bartpe including UBCD4WIN & others.

The initial release of the new driverpacks base only supports mass storage drivers.
There was no doubt that the mass storage drivers were more important and needed to be first.
LAN & WLAN will be next on the list, please remember that this is a freeware project and anything
worth having will take time to create, test & debug.

We have tested this method on a few dozen systems of different hardware configurations, but our resources
in this area are limited. As always... USE AT YOUR OWN RISK. Great care has been taken to make sure this
package is safe to use, but there is always a chance of bugs that were not found during development.

The benefit of this setup is that the pebuilder plugin is created dynamically with the current driverpack release.
The mass storage driverpack included in this plugin is up to date as of now.
When new versions are updated, simply replace the driverpack.7z file in the \base\driverpacks folder and rebuild the plugin.

Overflow (Jeff Herre) & I have been working together on this for the past couple of months.
Jeff has done an outstanding job and deservers a big THUMBS UPS for his work with the driverpacks base support.

Please direct any request for additional drivers to driverpacks.net as they are the maintainter of the driverpacks because we cannot add the drivers for you. They are doing a great job and normally get any requests uploaded in a short time, but please have patience.

When testing this package myself I did notice a few drivers that were not included, so yes your driver may not be supported at this point but this whole package is dynamic and adding drivers should be as simple as your posting a link to the driver you need at driverpacks.net and using the word PLEASE might not hurt either.

THANX to Bashrat the Sneaky, Overflow and everyone else who has contributed their time to the community.
None of this would have been possible if it were not for the work done by Bashrat the Sneaky on the original driverpacks.

Please concider donating to driverpacks.net & ubcd4win.com if you use this software in your workplace.
Nothing is ever required, but any donation is always welcomed and used to cover the costs of maintaining these projects.

-------------------------------------------------------------------------------------

Installation Instructions

Disable or remove any existing Mass Storage Drivers.
UBCD4Win currently comes with many drivers and to avoid conflicts these need to be disabled.

To disable the included MS drivers...
create a new folder in the UBCD4Win folder called DISABLED then cut and paste
the <UBCD4Win>\drivers\SCSIAdapter folder to the <UBCD4Win>\DISABLED folder.

You can also simply delete this folder if you wish but this would not allow you to use them later if needed.

Extract the plugin to the following location on your hard drive depending on your version of pebuilder.
<Pebuilder>\plugin
<UBCD4WIN>\plugin

After running the self-extracting executable, you will have the following new folder under \plugins...
<Pebuilder>\plugin\DriverPacks_BartPE_Plugin
<UBCD4WIN>\plugin\DriverPacks_BartPE_Plugin

DO NOT CHANGE THE NAME OF THIS FOLDER!!!
"DriverPacks_BartPE_Plugin" is hard-coded into the executable and must not be altered in any way.

After you extract the plugin to the proper folder....
Run UBCD4WINBUILDER.EXE (or pebuilder.exe) and open the plugins page.
select "# DriverPack - Press <CONFIG> to enable drivers" & press the CONFIG button.
This will setup the base.ini file to your local directory and run the driverpacks base which will generate the mass storage drivers plugin.

You MUST press REFRESH before you will see the new plugin listed in pebuilder.
-------------------------------------------------------------------------------------

Link for BTS MassStorage DriverPack for BartPE

This post has been edited by hilander999: Jul 7 2007, 08:05 PM

[TheHive]

Congrats! and Thanks for the Drivers.

[Former_frodo_post]

Good work to everyone involved!

I guess this means i can (almost) get rid of the hacky autobuild version ive been using for eons now.

I know it cant be an easy thing to get all the drivers working, so hats off to you guys.

[oscar]

After you extract the plugin to the proper folder....
Run UBCD4WINBUILDER.EXE and open the plugins page.
select "# DriverPack - Press <CONFIG> to enable drivers" & press the CONFIG button.
This will setup the base.ini file to your local directory and run the driverpacks base which will generate the mass storage drivers plugin.

A question about instructions:
For whom do not know what UBCD4WINBUILDER.EXE is the solution is to manually run CONFIG.cmd, am I correct ?

[hilander999]

A question about instructions:
For whom do not know what UBCD4WINBUILDER.EXE is the solution is to manually run CONFIG.cmd, am I correct ?

Yes, you can run config.cmd manually if you like.
I'll change that part now for people that do not know about different oem versions of pebuilder.

@Frodo
Hopefully all drivers will work, but this needs much testing which is why we went public.
The dynamically generated plugin has worked on some configurations that are know to be difficult to get working, even in a normal windows instalation. This allows us to believe that the package is ready for testing on a wider scale and should should support all hardware for which there is a driver included in the matching driverpack.7z file.

Many drivers are not there already, so I leave requesting them to anyone who finds there hardware is not included inthe driverpacks. The bts team is expecting a small flood of requests for additional drivers and the transittion should not take long to complete.

@ALL
Anyone who has hardware they can test the new driver setup on, can you please post what hardware has been confirmed to work/not work so we can debug this as quickly as possable.

This post has been edited by hilander999: Apr 6 2007, 11:29 AM

[bionic]

Nice work

Id like to point something out though.
The siI 3114r driver is misssing the SATALink driver accelerator part leaving the controller in a speed reduced mode.
Might be an issue with the 3112r part too, havent tested.

I have made a txtsetup+reg entries plugin that afaik is working proper.
Its made up of some of my own work and some from others, cudos to whomever may recognize their work
Im just posting this as a possible guide not as a guaranteed working addon/edit.
Hope its usefull, if not id like a mod to delete this post to avoid cluttering of the original thread.

siI3114r.inf:

CODE

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Mass Storage Drivers: SiI3114r"
Enable=1

[SourceDisksFiles]
; Silicon Image SiI 3114 SATARaid Controller
si\si3114r\si3114r.sys=4,,1
si\si3114r\SiWinAcc.sys=4,,1
si\si3114r\si3114r.inf=20,,1
si\si3114r\SilSupp.cpl=2,,1

[SetupReg.AddReg]
0x1, "ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_3114&subsys_90181695","ClassGUID","{4D36E97B-E325-11CE-BFC1-08002BE10318}"
0x1, "ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_3114&subsys_90181695","Service","si3114r"
0x4, "ControlSet001\Services\SiFilter","Type", 0x00000001
0x4, "ControlSet001\Services\SiFilter","Start", 0x00000000
0x4, "ControlSet001\Services\SiFilter","ErrorControl", 0x00000000
0x4, "ControlSet001\Services\SiFilter","Tag", 0x00000007
0x2, "ControlSet001\Services\SiFilter","ImagePath","System32\DRIVERS\SiWinAcc.sys"
0x1, "ControlSet001\Services\SiFilter","DisplayName","SATALink driver accelerator"
0x1, "ControlSet001\Services\SiFilter","Group","Filter"
0x3, "ControlSet001\Services\SiFilter\Security","Security",\
   01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
   00,1C,00,01,00,00,00,02,80,14,00,FF,01,0F,00,01,01,00,00,00,00,00,01,00,00,\
   00,00,02,00,60,00,04,00,00,00,00,00,14,00,FD,01,02,00,01,01,00,00,00,00,00,\
   05,12,00,00,00,00,00,18,00,FF,01,0F,00,01,02,00,00,00,00,00,05,20,00,00,00,\
   20,02,00,00,00,00,14,00,8D,01,02,00,01,01,00,00,00,00,00,05,0B,00,00,00,00,\
   00,18,00,FD,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
   00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00
0x4, "ControlSet001\Services\Si3114r","Type", 0x00000001
0x4, "ControlSet001\Services\Si3114r","Start", 0x00000000
0x1, "ControlSet001\Services\Si3114r","Group","SCSI miniport"
0x4, "ControlSet001\Services\Si3114r","ErrorControl", 0x00000001
0x1, "ControlSet001\Services\Si3114r","DisplayName","SiI-3114 SATARaid Controller"
0x2, "ControlSet001\Services\Si3114r","ImagePath","system32\DRIVERS\SI3114R.sys"
0x4, "ControlSet001\Services\Si3114r","Tag", 0x00000022
0x4, "ControlSet001\Services\Si3114r\Parameters\Device","NumberOfRequests", 0x00000040
0x4, "ControlSet001\Services\Si3114r\Parameters\Device","MaximumSGList", 0x00000021
0x4, "ControlSet001\Services\Si3114r\Parameters\PnPInterface","5", 0x00000001
0x0, "ControlSet001\Services\Si3114r\Parameters\VEN_1095&DEV_3114&SUBSYS_90181695&REV_02\BUS_01&DEV_0c&FUNC_00\Device Parameters"
0x1, "ControlSet001\Services\Si3114r\ProblemDevices","",""
0x1, "ControlSet001\Services\Si3114r\ProblemDevices","Maxtor 4D060H3                          DAK05GK0","MaxMode = UDMA-5"
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller", 0x61141095
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Fujitsu-Siemens 2885)", 0x288510f1
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Aopen 047A)", 0x047aa0a0
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Aopen 0478)", 0x0478a0a0
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Aopen 0479)", 0x0479a0a0
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (EPoX 9018)", 0x90181695
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Chaintech F642)", 0xf642270f
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (DFI 1004)", 0x100415bd
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9125)", 0x12501462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9131)", 0x13101462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9156)", 0x15601462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9161)", 0x16101462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (GIGABYTE)", 0xb0031458
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (ECS)", 0x1b711019
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MITAC)", 0x61141071
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (IWILL)", 0x003515d4
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Abit SC-1P)", 0x1025147b
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Abit WI-2P)", 0x1001147b
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Abit)", 0x1c0a147b
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (ASUS P5GD/P5AD)", 0x81361043
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (HP 2A1E)", 0x2a1e103c

[SetValue]
"txtsetup.sif","SourceDisksFiles","si3114r.sys", "1,,,,,,_3,4,1"
"txtsetup.sif","SCSI.Load","si3114r", "si3114r.sys,4"
"txtsetup.sif","SCSI","si3114r", """Silicon Image SiI 3114 SATARaid Controller"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_61141095", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_288510F1", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_90181695", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_F642270F", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_100415BD", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_12501462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_13101462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_15601462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_16101462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_B0031458", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1B711019", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_61141071", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_003515D4", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1025147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1001147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_130A147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1C0A147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_81361043", """si3114r"""

This post has been edited by bionic: Apr 7 2007, 06:57 AM

[hilander999]

@Bionic
Please direct any driver requests to www.driverpacks.net

They have a team of people working on the driverpacks and can add them easily.

THANX.

[oscar]

To solve this

DO NOT CHANGE THE NAME OF THIS FOLDER!!!
"DriverPacks_BartPE_Plugin" is hard-coded into the executable and must not be altered in any way.

better is to include something like this in the plugin

rem Start_Here.cmd by oscar

@echo off

echo Warning !
echo.
echo If plugin\DriverPacks_BartPE_Plugin folder name
echo.
echo was changed to something else stop here pressing CTRL-C
echo.
echo then rename to plugin\DriverPacks_BartPE_Plugin
echo.
echo and run this Start_Here.cmd again
echo.
echo else
echo.

pause

Config.cmd

[JonF]

Well, it works for me on at least one system that I couldn't see with the old auotrun driver pack; a Gateway MA6 notebook with Intel 82801GBM ICH7-M SATA controller (and SATA disk). Yippeee!

Thanks.

[jeffie]

How can we add additional driver packages like LAN and WIFI?

Thanks
Jeffie

[rdsok]

How can we add additional driver packages like LAN and WIFI?

Thanks
Jeffie

Jeffie

You may want to re-read the original post introducing these drivers because you apparently missed the following...

The initial release of the new driverpacks base only supports mass storage drivers.
There was no doubt that the mass storage drivers were more important and needed to be first.
LAN & WLAN will be next on the list, please remember that this is a freeware project and anything
worth having will take time to create, test & debug.

In more direct words... you can't add them yet.

[hilander999]

To solve this

DO NOT CHANGE THE NAME OF THIS FOLDER!!!
"DriverPacks_BartPE_Plugin" is hard-coded into the executable and must not be altered in any way.

better is to include something like this in the plugin

We are working on a better solution. Driverpacks.net had to release the new base to support changes to the new driverpacks that are now using ini files for more controll over the install process.

You will like what we have done, but it will take some more time before the new version goes public.
We are trying very hard not to hard-code anything, but this is no small task when you concider that it must be able to supprt the full line of driverpacks when finished. Mass Storage is ony the begining, give us some time.

[TheHive]

We are trying very hard not to hard-code anything, but this is no small task when you concider that it must be able to supprt the full line of driverpacks when finished. Mass Storage is ony the begining, give us some time.

Sounds like a good future development coming.

[hilander999]

@boinic
Can you test your plugin with the inf line commented to see it it really needs to be there?
;si\si3114r\si3114r.inf=20,,1

In all testing we found troulble when using inf files for txtmode drivers because if pnp is run, it may detect the already-mounted device and reset it while the data is mounted, thus causing corruption on a lrage scale that in my tests was not recoverable and resulted in total data loss.

IF & ONLY IF the registry settings do help with speed, and the INF file is not needed, I will take another look at the code and see if it is even feasable to do this given the method we choose is working very well and regardless of speed does allow acces to the hard drive for the purpose of saving data which is our mian goal.

THANX for re-posting the data I ask for. I do appreciate it.

Nice work

Id like to point something out though.
The siI 3114r driver is misssing the SATALink driver accelerator part leaving the controller in a speed reduced mode.
Might be an issue with the 3112r part too, havent tested.

I have made a txtsetup+reg entries plugin that afaik is working proper.
Its made up of some of my own work and some from others, cudos to whomever may recognize their work
Im just posting this as a possible guide not as a guaranteed working addon/edit.
Hope its usefull, if not id like a mod to delete this post to avoid cluttering of the original thread.

siI3114r.inf:

CODE

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Mass Storage Drivers: SiI3114r"
Enable=1

[SourceDisksFiles]
; Silicon Image SiI 3114 SATARaid Controller
si\si3114r\si3114r.sys=4,,1
si\si3114r\SiWinAcc.sys=4,,1
si\si3114r\si3114r.inf=20,,1
si\si3114r\SilSupp.cpl=2,,1

[SetupReg.AddReg]
0x1, "ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_3114&subsys_90181695","ClassGUID","{4D36E97B-E325-11CE-BFC1-08002BE10318}"
0x1, "ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_3114&subsys_90181695","Service","si3114r"
0x4, "ControlSet001\Services\SiFilter","Type", 0x00000001
0x4, "ControlSet001\Services\SiFilter","Start", 0x00000000
0x4, "ControlSet001\Services\SiFilter","ErrorControl", 0x00000000
0x4, "ControlSet001\Services\SiFilter","Tag", 0x00000007
0x2, "ControlSet001\Services\SiFilter","ImagePath","System32\DRIVERS\SiWinAcc.sys"
0x1, "ControlSet001\Services\SiFilter","DisplayName","SATALink driver accelerator"
0x1, "ControlSet001\Services\SiFilter","Group","Filter"
0x3, "ControlSet001\Services\SiFilter\Security","Security",\
   01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
   00,1C,00,01,00,00,00,02,80,14,00,FF,01,0F,00,01,01,00,00,00,00,00,01,00,00,\
   00,00,02,00,60,00,04,00,00,00,00,00,14,00,FD,01,02,00,01,01,00,00,00,00,00,\
   05,12,00,00,00,00,00,18,00,FF,01,0F,00,01,02,00,00,00,00,00,05,20,00,00,00,\
   20,02,00,00,00,00,14,00,8D,01,02,00,01,01,00,00,00,00,00,05,0B,00,00,00,00,\
   00,18,00,FD,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
   00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00
0x4, "ControlSet001\Services\Si3114r","Type", 0x00000001
0x4, "ControlSet001\Services\Si3114r","Start", 0x00000000
0x1, "ControlSet001\Services\Si3114r","Group","SCSI miniport"
0x4, "ControlSet001\Services\Si3114r","ErrorControl", 0x00000001
0x1, "ControlSet001\Services\Si3114r","DisplayName","SiI-3114 SATARaid Controller"
0x2, "ControlSet001\Services\Si3114r","ImagePath","system32\DRIVERS\SI3114R.sys"
0x4, "ControlSet001\Services\Si3114r","Tag", 0x00000022
0x4, "ControlSet001\Services\Si3114r\Parameters\Device","NumberOfRequests", 0x00000040
0x4, "ControlSet001\Services\Si3114r\Parameters\Device","MaximumSGList", 0x00000021
0x4, "ControlSet001\Services\Si3114r\Parameters\PnPInterface","5", 0x00000001
0x0, "ControlSet001\Services\Si3114r\Parameters\VEN_1095&DEV_3114&SUBSYS_90181695&REV_02\BUS_01&DEV_0c&FUNC_00\Device Parameters"
0x1, "ControlSet001\Services\Si3114r\ProblemDevices","",""
0x1, "ControlSet001\Services\Si3114r\ProblemDevices","Maxtor 4D060H3                          DAK05GK0","MaxMode = UDMA-5"
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller", 0x61141095
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Fujitsu-Siemens 2885)", 0x288510f1
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Aopen 047A)", 0x047aa0a0
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Aopen 0478)", 0x0478a0a0
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Aopen 0479)", 0x0479a0a0
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (EPoX 9018)", 0x90181695
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Chaintech F642)", 0xf642270f
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (DFI 1004)", 0x100415bd
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9125)", 0x12501462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9131)", 0x13101462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9156)", 0x15601462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MSI MS9161)", 0x16101462
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (GIGABYTE)", 0xb0031458
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (ECS)", 0x1b711019
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (MITAC)", 0x61141071
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (IWILL)", 0x003515d4
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Abit SC-1P)", 0x1025147b
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Abit WI-2P)", 0x1001147b
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (Abit)", 0x1c0a147b
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (ASUS P5GD/P5AD)", 0x81361043
0x4, "ControlSet001\Services\Si3114r\SupportedSubsystemIDs","Silicon Image SiI 3114 SATARaid Controller (HP 2A1E)", 0x2a1e103c

[SetValue]
"txtsetup.sif","SourceDisksFiles","si3114r.sys", "1,,,,,,_3,4,1"
"txtsetup.sif","SCSI.Load","si3114r", "si3114r.sys,4"
"txtsetup.sif","SCSI","si3114r", """Silicon Image SiI 3114 SATARaid Controller"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_61141095", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_288510F1", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_90181695", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_F642270F", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_100415BD", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_12501462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_13101462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_15601462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_16101462", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_B0031458", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1B711019", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_61141071", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_003515D4", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1025147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1001147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_130A147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_1C0A147B", """si3114r"""
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_1095&DEV_3114&SUBSYS_81361043", """si3114r"""

[cdob]

0x1, "ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_3114&subsys_90181695","ClassGUID","{4D36E97B-E325-11CE-BFC1-08002BE10318}"
0x1, "ControlSet001\Control\CriticalDeviceDatabase\pci#ven_1095&dev_3114&subsys_90181695","Service","si3114r"
0x0, "ControlSet001\Services\Si3114r\Parameters\VEN_1095&DEV_3114&SUBSYS_90181695&REV_02\BUS_01&DEV_0c&FUNC_00\Device Parameters"

This HardwareIDs relate to a single machine only. Not all Si3114r use this.

A more general general solution would be nice.
Can't SiWinAcc.sys be loaded as txtsetup.sif filter driver? Compare nvidia nic drivers.

[bionic]

@boinic
Can you test your plugin with the inf line commented to see it it really needs to be there?
;si\si3114r\si3114r.inf=20,,1

In all testing we found troulble when using inf files for txtmode drivers because if pnp is run, it may detect the already-mounted device and reset it while the data is mounted, thus causing corruption on a lrage scale that in my tests was not recoverable and resulted in total data loss.

IF & ONLY IF the registry settings do help with speed, and the INF file is not needed, I will take another look at the code and see if it is even feasable to do this given the method we choose is working very well and regardless of speed does allow acces to the hard drive for the purpose of saving data which is our mian goal.

THANX for re-posting the data I ask for. I do appreciate it.

Sure, thx for looking into it, any improvement is much appreciated
The si\si3114r\si3114r.inf=20,,1 doesnt need to be there, just tested.
Yeah speed is not of the essence i agree, just played around since i had to move huge amounts of data during a restore operation and a speed difference of 30+mbps did make quite a difference.
Its just a dirty hack on my part, im not knowledgeable enough to really get into it.
I do have one for 3112r and nforce2 too though(also snatched partly from others)
Ive uploaded the infs(without the si3114r.inf and 3112r.inf entries) , use or discard

CODE

http://w13.easy-share.com/1008226.html

This post has been edited by bionic: Apr 18 2007, 07:04 AM

[insomniac]

Has there been any new updates, besides controller drivers?

[mike56]

Hi,
I installed the BTS driver pack and it works great on all machines with SATA except one. I have a Silicon Image based card with two external SATA ports (NOT RAID) for my Seagate external hard drive. This setup works great under XP but is very problematic under PE. Every once in a while a boot will work OK. Most of the time the drive is not recognized or occasionally produces a delayed write error. Also after not working under PE XP needs to CHKDSK the drive.

Do I need to deactivate some windows drivers under PE? I see that under UWBD you do.

Thanks for all who help with a great project.

Mike

[hilander999]

Any mass storage drivers should be removed from the <pebuilder>\drivers\SCSIAdapter folder unless you know for sure that they are not included in the driverpack.

Get the latest mass storage driverpack.7z file from www.driverpacks.net and run the configuration again.
I'm not certain about the specific driver you are asking about, but I do know they found a few duplicates and have corrected some bugs that got into the pack somewhere along the line.

[mike56]

Thanks for the instant reply! I don't have any drivers in that location. I will download the latest drivers and give it a shot.
Thanks for the assist.
Mike