Explorer09

I think they should update tomorrow (or in a few hours). Adobe now follows Microsoft's Patch Tuesday for their Flash updates IIRC.

Only the latter (the file checker) is correct. The web page really misses the line about the reg file going to HFSVCPACK.

I knew the difference already, but you didn't notice that the new updroots.exe is bit-for-bit identical to the one inside the rvkroots.exe.

I think I should wait for a few days. MS didn't make an announcement about this update (yet). But, I can try installing it on a virtual machine and compare the difference. EDIT: Here is my brief compare result. (rootsupd.exe November 2012) In "HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates", 5 keys have been added by this update: 06143151E02B45DDBADD5D8E56530DAAE328CF90 0C628F5C5570B1C957FAFD383FB03D7B7DD7B9C6 585F7875BEE7433EB079EAAB7D05BB0F7AF2BCCC EABDA240440ABBD694930A01D09764C6C2D77966 F138A330A4EA986BEB520BB11035876EFB9D7F1C There are also 349 registry keys modified by this update in total: 342 keys in "HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates", 1 key in "HKLM\SOFTWARE\Microsoft\SystemCertificates\CA\Certificates", 6 keys in "HKLM\SOFTWARE\Microsoft\SystemCertificates\ROOT\Certificates". EDIT2: I found another strange thing. Perhaps this is a bug in Microsoft, but the file modified date inside rootsupd.exe seems to be misleading or incorrect. For example, between the April and the November update, only these files are changed: rootsupd.inf, updroots.exe, updroots.sst. But two of the modified dates stay the same. Files inside the new rootsupd.exe (November 2012): 05/31/2012 04:54 PM 91,136 ADVPACK.DLL 11/02/2012 02:24 PM 75,116 authroots.sst 08/29/2011 05:08 PM 16,562 delroots.sst 07/24/2012 03:44 PM 7,273 roots.sst 05/16/2011 03:16 PM 1,610 rootsupd.inf 06/01/2012 11:48 AM 6,656 updroots.exe 08/29/2011 05:08 PM 375,712 updroots.sst 05/31/2012 04:55 PM 2,272 W95INF16.DLL 05/31/2012 04:55 PM 4,608 W95INF32.DLL 9 File(s) 580,945 bytes Files inside the old rootsupd.exe (April 2012): 05/16/2011 02:52 PM 91,136 ADVPACK.DLL 04/06/2012 12:07 PM 75,116 authroots.sst 08/29/2011 05:08 PM 16,562 delroots.sst 03/14/2012 12:29 PM 7,273 roots.sst 05/16/2011 03:16 PM 1,610 rootsupd.inf 05/18/2011 02:01 PM 5,632 updroots.exe 08/29/2011 05:08 PM 368,180 updroots.sst 05/16/2011 02:53 PM 2,272 W95INF16.DLL 05/16/2011 02:53 PM 4,608 W95INF32.DLL 9 File(s) 572,389 bytes

Third revision. This time I changed many parts of the code to make it easy to add updates. And it now supports Japanese version of Windows XP/2003 x64. I hope I can support more languages, but except for English and Japanese, I don't know what to do. I don't have Server 2003 or any of its MUI packs.

@KapnJackSparrow So you meant Han characters (or CJK unified ideographs) in general, didn't you? I didn't use nLite to remove components so I cannot give you detailed instructions. But I can say that if you keep at least one East Asian language (Chinese, Japanese, Korean) installed. The Chinese characters will be displayed properly.

Yes it is. Don't remove it. Long answer: There are 4 fonts included in Windows XP disk that are used to display Chinese characters. MingLiU / PMingLiU (for Traditional Chinese) DFKai-SB (for Traditional Chinese; DFKai-SB is present only in Chinese Taiwan version of WinXP) SimSun (for Simplified Chinese) SimHei (for Simplified Chinese) If you want to support Chinese characters, you shouldn't remove these fonts. EDIT: Here are more fonts. These are for Han Characters in Japanese and Korean. Batang / Gungsuh (for Korean) Gulim / Dotum (for Korean) MS Gothic (for Japanese) MS Mincho (for Japanese) So, which one do you like? When you are speaking of Chinese characters you should say which Chinese you are referring to.

It's not just for file sharing, it's for code sharing. Some of the open-source software host their source code there. And people can make code commits or file bugs easily in GitHub.

I think it's time for Mimo to sign up an account in GitHub, and host the file-checker there. How would that be? At least for me, I can commit the code as soon as MS (and Adobe) release a new update, saving time for jvidal and other people.

Actually it's an update for Compatibility Pack. I mention that just for someone who has Compatibility Pack along with Office 2003.

November 2012 Patch Tuesday Windows XP 2727528 | MS12-072 | Windows Shell (synceng.dll) | x86:35624 x64:35688 | doesn't replace 2761226 | MS12-075 | Kernel-mode drivers (win32k.sys) | x86:35643 x64:35616 | replaces 2731847 (MS12-055) Malicious Software Removal Tool 4.14.6800.0 Office 2003 2687481 | MS12-076 | Excel | 35715 | replaces 2597086 2687311 | MS12-076 | Compatibility Pack (xlconv) | 35690 | replaces 2597162 2760492 | non-security | Junk Email Filter | 35691 | replaces old Junk Email Filter 2687403

Check your permissions of your HFSLIP folder right after you extract the hfslip_beta_Apr29_v10.zip. The problem should be there. Or check the permissions of your hfslip-1.7.10_beta_J_v10.cmd. As far as I know, your XP editions in SOURCE don't matter.

The "access denied" message appears when HFSLIP is trying to create temporary directories like "TEMP" and "WORK\I386E". I guess the reason is that when you unpack the HFSLIP, your unpacking program didn't set full folder permission for you. Perhaps you should check the permissions of your HFSLIP folder and make sure you have full control of it.

Correction. It's ECHO ON. Because I want to see which line of code produces that access denied message.

Ok, since I can't reproduce your problem on my side, can you do something for me so I can help you find your problem? First, open hfslip-1.7.10_beta_J_v10.cmd with a text editor, and find these lines: :HF1EXTRACT TITLE %T1% - Processing %HF% ECHO %HF% MD TEMP&START/WAIT HF\%HF% /Q /X:TEMP Add a command "ECHO ON" just after ECHO %HF%: :HF1EXTRACT TITLE %T1% - Processing %HF% ECHO %HF% ECHO ON MD TEMP&START/WAIT HF\%HF% /Q /X:TEMP Then, run the HFSLIP again and take a screenshot where you get the "Acceso denegado" message. Edit: Change ECHO OFF to ECHO ON. Thanks jvidal for pointing out.

Read my "EDIT:" part of my previous post. Because I didn't see any "access denied" message when I run hfslip under my Win7 (x64) computer. I suspect the reason you get "access denied" is because you didn't run HFSLIP in a folder with full privileges. Try running HFSLIP in your My Documents folder, and see if you have any problems.

Okay, I finally understood the code, and made a patch for it. Here it is: (in unified diff format) --- old/hfslip-1.7.10_beta_J_v10.cmd 2012-08-25 17:27:08.000000000 +0800 +++ new/hfslip-1.7.10_beta_J_v10.cmd 2012-11-04 23:39:23.343750000 +0800 @@ -2392,6 +2392,11 @@ ECHO>>WORK\HFSSDF.TXT MUAuth.cab=1&ECHO>>WORK\HFS_SOFTDIST.TXT AuthCabs\7971f918-a847-4430-9279-4a52d1efe18d\MUAuth.cab,MUAuth.cab ) ) +IF EXIST WORK\I386E\uiautomationcore.dll ( + REN "WORK\I386E\uiautomationcore.dll" uiacore.dll + ECHO>>SOURCESS\I386\TXTSETUP.SIF uiacore.dll = 1,,,,,,,2,0,0,uiautomationcore.dll&ECHO>>SOURCESS\I386\DOSNET.INF d1,uiacore.dll + ECHO>>WORK\HFSLIPCMDP1.TXT regsvr32.exe /s %%SYSTEMROOT%%\system32\uiautomationcore.dll +) IF EXIST WORK\I386E\updroots.exe ( IF EXIST WORK\I386E\authroots.sst ( REN WORK\I386E\authroots.sst authroot.sst For those who don't know what this patch does, here's some brief explanation: These 5 lines are going to be added in the :POSTHFX section of the HFSLIP. The :POSTHFX section includes rules to handle unusual MS updates and hotfixes. This section is run before HFSLIP copies the disc content from SOURCE to SOURCESS directory. These 5 new lines handles the special file "uiautomationcore.dll" by doing these: 1. Rename "uiautomationcore.dll" to "uiacore.dll" (see post #18 and #19 for why) 2. Write to TXTSETUP.SIF and DOSNET.INF to note the presence of "uiacore.dll". (The file does not exist in the original Win XP or 2003) 3. Add a command to run this during the Windows installation: regsvr32.exe /s %SYSTEMROOT%\system32\uiautomationcore.dll This line is in "WORK\HFSLIPCMDP1.TXT", which will be copied and appended to "SOURCESS\I386\SVCPACK\HFSLIP.CMD" at the later part of HFSLIP. Note: This patch does not work with KB2564958-x64 update! The update for x64 has additional files that needs to be handled, and I don't know how to write code for that. EDIT: Perhaps this one will work also: --- old/hfslip-1.7.10_beta_J_v10.cmd 2012-08-25 17:27:08.000000000 +0800 +++ new/hfslip-1.7.10_beta_J_v10.cmd 2012-11-05 08:45:29.953125000 +0800 @@ -2392,6 +2392,11 @@ ECHO>>WORK\HFSSDF.TXT MUAuth.cab=1&ECHO>>WORK\HFS_SOFTDIST.TXT AuthCabs\7971f918-a847-4430-9279-4a52d1efe18d\MUAuth.cab,MUAuth.cab ) ) +IF EXIST WORK\I386E\uiautomationcore.dll ( + REN "WORK\I386E\uiautomationcore.dll" uiacore.dll + ECHO>>SOURCESS\I386\TXTSETUP.SIF uiacore.dll = 1,,,,,,,2,0,0,uiautomationcore.dll&ECHO>>SOURCESS\I386\DOSNET.INF d1,uiacore.dll + ECHO>>WORK\NSFREGt.TXT uiautomationcore.dll +) IF EXIST WORK\I386E\updroots.exe ( IF EXIST WORK\I386E\authroots.sst ( REN WORK\I386E\authroots.sst authroot.sst

Am I too late to reply to these two posts? Anyway... But it's consistent. In general there is no uninstall-info or hotfix-info if you make a Windows-XP-CD with HFSLIP (or do I miss something?). So I would not prefer this but you could use a reg-file (in HFSVCPACK).Microsofts automatic update doesn't need this info for Windows XP (but they changed it a long time ago for Office 2003 - for Office 2003 this registry-info is needed now). Just for the info. The automatic update (and Windows Update too) in Windows XP (x86) needs only this info "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KBxxxxxxx","Installed" to see whether these updates are installed: KB961118, KB968389, KB2570947, KB2603381, KB2659262, KB2686509 For other updates, the "Installed" registry can be deleted without problems. In fact I do so in my slipstreamed disc. Does this work for this problem here? Without negative side effects?Is this (maybe with a further ini-section-name) also a solution for this: nLite misses a registry entry when integrating KB2641653 (XP x86) Yes, it will work without side effects. But it may cause a side effect if you apply this solution on my thread about KB2641653. The reason is that the KB2641653 case is a conditional AddReg entry.

BTW, I would like to write a patch to the HFSLIP code, but its coding style is so poor that I don't know where to patch.

The inf file in KB2564958 uses the abbreviation "UIACore". Perhaps we should rename to "UIACore.dll" instead of "uiaucore.dll"?

AFAIK, HFSLIP is not designed to slipstream stuff for Windows Vista or 7. EDIT: I misunderstood your problem. It seems what you want to do is slipstream updates for XP while the host OS is Win7. So... Try putting your updates and your XP disc files all in your My Documents folder (or its sub-folders). Did you try this?

The ISO files contains other files (for example "dotnetfx" and "support" directory) in addition to the "network install flavor of SP3". For beginners, I suggest that you not bother with the ISO version, because it's mostly useless to you.

That key is present in all of the crypt32.dll updates. AFAIK. In Vista/Win7 the certificates inside the updates are stored in your computer when you install the updates. This is what I can tell so far. I don't use Win7 often.

I hope this can save people's time. October 2012 Patch Tuesday Windows XP x64 KB2724197 | MS12-068 | Kernel | 34840 | (KB2731847 (win32k.sys) + KB2724197 (ntoskrnl.exe etc.) together replace KB2676562) KB2749655 | advisory | Wintrust.dll | 34877 | nothing replaced KB2705219-v2 | 30543 (same link as before) * KB2731847-v2 | 30605 (same link as before) * KB2661254-v2 | 30494 (same link as before) * KB2756822 | timezone | | 34911 | replaces KB2732052 KB890830 | MSRT v4.13.6701.0 | 9905 (same link as before) | replaces v4.12.6601.0 * : Microsoft just re-signed their updates with new certificates. The v2 version of these updates should replace their v1 versions.

May I summarize all of these? October 2012 Patch Tuesday Windows XP KB2724197 | MS12-068 | Kernel | 34845 | replaces KB2707511 (MS12-042) KB2749655 | advisory | Wintrust.dll | 34924 | nothing replaced KB2723135-v2 | 30590 (same link as before) * KB2705219-v2 | 30497 (same link as before) * KB2731847-v2 | 30564 (same link as before) * KB2661254-v2 | 30503 (same link as before) * KB2756822 | timezone | | 34931 | replaces KB2732052 KB890830 | MSRT v4.13.6701.0 | 16 (same link as before) | replaces v4.12.6601.0 * : Microsoft just re-signed their updates with new certificates. While the download link is the same as before, HFSLIPFC has to be aware of the v2 versions of these updates. Office 2003 KB2687483 | MS12-064 | Microsoft Word | 34882 | replaces KB2598332 (MS12-029) KB2687314 | MS12-064 | Word Converter (Compatibility Pack) | 34876 | replaces KB2596880 (MS12-029) EDIT: Today (2012-10-10) Microsoft adds the "validation required" thing to the download pages of these updates: KB2661254 KB2749655 KB2756822 Darn it!