Recent content by NJRoadfan

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...

AppleDouble has the advantage of incorporating the Finder Flags (archive bit, label/colors, etc.) into the archive as well since it has the full FinderInfo of a file. I'll take a look at the source later and maybe add in support for native FinderInfo on macOS hosts using extended attributes.

I'm guessing the .info files are the raw 32 byte FinderInfo data? If so, you can grab this natively from macOS file systems by dumping the extended attribute called com.apple.FinderInfo. Easy enough to do in C. You can technically dump the resource fork this way, but its a pain in the neck.

Both cards were BTO options on the beige G3, so no surprises there. The server configurations generally came with AppleShare IP installed along with other "serious bizness" packages. Otherwise they are the same as the plain G3s.

The UnArchiver can extract MacBinary and Stuff-It files on a modern system. In terms with disk imaging tools, there is CiderPress II. The command line versions should run fine on macOS. The GUI versions require Wine. While more Apple II oriented, it does work with HFS disk images and MacBinary...

I heard the Mac chime, its back.

Jumper to fast mode (basically this sets the card to appear as a SmartPort device) and place it in Slot 5 if you want to use more then 2 ProDOS partitions on a drive. These early cards are very weird about partitions as they tend to be written "raw" without any partition table on the drive. The...