Mandarin

Thanks for clearing that up - looks like the WMP slipstreamer is smarter than it appears. Will try it that way once the new Windows updates are available after Patch Tuesday.

Thanks Booogy but on that link it says install the slipstreamer but in your reply you say add the slipstreamer to the hot fix page so I am confused. Do I install the slipstreamer to my system and then also add it to the hotfix section along with any other WMP hotfixes? Or do I add the WMP slipstreamer to the hotfix section along with the WMP 11 program and any associated hotfixes? Or do I somehow add the WMP slipstreamer into nLite as a plug-in? Not a biggy cos it works fine the way I do it but if there is a simpler method that does it in one step I will use that.

How do we use it via nLite Booogy? I've used the slipstreamer as a stand alone and it works great but didn't realise it could somehow be used within nLite. Here is what I do - use Signet's Integrator to add Ryans update pack to my SP2 CD - open the slipstreamer and point it to the i386 folder and slipstream all the updates - then I use nLite to lighten my CD. Is there a guide to using the WMP slipstreamer in nLite - I must have missed it somehow.

Both addons have been updated several times since so I don't see the value in you spending time on those particular ones. But for info one addon was Foxys Nirsoft Collection large v1.5 which would never work for me with Kels Uber pack v9.9.5. Changing either would solve the problem and I don't get the issue with either of the updated addons. I can understand Ricktendo's issue because both of those addons are variations of each other - you would never usually use both together on the same system.

And sometimes it is not as simple as a single addon either! I had this problem for over a month before finally working out which two addons were responsible - both worked perfectly on their own and each had worked fine in previous versions but I had one particular combination that just didn't want to play ball. Took hours and hours to track down.

Are you using Kels Uber Addon pack?

There is an option in nLite to get round exactly this problem. It is on the very last screen before you ask it to start the process - the screen that has two tabs and a whole bunch of options listed, one of which is to include the config files on the CD for example. Maybe someone else can help with describing it better than me but it is in there for sure.

You can click and drag them to the position you want them. Oddly enough this was a feature in earlier versions of nLite - wonder why it isn't there now?

I stated earlier that I add your addons with Signet's Integrator, then I run the build through nLite, that is why I asked if you also wanted the Integrator log. Of course the nLite config file will not show something that has already been integrated with the Integrator. If I add just the new 2.1.9 addon pack (with the integrator) and then run it through nLite using the config file I attached, everything works perfectly. If I add the Uber pack version 9.9 (again with the Integrator - either at the same time as the update pack or as a seperate run after the pack has been added) and then run it through nLite I get the errors as shown. Post #21 does make this fairly clear and also states that I don't think either nLite or the Integrator is to blame. Possiblly the Uber pack is also not to blame on its own because few other people seem to have any problem. But when nLite is used after the Integrator with ver 9.9 it breaks my install and version 9.7 does not so I don't know what is going on? I can reproduce the error (as per the screenshots taken last night) every time. It's not a biggy anyway cos I can easily drop back to 9.7, which has always worked perfectly but just thought you might like to know there is a potential issue. After all my setup can't possibly be totally unique.

OK - just had the same error again. Attached are two screengrabs from VMWare, first is of the first error, clicking on OK then gives the second error message. Config file from nLite also attached. Having problems getting the setuperr log out of VM Ware - will have another go tomorrow, it is now coming up to ¼ to 2 in the morning. LAST_SESSION.INI

Hi Kel - I'm back home tonight and will reproduce the errror and post the info you have asked for. I'm using XP Pro with English UK as the language. Is there anything else you need to see besides the setuperr log and my session.ini file? I am using Signet's Integrator to integrate Ryans 2.1.9 update pack and the three addons that I mentioned - then I run nLite and use nLite to make the final ISO. Is there anything from the Integrator log that you need?

If I don't use any addons everything works perfectly. As soon as I start using addons it fails so I set about trial and error to find the cause and have carried out over 50 tests last week, each taking around two and a half hours so I have spent a lot of time on this. I use a number of tried and tested packs as routine and this is one of them which hasn't caused a problem before so I jsut kept adding it and kept getting problems. Then I took a step back and just added any packs that had been updated or were new since the 2.1.8 build that worked and it failed. So then I took out the ones I had used previously and just put brand new ones in and it worked. This suggests it is an updated pack. I then try again using packs that I have tried before with success but have been updated and use 3 packs Kels Uber pack version 9.9 Kels runtimes pack 2.51 (I had been using 2.3) and Kels Vista drive indicator v1.8 (been using 1.6 previously) I get the error - so it suggests that one of the above is causing it. I drop back to version 9.7 of the Uber Pack having noticed that someone else mentioned a problem with 9.9 in nLite and everything works perfectly. I try using nLite to do everything (including the 9.9 pack) and get the error. I am only reporting an issue I am getting in the same way I have reported other problems. An example is the Luna Royale pack that caused issues made by Ricktendo. Loads of downloads and nobody had reported a single issue with it until I posted, then others reported the same issue and Ricktendo himself replies to say he was grateful cos he couldn't track down which of the addons was breaking his install! Based on the above I felt it necessary to mention what I thought was causing the problem in my case, that way everyone benefits. It is not a dig at anyone - it is the result of a huge amount of testing which has taken over 100 hours of my own time. In a similar way I am testing the new office integrator with Signet, which had issues preventing it working in the first releases - but people responded saying it worked perfectly for them!!

It's not nLite - as I mentioned in an earlier thread. I have no identified the addon that is responsible for breaking all my installs. I did try using nLite on its own and it worked perfectly. I tried integrating Ryans latest pack with the Integrator then using nLite with my tried and tested configuration and it works perfectly. It was only when I started using addons that I got the issues and after hours and hours of testing I am fairly certain that it is Kels Uber addon pack V9.9 that is breaking it. If I leave it out everything works fine, soon as I add it the install goes all screwy. I know it is nothing to do with your original problem but anyone seaching for this error message will find this reply which may now help them. Good luck with your issue.

Sounds like you need to enter those details on the unattended section - that is the step where you get the option of entering your serial number. The network name etc. are on the other tabs. I also remove the oobe (out of box experience) which gets rid of the need to enter user details etc.

I am aware of how you get this issue, the point I was making is that I am getting exactly the same errors without doing anything to SP2, manually or otherwise because my media has SP2 already in it. Anyway, after dropping back to the earlier edition of Ryans pack I still get this error so it is not the pack itself and must be an addon that I am using. My tweaks section is identical to the earlier working ones. In fact my whole nLite section is identical to eariler, successful builds so I am more puzzled now than ever.

Just to add to this further it is beginning to look like a problem with compatibility with nLite and Ryans update pack. Each works perfectly OK on its own but the issue comes when using Signet's Integrator and nLite, but only since the new pack came out - never had an issue with the March update pack or any before that. I normally use the Integrator to add the latest update pack then nLite the resulting folder to reduce its size and apply a load of tweaks - the same basic setup I have used for over a year. Then I add any other addons that I need using the Integrator again before making the ISO with nLite when I am finished. If I just add the update pack with the integrator and just run nLite with no additonal addons it works. Add even a single addon and the install breaks - even with addons that I have used for a long time so know that they are fine. As a final check I just finished running the whole lot in nLite alone with no integrator involved and got the same failure - so the only common factor is the new update pack. Going to try dropping back to the March pack and try it again and if the errors go away it sort of proves where the problem then lays.

Save a copy etc. does just that - it saves a copy of your nLite settings on the CD you create. The advantage of that is that should you wish to create a new CD later on you can load up the configuration details from the CD you originally made without trying to remember all the settings you made. It has nothing to do with any Windows configuration as such, though one obviously affects the other. The second question - you need to disable Windows file protection to avoid this issue. There is a small application that can toggle WFP on or off on an existing install which is probably your best bet now rather than start all over again. A search on the forum should find the utility.

The eSnips link is working just fine - just downloaded and will use for my next build. Thanks.

I'm getting this error for the first time after doing loads of nLited CDs previously with no issues. Can't add much other than it has nothing to do with SP2 cos my original CD has SP2 built in so I am not adding it at any stage.

I've run a fairly good and functional nLite version on an old 400 MHz laptop with just 63MB of RAM. Slow but the machine is slow anyway. Adding 128 MB of memory to it didn't actually make a whole load of difference on cos it is so slow to start with but it works.

When you come to the installation type screen in nLite you must pick the bottom option in the drop down list to keep this function, it then works fine.

It is a microsoft bug, not an nLite one and has been mentioned before on this board. It only occurs when you have a lot of addons (can't remember what number was quoted right now). I get the same problem and use about 125 addons as well as Ryans addon pack. Takes around 2 hours in VM Ware but is quicker in a real machine, which is a bit odd cos it always used to be the other way round. No addons and the install flys along, same as always.

Mine can take anything from an hour to an hour and a half on a virtual machine but it is always much faster on a real PC. It gets the point where the final reboot takes place and then the blue screen where it says loading and applying personal settings - that is the bit that takes forever! Sometimes it just sticks at this point and I do a manual restart and that seems to kick start it again. My earlier nLited CDs didn't do this but then my earlier CDs didn't have anywhere near as many addons slipstreamed either.

You have to copy your key file from your existing install of Everest. In other words you have to own this software before you can make a full registered version to use as an addon.