Arie

You give too little information for others to properly answer your question. See the Unattended Guide for how to install Microsoft Office, $OEM$-folders, or even nicer RunOnceEx directly from CD-ROM.

According to the nLite FAQ, you cannot re-add components to an installation which you previously removed.

You're messing things up. Remove the line "SET PP=%cdrom%\Apps\" from your scripts completely. The line "SET CDROM=%%i: " creates the variable %CDROM%, so if you have a folder named "Apps" in the root of your CD, the command to install an application would be "%CDROM%\Apps\YourApplication.exe". You could replace the whole line with the "SET CDROM" with the following by the way, which is shorter: SETLOCAL ENABLEEXTENSIONS SET CDROM=%~d0

Making even less sense after reading this article

Don't understand? I'm very sorry, but again I don't believe that I understand your posting. Perhaps it's just me as I'm not English from origin? To only focus on the question above, you seem to use a kind of virtual solution by Altiris which discards changes made using nLite and such? I would suggest to uninstall this Altiris solution. If you would like to test your nLite end result, you can use Microsoft Virtual PC 2007 for example, which is freeware.

Add AutoPartition = 0 to the [DATA] section of your WINNT.SIF and UnattendMode = ProvideDefault to the [uNATTENDED] section.

To be honest and without any offense intended, I don't understand a word you just wrote, eventhough it looks like English What is the problem which you are encountering and what is your question?

I'm afraid that I can't be of much help in regards to solving your problem, but please be aware that there are freeware alternatives to scan your Registry for invalid entries and such. Download CCleaner for example, which comes with a Registry cleaner.

You could use IEAK to customize your browser. I believe it's mentioned on the HFSLIP web site as well.

As already answered by "jbm", the files can go anywhere you want, as long as the path used in your RunOnceEx will be the same of course. But instead of using $OEM$-folders, which are first copied to your hard disk, you could also simply install applications directly from your installation disc. See the Unattended Guide on how to discover your installation disc via RunOnceEx.

Yes and yes. They can be useful, but you can safely delete them if you don't use them.

Integrating would be the best method. Integrating this hotfix should work I believe. Personally I use HFSLIP to integrate hotfixes, which works like a charm.

Are you sure that autorun isn't simply disabled? For as far as I can see your INF-file should work.

So if I understand you correctly, I could replace my TXTSETUP.SIF in my SOURCE and it should come out fine in SOURCESS and still include my manual changes?

Nonsense. But for a second lets assume that this would be the case, then why would Microsoft release a Windows XP compatible version of Internet Explorer 7 in the first place, which recently even got replaced with a copy which doesn't validate your copy of Windows XP? This would not make any sense. Logical thinking, common sense.

It's something which is triggered from SVCPACK.INF. You yourself must know best what you added to your installation via SVCPACK.INF Run all applications which you added to SVCPACK.INF manually to see which one gives you this pop up. You'll need to recreate this specific package to run silently.

Try the command "runas".

I should have figured that out myself. D'oh! Cheers for the help!

Yes, there should be a * there. You can easily test this yourself. Replace your name for something else and simply run it on an already installed test machine. If it doesn't work, it won't work during your unattended installation process either.

Post the contents of your RunOnceEx so that people can see what might be wrong.

Extract the file on a different machine and place it on a USB stick for example. Download a live distro such as Knoppix and replace the file.

I replied that I didn't mean my reply in a bad way. I also apologised for the way my reply could have come across. I didn't mean to be a smartass, I meant my reply funny, hence the smiley. If "ccl0" doesn't accept my apology, then there is nothing I can do about it. I'm only trying to help and I believe that I did above.

I'll give it a try and see what I come up with. If I get it properly working, I'll write a simple batch to automate it and I'll upload it for all. But first I need to get my SP2.CAB missing error solved which I get with HFSLIP ;(

I don't use the method as described in this topic, but I do install Microsoft .NET Framework version 1.1 SP1 and version 2.0 SP1 separately from version 3.0 SP1 and version 3.5. I install the first two via SVCPACK.INF, which allows me to install any applications which depend on either of these to be installed afterwards via SVCPACK as well. I install a package which contains both version 3.0 SP1 and version 3.5 next via RunOnceEx, as neither are SVCPACK.INF compatible, followed by any applications which depend on either of these via RunOnceEx as well. Instead of using the method described in this topic, I use RogueSpear's silent installer packages.

When using the repair option you don't have rights to write to your Windows folder if I'm not mistaken. You would need to add a few registry keys first which enable you to use the... ehm, I believe it was the SET command... and then boot to the repair option, make your Windows folder writable and then it should work... But as you might have guessed by my reply, I have never used the repair function myself, instead I prefer to boot from a live CD and restore the file that way. I hope however that my reply will give you a hint in what direction to look.