mediapla

I understand, i must place the I386 in a subdirectory of thr root ! This was the way i used with BCDW 1.5. I patched the bootimage/setupldr ant txtsetup. But i thougz in the new version 2.0 you can link direct to the "I386-setupldr.bin". The problem is not the diskspace - i use cdimge - its the time. I work as PC Tech with Hardware of some manufacturers,the use preactivated OEM Versions - so i have 17 XP versions on my old disk. Ive tried to be up do date, with drivers and MS-patches - but thats a lot of work, to update each of this 17 $OEM$ dir. So i hoped bcdw 2.0 can help....

Hallo, in just a beginner, but i have tried BCDW 1.5 the last time. Now i would use bcdw 2.0, because the new options looks good. But i have tried some time and DVD-RWs to install this tool and it doesnt work ! My questions : Must i also hex patch some files like at version 1.5 ? Where must be the different files of BCDW on the disk ? How is the structure of the directories, if i wanna use more than 1 different XP versions ? (At ver. 1.5 i had over 10 OEM Versions running on one DVD) Can i point the bootmanager directly to setupldr.bin ? My idea is root |-$OEM$ (for all Versions to use) |-BCDW |-LDR1(Barts PE-XPE for Recovery) |-PROGRAMS (for Bart) |-XPH1(should be the I386 from first OEMVersion) |-XPH2( I386 XPH2 the 2.) |-XPH3( " the 3.) ....AND MORE etc. Is this possible ? I have tried it out just with one Version, but if XP wanna install and format my HDD it says: "Partition cannot be formated - Maybe there is not enough memory or some files are not ok. If i point to the BartPE, it runs ! Why does windows not install.... Pleas eforgive my bad english, i hope you can understand what i mean.