Metzen

If you use a theme file with your wallpaper located in it, it will retain your wallpaper and custom icons.

Are you running it in a virtual machine? If so, you might need to increase the RAM on it. Or, if your running it in a computer with low RAM you might get that message as well. Can you bring up the task manager and tell us how much RAM is in the system and what the PF usage is?

Are you using a SETUPLDR.BIN file from SP2 or from SP1? The files are different. SP2 -- 254 KB (260,272 bytes) SP1 -- 240 KB (245,920 bytes) <edit> nevermind. I should read the whole post before *I* post.

I have it working on read-only media. Complete with opening *.MSC and all I am using the newest WinPE OPK, however. It is WinPE OPK 2004. It comes with plug and play support and unlimited resources amoung other improvements.

You can copy your "preactivated SLP" files to your unattended CD so you won't have to activate. The files are the following in your recovery media: Oembios.bin, Oembios.cat, Oembios.dat and Oembios.sig. The files may be compressed and so named: Oembios.bi_, Oembios.ca_, Oembios.da_ and Oembios.si_. Microsoft provides "template" files of these on a normal XP CD. Simply replace those with the files from your recovery media.

Diskpart only keeps the drive letter assignment for that session of WinPE. It does not store the values afterwards in the install. For instance, if you set the "C" drive to be the "F" drive, that only stays as the "F" drive until you leave the WinPE environment. Upon reboot to the install, Windows assigns the drive letters according to how it finds the drives. At least, that's my understanding of how it works.

Are you using Ghost or other imaging software? I've found that because I use Ghost (made a image right after GUI mode setup, but before first boot) that every system made from that image gets the same network name. This causes the first system with X name to boot and be able to contact the server via it's "computer name", but every system thereafter cannot. The solution I've found is to refer to the computer by it's IP address.

I noticed this as well, but it seems to only happen with Intel Chipset systems. VIA or Nvidia systems have no such problems (haven't tried with any other chipset).