VirtualBox.script, Version=051 no longer functions

Hi All,

My Win7pe_se has a minor problem. The VirtualBox.script, Version=051 no longer functions since I started doing Win8pe_se builds on another separate hard drive (totally independent of Win7pe_se). This is probably just a coincidence, I think.

The VirtualBox.script Log reports it runs and concludes without error. But, nothing happens.  Not even a Warning.

At the moment I am simply running the iso built manually in VirtualBox.
The peculiar thing is, a week or so ago it was working fine. Now, it just does not work at all.

The same version script with exactly the same settings works perfectly in Win8pe_se, just not at all in Win7pe_se.
I updated the VirtualBox to the latest release about 3 weeks ago.
I have updated both Win7pe_se and Win8pe_se from the server today with no improvement to this problem.

This is a minor inconvenience of course.
Can anyone suggest something I should look for..?

Regards,
BobxT

The last changes made to the VirtualBox script is the addition of the option I/O ACPI.
which seems required for x64 building http://theoven.org/index.php?topic=576

By disabling "enable I/O ACPI" checkbox, you have the same script as before.

The last changes made to the VirtualBox script is the addition of the option I/O ACPI.
which seems required for x64 building http://theoven.org/index.php?topic=576

By disabling "enable I/O ACPI" checkbox, you have the same script as before.

Hi ChrisR,

I saw that other post and tried it. No change.

I disabled "enable I/O ACPI" checkbox.
I also tried another build with "Turn off VT-X", still not working.

BobxT

Hi BobxT

Then I do not know,
I mainly use VMware and VirtualBox works here.
Try May be to play with the advanced options (more options).

Hi ChrisR,

I have had a look at the Advanced Options.

I have tried various others. Next will be to find my backups of the earlier scripts and see what if anything happens.

My personal hunch is that it is something weird with VirtualBox, perhaps VB is getting confused with me running Win8pe_se as well as Win7pe_se.  (Although not at the same time, of course.)

Not a show stopper, I will look at it some other time and get back here when/if I find anything of interest.

Regards,
BobxT

I build win7x64 on a wun7x64 machine (no win8 stuff), but it works fine for me.  I am a newbie at this (long time {former} BartPE user) and it didn't work for me at first. But I updated my virtual box to the latest one and had then hacked the script to add the "enable I/O ACPI" along with a couple of other options in order for it to boot in the VM.  Not at home now,so can't reference my changes right now - but in order for it to work on my Win7 x64, I had to have the ACPI option on.  Are you saying that the win7x64 build does not boot unless you start it manually from virtual box?
Currious...are you able to build the win8 from win8 source ON a win7 machine?   

I build win7x64 on a wun7x64 machine (no win8 stuff), but it works fine for me. 

I am a newbie at this (long time {former} BartPE user) and it didn't work for me at first. But I updated my virtual box to the latest one and had then hacked the script to add the "enable I/O ACPI" along with a couple of other options in order for it to boot in the VM.  Not at home now, so can't reference my changes right now - but in order for it to work on my Win7 x64, I had to have the ACPI option on.  Are you saying that the win7x64 build does not boot unless you start it manually from virtual box?

Currious...are you able to build the win8 from win8 source ON a win7 machine?   

Starting again as my login expired..

I tried all those settings but no different. I also tried reverting to an earlier VirtualBox.script #050 and it was no different.
I am thinking that there is something weird within my OS installation of VirtualBox on this computer.

MY Win7pe_se is x86 and this is a Win7 x86 Operating System. After a build run I can boot from my Win7pe_se x86 iso if I manually attach it to a Win7 x86 guest within VirtualBox. The same iso just will not run automatically at the end of a Win7pe_se build run.


Off Topic - YES.
I am ALSO building Win8pe_se x64 on the Win7 x86 system. I use a Win8 x64 source from Microsoft. It is the Windows 8 Enterprise Evaluation x64 for developers 90 day Trial version and the link for this is on the opening screen of the Win8pe_se builder program.

VirtualBox supports x64 Windows Guests on a Windows x86 Host.

Regards,
BobxT

AHHH, so the iso itself would seem to be ok, just not running from the script.  Weird.  I have had a problem - several times now - as I create scripts, that causes the iso to be made but it does not run in vbox.  No errors in the log.  However, in my case the iso craps out during the load into windows, windows complains of a possible hardware change.  Nothing consistant in the 'bad' scripts but it does seem to be the ones where I make registry entries.
At any rate, my virtual box settings are to use 2048MB virtual memory/64MB video ram/2D accel on/USB 2/bridged network/Virtbox HDD/APIC on/Bidirectional clipboard (not working since build lacks Guest additions). in the vbox, I also enable PAE/NX, VT-x,Nested paging,direct sound.
btw I have run it without the virtualbox HDD and it is fine.
The version is 4.2.10 r84104
The vbox manual says: (tho maybe not significant since manual load is working)
64-bit guests on some 32-bit host systems with VT-x can cause instabilities to your system. If you experience this, do not attempt to execute 64-bit guests. Refer to the VirtualBox user forum for additional information.

NX (no execute, data execution prevention) only works for guests running on 64-bit hosts or guests running on 32-bit hosts with PAE enabled and requires that hardware virtualization
be enabled.

As I thought about this, perhaps there is something amiss in how the script forms the command line when call the vbox manager.
I just ran the script on my machine and zipped the html version of the log.  Maybe it can help?

As I thought about this, perhaps there is something amiss in how the script forms the command line when call the vbox manager.

I just ran the script on my machine and zipped the html version of the log. 
Maybe it can help?

Huge amounts of EGG ON FACE..!
I compared your log to mine and your clue about "the script forms the command line when call the vbox manager" made me look at near the end of yours and my script logs.

It suddenly dawned on me what I had done.

I had renamed the opening screen title of the WinBuilder interface project screen "Win7PE SE" to read  "Win7PE SE - Choose which Acronis Imaging program required..!".

I did that to remind me to choose which of two Acronis programs to pick before building.
They are both mutually exclusive and as I often forget, I wanted an "in my face" reminder.

I do this a lot on individual scripts as well as alter the fonts within the scripts to increase the font display size on screen and to place notes within some scripts. (I wish WinBuilder would have font display settings.. )

It would appear that the VirtualBox.script it parsing the NAME from that interface opening project screen DESCRIPTION.

Thanks Voltaire.

I feel like an idiot.. 

Regards,
BobxT

Starting again as my login expired..

To avoid disconnect, you can click on the login link at the top right and on top of the login button.
and choose the time to stay connected or Always stay logged.

Maybe Galapo can increase the default timeouts, which seems short indeed.

Starting again as my login expired..

Yep we all lived ;) and learned ;)
The main trouble is current free forum engine do not have a nice cache mechanism to keep written text...

Maybe Galapo can increase the default timeouts, which seems short indeed.

Currently an hour as default ;)
 besides an hour passes quickly  so maybe 2 hours or 3 ......

To avoid disconnect, you can click on the login link at the top right and on top of the login button.
and choose the time to stay connected or Always stay logged.

Best way 

I bumped it up to 3 hours.

Regards,
Galapo.