Bouchehog

I feared that it might be that. Ah well, never mind. Thanks for the posts!

Hopeful Bump?

I've also just noticed that documents copied to $OEM/$Docs/All Users/Documents don't show up when I'm logged in as Administrator.Computername. Thus my two solutions would be: Put my Documents and Favorites in $OEM/$MoveMe and move them with a bat file command to %userprofile% and the relevant folders Work out why it's creating this second folder, elimate the problem and keep the two in $OEM/$Docs/Administrator/Favorites and /Documents respectively I'd sooner go for the latter as it's a more attractive solution and means I don't have this second ghosted account. The first solution I can do myself. Oh and I should add that I'm not trying to create any new accounts at all, I'm happy just to keep logged in as the Administrator and leave it at that.

My XP CD is perfect, except for one final element. When I install I get two admin accounts set up, so my documents and settings folder has: All Users Administrator Administrator.ComputerName This is irritating because although I can use %userprofile% to make sure that I'm accessing Administrator.ComputerName, it leaves me with a seperate account. Furthermore, my favorites don't seem to want to work when I copy them to /All Users/ and I don't want to have to copy them to "%userprofile%\Favorites" using a batch command - it's just too inelegant. I'd prefer to have them in my $Docs folder and do it that way. Anyone know why it's creating this account? If I delete the [userData] ComputerName=x line in my Winnt.sif will that stop it creating this second Admin account? This thread suggests that it happens when I install over another account. This is after a format, but I do have a $OEM/$Docs/Administrator folder. Could this be it? Why don't favorites work from All Users?

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!

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?

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.

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

On booting from the CD, I get the following message: 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:

**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: 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 : So, according to his guide that should now be it. I burn the CD in the usual way but...

Nevermind - I was being thick.

I've found a copy of one on an old Dell CD It was pre-SP1 and the new install is SP2 - does that matter? Does it need to be as bloated as it is, or is there a whole bunch of stuff from the Dell install? Also, there are headings for [sourceDisksFiles], [HardwareIdsDatabase], [sCSI.load] and [sCSI] already - does it matter if I stick new ones at the end, or should I replace the existing ones? Could I not just use this? [Version] signature="$Windows NT$" ClassGUID={00000000-0000-0000-0000-000000000000} [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"

Double post VVV

I'd love to be able to copy Greenmachine's guide to slipstreaming my VIA SATA drivers into my XP install as it refuses to install any unattended install using F6 (the drivers do however work with F6 and an attended installation). I know that I need to put this in my Unattend.sif, which should be in my XPCD I387 folder: [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" I also have the drivers in my $OEM$\$1\drivers\03_SATA. The three files are from the 310E VIA drivers for the VT8237/6420 and are VIAMRAID.SYS/INF/CAT. There is a corresponding line in my Winnt.sif The problem is that I don't have an Unattend.sif file in my I387 folder. What gives?

Thanks! I was being thick and putting the variables in as switches.

Anyone?

Is it possible to install this using a bat file? Using something like: I've not got around to running any runonceex things yet and I don't understand them as well as I understand bat files.

My apologes if this has already be covered, I did do a search. Question 1 Is there any way to create shortcuts for a program? I have a couple of programs that only need copying over, but I'd like to stick a shortcut in the start menu. Question 2Also, does anyone know how I can get Norton Anti-virus professional to run from my install cd as the last thing? I know that there are several threads on this already, but I don't want to register it, just to start the installer as the last thing and run it manually. The following script doesn't work though. It says that I have to go through setup. (Presumably I could still copy over the latest definitions before the install though) Question 3 Is there any way that I can alter the file associations automatically? All help greatly appreciated!