RyanVM

That link says nothing about InstallShield files on the Windows XP CD...

HKCU entries have to be applied during the T12 (svcpack.inf, cmdlines.txt) stage for them to work properly. RunOnceEx is too late.

Windows setup doesn't do anything with InstallShield. The files are coming from something else you're installing from your CD.

There's a 9 page thread on the first (maybe second by this point) page of the unattended forum.

I also suggest you read the rules of the forum so your next post will hopefully better adhere to them. There's a link at the top of the page. Also, the unattended guide is in the middle of an overhaul at this point in time. Once that's completed, I think there will be more information on how to do things. That being said, start with the Beginning Users section of the current guide. Work your way through it so that you really understand the gist of what's going on (100% understanding isn't needed - even I'm not at that level ). Applications are under the Intermediate section, meaning you should have a fairly decent grasp of how unattended CDs work before you get into things like that. Above all, calling yourself an id*** or a n00b isn't going to get you anywhere. If you've got the desire to learn, you possess the ability to do so. Take it slow. Be deliberate. Have some confidence . We all had to start at the beginning - if we can do it, so can you!

Correct

You've got the basic idea. I actually do put the CAT files in the svcpack directory as well, though. Putting them there and adding their entries to svcpack.inf allows the updated files to be protected by Windows File Protection. It saves a ton of time and space, though, since it doesn't require any EXEs to be on the CD and run during Windows setup, which /integrate does still.

The directions on my site say specifically to delete __integrate.exe without running it if you've integrated 1.2.2b with nLite.

Nice program, thanks for the link.

By manual, do you mean /integrate? If so: # Direct integration means that all hotfixed files are integrated into your CD from the start. No need to worry about your computer being insecure in the time prior to the installation of hotfixes. # This pack requires little extra space on the CD, especially when compared to other integration methods.From the very top of http://ryanvm.msfn.org/updatepack.html

Because it's an update for OfficeXP, not Windows XP. Read the KB article, the file being updated doesn't even exist on the XP CD.

Viruses, spyware, etc. If you claim you aren't smart, I wouldn't wouldn't be surprised if you're a victim of them

The regsvr is to register the DLL with Windows.

The sticky lists all the currently available hotfixes on Windows Update for a fresh install. My package contains the most current files, no matter what hotfix they're from (official or unofficial).

Nice find. Is there an equivalent for Microsoft Update?

You're running the EXE without switches? I'm using the exact same EXE and it doesn't give any prompts...

Lots of ones that aren't available unless requested from MS. There's also a list of obsolete fixes on my site, and it's not hidden

I won't even mention my work to you

Like boooggy said, you need to add the entry to txtsetup.sif, not layout.inf (I'm surprised you could even edit layout.inf without Windows setup throwing a hissy fit at you). Now if you really want a challenge, integrate Microsoft Update and (the tricky part) get Tools...Windows Update to default to it (I haven't managed to figure that part out).

@eirogge: /integrate also (stupidly) replaces the CAB-compressed files on in i386 with uncompressed hotfixed versions. @Majoram: The two "hotfixes" you're adding to svcpack.inf aren't hotfixes, hence why they don't support integration. Neither is updating any files on the Windows installation. That being said, you should be OK running their EXEs from svcpack.inf. As for KB893066, are you using a hacked tcpip.sys by chance?

You're also going to be leaving behind unnecessary uninstall files (of course, to delete them you also have to remove the references to them in the MSI). Not doing so will only add to the size of the final EXE. @sleepnmojo - Actually, I don't anymore. I was running into some issues with the unofficial fixes, so I ended up nixing them outright. If anybody else wants to attempt it, though, I can send what I've got.

I bet you'll still have one set of entries remaining

...it's the regtweak that's the problem, not the DLL in my pack. And to answer your question, it's doable, but not easy.

Remove the regtweak enabling Copy To/Move To.

It sounds to me like your PC has other problems. Are you sure it's malware-free?