2021-09-27, 16:32:37
re 4) Note that if you are using BitLocker and the VM lives on an external disk that you -by default- don't have access to the external disk until you login. Not sure if that is relevant for your case, but figured to mention it.
re 5) Originally the idea for storing the program's location was to be able to override it. Sadly though it gets overwritten each time you run Vimalin. But .. the important location is not so much where VMware Player lives, more important is where VIX is installed as that's the automation mechanism that Vimalin uses.
re --reload ) ... It is the very first time I hear about this. As mentioned, Vimalin uses VIX for its automation. If the VMware Player UI throws that error then it sounds like something in VMware Player going awry. What version of VMware Player is this?
re 5) Originally the idea for storing the program's location was to be able to override it. Sadly though it gets overwritten each time you run Vimalin. But .. the important location is not so much where VMware Player lives, more important is where VIX is installed as that's the automation mechanism that Vimalin uses.
re --reload ) ... It is the very first time I hear about this. As mentioned, Vimalin uses VIX for its automation. If the VMware Player UI throws that error then it sounds like something in VMware Player going awry. What version of VMware Player is this?