pkeller's Posts

pkeller · ‎11-28-2022

P.S. (why does "Edit reply" do nothing??) I of course also edited the VMX file, as described here.

pkeller · ‎11-28-2022

I'll hitch a ride on this thread, since I'm trying to do the same thing. I also created an ISO, using this shell script, as suggested by @Technogeezer. I then created a custom VM with the macOS 13 pr...

I'll hitch a ride on this thread, since I'm trying to do the same thing. I also created an ISO, using this shell script, as suggested by @Technogeezer. I then created a custom VM with the macOS 13 profile; my only settings changes were to disable side-channel mitigations and set the startup disk to the ISO file. The installation starts out well enough (see first screenshot), but around the "12 minutes remaining" mark, the installer silently crashes and the VM reboots off the ISO image. I've also attached a screenshot of the last part of the Installer Log (can't copy it in text form, because I don't have VMware Tools... ;-), and I've highlighted the section I think is relevant. All I can get out of it is that the restart appears to have been delayed because it was running ReportCrash. Any suggestions?

pkeller · ‎11-26-2022

Just to close the loop on this question: I verified that you can also boot off the .dmg generated by the shell script.

pkeller · ‎11-25-2022

Yes! I'm in the process of installing, too. I see that the script uses a map with 3 partitions; I didn't do that and I suspect that's why my .dmg didn't boot. Thanks for the workaround! I will repor...

Yes! I'm in the process of installing, too. I see that the script uses a map with 3 partitions; I didn't do that and I suspect that's why my .dmg didn't boot. Thanks for the workaround! I will report this to VMware Tech Support, and report back if they find out why their regular installation process doesn't work.

pkeller · ‎11-25-2022

Thanks for confirming the problem. I'm now working with VMware's Tech Support on this; I'll post our findings as soon as there are some. I pursued exactly the same route as you're suggesting, except...

Thanks for confirming the problem. I'm now working with VMware's Tech Support on this; I'll post our findings as soon as there are some. I pursued exactly the same route as you're suggesting, except, since I didn't have a USB key that was big enough, I copied the installer to a disk image. I got that to work, but the VM was not able to boot off it. So I might just have to go out and buy a bigger USB stick (16 GB minimum), and do exactly what you're suggesting... unless you have the material to do that experiment?

pkeller · ‎11-24-2022

Update: I ended up creating my own keyboard layout using Microsoft Keyboard Layout Creator : Open Apple's Character Viewer (Edit > Emoji & Symbols). Click in the Search box and type the special ch...

Update: I ended up creating my own keyboard layout using Microsoft Keyboard Layout Creator : Open Apple's Character Viewer (Edit > Emoji & Symbols). Click in the Search box and type the special character you want (e.g. "@"). Right-click on the search result and "Copy Character Info". Paste that into a text editor and copy just the Unicode number ("U+..."). Paste the Unicode number into Microsoft's Keyboard Layout Creator. It's a royal pain, but it works – perhaps someone knows an easier way? If anyone wants a Mac-style Swiss-French layout, I'm more than willing to share! If you tried following VMware's instructions and want to clean up, you can uninstall the BootCamp drivers like so: msiexec /x BootCamp.msi.

pkeller · ‎11-24-2022

I'm trying to create a VM with macOS 12.6.1 under Fusion 13. I downloaded the "Install macOS Monterey" application, drag it into the new-VM dialog, tell it that it's macOS 12, save the machine, ... a...

I'm trying to create a VM with macOS 12.6.1 under Fusion 13. I downloaded the "Install macOS Monterey" application, drag it into the new-VM dialog, tell it that it's macOS 12, save the machine, ... and then I get the dreaded "Unable to create the installation medium" message. None of the suggested fixes for the same problem in previous versions of Fusion seem to work for me. In particular, I tried moving the installer out of the Applications folder onto my desktop, and I verified that the installation disk image was not already mounted. Does anyone have any other suggestions?

pkeller · ‎11-24-2022

I use the Swiss/French keyboard, and am trying to get the full Mac layout in Windows 11, including the Option keys commonly used for programming. I followed the procedure in the article Using an alt...

I use the Swiss/French keyboard, and am trying to get the full Mac layout in Windows 11, including the Option keys commonly used for programming. I followed the procedure in the article Using an alternate keyboard layout for a virtual machine in VMware Fusion, supplemented with the command-line method to install the BootCamp drivers, msiexec /i BootCamp.msi, described here. However, when I try to add the keyboard in Windows (Settings > Time & Language > Language & Region > Options), I do not see the promised "... (Apple)" keyboards. I do have the "French (Switzerland)" language pack installed. I don't quite understand step 4 of the instructions, "Find the language you want, and expand the language and keyboard set." That doesn't seem to work that way in Windows 11? Any idea what I'm doing wrong?

pkeller · ‎08-24-2018

I upgraded to macOS 10.13, "High Sierra", but I'm stuck with Fusion Pro 8.5 because my machine does not support Fusion Pro 10. My "standard" VMs seem to work OK, but I need to use my Boot Camp pa...

I upgraded to macOS 10.13, "High Sierra", but I'm stuck with Fusion Pro 8.5 because my machine does not support Fusion Pro 10. My "standard" VMs seem to work OK, but I need to use my Boot Camp partition too. Trying to start the machine gives the message: "Operation not permitted: Cannot open the disk '/Users/keller/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/Boot Camp.vmwarevm/Boot Camp.vmdk' or one of the snapshot disks it depends on. Module 'Disk' power on failed. Failed to start the virtual machine." The conclusion of this thread is rather laconic: can't be done. This thread, however, provides a little more information: the basic problem is that the BIOS boot data can't be read from the boot disk when System Integrity Protection (SIP) is enabled; it then shows how to fix the problem for Fusion 10. I successfully used this fix for Fusion 10 on my other machine; so I thought, what the heck, maybe a similar fix works for Fusion 8.5. I have verified that Boot Camp does indeed boot within Fusion when SIP is disabled. However, the patch to the "Boot Camp.vmdk" file (last paragraph of the fix) does not work. Does anyone understand enough of this file and the Windows boot process to figure out what the patch is doing? I imagine that the fix copies the BIOS boot data to somewhere accessible even when SIP is enabled; and I also found this document about the structure of the .vfx file. But I'm missing the know-how to imagine a fix – or to know whether it's possible. Thanks in advance!! -- Phil

pkeller · ‎02-17-2008

Unlike smcrae, I do have the OS X Keyspan drivers installed, and my Keyspan works fine with either OS X or - now that I've downgraded to Fusion 1.1 - WinXP. Note I said OS X OR WinXP - of cours...

Unlike smcrae, I do have the OS X Keyspan drivers installed, and my Keyspan works fine with either OS X or - now that I've downgraded to Fusion 1.1 - WinXP. Note I said OS X OR WinXP - of course you're going to have trouble if you try to connect a device to Fusion if it's already open in another OS X application - SerialClient in your case. It is possible that there's another layer of confusion with Leopard compatibility. I'm still running Tiger. -- Philip

pkeller · ‎02-04-2008

Add me to the lengthening list of people with USB problems after upgrading to Fusion 1.1.1. In my case, the peripheral is a Keyspan USA-19HS USB/RS-232 adapter. Fusion can connect to the device...

Add me to the lengthening list of people with USB problems after upgrading to Fusion 1.1.1. In my case, the peripheral is a Keyspan USA-19HS USB/RS-232 adapter. Fusion can connect to the device, the Keyspan software sees the device, sending data makes the LED blink - but no input, and the loopback test fails. Rolling back to Fusion 1.1 fixed the problem. As a consequence, 1.1.1 is unusable for me. -- Philip

All

pkeller's Posts

Re: VMware Fusion 13 unable to create MacOS VM?

Re: VMware Fusion 13 unable to create MacOS VM?

Re: Fusion 13 / macOS 12 : "Unable to create the installation medium"

Re: Fusion 13 / macOS 12 : "Unable to create the installation medium"

Re: Fusion 13 / macOS 12 : "Unable to create the installation medium"

Re: Fusion 13 / Win11 : cannot install BootCamp keyboard layouts

Fusion 13 / macOS 12 : "Unable to create the installation medium"

Fusion 13 / Win11 : cannot install BootCamp keyboard layouts

Boot Camp in Fusion 8.5.10 under macOS 10.13 "High Sierra"

Re: Fusion 1.1.1 breaks USB device support

Re: Fusion 1.1.1 breaks USB device support