oao

wanna make sure I understand this correctly: 1. The zip file of TweakUI can be put in the Hotfix directory for regular integration by nLite? 2. As per a different thread, Silverlight can be put in \RunOnce and installed with the silverlight.exe /q silent install at nLite's RunOnce? Thanks.

Thanks. Is it nLite-able and in what section?

Thank you again, Kurt. Looks like the best way to do it for me is: 1. Use 5eraph's pack and add-ons for xp64 with IE8. 2. Use the wmp11 hotfixes in your list, as I usually run VLC for videos and Silverlight for Netflix. 3. Install only .NET 2. 4. Create a separate folder with the same structure as the one you set up, name it optional, and put in each of its subfolders the surplus of items that I leave out. Then, if I have to reinstall xp I will see which surplus items are requested by applications and integrate them in the next slipstreaming version. This way I can keep the system lean with a minimal hassle later on. 2 more questions: 1. Am I correct to assume that when you post updates, you modify the lists at the front of the guide? One doesn't read every update post and modify the list for himself, right? 2. Let's call the folder that contains SP2, Hotfix, etc SLIPSTREAM. Where should I put it for the nLite session? (Note that I won't use your procedure EXACTLY, just as a guide to the folder structure). Regards, FP

ok, thanks. i just wanted to make sure i inderstand correctly.

Thanks. I would like to offer the following thoughts: 1. The whole point of bothering with slipstreaming is to avoid as much as possible future problems or WU nags. If one goes through the hassle of learning and doing the work, it makes sense to include anything with the potential to prevent problems. So I like to add all fixes unless there is a good reason to avoid any. 2. Furthermore, another purpose of slipstreaming and keeping the OS source up to date is to ensure that the next OS reinstall will be as painless as possible. If I refrain from including some items and I am forced to add them manually later, it means that the source I have will cause me this hassle next time I have to reinstall it too. 3. The reality is that we cannot know at any point time what we will do on the computer and what optional fixes will prove necessary or not. Having said all that, I agree is that .NET 3.5 is awful bloat and I would prefer to avoid it. The thing is I can't even recall if any existing tasks require it and I sure as hell dk if and when MS and app developer will start requiring it. But that'll mean more hassle in the future, which is what slipstreaming is trying to prevent. So the choice is between possibly unnecessary bloat now and possible hassle later. Perhaps with powerful enough computers the bloat is not too bad? I wonder if anybody has a good sense of the effects of the bloat on a running system? Regarding the The C++ 2005, I was hoping that Kurt know and will say if it can be skipped given that the current version is C++ 2008. That leaves us with the directX. I'm not sure that it is needed for my tasks and what it does, but I would install it anyway if I didn't have to bother with a program other than nLite and I sure don't feel like figuring out how to do it in nLite. If anybody has the RunOnce code for it, I'll appreciate it. Regards, FP

Excuse me, but it was you who urged me to ask Aust HERE!!!! If you deem it necessary to delete the initial message, which you thought was in the wrong place, please feel free to do so. It was not my intention to duplicate and I did not know it was a problem. Incidentally, I made a slight change to one of the questions based on the reply I received to the first instance. Thanks.

The contents when using MS fixes are listed as: --------------------------- All of the following files are optional (except KB973525), like the optional files in the hotfix list above if you include them as directed then they will be installed. At \RunOnce for installation via nLite's RunOnce / batch files. % ▼ directx_aug2009_redist.exe 108,279,664 . . . MD5: 3F615F38FDC5EE3A8F142DC6F7594657 . . . SHA-1: 563B96A3D78D6038D10428F23954F083320B4019 @ . . . install_flash_player_ax.exe 1,956,528 Updated 8 Dec @ ▼ vcredist_x86.exe 2,745,256 Visual C++ 2005 SP1 32-bit @ ▼ vcredist_x64.exe 3,215,280 Visual C++ 2005 SP1 64-bit @ ▼ WindowsServer2003.WindowsXP-KB956744-x64-ENU.exe 4,044,672 MS09-044 - Remote Desktop Connection @ . . . WindowsServer2003.WindowsXP-KB973525-x64-ENU.exe 674,176 MS09-055 - ActiveX Kill Bits - Cumulative # ▼ WindowsUpdateAgent30-x64.exe 7,749,976 Updated (in this guide) 8 Dec --------------------------- The contents when using 5_eraph pack are listed as: ------------------------------ At \RunOnce: % ▼ directx_aug2009_redist.exe 108,279,664 . . . MD5: 3F615F38FDC5EE3A8F142DC6F7594657 . . . SHA-1: 563B96A3D78D6038D10428F23954F083320B4019 @ ▼ vcredist_x86.exe 2,745,256 Visual C++ 2005 SP1 32-bit @ ▼ vcredist_x64.exe 3,215,280 Visual C++ 2005 SP1 64-bit --------------------------------- I am using 5eraph's pack and need some clarifications: 1. Can I assume that some of the files are not used because they already are in the 5eraph pack? If not, why were they dropped? 2. Of those that remain, if I don't integrate them will I get bugged by Windows Update? 3. I notice that in my running system, which is up to date by Windows Update, there are no Visual C++ 2005 fixes. Instead I have only Visual C++ 2008 fixes, which I assume are in the 5eraph pack. So should I apply these? 4. I understand that these are not integrated as fixes by nLite except as switchess/unattended. Can they be integrated by Ryan's Integrator and, if so, before or after nLite? I hope I am not missing something here. Thanks.

Gee, I missed again. That was my intention.

Thanks, Martin. Unless I am mistaken MS does not have a page with an official list of all the fixes, categorized into optional or not -- right? If so this is amazing to me. That's why so many go thru the trouble to keep track of this and we end up with many understandable discrepancies. All this would go away if MS published one correct list, but hey, we all know MS. If nLite does not support them the question is whether they can be integrated before or after nLite with something else, say Ryan's Integrator.

Thanks. I am like you -- who knows when a problem will pop up; and getting bugged by Windows Update defeats the purpose of going through the hassle of slipstreaming, doesn't it? But I don't want to slipstream incorrectly -- I don't like discrepancies that I don't understand, so I need confirmation from knowledgeable people as to the source of such differences. (BTW, I was born in Bucharest, went to school there and left Romania in 1961. Since then I visited several times.)

Alas, that was a long time ago and I don't recall. The only thing I remember was that I was getting some errors and in searching online for a solution I came across it, installed it and the errors went away. Perhaps if you did a search by its name you may come across something that talks about that.

The contents when using MS fixes are listed as: --------------------------- All of the following files are optional (except KB973525), like the optional files in the hotfix list above if you include them as directed then they will be installed. At \RunOnce for installation via nLite's RunOnce / batch files. % ▼ directx_aug2009_redist.exe 108,279,664 . . . MD5: 3F615F38FDC5EE3A8F142DC6F7594657 . . . SHA-1: 563B96A3D78D6038D10428F23954F083320B4019 @ . . . install_flash_player_ax.exe 1,956,528 Updated 8 Dec @ ▼ vcredist_x86.exe 2,745,256 Visual C++ 2005 SP1 32-bit @ ▼ vcredist_x64.exe 3,215,280 Visual C++ 2005 SP1 64-bit @ ▼ WindowsServer2003.WindowsXP-KB956744-x64-ENU.exe 4,044,672 MS09-044 - Remote Desktop Connection @ . . . WindowsServer2003.WindowsXP-KB973525-x64-ENU.exe 674,176 MS09-055 - ActiveX Kill Bits - Cumulative # ▼ WindowsUpdateAgent30-x64.exe 7,749,976 Updated (in this guide) 8 Dec --------------------------- The contents when using 5_eraph pack are listed as: ------------------------------ At \RunOnce: % ▼ directx_aug2009_redist.exe 108,279,664 . . . MD5: 3F615F38FDC5EE3A8F142DC6F7594657 . . . SHA-1: 563B96A3D78D6038D10428F23954F083320B4019 @ ▼ vcredist_x86.exe 2,745,256 Visual C++ 2005 SP1 32-bit @ ▼ vcredist_x64.exe 3,215,280 Visual C++ 2005 SP1 64-bit --------------------------------- I am using 5eraph's pack and need some clarifications: 1. Can I assume that some of the files are not used because they already are in the 5eraph pack? If not, why were they dropped? 2. Of those that remain, if I don't integrate them will I get bugged by Windows Update? 3. I notice that in my running system, which is up to date by Windows Update, there are no Visual C++ 2005 fixes. Instead I have only Visual C++ 2008 fixes, which I assume are in the 5eraph pack. So should I apply these? 4. Must these fixes be in the RunOnce folder? Can't they be in the Hotfix folder? If not, can anybody provide the code for nLite? I hope I am not missing something here. Thanks.

The thing is I came up with a list based on Boooggy's x64 equivalents and it has 9 fixes more than Aust. If my list is correct, then it would mean that the 9 fixes are optional, hence they are not in Aust. That's quite possible, but it would be good to have either of them confirm this, just to be on the safe side.

WPI sounds interesting and I may wait for 8.0 to try on my applications, but not these small bits and pieces. Using it does have, however, some drawbacks and at this point I am spending already time and effort mastering the OS changes integration -- one thing at a time. I need to study Aust's guide more. Re UPHClean, it's hard to tell if it helps performance. I've been using it because some errors were generated in my event log and it got rid of them.

I do not integrate applications with nLite, but there is a bunch of MS programs/utils that I want to, as they are sort of extensions/fixes of XP64. I do not know whether they work with nLite and how -- e.g. what section. I looked around but have not seen any references. Here are the names, download URLs and file names. If anybody knows or can refer me to posted references, I would appreciate the information. ClearType Tuner PowerToy http://www.microsoft.com/typography/ClearTypePowerToy.mspx cleartype.exe Silverlight http://silverlight.net/getstarted/ Silverlight.exe SyncToy http://www.microsoft.com/Downloads/details...;displaylang=en SyncToySetupPackage_v21_x64.exe UPHClean v2.0 beta for 64 bit platform operating system http://blogs.technet.com/uphclean/pages/up...ta-for-x64.aspx uphclean-setup-x64-2-0-48.msi Windows Installer CleanUp Utility http://support.microsoft.com/kb/290301 msicuu2.exe This one was started by MS but not for XP64, so somebody picked it up and did it. TweakUI 64-Bit http://neosmart.net/dl.php?id=6 TweakUI_64Bit.msi Thanks.

Since boooggy does not provide a list of x64 fixes to slipstream, I went and searched Microsoft for all the x64 equivalents, going by their numbers. I found that all of them except 2 had x64 equivalents. however, I then read aust's page and he does not list 9 of those equivalents in his list. any idea why the discrepancy and should those additional hotfixes be ignored? Thanks.

No, but I looked systematically for all boooggy's x64 equivalent KBs and I found them with the exception of two. The question is why aren't they required by Aust? When Aust provides directory names to put files in, are they obligatory or discretionary? Thanks.

Yes, I finally figured out the Preset button a few minutes before I read your reply. Would have been better to name it Save. What is Tray button for? Where should I install the wmp11 slipstreamer -- anywhere? I noticed that boooggy has 9 more hotfixes on his wmp11 list than you -- any particular reasons you don't? Are there any of the directory names hardwired into nLite, or are they all at my discretion? Thanks.

The Intel site is one of the worst. When you search it it gives you either the wrong thing or not the most recent thing. I got an older utility than the one you refer to, hence I could not figure it out. Of course, I got that. It was just the version that I did not understand. Took me a bit to figure out what to extract. Regards, FP

Yes, OK, but when I searched the Intel download site for the driver it did not show me the one you mentioned. If it's the latest why didn't they post it? Where exactly did you get that version to .rar?

You are correct. Yes, xp64. However, see my question about the separation of some components -- should be OK but I would like it confirmed. And what about the ini saving i asked -- can you be more specific?

Thanks, Fernando. Yes, I know about the INF files -- I am referring to them as drivers because they represent the drivers to nLite. The message was written before I read your sticky. I was referred to it and it clarified most of the stuff for me. But I posted another message to your thread with some minor issues after I read the sticky -- can you pls reply? Regards, FP

I did. I don't see any prompt to save. I see only Back/Continue/Cancel, neither of which prompts me to give a name and save. Can you be more specific? I now see there was some confusion on my part regarding WMP11: I confused wmp with .net frame. According to your ini, WMP11 and its hotfixes go into Hotfix section, without the wmp11 slipstreamer. It is the .net frame which require RunOnce and special coding. Is there XP64 code available to use in nLite to integrate . net by nLite? I see some stuff on x86 but not x64.

Looks like DM works -- it did generate the folders. However, I see that it also generated separate folders for drivers that are included in other drivers and do not have to be inserted separately in nLite -- e.g. USB, PCI, LPC, SMBus. OTOH, it iput the Intel display card in an Intel chipset folder. Anybody knows if this is OK?

You mean within nLite, or manually as I described in my last message?