Installating on Windows 7 x64 pre-beta?

Mugwump00 · Post by **Mugwump00** » 8. Nov 2008, 18:44

Hello - anyone else managed this? It's fine on the x86 build.

I can't get it to install on x64 - it seems to have a problem installing the kernel driver - an MSI log shows the error:

DIFXAPP: ERROR - The operating system you are running on is not supported. Only Windows 2000, Windows XP, Windows Server 2003 and Windows codenamed Longhorn are supported.
CustomAction MsiProcessDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

the install ends with an MSI 1603 error.

Anyone with better luck?

Cheers

Post by **petrossa** » 8. Nov 2008, 19:24

i got it to install as far as halfway, got unexpected error and the installer quit cleanly saying it did a rollback.

i'm going to try msi -> exe and run in compabilitymode

update:
nope, no go

Mugwump00 · Post by **Mugwump00** » 8. Nov 2008, 19:38

Nice idea.

I guess as a pre-beta it has little importance, however VMWare Workstation doesn't work on it either, so I think there is a great window of oppurtunity to get people onto VB if they can fix this quickly?

I hope someone from the VB team can comment?

Post by **petrossa** » 8. Nov 2008, 19:54

i have the vbox installation on another disk. vboxsvc.exe runs, as do all other exe's. To run vbox itself i need to know which classes/dll's i need to register, i'm sure it'll run then. Where can i find this info?

Post by **Sasquatch** » 8. Nov 2008, 20:40

Windows 7 is not a final release. VB doesn't support non-final releases of an OS. You are running a beta release and try to run a program not build for that. Don't expect support on this matter until the OS is final (and full support is build in VB).

Post by **petrossa** » 8. Nov 2008, 21:24

I see you're dutch. So am i. so i can understand you seem to be rude and abrasive, since this is normal behaviour in the netherlands.
But maybe you can lighten up a little?

Post by **Sasquatch** » 8. Nov 2008, 21:36

It's just that there are a lot of posts about this Windows 7 that it's starting to annoy me. Everyone wants things fixed and expect support from the VB team and the volunteers, while we can't do that.

kuruk · Post by **kuruk** » 9. Nov 2008, 04:27

Sasquatch wrote:It's just that there are a lot of posts about this Windows 7 that it's starting to annoy me. Everyone wants things fixed and expect support from the VB team and the volunteers, while we can't do that.

The goal of a virtual computer could be enhanced by all failure reports. Sure Windows7 is beta software but why would it break on VirtualBox ?

I would take pride in making my software not fail even when running unexpected software.

Post by **petrossa** » 9. Nov 2008, 09:09

Sasquatch wrote:It's just that there are a lot of posts about this Windows 7 that it's starting to annoy me. Everyone wants things fixed and expect support from the VB team and the volunteers, while we can't do that.

I can relate to that. There's enough things to do then to be bothered with a not yet released os which still might change and undo the work.

I wasnt asking for support just throwing the question in the community which dll's need to be registered in order to make vb running since i have disk with a full installation. If i can register it, because all other parts seem to work properly and i have yet only found one program which doesnt work on 7, i could play about and gather problably some useful info for a later date.

7 is very impressive, and looks like a real winner. Even the 6801 version has no real isues i noted. And i did try to make it suffer.

http://www.virtualbox.de/wiki/User_FAQ · Post by **stefan.becker** » 9. Nov 2008, 12:15

kuruk wrote:
Sasquatch wrote:It's just that there are a lot of posts about this Windows 7 that it's starting to annoy me. Everyone wants things fixed and expect support from the VB team and the volunteers, while we can't do that.
The goal of a virtual computer could be enhanced by all failure reports. Sure Windows7 is beta software but why would it break on VirtualBox ?

I would take pride in making my software not fail even when running unexpected software.

What do you expect?

Every VM-Solution can only support an OS that is final when the VM-Release appears.

Post by **Sasquatch** » 9. Nov 2008, 16:02

kuruk wrote:
Sasquatch wrote:It's just that there are a lot of posts about this Windows 7 that it's starting to annoy me. Everyone wants things fixed and expect support from the VB team and the volunteers, while we can't do that.
The goal of a virtual computer could be enhanced by all failure reports. Sure Windows7 is beta software but why would it break on VirtualBox ?

I would take pride in making my software not fail even when running unexpected software.

If you're so eager to test it, why not dedicate a partition and install it on bare hardware? Don't blame the VM producers if it doesn't work as it should.

Mugwump00 · Post by **Mugwump00** » 9. Nov 2008, 18:58

I could write a snotty post about the stability of pre-beta Windows 7 being something of a lesson to some, that the Windows platform can do amazing things when people concentrate, but that would not be in the spirit of how I feel about VB to-date, which is that it is an amazing achievement.

I've switched to VPC, which works and, remarkably, seems to run about 5x faster than I remember it doing so on XP with no VT-x. And the VMs reboot on command. Which is nice.

Look forward to all future developments. Nothing tested, nothing gained.

Cheers