I am glad to say that somehow or rather, I manage to install BartPE into a USB flash drive and successfully run LAN connection and wireless connection to the internet on my Toshiba notebook. Besides the usual plugins that came along with pebuilder3110a, I added the xpe-1.0.7 and wireless service plugins into the compilation.

For the ramdisk.inf, I tried to use RamDiskDiskSize="0x08000000" which said that the size should be 128 MB, but when BartPE is working, I can only get around 95 MB as drive B:.

While surfing the net I downloaded and installed the warez 12 bootcd and found that the mini Windows XP there can give a B: ramdisk of 823 MB on my motherboard that had 2 GB of RAM installed.

I shall be very glad if anyone can tell me how to do this with the BartPE pebuilder3110a program.

Thanks again for everyones' help and information posted in this wonderful forum.

Plan on being very glad then when you read this thread: http://www.911cd.net/forums//index.php?showtopic=20203

Thanks Ed. I'll try that ImDisk out.

Thanks Ed for pointing out the Imdisk software to me, indeed I am very glad.

I tried to run the imdiskinst.exe directly in the flash drive which I compiled BartPe earlier, it worked fine and allowed me to create a virtual harddisk of variable size, and I was able to save a 4MB image file.

Next I put the files mentioned in the forum post howtopic=20203 as a plugin in pebuilder3110a to be compiled, and it turned out fine too, no errors occurred and I could see the 4 files - imdisk.cpl, imdisk.exe, ramdisk.cmd and Autorun4_Imdisk.cmd in the pebuilder3110a\BartPE\i386\system32 directory. Also there was a ImDisk folder in the \pebuilder3110a\BartPE\Programs directory.

My problem started when I used the PeToUSB3007.exe to compile the USB flash drive. The compilation completed without any error message, however the above mentioned 4 files were missing in the \minint\system32 directory. Besides this, the ImDisk folder was also missing in the \Programs folder in the flash drive.

Any idea of what I have missed out?

Being a newbie in modern computer software, I don't really understand how to use the "ImDisk.Script" after extracted from ImDisk.7z. Is this needed for the compilation and where shall I put it?

That is very strange. PEtoUSB writes everything in the BartPE folder that PEBuilder creates to the USB device. If the IMDisk files are missing from the USB device it would indicate that they are not in the BartPE folder you used as input to PEtoUSB. The question is why. Do you have multiple versions of the BartPE folder?

I have used both versions of PEtoUSB without problems. I have never used the .script file you refer to.

@woren

I've updated my own imdisk based ramdisk plugin a little bit.

Download here

The plugin is ready to use, all files included.

It is pre-configurated for BartPE with nu2menu.
For using in a XPE system, you have to edit IMDisk.inf (search for "enable the next 2 lines if using XPE")
and you must disable the ramdisk-plugin in the XPE-plugin.

In a computer with 2 GB of RAM, and the default ramdisk-size setting of 50% of free physical RAM, you get a ramdisk > 900 MB.


readme.txt:


fuwi

@Ed

I think I got my problem solved when I deleted the configuration setting file which PE2USB2007 created each time after it ran. After I deleted that file, I got the ImDisk sub-folder in the \Programs folder and after the flash drive was started, I got a 3.96MB B: local disk and was also able to setup another virtual ramdisk of my specified size. Thanks again for the information you posted.

By the way, I find that the PE2USB2007 can install BartPE on a 4GB flash drive formatting it with FAT; it broke the 2GB barrier which I read in some of the post in the forum.

@fuwi

Thanks for the link to your Imdisk. I'll try that out.

Happy to hear you've gotten by the problem.

I must admit I didn't read your posts properly. I thought your reference to PE2USB2007 was referring to one of the two versions of PEtoUSB that have been spoken about here not a separate app actually named PE2USB2007. And PEBuilder comes with a script named pe2usb. All the similar names gets confusing after a while.