VPC 2004 SP1 - Hangs or Get "An error has occurred"
in [Virtual PC]
|
From: ohaya on 5 Aug 2006 14:30 Hi, For the record: While I was working on this problem, I referred the support engineer to this thread and to the thread that Gorgo start entitled "Virtual PC 2004 Problem". In particular, I whether, even though they didn't seem to apply, he could send me the two hotfixes mentioned in the latter thread. He did that yesterday, and I got links for: 223208_intl_i386_zip.exe 240660_intl_i386_zip.exe along with passwords for unpacking each of those. For some reason, only the password for 240660_intl_i386_zip.exe worked, so I unpacked that, and installed: vpc2004qfe899525_msdn.msp then vpc2004qfe899525_update.msp which corresponds to http://support.microsoft.com/?kbid=899525 After applying that hotfix, VPC shows "Virtual PC 5.3.582.34". Because of the password problem, I have not been able to apply the 223208_intl_i386_zip.exe hotfix. Anyway, since applying the above single patch, I've been testing on two different configurations, and so far, it *LOOKS LIKE* this hotfix has eliminated the HANG PROBLEM!! This may be just wishful thinking on my part, or may be premature, but I hope not, but so far, with several hours of testing with the same 3 guests, I have not had the hang problem occur (fingers crossed!). Here's my hardware configuration again, for the record: Motherboard: MSI K8NGM2-FID CPU: AMD64-3000 (Venice core, rev. E) RAM: ~3.5GB (3x1GB + 1x512MB) "Host" OS'es that I've applied the hotfix to: Win2K Server SP4 and WinXP Pro SP2 (32 bit) Guests' OS: Win2K Server SP4 I'll post back later, reporting how things are going, but the bottom line is that if anyone runs across a similar hang problem, especially with an AMD64 CPU, you might want to try the above hotfix. At this point, if things continue to work, I don't think I'll try to apply the other hotfix ("don't fix what is not broken"!). Thanks for everyone's help! Jim Colin Barnhorst wrote: > I have not had an issue with VPC on an AMD64 running XP x86. Puzzling. > > "ohaya" <ohaya(a)cox.net> wrote in message > news:u20k51EuGHA.4460(a)TK2MSFTNGP04.phx.gbl... >> Colin, >> >> Believe me, I wish that the answer appeared already :)... >> >> Yes, I think I mentioned that I did a memory test awhile ago, when I first >> encountered the problem. >> >> I'm getting an indication that support thinks the problem may be because >> of AMD64, I think... >> >> Jim >> >> P.S. I had VPC hang with just a single guest running last night!! So, >> it's not even the particular combination of guests... >> >> >> >> Colin Barnhorst wrote: >>> This is a long thread so I don't remember if this came up, but have you >>> run a memory test? This usage may be surfacing a ram defect. > >
From: Robert Comer on 5 Aug 2006 16:31 Thanks for the update! -- Bob Comer <Microsoft MVP Windows - Virtual Machine> "ohaya" <ohaya(a)cox.net> wrote in message news:eG1160LuGHA.4336(a)TK2MSFTNGP06.phx.gbl... > Hi, > > For the record: > > While I was working on this problem, I referred the support engineer to > this thread and to the thread that Gorgo start entitled "Virtual PC 2004 > Problem". In particular, I whether, even though they didn't seem to > apply, he could send me the two hotfixes mentioned in the latter thread. > > He did that yesterday, and I got links for: > > 223208_intl_i386_zip.exe > 240660_intl_i386_zip.exe > > along with passwords for unpacking each of those. > > For some reason, only the password for 240660_intl_i386_zip.exe worked, so > I unpacked that, and installed: > > vpc2004qfe899525_msdn.msp then > vpc2004qfe899525_update.msp > > which corresponds to http://support.microsoft.com/?kbid=899525 > > After applying that hotfix, VPC shows "Virtual PC 5.3.582.34". > > Because of the password problem, I have not been able to apply the > 223208_intl_i386_zip.exe hotfix. > > Anyway, since applying the above single patch, I've been testing on two > different configurations, and so far, it *LOOKS LIKE* this hotfix has > eliminated the HANG PROBLEM!! > > This may be just wishful thinking on my part, or may be premature, but I > hope not, but so far, with several hours of testing with the same 3 > guests, I have not had the hang problem occur (fingers crossed!). > > Here's my hardware configuration again, for the record: > > Motherboard: MSI K8NGM2-FID > CPU: AMD64-3000 (Venice core, rev. E) > RAM: ~3.5GB (3x1GB + 1x512MB) > "Host" OS'es that I've applied the hotfix to: Win2K Server SP4 and WinXP > Pro SP2 (32 bit) > Guests' OS: Win2K Server SP4 > > I'll post back later, reporting how things are going, but the bottom line > is that if anyone runs across a similar hang problem, especially with an > AMD64 CPU, you might want to try the above hotfix. > > At this point, if things continue to work, I don't think I'll try to apply > the other hotfix ("don't fix what is not broken"!). > > Thanks for everyone's help! > > Jim > > > > Colin Barnhorst wrote: >> I have not had an issue with VPC on an AMD64 running XP x86. Puzzling. >> >> "ohaya" <ohaya(a)cox.net> wrote in message >> news:u20k51EuGHA.4460(a)TK2MSFTNGP04.phx.gbl... >>> Colin, >>> >>> Believe me, I wish that the answer appeared already :)... >>> >>> Yes, I think I mentioned that I did a memory test awhile ago, when I >>> first encountered the problem. >>> >>> I'm getting an indication that support thinks the problem may be because >>> of AMD64, I think... >>> >>> Jim >>> >>> P.S. I had VPC hang with just a single guest running last night!! So, >>> it's not even the particular combination of guests... >>> >>> >>> >>> Colin Barnhorst wrote: >>>> This is a long thread so I don't remember if this came up, but have you >>>> run a memory test? This usage may be surfacing a ram defect. >>
From: ohaya on 5 Aug 2006 22:16 Bob (et al), BTW, since installing the hotfix, I've noticed that occasionally, I'm seeing some problems with what I can only describe as "video bleed-thru" among the guests' windows. What I mean by this is that if I click on a guest window that is partially under another guest's window, the guest I clicked on will come forward, but sometimes, parts of the window that we overlapped take a bit before they appear. I've been experimenting with disabling DirectDraw on the 'real' host, using dxdiag, and so far, that seems to mostly eliminate this video bleed-thru problem. I'll post back after I've had more of chance to work with this. Thanks, Jim Robert Comer wrote: > Thanks for the update! >
From: ohaya on 5 Aug 2006 22:16 Bob (et al), BTW, since installing the hotfix, I've noticed that occasionally, I'm seeing some problems with what I can only describe as "video bleed-thru" among the guests' windows. What I mean by this is that if I click on a guest window that is partially under another guest's window, the guest I clicked on will come forward, but sometimes, parts of the window that we overlapped take a bit before they appear. I've been experimenting with disabling DirectDraw on the 'real' host, using dxdiag, and so far, that seems to mostly eliminate this video bleed-thru problem. I'll post back after I've had more of chance to work with this. Thanks, Jim Robert Comer wrote: > Thanks for the update! >
From: ohaya on 6 Aug 2006 00:30
Hi, So far, so good, so good with DirectDraw disabled... Maybe I'm imagining it, but screen/window refreshes seem just a "bit slower", but that "bleed-thru" problem doesn't seem to occur anymore. I've been dealing with that "hang" problem for so long, I had forgotten how nice it was when VPC "just worked" :)!! I guess that the upside of all of that was that I was forced to give VS a try, which I'd been wanting to do for awhile. Jim ohaya wrote: > Bob (et al), > > BTW, since installing the hotfix, I've noticed that occasionally, I'm > seeing some problems with what I can only describe as "video bleed-thru" > among the guests' windows. What I mean by this is that if I click on a > guest window that is partially under another guest's window, the guest I > clicked on will come forward, but sometimes, parts of the window that we > overlapped take a bit before they appear. > > I've been experimenting with disabling DirectDraw on the 'real' host, > using dxdiag, and so far, that seems to mostly eliminate this video > bleed-thru problem. I'll post back after I've had more of chance to > work with this. > > Thanks, > Jim > > > Robert Comer wrote: >> Thanks for the update! >> |