Okey, I have a customised WinPE 2005 iso file (with 1MB ramdisk) on RIS. It works fine. After I add a folder or modify some text files like startnet.cmd , all the GUI programs can not run and the network doesn't work either. No idea what's going on, please help.

BTW, the WinPE is based on Windows 2k3 SP1.

Ok. You need some priorities. Look at BartPE. Now look at ERD Commander. Now look at BartPE again. Notice any differences when you start the network after waiting to load all kinds of stuff? Load the network FIRST! o_O

It better be one of the first 3 things you load after Winpeshl because waiting to start the network after running those first commands is usually a bad idea when you need the network capabilities. As for your ramdisk, that's probably one of the bigger alarms going off more than anything to me. Why are you using a ramdisk in WinPE?

Everyone needs to move on to what I'm doing and just integrate the Vista write filter. It gives you access all over WinPE and your only limit is writing up to 32MB. You are attempting to use far less than this amount. I think you'll like it. Ramdisk would always give me a bunch of crap when I wanted some things to load on startup or if there were some keys in the registry that needed to be processed at startup. It's just a mess when you don't have the advantage you need.

As for Windows Server 2003, there are some bizarre problems reported when using it. I have no idea why.

Thanks for your suggestion, Daemonforce.

I have figured out the issue caused by the ISO editor. the iso file on RIS server may not be modified once it created. I just spend 3 hours to create a new one with all the new stuff and works fine.

Sure, the ramdisk is the matter but I need it to dynamicly create script file for diskpart or other utilities. The WinPE 2 with WDS is great, tested for a week, but there is no way to find all the NIC drivers for my systems. I have to wait it until final release.

Anyway, thanks a lot Daemonforce.