I'm testing the power supply outside the QS, bridging green wire with black.

I have replaced several capacitors, checked several suspicious tracks, checked the 4A thermofuse... and it still doesn't work. It doesn't seem like a capacitor problem, I think there is a short circuit in some component but I can't detect it with the naked eye.

Quote from: bamdad on Yesterday at 02:19:13 AM

i don't think it's about resource (fork) compression, because i have 9.1 running on my pismo and hellcats runs just fine after removing some unneeded monitors extension or something (i can't recall but i can dig it up).

I see. In that case, did you try all 3 color depths (256, thousands and millions), as well as all possible resolution settings? I assume you already did, but I'm asking just in case.

of course :) hellcats errors out if you try to run it on any depth above 256 colours, and it adapts pretty well to resolutions. if i plug in my pismo to the same monitor my mac mini is using it happily runs at 1920x1080 by scaling its interface to a 4:3 aspect ratio leaving the desktop visible beneath.


somehow i need to identify what causes the dynamically rendered part of the screen (above the cockpit) to be completely blank on 9.2.2. i'm pretty sure it's not an extension like quickdraw or quicktime because the same thing happens when booting with extensions off. next i'm going to try (on my pismo as it's not as hacky as the mac mini)
- older versions like mac OS 9.2 and 9.2.1
- mixing and matching ROM files in the system folder
- looking through hellcats's resources in resedit (at least the ones i can understand)
and see if i can come up with something.


if someone who's a pro in any of the above could join me in my efforts it would be really appreciated.

@chris, you can get around the SSL/TLS nonsense using Crypto Ancienne, using Power MachTen or an x86 VM of your choice. No need for extra machines, although that works, too.

I'm satisfied with Classilla 9.3.4b. MacLynx is also good. Older browsers also serve their various purposes well. If a website is coded like cr4p, I don't want to visit it in the first place, it's not even a matter of a browser being able to render it or not, for me.

As for what is happening and has been happening to web browsers in the past decade, and is getting far worse now with scope creep through the likes of WebAssembly and beyond, this is not lazyness. It's sabotage. So f*&^ them. We don't need them, and we especially do not even want them. I don't trust their browser code, for good reason. Did they even get a PPC compiler for Rust going, in the end? That move from C/C++ to Rust in Firefox is yet another thing that, due to absence of compilers for many targets, plus other things, are clear acts of sabotage AFAICT. And this problem is not simply limited as a "corporations" issue, it unfortunately stretches way beyond that. So-called "academia", for example. Agendas such as the decommissioning of what little hardware is left that is still reliable (because semi-old and new hardware both aren't). And more.

TL;DR I don't need a new web browser. Most of us don't. What we need is new websites, not web browsers.

I'm curious where does the 135 MHz figure come from.

Perhaps you should ask (or invite) darth to comment here?

Not quite certain what you’re really expecting from the 2005 Mac minis (with fixed 32mb or 64mb of VRAM) originally designed to work with Apple monitors. Sure, they will work with some other monitors, but not always and not at all resolutions, nor connection variants.

But I do hope you find your answers and any possible solutions.

This is GOLD! I can't the amount of times I have searched everywhere for some documentation on a API I stumbled upon and found... Nothing.

Great job!