RyanVM

I'm eventually going to make a 7zip SFX installer.

There are switches you can use to extract the EXE. Otherwise, there's a Driver folder in the directory you installed IAA4.5 to that has the drivers in it.

You can do that. However, the updated file won't be included in your installation source. That's not a big deal for the two updates so far, but it might be a bigger deal down the road when security updates start coming out. but will both approach have the same results when XP's installed? No, that's the POINT. The EXE will end up REPLACING the patched file you specifically put on the CD.

Is the error coming when the EXE tries to extract or when it tries to launch the MSI after extracting?

Things are looking very promising. However, my HighMAT tester went AWOL. Does anybody here use the HighMAT wizard?

At one point in Windows setup are you trying to install it?

When are you trying to install it?

You can do that. However, the updated file won't be included in your installation source. That's not a big deal for the two updates so far, but it might be a bigger deal down the road when security updates start coming out.

try renaming it to acrobat.msi and adjust config.txt accordingly. I'm wondering if StartX doesn't like two levels of quote marks.

if that works, I'm going to laugh

1.) Yes, the exe in the svcpack folder is the SAME file, just renamed 2.) Yes, you'll be replacing the file in i386 on your CD. The problem is that when KB884020.exe runs from svcpack.inf, it's going to overwrite your patched tcpip.sys which was copied from i386 with the unpatched version from the EXE. I've nearly got a solution for this problem ready to go, though

You've confirmed that the MSI works when called directly? Sounds like a corrupted MSI to me.

All you need to do is put in a registry entry for WindowsUpdate to ignore the GDI+ stuff. Exactly

Windows sets it up for you. You don't have to do anything. The point is that the updated file is integrated into the CD prior to hotfix installation, which is important for security fixes and stuff. ...for now

Using the /integrate flag creates a folder in your i386 directory called svcpack. Take a look inside

I haven't found any indication of any version above 9.0.1.1000. Any links to the patch?

*Nevermind, I can't read.* EDIT: But yes, I think the admin install point is considerably better than AutoIt.

yes, that should work (but I think the EXE will actually copy the old tcpip.sys back over when it runs from svcpack.inf - an annoying drawback...for now )

It matters very much. Report back when you've tested it.

Are you adding the registry entries during the svcpack.inf/cmdlines.txt stage or later?

Unless you've patched your file, it's 10

ahh, I get what you mean EDIT: Looking at txtsetup.oem for that, what's happening is that both nvatabus.sys and nvraid.sys are both being loaded (and both entries have "(required)" behind them) EDIT2: txtsetup.oem without all the commenting: [Disks] d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\ [Defaults] scsi = RAIDCLASS [scsi] RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)" BUSDRV = "NVIDIA NForce Storage Controller (required)" [Files.scsi.RAIDCLASS] driver = d1,nvraid.sys,RAIDCLASS inf = d1,nvraid.inf dll = d1,nvraidco.dll catalog = d1,nvraid.cat [Files.scsi.BUSDRV] driver = d1,nvatabus.sys,BUSDRV inf = d1, nvatabus.inf dll = d1,idecoi.dll catalog = d1, nvata.cat [Config.RAIDCLASS] [Config.BUSDRV] [HardwareIds.scsi.RAIDCLASS] id = "GenNvRaidDisk","nvraid" id = "*_NVRAIDBUS","nvraid" [HardwareIds.scsi.BUSDRV] id = "PCI\VEN_10DE&DEV_008E", "nvatabus" id = "PCI\VEN_10DE&DEV_0085", "nvatabus" id = "PCI\VEN_10DE&DEV_00D5", "nvatabus" id = "PCI\VEN_10DE&DEV_00EE", "nvatabus" id = "PCI\VEN_10DE&DEV_00E3", "nvatabus" id = "PCI\VEN_10DE&DEV_00E5", "nvatabus" id = "PCI\VEN_10DE&DEV_0035", "nvatabus" id = "PCI\VEN_10DE&DEV_0036", "nvatabus" id = "PCI\VEN_10DE&DEV_003E", "nvatabus" id = "PCI\VEN_10DE&DEV_0053", "nvatabus" id = "PCI\VEN_10DE&DEV_0054", "nvatabus" id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

My version is patched to allow 100 concurrent connections (from 10). Also, TCPIP.SY_ indicates that it's been compressed. You can't directly compare a .sy_ file to a .sys file. The EXE still needs to be run so that the necessary registry entries are created for the hotfixes (for now, anyway ) ModifyPE is only needed if you're modifying files in order to correct the CRC header. I'm pretty sure that Microsoft puts the correct checksums on their files . You can makecab the file if you want, it won't hurt anything.

1.) qchain isn't needed for post-SP2 hotfixes (heck, most post-SP1 hotfixes don't need it either) 2.) yes, moving them into svcpack is probably a good idea 3.) I've got something brewing (once I've tested it to satisfaction) which will greatly simplify all of this 3a.) With that said, if any of you guys actually use HighMAT (not just install it), please send me a PM so you can test some stuff for me. 3b.) Anybody know of a good way to verify that MSXML 4.0 SP2 is installed and working properly?

If slipstreaming drivers for MassStorage controllers you don't have was an issue, you'd be in a world of hurt. Ever notice all the RAID/SCSI controller drivers loaded by default at the beginning of textmode setup? All you're doing is adding one more.