LINK >>> https://bytlly.com/2sMGSP
then i went into virtualbox and checked the settings. they were set for the tib to be the virtual drive g. then i set the virtual drive e to be the target drive. a new virtual machine was created, and the virtual machine configuration window appeared. it had the following configuration:at this point, there was a message warning that all of the virtual hard drives in virtualbox had been added. so i followed the advice of the warning by clicking the button that would add the virtual hard disk for the virtual machine.at this point i could click the start button, and the virtual machine would start. when it did, the virtual machine would be set to the same operating system type as the virtual machine settings and the virtual machine size set in virtualbox. otherwise, the virtual machine would start with the virtual hard disk set to the default.next, i started with the process as described by vbox manual (virtualbox documentation, 2017 ), under "creating a disk image" (first edition). that started with the vhdx (virtualbox hard disk image) that i created from a conversion i had done about a year ago. it was a reasonable size, so i could start working on it immediately. it was a pretty straightforward conversion process. i started by attaching the vhd to a vm, and then ran this command:$ vboxmanage internalcommands createrawvhd -filename {.vhd} {.vhdx} tib to virtualbox converter the advantage of this command is that it gives you a file you can edit. i started with a command suggested by the virtualbox manual:$ vboxmanage modifyvm {vm name} --type hdd --hddvisorallocationmax {new size in gb} tib to virtualbox converter this command gives you a window that lets you set the size of the disk. i set it to the same size as the vhdx. i also set the vbox version to its default. that seemed about right at first, but then i noticed that i had to set the vhdx image to the default. vbox is not too happy if the original and new versions arent the same. i ended up with a disk size of about 70 gb. i didnt have to reboot to see that the vhd was no longer a file, but was now a disk image. i tried, then, to boot that disk image, but the boot wasnt complete. if i recall correctly, the boot process went into an endless loop with the message something like "cannot boot a disk on a partition". i just let it run. after about 20 minutes, the boot ended. there was a message, i recall, about being "outside the bounds of the disk". i turned on verbose mode and started to look at the messages. it turns out that there was a message about a "header of a disk." the boot wasnt complete because the original disk had changed! or so it seemed.
98329e995e
https://open.firstory.me/story/cldn9h4sx0pq701tj72y66dlz https://open.firstory.me/story/cldn9mu1i0pqe01tjccx75j1w https://open.firstory.me/story/cldn9i0ya0cv401t4hi3i5mwq https://open.firstory.me/story/cldn9hk180cv101t4733f78fj https://open.firstory.me/story/cldn9g7qy0cuv01t43keh63gs