In this article, we are going to identify some of the possible causes that can cause the Virtualbox import error when loading the operating system, and then I will give possible solutions that you can try to resolve this issue.
mpack wrote: ps. I don’t click on any external links, explicitly disguised links that just say “Please” check and don’t provide a description!
Got it. But I couldn’t post types created with external links (or [url] bbform tag cloud) because the forum required more than one post, 1 account and daily subscription. (A very clever anti-spam scheme Alt = “: D” )
And I assure you that I had no such adulterous intentions. I have tried to list a number of actions I have taken and have included them as sources. If you don’t have them, take a look, I’ll list them here.
IN LINUX MINT
1. An attempt was made to load the vmdk file in vbox (linux) by creating a new virtual machine ==> “ERROR GETTING LOADED OPERATING SYSTEM” 2. Disabled devices on floppy / CD-ROM, including Settings -> System Menu (I thought the system boots from the wrong device), but no changes. The product is activated again.
IN WINDOWS 7
1. Previously started working on VM in vmware ==> Get “OS LOADING ERROR” 2. Google solutions for your own. Try changing the hard disk controller (I don’t know how, there are just all the options for choosing different SCSI ports (SCSI 0: 0, SCSI 0: 1, .. … !! .. .. .. !!!. …. just. tried. other. locations …. no changes.)
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
b. An attempt was made to change the controller from the BIOS (“POWER using ON TO BIOS” … found only in the Primary Master option in the BIOS setup on the VM disk Set to (AUTO) … the rest of the parameters were empty .. tried who can set (AUTO -> USER TYPE (no change to some other suboptions) -> CD_ROM) … no change.
in. Installed Vbox on Windows and tried it I. Change controller to SATA as per this post
II.
Code: Choose almost any ViewCollapse Extend View
vmware-vdiskmanager.exe -R "c: blah my vm disk.vmdk"
(From the same article, 2nd solution with Windows rescue CD … “MS downloaded the installation document from the Windows XP / 2003 / VISTA CD (ISO file)”
this site .. mounted and tried to load from the game .. failed .. only black screen.
III. Another bootable disk downloaded from here
(There is no way to getboot from XP CD / DVD so you can) … select the “Restore (R)” option on the setup screen .. ..tried “fixmbr, chkdsk” … little changed either.
In this version I have disabled the agp440 service … still very little change.
E. Vbox completely removed …. Vbox tried it (no change). f.Vbox removed, Vmware installed … Completely unchanged g. vbox is installed No, replace.
RETURN TO LINUX MINT only one. Converted back to vmdk vdi on Linux unix system 2. New vm vdi combined with … no luck
Well, these are certainly pretty random methods I’ve tried, including various posts (pretty useless, I think) … but it might just be like that. I have not made any configuration changes on any of the systems.
I hope they light something up. (even now all links have some context)
I want to try and recreate this electronic device, although I did not use a USB stick during the process (and the original destination of the process was usually on the same 300GB hard drive).
) 
