Does not work if VMware Fusion.app is moved from default location in /Applications

[diamondsw]

Probably not a common issue, but this script (or the commands it calls) fails when VMware Fusion has been moved (I'm still a diehard organizer all these years of OS X later). If it's possible to work around the issue (for instance, locate the VMware Fusion executable and use relative paths from its location) that would be best, but at the very least present an appropriate error message.

[mikew]

Not super worried about this, and I wouldn't want to write something that's scanning for possible VMWare Fusion locations. How would an environment variable suite you? IE:

VMWARE_FUSION_PATH=/directory/containing/fusion fusion-make-bootcamp

[diamondsw]

That would work I suppose; I was hoping there would be a LaunchServices api that would allow finding an application bundle based on its id (e.g. com.vmware.fusion, etc). It's certainly not a common case - but also one that shouldn't crash.