trainee

The new post became so long that I created a new thread. It can be found here. Anyone know how to change the topic title? Becuase now it shows up in the list as: Does anyone know how to make 3ware drivers work, post by trainee How to make 3ware drivers work, post by trainee Contrary to popular opinion I don't strive to talk to myself.

RASOR IS CURRENTLY *NOT* AVAILABLE (NO ETA SET) I have written a utility called RASOR that is able to slipstream drivers with this method. It can be found: HERE. UPDATE: 10/15/2004 Guide updated to reflect new research from members, especially rcordorica Known working list added Previous update notices removed KNOWN WORKING LIST: 3ware 7k/8k Driver Silicon Image 3112r Driver PREAMBLE First, if there has already been a big post on this then I'm sorry for making another one. Second, I tend to have *very* verbose posts, so I will try to keep this short. Disclaimer: I only claim that this will work for my hardware setup but I am posting this in the hopes that someone else can get theirs to work as well. I will try to help where I can, but I'm no expert. INTRO I have a complete (for all intents and purposes) XP PRO slipstream via XPCREATE *with* 3ware Raid 7k/8k drivers installed via the $OEM$\TEXTMODE Method; aka Method 2. From here on I'm calling this M2 because I'm tired of typing it out so much. I have tried the txtsetup aka Raskren's aka GM's aka RyanVM aka M1 method but was never able to get the 3ware drivers to load properly with that. It doesn't seem like too many people are running 3ware Raid cards, but if you are then *this* IS the method you should use. This should not be confused with the similar but more complex method outlined by Pure Krome (which I have not tried, but I do believe works) as listed here. SETUP I am using a XPCD slipstreamed with SP2, WMP10, Journal Viewer, .NET framework w/ SP1 THE PART YOU CARE ABOUT: EDITING DRIVER FILES So how do you use M2 to get your raid drivers on the CD? There have been a lot of posts about this as well as the somewhat erroneous information provided in deploy.chm (part of the MS SP1/SP2 deployment pack). I will assume you have your driver files (the equivalent of a floppy driver disk). A driver file-list *might* look like this (where driver is some relevant driver name): txtsetup.oem (this file sets the driver up for textmode) driver.inf (may also be named something like oeminstall.inf) driver.sys (1+ driver files) driver.cat (WHQL signing) driver.cpl (control panel file) driver.dll/.exe/.vxd (other libraries/executables for your driver) disk1 (a weird disk file may or may not be included; possibly plaintext) readme (of some sort) Many driver packages will NOT include .cpl, .dll, .exe, or .vxd files. There is nothing missing and this will usually make your install even easier to deal with. *IF* however you do have any of these files you *may* need to edit your txtsetup.oem file. Once again this is only for people who have files other than .inf, .cat, .sys and .oem in their driver packages. Okay you need to open up your txtsetup.oem file (notepad or any text editor will do) and change any reference to "DLL = " to "INF = " (thanks to rcordorica for figuring this out). For some reason textsetup chokes on these entries. These entries should be easy to find and replace in the file. Save the modified file and close it. Again if you don't have any "DLL = " references in your txtsetup.oem then you don't need to change anything and you read this entire section of the guide for nothing . THE PART YOU CARE ABOUT: COPYING DRIVER FILES Now you are ready to copy the driver files to the proper locations. You *can* strip the disk1 type files and the readme however I usually copy them for good measure. I also do not compress any of the sys files, although you *probably* could. So I choose to copy ALL of the driver files to these 2 directories: $OEM$\TEXTMODE\ I386\$OEM$\ If you have .cpl, .dll, .exe, .vxd files you need to copy these to a third location (A really big thank you goes to rcordorica for his tireless work figuring this out). Copy these additional files to: $OEM$\$$\OemDir\ THE PART YOU CARE ABOUT: EDITING WINNT.SIF Now 2 things need to be added to winnt.sif (if you don't know what that is, you really shouldn't have gotten this far in the post). A new [MassStorageDrivers] heading with 2+ entries (New Controller & CD-ROM Driver) A new heading [OEMBootFiles] which will list all of the files from the new driver This is best illustrated with my own winnt.sif (the whole of which is presented here) ;SetupMgrTag [Data] MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] DriverSigningPolicy=Ignore Repartition=Yes UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes UnattendSwitch="Yes" WaitForReboot="No" TargetPath=\WINDOWS [GuiUnattended] AdminPassword=XXXXX EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=4 OemSkipWelcome=1 [UserData] ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="Trainee" OrgName="Thunderwalker" ComputerName=XXXXX [Identification] JoinWorkgroup=XXXXX [Networking] InstallDefaultComponents=Yes [MassStorageDrivers] "3ware Escalade 7000/8000 Series ATA RAID Controller" = "OEM" "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" [OEMBootFiles] TXTSETUP.OEM oemsetup.inf 3waregsm.cat 3WDRV100.SYS 3WFLTDRV.SYS For the [MassStorageDrivers] entry I have been told that the listing must *exactly* match the description in txtsetup.oem. I have not confirmed this but I opened up txtsetup.oem and copied the description out of it, it should be very easy to find under the [sCSI] heading. I am 99% sure you must also list the IDE controller for your CD drive. If you don't, I don't believe that the setup can continue after the first reboot. I do not know if order matters, however I chose to list my RAID controller first followed by my IDE cd-rom controller. Anyone who has an IDE cd/dvd drive can pretty much just copy my line. The new controller should be listed as "OEM" as in look around in OEM to find the drivers. Any other controller (like the cd-rom) that use already built-in drivers should be listed as "RETAIL" as in included with the retail cd. Now the [OEMBootFiles] listings are basically the files from your driver disk. I do not know if order is important, but I chose to list the txtsetup.oem first, followed by any .inf, .cat, .sys and so on. I do not list the readme, or the crazy Disk1 type files. COMMON MISTAKES/MISCONCEPTIONS A number of posts list the TEXTMODE directory incorrectly as TXTMODE Deploy.chm states that if a txtsetup.oem file does not contain the HardwareID (as listed in the .inf) that it must be added. I know for a fact that this is WRONG. I screwed up my own install many times trying to add this to my txtsetup.oem. The 3ware txtsetup.oem does not have the hardwareID and installs perfectly. Make sure to list both your new controller AND your cd-rom controller under [MassStorageDrivers] There have been claims that ntfs won't read the /'s and all /'s must be changed to .'s and visa versa. IMHO: WTF. In most cases you shouldn't have to alter any of the driver files including txtsetup.oem (see next point). If your txtsetup.oem file contains "DLL =" entries (without the quotes), you will need to change them to "INF =" to get around a textmode parsing error (thanks rcordorica). NOW YOU TRY IT While this post is very long, I think you will agree that this is a fairly simple method to add drivers to your slipstreamed XP CD *IF* it works. Right now the only drivers known to work are the 3ware 7k/8k drivers and the Silicon Image 3112Raid driver. Unfortunately I don't have the hardware to test any other drivers right now. If you have any questions please ask them here, or PM me and I will do my best to answer them. ERRATA I'm including links to the 3ware txtsetup.oem and oemsetup.inf for reference, however neither of these files were altered (note that these were changed to .txt files so they aren't a pain to open). txtsetup.oem oemsetup.inf <--me, because I talk and talk and talk until even I'm bored!

Ok I have it *ALL* working. The $OEM$\TEXTMODE method (M2) is working great for me now, but I'm not sure there is enough interest to validate a big-ol post, so if people are interested let me know and I'll do up something (with as much detail as possible). Now that I am past this part I need to go learn more about regtweaks

Okay here's where I am: I now have a XPCD with SP1a (only! no other updates), working with the TEXTMODE method (i.e. method #2). I will be burning a full XPCREATE CD soon to make sure that it works with that as well. When I get that working I will provide greater detail on how I fixed this. It seems like only a handful of people have gotten the TEXTMODE method to work from CD, so I'm figuring that people will be interested if it does with a complete slipstream. Hopefully at least anyone else struggling with 3ware drivers will be able to learn something cya. (wow emotes sure are fun)

Errr no... I said they work with an f6 install (fully ATTENDED) to illustrate that the drivers aren't totally bunk thats all. (more clarity: bunk=FUBAR, FUBAR=malware, malware=well you get the idea). Anyway I'm sorry if my post seemed to indicate otherwise (rrraaaRRRRrrr Bad post! badddd post!), but I, like the rest of you, cannot do an unattended install with f6 loaded drivers, but I wish that I could . Anyway I've been up all night trying out different crap so excuse my ranting <---me. And that's all I have to say about that (holy crap I used a lot of smilies) EDIT: It's official, this is the only thread that shows up when you do a search for FUBAR. And I've hit the smiley limit, otherwise there would be a happy face <here> EDIT2: I edited the previous post to help alleviate the confusion, so RyanVM wasn't crazy it was not clear *BEFORE* hopefully it is now

Yeah, I've tried it with greenmachines method as well (that was my hacked by hand listing) To clarify I have tried these 3 methods (tweaking each to try to make them work): 1.) Using GM's method 2.) Using textmode method 3.) Using RyanVM's method (very similar to GM's method) With both #1 I am able to find and format the raid array, and do the initial install. Following the 1st reboot, I see the winXP startup very briefly and then get a BSOD with an 0x0000007B error (can't find disk) With #3 I get a BSOD subsequent to loading all the drivers (I watch them across the bottom) and prior to formatting the drives. With an f6 floppy load (standard attended install) I have no problems (thank god or i would really be SOL now wouldn't I?), so I know the drivers *DO* work. I am going to try and contact 3ware to see if they have any possible solutions (it is possible that they have a system integrator package or something since they ship primarily for large arrays and workstations. Thanks for the help and I will let you know if I make any progress. Note: No offense to anyone but isn't GM's method a.ka. Raskren's or a.ka. i don't even know who started it's method? A lot of what I got was from raskren's post. I find his to be slightly more general than GM's where GM's is slightly cleaner and more straightforward. Once again I'm not meaning to slight anyone; just trying to give credit where credit is due. Edited for clarity

I haven't found any posts about people using 3ware raid driver (specifically 7k/8k) successfully in an unattended install. I know that RyanVM has integrated the latest driver into his pack but I have not been able to get it to work. Here is what I am using: XPCREATE Slipstreamed CD tested working on a machine that doesn't need additional Raid drivers. Then I add raid information to the XPCREATE CDROOT and re-burn the CD (either hacking the drivers in by hand or using Ryan's patch, etc.) With Ryan's I get BSOD right after it finishes loading drivers on install So far the best I have been able to hack, gets me through install, but then I BSOD after first reboot. This may be an XPCREATE question, but I kinda feel like it is a chicken or egg thing. I guess I should try just getting the drivers to work without any slipstreamed updates. Anyway, does anyone have these drivers working in ANY unattended installation that may be able to help me? Thanks in advance for any help. EDIT: I have gotten just as far with METHOD #2. ie. $OEM$\Textmode & winnt.sif edit gets me as far as I can get with hacking txtsetup.sif. I can recognize the drivers initially, format the hard drive, and complete the initial install. After reboot I get a 0x0000007B error (essentially cannot find raid drivers). So if anyone wants to try (again) the Textmode winnt.sif method (with a driver they can already get to work with the txtsetup.sif method), then PM me and I can give you a detailed description of what I did.

@GreenMachine Okay. I found another post where you mentioned keeping the XP source on the hard drive. This definitely cut down on creation time for me. But what are the side effects of DOCABS=NO? My wild guess is that the cd size will be larger because the new files will not get packed into the cabs. If this is true (big if), won't the install size also be larger? I admit that I have little knowledge of what is going on when the install runs, but it was my impression that most of the cabs get copied over to allow for PnP hardware etc. For the original question: If you feel safer re-running the entire batch then so do I! I was really testing this one software/driver package that was giving me headaches. I was having difficulty recreating the initial install condition; ie. the package installs so many different files in multiple locations that uninstalling, and reinstalling did not produce the same order of events as the initial install. I made the decision that it was faster to re-burn and re-install than develop a full uninstall methodology. In retrospect there is probably a tool perfectly suited to this, but I have it working now and hindsight is 20/20. Thanks again.

Hi! I'm using XPCREATE to create my unattended install and I was wondering if there was a way to make a few changes in my included files (aka RunOnceEx, winnt.sif, etc.) and re-ISO and re-Burn without having to go through the entire process of integrating hotfixes and servicepacks again? I have the hotfixes installing (GreenMachine's list) and I just want to tweak and add to the RunOnceEx. I prefer to make changes incrementally to help contain errors (personal preference). I believe that I should put the changed files in the correct locations under CDROOT and then execute a subset of the commands in the xpcreate.cmd, specifically: CALL :SETVARSCALL :MAKEISOCALL :BURNISOCALL :DONEI think this works, but I want to make sure I'm not doing anything blatantly wrong or *bad* by doing this. Thanks in advance! Since this is my first post I wanted to say thanks to GreenMachine for the awesome program and resources he has made available, AND to the entire MSFN community for all the information provided here. These forums have taught me a lot in the last week and have the greatest breadth, depth and accuracy of any XP forum I know of.