Hi Jaclaz. Maybe you did not make the .sif file, but you did make a script that made maybe a bootsect? It was over on boot-land. It made RMLD1, ramx1.sif and inside directory btsec it made RMLD1.bs. I will restructure the question, as 2 days later I have a better idea. In XP, I made a standard BartPE ISO that used the ramdisk files from 2003. I think it was Wimb's method, that also included your script I believe, that made it possible to rename (I think) the .iso into .img. The projects name was I think USB_XP_Setup. Anyway, using this project allowed the bartpe.img file to be included into a standard XP boot.ini in this fashion C:\btsec\RMLD1.bs="Bart PE - Boot BartPE.img from RAMDISK" This worked out really well for me. In the BartPE image I had all my drivers as well as the Macrium Reflect PE plugin. Once I made an image of my hdd, I stored it on another hdd. When I wished to restore my c: back to an image, I simply used the boot.ini option to load BartPE into RAM. The BartPE.img lived on the c: root. Once it was loaded into RAM, I could overwrite c: with a Macrium image using the Macrium Restore Tool from BartPE that was loaded in RAM. I understood this well enough that I had multiple .img options in my boot.ini file. I set up countless people with the ability to make disk image backups and restore very easily. Since the BartPE.img and associated boot.ini options were in the images themselves, whenever you restored an image it was all still working just as normal. Now, I have updated to Win 7 Ultimate. I am of course imaging with Macrium. I have a working version of Win7RescuePE built with WinBuilder, simply because it is so easy to use. I have this on a CD, and it works as expected. However, I am now seeking to re-create a boot option, preferably one in the BCD that is similar to the boot.ini option I had in XP. This option is to boot, into RAM, a PE image that is on the root of the primary boot partition. I have had success in vmWare by using grub4dos. You helped me out immensely years ago with your little EZCD script, which I have make literally hundreds of XP UACDs with. With grub4dos v0.4.4, I am utilizing the iso boot option to boot the Win7RescuePe.iso file. It does work, but I am unable to use the --mem parameter. It is due I think to the fact that the iso is already a RAM disk boot image. I have it working with the (hd32) and the (0xff) parameters. I find that since win 7 likes to create the 100/200mb boot partition, just paying attention to whether to use (hd0,0) or (hd0,1) is faster than using the find function. Honestly though, using the --ignore-floppies and --ignore-cd parameters means there is not much speed difference in the find command. Anyway, I am still interested in a method that utilizes the BCD to do this. Actually, the whole wim and vhd thing is quite different than what I have become accustomed to, and I enjoy learning new things. Thanks for the time Jaclaz. Sul.