Jump to content

SATA/RAID driver integration testers ?


nuhi

Recommended Posts


just tried it out with my si3112r controller and it works fine

but when i integrate the other files 4 txtsetup but used 4 windows like the .CPL File does winxp install them? or do i need to copy the files to $OEM$ and edit winnt.sif file?

Link to comment
Share on other sites

hi,

where autor of Complete Beginners Guide to nLite Unattended CD's find this:

"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_82141033 = "Si3112"

PCI\VEN_1095&DEV_3512&SUBSYS_35121095 = "Si3112"

PCI\VEN_1095&DEV_3512&SUBSYS_01661028 = "Si3112""

???

i have VIA SATA and in Viasraid.inf is only this:

...

[strings]

VIA="VIA Technologies, Inc."

PCI\VEN_1106&DEV_3149.DeviceDesc="VIA Serial ATA RAID Controller"

REG_EXPAND_SZ=0x00020000

REG_DWORD=0x00010001

IOLOGMSGDLL="\IoLogMsg.dll"

DISKNAME1="VIA IDE RAID Driver Diskette"

DISKNAME2="Windows system"

Link to comment
Share on other sites

Don't look in the inf file, look in the txtsetup.oem file. You can set them equal to whatever you want as long as you use the same reference everywhere else.

# 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 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \winxp

d2 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \win2000

d3 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \winnt40

d4 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \2003ia32

# 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 = VIARAID_VT3149_XP

# 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]

VIARAID_VT3149_2003IA32 = "VIA Serial ATA RAID Controller(Windows 2003 IA32)",VT8237

VIARAID_VT3149_XP = "VIA Serial ATA RAID Controller(Windows XP)",VT8237

VIARAID_VT3149_2K = "VIA Serial ATA RAID Controller(Windows 2000)",VT8237

VIARAID_VT3149_NT = "VIA Serial ATA RAID Controller(Windows NT4)",VT8237

# 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.VIARAID_VT3149_2003IA32]

driver = d4, viasraid.sys, viasraid

inf = d4, viasraid.inf

## Cat file directive. It should be marked with non-digital signed driver

#catalog = d4, viasraid.cat

[Files.scsi.VIARAID_VT3149_XP]

driver = d1, viasraid.sys, viasraid

#dll = d1, setupvia.dll

inf = d1, viasraid.inf

## Cat file directive. It should be marked with non-digital signed driver

#catalog = d1, viasraid.cat

[Files.scsi.VIARAID_VT3149_2K]

driver = d2, viasraid.sys, viasraid

#dll = d2, setupvia.dll

inf = d2, viasraid.inf

## Cat file directive. It should be marked with non-digital signed driver

#catalog = d2, viasraid.cat

[Files.scsi.VIARAID_VT3149_NT]

driver = d3, viasraid.sys, viasraid

inf = d3, viasraid.inf

[HardwareIds.scsi.VIARAID_VT3149_2003IA32]

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

[HardwareIds.scsi.VIARAID_VT3149_XP]

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

[HardwareIds.scsi.VIARAID_VT3149_2K]

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

# 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.VT6420]

value = "", Tag, REG_DWORD, 1

#HP-Delete following line

#value = "Parameters\PnpInterface", 5, REG_DWORD, 1

Link to comment
Share on other sites

PC CONFIGURATION:

A7N8X-E DELUXE

MAXTOR 160GB SATA (Si3112r)

EXPERIENCE:

I used nlite-0.99a for SATA integration, then nlite-0.98.8bi for components removal. Windows detected my SATA and started copying installation files. After first reboot...BSOD :no:

Link to comment
Share on other sites

I tested this on my 3114 controller last night and it works fine.  I look forward to this being realeased uncrippled so I can make another image.  There was some other goodies I seen while testing that I think everyone will enjoy with the new release...

same result wiht silicon 3114 sucess :w00t:

Link to comment
Share on other sites

I would be willing to test this out also, I manually changed everything to try and get it to work. But none the less I am still getting the BSOD. I am using the VIA chipset and this is what was added manually. Though I did use an earlier version of nLite to slipstream SP2. System board is Soyo KT600 dragon ultra, with the WD740GD Raptor, no OS installed on drive, so I can test away. :-)

[sourceDisksFiles]

viamraid.sys = 1,,,,,,_x,4,1

viapdsk.sys = 1,,,,,,_x,4,1

[HardwareIdsDatabase]

PCI\VEN_1106&DEV_3249 = "viamraid.sys"

PCI\VEN_1106&DEV_3149 = "viamraid.sys"

PCI\VEN_1106&DEV_3164 = "viamraid.sys"

PCI\VEN_1106&DEV_4149 = "viapdsk.sys"

[sCSI.Load]

viamraid = viamraid.sys,4

viapdsk = viapdsk.sys,4

[sCSI]

viamraid = "VIA RAID Controller(Windows XP)"

viapdsk = "VIA ATA/ATAPI Host Controller(Windows XP)"

Link to comment
Share on other sites

I would be willing to test this out also, I manually changed everything to try and get it to work.  But none the less I am still getting the BSOD.  I am using the VIA chipset and this is what was added manually.  Though I did use an earlier version of nLite to slipstream SP2. System board is Soyo KT600 dragon ultra, with the WD740GD Raptor, no OS installed on drive, so I can test away.  :-)

[sourceDisksFiles]

viamraid.sys = 1,,,,,,_x,4,1

viapdsk.sys = 1,,,,,,_x,4,1

[HardwareIdsDatabase]

PCI\VEN_1106&DEV_3249 = "viamraid.sys"

PCI\VEN_1106&DEV_3149 = "viamraid.sys"

PCI\VEN_1106&DEV_3164 = "viamraid.sys"

PCI\VEN_1106&DEV_4149 = "viapdsk.sys"

[sCSI.Load]

viamraid = viamraid.sys,4

viapdsk = viapdsk.sys,4

[sCSI]

viamraid = "VIA RAID Controller(Windows XP)"

viapdsk = "VIA ATA/ATAPI Host Controller(Windows XP)"

Where find this ? 1,,,,,,_x,4,1

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...