Search options (Page 4 of 9)

Guys, 'Andrew' is a rookie Internet Tough Guy who has been popping up on various forums for about 6 months now.

The idiot registered with his real name, age, and zip code in a few places.

Don't worry about him.  He really needs to go back to his spiritual advisor and try to reconcile his short fuse and offensive temper with a professed love for The Lord.

The new XP Compatibility virtual machine is not the stock MSFT Virtual PC.  As I expected above, 'they say' that the new XP VM is 'highly tuned' for perfomance and desktop integration with Win7.

The XP virtual machine will require that the hosting CPU have Intel/AMD hardware virtualization.  There may also be a minimum ram requirement of 3 or 4 Gb.

MSFT could be tossing in a stripped down version of their Hyper-V virtualization manager to support all of this.  Hyper-V does require hardware virtualization where the stock Virtual PC does not.

So two things to check, look in the BIOS for a virtualization on/off/enable/disable setting and then run CPU-Z or that utility from Steve Gibson (www.grc.com) to verify support.

Early C2D and most Pentium Dual Core chips do NOT have this.  Additionally, for those machines that support VT, the option is often turned off in the BIOS (by default).

Methinks that the VM requirement is going to raise the street price of 'upgrade' CPUs (and drive down the price of non-VT chips).  So those of you with Pentium Dual and/or older C2D cpus should probably jump on the upgrade bandwagon sooner rather than later.

I also think that given the amount of integration that MSFT is promising with the new XP VM, VirtualBox (and Xen and the others) will be working very hard on their device driver addons to match the level of integration that MSFT is trying to deliver.

There are however, a set of boot-time switches for both Vista and Win7 that can only be set/managed from a specialized command-line editor.  Open up a command box as Administrator and then run bcdedit.

My new fave setting is increaseuserva which I currently have set to 2.5Gb (out of 4 Gb in the machine).  I'm running that value up 128Mb every week or so trying to find the point at which the OS starts to slow down and/or my ram-hungry applications (mostly Photoshop CS4) stop getting more responsive.

bcdedit works much the same way as the command-line tools that support WAIK.  It's a good idea to get familiar with them.

isn't this just a disguised VirtualPC runtime and XP image?

If so, it could be the basis for more legal wrangling in the EU and US such as we've seen with MSIE.

I wonder if this is the same guy who recently got banned over at Kels

or, think hard about your needs and suggestions and express them in terms that do not denegrate anyone here.

is that driver for the new cell CPU based controllers?

You've given us no information with which to 'fix the problem'.

At a minimum we need your finisher logs as well as the hwids of the machines that are giving your problems.

No one here is a mind reader or distance see-er.  We need real, hard data to work with.

What you don't want to do doesn't matter here.  There is but one way to 'fix' your problem.

what do you mean "from update"

Exactly where did you download this pack from?

just tested on vbox 2.1.4.  this addon resulted in the vmware drivers being loaded on a virtualbox instance.

more details, please.  What do you see or need.