#Download mac os x vdi file iso#

The only thing you can't then do is mount the copy in a VirtualBox VM, until the UUID field in the header has been changed, otherwise it conflicts with the original. You certainly can copy them (with the host OS I assume you mean) without corrupting them. Dec 2011, 10:26 Primary OS: Solaris VBox Version: PUEL Guest OSses: Linuxes, Win8Д¬efmel wrote:It's possible that maybe I copied them before I realized that you can't copy these VDI files without corrupting them. On edit: looks like you are making some headway in the Allgemeine Diskussionen forum, but the nuances are beyond my slight grasp of Deutsch. Either by success or failure, it will take very little time to ascertain what's going on that way. vdi in VBox by applying the tutorial I linked. If you just don't know at this point, I'd suggest trying to start the. I asked in two different ways because you need to be clear on this, as it makes a difference in how we proceed.

Is this basically what we're dealing with here, something meant to be a standalone OS? Or is it a case like Etepetete described, where you are expected to attach your DOS.

#Download mac os x vdi file iso#

iso installed on it, just like a physical hard drive with an OS installed on it. vdi in the link I posted is like a little hard drive with an. vdi image? Is it supposed to result in a functioning VM? Or is it intended to be plain storage for an existing VM you already have running? )ДЄfter we get your DOS VM running you can likely create a shared folder so programs outside VBox and the VM can have access to the output like you want. (booting and running another OS on VBox is what I mean by 'Create a VM'.the running OS is called a 'Virtual Machine'.sorry about the new vocabulary. vdi has a boot sector it should be bootable, but we can't tell yet. You don't need to create one if you already have a suitable. Of course, your vm name, ostype, and memory requirements will be different, but the section about 'Use existing hard disk' is the important part. I'm trying to find a way to export what ever files are in the vdi if possible. I believe these small output files are in the vdi file since I believe it is the virtual hard drive for the DOS VM. I have a DOS application that runs on the VM DOS system and creates small files that I need to take off this computer, to use them on an older computer that runs an engraving machine. To me, the vdi file is like some black magic box that can't be broken into from the outside, you can only see it from the inside on the guest OS. I still have no way of reading a vdi file from the host, thus there is no way for me to get files from the guest virtual hard drive. Are you saying that instead of booting from an ISO file you can boot from a vdi file? If so, what would be the advantage.

Cefmel wrote:Hi allpoints, I'm not sure what you mean by using a vdi file to create a VM.