• 0

Running Mac OS X on x86 PC!


Question

Recommended Posts

  • 0
Hmm... Booting Disc2.iso did not do anything either. Still hanging on this problem below. Any ideas??

Thanks,

Unrealism

Mac OSX 10.2

:blink:

I don't think disk2 is bootable.

After disk 1 installs, boot from the hard drive (change the "auto" in the script file to "select").

Once the installer starts back up again, it will ask for disc 2.

  • 0

I tried that, but I still get the same screen as last posted. Someone said something about the memory settings in the script. Here is my current script.

============

# PearPC Configuration File

#

# Resolution

#

# 0: 640x480x8 (indexed)

# 1: 640x480x15

# 2: 640x480x32

# 3: 800x600x8 (indexed)

# 4: 800x600x15

# 5: 800x600x32

# 6: 1024x768x8 (indexed)

# 7: 1024x768x15

# 8: 1024x768x32

#

# The indexed modes are unsupported.

#

# default: 4

ppc_start_resolution = 4

#

# Redraw interval (in ms)

# must be between 1 and 999

#

# If you set this higher, PearPC will spend less time doing redraws (and so run faster)

# but feel less responsive. You should adjust this to your computer speed and personal

# preference.

#

redraw_interval_msec = 20

#

# Loader

#

#

# Boot method

# this can be

# 1. "auto", prom will boot the first bootable partition found (default)

# 2. "select", prom will show you a list of bootable partitions

# 3. "force", prom will load and boot the local file prom_loadfile

#

prom_bootmethod = "select"

# Example of how to use "force":

#prom_bootmethod = "force"

#prom_loadfile = "test/yaboot"

#prom_env_bootpath = "disk"

#

# bootargs: don't change unless you know what you are doing

# machargs: set to "-v" to get a verbose startup

#

#prom_env_bootargs = ""

prom_env_machargs = ""

#

# This is needed if you want to boot Mac OS X

#

prom_driver_graphic = "video.x"

# This will adjust the position of the initial page table (don't change)

#page_table_pa = 104857600

#

# CPU Config

#

# Processor Version Register

# Defaults to 0x00088302

# Only change if you know want you are doing

#

#cpu_pvr = 0x00088302

#

# Main memory (default 128 MiB)

# must be >= 64 MiB

#

#memory_size=0x8000000

#

# IO Devices

#

#

# PCI IDE Config

#

# Drive type will be set according to file extension:

# .img: Harddisk (filesize must be multiple of 516096)

# .iso: CD-Rom

# Or you can override this by specifying the type via

# pci_ide0_master_type / pci_ide0_slave_type

pci_ide0_master_installed = 1

pci_ide0_master_image = "osx.img"

#pci_ide0_master_type = "hd"

pci_ide0_slave_installed = 1

#pci_ide0_slave_image = "darwin-701.iso"

pci_ide0_slave_image = "osx.iso"

#pci_ide0_slave_image = "/dev/cdrom"

pci_ide0_slave_type = "cdrom"

#

# Network (unavailable on windows)

#

pci_3c90x_installed = 0

pci_3c90x_mac = "de:ad:ca:fe:12:34"

#

# USB

#

pci_usb_installed = 1

#

# NVRAM

#

nvram_file = "nvram"

  • 0

I tried that, but I still get the same screen as last posted. Someone said something about the memory settings in the script. Here is my current script.

============

# PearPC Configuration File

#

# Resolution

#

# 0: 640x480x8 (indexed)

# 1: 640x480x15

# 2: 640x480x32

# 3: 800x600x8 (indexed)

# 4: 800x600x15

# 5: 800x600x32

# 6: 1024x768x8 (indexed)

# 7: 1024x768x15

# 8: 1024x768x32

#

# The indexed modes are unsupported.

#

# default: 4

ppc_start_resolution = 4

#

# Redraw interval (in ms)

# must be between 1 and 999

#

# If you set this higher, PearPC will spend less time doing redraws (and so run faster)

# but feel less responsive. You should adjust this to your computer speed and personal

# preference.

#

redraw_interval_msec = 20

#

# Loader

#

#

# Boot method

# this can be

# 1. "auto", prom will boot the first bootable partition found (default)

# 2. "select", prom will show you a list of bootable partitions

# 3. "force", prom will load and boot the local file prom_loadfile

#

prom_bootmethod = "select"

# Example of how to use "force":

#prom_bootmethod = "force"

#prom_loadfile = "test/yaboot"

#prom_env_bootpath = "disk"

#

# bootargs: don't change unless you know what you are doing

# machargs: set to "-v" to get a verbose startup

#

#prom_env_bootargs = ""

prom_env_machargs = ""

#

# This is needed if you want to boot Mac OS X

#

prom_driver_graphic = "video.x"

# This will adjust the position of the initial page table (don't change)

#page_table_pa = 104857600

#

# CPU Config

#

# Processor Version Register

# Defaults to 0x00088302

# Only change if you know want you are doing

#

#cpu_pvr = 0x00088302

#

# Main memory (default 128 MiB)

# must be >= 64 MiB

#

#memory_size=0x8000000

#

# IO Devices

#

#

# PCI IDE Config

#

# Drive type will be set according to file extension:

# .img: Harddisk (filesize must be multiple of 516096)

# .iso: CD-Rom

# Or you can override this by specifying the type via

# pci_ide0_master_type / pci_ide0_slave_type

pci_ide0_master_installed = 1

pci_ide0_master_image = "osx.img"

#pci_ide0_master_type = "hd"

pci_ide0_slave_installed = 1

#pci_ide0_slave_image = "darwin-701.iso"

pci_ide0_slave_image = "osx.iso"

#pci_ide0_slave_image = "/dev/cdrom"

pci_ide0_slave_type = "cdrom"

#

# Network (unavailable on windows)

#

pci_3c90x_installed = 0

pci_3c90x_mac = "de:ad:ca:fe:12:34"

#

# USB

#

pci_usb_installed = 1

#

# NVRAM

#

nvram_file = "nvram"

  • 0

You may want to give this a try:

well the people at the offical forum have found a way to get the macosx to boot if it has not booted after the install and yes it does require darwin to do what is required i

here it is

OK Its working now. Luckily you dont need to reinstall OSX from scratch. It worked for me, but Im not sure (but a little confident) that it will work in all the cases, so if you doubt please make a backup copy of your current hard disk image just in case.

This is the way I fixed it:

1.- Download darwin (yes, Im sorry)

2.- Start pearpc using the installed OSX hd image as master and darwin iso as slave.

3.- Once darwin has stated drop to a shell by typing "shell"

4.- Enter the "pdisk" commands

5.- As in the normal installation select type "e"

6.- Enter "/dev/disk0" as the name of the device.

7.- If you want to see how your partitions are mapped enter "p".

8.- Use r to swap partitions, you have to set the map partition as the first one (Im pretty sure that it already is the first one) and the OSX partition as the second one (it was placed third in my installation).

9.- Finally enter "w" in order to write the partition table.

10.- Now its fixed, and it will boot without problems. Just boot with the OSX disk 2 in you slave because the installation continues

  • 0

IIRC, .dmg is a proprietary Macintosh file format that can only be converted to .iso on a Macintosh computer.

There was some brief mention of .dmg files back somewhere like 20 pages ago in this thread. I just hope I can push the clock speed on this PearPC up past 10MHZ.

It would speed things up :)

  • 0

yeah thanks niteowl for the info! I wasnt even aware of such a file name, although I dont really use mac. I am hoping to get this pearpc working so I can use it to learn a bit. Yeah even thought it would be slow... I know!

Anyone have any ideas about why I am not booting OSX 10.2 the rest of the way after install?? I get the spinging grey pinwheel and a circle with a slash through it. Sits and does nothing. hmm...

  • 0

If it doesn't work then trying starting from the beginning again: http://pearpc.sourceforge.net/installdarwin.html (without actually installing it, but still have it start the installation, then exit when it starts copying the information).

  • 0
no seriouslys guys apart from the german one, is there a guide? cuz i can't read german...hehe

I honestly have never found one.

I searched on Google, Yahoo, Alltheweb, and Altavista and could not find one guide to installing any Macintosh OS, let alone OS X.

I am just winging it ;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!