gringley's Accepted Solutions

I am still using these instructions I got from an older message in this forum I think: From inside the VM using a terminal session I issue the following command cat /dev/zero > wipefile; rm wipefi... See more...
I am still using these instructions I got from an older message in this forum I think: From inside the VM using a terminal session I issue the following command cat /dev/zero > wipefile; rm wipefile Shutdown the VM and exit VMware Fusion Execute the following command to defragment the disk (substitute VM name/Disk Name) /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -d macOS\ 10.15\ 64-bit.vmwarevm/Virtual\ Disk.vmdk Execute the following command to shrink the disk (substitute VM name/Disk Name) /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -k macOS\ 10.15\ 64-bit.vmwarevm/Virtual\ Disk.vmdk You would need to substitute your VM folder's names in there.  I usually navigate to the VM folder so I do not have to type all that out to run the commands.  I have had some problems with Big Sur VMs but everything else shrinks.
Got to it quicker than I thought...and same error in Fusion 12. I guess I kiss my old friends goodbye...seems to only be NT that is affected.  Windows 2000 still works and also Windows ME/98 works.
I do not recommend using Wi-Fi for this purpose.  The Wi-Fi connection in Fusion 12 has had a lot of issues and at least some of them seem to be issues that Apple needs to fix.  A Thunderbolt to Ethe... See more...
I do not recommend using Wi-Fi for this purpose.  The Wi-Fi connection in Fusion 12 has had a lot of issues and at least some of them seem to be issues that Apple needs to fix.  A Thunderbolt to Ethernet or USB to Ethernet would be better if the Mac does not have native Ethernet.
Such a table does not exist.  I have reviewed my inventory over the years and tried the idea of using the virtual hardware level that was new when the operating system was new, but things are never r... See more...
Such a table does not exist.  I have reviewed my inventory over the years and tried the idea of using the virtual hardware level that was new when the operating system was new, but things are never really conclusive in that regard.
I tried doing install from the recovery partition and that hung with no progress for 20 minutes so I did this: Make a bootable installer from Apple's standard instructions - https://support.apple.co... See more...
I tried doing install from the recovery partition and that hung with no progress for 20 minutes so I did this: Make a bootable installer from Apple's standard instructions - https://support.apple.com/en-in/HT201372 Create a custom VM for macOS 11 as Fusion does not know 12 yet. Power on the VM.  It won't do anything but that's not important right now. Go to USB settings in the VM and check the box for and Connect to VM the Install macOS Monterey USB device. Restart the VM and at least for me the USB installer booted and I was off and running. I have not completed my first install yet but it looks like it will finish.
You know what...I am on Monterey 12.0.1 and I cannot reproduce this problem anymore.  Perhaps Apple figured something out?
I checked my Apple GPU Vmx and they are working.  They are set for hardware version 18 under compatibility.  You should check your compatibility setting?
...well  sudo ip link set dev ens160 mtu 1499 then allowed my Ubuntu 20.04 to apt where everything was corrupt at the default 1500...