Recent content by joevt

The website has Micro-Cap 5 to 12. Micro-Cap II, III, and IV are earlier versions? https://gotroot.ca/spectrum/www.spectrum-soft.com/aboutus.html I guess Micro-Cap V and Micro-Cap V 2.x exist on the website as Micro-Cap 5 (v1.3) and Micro-Cap 5 (v2.1.2). Here's a recent post from a person that...

I think that #2 should be done first (unless you already have an address name map somewhere?). Then #1 can be compared with that using a script. This would apply to the Mac Plus since there's no Apple supplied rom map for the earlier Macs. The same source code in your repository is used for 128K...

the ndrv that is in the fcode image of the PCI Option ROM is responsible for controlling a display in Open Firmware and in Mac OS (handles detecting a connected display, and setting resolutions and color depth and color palette). I extracted the ndrv from each fcode image as a .pef file for...

The Beige G3 has two fcode images for ATI GPUs. 1002:4754 ATY,mach64_3DU ATY,GT-B 113-XXXXX-1.1 1.49 1002:4750 ATY,mach64_3DUPro ATY,GT-C 113-XXXXX-1.1 1.53 DingusPPC supports these device IDs: ATI_RAGE_PRO_DEV_ID = 0x4750, // GP (Rage Pro) ATI_RAGE_GT_DEV_ID...

That is not normal. If it's not recognized as a Twin Turbo, then what is it recognized as? For each machine (Beige G3, B&W G3), gather some info from Open Firmware via serial port: Do a dump-device-tree Do lspci as described at...

I don't get it. If there's a firmware lock, why is it letting you boot different OS's? You have access to everything except the Startup Manager? https://support.apple.com/en-ca/102603 How does firmware lock work on an iMac from 2011? Maybe you can get a ROM dump and examine it with...

Don't got it. It's listed in the MacROMan GitHub repository but is not included in that repository's TestImages folder.

There's two ways to find out how the bits are arranged in the ROMs: - schematics to see how the ROM chips are connected - ROM dumps The arguments work for your ROM dumps of the 1400cs - 32 bits, 16 bits per ROM chip. @Bolle and @demik were probably working with ROMs from a different Mac - 16...

https://srecord.sourceforge.net/man/man1/srec_examples.1.html The Low and High ROMs take two bytes at a time, so I guess the correct -split arguments is going to be -split 4 0 2 for High and -split 4 2 2 for Low. But the two bytes are swapped, so the first thing to do is a -byte-swap 2 before...

What ROM does the PowerBook 5300 use? I might have it but it doesn't have an obvious name. I see a ROM for the Power Mac 5300 but not the PowerBook 5300.

Most emulators have their own scaling feature to fill the screen without changing the resolution of the screen but I suppose it would be faster if the panel controller had its own scaler. 640x400 is too small for some apps. In that case you'll want a working 1280x800 mode. I don't know. I think...

The first mod changes the device ID in the PCI Header from 5631 to 8A01. The second mod makes the same change to some PPC code in the ndrv driver.

Is your goal to output 640x400, or to fill the panel? 640x400 is a 16:10 aspect ratio (same as 8:5, but I think 16:10 is the more common description). 640x400 on 16:9 panel requires pillarboxing as you said. 640x400 on a 4:3 panel requires letterboxing. SheepShaver supports arbitrary...

When scanning for boot devices, the ROM usually starts with the higher SCSI ID? I think that's what I see when looking at the logging in DingusPPC.

Are we looking at GA6 1.0.6 or 1.2.6 ROM? Both have code that references these registers: 3c4h Sequencer Index Register (SEQX) 3c5h Sequencer Data Register (SEQ_DATA) 1.0.6 appears to have code that modifies: SR1, SR8, SR9. colon_definition_function_80b ( data index -- ) is for modifying an...