Garak

The idea setting up everything without the SATA drivers is a good one. If I can't get this working I'll go ahead and do that. I'm not 100% sure that there isn't something else going on here BAM. The drivers for my controller appeared to be the same to me as well. I've been thinking that maybe I was doing something wrong here. It is possible that the stop errors are from something else. However, this is exactly the same place I got the stop errors when I was first learning to integrate a SATA driver a year ago. It's like the CD loads it on first bootup and is able to format the drive. Upon reboot, the driver does not load and is not able to pickup the install from the hard drive. My latest efforts have been to minimize this possibility. My exact procedure has been to use the latest Nlite to slipstream in SR2 and disable the file protection. After that I go through the installation of the BTS Driverpacks exactly as directed in the extended intructions. I'm not using any of my usual application adding or registry tweaks. I haven't added a thing from what I've told you. Windows is not my strong suit but I'm still fairly competent with it. I've created slipstreamed installs before (manually) without problems. Having all the drivers included with the BTS install is very appealing and I'd like to get that working if possible. The only possible thing I can think of that might be interfering with the SATA driver is the fact that it is installed to the SATA2 port instead of SATA1. The first SATA port had the plastic cover break off during initial installation. The SATA port still works fine, but without that plastic cover, it will not stay in place firmly when hooking up the drive. The system works fine on the second SATA port. I only mention it because it is the only thing I can think of that is not completely standard. I can't imagine that this would make any difference but I could be wrong. I'm sort of grasping at straws here and I'm open to any suggestions, no matter how remote a possibility. I'm leaning toward the suggestion of just putting in all the drivers but the MassStorage ones and adding the two or three most common ones I use manually. I'm going to give it some time to let others read these posts and offer any other suggestions first. None of this just makes any sense to me. From what I can tell, this should be working. One last note, I have downloaded the drivers once again (one at a time) just to make sure that there is no corruption as other seem to have had this issue recently.

I've been trying to get the BTS Driverpacks working on one particular system for about six months now. I've checked back with the forum every month or so to see what is going on, and try downloading the latest version for another go at it. I've been assuming that the problems were due to development of the MassStorage being a work in progress. I've got a small form factor PC (Biostar IDEQ 200N) with the nVIDIA nForce2 IGP chipset utilizing a Realtek 8201BL controller for the SATA drive. This is all onboard. I just downloaded all of the BTS driverpacks last night and followed the directions to the letter. I'm using method one and keeping the drivers. I'm trying to get the most straightforward setup possible so that there is the least chance of a problem. The same problem persists for me. I am able to boot from the CD and format the partition. It loads all of the drivers just fine. Then on the first reboot, I get stop errors which appear to be releated to the SATA. I've made install CDs for WinXP Pro before using the Green Machine method of adding SATA support. I'd like to have a CD that has all of the drivers in it. That is not going to be possible if I have to add all of them manually. I simply don't have the time. Do the BTS drivers include boot support for the MassStorage devices? I've been assuming they did. If they do, is there an issue with this SATA driver? Please someone take a look at this. I've been trying to be patient but I'm about to give up on using the BTS Driverpacks and just add a couple of SATA drivers in manually and call it quits. I'd like to have a CD that I have use on all of my friends systems when they screw it up. Somehow I always get called to help them out. Thanks.

I'm getting the same problems with aliide.sys during the txtmode setup. I did notice that during the integration that there were some anomolies. I wish I had noted exactly what happened but there was an extra directory created with one driver assigned moved to it. I don't think it was the aliide.sys however. I just attributed it to a type-o in the batch and copied it to the i386 folder. When you're going over the problems with these drivers that were fixed in a previous version, you might want to double check for type-o's as well. Looking forward to testing the next update. Thanks for working through these issues.

I'm still getting a BSOD after first reboot. Windows Professional Corp Athlon 3000 Chipsets: KM400A / VT8237 1 x SATA Drive 250gb (no raid) Using Nlite 0.998 (just downloaded today) Using Ryan's Update Pack Lite (just downloaded today) Using all current versions of BTS packs (downloaded today) Method 2 used I'm not using any hacked files or registry tweaks that I haven't used on past installations. Also, I believe that these are applied after this point in the installation process. Not many options were applied in Nlite. Mostly just SR-2 slipstream and a couple of standard tweaks. I've tried this same setup without Ryan's Pack to see if that was it. Same problem. Getting Stop error 0x0000007B. Everything appears to be fine up until the first reboot. I get the WinXP logo and then it immediately goes to BSOD. I've repeated this process several times with the same result. A couple of notes however: I notice that the final batch file creates both a "$OEM$" and an "OEM" folder. I've tried combining them and leaving them separate. I thought this was odd. I don't seem to have any of the sound control panels batch files I was use to from previous versions. Have these been removed? I repeated the install procedure several times thinking I must have been doing something wrong. I had a similar problem many months ago when I slipstreamed in SATA drivers manually. It turned out that the order in which the drivers were added made a difference (at least it appeared so). On that system I was using a Raid 0 with a nforce2 chipset. When I put the 3112r drivers before the 3112 drivers in txtsetup.sif, it solved the problem. I never quite understood why that would make a difference. Perhaps it was just my lack of understanding. I'm at a loss. Am I doing something wrong here or is there an issue?

Nice detective work. I know you are pressed for time Bâshrat, but could I make a request? Could you release a version of the Mass Storage drivers with all of the drivers that work updated but using a previous release of the Nvidia drivers that are giving everyone so many problems? The last time I started editing entries for slipstreamed nvraid drivers I got myself in a world of hurt which took me days to straighten out. Windows slipstreaming has not been my area of expertise and I've been awaiting the fix for this bug with baited breath. I have a couple of new systems which I want to deploy with WinXP Pro SR2 slipstreamed in as soon as possible. If you're close to a final workaround then just disregard this request. Thanks for all the work in troubleshooting and maintaining these driver packs. I think you are doing an outstanding job.

I had a very similar problem with the same driver. My solution was this: 1) Take out Ryan's driver pack (it doesn't work for the Si3112 driver) 2) Download the driver from your motherboard manufacturer 3) Follow the Green Machine's instructions to the letter. The motherboard manufacturer should include all of the files you need to accomplish this. At least Asus did in my case. I did get mine working so I know its possible with the Si3112 driver.

[removed]

I am using an almost identical install now as I was with SR-1a. The only two major differences are that I'm now using NLite, and SR-2. It is interesting to note that my install does complete if left alone, despite the nag screen. When it is finished, Alcohol 120% works fine. I'm suspecting that this has something to do with SR-2. Perhaps as Alcohol is installing the virtual CD drivers, it forces a hardware detection refresh. Windows may be wanting to install drivers for the virtual CD drive on it's own, despite the fact that there has already been a driver installed. I also wonder if this has something to do with the new protocols of not installing unsigned drivers. Others have noted that the new Nvidia Forcewave 61.77 drivers (which are currently the only ones that support DirectX 9.0c) will not slipstream because they are not signed. I have confirmed this myself. My current guess is that since Microsoft has decided to make SR-2 the "Security Awareness" release, that they have made driver installation more restrictive (especially to a slipstream install). My next step is going to be to make a custom installation package just for Alcohol. Perhaps something along the line of using InstallRite which appears to just throw the software in the correct directories and then patch the registry. Perhaps that can bypass the hardware detection problem. But that is for another day. I've got to get some sleep.

I'm having the same problem. Can't seem to find the solution anywhere in the forum. Anyone have a link?