Virtual Test crashes bur running in VB works

Great job!!!!!!!!

Building x64 from the downloaded Enterprise evaluation. I have VirtualBox emulation selected with 2048 allocated for memory. I get the result shown below. I tried truning off VT-x and it wouldn't even try to boot. When I set up a VIrtualBox machine using the ISO in the CD drive and the same amount of memory it fires up fine.

Oh, and "Remove Watermark" doesn't. Not a big deal.

Hi JonF,

I just reproduce  ,
I hope you have time and can help to fix,

There is "More Options" button
After using vbox plugin (and see failure screen),
click "Open Work Dir"

You will see a set of files to help development of vbox plugin,
1Debug.cmd
(which reproduce what plugin does .. )
will help you make tests faster ....



edit:
at 1Debug.cmd add
line 9 ish

Code: [Select]

cd /d %~dp0

line 23 ish

Code: [Select]

C:
cd "C:\Program Files\Oracle\VirtualBox\"

to be added to plugin after your final fix

No difference. I am not sure I put the changes in the correct places: see lines 1, 8, and 21.

No difference.

As expected 

I hope you have time and can help to fix,

What I meant (forget anything else on previous post, 1debug.cmd etc.)
 I hope you can figure out a fix 

I'll see what I can do, I'm pretty busy right now.

Using %VBOX_INSTALL_PATH% is safer than hard-coding the path.

Feel free to make any improvments 

I did, and attached it.

I mean:
Do as you like when fixing plugin,
including changing 1Debug.cmd creation the way you recommend ... 

 

same error with qEmu emulation

I'm not planning to do much more testing. I did determine that the batch file does not duplicate the actions of the script, most notably bltxtrline.exe is never executed because it's not in the current directory and a path isn't supplied, and there may be one or two other things I don't remember. But I don't know enough about what all those things are doing work on it without a long learning curve

Whenever I run the batch file it deletes all my VMS from the VirtualBox interface. Luckily I can recover them from C:\Users\Jon\VirtualBox VMs by double-clicking the vbox files.

FWIW I'm enclosing the script with the errors I found fixed.

not same on qEmu error here 

well, qEmu , even when works, quite slow to boot SE, instead it is more useful when designing/testing bootmenu ..

Same with VirtualBox, when you open "Advanced Options", and click "View Qemu Files" , you will see 1Debug.cmd which is quite useful on tests and development.
 Maybe you might be interested in making improvments on Qemu plugin in this lazy people world.


**
Thanks JonF,

Yes batch was not perfect since first day due to vbox things, it was there only to "help" to someone who have time and aim to figure out things, also to test/fix things easly.....
 If one day you (or anyone)  succeed running SE x64 iso with vbox commands with a batch in "any way", it is the day.


ps: I plan to check your plugin in some far future, I have finals, Remind me if I forget ....

 

Well your right I do not get 0X00000C4 but I get 0X000000A no matter amount of memory.
Running on a Windows8.1 (x86) with 4 GB RAM
And have to Terminate QEmu as it is not responding after the Error, resulting in "Error -805306369" in the "1Debug_ErrorExists.txt"

qEmu starts and show 1) Bios choices 2) Loading files ........ 3) Windows 8.x boot logo/picture, and then the error happens

Have now tested the ISO via ESXi and on a physical machine no issues, and I do not utilise VirtualBox

Just like https://bugzilla.redhat.com/show_bug.cgi?id=1023268  I just Run Windows 8.1 x86 as Host on a Intel I7 CPU

Using Grub4dos, on qemu stuck with Grub4dos (my initial test)

I get 0X00000C4  on both vbox and qemu when I set "MainConfiguration"-BootManager-"Auto" with x64 source.

Anyway, I hope one of you can find a solution.