Arie

If I understand you correctly, you want to install Windows XP on one partition or hard disk, using another partition or hard disk as the source for the installation files? Simply boot from diskette or CD-ROM and at the prompt browse to the I386 folder on the other partition or hard disk and start winnt.exe with the correct parameters to specify the location of the source files. You can run winnt.exe /? to find out the possible parameters.

It's not the cause. The caching of thumbnails has nothing to do with these shadows. You probably removed something else which you shouldn't have. If you post your last session log file as an attachment I'm sure that someone can tell you what you removed which you shouldn't have.

This should help.

Perhaps AnyDVD by Slysoft can, you would have to check their web site.

According to the nLite FAQ, removed components cannot be restored. But what do I know, I don't use nLite myself

cd ..\"Folder 2"

Re-download the file via the Microsoft web site and try again. Possibly the file you downloaded is corrupted.

Are you using Windows XP Home or Professional? Are you positive that you didn't remove anything related to this via nLite? (I don't know if this last thing is possible at all as I don't use nLite myself.)

There is no benefit when you look at your system later (not a production system, as the nLite EULA does not allow this) if the applications were installed later or during setup. The advantage is first of all the ease of use; once the installation is done, you have all your applications already installed as well. Why not use RunOnceEx for example you might wonder; my opinion is that if an application can be installed during setup, you won't notice that they're being installed, afterwards via RunOnceEx you'll see a whole different setup screen, which always makes someone wonder what it is. I like the fact that once setup is done, my whole installation process is done and nothing needs to be installed anymore.

Perhaps you can kill the task if it runs straight away. See the Unattended Guide, there is an example there I believe.

You could create an unattended installation disc for example, or make an image using sysprep, or by simply using Ghost. The choice is up to you. If it's for one machine only, I would personally simply make a Ghost image.

Same question as above, but replace administrative rights with power user rights

Paste the following in Notepad and save the file as "morland.reg" (note: only the extension is important): Windows Registry Editor Version 5.00 ; SPEED UP ACCESS TO AVI-FILES [-HKEY_CLASSES_ROOT\CLSID\{87D62D94-71B3-4b9a-9489-5FE6850DC73E}] [-HKEY_CLASSES_ROOT\SystemFileAssociations\.avi\shellex\PropertyHandler] [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{87D62D94-71B3-4b9a-9489-5FE6850DC73E}\InProcServer32] ; DISABLE PREVIEW OF MOVIE FILE FORMATS [-HKEY_CLASSES_ROOT\.avi\ShellEx] [-HKEY_CLASSES_ROOT\.mpg\ShellEx] [-HKEY_CLASSES_ROOT\.mpe\ShellEx] [-HKEY_CLASSES_ROOT\.mpeg\ShellEx] Double click the saved file, morland.reg, and when asked if you would like to import into your Registry, answer Yes. Please let me know if you managed and if it solved your problem.

Waiting for SP3 will give you a cleaner install than upgrading SP2 to SP3.

KB935448 is supported. It should have been incorporated into your source. Perhaps it causes a conflict with another update which is not supported. Can you post your HFSLIP log file as an attachment?

Using the Search function you would have found this topic by me

Please note that this will only hide specific drive letters, it does not offer any kind of security, meaning that this is not safe.

This should fix it. ; SPEED UP ACCESS TO AVI-FILES [-HKEY_CLASSES_ROOT\CLSID\{87D62D94-71B3-4b9a-9489-5FE6850DC73E}] [-HKEY_CLASSES_ROOT\SystemFileAssociations\.avi\shellex\PropertyHandler] [-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{87D62D94-71B3-4b9a-9489-5FE6850DC73E}\InProcServer32] ; DISABLE PREVIEW OF MOVIE FILE FORMATS [-HKEY_CLASSES_ROOT\.avi\ShellEx] [-HKEY_CLASSES_ROOT\.mpg\ShellEx] [-HKEY_CLASSES_ROOT\.mpe\ShellEx] [-HKEY_CLASSES_ROOT\.mpeg\ShellEx]

It sounds like you're using nLite for other than personal use, which would mean that you're breaking the EULA. In reply to your questions, why would you want to sysprep an unattended installation?

The normal log on screen, so not the Welcome screen, comes with the Lock Computer, Change Password, Shutdown, Cancel, et cetera window when you press Ctrl + Alt + Delete. If you use the Welcome screen, pressing Ctrl + Alt + Delete opens the Taskmanager. You cannot change either of these to show the other kind of window when pressing Ctrl + Alt + Delete. If you want to switch back to the Welcome screen, you can do so via the Control Panel using by heart User Accounts, or something called like this

Only use release candidates in a test environment. My suggestion, wait for the final release.

Why would you want to "switch back"; this implies that you are planning on using a release candidate in a "production" (I use this term widely here) environment and not in a test environment, what release candidates are meant for really. My advise, never install pre-release versions of any software on your machine if the machine in question is not a test machine. Keep in mind that you can also test pre-release software in a virtual environment, so it doesn't interfere with your normal workstation behaviour.

Perhaps you removed certain things using nLite which has caused this. I would suggest that you post your question at the nLite section of this forum and that you include your last nLite session information. You could also just reinstall Windows XP the normal way, without using nLite, to see if your drive works properly then.

For part one, you should ask at the nLite section of this forum. For the second part, you could use $OEM$ folders for that. See the Unattended Guide for that which is linked at the top of this forum. Both questions are posted in the wrong section of this forum. Please read the rules and post in the correct sections. Thank you.

No idea what you're on about to be honest. A screenshot would help.