@headspin: Reluctently, I have updated the download list. Let me know if there are any more dead links. I will look over your SATA drivers this week. I will add any signed SATA drivers to XPCREATE's list, once the person requesting it can confirm success. Unsigned drivers may (or may not) be added using the method outlined on my website, but I will not be integrating or testing them. (You're OK, there are signed drivers.)
@Geezer: Welcome. I'm sure if you look around long enough, or ask the right questions, you will find whatever you need here. As for XPCREATE and WIN2K, both boehmri and utln have had some success. I did have a version of 2KCREATE. I should have some time this week, and together we could go over the remaining issues. Progress will be directly related to your availability for testing and reporting. Perhaps this would be a good time for anyone else intereted in WIN2K to speak up.
Syncronising documentation and functionality is, for any developer, an ongoing battle. In my case it depends on many external factors, such as my workload, and my mood ... XPCREATE is nearly "fixed" for it's next release, and at that point it will be easier to write the documentation. As for grammatical correctness, I was terrorized by my A level English teacher, who used to jump up on the desk and recite King Lear (or even worse, Cordilia ... ). I've not been the same since. I am glad to see that it has been noticed, and I will note that I do it without a syntax/spell checker. If it paid as well, I'd just as soon write English as code, but I ain't that good.
I'll give a test WIN2K run here, and let you know where it stands. As for service pack 5 ... forget about it. But perhaps you could compile a list of critical / recommended SP4 hotfixes? Perhaps someone else already has one? I'm also curious as to why you want WIN2K, and not XP, and how many machines you intend to install. As for IE, I believe the best solution is to use the IEAK, create the distribution flat, and pack it into an IExpress package. It works for MS, it'll work fine for us. Take a little time to set it up correctly, and you will end up with a perfectly tuned IE installation, available for installation with the click of the mouse. Doing so will also ease the inevitable debugging, by keeping it modular.
I'm almost there ... and should wrap up the slipstream module shortly. In the meantime, please use the "New and Improved" version HERE
. The slipstreaming algorythms have not changed.