Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
Angel Blue01

should I integrate my SATA drivers?

Recommended Posts

I'm thinking of buying an Abit AX8 based on the VIA K8T890 + 8237 chipset for my new system.

I'm preparing my unattended Windows install.

Should I integrate my SATA drivers? How?

I don't want to lose the ability to push files to the install with a $OEM$ folder. But if I don't load the drivers correctly Windows won't install.

Share this post


Link to post
Share on other sites

First read the guide. The part your looking for is under intermediate/device drivers/sata/raid. Then search the forum, you'll find lots of posts on the subject. Have you done any searching at all?

Share this post


Link to post
Share on other sites

This is the method I use http://greenmachine.msfnhosting.com/READING/addraid.htm

To figure out whats needed for your own drivers look in

it's txtsetup.oem file. Here's an example

[SCSI] 
Si3114r_AMD64 = "Silicon Image SiI3114R Controller (AMD64 or EM64T)"
;The above line goes under the [SCSI] section of txtsetup.sif            

[HardwareIds.SCSI.Si3114r_AMD64]
id = "PCI\VEN_1095&DEV_3114&SUBSYS_61141095", "si3114r"
id = "PCI\VEN_1095&DEV_3114&SUBSYS_288510F1", "si3114r"
id = "PCI\VEN_1095&DEV_3114&SUBSYS_81361043", "si3114r"

;The lines above would go under [HardwareIdsDatabase]. But you need
to change them to the form.
PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "si3114r"

I'm not familiar with the use of the driverpack so I can't help you

there. But I think you would get a better response if you asked a

more specific question. Like I've done such and such but it didn't

work as it said it would. Or I don't under stand this step.

Share this post


Link to post
Share on other sites

Well I've tried nlite, and it tells me there are 3 drivers (3 parts?) on the disk. I don't know how you'd even install 3 drivers...

I certainly don't know how to integrate 3 of them in nlite.

The instructions in the guide say they should be similiar to the example given there, but I don't know what to do. So I can't do it by hand.

I'm only installign 1 drive. No RAID needed.

My motherboard manual doesn't help.

Share this post


Link to post
Share on other sites

what SATA controller do you have?

Share this post


Link to post
Share on other sites

Its integrated into the motherboard.

As I said its an Abit AX8 motherboard with the VIA K8T890 + 8237 chipset. Doing some research reveals its a 3-part driver.

Share this post


Link to post
Share on other sites
#

# format for txtsetup.oem.

#

# General format:

#

# [section]# key = value1,value2,...

#

#

# The hash ('#') introduces a comment.

# Strings with embedded spaces, commas, or hashes should be double-quoted

#

# This section lists all disks in the disk set.

#

# <description> is a descriptive name for a disk, used when

#  prompting for the disk

# <tagfile> is a file whose presence allows setup to recognize

#  that the disk is inserted.

# <directory> is where the files are located on the disk.

#

[Disks]

d1 = "SMARTX",\Driver,\Driver

# This section lists the default selection for each 'required'

# hardware component.  If a line is not present for a component,

# the default defaults to the first item in the [<component_name>]

# section (see below).

#

# <component_name> is one of computer, display, keyboard, mouse, scsi

# <id> is a unique <within the component> string to be associated

#  with an option.

[Defaults]

scsi = VIA_SMARTX_BUS

# This section lists the options available for a particular component.

#

# <id> is the unique string for the option

# <description> is a text string, presented to the user in a menu

# <key_name> gives the name of the key to be created for the component in

#  HKEY_LOCAL_MACHINE\ControlSet001\Services

[scsi]

VIA_SMARTX_BUS = "STEP 1: Install VIA SMARTX Bus driver"

VIA_SMARTX_PORT = "STEP 2: Install VIA SMARTX Port driver"

VIA_SMARTX_RAID = "STEP 3: Install VIA SMARTX RAID driver"

# This section lists the files that should be copied if the user

# selects a particular component option.

#

# <file_type> is one of driver, port, class, dll, hal, inf, or detect.

#  See below.

# <source_disk> identifies where the file is to be copied from, and must

#  match en entry in the [Disks] section.

# <filename> is the name of the file. This will be appended to the

#  directory specified for the disk in the [Disks] section to form the

#  full path of the file on the disk.

#=======================================#

[Files.scsi.VIA_SMARTX_BUS]

driver = d1, viaxbus.sys, viaxbus

inf = d1, VIASRX.inf

dll = d1, viaxinst.dll

[Files.scsi.VIA_SMARTX_PORT]

driver = d1, viaxport.sys,viaxraid

[Files.scsi.VIA_SMARTX_RAID]

driver = d1, viaxraid.sys,viaxraid

[HardwareIds.scsi.VIA_SMARTX_BUS]

id = "PCI\VEN_1106&DEV_3149","viaxbus"

[HardwareIds.scsi.VIA_SMARTX_PORT]

id = "PCI\VEN_1106&DEV_3249","viaxbus"

[HardwareIds.scsi.VIA_SMARTX_RAID]

id = "RAID_Virtual_Channel","viaxraid"

#===============================================================================

# This section specifies values to be set in the registry for

# particular component options.  Required values in the services\xxx

# key are created automatically -- use this section to specify additional

# keys to be created in services\xxx and values in services\xxx and

# services\xxx\yyy.

#

# <key_name> is relative to the services node for this device.

#  If it is empty, then it refers to the services node.

#  If specified, the key is created first.

# <value_name> specifies the value to be set within the key

# <value_type> is a string like REG_DWORD.  See below.

# <value> specifies the actual value; its format depends on <value_type>

[Config.viaxbus]

[Config.viaxraid]

This is the contents of my txtsetup.oem

Share this post


Link to post
Share on other sites

Moved to Device Drivers.

You shouldn't post this in the DriverPack MassStorage forum! It's meant for the DriverPack MassStorage only! (That's a project...)

Share this post


Link to post
Share on other sites
Well, according to the guide here http://www.collosumus.net/amd64/addhw_1.html I should add a line like

fasttx2k.sys = 1,,,,,,3_,4,1,,,1,4

  fasttx2k.inf = 1,,,,,,,20,0,0

to my txtsetup.sif but i don't see anything in my txtsetup.oem that coorisponds to that code.

You won't see anything like that in your txtsetup.oem.

Just take the name of your driver and replace the fasttx2k with

the name of your driver so it becomes

mydriver.sys = 1,,,,,,3_,4,1,,,1,4

mydriver.inf = 1,,,,,,,20,0,0

Where mydriver is the actual name.

You should end up with something like this

I just realised your tr

[SourceDisksFiles]
viaxbus.sys = 1,,,,,,3_,4,1,,,1,4
viaxport.sys = 1,,,,,,3_,4,1,,,1,4
viaxraid.sys = 1,,,,,,3_,4,1,,,1,4


[HardwareIdsDatabase]
PCI\VEN_1106&DEV_3149 = "viaxbus"
PCI\VEN_1106&DEV_3249 = "viaxbus"
RAID_Virtual_Channel = "viaxraid"

[SCSI.load]
viaxbus = viaxbus.sys,4
viaxport = viaxport.sys,4
viaxraid = viaxraid.sys,4

[SCSI]
viaxbus = Via smartx Bus driver"
viaxport = "Via Smartx Port driver"
viaxraid = "VIA Smartx Raid driver"

Don't forget to edit your winnt.sif and add the oempnpdriverpath

and to copy the files to that directory and to your i386 directory.

I just realised your tying to integrate your driver into XP64, right?

If you are its more complicated than for 32bit XP. The only way I've been

able to get it to work is to follow the steps in these posts.

http://www.msfn.org/board/index.php?showtopic=47053

but there's no guarantee it will work. It didn't work on

my nforce3 raid drivers, but did on my promise and silicon image.

Share this post


Link to post
Share on other sites
No, its 32-bit Windows.

So copying your txtsetup code will put work?  :w00t:

I believe so. but don't shoot me if it doesn't.

Share this post


Link to post
Share on other sites
There are several [sourceDisksFiles]s. Does it matter which one?

You canjust paste it all on the end of the txtsetup.sif

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...