thanks so much, we CardBus people need to fix this nothing cooler than run a Mixrig off of a Pismo or an HD rig off of a TiBook

good i saved this because now i cant download it any longer
https://web.archive.org/web/20030204075204/http://www.digidesign.com/download/mp/

>
MagmaSlots.sea.hqx

MAC.sit/MAGMA.SIT weren't there.
MAGMA.PXB.Extensions.hqx was but -unfortunately broken.

For those that haven’t a clue as to who Bill Atkinson was — and even for those that do… if you’ve any interest at all about where, when and how these wonderful machines and their capabilities originated, you owe it to someone (yourself perhaps?) to do a simple search here for Bill Atkinson. https://folklore.org/0-index.html

A very Apple essential site, providing great insights and detail into those “early days”.



And thanks to new member @obstinacy - for comments and reopening this thread in such a manner!

“HyperCard wasn’t just ahead of its time, it created a time that hadn’t existed yet. So many tools today owe their lineage to it. He really saw computing as something deeply human.” — @obstinacy

MagmaSlots for Macintosh   
[100KB] MagmaSlots.sea.hqx. A utility for displaying all PCI cards installed in the Macintosh and in the MAGMA PCI expansion chassis. This is a native PowerPC application and cannot be run on a 68K Macintosh. A Readme file is included.
 
 MAC.sit   From CDROM "MAGMA CB03A"
[3429KB] MAGMA.SIT. A stuffit file with all the drivers, extensions and utilties that are currently distributed on the MAGMA Cardbus Drivers and Utilities CDROM Disk. Updated June 28, 2002
 
 ApplePCI.img.hqx   From CDROM "MAGMA CB03A"
[189KB] ApplePCI.img.hqx. An Apple Image file with the Fix for the G4 Titanium 550-667 and 667-800 series Power Books. This fixes the problem with the ATTO SCSI cards when used with Applications such as ProTools. Updated June 19, 2002

i am still looking for the other 2 utils anyone has them?

.

HyperCard wasn’t just ahead of its time, it created a time that hadn’t existed yet. So many tools today owe their lineage to it. He really saw computing as something deeply human. Rest well, Bill.

Funny revisiting this thread years afterwards and make a follow up necropost -I’ve been busy elsewhere.

Three months ago I confided to a friend that my next purchase would be the new C64x, after watching this review.
Yes it is a PC running a C64 themed Linux desktop, bundled with pre-configured emulators. Nonetheless it’s hardware and makes everything simpler, and I got excited, an excitement I hadn’t felt for a new computer in decades.

Speaking of emulation.
At that same time I finally got around to installing RetroArch on our Apple TV -what a blast! I ended up installing it on 3 more devices.
There’s a bunch of cores, even for MiniVMac and MAME -so you can run Apple II, Macintosh, Mac OS, Windows XP, and whatnot.
(The App Store version comes with most cores -preinstalled.)

Fast forward.
Commodore Back On Track

@Starglider 2 aka Perifractic/Perry from Retro Recipes bought Commodore -just announced. The whole original crew is back.

In the past we only had Retro-Futuristic dreams
Onwards the future will be Futuristic-Retro lived.

I've got a pile of older PC radeons just gathering dust.  Have been itching to try flashing at least some of them and give them a useful second life.

If I find I have any interesting ones, and/or similar (or different in some fun way) to the ones above, I'll mention it.

Thank you very much for your help.

Yesterday I was comparing the photos, and although there are some differences, they are very similar. I found a couple of resistors on the front that were different, so I moved them, but that didn't work either. The downside to reduced ROMs is that they don't support Open Firmware, and they don't display an image until you reach the desktop.

I'll keep investigating.

Exactly!  But also the reverse, because there's still m68k code even in MacOS 9.  So a native powerpc app will silently be transitioning to emulation many times.  Apple never bothered to convert some parts of the system to powerpc.

This especially is the case if you install extensions or whatnot that are m68k on a powerpc machine.

The UPP contains not just the pointer to the code, but info on the arch (and how to handle parameters), so when a function using one is called (with help from the mixed mode manager), it knows to use emulation or not.

This is especially important with callbacks, as the manger may be in one arch, and the callback another.  The idea with UPPs is that you never have to worry about if you're in emulation or not, as long as you use them properly.

As a bonus, if you are on an m68k machine, and are using CFM-68k there is a "mixed mode manager" also, but it is used to switch between between CFM and non CFM code.  So CFM-68k needs to use real UPPs and do a lot of the same things you do on powerpc.

Finally, if in source, the code uses UPPs, when you compile just for plain m68k, the universal headers just redefine them as plain pointers.  The same code then builds regardless.  Magic!