oao

Most of the XP64 drivers for my laptop must be extracted from executable archives distributed by the mfgrs and this makes it unclear how to select the proper driver for nLite to integrate. 1. Multiple INF files for one driver in the same directory e.g. Intel® Matrix Storage Manager Driver: it has IASTOR.INF and IAHCI.INF in the same directory, both of which I think are needed. If I specify One Driver to Insert I must choose one of them and then I DK if the other will be installed; if I try to select the other one too, nLite does not accept it from the same directory. So should I specify Multiple Drivers to insure both will be included? 2. One driver with multiple files in different directories e.g. nVidia graphics driver: it has the INF of the core driver in one directory and an INF for a HDMI driver in ahanother directory. Here my guess is that I need to specify each directory as one driver and insert them separately, as I doubt the graphics driver will also include the HDMI. 3. Multiple INFs for multiple drivers in the same directory e.g. Intel Mobile Chipset. Here there is a double problem: there are multiple INF files for the same chipset family all of which must be installed and multiple INF files for other chipset families none of which must be installed. The thing is I cannot tell from the names of the files which should be in and which out. So if I specify One-Driver to Insert, I don't know which INFs to select. But if I specify Multiple Drivers, all of them will be selected and I dk is that's correct -- would they all be installed? Would appreciate advice from those in the know. Thanks.

Who is this question addressed to? If it is Fernando 1, then please place a reply in his thread.Ah, OK, will do. Yes and I replied to it. Thanks.

Good idea. I'll check it out, thanks. Hope the Lite version will do.

Ah, well, that's life. Too bad. What I am talking about is: 1. The ability to specify the ini file in multiple sessions rather than in one, and process only after it's all specified. 2. Producing a new XP64 CD after enough new changes have occurred without respecifying everything from scratch. Thus if I ever need to reinstall XP I don't gave to install from an old nlited CD and apply post-CD changes manually: i specify only the changes and nlite produces a revised ini file. Since the ini file is produced by nlite in one session and after the full specification, neither is possible via nlite. If so, the only way is to first fully specify an ini file and apply it in one session so as to produce a full ini file, then each subsequent time edit the ini file manually to reflect changes, import it and process. What I wanted to do but can't is avoid (a) the first full specification IN ONE STAGE (b) subsequent MANUAL edits to the ini file, which are riskier. afaicr I have not seen any reference that says wmp11 slipstreamer itself can be input into nlite, but if you say you do it i'll take your word for it. i suggest a note should be added to aust's guide where appropriate to let people know it's possible to do it that way too (and how). thanks and best regards, FP

I checked out SATA sticky. I have a Gateway T-6836 laptop which came with Vista32 and I upgraded to XP64. There are no XP64 drivers for it, so I installed XP64 with integrated drivers that I collected from various sources. Some I extracted from Intel's self-executable archives: The specs say: chipset: Intel GM965 Display: Intel X3100 but do not say whether the SATA controller is a ICH8 or ICH8M. When I integrated the drivers, the OS installed the driver for ICH8M, so I assume that's it. Regarding the chipset: 1. The specs say it's a GM965. Note, however, that the .rar archive you made available has inf files for 965m and 965g; the only gm is for the 945gm. This may not matter, though, as the OS will install the correct one. 2. The latest version downloadable from Intel is 9.1.0.12 dated 2/2/2009. The label on the .rar you made available is 9.1.1.1025 -- newer than Intel's, but the inf files inside say they are older versions from 2007 and 2008. What gives? 3. If the .rar is newer I would want to install it instead of Intel's, but I can only integrate it into my next XP64 CD. To update my running system I would need an executable, which the RAR isn't.

I have already put all driver folders in one folder, but I think pointing to that folder won't pick up the inf files. I think you have to point to each driver folder separately, because they include the infs. But I'll check it out. If only the proper drivers will be installed and if multiple inf drivers will take care of each other, one can specify all of them and not worry about it. I sort of guessed that is the case, but wanted to make sure. In fact my graphics card is Intel's, not nVidia's. I guessed that if they put the HDMI files in a different directory than the card driver's directory, then the latter would not install the latter, so they must be specified separately. I will take a look at the stickies. Thanks.

There is no need to test, yes, the INI file is generated at the end of specs, which means that I cannot add to or change specs before I integrate. More than once it happened that I started specifying and I reached a point where I could not continue without further research. So I needed to put the operation on hold, figure things out, then continue, sometimes later or the next day, etc. One cannot do this -- one must lose all specs and start from scratch. Since the full specs process is long and rather tedious, repeating it more than once can drive one nuts. Hence the need for partial saves/alterations. Regarding Aust, yes, there is no need to save the INI file after a SP run -- that's trivial, because then the process is short and simple. I was responding to the argument that one should ALWAYS start with a clean source -- in that case one starts with a source which was already modified with SP and WMP11 Slipstreamer. As far as I know the WMP fixes must be set in RunOnce mode and one must learn how to do that, which I don't care for. So Aust's way is much easier for me. I reiterate: I don't want or need to APPLY integration in stages; I want to SPECIFY the integration in stages. If the INI files were created during the specs and not at integration time, it would make life easier for reasons I specified above. What I am saying is a future improvement.

Most of the XP64 drivers for my laptop must be extracted from executable archives distributed by the mfgrs and this makes it unclear how to select the proper driver for nLite to integrate. 1. Multiple INF files for one driver in the same directory e.g. Intel® Matrix Storage Manager Driver: it has IASTOR.INF and IAHCI.INF in the same directory, both of which I think are needed. If I specify One Driver to Insert I must choose one of them and then I DK if the other will be installed; if I try to select the other one too, nLite does not accept it from the same directory. So should I specify Multiple Drivers to insure both will be included? 2. One driver with multiple files in different directories e.g. nVidia graphics driver: it has the INF of the core driver in one directory and an INF for a HDMI driver in ahanother directory. Here my guess is that I need to specify each directory as one driver and insert them separately, as I doubt the graphics driver will also include the HDMI. 3. Multiple INFs for multiple drivers in the same directory e.g. Intel Mobile Chipset. Here there is a double problem: there are multiple INF files for the same chipset family all of which must be installed and multiple INF files for other chipset families none of which must be installed. The thing is I cannot tell from the names of the files which should be in and which out. So if I specify One-Driver to Insert, I don't know which INFs to select. But if I specify Multiple Drivers, all of them will be selected and I dk is that's correct -- would they all be installed? Would appreciate advice from those in the know. Thanks.

So there are 2 issues here: 1. Let's suppose I created a CD earlier and since then there have been some new hotfixes/packs and the drivers were updated. I would start with a set of clean install files from the MS CD, but I don't want to respecify EVERYTHING I specified last time, but rather alter the previous INI files to reflect just the new changes, then reapply the whole shabang to the the original install. 2. I want to keep modifying an INI file until such time as I am ready to apply it to the install files.

I am not sure I was understood correctly. I don't want to APPLY the changes in several steps. I want to SPECIFY THE CHANGES in several steps, So not starting with a clean source is not an issue. For example, let's say I start with a clean source and specify the hot fixes only, then without processing get out; next day I want to specify the drivers and get out, without processing; so I want to start with the hotfixes already specified. And so on, until I specified everything and THEN APPLY the changes. The reason is that specifying all the changes at once takes too much time and is tedious. There should be a way to have the new specs each time I exit, until such time as all the specs are in and I apply the changes to the file. IOW, the INI files should be created cumulatively and the changes applied only when I choose to do so. Isn't that how it actually works? In fact, I've seen instructions somewhare (Aust?) to apply SP2 in one session, get out, install and apply hotfixes to WMP11 with WMP11 Slipstreamer, then go back and apply the hotfixes, drivers and tweaks. If so, then the second session starts with a source to which SP2 and WMPII were already applied, which you say should not be done. Are those instructions wrong?

I need some clarifications on last session settings: I am running nlite from my hard disk with everything else on a USB hard drive. I want to do the whole process in several steps and I want the info input in each step to be saved for the next until the CD is ready, then save the whole thing for when and if I may need to create the CD again. 1. My understanding was that the INI files are created where the Windows source (target) resides. But when I put earlier copies there, they don't come up for loading when I run nLite. It appears only in the Presets directory they are recognized. Is this how it's supposed to work? 2. If I do certain parts but then I get out, the new input is not being saved to be available when I continue. Thus, if I use a saved previous INI, when I exist the program, the INI remains unchanged and I lose the new input. How do I insure that new changes are added to the old changes? Thanks.

I have renamed the IE8Tweaks.ini file without entries and 7z'ed it and yet nLite rejects it: I get Unsupported file.

Thanks. I obtained my list of fixes from merging together the list given by Aust and by boooggy, so it's not clear why I had wrong ones and missing ones. Anyway, I made the changes and it worked.

I am using WMP11 Slipstreamer in XP64 to integrate into xp64 CD and have run into the following problem. Pls advise. Thanks. WMP11Slipstreamer v1.4.2.0 Detected source: Windows™ XP Professional x64 SP2 Hotfixes: WindowsServer2003.WindowsXP-KB973540-x64-ENU.exe windowsmedia11-kb928788-x64-intl.exe windowsmedia11-kb929399-v2-x64-intl.exe windowsmedia11-kb929773-x64-intl.exe windowsmedia11-kb932390-x64-intl.exe windowsmedia11-kb933547-x64-intl.exe windowsmedia11-kb935551-x64-intl.exe windowsmedia11-kb935552-x64-intl.exe windowsmedia11-kb939209-x64-intl.exe WindowsMedia11-KB939683-x64-ENU.exe WindowsMedia11-KB941569-x64-ENU.exe windowsmedia11-kb944882-x64-intl.exe WindowsMedia11-KB952069-x64-ENU.exe windowsmedia11-kb954067-x64-intl.exe windowsmedia11-kb954069-x64-intl.exe WindowsMedia11-KB954154-x64-ENU.exe WindowsMedia11-KB968816-x64-ENU.exe WindowsServer2003.WindowsXP-KB941569-x64-ENU.exe WindowsServer2003.WindowsXP-KB954155-x64-ENU.exe Epsilon.Parsers.IniParser+Exceptions+KeyNotFoundException: The section does not contain this key or line. at Epsilon.WMP11Slipstreamer.Backend.StandardHotfixApply(String fixesFolder) at Epsilon.WMP11Slipstreamer.Backend.ApplyFixes() at Epsilon.Slipstreamers.SlipstreamerBase.Slipstream() at Epsilon.WMP11Slipstreamer.MainForm.WorkerMethod(Object workerParam) Extra error information: Section: Strings Key: US_PRODUCT_NAME Identifier: Update_SP2QFE.inf Offending hotfix: WindowsServer2003.WindowsXP-KB973540-x64-ENU.exe The source has not been corrupted. All changes have been successfully undone.

OK, thanks. Now, if I always run as Administrator, should I just delete all the material referring to access or do I have to modify anything?

Thanks for the info, will look into using this guide then. Looks like I posted my question in the wrong place, so let me repost it here. The survey seems to indicate that others have used the guide on XP32, so it must have worked. Before I go study the guide in detail, do I take you to mean that the attached files you list upfront to download, and which have xp64 names will work AS IS (except for the timeout) as long as one uses the appropriate xp32 packs, add-ons, etc? Or does one need to modify them? What about the directories it creates? Also, can one create the xp32 CD on a XP64 system, or must one do it on a xp32 system? Thanks.

I see that others report they have used the guide on XP32 so it must be possible. Before I go and read the guide in detail, do I take you to mean that the upfront files you list to download which have x64 names can be used AS IS (with exception of timeout) for XP32? Also, can the guide be used on a XP4 system to create a XP32 CD, or must it be used on a XP32 platform? Thanks.

Has anybody experienced any problems after the last batch of patches? Rebooting after the update the system won't respond to mouse. After a while it complains of insufficient memory and I could not even get the Task Manager to pop up. After a while I get a message of insufficient memory and that the system will increase the pagefile. When finally the Task Manager pops i see that the RAM is all used (4GB!!!!) and the peak memory of services. exe is 3+GB. I also noticed that Avira anti-virus gets stuck at startup and does not load. It's difficult to even bring up msconfig to deactivate all startup apps to try and investigate if either effects the problem. Sometimes rebooting prompts me to boot the last valid configuration. when I do the system runs ok but when i reboot the problem reappears. any ideas?

Thanks. That auto restart is NOT checked. I retried the slipstreaming and monitored the tasks and apparently nLite choked on the SP1 of net frame 2. I forgot that the net frame install already contained 3.5 so my guess is it would not apply SP1 to a prior version. But it should not have rebooted the 1st time. That's why I think a log file would be useful.

During the integration of .NET Frame 2.0 the system rebooted. There was no error message and as far as I can tell nLite does not keep a log so I cannot tell the exact task it was doing. Any ideas? If I try a 3rd time is there anyway that I can generate a log that can trace the tasks?

john, The question is if I keep the feature out if I eliminate the lockout. Chances are not. As to drivers I'll just install all.

1. That was a good guess about KB's. I found KB911164 in the AMD64 folder. Google came up with this thread: http://forums.microsoft.com/TechNet/ShowPo...6&SiteID=17 Turns out that nLite is aware of it and it offers to roll it back, which seems to be the right course. 2. Regarding the drivers: I sort of assumed the same -- that as long as the drivers are all x64, it does not matter that you specify All, but I was not sure. But it's rather tricky. Some have folders with multiple INF's and the structure and naming of folders does not say whether they are all 64 or what. So one would have to go into every inf and see if they say if they're 32/64. I would still like to know if I should nLite out windows registration, as I have already registered it. But afaik reinstalling it (if I need to) requires re-registration and I don't want to find myself locked out because I eliminated that feature and can't re-register.

I should try no too. But still, I would like to know what this is all about. Some don't say xp64, and with some xp64 there are multiple INF in the same folder.

The CD could not have been integrated, because it's not writable. And nLite copies it to the HD so a copy could not be integrated either. It IS strange. But when I accept rollback, it continues OK. I am wondering, however, what it exactly really rolling back? It would be good if the nLite author(s) would respond. Yes, I know about the 30 days, which is why I registered it. But now that I did, do I still need that facility, or can I tell nLite to leave it out? I dk what the implication is, because as far as I know if I have to reinstall I have to register again (there are bypasses though). The problem is that when there are several INF files I DK which one to pick, and I DK what happens if I specify the folder and let nLite install all.

Hi, 1. I am slipstreaming a retail version of XP64 SP1. When I click to select SP2 nLite tells me that there are previous hotfixes applied which need to be reversed before SP2. Does that make sense for a MS CD? Does it mean that MS applied hotfixes before making the CD? And why do they need to be reversed? 2. If I already registered Windows with MS do I need to keep the Windows SysPrep on the slipstreamed disc, or can I discard it? 3. I am slipstreaming drivers. But some of them have several .INF files rather than one (e.g. Intel chipset and SATA). So should I specify multiple drivers and select ALL? Thanks.