Acheron

**** placeholder ****

I have also tried to manually patch the files using dencorso's method. It resulted in the boot process getting stuck. Searching further I found the Chinese XP64G patch. I assumed it was only for Chinese or English systems, but it also seems to work just fine with other localized kernel files. The patch does not alter the ntoskrnl file directly, but creates a copy and adds a separate boot entry. Comparing the differences between methods I found that the Chinese patch also modifies the following bytes in hal.dll at 0x1DCFF: 10 68 00 00 00 01 53 C7 05 C4 32 02 80 40 00 00 00 BE 00 00 01to: 30 68 FF FF FF FF 53 C7 05 C4 32 02 80 00 40 00 00 BE 00 00 03

Unfortunately Windows XP by default has no mechanism to prevent file fragmentation when copying files. So if you move a lot of files most of them will become fragmented. You can defrag your drives often as a workaround for this problem. To prevent fragmentation there is AFAIK only one software solution on the market, called OptiWrite which is part of recent PerfectDisk versions. If you select this option in PerfectDisk it activates a file system filter driver which controls file placement when files are being copied. This does come with a cost. When this OptiWrite feature was first introduced in PerfectDisk 12 it was affecting system performance negatively. I recently tested PerfectDisk 13 performance. The general defragging speed of PerfectDisk 13 is still very slow, but the OptiWrite feature has improved. It is not perfect at preventing fragments, but it has some effect.

I have seen over the years different patches for syssetup.dll for Windows XP SP3 here and on ryanvm.net and most of them have some problems about driver warnings or breaking some functionality. Recently I replaced all of them with the patches published by Mr. Dusha on OSZone.net and have not had any problems since. http://forum.oszone.net/thread-119984.html. I had to register to download the files. The text file is very useful but despite its name does not contain all modifications made. Using the Fake Setup Advanced command line I was able to apply all the patches to syssetup.dll and setupapi.dll. Here's the complete list of patches and descriptions for Windows XP SP3. //=============// SETUPAPI.dll//=============//5.1.2600.5603 (KB948720)0001CD29: 74 EB // Disable DSP increase from 0 to 1,0001D509: 74 EB // if replaced SFC-protected signed driver00021B5F: 74 90 //00021B60: 0A 90 // Disable unsigned drivers decreasing rank00021B6E: 75 EB //000456A7: 74 EB // Disable error messages in Setupapi.log and pop-up driver install dialogs with patched syssetup.dll.....//5.1.2600.55120001CD29: 74 EB // Disable DSP increase from 0 to 1,0001D509: 74 EB // if replaced SFC-protected signed driver00021B7F: 74 90 //00021B80: 0A 90 // Disable unsigned drivers decreasing rank00021B8E: 75 EB //000456C7: 74 EB // Disable error messages in Setupapi.log and pop-up driver install dialogs with patched syssetup.dll.....//========================// SYSSETUP.dll PatchBlock//========================//5.1.2600.551200033B29: 73 EB // Disable Syssetup.inf protect 00033E00: 39 85 //00033E01: 5D DB // DefaultDrvSignPol = 0 (params in winnt.sif will be ignored)00033E02: 08 90 //000574FF: 74 90 // Disable OOBE00057500: 07 90 0005AB31: 6A EB // Disable SFC files scan in T-80005AB32: 46 0D ////===========// SFC_OS.dll//===========//5.1.2600.55120000EC87: 75: EB // SfcDisable=0xFFFFFF9D enable//=======================// UXTHEME.dll PatchBlock//=======================//6.0.2900.551200018727: 8B 33 //00018728: FF C0 //00018729: 55 C2 // Unsigned themes usage enable0001872A: 8B 04 //0001872B: EC 00 //

I have uploaded a new build of HFSLIP beta K v6 to fix a few path issues. I have also added a check to skip the integration of msdelta.dll included with WMP11 when this file is found in your SOURCE.

I use the following registry tweaks to prevent the CTFMON.exe process from running. ;Disable Advanded Text Services (Language bar)HKCU,"SOFTWARE\Microsoft\CTF","Disable Thread Input Manager",0x10001,1HKCU,"SOFTWARE\Microsoft\CTF\LangBar","DontShowCloseLangBarDlg",0x10001,1HKCU,"SOFTWARE\Microsoft\CTF\LangBar","ExtraIconsOnMinimized",0x10001,0HKCU,"SOFTWARE\Microsoft\CTF\LangBar","ShowStatus",0x10001,3HKCU,"SOFTWARE\Microsoft\CTF\MSUTB","ShowDeskBand",0x10001,0HKLM,"SOFTWARE\Microsoft\CTF\SystemShared","CUAS",0x10001,0You don't need the language bar to switch between keyboard layouts. Simply pressing ALT + SHIFT still works with these reg tweaks applied.

Jakson, at the moment my main OS is still Windows XP. So I was not aware of this problem you experience when running HFSLIP under a newer OS. I have merged some fixes from tomasz86, but these lines are new to me. Anway I have added them to beta K v6 now.

I have uploaded beta K v6 again to fix the logon issue caused by integrating a newer dpcdll.dll file.

Hi Jakson, unfortunately I can't help you with your problem. You might want to test installing these updates on a live system and try if you can reproduce the issue. I have uploaded HFSLIP beta K v6 which changes a lot of stuff regarding delayed file registration and commands run from the generated batch file inside the SVCPACK folder. For executing inf files from the SVCPACK directory the batch file is still generated. If you prefer not to have a batch file you can add your custom inf files to a new HFINFS folder within your project directory. These files will be copied to disk and launched from HFSLIPWU.INF.

Updated first post with beta K v5

I have a workaround included in HFSLIP 1.7.10 beta K http://www.msfn.org/board/topic/163230-new-hfslip-1710-beta-k-v4/

I think the problem is probably not a broken Windows Installer, but SNMSynth causing issues. At what moment are you installing .NET during setup? KB951847 will show up if you are installing .NET framework at logon as the Windows Update service will search for updates before launching the .NET installer and report the .NET framework is missing. You can workaround this by disabling the Windows Update service during setup and reenabling it again after you have installed the .NET framework. Another option is to install .NET framework at T13 using the SystemSetupInProgress registry tweak.

A lot of software now uses .NET Framework 4.0. As .NET 4.0 is independent of previous versions you can choose to only install the .NET 4.0 and remove .NET 2.0, 3.0 and 3.5 from your system. .NET 1.1 is legacy and I don't know of any recent software that needs it.

Just encountered this specific issue when I moved the .NET installer from GUIRUNONCE stage to T13 stage. The solution posted here has helped me find the problem, but did not solve it as on my system The Temporary Internet Files directory was already there inside the Local Service profile. The problem of the missing Temporary Internet Files directory is indeed caused by the Local Service profile being created too early. With an incomplete registry other problems might occur with other services. The solution of wiping the Local Service profile after the installation of the .NET Framework as suggested by Minkus will result in the Local Service profile being generated at the correct moment with all necessary registry entries.

I have uploaded beta K v4 which contains a few fixes from HFSLIP 2.0 branch. Another change is that the TEMP folder will not be removed anymore and recreated between each extracted update.

nuhi, despite these quirks nLite is still a great tool which has helped me get into the world of customizing Windows setups and slipstreaming updates. Recently I have worked on removing a lot of legacy stuff from Windows XP and nLite has helped me to get rid of most. However some component removal could be divided into subcomponents to remove more, without breaking functionality. Some things I would like to remove with nLite: OOBE mouse tutorial (You can remove OOBE, but not this subcompent) Windows Media Player 9 tour Animated screen characters Courtney and Earl The following files can be removed safely with no effect on any functionality: Windows Help directory: sniffpol.dll sstub.dll Search Assistant directory: msgr3en.dll nls302en.lex System32 pentnt.exe (floating point divide error report utility) write.exe (redirect to wordpad.exe) routemon.exe dvdupgrd.exe Another minor grief is that when you have removed all this stuff, you still get a lot of empty folders created on each install. To prevent creation of these folders you can comment out the corresponding lines in the [WinntDirectories] section of txtsetup.sif. Hopefully all of this gets implemented in next release.

I agree with Jaclaz that the current nLite tool has too many quirks when processing a modified source. My main complaint is that it modifies a lot of setup files to remove comments and white space on every run. This makes it harder to compare the differences when using version control to check what changes are made. I would like to have a detailed info tab in nLite which describes exactly what files are modified and why it is necessary to make those changes. It should also explain what nhelper.exe is doing and why it is added.

You should report this problem to the author of the software and maybe they'll fix it in an update.

August 2013 security updates for Windows XP: KB2862772 - MS13-059: Cumulative security update for Internet Explorer (supersedes KB2846071)KB2850869 - MS13-060: Vulnerability in Unicode Scripts Processor could allow remote code execution (supersedes KB981322)KB2849470 - MS13-062: Vulnerability in remote procedure call could allow elevation of privilege (supersedes KB2360937)KB2859537 - MS13-063: Vulnerabilities in Windows kernel could allow elevation of privilege (supersedes KB2839229)KB2863058 - August 2013 cumulative time zone update for Windows operating systems (supersedes KB2829069)KB890830 - Malicious Software Removal Tool v5.3For .NET Framework 2.0 the following update: KB2844285 - MS13-052: Vulnerabilities in .NET Framework could allow remote code execution (v2)and finally KB931125 - Update for Root Certificates [August 2013]

For processing of HTML characters I would choose to use regular expressions. You can use vbscript for this or any other scripting engine like perl or AutoIT. If you insist on using a batch file you better start writing the script from scratch. Copying from online examples can help you, but you need to understand each line of code.

You can use wimakcab.vbs to rebuild the msi installer. It is part of the Windows SDK: http://msdn.microsoft.com/en-us/library/windows/desktop/aa368616%28v=vs.85%29.aspx

I can confirm that KB2834886 completely replaces KB2659262. It is possible that multiple versions of dll files can coexist in the WinSXS folder and they can have different functionality. When an application tries to load a specific version of a dll Windows looks up the policy file in the Policies directory. This is the manifest file of KB2834886: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity type="win32-policy" name="policy.1.0.Microsoft.Windows.GdiPlus" version="1.0.6002.23084" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df"/> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.GdiPlus" processorArchitecture="x86"/> <bindingRedirect oldVersion="1.0.0.0-1.0.6002.23084" newVersion="1.0.6002.23084"/> </dependentAssembly> </dependency></assembly>The bindingRedirect shows that all previous versions of gdiplus.dll are replaced by this update.

For discussion of integrating addons I suggest you to open a new topic for it.

It is not a problem during setup and probably not a big deal after setup. Most people won't need SFC to be working anyway. But if you want system file protection enabled any modification to the layout.inf file will break it. At least on Windows XP SP3.

Just an issue I have when modifying layout.inf is that it breaks Windows System File Protection from asking for a CD. Even with a patched setupapi.dll when you run sfc /scannow Windows will not show any warnings, but instead error 0x00000490 Element not found will be written to the event log.