I've tried it on two machines with the same result.

* clean install VPC07 SP1
* Create a WinXP (gold) VM.
* Install the "VM Additions" to access the host (vista ultimate) shared folder

*** My color quality (display props settings) goes to Lowest (4 bit). It
looks horrible. Is this a known issue?

Machine specs:

Dell Inspiron e1405 laptop, 2G RAM, 320G HDD, 1.8Ghz duo core, Intel 945GM
video card (shared video memory).

winXP VM has 512 mb RAM, 65G VHD (default). Everything else is default.

On Fri, 7 Nov 2008 21:41:00 -0800, betadude
<betadude@xxxxxx> wrote:

>I've tried it on two machines with the same result.
>
>* clean install VPC07 SP1
>* Create a WinXP (gold) VM.
>* Install the "VM Additions" to access the host (vista ultimate) shared folder
>
>*** My color quality (display props settings) goes to Lowest (4 bit). It
>looks horrible. Is this a known issue?
>
>Machine specs:
>
>Dell Inspiron e1405 laptop, 2G RAM, 320G HDD, 1.8Ghz duo core, Intel 945GM
>video card (shared video memory).
>
>winXP VM has 512 mb RAM, 65G VHD (default). Everything else is default.

There have been several reports on this color depth issue lately...
Personally I have encountered it in VirtualServer 2005 about 8 months
ago. I installed VS2005 latest version on an XP-Pro host and then I
created a guest using a VHD I already had created with VPC2004 a while
back.
VS2005 complained that the additions were out of date so I uninstalled
them inside the guest, then installed the VS2005 additions and BANG!
The color depth dropped to 4 bits and screen size also suffered!
By uninstalling the additions I was back at normal screen resolution,
but no integration of course.

I could only get mouse integration back (after several iterations) by
uninstalling the VS2005 additions and installing the VPC2007 (no
service pack!) additions. Complain or not from VS2005, after that it
worked as expected.

I think that the VS2005 and VPC2007 versions prepared to handle Vista
guests are the culprits here! That happened in the service packs...

Try to get hold of VPC2007 (before SP1) and extract the additions iso
from that, then manually insert that ISO file in the guest CD and
install additions from it. I think it will work much better.

Of course if you want to run Vista as a guest, you need the newest
additions, but why would you want that?

--

Bo Berglund (Sweden)

"Bo Berglund" <boberglund@xxxxxx> wrote in message
news:u7oah4h3p35ncf6kub4qdh88v7363e8e9f@xxxxxx

> Of course if you want to run Vista as a guest, you need the newest
> additions, but why would you want that?

I have several Vista guests: one with loads of different web browsers
installed so that I can test my web applications without cluttering up my
DEV machine with loads of different browsers, one for testing beta software,
one for testing how my WinForms apps run on Vista Home Basic with low RAM
etc...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

On Sat, 8 Nov 2008 12:05:43 -0000, "Mark Rae [MVP]"
<mark@xxxxxx> wrote:

>"Bo Berglund" <boberglund@xxxxxx> wrote in message
>news:u7oah4h3p35ncf6kub4qdh88v7363e8e9f@xxxxxx
>

>> Of course if you want to run Vista as a guest, you need the newest
>> additions, but why would you want that?

>
>I have several Vista guests: one with loads of different web browsers
>installed so that I can test my web applications without cluttering up my
>DEV machine with loads of different browsers, one for testing beta software,
>one for testing how my WinForms apps run on Vista Home Basic with low RAM
>etc...

Yes,
but very often people asking here have installed VPC2007 on Vista in
order to be able to *also* run XP because they have software that
won't install in Vista or they are plain more comfortable with XP.
I assumed this was one of these cases....

--

Bo Berglund (Sweden)

"Mark Rae [MVP]" <mark@xxxxxx> wrote in message
news:uVbuXpZQJHA.3876@xxxxxx

> "Bo Berglund" <boberglund@xxxxxx> wrote in message
> news:u7oah4h3p35ncf6kub4qdh88v7363e8e9f@xxxxxx
>

>> Of course if you want to run Vista as a guest, you need the newest
>> additions, but why would you want that?

>
> I have several Vista guests: one with loads of different web browsers
> installed so that I can test my web applications without cluttering up my
> DEV machine with loads of different browsers, one for testing beta
> software, one for testing how my WinForms apps run on Vista Home Basic
> with low RAM etc...

I have a Vista Business guest (also 2 XPs and a Server 2003) all running in
VPC (non SP1) on Vista Ultimate 64. All run fine.

I also had this problem with the vpc07sp1 additions dropping my video
resolution to 4bit. I promptly exited the vm & selected cancel the changes
(ie like uninstalling, but no need to do so if it wasn't saved to the vhd).
From another post above yours:

"
Yes,
the screen corruption problem does not hit everywhere. There must be
something else undrlying this problem, but I did not find it so I
moved to an earlier vmwdditions release and all was fine."

Thank you. After playing around for a while, I noticed that if I installed
WinXP SP2 & 3, I could get the resolution back. It looks like VPC SP1
requires at least WinXP SP2, but it's not detailed anywhere that I'm aware of.

Now, it's working like a charm, but it make me waste a lot of time. FWIW, I
also noticed that if you limit the size of VHD (say 5 gig), after installing
"additions", you can't even get to a shared folder from the host.

So, here's what needs to happen:

* install VPC07 SP1
* create new VM
* install WinXP (gold) - original released version w/out any Service Pack
* install VPC "additions" - screen resolution goes wacky
* install WinXP SP2, then SP3
* resolution goes back to normal and all seems OK from the point on

"No1ishere" wrote:

> I also had this problem with the vpc07sp1 additions dropping my video
> resolution to 4bit. I promptly exited the vm & selected cancel the changes
> (ie like uninstalling, but no need to do so if it wasn't saved to the vhd).
> From another post above yours:
>
> "
> Yes,
> the screen corruption problem does not hit everywhere. There must be
> something else undrlying this problem, but I did not find it so I
> moved to an earlier vmwdditions release and all was fine."

I can't figure out the problem with mine. Here's my pc spec's,

Vista Ultimate 64 bit (all the way updated but the new search program from windows)
4gb of ram
AMD Phenom 9950 2.6GHz
BFG GeForce 7600 GT OC SLI 256mb
Motherboard is a ASUS Crosshair II Formula (Latest Bios)

All this and with the newest Virtual PC 2007 sp1. When I make the new vpc when it goes to start it up and restarts the whole pc. It didn't do this when I ran it on my 32bit before I upgraded to 4gb of ram and install the 64bit os. I've reinstalled four times and still does it. IS anyone else getting this? Or will they get a little further and then it reboot the host pc? Hope anyone can help :-)

It sounds like you have a hardware problem, and since you upgraded the
RAM last, I'd take the new RAM out and try it then just as a test, if
it still blows up, you can at least know it's not the new RAM.

--
Bob Comer


On Sat, 15 Nov 2008 01:03:31 -0600, Chronologic
<guest@xxxxxx-email.com> wrote:

>
>I can't figure out the problem with mine. Here's my pc spec's,
>
>Vista Ultimate 64 bit (all the way updated but the new search program
>from windows)
>4gb of ram
>AMD Phenom 9950 2.6GHz
>BFG GeForce 7600 GT OC SLI 256mb
>Motherboard is a ASUS Crosshair II Formula (Latest Bios)
>
>All this and with the newest Virtual PC 2007 sp1. When I make the new
>vpc when it goes to start it up and restarts the whole pc. It didn't do
>this when I ran it on my 32bit before I upgraded to 4gb of ram and
>install the 64bit os. I've reinstalled four times and still does it. IS
>anyone else getting this? Or will they get a little further and then it
>reboot the host pc? Hope anyone can help :-)

Robert Comer <bobcomer-removeme-@xxxxxx> wrote:

>It sounds like you have a hardware problem, and since you upgraded the
>RAM last, I'd take the new RAM out and try it then just as a test, if
>it still blows up, you can at least know it's not the new RAM.

memtest86 A comprehensive, stand-alone memory diagnostic.
www.memtest86.com
Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

Note that a friend had some memory problems found by memtest86.
Interestingly enough swapping the memory was enough to fix the problem

<rant>For the extra few $$$s it would cost I wish that all
motherboards supported ECC Ram and that ECC Ram was all you could
purchase.. GRRRRR </rant>

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/