in theory it should work with post-HFS disks, too. but it depends on what you do (archives, network protocols)

sitx is a nonsense format made specifically for jpg/mpeg files.

but i would  think that stuff it in mojave would warn you when there is a resource fork in a file which cant be written to disk without corrupting the file.

regarding MacOS9 - that only works when the archive file has been put in "compatibility mode" (most sitx files were not, because then it is without the new features such as jpg supprt or encryption)

Hi everyone, so I have a new quiet 80x80x25mm PSU fan and wondered if anyone has any tutorials they know of to navigate this.  I'm sure I could fumble through it, but I'd rather arm myself with some knowledge before I go in.

Important things I want be sure about too is that the fan's air flow is going the right direction. 

I have an NB-Multivframe Ultra Silent Fan
https://www.ebay.com/i/131759116416?chn=ps

Just added four 7/8" rubber feet to each corners of my mini G4's bottom pad, and while the bottom seems to actually feel cooler than before I'm still getting the auto-sleep/shutdown issues, particularly when attempting to extract 400MB+ Stuffit files on both Mac OS X Leopard and OS 9.2.2, with the CPU maxing out at 100% according to Leopard's Activity Monitor. About to run the Apple Hardware Test on my machine in a bit so I'll be sure to leave another update on this post.

Update #3 (4/20/19): Managed to burn a disc of the Apple Service Diagnostic which includes support for the late 2005 mini G4, and while a single ASD test set completed as Passed and the log reports an Error Count of 0, which should mean my mini G4 is fine, it still turned itself off ater about 22 minutes of being left on. I wish I can save the log file but this is just weird now. Perhaps I'll need to open it up again for a close look for anything I've done wrong physically, but for now I'll play the waiting game.

It sounds like you are using Multiple Users or something like that which enforces the startup device and throws an error if the wrong one is used.

Is that correct?

And if you Cmd+Option+Esc (twice) when that registration process begins…
and then reboot afterwards, you can skip the whole thing.