WoodyZ wrote: Because only the Server versions of 10.5 and 10.6 may be legally virtualized! Anyway it is normal and expected for the size of the Virtual Machine Package to increase in size...
See more...
WoodyZ wrote: Because only the Server versions of 10.5 and 10.6 may be legally virtualized! Anyway it is normal and expected for the size of the Virtual Machine Package to increase in size the amount allocated to RAM when it is started and then when shutdown, not suspended, the size of the package decreases the amount allocated to RAM. If it is the actual virtual hard disk increasing in size then you'll have to investigate what's writing to the virtual hard disk. Also keep in mind that taking a Snapshot or AutoProtect (aka AutoDestruct) will cause the size of the package to increase. Right you are (about the virtualization legality)! I took advantage of VMWare's brief mistake to install a 10.6.8 client as a VM, primarily as a way to test if that's something that I found worthwhile to do. At some point, when I give up Snow Leopard as my primary OS, I'd like to keep the ability to use some legacy Rosetta apps. For the time being, I'll do that via keeping a partition with Snow Leopard. Later I may see if I can get my hands on a SL server copy (if it isn't too expensive). Thanks for explanation for how the VM package shrinks and grows during use.
I have a VM running 10.6.8 under Fusion 4.1. The virtual hard drive was about 14GB. I used the method described in these forums to shrink the virtual hard drive, and it shrank to about 6.5GB, ...
See more...
I have a VM running 10.6.8 under Fusion 4.1. The virtual hard drive was about 14GB. I used the method described in these forums to shrink the virtual hard drive, and it shrank to about 6.5GB, a nice savings. I then booted the VM, and shut it down immediately. It then blossomed to 10GB. What would cause a nearly 4GB increase just from booting up a virtual system? I know that virtual disks don't shrink automatically, but I can't figure out what would cause such a huge increase when nothing (other than booting) was done. Any ideas?
I wanted to restore my XP Virtual Machine to an earlier Restore Point and noticed that I have many, many restore points each day (which means I can't go back very far because XP purges old Restor...
See more...
I wanted to restore my XP Virtual Machine to an earlier Restore Point and noticed that I have many, many restore points each day (which means I can't go back very far because XP purges old Restore Points when the Restore Point list gets too large). These Restore Points all say "Printer Driver TP PS Driver..." (with the ... followed by a bunch of hex characters). Does anyone know what's going on here and how to get Fusion not to provoke XP into making all these restore points? I find I can't actually restore to any of them (I try and Windows reports that the restore was unsuccessful). I had to go back to a "System Checkpoint" Restore Point.
For me (Mac Pro 2.66/10.6.3) Fusion 3.1 is quite noticeably faster in pretty much every way...initial boot, program startup, shut down, suspension, the whole shebang. Nice!
The recommendation seems to be to run 3.1 in OS 10.6.3 but it didn't seem to be an absolute requirement. What are the downsides of running 3.1 in Leopard rather than SL?
My first attempt at upgrading to 3.1 also had a crashing problem, but it wasn't the 10.6.3 OS. Fusion would crash immediately upon startup. Redownloading and reinstalling Fusion 3.1 solved th...
See more...
My first attempt at upgrading to 3.1 also had a crashing problem, but it wasn't the 10.6.3 OS. Fusion would crash immediately upon startup. Redownloading and reinstalling Fusion 3.1 solved the problem.
OK, this isn't a VM issue! Printing to the Adobe PDF 8.0 printer is broken on the Mac side, also, so it isn't surprising it won't work on the VM side. Lots of people seem to have this issue wit...
See more...
OK, this isn't a VM issue! Printing to the Adobe PDF 8.0 printer is broken on the Mac side, also, so it isn't surprising it won't work on the VM side. Lots of people seem to have this issue without an obvious solution (on the Mac side).
I have my Fusion 2.x VM set to share my Mac printers, and a printer named "Adobe PDF 8.0#2" shows up in the XP VM, as expected. When I print to that printer from the VM, the print dialog box com...
See more...
I have my Fusion 2.x VM set to share my Mac printers, and a printer named "Adobe PDF 8.0#2" shows up in the XP VM, as expected. When I print to that printer from the VM, the print dialog box comes up and it appears to print. But, the output file disappears? Where does it go? I've tried searching via Spotlight on the Mac and via the XP search facility for .pdf files created on the right day, but no dice. Where could these files be going?
OK wiseguy ("bugs" indeed!). Thanks for your thoughts. Sometimes someone is able to say something like "it doesn't work as advertised, but if you hit CTRL-ALT-DEL while standing in a pentagra...
See more...
OK wiseguy ("bugs" indeed!). Thanks for your thoughts. Sometimes someone is able to say something like "it doesn't work as advertised, but if you hit CTRL-ALT-DEL while standing in a pentagram with a perimeter of 28 meters, it will work just fine." No such luck here, I guess. I appreciate your suggestions. That's a reasonable work around.
I'm running 2.0.6 and the printers to be shared from the Mac periodically don't show up in the VM. Sometimes those printers will reappear if I reboot the VM, sometimes they don't appear (which m...
See more...
I'm running 2.0.6 and the printers to be shared from the Mac periodically don't show up in the VM. Sometimes those printers will reappear if I reboot the VM, sometimes they don't appear (which means I can't print from the VM unless I manually add the printers). I tried upgrading to Fusion 3, but the printers have never showed up in 3. What could cause the printers to disappear and reappear, seemingly at random, and is there any fix that would get them to stick around?
Well, I "solved" it! A SECOND complete reboot of the Mac (host) (after shutting down the guest first) took care of things. No idea what's going on here. YMMV.
I installed 2.0.6 in the usual way, being sure to shut down my VM before upgrading and I restarted the Mac after the upgrade. 1. I lost my (bridged) ethernet connectivity. The settings show ...
See more...
I installed 2.0.6 in the usual way, being sure to shut down my VM before upgrading and I restarted the Mac after the upgrade. 1. I lost my (bridged) ethernet connectivity. The settings show that there is a connection, but upon starting up the VM, I get an error stating: Could not open /dev/vmnet0: No such file or directory 2. I also lost all USB connectivity. When trying to connect a USB headset I now get a message stating: Unable to connect USB device "Plantronics Headset" to the virtual machine (error code 4). Please contact technical support." I tried to disconnect and reconnect the ethernet via the suggestion in http://communities.vmware.com/thread/235440?tstart=30, alas without avail. I see that others have run into the ethernet issue, though I haven't noticed a post re the USB issue. Anyone have any thoughts here, or is downgrading to 2.0.5 the only option? Thanks!
When an earlier version of Fusion (2.0.2 I believe) broke driverless printing for me, installing 2.0.3 fixed it. Installing 2.0.4 broke it for me again (well, I don't know that for sure, because...
See more...
When an earlier version of Fusion (2.0.2 I believe) broke driverless printing for me, installing 2.0.3 fixed it. Installing 2.0.4 broke it for me again (well, I don't know that for sure, because I did some OS X software updates in there as well). 2.0.5 didn't fix it again by itself, but using the Fusion uninstaller and reinstalling 2.0.5 from scratch took care of things. I thought I'd pass this along in case it might be of help to someone else.
Well, I obviously "overasked" the question that I really was looking for. I really don't have any need or desire to know specifically the cause. As this (as far as I know) has never happened be...
See more...
Well, I obviously "overasked" the question that I really was looking for. I really don't have any need or desire to know specifically the cause. As this (as far as I know) has never happened before, at least not that I noticed, all I really wanted to know is whether this was normal/expected behavior, and you've indicated that it is, for which I thank you.
My virtual disk has been running about 13GB (the size as reported in the Mac Finder). All of a sudden, it ballooned to about 28GB. Using VMWare tools, I was able to shrink it back down again to...
See more...
My virtual disk has been running about 13GB (the size as reported in the Mac Finder). All of a sudden, it ballooned to about 28GB. Using VMWare tools, I was able to shrink it back down again to about its original size. What kind of stuff would cause the file size to balloon like that, especially since the fact that it shrank back down suggests there was nothing really important happening in the expanded part?
Is it possible to keep both 1.1.3 and 2.0? The normal installation process will install 2.0 and 1.1.3 will be gone. Is there any harm in moving the 1.1.3 app somewhere else and then running i...
See more...
Is it possible to keep both 1.1.3 and 2.0? The normal installation process will install 2.0 and 1.1.3 will be gone. Is there any harm in moving the 1.1.3 app somewhere else and then running it if/when 2.0 doesn't work well? Or is a 2.0 uninstall/1.1.3 reinstall the only way to go? Also, while I know it is not necessary to create a new VM when upgrading to 2.0, are there any advantages in a "clean" install of new VM built from the ground up?
1. Removing one of the network connections (the NAT--I kept the bridged connection) eliminated the "duplicate network name" issue. 2. I'm not sure what you are suggesting by "backup and rest...
See more...
1. Removing one of the network connections (the NAT--I kept the bridged connection) eliminated the "duplicate network name" issue. 2. I'm not sure what you are suggesting by "backup and restoring." Do you mean simply copying the VM in the Mac and then copying back, or something within Windows? Again, thanks for the help here on the forum!
