magic12kenneth

Blue, Do you use the DISM or PKRMGR tool to remove the packages or features in 7customizer 0.5? If I manually remove the packages using DISM first and then use 7customizer to integrate updates and hotfixes, it will still work? Ken

Is this compatible with Windows 7 SP1 MSDN? Ken

Thanks Skauneboy. After correcting that mistakes, everything works now. Now, if I can import the registry tweaks into the default profile. Any suggestions? Kenneth

For Windows XP Unattended, I use the same method as the link above. I find Windows 7 uses this two registry keys. First create a new user account. Logon to the new user account and create the quick launch toolbar on the taskbar. Use Regedit to export the two keys below. The final step is to use the autounattend.xml to import the registry tweak to the default profile. But I don't know how. Has anyone try it yet? [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\FolderDescriptions\{52a4f021-7b75-48a9-9f6b-4b87a210bc8f}] "Name"="Quick Launch" "Category"=dword:00000004 "Rela

Same here. I didn't like it very much. I know how to enable it manually but would love a way to automatic and put it in the unattended setup. Please keep us updated on your solution. Kenneth

Has anyone figure out a way to automatically enable the Quick Launch in Windows 7 using some registry tweaks and a dos batch or visual basic batch file to do it? Kenneth

Ahh... I somehow have missed that. I'll try again and see what happen. Thanks. Kenneth

Hi, I created a basic autounattend.xml for Windows 7 RC that works fine. But when I wanted to install some applications and some registry tweaks and use the FirstLogonCommands. Windows Setup install fine without any errors find in the setup logs. I tried severals times without any success. Nothing gets install. Can someone take a look at it and see what I'm doing wrong? I use this guide from this l Here my autounattend.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft

Smiley89, thanks for the hint. I'll take a look at it because I need it for using nLite. Kenneth

Smiley89, Using HFSLIP 2.0 alpha, did you place all the hotfixes in the HF except for the Windows Installer 4.5 (KB942288) and Time Zone (KB951072) in the HFSVCPACK_SW1 folder? EDIT: Also, did you use HFSLIP_POST_getnewfiles_v3.cmd in the HFTOOL folder? If so, did u get the NEWBIN.TXT created? I used it but it didn't create the NEWBIN.TXT. Thanks Kenneth

I like the 5th option much better because it's very simple and standard. That means, after I prepare my Windows XP source with nLite and DriverPack, I simply use your USB_Multiboot to format the USB drive and then select the XP source to copy to the USB without any modification. Boot PE from USB and run the a setupxp.cmd to start Windows XP Setup. Do you have a beta version out yet to test the option 5? Kenneth

I'm agree with you 100% on this feature request. It will save lots of time. Provided that it is easy for Nuhi to implement it. Another nice feature for request is to automatically shutdown the computer when vLite is done. That means, the user will setup all the settings including loading previous settings, pointing to the Vista Source (without copying files until the user finish setting up), etc.. It's like an unattended. This feature should also added to nLite too. Nuhi, what do you think? Is it doable and easy to implement? Just wondering. Kenneth