jrzycrim

Oh okay. Your comment about 2 Winnt.sif's through me off. What I do is import the values for these keys from cmdlines.txt: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ThemeManager] [HKEY_CURRENT_USER\Control Panel\Colors] [HKEY_CURRENT_USER\Control Panel\Desktop] [HKEY_CURRENT_USER\Control Panel\Cursors] <-- if you want custom mouse pointers If you have your .theme file already created, you might look at this key: [HKEY_CURRENT_USER\Software\Microsoft\Plus!] That key holds settings for the currently active theme. I haven't tried using that key, however. If you use the classic logon screen and want the same theme settings applied there as well, you can import the above theme settings into HKEY_USERS\.DEFAULT: [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\ThemeManager] [HKEY_USERS\.DEFAULT\Control Panel\Colors] [HKEY_USERS\.DEFAULT\Control Panel\Desktop] [HKEY_USERS\.DEFAULT\Control Panel\Cursors]

Thanks for the correction. That will probably save egil some trouble.

Are you saying that you want a script that will let you select which theme to use?

Copy a shortcut for explorer.sfc to the quick launch folder during setup. The folder for quick launch is: %userprofile%\Application Data\Microsoft\Internet Explorer\Quick Launch

http://labmice.techtarget.com/windows2000/install/RIS.htm http://www.microsoft.com/technet/prodtechn...t/superris.mspx The $oem$ folder is placed along side the I386 folder for a CD based unattended installation. For a unattended installation from a network share/ris server. the $oem$ directory is placed inside the I386 directory. I'm sure others will post lots of tips and/or links. Good luck.

That's a fairly common problem and it's usually related to context menu handlers (right click menu entries) that 3rd party applications install. Have you installed any new progs recently? Do you receive any errors? Does it happen with any type of folder or with folders that contain images? Launch regedit (start > run, enter regedit), and export these keys: HKEY_CLASSES_ROOT\Directory\Shell HKEY_CLASSES_ROOT\Directory\Shellex\ContextMenuHandlers HKEY_CLASSES_ROOT\Folder\Shellex\ContextMenuHandlers Post the contents of those keys here and maybe the potential problem can be found.

Are you using DesktopX? I think that file is a part of that installation. CompanyName : Stardock FileDescription : MCPServer InternalName : MCP OriginalFilename : SDMCP.exe ProductName : Stardock MCP Core Services (System Extensions and Hooks) Are you having a problem with it?

I also found this in ref.chm. ref.chm can be found on the XP CD in Support\Tools\Deploy.cab. This page provides the valid Locale ID:Input Locale combinations for a particular language. http://www.microsoft.com/globaldev/referen...xp/xp-lcid.mspx Apparently, only these combinations are supported for Dutch Standard: 0409:00020409, 0413:00000413, 0409:00000409

Well, I think I was wrong about the ProvideDefault option. Taken from ref.chm: ProvideDefault Specifies default answers in the answer file. In this case, Setup displays these default answers to the end user, who can change them if they are not appropriate. Use UnattendMode = ProvideDefault in preinstallation scenarios where the OEM or administrator wants to give the person setting up the computer the option to change the predefined default answers (especially network options). That shouldn't have any thing to do with the problems you are encountering. I'm really not sure about the keyboard problem.

First, you should remove your Product key. I mean remove it from your post, not from your winnt.sif. Second, I would say that UnattendMode=ProvideDefault is causing your trouble. Change that to UnattendMode=FullUnattended. Setting that to ProvideDefault is limiting the options that you can set.

You can use this registry key to set the Swap file: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] After adjusting your Virtual Memory settings to your preference, export the above key. You can import the Reg file manually or automatically during an unanttended install. Many users change the location of the Program Files directory to a partition or hard drive other than the system partition. I'm not sure what the benefit of doing this is. If you have to reformat and install windows, your 3rd party applications will be present on the other drive but all the registry information for these programs will have been wiped out during the re-installation and will pretty much be rendered useless. Good luck on getting straight answer for the best method of setting up your swap file. There are many, many different opinions on the subject. I will leave you with this link, however. http://aumha.org/win5/a/xpvm.php

Where do you recommend I put this command? The easiest way would be to create a batch file with the subst command and place it in your Startup folder in the Start Menu. Make a text file named something.cmd and place the subst c: h:\ in that file. Place your .cmd file in the startup folder. Alternatively, you can make your .cmd file a logon script. Goto Start > Run, enter gpedit.msc, Go to User Configuration > Windows Settings, select Scripts (Logon/Logoff), Double-click Logon, Click add, Browse to where your script is, Click ok, click ok. Now your Script will execute at logon.

http://support.microsoft.com/default.aspx?...kb;en-us;307028

qchain strikes again!

You probably used a cleanup.cmd file that you found here in which one of the commands is shutdown.exe -r -f -t 60 -c or something similar. It's supposed to do that.

I don't know. I didn't see reg.exe in the list of available commands. The RC is pretty limited in functionality. That's a tricky Key, I've been fooling around with permissions but so far I haven't been able to delete it...

You can't use the recovery console to edit the registry. Bartpe might be an alternative to consider. This registry key can't be deleted from within regedit?

$Docs and $Progs should be placed in $OEM$. http://unattended.msfn.org/xp/oemfolders.htm Having a folder named administrator is going to cause a problem. When setup finds that folder in Documents and Settings, it will create a new folder called Administrator.computername. Your favorites will end up being in the wrong place. You can make a self extracting archive of the Admin folder, place it in $Docs, and the extract it during RunOnceEx. Or just copy the files that you need over to the administrator folder (or other user folder) sometime during setup.

Another option is to use the recovery console. http://www.wown.com/j_helmig/wxprcons.htm

Go to Start > Run, enter msinfo32, from there go to Components > Display. You should be able to see the amount of Ram that is being used for Video memory. As prathapml pointed out, this generally can be adjusted in the bios although 896MB is a goodly amount of ram.

I was hoping to report back with positive results as far as icon positioning goes but alas, due to unrelated problems with my latest unattended CD, I never made it to first logon. *shrug*. Not sure where the problem lies but I suspect the ISO I was testing was corrupted in some way. Didn't get any errors, just hung during the reboot after setup. I sure hope these tweaks work or there are going to be some people p***ed off at me.

The Logon screen or the boot screen where you see the progress bar?

After arranging your icons like you want them, log off and then log back on, open Regedit and export this key: [HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags\1\Desktop] You'll need to import this before the first logon.

Thank me if it works for your Unattended CD.

Awww, shucks. Like I said, I haven't tested these during an unattended install but I think they will work if you import these settings before the first logon.