Search results

Thanks. I've been working from the specification by Peter N. Lewis that's distributed with his MacBinary II application.

That's good to hear. There should always be (at least) two ways to do anything. :) I know that The Unarchiver (or more specifically the XAD Objective-C library it uses) has support for multiple StuffIt compression algorithms, including Arsenic, Brimstone, Cyanide, and Darkhorse. At some point...

The app contains several large hardcoded arrays of strings, which you could copy into string list resources ('STR#') using ResEdit as a starting point for localization. There could be a STR# ID=1 "Locations-sl" resource that contained all the strings from locations.c, a STR# ID=2 "Messages-sl"...

I think the reason that you're not seeing any replies is that you're asking for a lot more work than you realize. Porting a standard I/O console application to be an event-driven Mac GUI application is a non-trivial task. AppMaker has generated a set of template source files for you (.c and .h)...

Having support for A/UX is very cool indeed! One question: does LToUDP work with A/UX? I've enabled it on the printer port and it looks like packets are sent and received, but there are no zones in the Chooser and it doesn't see other LToUDP (Mini vMac) instances on my network. Am I forgetting...

Sorry it took so long, but I finally got around to making `sit` read the `com.apple.FinderInfo` extended attribute for file metadata. It's a lot more useful now when archiving a file that doesn't have a resource fork.

Some folks reported bugs with uninitialized variables, time-of-check/time-of-use races, and use-after-free issues in the AppleTalk code. These are generally considered security issues. The core Linux maintainer responsible for this code apparently was unable to get anyone to review the patches...

You can still run a VM with a version of Linux (or NetBSD, etc.) that has AppleTalk support, even on a host system that doesn't have AppleTalk, as long as you use a bridged network interface. Honestly, I think this was the inevitable result of the decision Avie Tevanian made over 20 years ago to...

I don't recognize that particular card, but the Card Cat program might recognize it. https://henrylowe.net/card-cat/

This is good to hear. Glad it worked for you! I didn't realize that the Apple Scribe essentially uses the same commands and can be treated as if it were an ImageWriter printer. The Apple Scribe reference manual seems to have a complete list of its supported commands so I'll go through them and...

Ooooh! I like that version! I was trying to remember where I've seen a similar keyboard, and I think it's the one from Deluxe Music Construction Set. One difference is that they don't bother with the full key region, only highlighting an inset rectangular portion. Your full key highlighting is...

That looks good. I still agree with @joevt that the insets need tweaking a bit. There is a white line where the white key touches the black keys. If you keep that, then maybe that white line should go all the way around the inside border of the key? Yes, that part's easy. The hard part is...

Most of the people I hear saying "it's just a tool and it helps me be more productive" are already proficient software developers. What worries me is that the tool will be increasingly relied on by folks who are not yet proficient, and/or whose only motivation is to get to the end of the...

Maybe you can use a 50% or 75% gray pattern for the highlight, so it's easier to see whether black keys are held down? Inverting them to white looks odd when I'm looking for a chord pattern consisting of mixed white and black keys that visually reads the same. Just a thought. This project looks...

My #MARCHintosh project this year is called Simple Spooler -- think of it as the Simple Text of print spoolers. It's an application that runs on old Macs (System 6.0 up to 9.2.2) and lets you share your serial ImageWriter printer over the network, without needing an AppleTalk Option Card...

Interesting. They also forked the same sit.c file from 1988, back in 1990. Looks like the only addition is to stick the FInfo in a .finderinfo/<filename> path, where AUFS expected to find it.

It became shorthand for the word "folder" itself. Practically, it meant you could save characters in a filename, since "Sample Projects ƒ" takes up less space than "Sample Projects folder". (Although yes, the word "folder" in a folder's name is sort of superfluous anyway. 🤷‍♂️ )

I'm actually slowly changing my mind on the question of adding MacBinary support to sit. There are two reasons: 1. A MacBinary-wrapped archive allows the correct type and creator to be set for the archive file itself when reconstituted on a classic Mac. 2. The original author of sit, Tom...

A couple of new bug fixes for the New Year have been pushed to the git repository. 1. Using sit to create archives of files from developer CDs and other old content, I noticed that filenames with "high ascii" (option-key) characters weren't being translated properly to MacRoman when expanded...

That explains it. I was trying to run Netatalk 2.x on this system a while back and probably did a `make install` to get it there.