The URI of a Bonjour share always ends with “._smb._tcp.local” including “local” as the Bonjour TLD. Bonjour networking works best because it is not dependent upon DNS services or fixed IP addresses. This works because VMware installs a network bridge-router on the host system for use by virtual systems. Then, mount the shared folder on the virtual macOS system using Bonjour networking. To enable this, activate file sharing for a macOS folder containing Helix Collection files by adding the folder to the list of Shared Folders in the Sharing Preference Pane of the host macOS system and set the access permissions appropriately. Our macOS systems provide this functionality natively using macOS file sharing. I witnessed this twice before finding the root cause.įortunately, neither of these methods in necessary for sharing convenient access to Collection files between the virtual and host systems. When the two versions of the Collection structure loose synchronization, then the Collection file appears to be irreparably damaged when opened by Helix applications running on the virtual system. When a file in a VMware shared folder is a Helix Collection file created by a version of Helix before version 8, then the Collection structure is stored in a resource fork extended attribute. The result is that files accessed by the host system acquire extended attributes which are out of synchronization with the companion files created by the virtual system. The host macOS system knows that the files are actually stored on macOS storage volumes, so the host system ignores the companion files. Companion files share the name of the their main file prepended with “._” causing the companion files to be invisible. One of these two files contains the main data portion, and the other “companion file” contains the extended attributes. The result is that macOS files stored in shared folders by the VM use the apple-double format. This feature uses a file sharing service installed by VMware that treats all storage as non-native to macOS. Completely avoid using the Shared Folder feature of VMware Fusion.
0 kommentar(er)
