While no comment from Apple specifically, I doubt that VMWare's legal department would have allowed this to happen without at least some prior contact.
Very good, indeed!
And a very interesting article, the one from Macworld above.
BTW, it is also interesting to note that when installing the client versions of Leopard and Snow Leopard, first it runs as a Server install (with only English, French, German and Japanese available as languages to choose); once installed, one can then change the language to the preferred one.
Good also to have consistent names of the various Mac OS X versions when creating the VM: Mac OS X [Server] 10.5/10.6/10.7 (64 bit).
... And from the article:
[...] Fusion’s support for Windows includes a Unity mode that lets Windows apps float among your Mac windows. Virtual Macs will only display inside a window or filling a screen in full-screen mode [...]
So, for Fusion 4.2 (or Fusion 5) it would be a good thing to have Unity also for Mac OS X guests...
Yes, of course: but - as Fusion should ideally be the excelsior of virtualizers on the Mac platform - noblesse oblige (and the former default Mac OS X classification was something of a mess)...
In other words, a little more elegance - here in the default VM names - is a good thing.
That said, I, too, often change the names of the VMs: for example, I remove the "x64" (not needed, if one only runs 64 bit VMs of an OS), and add, for example, "11.10" to Ubuntu VMs.
Returning in topic, a (good, positive) common sense eventually has prevailed, for virtualizing Mac OS X (and probably that's OK also for Apple, even if they haven't yet explicitly changed the EULAs)...
P.S.: One of the international Mac sites I usually read already talks about it:
... with the title (translated) Fusion 4.1 virtualizes Leopard and Snow Leopard and can bring back Rosetta to Lion.
BTW, that means being able to run, for example, also AppleWorks and other "historical" programs in Lion; if only there were Unity view, now...
As I said before, for international users that want their own language, the OS language must be changed after a (Snow) Leopard installation in Fusion 4.1; here, for example, is how to do it:Be sure to do also the last step, in the Terminal:$ sudo /System/Library/CoreServices/Language\ Chooser.app/Contents/MacOS/Language\ Chooser... which sets the master language system-wide.
> when installing the client versions of Leopard and Snow Leopard, first it runs as a Server install (with only English, French, German and Japanese available as languages to choose); once installed, one can then change the language to the preferred one.
> for international users that want their own language, the OS language must be changed after a (Snow) Leopard installation in Fusion 4.1
Weird, this is not what I see. When I create brand new Leopard Client and Snow Leopard Client VMs in VMware Fusion 4.1 (using File > New...), everything seems to be working as expected with respect to language selection. See attached screenshots.
Yes, you are right, of course; and, guess what, the cause of the server-like install behavior was a more than trivial error: I had simply forgotten to remove the ServerVersion.plist file from /System/Library/CoreServices on the install DVD images (which I had modified some time ago, when this little hack was still needed in order to experiment with the client versions).
Thank you for the heads-up!
(Now, I will reinstall Leopard and Snow Leopard with the correct client settings: it's always a more elegant solution...)
Edit: Changing the language is not necessary; see the comments below:
The Max OS X (Snow) Leopard language chooser indeed works fine during the client install.