Zamiel

Ok, thanks 5eraph. =)

I re-integrated those 3 updates into the same source and installed again. Now, Windows Update only shows as needing KB2862330. My hypothesis: nLite operates in such a fashion that it integrates hotfixes alphabetically. Thus, it tries to integrate "IE8-WindowsXP-KB2510531-x86-ENU.exe" and "IE8-WindowsXP-KB2879017-x86-ENU.exe" before "IE8-WindowsXP-x86-ENU.exe". In other words, it tries to integrate an IE8 hotfix before IE8 itself has been integrated. This is a bug - nLite should have some kind of logic to look for "IE8-WindowsXP-x86-ENU.exe" first before doing other IE8 related integrations. As for KB2862330, I don't know why it isn't working. Is anyone else having a problem integrating this particular hotfix with a stock XP?

- The SHA1 hash of my stock ISO is "66ac289ae27724c5ae17139227cbe78c01eefe40", which is the same as what is reported on TechNet. - I am using the latest version of nLite. - The files "IE8-WindowsXP-KB2879017-x86-ENU.exe", "WindowsXP-KB2862330-x86-ENU.exe", and "IE8-WindowsXP-KB2510531-x86-ENU.exe" appear to be properly downloaded by the UDC-10.08.13 tool. - The same 3 files are listed as being correctly integrated by nLite, with no errors. If it is something on my end, what else should I try checking? Re-integrate them again?

Hello. nuhi I am so glad you are back, nLite is one of my most favorite programs of all time. =) I am having problems integrating: 1) KB2879017 2) KB2862330 3) KB2510531 Maybe the updates are correctly integrating, but Windows Update doesn't properly recognize them. OR, they could not be integrating correctly. I am not sure. - Attached is a picture of what Windows Update reports upon first booting into the updated OS. - Also attached is my LAST_SESSION.INI from nLite. Steps that I took: 1) The original source is from en_windows_xp_professional_with_service_pack_3_x86_cd_vl_x14-73974.iso, directly from my MSDN Technet Subscription. 2) I used xdot's UDC-10.08.13 (found at http://xdot.tk/updates.html) to download all of the updates. 3) I put all the UDC files into nLite's hotfixes section, integrated them, then made a new ISO. Does anyone know if this is a bug in nLite or am I doing some step incorrectly? Thanks. LAST SESSION.INI

Blue, First of all, thanks so much for this product. I, and the rest of the world, look forward to this becoming a fully-functional replacement for vLite. Some changes that I would like to see: 1) For the unattended tab, have the "Time and Currency" option default to "English (United States)" instead of "Afrikaans (South Africa)". 2) For the unattended tab, have the "Keyboard Input" option default to "US" instead of "Albanian". 3) For the tweaks tab, under taskbar, add "Always show all icons and notifications in the taskbar". The associated registry key is: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\EnableAutoTray=0 4) Add some sort of option where we can give the installation manual registry tweaks via a .reg file, like nLite. Some issues that I am having: 1) The unattended file that 7Customizer is creating is bugged - it tells me that my (legitimate) CD-key is wrong and the setup automatically exits. 2) There is an issue with integrating Windows6.1-KB2479943-x64-RC. 7Customizer does not report any integration errors, but Windows Update still reports as needing the update. 3) There is an issue with integrating Windows6.1-KB2533552-x64. 7Customizer does not report any integration errors, but Windows Update still reports as needing the update. Thanks again. My log.txt:

Devs: For your reference, here is my exclude.txt: ntkrnlpa.ex_ ntkrpamp.ex_ Here is my hfslip.log This file is automatically generated by HFSLIP Use of HFSLIP for anything other than personal non-commercial purposes is strictly prohibited. Copyright(C) TommyP 2005-2009 ============================HOW TO REPORT A PROBLEM============================ If running into problems, refer to http://hfslip.org/support.html HFSLIP support forum: http://msfn.org/board/index.php?showforum=129 =============================================================================== Host OS - Windows XP HFSLIP Version - 1.7.9_beta_k, build 90419 HFSLIP Path - C:\Documents and Settings\Nesta\Desktop\hfslip_beta_Apr19\ OS in SOURCESS - Windows XP Professional SP3 English MSIE Version - MSIE7 Drivers - DRIVER.CAB Updated CD Install Path - Default CDTAG - WIN51 =============================================================================== Files in your HF folder: IE7-WindowsXP-KB938127-v2-x86-ENU.exe IE7-WindowsXP-KB958215-x86-ENU.exe IE7-WindowsXP-KB960714-x86-ENU.exe IE7-WindowsXP-KB963027-x86-ENU.exe IE7-WindowsXP-x86-enu.exe WindowsXP-KB923561-x86-ENU.exe WindowsXP-KB923789-x86-ENU.exe WindowsXP-KB938464-x86-ENU.exe WindowsXP-KB946648-x86-ENU.exe WindowsXP-KB950762-x86-ENU.exe WindowsXP-KB950974-x86-ENU.exe WindowsXP-KB951066-x86-ENU.exe WindowsXP-KB951376-v2-x86-ENU.exe WindowsXP-KB951698-x86-ENU.exe WindowsXP-KB951748-x86-ENU.exe WindowsXP-KB951978-x86-ENU.exe WindowsXP-KB952004-x86-ENU.exe WindowsXP-KB952287-x86-ENU.exe WindowsXP-KB952954-x86-ENU.exe WindowsXP-KB954211-x86-ENU.exe WindowsXP-KB954459-x86-ENU.exe WindowsXP-KB954600-x86-ENU.exe WindowsXP-KB955069-x86-ENU.exe WindowsXP-KB955839-x86-ENU.exe WindowsXP-KB956391-x86-ENU.exe WindowsXP-KB956572-x86-ENU.exe WindowsXP-KB956802-x86-ENU.exe WindowsXP-KB956803-x86-ENU.exe WindowsXP-KB956841-x86-ENU.exe WindowsXP-KB957097-x86-ENU.exe WindowsXP-KB958644-x86-ENU.exe WindowsXP-KB958687-x86-ENU.exe WindowsXP-KB958690-x86-ENU.exe WindowsXP-KB959426-x86-ENU.exe WindowsXP-KB960225-x86-ENU.exe WindowsXP-KB960715-x86-ENU.exe WindowsXP-KB960803-x86-ENU.exe WindowsXP-KB961373-x86-ENU.exe WindowsXP-KB967715-x86-ENU.exe WindowsXP-WindowsMedia-KB952069-v2-x86-ENU.exe Files in your HFCABS folder: wbemoc.cab Files in your HFGUIRUNONCE folder: Files in your HFSVCPACK folder: KB956391.reg Files in your HFSVCPACK_SW1 folder: Files in your HFSVCPACK_SW2 folder: Files in your HFTOOLS folder: boot.bin CDIMAGE.EXE Files in your REPLACE folder: =============================================================================== HFSLIP run time: 11m58s Hopefully this helps bring the beta one step closer to release. Thanks for all your hard work into HFSLIP!

Bump; where are you, unattended installation gurus? =p

Bump. Why isn't this simple feature been implemented into nLite?

The problem with nLite is that it does not include an option to automate the text-only part setup. (Side note: nuhi, please implement this!) I found the following add-on on the forums that accomplishes this. It works great with a Windows XP Professional installation. Entries_WINNT.SIF_Editor.ini: [general] builddate=2008/06/05 description=Edits WINNT.SIF. language=Multilanguage title=WINNT.SIF Editor version=1.0 website=http://www.msfn.org/board/cant-update-winntsif-via-nlite-t118718.html [ExtraFileEdits] WINNT.SIF|AutomaticUpdates="Yes"<NEXT>Autopartition=0|AutomaticUpdates="Yes"<NEXT>; Autopartition=1|1 [EditFile] WINNT.SIF,Unattended,AddRepartition [AddRepartition] Repartition = Yes When I use this add-on with a Windows Server 2003 Enterprise source, it doesn't work. In a nutshell, why? Help! =)

Hey man, I am a longtime user of hfslip (for several years now). And I have always loved it to pieces. And I still do. Thank you for the tremendous amount of work you put into this project. I appreciate it with all my heart. Every time I use hfslip I tingle with joy. Uh, that's all. Donation inc!

Yes. =) I'm aware that the message is bogus and that I should hit no; the bug lies in the fact that I have to click no a hundred times a day. =p

After experimenting a bit with nLite over a year ago, I've found the biggest bug with it is still present today in 1.21. For Windows XP Pro Corp (w/ SP2), upon every driver install, (for example, plugging in a USB thumbdrive for the first time) Windows will prompt you to insert the Windows CD to replace altered system files. This shouldn't happen. This isn't a new problem either; this has been a part of nLite for a long time and there is more than one thread covering it. However, they seem to lack any current information. 1) This bug isn't happening to just me, right? 2) I haven't done extensive testing with this version of nLite yet, but it is my understanding that this bug will occur whether you completely motify the OS or hardly do anything with nLite at all. Is this correct? 3) Any word from nuhi as to when it will be fixed? 4) I don't like the idea of disabling it, but I assume this is the easiest workaround. How would I go about removing WFP using nLite itself? 5) Are there any other options? I know about the editing of that one registry entry; it doesn't work for me.