[Bouchehog]

**Solved - extra crap in the winnt.sif from a previous attempt**

I'm trying to slipstream my SATA drivers into my XP SP2 unattended installation. I'm following GreenMachine's Guide. It's very similar to Rasken's version.

My machine is based on a ASUS K8V Mobo (a VIA VT8237 and VT6420 Southbridge) with a new 120Gb SATA Seagate Barracuda (7200rpm,8M cache) . I'll split the method I used into sections to make it easier for someone in the know to check what I'm doing!



Obtaining the driver files
I downloaded the lastest version listed on the ASUS site. They were listed as "VIA VT6420 (VT8237) SATA RAID Driver Package Version 2.20D WHQL." and dated 2004/03/08.

In the file at this path are the following drivers:
VIARAID220d\VIARAID\DriverDisk\SATA\Winxp\
VIASRAID.INF
viasraid.sys
viasraid.cat

It should be noted that the only TXTSETUP.OEM file is at "VIARAID220d\VIARAID\DriverDisk\SATA\". It also contains the file "VT8237" and at that level there are several folders, one of which is the Winxp folder where I got these drivers. There is also a later version (310E) at the VIA site, but I stuck with the one from the ASUS site because I know it works using the F6 method in an attended installation.



Copying the driver files
I made a compressed version of viasraid.sys by using the following RUN command:
MAKECAB E:\VIARAID220d\VIARAID\DriverDisk\SATA\Winxp\viasraid.sys E:\VIARAID220d\VIARAID\DriverDisk\SATA\Winxp\viasraid.sy_

I then copied these files into E:\XPCD\$OEM$\$1\drivers\01_SATA:
VIASRAID.INF
viasraid.sys
viasraid.sy_
viasraid.cat

I copied viasraid.sy_ into E:\XPCD\I386 as well.



Modifying the WINNT.SIF file
The [Unattend] section of my WINNT.SIF in the I386 folder file already said this:

Quote

[Unattended]    UnattendMode=FullUnattended
    OemSkipEula=Yes
    UnattendSwitch="yes"
    TargetPath=\WINDOWS
    FileSystem=*
    WaitForReboot="No"
    KeyboardLayout="United Kingdom"
    OemPreinstall=Yes   
    DriverSigningPolicy=Ignore
    OemPnPDriversPath="drivers\01_SATA\;drivers\02_Chipset...and so on"

Modifying the TXTSETUP.SIF
The VIASRAID.OEM file from GreenMachine's list tells me to add this to the TXTSETUP.SIF file in the I386 folder, at the end and just before the :

Quote

[SourceDisksFiles]viasraid.sys = 1,,,,,,4_,4,1,,,1,4

[HardwareIdsDatabase]
PCI\VEN_1106&DEV_3149 = "viasraid"

[SCSI.load]
viasraid = viasraid.sys,4

[SCSI]
viasraid = "VIA Serial ATA RAID Controller"

So, according to his guide that should now be it. I burn the CD in the usual way but...

[Bouchehog]

On booting from the CD, I get the following message:

Quote

File txtsetup.oem caused an unexpected error (18) at line 1747 in D:\xpsprtm\base\setup\oemdisk.c

Press any key to continue.

That message comes up again immediately after pressing a key. It then copies some files, states "Setup is starting windows", "Searching for previous versions of Windows" and then come up with this message:

Quote

The manufacturer provided file that setup is trying to use is corrupted or invalid:

Line 1 contains a syntax error

Setup cannot continue. To quit setup press F3.

[Bouchehog]

I should add that the TXTSETUP.OEM for these drivers, in the folder below (E:\VIARAID220d\VIARAID\DriverDisk\SATA) contains this (to save anyone having to look it up by downloading the drivers):

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

[trainee]

I have no experience with these drivers *but* the following quote is from GreenMachines Method (link).

Quote

The use of the TXTSETUP.OEM file is not needed, nor are the MassStorageDevices entries int WINNT.SIF. I have removed the TXTSETUP.OEM file from my installations. The use of the TEXTMODE directory is not needed either.

My belief is that you should not be including the TXTSETUP.OEM file on your CD with these methods.

Have you tried the DriverPack MassStorage - updated 31st August-BETA provided by Bâshrat? I *think* it includes your drivers. Hope this helps.

[Bouchehog]

I'm not including a TXTSETUP.OEM.

I wansn't using a TEXTMODE folder with the drivers in it, but I've just made one as it's included in Rasken's method. I'll try that and then try the drivers you link.

[Bouchehog]

I get the same error both using the method outlined above (plus a TEXTSETUP folder) and using the Mass drivers file. This is crazy! It works with F6, but that means that I can't do an unattended installation!

Can anyone at least shed some light on what the errors mean?

[trainee]

Okay I have a number of suggestions:

Test Virtually
First, if you aren't already you may want to do your testing in virtualpc until you get passed this problem. You can get a free 45-day trial here. Virtualpc won't be able to actually test the drivers but it should still present you with textmode/winnt/txtsetup type errors (like your invalid line error). This should be a whole lot easier than burning new CD's and should save you some time as well.

Start from Scratch
Next, you should try and make the rest of your installation as basic as possible until you get the sata drivers to work. This will help to reduce the complexity and amount of detail you have to juggle. So don't worry about registry tweaks, hotfixes, etc until you get this working. Your error seems very odd to me since you aren't even including a textsetup.oem. I recommend starting over from scratch.

Latest Drivers
Now, the drivers integrated in Bâshrat's MassStorageDrivers Pack (here) appear to be of a later version than the ones provided by Asus:

Quote

VIA VT6420 (VT8237) SATA RAID Driver Package Version 2.20D WHQL." and dated 2004/03/08.

The MassStorageDriver Pack on the other hand appears to have the latest drivers from VIA dated from 2004/07/30. (off-topic: is this how things are dated in the UK?...wierd). The via site is acting a little wierd right now but you can get the driver zip here. Inside there is a subfolder called DriverDisk which contains the files you would put on the floppy drive. I am not an expert on the MassStorage pack so you may want to add a post to that thread with your problems if you are trying to use that method. I am pretty sure that a number of people have the VIA drivers slipstreamed correctly with the DriverPack so that may be your best bet.

Method 2
Finally there is another driver integration method you can try known as Method 2 (M2). It is as of yet untested with your drivers but has the possibility of working. I wrote a psuedo-guide here. I would concentrate on the MassStorageDriver Pack, but if you are still having problems (or are just adventurous) you can try it.

[Bouchehog]

Yes - I thought it was strange, but put it down to the fact that I only partially understand how windows installs things anyway. Then I read your post and realised that it must be something to do with the textsetup.oem.

I quick search from scratch later and I found a couple of entries from a previous attempt hidden at the bottom of my winnt.sif.

Many thanks for the help - virtual PC was a great idea btw and I'll try it now as there are still a few issues I need to teeth out.

Also, the mass driver pack was very useful and I'll keep it in even though I've worked out what was wrong with my lite version.

In short - thanks guys!