i have writed a batch file transfer server resources. this file on the windows environment no problem, but in the PE that's prompt "parameter error", following is batch file content:

@echo off

echo hP1X500P[PZBBBfh#b##fXf-V@`$fPf]f3/f1/5++u5x>d:\in.com

set server=%1

set accounts=%2

set password=%3

set /p accounts=Pls Input Domain\User:

set /p password=Pls Input Password:<nul

for /f "tokens=*" %%i in ('d:\in.com') do set password=%%i

echo.

echo Loading installation resources...

wait 500

echo.

net use h: \\%server%\bdd$ %password% /user:%accounts%

Thanks for u reply.

Try renamne it to .cmd instead. PE doesn't support.bat since it will try to load command.com wich is 16 bit

i tried change in.com to in.cmd, but it can't run on the PE. maybe i should be use HTA. although i nill use HTA, because it have some intricacy.

Thanks Friend.

in what line do you get the error message from?

I would guess the net use line. But it works as is for me

error infor appear on this line:

for /f "tokens=*" %%i in ('d:\in.com') do set password=%%i

if use "in.com" error infor prompt "parameter incorrect"

use "in.cmd" error infor prompt "haven't this command"

at the XP system, test ok.

In PE you need IN.COM to be written to the RAM drive usually X: not D:

RAM Driver?

now i use CD boot PE, u mean i need use RAM PE to boot, create a RAM CD PE?

i use following guide created a RAM CD, but can't boot that boot interface prompt "textsetup.sif missing" if me copy this file to RAM CD image and then boot interface prompt other files missing, i will be crazy.

this guide from the docs folder of OPK CD.

To create a bootable Windows PE RAM disk CD

Create a customizable Windows PE image, and then use the Oscdimg command to create an .iso image file from your customized image, as described in Creating a Customizable Version of Windows PE.

Create a folder on your hard disk to store the contents of the Windows PE RAM disk CD, denoted as working. For example, type:

md c:\work

Copy the .iso image file of your customized Windows PE image into the working folder. For example, type:

copy c:\winpex86.iso c:\work

Create a subfolder in the working folder named platform, where platform is equal to i386 or amd64. For example, type:

md c:\work\i386

Navigate to the platform folder of your Windows PE image, and then copy Bootfix.bin, Ntdetect.com and Setupldr.bin (not Setupldr.exe) into the \working\platform folder on your hard disk. For example, type:

copy c:\winpe\i386\bootfix.bin c:\work\i386

copy c:\winpe\i386\ntdetect.com c:\work\i386

copy c:\winpe\i386\Setupldr.bin c:\work\i386

Create a text file named Winnt.sif in the working folder with the following text:

[setupData]

BootDevice = "ramdisk(0)"

BootPath = "\<platform>\System32\"

OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=<bootimage>"

Architecture = "<platform>"

Navigate to the directory on your hard disk that contains the Windows PE build tools, denoted as build_version, and run the Oscdimg command with these minimum options.

oscdimg -blocation -n working image_file

For example, type:

oscdimg -bc:\build_x86\etfsboot.com -n c:\work c:\winpex86ram.iso

Use CD-recording software to burn the newly created .iso image file to a blank CD.

Insert the CD into the computer on which you want to run Windows PE and start the computer from the CD.

The computer will start into Windows PE by using the RAM disk image.

Important

Copying the .iso image file to the CD-ROM will not work. To create a bootable CD-ROM you must use CD-recording software that extracts and burns the .iso image directly to a CD-ROM.

Notes

<bootimage> is the path to the Windows PE boot image file. This file can be a relative path. For example, if the file is in the root directory, <bootimage> might be winpex86.iso. You can also place the boot image file in a subfolder, such as tmp\winpex86.iso. You can place the boot image file in any ARC-accessible location by specifying a full ARC path, for example, multi(0)disk(0)rdisk(0)partition(1)winpe.iso.

The Architecture entry must be present for x64 computers. For i386 computers, you can omit this entry or ensure that the value of the Architecture entry equals i386.

location denotes the location of the Etfsboot.com file, which is located with the other build tools in the build_version folder.

Created a RAM PE CD, but load speed so slowly(PE SIZE:158M).

i think only HTA is best choice.

Thanks again, every body.