pr1ngl3

After 2 full days of searching and researching I have come up blanks so was hoping someone could help me. I have hundreds of scripts written by 3rd parties that I need to incorporate into a WIM, the trouble is all the scripts are hard coded to reference an X: drive. I can not rework the scripts becuause of licensing and liabilities so need to find a way of getting WinPE to alllow me to physically set the drive letter it loads as the RAM drive and subsiquently mount a device as the X: drive. I have looked into SUBST but it will obviously not allow substitution of the %Systemdrive% I have looked at DOSKEY but the complexity because of the number of hardcoded references to X:\<whatever>\<whatever>\<whatever> far outweighs the possibilities I have looked at the options within bcdedit > devobject > {ramdisk} but there is nothing associated with the drive letter I can't believe MS would hardcode the drive letter so deeply that it can not be changed, I know with the intruduction of WMI the registry needs a hardcoded reference, but surely this can be dynamic up to the point of creating the RAM Drive, even if this means rebuilding the sdi.

Thanks for the reply, but I had already tried this and it does not work.

I hope someone can help with this urgent issue. I use WinPE on a USB Thumb drive to install 2003 server. A quick summary of the process Boot from USB drive using syslinux bootloader (menu driven loader) Boot WinPE ISO via Grub Loader (syslinux will not load the iso) From WinPE, use Diskpart to Clean, Partition and make active HDD Format HDD (Logical Drive) to NTFS Copy over bootfiles (NTDetect, NTLDR etc etc) Copy over sysprep image Reboot machine and let it install from sysprepMy linked Image All this works fine on a machine running RAID 5 over 3 SAS disks; however the problem i'm having is getting this to work on a machine running RAID 5 over 3 SCSI disks. (both have only 1 logical drive) It partitons the Logical Drive and marks it as active but when the system reboots, it sticks on 'Error loading operating system' If I run the same process but instead of using a USB device, run WinPE from a CD (and altering the DiskPart commands as required), it will work fine. In addition to this, if I run the above steps from a USB device twice, it will work. I have tried the MBRFIX tool from Here to no avail, I have also tried the Vista Bootsect.exe tool to no avail. Here are the Diskpart commands I am running (they are all batched) Booting WinPE from CD select disk 0 clean select volume 0 assign letter=E: <<< CD Drive select disk 0 <<< Logical Drive create partition primary assign letter=C: select partition 1 active exit format c:\ /fs:NTFS /Q /Y This will work on both the SCSI and SAS RAID 5 from CD Booting WinPE from USB select volume 1 assign letter z: <<< USB Drive select disk 1 <<< Lofical drive, now 1 because USB takes 0 clean create partition primary assign letter=C: select partition 1 active exit format c:\ /fs:NTFS /Q /Y This works on the SAS RAID 5 from USB but not the SCSI RAID 5, it hangs on 'Error loading operating system' It reports that it has succeeded in all steps and if I boot off the USB drive again and check the partition, everything seems fine. If I run the same procedure again, it will work fine Before anyone asks, I have checked that the Disks, Volumes and partitions I am referencing in the diskpart commands are infact the correct ones. Please help as this is very urgent... Thanks in advance I have since discovered this also happens to the SAS drives. It only occurs when the RAID set gets deleted and recreated.