Arie

The script which you posted and the problem which you're experiencing are not related I'm afraid. What else have you done in between the moment that it still worked and the moment that it stopped working? If I were you I would simply use System Restore to return to a previous state.

Not really as the scripts will remain on your hard disk, which is not required and they will only take up space, which most people want to avoid who use nLite as they want the smallest installation possible.

You seem to run into some of the downsides of nLite. My humble opinion is that nLite is not really meant for advanced users. It offers too little control over your project. I personally prefer HFSLIP. If the points which you mention get changed in a next build of nLite, I believe that nLite will always be straight forward, meant for the masses who simply want to click Next and Finish and that's fine, don't understand me wrong, but I'm not fond of it myself.

What have you tried yourself and what problems did you encounter?

With starting from scratch I assume that you mean that you would like to integrate the latest Service Pack yourself as well, instead of purchasing a copy which already includes the latest Service Pack? I would personally always prefer a copy which already has the latest Service Pack integrated. First of all it saves you the work of integrating the latest Service Pack, second of all it's a cleaner source than your own slipstreamed source would be.

What else you're missing? You seem to post a new question in an existing thread which isn't related to your question at all.

Did the problem occur midway through the download of SP2 or midway through the installation of SP2? If the problem occured midway through the download of SP2, then the problem has nothing to do with SP2. If the problem occured during the installation of SP2, it could be that the downloaded installer is corrupted (clear your cache and re-download to solve), you hard disk might have bad sectors (run chkdsk.exe to verify), you might have had various other applications running which conflicted with the installation of SP2 (kill all unneeded applications and processes before starting the installation), et cetera. Some good advise: always make proper backups of your data, especially when performing a major upgrade.

You could use Remote Desktop, any WinVNC based client, et cetera for example or perhaps simply send the links via Windows Live Messenger.

First of all, where did you bring it? Your question is somewhat unclear. No, you don't need to purchase any additional software for partitioning your hard disk. When you boot from your Windows XP installation disc, at one point you can choose where to install to. Here you can delete all existing partitions if there are any and then create new partitions. Please be aware that if you delete a partition, all data on it will be lost. Say your hard disk is 100GB big and you only have one partition, then you can't create any other partitions as you have no more hard disk space available. Delete this 100GB partition so that you have zero partitions and create for example two new partitions; 30GB and 70GB. If this does not work for you, please describe what error message you get while installing as currently your question is too unclear to come up with a better answer than this.

Read the Unattended Guide for a start.

Install the latest version, reboot your machine and then uninstall via Add/Remove Programs.

Yes and yes.

First of all, this thread is over half a year old Anyway, adding every silent installer to your WINNT.SIF file is not advisory. It would be better to add them all to your SVCPACK.INF and the ones which are not compatible can be installed via RunOnceEx for example.

Both.

You could create a silent, self-extracting archive, which extracts your theme files to the correct paths. You could let it extract via SVCPACK.INF for example.

The REG command is a Registry Command Tool. To see all available parameters, type the following in a command prompt. REG ADD /? The above command adds a key to RunOnceEx. You can see the command between the quotes (""). This specific command imports a Registry script silently (REGEDIT /S), which contains the registration information for the application Alcohol 120%. To see all available parameters, type the following in a command prompt. Same as above; the part between quotes ("") is the command, the part before and after the quotes belong to the REG command, so to know what /F stands for... *cough* REG ADD /? *cough* As for the /s /v/qn part in the command between quotes ("") itself, it's meant to install this application silently and unattended. Every installer type has it's own parameters which it accepts. Run the installer with /? to see what parameters are available. Sometimes though this doesn't show any available parameters, so then you'll need to find out what kind of installer the application uses to know which parameters it accepts. There is information about this in the Unattended Guide, so I advise you to read it. The Unattended Guide is a good start. Read the forum. Keep trying, trying and trying. And ask if something is unclear. Good luck!

As I already replied, these files are not present in a normal Windows XP source. This means that you have an altered source of some kind. Either you're using a modified source, perhaps an OEM source or an illegally downloaded copy. Anyway, you'll need to get yourself a proper source disk.

Will definitely make things more clear to some, nice

You could import your registry changes in HKEY_LOCAL_MACHINE.

Not included in an original source.

Even easier, the answer is written in the first step:

Nope, I use a corporate edition.

My source files don't include any files containing "perf". I believe that you're not copying the correct files from your scratched CD-ROM. You need the files in the root of the disc, as well as the whole I386 folder. Make sure that you're not copying files from an already nLited installation disc; those "perf" files might be a part of an add-on for example and not needed. I doubt that you're copying your source files from the original source disc. But to answer your questions, use Google to search for file comparison software, that should help you find out which files are missing. You could try to "fix" your scratched CD-ROM using toothpaste for example to slightly polish it. I cannot garantuee that it will work though. I would also suggest using Google to search for ways in regards to "fixing" scratched CD's. You can also ask Microsoft or your supplier for a replacement installation disc, or borrow one from someone.

You could create your own theme and have it applied during setup automatically via WINNT.SIF and you could have the wallpaper copied over using $OEM$ folders for example, or by running a script via SVCPACK.INF. Another method is to rename the default wallpaper in your source with a custom one for example. I personally prefer the first method however. See the Unattended Guide for more information.

This command imports a file named "activate.reg" silently into your Registry.