Search results

Connect to the Mac mini G4 in Open Firmware using telnet. https://forums.macrumors.com/threads/question-how-powerful-of-a-graphics-card-will-work-in-a-beige-power-macintosh-g3.2303689/ Gather info about the Mac mini G4 using this command: dev / ls unselect-dev " devalias" evaluate " printenv"...

I didn't ask for the rest before. I just figure while one is in there, why not gather the other info from Open Firmware as well? The width of your output was truncated to 120 characters. What terminal app did you use to capture it? My lspci for Open Firmware requires width 550 or word wrap...

ATI graphics chips have PCI vendor ID 0x1002 and a device ID that usually composes of two ASCII characters. 0x4750, // GP (Rage Pro) 0x4754, // GT (Rage II) 0x4756, // GW (Rage IIc) 0x4758, // GX 0x5654, // VT I guess VT-A and VT-B are two types of ATI graphics chips with device ID 0x5654...

I see that the cables from the motherboard that you show in #46 for the non-SCSI side of the top half of J18 (S1 to S50) has a 6 line cable for S1 to S6 and a 34 line cable for S7 to S40 and a 7 line cable from S? to S?+6 (where S?+6 ≤ S50 probably S44 to S50)? Anyway, BOXID0 is S18...

According to the code in HWInit of gazelle ROM, the emmo pin is connected to CPU_ID2 instead of CPU_ID0. The emmo pin starts the Serial Test Manager which exists in many (all?) Power Mac ROMs. The string "Serial Test" exists starting from the first PCI Mac to the last 32-bit New World Mac ROM...

Probably not. I don't see in the schematic how CPU_ID0 is set to 0 unless R165 is removed? Well, I don't think anyone's shown a photo of that location on a pm6500 yet. The photo at #12 is for a 5500.

Thanks for that. The info should allow DingusPPC to get the gazelle ROM to select the correct ProductInfo for a pm6500. calcids () { local ohareid=$1 local idoffset=0 for theids in fp mon mb cpu; do id0=${ohareid:0+$idoffset:2} id4=${ohareid:0+$idoffset+2:2}...

Try the attached file. Copy it to the root folder of the Mac OS 9 partition. Get the partition number of the Mac OS 9 partition using pdisk or whatever. In my case, it is partition 10 (decimal). Partition Map contents (18 partitions) 1: 63 @ 1 Type:"Apple_partition_map"...

Ok, this one should work. I switched to using find-package because dev and find-device do extra stuff like output a beep on failure or change the active-package which we don't need to do. But find-package doesn't know about device aliases on B&W G3 so I have to get the mac-io alias manually...

For 6500 and some other Macs, mac-io needs to be replaced with the actual device path for the OHare chip. For the 5500/6500/TAM it should be pci1/ohare I updated the script in the probe-ids.txt.zip attachment.

Copy and paste? You would have to do one line at a time, or increase the serial text pacing delay. The Open Firmware download command dl is fastest - it probably doesn't require increasing the text pacing delay...

What exactly was the error message? What was the source for the System Folder copy? What was the destination of the System Folder copy? Try copying the System Folder to a different folder? Or use sudo cp -R to copy the System Folder?

I think I downloaded it from https://www.stuffit.com Stuffit Deluxe Mac Updates Version 16.0.5 English – Mac OS X 10.8 – 10.11 in 2018. Actually, I downloaded it from smithmicro.onfastspring.com which I guess was their online store at the time? I don't know if the update from...

I was able to do it with Stuffit Destinations.app on modern macOS (Monterey). Unarchiver.app did not like it.

I suppose that would work. Not as fun as being able to make your own ROM though.

If you have a Mac with OHare, Heathrow, or Paddington, then give this a try: cr " mac-io" find-device " assigned-addresses" active-package get-package-property device-end 2drop 8 + @ 34 + constant idreg : probe-id ( idreg -- ) >r 0 r@ rb! 1 ms r@ rb@ 2 u.r 0 r@ rb! 1...

Oh right. The tbxi of the New World Mac OS ROM file does Open Firmware stuff before Mac OS boots. tbxi dump extracts a boot script which I guess you can edit. Then tbxi build should take the edited boot script, fix up the offsets and checksum and include it in the new ROM. I haven't tried it...

Which of @elliotnunn 's tools works with New World Boot ROMs (1 MiB flash chips)? I have scripts to dump parts of New World Mac firmware updaters and ROMs. Some changes would be needed to allow modification and rebuilding the ROM or firmware updater. Need a PPC assembler for the PPC assembly...

Some minor changes: Translate LF to CR so the script is more easily editable in Open Firmware. Use a heredoc for multi-line nvram variables like nvramrc to make the script easier to read. unselect isn't a word until Open Firmware 3.1.0 (the first New World Mac Open Firmware?) which is ok for...

Is AIX big-endian or little-endian? Does AIX enable 16 or 32 bit color modes? What's Extended RAS?