You *MUST* have the .NET framework installed to use this utility.
If you successfully integrate a driver with this program and it is not listed as *verified* please post your success to this thread (I'm sure people will post if it doesn't work).
RASOR is only designed for use with XP (currently)
WHAT IS RASOR?
Raid Ata Sata Oem Repackager (RASOR) is a little utility to slipstream disk controller drivers into the textmode portion of unattended XP installs. It was spawned from trying to get my 3ware 7000-2 raid card working and from my desire to help others get their drivers working after I did. Rasor utilizes Method 2 (M2) style slipstreaming which is different (and less tested/verified) than the method (M1) used in Bashrat's Driver Pack. My2001 has written a good overview of the different types of slipstreaming here. I have previously written a guide about M2 style slipstreaming here,which may give you a better idea of what the utility is doing (atleast trying to do at this point). As I have before, I would like to thank rcordorica for his help in furthering the developement of the M2 method. While not a complete list I would also like to thank Bilou_Gateux, cfeedback, EDDI, my2001, and of course B‚shrat the Sneaky for their insights and support. Here is a Screenshot so you know what you are getting yourself into.
CUTTING TO THE CHASE - SUPPORTED DRIVERS
The list of currently supported drivers will be maintained (I hope)
- 3ware 6000 Series
- 3ware 7000/8000 Series (*verified*, trainee)
- Acard AEC-67160
- Acard AEC-671x
- Acard AEC-6880
- Adaptec Ultra160 Family
- nVidia nvRaid (*verified*, rcordorica)
- Silicon Image SiL 3x12A Raid
- Silicon Image SiL 3114 Raid (*verified*, rcordorica)
You can download Alpha 3 here: Rasor.exe (Right-Click Save-As).
The current release is Alpha 3. There is little to no reason for me to call it alpha 3 or to even have versions but what the heck, its fun! I have chosen to distribute this software under the Academic Free License v. 2.1 It can be viewed here. Basically it says: use, distribute, have fun, screw up, anything you want, but you still can't sue me. Please keep in mind that this is a very early release and there isn't very much 'ohh-crap' code. If you do something wierd to the software, it will most likely eat-sh*t-and-die. Generally this is easily solved: restart the software. That said, the software has only 1 known stability issue at this time (see bug list below).
CUTTING TO THE CHASE - USING IT
After you download RASOR you should put it in its own directory. RASOR does not create any registry entries or actually do anything at all outside of the directory you run it from and the directory you point it at when you use it (your XPCD source). If you are tired of having RASOR's useless carcass cluttering up your hard drive (all 60K of it) you can calmly delete the directory and all will be as before. If you didn't bother to read the big red .NET framework requirement at the top, please do so now. Back?...okay the only other requirement is that you *must* be connected to the internet for RASOR to work properly. All of the driver packages are stored remotely. This means you don't have to go and get them yourself. It also means that they *should* always be up to date (in the future I might get some help for this). If you can't handle my little program downloading things to your computer from the internet then you shouldn't use it.
When you first run RASOR it *may* take a few seconds to load and may flash some windows. This is perfectly normal! Rasor will first go out to the internet and look for a new version of itself. If a new version is found it will download it and restart. This makes sure that everyone is using the latest version. It also means that if I introduce some horrible bug, it will make everyone's copy break, yay! Then RASOR will grab the latest driver configuration list and ask you to choose the drivers to download.
The rest of the program should be pretty self-expanatory. You should pick a directory for the utility to repackage the drivers to. The program will find and append to an existing winnt.sif or will generate a new one (not a complete one, just a new one). It will create the necessary folders and it will copy the files <crossing-fingers>.
ANTICIPATED FAQ - BECUASE NOBODY HAS ASKED ANY QUESTIONS YET
Q: Why RASOR? Why not Method-Two Freakin-Cool Slipstreaming Utility?
A: Because RASOR is cooler and I can't pronounce MTFCSU.
Q: I don't like M$ and I don't want to install .NET. Will there be a non .NET version in the future?
A: No. I am a computer engineer by training (not a computer scientist), and my programming language of choice for small projects is C#.NET.
Q: Where do I put my driver files?
A: RASOR will download all of the necessary files for you. Again, you do NOT need to provide the driver files to RASOR.
Q: Will more drivers be provided in the future?
A: Yes! I will add driver files as I can, with priority to requests.
Q: Why is RASOR so ugly?
A: Becuase I wanted to make it work before I tried to make it pretty.
Q: Why wouldn't I just want to add every driver from the driver list to my CD?
A: Some of the drivers conflict with one another. In the future RASOR will not let you add drivers that conflict with one another but until then, you should only add the drivers you need. This will also make debugging problems much easier.
KNOWN BUGS & PLANNED IMPROVEMENTS
- RASOR always downloads the drivers, even if it already has the latest ones cached locally
- RASOR always downloads the Update utility, even if it already has the latest one
- RASOR crashes when not connected to the internet or when the rasor website is down
- File format has a compatibility problem with nvRaid drivers (fixed very soon)
- RASOR is not pleasant to look at
- Driver description is not properly updated when switching back and forth between the currently active available and selected drivers treeviews
- No progress bar when downloading files
This post has been edited by B‚shrat the Sneaky: 16 October 2005 - 12:18 PM