Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Is there an easy way to downgrade back to v1.3? I just tried and it installed, but I couldn't start my VM because it said that 2.0 modified the VM. So I had to reinstall 2.0 again and I still can't install VMWare Tools, which blows.
 
I don't really care about the documents inside Windows. I'm a Mac user exclusively, and all my documents are on my Mac. I only use Windows virtual machines for Internet Explorer testing, and I have three virtual machines, one for IE6, IE7, and IE8. What I want to back up is the machines, not the documents in them.

At a RefreshDC presentation, Multiple_IEs was mentioned as a great way to test out various versions of IE in just a single VM. Just thought I'd mention it.
 
At a RefreshDC presentation, Multiple_IEs was mentioned as a great way to test out various versions of IE in just a single VM. Just thought I'd mention it.

I'm using IEtester for that:

ietester-0.2.png


http://www.my-debugbar.com/wiki/IETester/HomePage
 
multiple IE installs are never quite the same

Those work fine and dandy until you're on the phone with a client who sees some weird bug in IE6 and you don't see it in your pseudo-IE6. When it comes to the very unstable world of IE bugs, 3 or 4 cloned VMs with different levels of upgrades work great for me.
 
I had a follow-up question on something pete.d suggested, as I'm very interested if there is a way to avoid having WGA (Windows Genuine Advantage) constantly decide to require re-activation every time I switch between running the Vmware 2.0 Bootcamp and booting straight into Bootcamp (ie. normal non-VM bootcamp):

> pete.d:
> Sep 24, 2008, 01:34 AM
> For what it's worth, in both Parallels and Fusion, a workaround for this that
> I've found works for Microsoft's Product Activation (the only hardware-based
> activation stuff I personally have run into) is to ensure that the virtualized
> ethernet adapter has the same MAC address as the actual hardware adapter.
>
> In Parallels, you have to configure this in the VM settings from the host OS
> side of things (Mac OS). In Fusion, you can configure this manually in
> Windows in the network adapter properties, assuming Fusion doesn't
> reconfigure this automatically for you (I could swear I've seen it do that at
> least once, but don't recall off the top of my head whether this is reliable).

Can you explain how to make the virtualized ethernet adapter MAC address the same as the hardware?

It's easy enough to find the hardware MAC address using System Profiler in OS X. But I'm unclear on where to modify the virtualized MAC address in the VmWare 2.0 bootcamp partition? FYI (in case it matters), my bootcamp partition has XP Pro SP3 on it, and I'm using VmWare 2.0 on a MacMini.

Here's where I've gotten so far: I fired up the VmWare 2.0 Bootcamp, then (inside Windows XP Pro in the bootcamp VM) I went to:

Control Panel->Administrative Tools->Computer Management->System Tools->Device Manager->Network adapters

and then right-clicked on "VMware Accelerated AMD PCNet Adapter" and selected Properties. I couldn't find anything that said MAC address, so I wanted to check with you if I'm even in the right place? I found on the Advanced tab that there was a choice for "NetworkAddress" which was marked "Not Present" by default, but which had an empty field called "Value" that I could fill in. Is this where I should enter the MAC address? I wasn't sure, because it didn't have the format of "aa : bb : cc : dd : ee : ff" that MAC addresses usually have.

So what is the correct place and format to use do what you suggest (to change the Vmware virtualized network adapter MAC address to match the actual hardware MAC address)?
 
Go with Fusion!

I tried both and Parallels crashed or would not start at all and their support was not good. The new Fusion is awesome! I have to use it to interact with my server at work and to run Microsoft Money - works like a dream!
 
I had a follow-up question on something pete.d suggested, as I'm very interested if there is a way to avoid having WGA (Windows Genuine Advantage) constantly decide to require re-activation every time I switch between running the Vmware 2.0 Bootcamp and booting straight into Bootcamp (ie. normal non-VM bootcamp):

> pete.d:
> Sep 24, 2008, 01:34 AM
> For what it's worth, in both Parallels and Fusion, a workaround for this that
> I've found works for Microsoft's Product Activation (the only hardware-based
> activation stuff I personally have run into) is to ensure that the virtualized ethernet adapter has the same MAC address as the actual hardware adapter.
>
In Fusion, you can configure this manually in
> Windows in the network adapter properties, assuming Fusion doesn't
> reconfigure this automatically for you (I could swear I've seen it do that at
> least once, but don't recall off the top of my head whether this is reliable).

Can you explain how to make the virtualized ethernet adapter MAC address the same as the hardware?

It's easy enough to find the hardware MAC address using System Profiler in OS X. But I'm unclear on where to modify the virtualized MAC address in the VmWare 2.0 bootcamp partition? FYI (in case it matters), my bootcamp partition has XP Pro SP3 on it, and I'm using VmWare 2.0 on a MacMini.

Here's where I've gotten so far: I fired up the VmWare 2.0 Bootcamp, then (inside Windows XP Pro in the bootcamp VM) I went to:

Control Panel->Administrative Tools->Computer Management->System Tools->Device Manager->Network adapters

and then right-clicked on "VMware Accelerated AMD PCNet Adapter" and selected Properties. I couldn't find anything that said MAC address, so I wanted to check with you if I'm even in the right place? I found on the Advanced tab that there was a choice for "NetworkAddress" which was marked "Not Present" by default, but which had an empty field called "Value" that I could fill in. Is this where I should enter the MAC address? I wasn't sure, because it didn't have the format of "aa : bb : cc : dd : ee : ff" that MAC addresses usually have.

So what is the correct place and format to use do what you suggest (to change the Vmware virtualized network adapter MAC address to match the actual hardware MAC address)?

Bumping for clarity.
 
[...]Here's where I've gotten so far: I fired up the VmWare 2.0 Bootcamp, then (inside Windows XP Pro in the bootcamp VM) I went to:

Control Panel->Administrative Tools->Computer Management->System Tools->Device Manager->Network adapters

and then right-clicked on "VMware Accelerated AMD PCNet Adapter" and selected Properties. I couldn't find anything that said MAC address, so I wanted to check with you if I'm even in the right place? I found on the Advanced tab that there was a choice for "NetworkAddress" which was marked "Not Present" by default, but which had an empty field called "Value" that I could fill in. Is this where I should enter the MAC address? I wasn't sure, because it didn't have the format of "aa : bb : cc : dd : ee : ff" that MAC addresses usually have.

So what is the correct place and format to use do what you suggest (to change the Vmware virtualized network adapter MAC address to match the actual hardware MAC address)?

I guess you're waiting for me to answer the question?

Unfortunately, as I though I was clear about in a previous post, I don't actually use Fusion regularly. I tried it, but found it (just barely) unsuitable for my needs as compared to Parallels (even though I like the company much better). I have no specific information off the top of my head regarding your question.

From your description, you seem to be in the right place. The MAC address format won't always have spaces or colons; sometimes it's just the hex digits, sometimes it's the hex digits with just colons, sometimes you can enter it however you like and the software will figure it out (stripping spaces, colons, etc.).

Each network adapter, if it supports modification of the MAC address, does it differently. And VM software like Parallels and Fusion introduce another complexity, in that there may be configuration settings in the host UI that controls the MAC address (Parallels is like this).

I'm pretty sure when I was testing Fusion, I found a way to set the MAC address explicitly, but of course if you can't, yet another alternative is to change the non-virtualized Boot Camp MAC address to match whatever Fusion sets (again, that would be found somewhere in the network adapter properties, as you've already guessed).

Good luck. And don't forget to write to Microsoft and complain vociferously about their idiotic "Product Activation" "feature". Be sure to remind them how the "feature" does nothing to stop people who want to download a cracked version of Office, but it does severely impede paying customers who just want their software to work.
 
both very good apps, i don't think i'll be upgrading to parallels 4 this year.

dosn't seem worth the money, and even if the games support is better things like xtrap would except the mouse and keyboards.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.