Tomcat76

For .NET 2.0, use Zxian's silent installer (English or multilingual)

It wasn't an error... Sorry. And like TommyP, I didn't experience an error integrating WMP10 either. The background music still ain't there, but no "syntax error" or anything like that. When is that error displayed, actually? Is that during T-13, while "Registering components"? I use these switches with cdimage: -h -n -m -o Open up a command prompt and navigate to a folder that contains cdimage. Then run cdimage /? and read the info. That's how I ended up using these switches...

I think I located it. I'm sending the correction to TommyP.

The Redist was released a day earlier. This topic is a bit confusing...

Unfortunately, it requires .NET Framework...

Uh... For HFSLIP, just take the Redist. Third title from the top. It's available in German. But hey... I'm in a good mood... http://www.microsoft.com/downloads/details...&displaylang=de

http://www.microsoft.com/downloads/Browse....rtCriteria=date Third title from the top (for now at least... )

Only the *d3dx9* files are of importance for the moment. These are used for the preprocessing of shaders and game developers are taking advantage of this already. The XInput technology doesn't seem to have as much impact for the moment. At least, noone here asked to include it yet citing "a game" that requires it. It's supposed to replace DirectInput in the long run. I don't know about the new file. It's another new thing, apparantly. Edit: just add in the Feb2006_d3dx9_29_x86.cab file; it's gonna be processed by HFSLIP.

Try this... Download the attached file and place it in the HFSLIP folder. Delete the SOURCESS folder. Run the file. This is gonna take a while. When it's finished, open up driver.cab (which will be in SOURCESS\I386) and see if the missing files are in there. Don't use this file on your CD. It only upgrades driver.cab to SP2 level; it doesn't contain the updates from the hotfixes. It's a test.

He means full slipstreaming with a command line is not possible. You can't completely slipstream it in the same way you'd slipstream a service pack. You can only use the /integrate switch which basically places it in the SVCPACK folder (like with a regular hotfix). HFSLIP gets around this by extracting the rollup and updating the source with the new files.

Again: you are not supposed to have any spx.cab files when choosing options A, B or C for the merging. So just don't think about it.When you run HFSLIP with that win51ic.SP2 tag file in the SOURCE folder, does driver.cab in SOURCESS\I386 finally contain the three missing files? Incidentally... Have you removed the read-only attribute off of every file and folder in the SOURCE folder after you copied them from the CD?

Where?

[Attachment removed] Like I said... that's the point of merging options A, B and C. In the code, haha.Download the attached file, place it in the HFSLIP folder and run it. Note what is echo'd on the screen and post back.

It's probably not related, but I see now that HFSLIP requires you to have the correct tag file in the root of the SOURCE folder. For Windows XP Home SP2, that would be "win51ic.SP2". Check that it's there...

That's the point of merging the cabs. Is it there in the SOURCE, and does that cab contain the three files you are missing? No. HFSLIP doesn't create a numbered cab file. If you choose merging option D, E or F, you do get an additional spx.cab file if required.

Which OS level is this? amdk7.sys and tunmp.sys are in sp1.cab and sp2.cab; mssmbios.sys exists only in SP2.cab.

The SPX.CAB section rewrite passed the test. I'll take a look at the section that handles options A/B/C now...

Which driver merging option are you choosing? I just finished rewriting the SPX.CAB section and am about to test it. If it works 100%, I'll pass it on to TommyP. So far, I never had a problem with A, B and C.

A little big problem. It had to be recalled. The next is gonna blow you away, haha. Edit: maybe not 100%. There's gonna be a little version in between...

The newest version of LegitCheckControl.cab doesn't contain GWFSPIDGen.dll anymore. HFSLIP had to be changed for that. As wela suggests, use a newer version of HFSLIP.

setupp.ini basically determines whether it's an OEM or a retail CD (or "corporate" if applicable). These require different keys.

/Q:A suppresses all messages and /R:N instructs the installer to never reboot. /R:N = never reboot /R:A = always reboot (showing prompt) /R:I = reboot if needed (showing prompt) /R:AS = always reboot silently (no prompt) /R:IS = reboot silently if needed (no prompt)

The *d3dx9* files can stay. Those contain the new dlls and they are processed by HFSLIP. You can leave Oct2005_xinput_x86.cab in if you want, but that one IS ignored...

HFSLIP is using boot.img for CDIMAGE and boot.bin for mkisofs. I suppose this could be changed to boot.bin for both programs since CDIMAGE supports both types. Also, bbie outputs bin files so it'll only make things easier.

You can just overwrite the existing ones in I386. If you want to let HFSLIP do it, the FIX folder is the way to go, yes.