Super-Magician

@Yzöwl, just a quick note. Since you have KB905474 in HF, you don't need LegitCheckControl.cab in your HFCABS folder (the hotfix contains the DLL). By the way, how fast is your processor? I can't believe you can run HFSLIP in only 7 minutes!

MS hotfixes and files contain a lot of junk and other useless binaries .

That was TommyP's writing. He's the one that has limited time - that's why Tomcat "took over"!@Tomcat, there are a few things to update in the main post of this topic. Specifically: There might be more, but I'm too lazy to post it .

Yup. No reason to leave the old file there.

@Tomcat76 Can you update your lists for the new Windows Script 5.6? scripten.exe (old version) is no longer available from Microsoft.

List updated. See changelog above.

Whoops! So sorry about my ignorance! Guess I should have done some research first !

Sorry, but although that URL leads us to an archive of the page, the actual file which the page links to does not exist. I think we would be better off with TAiN's link.

No, file not found errors are common. Nothing at all to worry about .

Help doesn't work because the actual help file doesn't exist. Siginet hasn't updated it in a while (last update I guess was for 1.0 RC5 or something). It will undoubtedly be packaged into the final RC8, but for now, the actual executable file contains only the program and does not extract anything (except writing a powpack.ini settings file). Sorry, I know I'm not Siginet, but I can still answer your questions. PowerPacker doesn't have the ability to detect the type of source you have, but in your case, you should select 'corporate'. It doesn't really matter for the actual packaging, but the options are there so that PowerPacker activates the correct sections in the boot menu files (it also tells the program what to name the folders). The RyanVM Integrator is maintained by RyanVM (big surprise !). It is not packaged into WXPP though, so yes, you need to download it separately. WXPP can in some way communicate with the RyanVM Integrator, but you need to wait for Siginet to explain this because I am not familiar with that portion of the program. Hope this helps !

@Tomcat, quick question: What exactly is the purpose of setting the variable 'BBIN' in the MAKEISO section (as in the following line)? The usage seems inconsistent because you switch between BOOT.BIN and %BBIN%. Plus, wouldn't it make more sense to do just SET BBIN=BOOT.INI in this line if you leave the variable?Just wondering...

One of these 'unrevealed' variables (if I am correct about the two that you are using) causes the WORK directory to remain.I prefer not to say which one because Tomcat does not want us to discuss it, but if I am right about the variables, you should be able to figure it out.

I don't think most users here would ever venture toward using Vista.

Actually, that was TommyP, just so you know .

We're getting there...I just encountered this today . Will test and report. Hopefully, the Extra Pack File function was fixed .

Sorry, zartrix, but I'm afraid you have to start all over again. HFSLIP only works with a clean source.

This seems to happen often with Win2000 Setup. I've encountered the error before too. Can you attach your HFSLIP.LOG file? Also, is SP4.CAB present in your SOURCE\I386 directory? Which driver compression method did you select?

We're already up to 60616b now .

Um, technically, the actual variable names are not case-sensitive. I tested this the other day.

This might be a possibility, but the INF file and commands in HFSLIP.CMD do not seem it could cause your problem.Can you upload your .NET 2.0 installer somewhere and let me take a look at it?

If you don't want the WGATray, then don't slipstream it. I doubt Tomcat would want to integrate a fix for turning off WGA Notifications (KB905474), but I could be wrong as we had a bit of a similar discussion about a week or so ago.

If anyone wants these, here are the MD5 checksums of all English Windows XP SP2 hotfixes/updates, placed in HF, as listed on Tomcat76's WinXP SP2 update page with all applicable options selected. *List updated on February 18, 2008* Recent revisions: 2008-02-18 • added KB931374, KB941644, KB942830, KB942831, KB943055, KB943485, IE7-KB944533, and KB946026 • removed KB917537, KB917953, KB921503, and IE7-KB942615 • updated KB890830 (Malicious Software Removal Tool) to v1.38 • new Roots Certificate Update Download checksum file (posted 02/18/2008): HF_XP_md5.zip b1cd797ab2abc148f0ae045c206250c7 *directx_nov2007_redist.exe ab7d089a6282c4bfce4bb3ebe26ce31d *IE7-WindowsXP-KB938127-x86-ENU.exe c257184a784f1e210869befbdf6d7b92 *IE7-WindowsXP-KB944533-x86-ENU.exe ea16789f6fc1d2523f704e8f9afbe906 *IE7-WindowsXP-x86-enu.exe e2bb0eb06f758845a07214227c6dd548 *msxml2sp6-kb887606-x86-enu.exe 4052b3f1d648d3e6cfce97aafd33789d *msxml4-KB941833-enu.exe 60dcb418e72d46fc0c26ebe8f3c0503e *msxml6-KB933579-enu-x86.exe 020ef20dd655f8992a64fbfc6f59ff90 *rootsupd.exe 59634478488ff2c6fac89c43dd20b867 *Windows-KB890830-V1.38.exe 8e3b8f909d86035edd516ef81b357326 *Windows-KB909520-v1.000-x86-ENU.exe 342f79337765760ad4e392eb67d5ed2c *WindowsInstaller-KB893803-v2-x86.exe f3191e8d5ecd92679b2993bc5089064a *WindowsMedia-KB911564-x86-ENU.exe a780de538c0360eabed54ed4dc4d9bdb *windowsmedia11-kb929399-v2-x86-intl.exe aa84bef31b902a419018656570e0f6f0 *WindowsMedia11-KB936782-x86-ENU.exe 78483f3595bf4b096e2d8e60190ef9ef *WindowsMedia11-KB939683-x86-ENU.exe 9dc5520df317c8e1a8c411edcf7fe609 *WindowsMedia6-KB925398-v2-x86-ENU.exe 16f9d1d66fde4b40b3c0980d9cd847e2 *WindowsRightsManagementServicesSP2-KB917275-Client-ENU-x86.exe 5401f801a74efa5cb8ca22fffad1cd8b *WindowsUpdateAgent30-x86.exe 7a2fa167dde4aef13de6660278ff0b45 *WindowsXP-KB873339-x86-ENU.exe 1dc8f64ea4ef88b519d0b5a9aff570da *WindowsXP-KB885836-x86-ENU.exe 8e216a152342bc90c4235f2fcfbdc1fd *WindowsXP-KB886185-x86-enu.exe 2af84b78ba17285bd1dd8511607c630e *WindowsXP-KB887472-x86-enu.exe 45eae1caf344f082807da4f1bd5bc953 *WindowsXP-KB888302-x86-ENU.exe e5d89f16540f70376ba3ec93dca30e33 *WindowsXP-KB890859-x86-ENU.exe 660a840382cb0b92de062e574479501c *WindowsXP-KB891781-x86-ENU.exe 467ce43c161268e9d21c447102ed0fa0 *WindowsXP-KB893756-x86-ENU.exe 61447e9a3747e4105e50b5985162ef4a *WindowsXP-KB896344-v2-x86-ENU.exe 48f0569f56b65bde6ea1dd608a73884b *WindowsXP-KB896358-x86-ENU.exe 0cf4c8399bace121ce41ec542f70aa63 *WindowsXP-KB896423-x86-ENU.exe ed4dcca17205c6a51fa3423c4ad77e41 *WindowsXP-KB896428-x86-ENU.exe 4f2794e0da1d033d68901db201789ce7 *WindowsXP-KB898461-x86-ENU.exe 4b49c6be714ed9ce43947144dd1f620d *WindowsXP-KB898543-v3-x86-ENU.exe b7fd05bbbc1a1eaa1b1f170d4d1731b5 *WindowsXP-KB899587-x86-ENU.exe 148c34207d40969c1fc05008ef86cfeb *WindowsXP-KB899591-x86-ENU.exe 89535dd99fa4967f11ae1b373cdeadb5 *WindowsXP-KB900485-v2-x86-ENU.exe 78efeb688354360f865d57fe64c0f9f1 *WindowsXP-KB900725-x86-ENU.exe 56c00bbdd9c97f782232dd5fe2602d66 *WindowsXP-KB901017-x86-ENU.exe 0b3ea6c1596a29173638efa2119844c5 *WindowsXP-KB901190-x86-ENU.exe 76b4fe62763af73b1b99807d982ee9d6 *WindowsXP-KB901214-x86-ENU.exe 38d14d171b5066ca53c8e387ad501eca *WindowsXP-KB904942-v2-x86-ENU.exe 368ee15b4790f90f15f963fc050dc359 *WindowsXP-KB905414-x86-ENU.exe 545466441acbe56e696f6ea8ee223bcb *WindowsXP-KB905474-ENU-x86-Standalone.exe 8244b747cd94faef913f2cb370ce4cdf *WindowsXP-KB905749-x86-ENU.exe b82592a7b82e201fb2df1b102eb70332 *WindowsXP-KB908519-x86-ENU.exe 2922afed8ffd5240ccce2b33e87fe664 *WindowsXP-KB908531-v2-x86-ENU.exe 139177af57add6f0370d149e401fe729 *WindowsXP-KB910437-x86-ENU.exe b163730a1b319f5bf64bd7e5ecd9c7c8 *WindowsXP-KB911280-v2-x86-ENU.exe f2a92739cdfc8d49fb49451a7a53cfcb *WindowsXP-KB911562-x86-ENU.exe ac2f6936ca5c08c4745e34a23ba4fc85 *WindowsXP-KB911927-x86-ENU.exe ad3424e21e8322249c76a33a781cffb6 *WindowsXP-KB912817-v2-x86-ENU.exe fc953b4cb6470a92765c153f328a2cae *WindowsXP-KB913580-x86-ENU.exe ffd8eeb4fb932297aac8dac86a3c1db3 *WindowsXP-KB914388-x86-ENU.exe 09da09a03889a01315e3358d8679ebd0 *WindowsXP-KB914389-x86-ENU.exe 2cdfba4082e86ff5b6f3bf666b53931f *WindowsXP-KB914440-v12-x86-ENU.exe d2138a11a36b620e8853c9d05d364b9b *WindowsXP-KB916595-x86-ENU.exe eca95e44467a1ae707d92c035f97af98 *WindowsXP-KB918118-x86-ENU.exe 51cdd5e3878eec1b0b415ac505e133d0 *WindowsXP-KB918439-x86-ENU.exe 4001f608fcecd45c6a251c010d657536 *WindowsXP-KB919007-x86-ENU.exe 629df3aeffffdac08fa353c62892a373 *WindowsXP-KB920213-x86-ENU.exe d07d6ba92c6f208104adeb6b3529dfad *WindowsXP-KB920342-x86-ENU.exe e8b626e3ffd65120610d6ad069cb0c63 *WindowsXP-KB920670-x86-ENU.exe 4c9411078b5df667890e98d25c4dbabc *WindowsXP-KB920683-x86-ENU.exe 4eeb6da87dc23abde735c98d3a7f8ed4 *WindowsXP-KB920685-x86-ENU.exe b65376a19595dde927182f4f681132b9 *WindowsXP-KB920872-x86-ENU.exe 4aab79324581490f1d263b9665ca78ff *WindowsXP-KB922582-x86-ENU.exe 97e886a6d909fd5d02bf81db15201aad *WindowsXP-KB922819-x86-ENU.exe ffab91ba8f874a1089c21c41d9794598 *WindowsXP-KB923191-x86-ENU.exe bb9c5427111db02f9367341b587a27c7 *WindowsXP-KB923414-x86-ENU.exe e6d6db414cab8926a1dacdc5ece9df8a *WindowsXP-KB923980-x86-ENU.exe 728dc1b651ae20dac7ed1dc49d5fd45a *WindowsXP-KB924270-x86-ENU.exe 72f091e15b9b7f09f8ddc0581388c6eb *WindowsXP-KB924667-x86-ENU.exe 6afc27a0b7871e4dae6e4c4014351bad *WindowsXP-KB925876-x86-ENU.exe 1ff4e2e41dd980dce30ad94220dfcc31 *WindowsXP-KB925902-x86-ENU.exe da3360a8e9077045613cddfddccb7cd5 *WindowsXP-KB926247-x86-ENU.exe 3084dfef0a1798a477e19e01fb2ca45a *WindowsXP-KB926255-x86-ENU.exe 37e1e1547dd8bd77565e7e1e2a6fe3ef *WindowsXP-KB926436-x86-ENU.exe 1365b78d3e1e1a3f70d22ca1723a5d08 *WindowsXP-KB927779-x86-ENU.exe 6a88825c5dcd22fcf042cd645c8e1739 *WindowsXP-KB927802-x86-ENU.exe adb6aa3190443232b2491160b587a6db *WindowsXP-KB927891-v3-x86-ENU.exe a270d50b21519688e6adc3eed180e9d2 *WindowsXP-KB928255-x86-ENU.exe 01783b48b99b6c99ddaadaf4d8c72545 *WindowsXP-KB929123-x86-ENU.exe 842622ce51c26a6cd7f0e79630fca3dd *WindowsXP-KB930178-x86-ENU.exe c2f12ad9606f6dc9b842620c3af5f5c3 *WindowsXP-KB930916-x86-ENU.exe 6baab30ac09bb2a2d056798b337db4b4 *WindowsXP-KB931261-x86-ENU.exe f0f5dcd73f885b5221d32fca5fb6502d *WindowsXP-KB931374-x86-ENU.exe 664f2beb0410896cefb715160c65d335 *WindowsXP-KB931784-x86-ENU.exe 50f6dc64b57d9c449ee3ac5e127f6d26 *WindowsXP-KB932168-x86-ENU.exe 09e45147f37509e6340f35e4625e8db4 *WindowsXP-KB933729-x86-ENU.exe 12f92378a8185377ae9e7143c8f5ba15 *WindowsXP-KB935448-x86-ENU.exe 679695ed907b03c002621ef986b13a3d *WindowsXP-KB935839-x86-ENU.exe 7b09c21d66d5d613df698c03497f6188 *WindowsXP-KB935840-x86-ENU.exe d28abcffd014654fe7a64831deef3a43 *WindowsXP-KB935843-x86-ENU.exe 2d99b9532977a7482d21e356060d596b *WindowsXP-KB936021-x86-ENU.exe 0d1e661223007dd7f941400f8f514fa6 *WindowsXP-KB936357-v2-x86-ENU.exe fa7fe55ecc3d32d717c685875371fbf2 *WindowsXP-KB937894-x86-ENU.exe a4573f48852305759964d53c3263f21c *WindowsXP-KB938828-x86-ENU.exe 866b98a2b134c5ccae7331ba3bba0c39 *WindowsXP-KB938829-x86-ENU.exe 55e4713ad10f721a8a1bdb8b0764469f *WindowsXP-KB939373-x86-ENU.exe b3f489284840ebea886cf60c55b49f3d *WindowsXP-KB941202-x86-ENU.exe 8fd8f62f768d969ca62f0a553d3ab7bc *WindowsXP-KB941568-x86-ENU.exe 085ad4b9ca30f39d67493800f74ce8c3 *WindowsXP-KB941569-x86-ENU.EXE 081114aea4a18646386767795b4e6ea1 *WindowsXP-KB941644-x86-ENU.exe 6f5fa7bdc4aabc2d9a675ad5f7d19fdf *WindowsXP-KB942830-x86-ENU.exe 42f8eb791b6a9977998b4c4cba1e43f5 *WindowsXP-KB942831-x86-ENU.exe 352636a43469e9c4ff1a8b5362a19ebf *WindowsXP-KB943055-x86-ENU.exe 8a95b39c895d6ee459dc2e3f2c497ec5 *WindowsXP-KB943460-x86-ENU.exe f34bafdf7edaa05c63e413266d024776 *WindowsXP-KB943485-x86-ENU.exe 01113aea9f275db8aa799710c91d4d8e *WindowsXP-KB944653-x86-ENU.exe 565d4ad776d1a87c8bc2823d84a3834c *WindowsXP-KB946026-x86-ENU.exe e03ce05a1fb25438ba03553f7ceb2f7f *wmp11-windowsxp-x86-enu.exe

IIRC, if you place the installation file for .NET 1.1, SP1 for that, and the KB886903 hotfix all in HF, HFSLIP will install them correctly. I am not sure why integrating .NET 2.0 would prevent .NET 1.1 from installing correctly.

Of course, make sure you also put LangPack.exe inside SOURCESS\I386\SVCPACK (this is where HFSLIP.CMD is located).

Since this is .NET 2.0, you need a special registry hack in order to install it via SVCPACK at T-13. I am sure you encountered information about this at some point during your search. Aaron Stebner's WebLog If you would like HFSLIP to automatically produce the needed INF file and command-line entries, rename your silent switchless installer (5Dotnet.exe) to dotnet2.exe (note: it must be named this in order to work) and move it to HF. Otherwise, you can either use the following (place the two files in HFSVCPACK) or create your own. 5Dotnet.cmd FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\I386\SVCPACK SET HFSLIP=%%i:\I386 %SYSTEMROOT%\SYSTEM32\rundll32.exe %SYSTEMROOT%\SYSTEM32\advpack.dll,LaunchINFSection %HFSLIP%\SVCPACK\DOTNET2.INF,DOTNETPRE START/WAIT %HFSLIP%\SVCPACK\5Dotnet.exe %SYSTEMROOT%\SYSTEM32\rundll32.exe %SYSTEMROOT%\SYSTEM32\advpack.dll,LaunchINFSection %HFSLIP%\SVCPACK\DOTNET2.INF,DOTNETPOST 5Dotnet.inf [Version] Signature="$WINDOWS NT$" [DOTNETPRE] DelReg=DelRegDN AddReg=AddRegDN [DOTNETPOST] AddReg=AddRegDNPost [DelRegDN] HKLM,"SOFTWARE\Microsoft\PCHealth\ErrorReporting\DW" [AddRegDN] HKLM,"SYSTEM\Setup","SystemSetupInProgress",0x10001,0 [AddRegDNPost] HKLM,"SYSTEM\Setup","SystemSetupInProgress",0x10001,1