Page 1 of 1
Error: virtual display is currently set to 24 bit
Posted: 10. Sep 2011, 02:28
by Artch
Hello
I have a problem installing Guest OS - Windows 7 (64bit)
When I start the system this appears:

- When I start the system this appears:
- 9-9-2011 5-13-47 PM.png (89.73 KiB) Viewed 1718 times
Details about my Guest OS:

- Details about my Guest OS:
- 9-9-2011 5-16-19 PM.png (77.64 KiB) Viewed 1718 times
My operating system is Windows 7 Home Premium (64 bit)
Is there anything I can do to fix these problems? Please Help!

Re: Error: virtual display is currently set to 24 bit
Posted: 10. Sep 2011, 03:00
by BillG
Where did the virtual disk come from? You are obviously not doing a fresh install.
Re: Error: virtual display is currently set to 24 bit
Posted: 10. Sep 2011, 07:23
by Artch
BillG wrote:Where did the virtual disk come from? You are obviously not doing a fresh install.
Fresh install? I mounted an image (original Windows 7) using Alcohol and launched it from the VirtualBox just like everyone does it. I have no idea what's wrong.

Re: Error: virtual display is currently set to 24 bit
Posted: 10. Sep 2011, 13:12
by mpack
Actually, I did a fresh install of Vista the other day and got a very similar message. I didn't care about line-in audio, and I didn't care that the boot screen was using a strange graphics mode (I could see that!), so I just clicked the "Don't show this message again" checkbox. Problem solved.
Re: Error: virtual display is currently set to 24 bit
Posted: 11. Sep 2011, 01:53
by BillG
Artch wrote:BillG wrote:Where did the virtual disk come from? You are obviously not doing a fresh install.
Fresh install? I mounted an image (original Windows 7) using Alcohol and launched it from the VirtualBox just like everyone does it. I have no idea what's wrong.

Actually that isn't "like everyone does". Most people mount the OS install media and install an OS (ie a fresh install or clean install). You are creating a new vm from an image file. The OS is complaining that the "hardware" in the vm does not match the hardware in the image.
Have you tried the "Don't show this message again" approach that mpack suggested?