Arie

Why would anyone even want desktop search functionality? (Seriously, why?)

What functionality which nLite offers would you like to use in a business environment? Integrating service packs, hotfixes and such can be done manually as well. Silent installations, tweaks, et cetera during the setup process can be handled manually as well via SVCPACK.INF for example. Removing default Windows features is not advisory in a business environment. So what's left then for which you need nLite?

First of all let me state that I don't use nLite myself as I use HFSLIP, default Microsoft tooling and such. 1a. Hotfixes get integrated into your installation source files. This means that your installation source files are updated. The installation process will therefore copy the new files straight away, as the old files are replaced. This is default functionality of most if not all Microsoft hotfixes. You could therefore do this manually as well if you would want; tools such as nLite and HFSLIP only makes this easier. See the Unattended Guide for an introduction on how to integrate hotfixes manually. 1b. Switchless, silent installation packages are not integrated into your source files as they didn't exist in your original source files in the first place. These packages are copied into your installation source files and are executed at T13 via SVCPACK.INF. Once again you could do this manually as well if you would want; tools such as nLite and HFSLIP only makes this easier. See the Unattended Guide for a complete timeline. 2. This question is most likely answered in the nLite FAQ. As I don't use nLite myself I cannot answer this question I'm afraid. 3. The location of these setups does not matter, but I would advise you to create a folder in the root of your installation disc named "Software" for example so that the used pathname will never be too long and cause any problems. You can choose to use an $OEM$-folder to copy the setup files to your hard disk first, afterwhich you can start the setup, or you can choose to start the setup from your installation disc directly. I prefer the latter. See the Unattended Guide for an overview of $OEM$-folders. How to have these applications install, I will answer below: 4. RunOnce and RunOnceEx are Registry keys which can be used to start a script, installation, et cetera. As the name suggests this will only happen once. In short, RunOnce simply starts a script, installation, et cetera, whereas RunOnceEx does so with a nice little progress kind of screen. Because of this I always use RunOnceEx to install applications directly from DVD on first boot. I use RunOnceEx to run various scripts, to run various switchless, silent installation packages which are not SVCPACK.INF compatible (see 1b), et cetera, all directly from DVD. See the Unattended Guide for an overview of RunOnceEx as well as how to start an installation from DVD using RunOnceEx. Hope this helps.

The difference between a three disc installation and RIS is quite big; you're going from one side all the way to the other. Why not simply put your installation files on DVD?

WINNT.SIF in short supplies the answers for the setup process of Windows XP itself. To run installations directly from CD-ROM after the installation of Windows XP has finished you can best use RunOnceEx. Click here for more information. Are you positive that you read the Unattended Guide?

Just have a look at the Unattended Guide

Upgrade to the latest version of nLite if you haven't done so already and otherwise try re-installing the latest version of nLite.

Perhaps your source files are corrupted. Re-copy your source files from your CD-ROM to your hard disk. Copy the files to a folder with a short name without spaces such as C:\Test and try again.

Download Regshot. Take a snapshot of your Registry. Change your home page. Take another snapshot of your Registry. Compare both snapshots. Export the keys which have changed which refer to your home page. Import the exported REG-file via SVCPACK.INF, or if you use nLite convert the REG-file to an INI-file and add it to your project.

Thank you for your reply... although I was hoping for a solution Kind of expected this since no one had replied yet and my own search has left me without a solution either. Thanks again.

Run RegSvr32.exe from your command line to register the required DLL-files.

Same here. Windows Update and Microsoft Update don't require me to install anything anymore either. Works like a charm.

Have you used both in a multi-country based company, consisting of 55.000 users in one of these countries alone? The solutions which Symantec offers for corporate environments beats ESET every day in regards to configurability, management, scalability, et cetera.

I would suggest to simply use a DVD to burn the project on, so that disc capacity will never be an issue.

See the reply above. Secondly, the filename of the batch script doesn't matter, it's the contents which count. The batch script simply adds keys and values to RunOnceEx in your Registry. The type of CD-ROM doesn't matter therefore; it can be a corporate release, retail release, et cetera.

No offense, but if you don't even know how to integrate a Service Pack and you apperantly couldn't find your answer using Google or get the answer straight from Microsoft if it would be a bug in SP3, why would you even be installing a Release Candidate, which isn't meant for normal home users as it's meant for testing purposes and might contain bugs or cause problems?! I kindly advise you to stick to SP2 and it's updates.

Read the Unattended Guide, the answer can be found there easily. You can have Office installed directly from CD-ROM via RunOnceEx.

There's a recent topic somewhere on this forum in regards to adding updates via SVCPACK.INF, search for that. Secondly, add updates one by one to find out which one is the culprit.

This isn't possible for as far as I know. Secondly, why would you even want this? I can't think of anything.

Add a text file to GuiRunOnce? That would be a very simple and cheap solution.

One: mine

Again, why ask nLite related questions here and not in the nLite topic which exists on this forum? Please ask a moderator to move your posting.

Why ask nLite related questions here and not in the nLite topic? Please ask a moderator to move your topic.

I fully agree with you, however it is quite obvious that the topic starter does not have the intention to perform any kind of pre-release testing.

You're using nLite. Ask your question in the nLite section of this forum.