I now use these variables:ĪPPEND initrd=/images/Boot1.ima Image_Dir=Ghost2 Batch=G.Bat The variables are transferred (from Linux to DOS) with ‘GetArgs.Com’. I think they started as small (readable) batch files and growed, in time, to a big mess (sorry….) Yes, I checked the original ‘dosubcd.igz’ file, but these files aren’t made for reading. Just rename your '*.Img' file to '*.Ima' and it will boot in & Chew. I too am a dos/windows guy so anything to do with linux sends me straight to & imA files are the same. However luckily enough isolinux can boot the kernel upon which true image runs. However the bootpart of the iso cant be run as a bot image. Acronis true image can be made into an iso and then burned to make a bootable cd. These are the kernel loading instructions that have to go into the acronis true image custom.cfg menu file (in the file /custom/custom.cfg). Explain me “APPEND initrd=/custom/acronisf/ramdisk.dat /S quiet vga=791 load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=32000” Then extract all the files in the root directory of what would be the cd if you burned it. When you download the ubcd iso you have to open up the iso with something like isobuster or even win rar.
Which files “Extract the ubcd files from the iso image”, please by name.Īll the files. Ubcd can be edited to boot certain software available as bootable cd's but that isnt't the same as booting an iso.
