Postage-Stamp Images: 4 Screen Images of a VM's console can be active - That is a drain on system resources with little benefit. Exception: Is a VM is suspended or not - that is useful information, but 4 Screen Images just to know a VM's state? A bit of text would suffice and without the cycles to copy/present as the VM's screen changes. Suggest a WowFactor-Disable/Enable toggle (stopping the cycle steal) under Settings for each VM.
Lock files: Why all the persistent '.lck' files for all VMs in the library? Just because the "Virtual Machine Library" is open? Postage-Stamp Images? If a VM configuration needs to be copied (or edited), Fusion must be terminated and that also terminates all other running VMs! Wait until next week, day, month, an hour or six while the other VMs do their assigned tasks? The lock should be acquired if and when the VM's configuration files are being updated (Settings, changing displayName) and then released.
BIOS Capabilities: You use the "Operating System" selection as criteria for setting the capabilities of the the motherboard configuration: IDE vs SCSI, BCD store or not. This may preclude configurations useful for testing (BCDEdit under XP).
Hard Disk contraction: You have a product called VMware Converter with purpose of assisting in migrating to Virtual Machines. One of its capabilities is to contract hard disk allocation as a hard disk is cloned. Hint, hint. Some porting work? (But without seizing up all of Fusion.)
PC Tools AntiVirus had to be uninstalled (removed) and reinstalled for Fusion V2. Suggest that it be removed before installing V2. I removed it after V2 and went thru a few BSOD (0x7E, 0x24) before XP would stay up long enough to reinstall it.
Back to v113 after rebooting OSX off this Alternate system
