Despite clearly not reading my post, I decided to attempt your suggestion. My first step was to follow your link to what is a forum with between 50 and 100 threads. I read the stickies and eventually got to the site which hosted the BASE and massstorage driver packs. Inside the useful Installation_Instructions.htm file provided the refreshingly simple steps of: "Step-by-step 0. DOWNLOAD all DriverPacks you'd like to use and put them in the DriverPacks folder. 1. EXECUTE BTS_DPs_Slipstreamer.cmd (1). 2. COPY the CONTENTS ONLY of the folder UWXPCD_ROOT to the root of your Unattended Windows XP CD (2). OR EDIT the batch file BTS_DPs_autocopy.example.cmd with your settings, AFTER RENAMING it to BTS_DPs_autocopy.cmd. 3. EXECUTE RUN_ME.cmd (3)." Except #1 references a file which does not exist, I used a .cmd with as close to that filename as I could find. #2 specifies moving files between a source and a destination, NEITHER of which make any sense. And in between steps 1 and 2 there was a non-documented choice of methods 1 2 and 3 that had no labels on their methods besides literally... 1 2 and 3. After succumbing to curiosity/defeat I yanked a floppy drive out of another machine and attempted to install MCE off the unadulterated burned ISOs using F6-method. Now I know the ISOs I have are perfectly fine as the install went off without a hitch. I was just continually baffled at the insistence that nLite (a fine program, based on my experiences) is compatible with MCE, when every attempt at using it to simply slip in one SI312 driver and reiso-burn, continually yeilded a corrupt install. Since nLite is obviously compatible with MCE (people have done it) I would appreciate a very basic procedure of nLite-opening a MCE-CD1 disk to add in one SATA driver, reburning and installing poiting out any pitfals and chances for corruption that I may have missed. I would like to stress that nLite was certainly successful in slipping in the SATA drivers, the SATA controller was found by the windows installer, the SATA drive was detected, formatted, copied onto, it's just the remaining installation failed to run smoothly beyond this point. Presumably because the files copied to the drive by the format were just plain wrong in some way.