Search results

Given that the Print Manager basically went unchanged until the end of classic MacOS, I'm not surprised at the spaghetti code. One plus of this is that you can run the LaserWriter 7 driver on the earliest System software that supports AppleTalk printing. QuickDraw GX was supposed to solve all...

I don't need another TashTalk per se, but I could use one for development purposes for A2SERVER. Any dev info, like the type of device it appears as helps.

Netatalk + CUPS is what you are looking for. Seamlessly bridge the old with the new. Now if you want a "native" driver, you got your work cut out for you as you'll need: An mDNS/Bonjour stack: This is needed for printer discovery. An IPP 2.0 Port Driver: This is how AirPrint and other...

I wish Apple didn't insist on such confusing terminology with the drive select signals. PCs were weird in that the first drive was wired as DS1 as opposed to DS0. Some docs refer to DS1 as "Drive B".... not be be confused with DOS drive letters! Later PC motherboards (and maybe the beige G3?)...

Manual inject PC style floppy drives support auto mounting inserted disks by monitoring the "disk change" signal. Amigas use it to automount inserted disks.

Looks like @bbraun saved the day with USB support.

40 Canadian Dollars, or roughly 28.78 US Dollars.

I have been testing the SQLite backend with A2SERVER. Already found a few minor issues that should be fixed in the next release of Netatalk.

9600s were still being used (with AVID IIRC) by the post production team of the Maury talk show back in 2003. They were "old" even back then, but still cranking out trash TV for the masses. :p

286 is no longer a problem: https://www.doomworld.com/forum/topic/140155-realdoom-doom-ported-to-16-bit-real-mode/ https://github.com/sqpat/RealDOOM

If you can see servers and connect to them, AARP should be working, which is what is usually mishandled by the WiFi access point. There may be other issues with multicast not working, which would screw with things like RTMP and ZIP packets. Does your ZuluSCSI machine properly acquire a node...

Most of the items on the list have been completed already....

None of these emulators support "real" LocalTalk output. GSport does LLAP-to-ELAP translation (the emulator handles AARP) with hooks into the SCC emulation. The rest all use LToUDP hooks. It may be easier to just hack away at the SCC emulation itself to properly support a TashTalk device. GSport...

On the mail interface selection screen use filter "atalk" for all DDP packets. I generally set this as "atalk or aarp" to get all startup traffic. Once sniffing, you can use "afp","asp","atp","aarp", and "pap" to isolate specific protocols as well. Wireshark does not have dissectors for MacIP...

The escape sequences/command set is backward compatible with the original ImageWriter and the "Apple Dot Matrix Printer" (basically a parallel port equipped lightly rebranded C-Itoh 8510), so yes... it'll work with the Lisa. Also of note, the Lisa supported color printing with the Canon PJ-1080A...

ASP isn't exactly a fast and efficient protocol. As you noted, the payload size per packet is limited. AFP over TCP is much faster.

What model is your old printer? HP's old LaserJets are pretty serviceable. Many are impossible to kill, only being EOLed by lack of toner cartridge replacements. OS X 10.4+ is guaranteed to work with a printer that supports PCL or PostScript. Auto discovery via Bonjour/mDNS should work as well.

Just as long as its running OS 9. AFP 3.0 has a ton of changes that could complicate things in a trace with an older client.

The malformed packets may be a problem... or not. Gotta love the lack of error handling in classic MacOS though. When trying to root out bugs in Netatalk, I've found it helpful to do packet traces using one of Apple's AFP servers to see how the communication should progress. The built-in file...

You need to return error -5018 for ObjectNotFound. -5012 is for ItemNotFound.