Recent content by NJRoadfan

The HFS MacFUSE file system would be a good starting point to see how to natively integrate resource forks and FinderInfo into the macOS port of afpfs_ng. https://github.com/thejoelpatrol/fusehfs Other platforms shouldn't attempt to do this. The existing method of throwing the resource fork...

ProDOS used 7 bits to store the date, but intentionally limited the date field to 00-99. GS/OS expands this further, but the onboard clock is still limited. https://prodos8.com/docs/technote/28/

MMX CPUs require split voltage supply. They just won't work in a standard Socket 5 motherboard hence why Pentium Overdrive MMX CPUs exist (they have the proper VRM are part of the chip).

Looking at period documents, this would sold under APDA #M7047/B. I also found references back in 1989 for an earlier document called "Script Manager Developer's Package" under APDA #M7047. This is likely an earlier revision of the document going by the order number and might also cover...

Yes, this machine came standard with a SuperDrive. I'm not surprised a consumable would go missing after all these years.

Of note, my Late 2003 15in Powerbook G4 1.25Ghz (first gen AlBook) came with a blank Apple branded DVD-R disc. I have to pull the box down the next time I'm in the attic.

megatron is part of Netatalk 2.x and was removed from newer versions due build issues. Don't know how it would have appeared on a macOS machine!

The STB Horizon+ is a generic Cirrus Logic CL-GD5430 based card. That happens to be the same chipset hypervisors like QEMU have support for.

IIRC, if the FinderInfo is entirely null bytes (or set as such), the OS will hide the com.apple.FinderInfo extended attribute from xattr and the C functions. The extended attribute itself is a system abstraction as stated previously.

As mentioned before, this is common with Apple II files stored on HFS volumes as they usually don't have resource forks (only GS/OS supported them), but still needed to store ProDOS filetype/auxtype information. Also many cross platform document formats are data fork only, so rely on FinderInfo...

Eck, I meant to say 2 bytes (16 bits).... whoops.

The "Finder Flags" are the 4 bytes after the 8 bytes of File Type/Creator. Its stores things like the color/label, "has custom icon", "is on desktop", "is alias", "invisible", etc.

Not every file has a resource fork (this is certainly the case for Apple II files stored on Macintosh volumes) and the resource fork doesn't store the Finder Flags (labels, etc.).

I'll get around to adding full native macOS FinderInfo metadata support.

The ZipGSX requires a utility to turn the accelerator on or off. Unlike the TranswarpGS which has that fancy built-in CDA. The cables and CPU socket used on these cards are very fussy. You need to try and carefully re-seat the cable. Also the pins on the cable aren't the same profile as a CPU's...