Skip to main content

Virtualization - Mac OS X 10.3.0 PowerPC Desktop on Qemu for Windows


Environment

  • Host: Windows 10 Intel x64
  • Virtualization: QEMU emulator version 6.0.93 (v6.1.0-rc3-11879-ge232c1bc00-dirty)
    qemu-system-ppc.exe
  • Guest: Mac OS X 10.3.0 Desktop PowerPC

Screenshots



Instructions

I have to write something here

Notes

  • Release mouse control back to host OS pressing Ctrl+Alr+G keys together.
  • Network only works if creating a network bridge connection. For my set-up, I called the virtual NIC mytap3430.
  • Network MAC address has to be unique. Each one of my Qemu guest NIC have a different MAC address...loads of MAC addresses....
  • Confirm the "Network Bridge" (in Control Panel\Network and Internet\Network Connections) is using the correct physical network card (Intel 1.0GB for me). I lost a great deal of time using the wrong NIC.
  • Possible SSH remote access problems solved here.

Links

  • https://wiki.qemu.org/Documentation/Platforms/PowerPC#Mac_OS_9.x_to_Mac_OS_X_10.4
  • https://www.emaculation.com/doku.php/ppc-osx-on-qemu-for-osx
  • https://wiki.gentoo.org/wiki/QEMU/Options
  • https://www.windowscentral.com/how-set-and-manage-network-bridge-connection-windows-10
  • http://wiki.laptop.org/go/Talk:Using_QEMU_on_Windows

Start-up script



/cygdrive/f/VMs, Emulators, Simulators/Qemu/Mac OS X/Mac OS X 10.3 (Panther)/Mac OS X 10.3 (Panther) Desktop/Mac OS X 10.3.0 (Panther) Desktop
qemu-start-mac-os-x-10-3-0.sh 

#!/bin/bash



sHD=mac-os-x-10-3-0-system-disk.qcow2

sName=$(basename "$(pwd)")



[[ ! -e "$sHD" ]] && "qemu.qcow2.exe" create -f qcow2 -o size=100G "$sHD"



# 52:54:00:12:34:30 

#              | |+-> 0: 10.3.0

#              | +--> 3: 10.3.x

#              +----> 4: Mac OS 10.x [Desktop Main Interface - Wired]



"qemu-system-ppc.exe" \

  -name "${sName}" \

        -L pc-bios \

        -boot c \

        -M mac99 \

        -m 1536 \

        -drive file="$sHD",format=qcow2,media=disk \

  -usb \

    --device usb-kbd \

    --device usb-mouse \

  -device sungem,netdev=mynet0,mac=52:54:00:12:34:30 -netdev tap,ifname=mytap3430,id=mynet0 \

        -prom-env "boot-args=-v" \

        -prom-env "vga-ndrv?=true" \

        -prom-env "auto-boot?=true" \

  -sdl \

        -g 1920x1080x32 \

        -device VGA,edid=on



cat >/dev/null << 'EOF'



   -netdev user,id=mynet0 -device sungem,netdev=mynet0 \

        -netdev tap,id=mynet0,ifname="Local Area Connection",script=no,downscript=no \

        -netdev tap,id=mynet0,ifname=OpenTAB,script=no,downscript=no \

   -netdev user,id=mynet0 \



For CD/DVD/DVD DL:

         -drive file=image.iso,format=qcow2,media=cdrom \



To boot from the 1st device: -boot c

To boot from the 2nd device: -boot d

To boot from the network   : -boot n



External source of information:

        https://wiki.qemu.org/Documentation/Platforms/PowerPC#Mac_OS_9.x_to_Mac_OS_X_10.4

        https://www.emaculation.com/doku.php/ppc-osx-on-qemu-for-osx

        https://wiki.gentoo.org/wiki/QEMU/Options

        https://www.windowscentral.com/how-set-and-manage-network-bridge-connection-windows-10

        http://wiki.laptop.org/go/Talk:Using_QEMU_on_Windows



EOF

Comments

Post a Comment

Popular posts from this blog

Movies - The Bubble (2022)

  Back to Evolution (2001) .
Post a Comment
Read more

IT - Fixing Windows Error 1327: Account Restrictions Are Preventing This User from Signing In

Fixing Windows Error 1327: Account Restrictions Are Preventing This User from Signing In Introduction Error 1327, “Account restrictions are preventing this user from signing in,” is a perplexing and disruptive issue that occurs on some Windows 10 and Windows 11 machines. The message typically appears at login or while connecting to remote resources, like shared folders, network drives, or remote desktops. Table of Contents Symptoms of Error 1327 Common Causes Step-by-Step Troubleshooting Advanced Fixes Automation via PowerShell Prevention Tips Further Reading Symptoms of Error 1327 Users experiencing this error may encounter one or more of the following: Login screen fails after credentials are entered. Error message appears when accessing mapped drives or network resources. Remote Desktop Connection (RDP) is rejected with the 1327 message. Group Policy logon restrictions silently block access. Co...
Post a Comment
Read more

IT - Troubleshooting Kodi DLNA Visibility Issues After Windows Updates: A Deep Dive Into Conflicts, Fixes, and Lessons Learned

Title: Troubleshooting Kodi DLNA Visibility Issues After Windows Updates: A Deep Dive Into Conflicts, Fixes, and Lessons Learned Subtitle: How I Diagnosed and Solved Intermittent Kodi Visibility Problems on a Samsung Smart TV After Windows OS Updates and Media Server Conflicts Introduction Home media streaming should be seamless, but anyone who has integrated Kodi into a smart home setup knows that stability isn't always guaranteed. Recently, I encountered a frustrating issue: Kodi, running perfectly on my Windows 10 Pro desktop, suddenly became invisible to my Samsung Smart TV via DLNA. The journey to resolve this seemingly simple visibility issue turned into a deep technical rabbit hole involving Windows Media Server, Universal Media Server, Jellyfin, NordVPN, and the very internals o... The System Setup Before diving into the problem, it's essential to understand my hardware and software setup: Operating System: Windows 10 Pro (build 2009) Media Server: Kodi (...
Post a Comment
Read more