virtualbox.org

Perryg wrote:Why the xp log file? my mistake.

Anyway to start in safe mode you press f8 at boot. You have to be quick though as it gets by really fast. I will try this in a minute. been catching up on work thanks to you.

The error tells you that something has changed from the original to now. Do you have a backup of the original *.vbox (control file) that you can compare with the new one?

I tried to attach that here but got this message from the forum:The extension vbox is not allowed.

I could compare these file Perry, I don't know what to look for......

You have to change the extension to txt <guest name>.txt

Make sure you post both and that they are marked so I can tell the old from the new. I will look at them tomorrow.

Perryg wrote:Why the xp log file?

Anyway to start in safe mode you press f8 at boot. You have to be quick though as it gets by really fast.

The error tells you that something has changed from the original to now. Do you have a backup of the original *.vbox (control file) that you can compare with the new one?

safe boot in OSx: Hold SHIFT key from start up.
tried to run the win-7 machine in safe boot and got the following messages:

You misunderstood. You do not want to start the Mac in safe mode you start Windows in safe mode.
As soon as you start the guest press the f8 key (probably multiple times) and see if it gives you the options window so you can select to start in safe mode.

Perryg wrote:You misunderstood. You do not want to start the Mac in safe mode you start Windows in safe mode.
As soon as you start the guest press the f8 key (probably multiple times) and see if it gives you the options window so you can select to start in safe mode.

yeah...I tried with the working xp guest and couldn't get that not safe mode.

i will try and rename the *.vbox files ( including the -prev) and post them

thanks

Perryg wrote:You have to change the extension to txt <guest name>.txt

Make sure you post both and that they are marked so I can tell the old from the new. I will look at them tomorrow.

Here are the drop box link(s).

http://dl.dropbox.com/u/5501747/windows%207.text

http://dl.dropbox.com/u/5501747/windows%207prev.txt thank you

Ok help me out here. These appear to be identical. Is the prev from the original backup that you made? That is the one I need to compare to this one.

i have not used the win-7 machine in 4-5 weeks can the files be the same?

here they are again.

Check this setting.

Guest settings -> System -> Acceleration -> Enable Vt-x/AMD-v & Enable Nested Paging must both be enabled.

Also make sure that you have the ExtensionPack 4.1.18 installed because you have several filters set for devices in the guest settings.

Also when you added this back did you select Windows 7 64-bit for the default?

Perryg wrote:Check this setting.

Guest settings -> System -> Acceleration -> Enable Vt-x/AMD-v & Enable Nested Paging must both be enabled.
THEY WERE ENEABLED

Also make sure that you have the ExtensionPack 4.1.18 installed because you have several filters set for devices in the guest settings.
CRossing fingers-just installed it!
Also when you added this back did you select Windows 7 64-bit for the default?

Hmmm.dunno. everything about this computer is 64bit....the download choice was 4.1.18 and/64 i thought.....

NO JOY.

Well Perry I have no idea why Windows-7 will not launch or allow itself to be repaired all of a sudden after the 4.1.18 upgrade when the 2 other machines (xp-pro) launch ok.

When I get home I can reinstall windows 7. BTW, where do the machines store data saved/created on the virtual disk?

thanks for trying to solve this puzzle.

BTW, where do the machines store data saved/created on the virtual disk?

$HOME/VirtualBox VMs/{machinename}
All control files and the actual VDI file are there and Logs, snapshots are stored in folders within the structure.

Perryg wrote:

BTW, where do the machines store data saved/created on the virtual disk?

$HOME/VirtualBox VMs/{machinename}
All control files and the actual VDI file are there and Logs, snapshots are stored in folders within the structure.

OH DEAR..thus "virtual Disk Image"?

so that stuff really doesn't exist anywhere but within this program?

The main virtual drive is the *.vdi file. Make a backup of it and when you install again you can attach the original as a second drive should there be data that you need to get off of it.