RyanVM

And of course, installation order shouldn't really matter at all since all current hotfixes theoretically have qchain functionality built into them anyway.

Thanks jrzycrim, I found what I was looking for in one of the docs. Below is code for a batch script which will automatically compress all .SYS files in a directory into .SY_ files with LZX compression. One caveat, it only works if the path has no spaces in it. If you can figure out a way around that, let me know. @echo off rem Compressing Driversfor /f %%i in ('dir *.sys /b /s') do makecab /D CompressionType=LZX "%%i"

Exactly what I was getting at.

Think about that for a second. When it installs the service pack, it backs up the CURRENT files being replaced. Where would it get the SP1 files from to backup? No, it won't work. And repairing the installation won't work either, you'll end up with setup freezing at the 39min mark of graphical setup. The only way to go back to SP1 is a format and reinstall.

You're probably going to want to use a method similar to what gosh outlines on his page. http://gosh.msfnhosting.com/part1.htm

What he suggested would work in my case most likely, but yeah, it wouldn't work if you truly needed it to run in full compatibility mode to install correctly.

Bueller?

Anybody?

My bug report has officially been closed as a duplicate. It was an issue with volume license keys and the status already says fixed. So at least the next build should work OK (though I'll be trying new builds in VirtualPC first from now on )

Theoretically all my pack does is automate GM's method. Any info you can provide about what you did to make a problem go away would be nice. Also, did you try the version with the batch file which patches txtsetup.sif automatically?

Two things: first, WTF is Web Folders anyway? I've seen it in the Uninstall section but never known what it actually does. Second, is there an INF file that can be edited so it's never installed in the first place (and by extension, a list of files that can be deleted from the XP CD).

The only time I've run into a program that doesn't go away after deleting it's uninstall registry key was the HighMAT Support hotfix from Microsoft. Looks like I just found out how to ditch it, thanks!

Well, it happens with slipstreamed copies as well. I get this error message when trying to log on for the first time: So yeah, something is nicely fubared with this build . And I too can confirm that this only happens with Volume License builds. I was able to slipstream it fine on a retail XP Pro CD.

Nice, thanks for the link.

VirtualPC is the plan. I bet I was right when I told MS that I was betting they'd be getting a lot more phone calls on that matter soon

I've had rather spotty results extracting to a temp folder. I've had more than one occasion where the files get deleted before setup is finished. Rather annoying

I've been attempting to hack sfc_os.dll lately and have been having a hard time finding out what to change. I want to do it to the version from the latest beta release, build 2120 (post-RC1). According to this thread, the value needing to be changed has changed. Unfortunately, build 2120 doesn't have this value at that offset and there's eleventy billion instances of 33C0 in the file. How does one go about knowing which one is the correct one to change?

I've noticed that the makecab utility doesn't use LZH compression by default (which usually get's an extra 15-20% off the size of the file). I saw in jdeboeck's batch files how he uses a DDF file to enable LZH when recompressing drivers.cab. I want to adapt that for a different purpose. I want to script cab-ifying (I love making up words ) all the files in a directory, but as individual .DL_ or .SY_ files rather than as one giant CAB file. This would be pretty easy if there were a command line option for enabling LZH compression, but I haven't found it yet. Anybody have an idea how to accomplish this?

I was going to test slipstreaming 2120 directly onto a VL install today just to see what happens - sound like it's a waste of time?

Apparently I wasn't the only one then

For the record, if you do this with a CD drive, the path is a really weird format (not just D:\blah.exe). Instead, it looks like this: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]"SIGN=444651F lv5\\installer\\disk1\\SETUP.EXE"="NT4SP5"

Meh, I'm content waiting for SP2 to go final before I start integrating hotfixes into it . Especially because a new build has already been released to testers (such as myself) - 2120. Of course, upgrading that on my laptop resulted in a dead machine (see my other thread in the WindowsXP forum), but that's another story altogether

Yes

Try this line under [sourceDisksFiles]: viasraid.sys = 1,,,,,,4_,4,1,,,1,4 Also, make sure you have the path to the driver defined in the OEMPnPDrivers key of winnt.sif. If all else fails, the pack I created (linked in my sig or the pinned thread) has support for that controller and automatically patches txtsetup.sif properly.

Works like a charm! I tested it on both Virtual PC and on a freshly formatted separate computer.