Rich, If you've downloaded the amd64 version, run isainfo -v to make sure you're booted in 64 bit mode. Some of us are running in 32 bit mode because our wifi hardware requires nasty NDIS drivers which aren't 64 bit ready :-/
Several VirtualBox startup scripts are bash scripts and they expect bash to be in /bin/bash. On Solaris Nevada bash is in /usr/bin/bash. So edit all of the scripts in /opt/VirtualBox to point to /usr/bin/bash instead of /bin/bash. Its also possible that some of the VirtualBox package postinstall scripts also use #!/bin/bash but after fixing the runtime scripts, I was able to get VirtualBox to run on an AMD64 on Build 84 by: export PATH=$PATH:/opt/VirtualBox VirtualBox Rich Teer wrote: > On Wed, 5 Mar 2008, Darren Kenny wrote: > > >> Oh well, that was worth a try ;) >> > > Yep! > > >> The only other thing that I can think of is that you have some KDE >> configuration >> lying around that is possibly effecting how QT (the toolkit used in >> VirtualBox) >> is behaving... >> > > Bummer; I've never used KDE so that's not likely... :-( > > To rule out oddities with my user, I think I'll add a new user just > to test VirtualBox out. > > Many thanks for the help. Does anyone else have any ideas? > >
