RyanVM

after

http://greenmachine.msfnhosting.com/READING/addraid.htm

nLite can do this as well (automatically).

If you have a Promise 378 controller, it's currently unsupported by that pack. If you have an Asus motherboard, that's likely to be your problem.

Yes it would, but it should work. Actually, I think I know of a way you could do it so as to keep WHQL signing intact. What if you renamed the file during the compression stage? You would have the 376/378 folder and the fasttx2k folder with their identically named files in them. fasttx2k.sys would be compressed and copied from the fasttx2k folder. From the 376/378 folder, fasttx2k.sys would be compressed and named fast378.sy_ or something. Change the associated txtsetup.sif entries and you're golden. And since fast378.sys would only be used during textmode setup, the WHQL issue is resolved. And to clarify for others, dosnet.inf patching is only needed for those initiating setup via winnt32.exe (in other words, from a WinPE or DOS startup disk). And unfortunately, the idea above wouldn't work for dosnet patching (since dosnet uses all the files).

The problem with the Promise 378 (and 376) controller is that it appears to use the same fasttx2k drivers as the other Promise chipsets of that era, but they are NOT compatible. An easy workaround for you Promise 376/378 users (especially now that the driver pack does compression on the fly) would be to download the latest drivers from your manufacturer and replace the files in the Promise TX2K folder with those (all of them should overwrite). Next, replace the entries in Add_to_txtsetupsif.txt that reference fasttx2k with the PCI DeviceIDs with the ones from the INF file that you just downloaded from the manufacturer. That should take care of it (though be advised that your CD won't work with other Promise TX2K controllers at that point). The best long term solution I can think of would be to rename the Promise 378 driver to something like promise378.sys and change the entries in its INF file accordingly.

Microsoft said awhile ago that they weren't planning to release any future standalone versions of IE, though there's talk that that tune might be changing with IE7 (coming with Longhorn). In other words, don't hold your breath.

They can all go. It's easily verified simply by installing only SP2 and running WindowsUpdate. No hotfixes will come up

If I were you, I'd start a thread in the nLite forum so nuhi can answer directly. Odds are good it's just a missed setting or something.

jdeboeck's XP reduction batch files have the ability to decompress the driver cab files and combine them into one. Your best bet is still to have nLite do it for you, since driver.cab and sp2.cab both need to be decompressed, the nVidia driver files need to be deleted, references to the files need to be deleted from the proper XP setup files, then the drivers need to be recompressed into driver.cab. Seriously, you're far better off (and less likely to run into problems) just letting nLite do it for you.

No, it just tells setup not to prompt you about using unsigned drivers during hardware detection.

You can try using nLite to remove the nVidia drivers included with XP. It may be defaulting to them because they're digitally signed.

Intel has newer drivers out than what you appear to have in your pack. http://downloadfinder.intel.com/scripts-df...61&DwnldID=4233 9.0, 7/27/04

That is freakin' awesome, and it will be especially useful a year or so down the road after MS has released a couple bajillion updates .

Might I suggest that you have some kind of moderation system for it so junk switches (or dupes) get weeded out?

Does the integrate switch imply that hotfixes can be integrated into install CDs now or am I misreading that? I know the /integrate switch worked for slipstreaming SP2 in one step instead of two.

What does the CompressionMemory parameter do?

Why are only the Central European versions updated to 6.0.2?

It maintains the list of files that WFP protects. The hacked version removes Program Files folders from the list without removing earlier ones.

Try this: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Attachments] "SaveZoneInformation"=dword:00000001

I would tell that to them, personally. It's pretty irresponsible programming to have a program that only works with an outdated virtual machine.

I'm not seeing 9.0.1.1000 for *COUGH*purchase*COUGH* on any sites yet.

Just stick with the Sun Java VM. It's far more up to date, more stable, and more secure.

hehe, didn't realize it was case sensitive And for what it's worth, I would have attached it but it was too big 8)

Anybody try integrating .NET 2.0 Beta 1?