johnhc

mrioa, in general when components are removed, they should be considered gone forever. This means recreating a new ISO from scratch. Since you did not attach your Last Session.ini, we cannot see what was removed, but see this thread and see if your think it applies. And, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

jeepster, thanks for telling us about this little message: This means that you have started with a previously processed source. I also see you are using Windows 2000 to run nLite to create an ISO for XP. We know people have trouble using Vista and W7 for XP ISOs, so it may also not work under W2000. The problems are mainly associated with integrating an SP. Can you run under XP? Where did you get the source CD? As far as you know, has it been modified by nLite or any other integration program or process? Please post a screen shot of a Windows Explorer view of the CD. Enjoy, John.

jeepster, there are some threads here discussing using Upgrade CDs. Please do some searching. I think at least some have been successful, but the CD for the Windows version being upgraded from is asked for during installation. You are not getting this far. I seem to remember a thread that got around this by copying some of the files/folders (from the old OS) to the new folder before making an ISO. I cannot find that post at this time. We do need more information, so, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John. EDIT: Here's the thread, Post #38.

Slinkie, you are welcome. I doubt the hot fix will help, but it is worth a try. I can't kill anything for I am just a poster as yourself. There are a lot of very smart people here and someone else may comment. Enjoy, John.

Slinkie, I think you are not in the correct forum, but I am curious. Why are you not running SP3? Are you using nLite (please attach (not paste) your Last Session.ini) or have you customized your XP? I found this MS article, which may not apply to you but may if you are using the Favorites menu heavily. It provides a hot fix you could try. Sorry, I cannot even suggest a forum of experts. Have you tried a trace like Wireshark (free)? Good luck, John.

geese howard, I do not use VirtualPC and have no idea what 'auto publish feature' is, but if you ran nLite under W7 to create an ISO for XP, then you are lucky that it installed much less runs. So, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

I found this post by prathapml (great thread - a little dated). It describes, among other things, how to set the paging file size during install. I had to do a couple of things to get it to work on my XP x64 system. The thread shows using pagefileconfig.vbs from the System32 folder. I did not have one on my running system (nLite install), but I had a pagefile.vbs (also not on the running system) in my original CD files. I placed this in my $OEM$\$$\System32 folder and called the pagefile.vbs routine from my command file invoked via the Unattended RunOnce exit. It worked fine except the paging file ended up fragmented. I don't remember what the original size definition by Setup was, but it was smaller than mine. I specified 1.5x my memory size for both the initial and maximum (6144 MB). I have done a lot of searching without luck for a method to set the paging file size before/in lieu of Setup, so I don't end up with a fragmented paging file. I have found several methods to defrag the paging file via Google, but I would rather not have to do this. I am hoping that someone can suggest a scheme to accomplish this. Thanks for any comments. Enjoy, John.

galocza, I am on the outside looking in, but I would think the drivers are OK and OK with Windows Setup since they work with the F6 method. Similar to my experience with the 3Ware RAID controllers (always seems to be RAID) indicates a simple change to the txtsetup.oem is useful. My symptoms were the same as yours and Fernando 1 corrected the problem. I know work arounds are not the ideal solution, but it is all we have right now, unless nuhi returns or asked some one else to take over. Thanks for giving us your time for testing. Fernando 1, I agree, many won't want to alter driver file(s), but the alternative is F6 and I think it is not very attractive. One of the main reasons I started using nLite was to avoid a floppy and my new machine has no floppy. I searched all my drivers and none use the ''ProblemDevices" code. What does this do? Have fun, John.

Fernando 1 and galocza, you guys have done a great job of defining the problem. Is it not possible to consider some change that might eliminate the problem? We seem to know that the two programs are most likely not going to be updated to correct the problem. Since the ''ProblemDevices" code is unusual, might it help if it were removed? What is the effect of these lines? What is the effect of leaving them out? Is there any other ideas you have Fernando 1? You guys are doing all the work, but I hate to see you have the problem defined so well, but unable to get a work around. Thanks for listening, John.

MysteryMan, yep, gone - thanks. Now that your system will boot the CD, are you installing OK? Sometimes, writing at a high speed can cause problems. You need to remove the Tweak "Explorer-Launch folder windows in a separate process" - it exposes a Windows bug, but not your problems. Please let us know where you stand now and if you have any problems. I see nothing obvious in you Last Session. Enjoy, John.

MysteryMan, quickly, you need to remove the posted Session_u.ini files! These contain your CD key and some other personal information. Quickly! John.

MysteryMan, how did you create your DVD? Are these all the files on your DVD? What is the total size of the source file? I had a problem when my source file got to 2.6 GB. The solution was to use the Mkisofs for the ISO Engine in the Create Bootable ISO task. And, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John. EDIT: Please see this thread.

-X-, I am not arguing that MS/nLite don't prevent newer version files from being overwritten by older ones. Some time ago I looked a little more deeply into the MS update process and saw all kinds of weird controls, including the GDR and QFE types of fixes. I hope Kurt_Aust will comment here. Enjoy, John.

andreyvul, so you are saying that it would have worked all along if plugged directly into a USB port? I would check with the mouse vendor tech support. Have you done some Googling? Good luck, John.

galocza, thanks for your reply and your willingness to do more testing. I am running XP x64 and had a problem with my 3Ware RAID card. I was able to test without actually installing (and wiping out my running Windows). I just booted the CD and let it go till Setup asked me to pick a HDD/partition. When it found my 3Ware RAID, I was good-to-go (then just hit F3). If you look at the link, you will see that Fernando 1 was able to help me. I suspect he will be all over your problem when he is available (I have no response to my PM). I too was unable to access MSFN forums yesterday. Again, thanks for your willingness to test. Enjoy, John.

4875720, great. You are welcome and thanks for reporting. Enjoy, John.

-X-, it would really surprise me that the update order did not matter. I think it is the MS update process that respects version numbers/order. I know Kurt_Aust goes to great length to have the updates in the correct order in his x64 thread. I hope others will comment. Enjoy, John.

galocza, I PMed Fernando 1 to have a look. He is the driver expert here. Hope he has a chance to take a gander. Enjoy, John.

bobn4burton, in my System32 folder is a file named msfeedssync.exe. Take a look at your folder and see if you have one. Also do a Google search and see what the module is about and other information about Synchronization Manager - I get lots of hits on it. MSDN has lots of articles and perhaps you can find how to enable it or put it back together. Ponch, the Support Information is placed there by the "OEM branding" Option. I find it useful. Have fun, John.

andreyvul, yes, basically I think you need to get down to the fundament and something that works. Hope you can give it a try. Enjoy, John.

bobn4burton, quick note. If you have the original install CD, the Last Session.ini file should be on it (Unless you selected the Option not to save). So find the CD and please post the Last Session.ini. The bad news is that is very hard if not impossible to reinstall an removed component, but we will take a look after you post your Last Session. Enjoy, John.

andreyvul, OK, thanks. I think now you should try Kurt_Aust's suggestion in another thread where lots of stuff was removed/tweaked. Run nLite (starting with a fresh copy of CD files/folders), remove nothing and tweak nothing. You need to permanently remove "Explorer-Launch folder windows in a separate process". It exposes a Windows bug, but is not your problem. I would warn against "CDPromptRemove" in options. This can cause Setup to start over and over. I am not familiar with "DisableFreereq" and "AdvTweaks" and can't find them in my Options Task (I am running x64). What are they and what do they do? For your test run, they should be removed. What is the ERSvc service you have disabled? Please let us hear the results. Good luck, John.

andreyvul, AMDAway is not a Cool'n'Quiet driver. Here is what MSI DL page says for 785GTM-E45 MB. I don't think I would want this on my system anyway. I would want to know about missing drivers. BTW, Cool'n'Quiet is not really a driver but just an application. Please run the experiment I suggested and let us hear the results and please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

andreyvul, you never answered my questions from an older reply, such as where your source came from. Knowing little at this time I would be more suspicious of the AMDAway driver. What purpose does it serve? Please post a link to where you DLed all the ATI and the AMDAway drivers. At this time I think maybe the best starting point is to remove all but the text mode drivers and see if the mouse works. Enjoy, John.

patcat88, that does not look like an nLite created winnt.sif. It should have a note at the top saying "; Generated by nLite 1.4.9.1". Using nLite, you will not have the Repair option unless you choose Prompt Repair for the Unattended Mode under the General tab of the Unattended task. Please see the the help (? in a circle) next to the Unattended Mode drop list. And, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.