Just ran dxdiag on my iBook G4 under VPC7 windows 2K and got a reported CPU speed of 300Mhz "Processor Virtual CPU P6, MMX, 300Mhz"
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Has anyone played with Virtual PC 2007 lately?
- Thread starter cammykool
- Start date
- Sort by reaction score
DXDiag results are useless unless you run a DirectX game, also DirectX versions above 8.0 seem to poll system info differently vs CPU Z(active CPU status).
That is one reason why any VPC user should maintain a clean backup of their most patched Win2k/XP. .NET failures in my experience are often from a .NET application/Windows crash or rare unexpected VPC crash. Also stability of some .NET products gone out the window during the XP SP2 to SP3 changes, any program which used the Windows IE URL/search widget API on the taskbar(removed in SP3) will break .NET via BSOD/hard freeze(VPC or physical PC). Thankfully the stupid framework issues never impacted Vista.
That is one reason why any VPC user should maintain a clean backup of their most patched Win2k/XP. .NET failures in my experience are often from a .NET application/Windows crash or rare unexpected VPC crash. Also stability of some .NET products gone out the window during the XP SP2 to SP3 changes, any program which used the Windows IE URL/search widget API on the taskbar(removed in SP3) will break .NET via BSOD/hard freeze(VPC or physical PC). Thankfully the stupid framework issues never impacted Vista.