FATAL: INT18: BOOT FAILURE

[Stamimail]

Hello,
I've a problem with Virtualize my computer (make a virtual copy of it) with Paragon Go Virtual. After making a Vmdk file with this software, and loading it in VBox [the same computer], I'm getting this: "FATAL: INT18: BOOT FAILURE".
I followed the instructions in comments in http://dottech.org/freeware-reviews/16940/ and it stiil doesn't work.
I also followed http://windows.microsoft.com/en-us/wind ... tup-repair and downloaded CyberNetNews.com_Windows_7_64-bit_Repair_Disc.iso, load in Vbox, operate the startup-repair option and... it stiil doesn't work.
What is the problem?

[mpack]

Being in VMDK format (a supported format) is not enough to ensure that VMWare VMs will run in VirtualBox without a problem. It very much depends on what "Paragon Go Virtual" did besides imaging the host drive. For example, did it install VMWare GAs which are incompatible with VBox? For that information you would have to ask Paragon.

[Stamimail]

I can load the Vmdk file as a non-bootable Hard Drive (boot from other Vdi file), and use folders and files of the Vmdk file. Doesn't it mean the conversion was correct?
If the Paragon tool is the problem, Do you know a good Free P2V Tool for VBox? Please, put a link.

[Perryg]

http://technet.microsoft.com/en-us/sysi ... s/ee656415

[Stamimail]

Thank You. I knew this tool. I'm looking for Disk2Vdi?

[Perryg]

Nothing works better for converting Windows, and you can convert it to a VDI file later or leave it a VHD (which VirtualBox also supports)
But you need to find that out for yourself. Plus there is no disk2vdi that I know of, except the long track of imaging and then repairing it to fix the no boot issue.

[Stamimail]

In my case, converting the Vmdk file to Vdi file (by conversion software) can help? Is this because of the format file?

[Perryg]

I think you will find that the whole paragon route is where you are loosing it. But that is just me. If you miss a step or don't do everything just right then you have issues and need to actually use the install CD/DVD to fix the MBR, which is where you are now if I am reading this right. With disk2vhd you just run it drop it in VBox and go for it. You will of course need to fix a ton of issues no matter how you go, due to the different drivers from metal to virtual. Anyway its worth a try right?

[Stamimail]

I think I've a problem to create a new virtual hard disk again by Disk2Vhd since the source partition has changed. The original partition was about 40GB (and in ideal state) and so the Vmdk file I have made. Now, This partition is about 120GB and this is a long way for me to return this partition to the previous state. [Also, I didn't get a Windows7 installion DVD disk while purchasing my laptop (but there is a recovery partition)]
Is there a more simple way or a special tool that can fix my Vmdk file from inside?
Thank you.

[stephanboy2030]

Operating system Ubuntu 10.04.3
Guest OS CentOS 6
VirtualBox version 4.1.4

I solved moving the .vdi file from a ext4 partition into a NTFS partition. I done this transfer using Virtualbox, and not simply using copy and paste.

[Stamimail]

I found the problem.
I needed to mark the partition as "active".
http://www.microsoft.com/resources/docu ... x?mfr=true

I used Windows 7 System Repair Disc:
1. Command Prompt --> Diskpart --> ... --> ACTIVE
2. Restart and letting the Windows 7 System Repair Disc to do the rest work.

I needed to run "Startup Repair" twice to make Windows work.