I'm coming to you now from a fresh install of Windows XP on an Intel ICH5R controller. I installed Windows without having to use a floppy disk and I would like to explain how I did this. I have looked all over the internet for months - across many different forums to find a solution that works. Perhaps if this works for people it could be a sticky? I would also like to explain how to "slipstream" the Intel INF drivers as well for a total Intel 865 or 875 solution!

Now here we go.

I. Some information on my hardware setup:
I'm using an IC7-Max3 motherboard which contains 4 SATA ports controlled by a Silicon Image 3114 chip as well as 2 other SATA connections controlled by the ICH5R southbridge. I currently have two SATA hard drives in RAID0 on the Intel controller. Installing Windows to disks on either the Intel or SI controllers requires an "F6" driver before the disks are even visible to the OS. Just to cover all the bases, I added both the SI and Intel drivers to this CD.

II. Getting the files:
The first thing to do is obtain the driver files that we need. AFAIK Silicon Image doesn't provide generic drivers on their website; you have to go to the mfg of your particular board. I got mine from Abit here. There are a couple places to get the ICH5R drivers. You can get them out of the Intel Application Accel. package, the Intel "F6" diskette creation utility, or your OEM. Since we're trying to avoid using a floppy strike the diskette utility and let us use the IAA Package.

III. Extracting Drivers:
Now we need to get the necessary files out of the zip archives we just downloaded. The Silicon Image drivers DL'd from Abit are easy, just use Winzip or Winrar to extract the exe file to the directory of your choice. Let us say you extracted them to a directory called "SI". Go there and inside you'll see numerous files as well as a directory called "2kxp." Look inside and you should see 8 files totaling 355,730 bytes.

Note: You can safely delete readme.txt leaving only 7 files.

As for the Intel drivers we have to use a few command line switches. First extract the contents of iaar353_...exe using Winrar or Winzip to any location. Open the contents of the extracted archive and you'll see Data1.cab and Data2.cab, those files contain the drivers we need. To get the drivers OUT open a command prompt and navigate to the file "Setup.exe" (the one we just extracted).

At the command prompt type:

Where "<path>" is a destination folder on your hard drive. For the remainer of this document I will assume you used a directory called "temp" on the "C:" drive.

Navigate to c:\temp and there should be a folder called "Driver" open it and there should be 4 files inside coming to 286,347 bytes.


IV. Putting the puzzle together
Now that we have the essential drivers extracted we'll need to put them in their proper locations on the CD. I ended up putting a few copies in various locations and I am unsure if the redundency is actually needed, but I'm going to explain exactly what I did just to be safe.

The first place to add a copy is to the TXTMODE folder of your CD. That is: "c:\xpcd\$OEM$\TEXTMODE" Here you can dump the 7 Silicon Image files and 4 Intel files.
Location number two is the location specified (or will be specified) in Winnt.sif for OEMpnpDriversPath. On my CD this is:



I have added the Intel drivers (all 4 files) to folder 01 and the SI drivers (7 files) to 02. Here you need to have your SATA drivers in the lowest numbered folders. That is, don't have your printer drivers in 01 and SATA in 02.

The third and final location is in the i386 directory which will be located at the root of your CD. This time we only need to be concerned with the *.sys files of each driver set. That would be iastor.sys and si3114r.sys; you do not need SIWinAcc.sys for this step. I chose to compress these files and I recommend you do the same. Use the MAKECAB utility to do so. You'll end up with "iastor.sy_" and "si3114r.sy_" Now simply copy both of these files to the i386 directory. Now we're done copying files.

V. Modifying installation files
The first file to be modified is TXTSETUP.SIF which is in the i386 directory. This file tells Windows what files to load during the text-only portion of setup. We are going to modify the file to make Windows think that Microsoft put these new driver files in i386 and load them accordingly. Open up TXTSETUP.SIF and do a search for [SourceDisksFiles]. In my file it was on line 181. Now add this text EXACTLY AS SHOWN (except what's in the brackets).

Each driver listing needs to be on its own line...you'll get the format once you look in TXTSETUP.SIF. You can put this anywhere within the [SourceDisksFiles] section. I'm aware that there are multiple instances of [SDF]...I added my drivers to the first instance.

For a detailed explanation of what all those numbers and commas mean go here.

Still within TXTSETUP.SIF look for [HardwareIdsDatabase] around line 18270. These entries associate drivers with PCI device Ids detected on the machine. Within this section add these lines:


As you can see there is only one Id for Intel and multiples for SI which is OK. Now remember the file "txtsetup.oem" that we extracted from both driver sets? That's a text file which can be opened in Notepad and it contains the device Ids. If you're trying this out with other drivers and don't know the proper Id, look in txtsetup.oem or the INF file associated with that particular driver.

We now need to find [SCSI.load] in TXTSETUP.SIF. Look around line 18725. Add the lines below to this section.

One more section to go...

Find [SCSI] - around line 21059. Add this:


Here you can replace the text in quotes with anything you want. So if you want iaStor to be "Super Pimped hizard dizisk controllaz" then go for it.

That's it for TXTSETUP.SIF. The next file we need to create or modify is WINNT.SIF. If you're frequenting the unattended forums then you probably already know how to create or modify it. If you don't, check
this out.
Here all we need to do is point OEMpnpDriversPath to the locations we set up. Remember $OEM$\$1\Drivers\01? If that is the location of the Intel or SI files then WINNT.SIF should read like this...

If you have multiple folders like I do make sure that its all contained on ONE line (the forum software might wrap it here).

VI. Blaze it
Now its time to burn the files to a CD or preferably, a CD-RW.

VII. Test it
Testing the functionality of our new drivers is impossible with VMware or Virtual PC because these raid/SATA controllers do not exist within the virtual machine, which is also why we burned an actual CD instead of creating an ISO image. Restart and boot from the CD. When it says "Press F6..." you can simply ignore it, or do like I did and give your monitor the finger. Now watch the bar at the bottom of the screen very closely as it lists drivers being loaded. I have a fairly fast machine and I was able to catch a glimpse of "Intel® 82801ER SATA RAID Controller" and "Silicon Image SiI 3114 SATARaid Controller" being loaded. It does go by very quickly though, so pay attention. Now I believe at this point your computer will reboot and you'll be taken to the disk formatting and partitioning screen (depending on what is in WINNT.SIF). If you see your hard drive listed then you have success!

So far I have only tested this on a RAID 0 setup using the Intel controller, but I assume that SI will work because the driver does load during text mode. Hopefully this method will work for all "F6" drivers, so lets see if we can give Nforce and PCI slot based controllers a hand too.

Good luck!

Here's my TXTSETUP.SIF if anyone wants it. It has the Silicon Image and Intel drivers as I listed above.

try installing these drivers WITHOUT having to hack the TXTSETUP.SIF file - that's a bigger challenge. The txtsetup.sif method has been known for ages.

for more info, search for other posts by me, re: SATA

Why? Its only 10 or 12 lines that have to be added.

Ignore Krome

You got it right the first time, the same as the OEM instruction we provide defining mass storage at boot time

Good work at taking the time and for providing the SIF for people it applies to. It should go a long way toward them filling in the gap with their own - promise.highpoint.etc

But you do need to adjust your driver folder order.

as a chipset driver (and it is in the intel design)
it goes to driver folder 000

for third party controllers they go to the ias/nas folders later in the sequence

Spheris: Could you provide 'correct' folder numbering for us.
Cheers,
Steve

Yes, please elaborate.

The method I outlined above worked perfectly for my install, but it could always be better.

I'm glad it worked out. Also great explanation. Now the problem is to do it with slipstreamed hotfixes and updates. I used THIS guide and it worked fine. I have tried for quite a bit Using GreenMachine XPCREATE (that's the easiest way I know to have all updates slipstreamed) without any luck for RAID. DId you try your method with all hotfixes slipstreamed and fully unattended setup?

Yes, its SP1, Rollup, and all hotfixes to date. Most hotfixes install using svcpack. In the past I was not able to use RAID drivers AT ALL if oemPreInstall=1 in winnt.sif. That's why I'm so excited that this method worked!

>>Why? Its only 10 or 12 lines that have to be added.

from what i understand with the Setup.sif file, there is a section called MassDrivers or something (it's been a few months since i last did any unattended stuff). MS added this section to make it QUICK and SIMPLE to add RAID/SATA drivers to an unattended install.

by QUICK and SIMPLE i mean :-
o) Dump the drivers in a Folder
o) Tell the installation (setup.sif) which driver to use.

there. done. simple.

no need to search for lines and copy and paste, etc. No need to double check that what u've typed is correct. No need to research what the hell that gobbedly-gook in txtsetup.sif really means. wtf does PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "Si3114r" really mean? what's dev_3114? subsys_61141095?

come on people!

don't just get a file and use it becuase people say 'this file makes your unattneded install work with a xxx SATA drive'. QUESTION EVERYTHING. I first found the above answer and had no idea what that ment. Yes, i could have look long and hard for what that ment, and repeat that process for any other SATA / RAID driver that poped into the office, so i looked for the generic solution and MS even provided one - albiet a bit buggy, but it seems to be the suggested way.

as always there are a million ways to do a single job. i personally find the above way a hack compared to other ways. Becuase it's a hack, doesn't mean don't use it, nor is it bad.

to use two more bad analogies -> it's all in the eye of the beholder, and whatever floats your boat.

just remember, please question everything suggested here so u understand what is going on, as opposed to just learning what files go where to fix a problem - that's not really learning persay.

anyways ...

@raskren
Could you post your winnt.sif file and take a screenshot from windows explorer of your expanded CD directories. It will be helpful.

@Pure Krome
It will be good if you could share this method with examples. I would be interested in it too. If you have a time please post step by step with short explanation (where needed). I will be happy to give it a shot and test it.

The OEM sort order for driver installation from .SIF

000=smbus/chipset
001=lan
002=usb/firewire/serial i-o
003=audio
004=video
005=nas
006=ias

*nas = network accessible storage
*ias = internal accessible storage/raid/fiber etc

considering the perpetual race to driver updates, it's probably time to create a set folder within the directory sort. out of order pnp sequence sorts are right now about 80% of either failed installs or underperforming and "troubled" installs reported from the OEMs in the last year and particularly post SP1 as the pnp system was revised and rolled to full acpi 2.0 specification to support HT and APIC support in the 865/875 systems


Reposted from the Discussion Thread for GreenMachine and I for collaboration on some of the clean up for xpcreate

Krome

I'm going to revise my previous harshness a bit with this. Yes, there are multiple means to the end.

Even our own approved one has its flaws in that end users have to be careful with doing it and be precise. But it does work in all cases where it is correct and support will respond to it if you have to contact them about it. Is it a hack

good question. Isn't nearly everything being done here that alters the original disc structure a hack?
Its all relative, but don't s*** on someone because they made some headway with doing it, right way or wrong way as long as they got somewhere with it. Otherwise I'd just be everywhere in here all day long smacking people for the most rediculous things.

Amen!

But sometimes, a hack is the only way, like UXTHEME. And considering all the hair-pulling over these drivers, and working solution is worth learning from. I read, with interest, lots of hacks all over this forum, even though I still feel quilty just replacing an empty SVCPACK.INF with my own. It all adds insight needed to find out what floats my boat.

Anyways, raskren has made more progress than me right now, on this, so thanks for posting your findings.

One question about testing these CDs: How are these CDs supposed to behave in VPC, or a NON-SATA/RAID system? I ask because of the need to add a PCI IDE Controller mentioned in THIS article implied (to me ...) sounded like it would not work without an implicit IDE driver.

... I got most of the loose ends tied in XPCREATE (for the moment), so it looks like this is my current quest ...

Yeah Chrome...already tried that. I have done extensive reading of MS KB articles for months now. When I use mass storage line in winnt.sif it: refuses to copy the necessary files over, causes a bsod, or iastor.sys generates a cryptic error message.

This is the only method that has EVER worked for me.

Why don't YOU do a search at www.microsoft.com for txtsetup.sif. Microsoft gives you instructions on how to modify this file.

I spent weeks researching, burning cds, and testing and now I want to share an easy method that WORKS for me. Just look at the number of F6 installs that don't work for people on this board. I don't understand why you must criticize when I'm providing free help for a widespread problem!

PLZ Pure Krome: Can you share the method you used for easily adding a RAID/SATA-Driver? I never tried it the hacked way because I didn't understand it and it seemed very specific for one device. Unfortunately I failed doing it the other way. I've been trying it for almost 2 weeks in a row and couldn't get it to work. Everywhere you get different instructions where to put you drivers and what files to modify.

So if you really got the second method to work I can hardly wait to give it a shot!

@raskren
I'm about to try your method. However I'm in doubt about 1 thing. If I set up oemPreinstall to NO will it install all the drivers? I have strong feeling that I'm missing something. I modified txtsetup.sif and set paths to the drivers but with OemPreinstall set to NO will it work. Here what I have

I had OEMPreInstall=Yes and it installed all of my drivers which were sata, chipset, audigy2, printer, and lan.

Spheris,

I was under the impression that MSFN suggested using a numbering system so drivers install in the proper order and lower folders are installed first. Since we're installing an operating system one would think that the most critical drivers would be the ATA/SATA set because of how picky Windows seems to be about the whole unattended/raid situation. I'm also curious as to where you found this information. In all of my studies I have not come across anything (by MS) like this. In fact, This article, KB314479 doesn't mention any particular method for folder naming. Just names like "lan", "video", etc.

Just out of curiosity, does anyone have a computer from a tier 1 or 2 OEM (one that has the capacity to press their own cds) that contains any sort of raid setup or pci controller card installed? It would be interesting to see how Dell, Gateway, MSI, Gigabyte, would do this...that is...as long as they don't force the user to use a **** floppy.

rasken

the 000 structure is what is used in house for HQL and engineering testing and recommended to OEM vendors as a failsafe.

The KB article is accurate to an extent, but we've found in house that for non ISO disc structures, the numeric sort seems to get around some of the unicode and other alphanumeric problems that crop up in testing.

you have the list as defined by the KB

or use the other, either will work in standardised scenarios. the other has proven more robust in non standard scenarios such as udf format discs and ISO level 3 etc.

There are no plans to update the KB article as the restructuring of the disc structure to non standardised formats isa violation of the eula and not recommended to end user practices.

Hi Folks...

i didn't get any emails about replies, so i forgot to check this thread *blush*

ok.. some info about what i did? sure.

(appologies for offsite link)

the my solution is this => http://forum.abit-usa.com/showthread.php?s=&threadid=29161

and for a detailed run down of the research ( a very mind-numbing read) ...

http://forum.abit-usa.com/showthread.php?s=&threadid=14297

so in the end, i _did_ get the OS to auto-copy the driver files over to the correct places by using the [MassStorageDrivers] line.

like i said - it's been a few months (october?) since i last mucked around with this ... but i've been trying for a year.



>>Why don't YOU do a search at www.microsoft.com for txtsetup.sif
heh keep your cool, buddy. did that a long time ago. anyways, i really don't want this to turn into a flame/troll topic. I was only trying to suggest other ways to solve the same problem - other ways which i believe are more stylish and less of a hack. Yes - we have to hack certain things to get our results (eg. the UXTHEME example above). I'm just hoping people continue to try and find more elegant and less troublesome ways to get the same solution - that is what this website is all about.

Please, have a read about what i posted up, and i hope u have some luck - please post any comments.

I followed this guide... I only had to add about four lines of test, and all is working fine.

http://www.nforcershq.com/forum/viewtopic....der=asc&start=0



Oh and of course, pointed the oem...path in winnt.sif to the $OEM$ folder...

Works fine for me

Hi all,

New to this forum.

I got a question for you guys, How in the world do you get the info for the fills you need to add to your files for the SATA installion.

This is from first post.

". Modifying installation files
The first file to be modified is TXTSETUP.SIF which is in the i386 directory. This file tells Windows what files to load during the text-only portion of setup. We are going to modify the file to make Windows think that Microsoft put these new driver files in i386 and load them accordingly. Open up TXTSETUP.SIF and do a search for [SourceDisksFiles]. In my file it was on line 181. Now add this text EXACTLY AS SHOWN.

CODE

iaStor.sys = 100,,,,,,3_,4,1,,,1,4
si3114r.sys = 100,,,,,,3_,4,1,,,1,4 "

What I want to know is how to find this information.

iaStor.sys = 100,,,,,,3_,4,1,,,1,4
si3114r.sys = 100,,,,,,3_,4,1,,,1,4

The numbers at the end. The rest of the information I'm able to find within my setup files for my SATA controller which is the Promsie 367. Build in for the P4PE MB from Asus. Smillar your guys, but my controller is differnet and doesn't use the two newer chips from Intel.

thanks for any info.

/me listens intently for an answer to Ghents question ....

Found something that you guys haven't listed about the Unattended Installation of windows. If you guys did I just missed it that's all.

Go to your deploy.cab on your Windows Xp Cd (SUPPORT\TOOLS) and extract the file to whereevery you want to. Look for the file called ref.chm and open it.

Yes it's a help file, but this file explains in detail everything you can do to winnt.sif.

Great little pieces of info like how to make sure MSN 4.6 and Explorer 7 aren't installed and so on.

Give it a look. There is a lot that you can make changes to the installation of windows and how it work without having to make reg files to be loaded durning installation.

Hope it helps out,

that cab also contains a simple program that automatically helps make a simple .sif file.

the good thing with that ref.chm help file is that it lists a huge bunch of things u can not install, much more than then .sif wizard program.

Now ... where is my CD.. burn baby burn. Thanks all for explanations.

This is about my earler post asking about what the what these number mean in the tstsetup.sif "autofmt.exe = 1,,,,,,_x,2,0,0,,1,2"

Here's a link to a web site that explains a bit of it, but not all. Still looking for more info on it, but no luck.

http://gosh.msfnhosting.com/txtsetup.htm

Guess the Credit for this goes to Gosh.

I'll post more if I can find anything more about the last few numbers, but they don't look to important.

Beleive only this part "1,,,,,,_x,2,0" is what you really do need to config so that your drive install properly at the textmode of windows so you can see your SATA drive's or RAID drive's.

@raskren:
Thanks again for your post. After trying various things, i have settled on a "lite" version of this method for use in XPCREATE. The changes I made:

1) I dumped the TEXTMODE directory as well as all of the TXTSETUP.OEM files, as they seemed to be too often the source of error.

2) I added all the text to TXTSETUP.SIF in one block, with it's own headers, to the end of the file. Make automated editing a breeze. As you noticed there where already multiple SourceDisksFiles sections. Windows parses all elements from multiple instances of a header together before processing the file itself.

For what it is worth, the steps I took are listed on THIS page.

Thanks again, raskren, for getting me started on this, and for your clear instructions.

Looks good!

That's a great idea to just add the subsections with their new entires all at the end. No more hunting for [scsi] and all that.

I'm glad you did not feel slighted!

Somehow it seems much "cleaner" without hunting down the INF sections, and I was not looking forward to writing that script. Thanks go out to jdeboeck for pointing out that multiple instances of the same section header were not a problem.

I actually started out using all the steps you listed, and removed or "simplified" them after that was working. And I NEVER liked those TXTSETUP.OEM. I think the key is that TXTSETUP.OEM requires editing depending on File Systems, and in a fresh CD install, you do not need to pre-determine the File System. I have not heard of anyone having succes with this file. (Except Pure Krome, but after looking at that method I determined that "hacking" TXTSETUP.INF was a whole lot cleaner than hijacking the XP install, and adding three different copies of TXTSETUP.OEM: Sorry, I had to conclude that this way is much less of a "hack"). I DO NOT believe that the WINNT.SIF / MassStorageDrivers was designed to be used for CD installs, rather for network or SysPrep installs.

Same here. After seeing just about everyone's install fail from CD that's the only conclusion I can come to.

I do have a hard time thinking of this as a hack. MS left txtsetup.sif as a plain text file when they could have encoded it in a binary and forced us to hex edit it. I'd call that a hack but not just editing a text file. Is creating winnt.sif a hack? Or cmdlines.txt? If Microsoft wanted to add new F6 drivers to the CD themselves I'm sure this is how they would do it. Once everything is put in its place the install is literally seamless.

Hello you jackass, no need to be a dick to people. The Winnt.SIF method only works on certain PCs, those that have the RAID/SCSI controller specified. If they don't, it errors out. It's also very hard to set up and have work right, it took me a helluva long time. The txtsetup.sif method worked first try for me, and it worked great.

@Rasken,
Dude, I give me my full support!!!! Your method worked for me right out of the box. I also have an ABIT IC7 MAX3 board and wanted to install unattended (without F6 input). 1 pass, no errors. Thnx.

Now,,,on,,, to figure out why Photoshop 7.0 is not installing.....................


The Old Dude

Right on my friend, glad to hear it!

I realize it was a while ago anyone posted in this thread but I have a question regarding adding SATA/RAID drivers using Raskrens method here (which btw I find much easier than Chrome's method which i find too complicated to bother with).

Raskren - you specified that we should add the following lines to txtsetup.sif:



I'm btw also adding SI3112A SATA drivers as well as Highpoint 372 RAID drivers to my installation. When I look at the TxtSetup.oem & .inf files of those drivers and look at the corresponding sections you mentioned above, it looks a bit different than the way you have described it. Here's an excerpt of the SI3112A SATA driver sections from the TxtSetup.oem & .inf files of the drivers I'm using:



Now if you compare these with those you posted the headers are obviously a bit different as is the information contained under them. There is also an additional header [Config.Si3112] which contains info specific to the 3112A controller as well. My question is: even if the info in my files isn't exactly the same as what you posted - would there be a problem adding these lines as is (in accordance to Greenmachines guide) to my txtsetup.sif? It seems to be stating the same info only in a different manner. Or do the lines to be added have to be exactly as you posted? If so, what's the reason for this?

Sorry about the long post but I need to get clarification on this point to really understand what's going on here...............

***BUMP***

This information may be of some help to you. It explains what all the digits in txtsetup.sif lines mean.
http://www.msfn.org/board/index.php?showtopic=14852&hl=

It looks like all your driver files belong in Windows\System32 so here's what you need to add:



You'll need to add the rest of the device ids in the format above. You should put the rest of the driver files (other than .sys) into $OEM$\$$\System32 so they get copied over as well.

Good luck, and if I don't respond here feel free to send me a PM and I'll glady try and help.

Don't forget to compress your .sys file before you copy it to i386.

man, that is complicated, i would also like to do the same on my maxtor sata's, i just got my second one, i will be formatting them and raiding them in a couple of weeks, never raided before, so dont know what im doing, but it would sure be handy to install the sata drivers and setup raid automatically, then do the unattended install of xp.

I spent a good day, day and a half, trying to get my Promise FastTrak 100 to work. Then it hit me, I already had a working solution from that BartPE CD I made the other week! So I used the settings I used from that:



at the end of my TXTSETUP.SIF and then put my fasttrak.sys file in \i386\ but I did not compress it with the makecab command from here http://greenmachine.msfnhosting.com/READING/addraid.htm and it works. So at least in my case, that page was almost correct, but not quite. The line under SourceDisksFiles is just slightly different, and I had to use an uncompressed driver. I couldn't get mine to work when I followed that page to the letter. Driver difference perhaps. Dunno. Working now though, woot.

Oh, and I made my TXTSETUP.OEM by hand, altering the one from Microsoft's ScsiCfgSet.exe example/guideline files. And I also altered the FASTTRAK.INF file to match what I used in the TXTSETUP.OEM file. I could paste them if someone wants to see them.

I have Promise Drivers on a AX4PEMAX card, here is my txtsetup.sif
Can you guys tell me if it is correct?

Hey Everyone,

Thanks for all the advice in this forum. I'm trying out this method of preloading drivers now.

I'm also curious if this method will work in Win2k? (Pro/Srv/Adv)

I'm building unattended installs here at work and would like to cover all my bases with this method of preloading the RAID drivers.

TIA!

Dave O.

twreck,

You don't need a txtsetup.oem file at all when using this method. Txtsetup.oem is accessed by setup if you use [massStorage...] in winnt.sif.


Neoh,

Your settings look right, did they work?


doslager,

This will work in Windows 2000 and perhaps NT4 but I haven't tested it on either platform.

i did it with sil3112 got an error when installing it, had 1 file 3114 named.
now i tested it trough Vmware and i saw it that he was loading it and no error came

I'm not good at english!
Who can show me the files for Intel 865PE-ICH5R motherboards!

Why do so many IDE drivers use 1,,,,,,4_,4,1,,,1,4 in txtsetup.sif?

Maurice,

VMware does not accurately portray how a Windows image will actually perform on your "real" hardware. Your virtual disk may be on a SATA drive or RAID array but the guest operating system is simply installed on a plain 'ol (virutal) IDE or SCSI drive. If you see the driver name flash by during the text mode setup, there's a good chance it will actually work.

zhenxy,

If your motherboard has an ICH5-R southbridge you need iastor.sys and that is all. Its the same file that I used in the article.

RyanVM,

I posted in regards to what all those commas and switches do here:

http://www.msfn.org/board/index.php?showtopic=14852&hl=

I hope this helps.

I've seen that thread and gosh's page, but I still don't understand what the 4s are for.

The 4 indicates the destination directory for the associated file. In this case: \Windows\system32. You need to analyze the INF file that comes with the driver(s) to determine exactly where things go.