Recent content by Bolacore

Published TashTalk support as an independent crate so it can be used in other Rust projects too with an async API. Docs available here: https://docs.rs/tashtalk/0.1.0/tashtalk/struct.TashTalk.html. Still need to add some more docs / readme for it, but it is very simple so I dont think it will...

TashTalk is now supported, just got it working tonight and have AFP transfers going from both EtherTalk and LocalTalk. Will have the next code push up in a couple days when it looks a little less scary hah.

Yes printer itself works OK, spits out a valid test page and I can print from my PowerBook G3 (OS 9.2) just fine on it with the same printer cable. Not using any special software, just what came on the 9.2 install disk. If I select networked StyleWriter on Chooser I can see NBPs going out for it...

Sorry for the delay, was away for a bit - Yes it's just like that and the manual that it came with says: Printer cable that was included with the StyleWriter (so no PhoneNet adapters or anything) going directly to the Stylewriter, power, and then RJ45 to a switch. Yup yup, has a sticker on the...

What OS are you on? It’s still Linux only at the moment but will support the others soon. If you’re not using Linux I could always do with testers once I add support for them too! To build its really easy! Install Rust from here https://rustup.rs/ Then clone the repo, run “cargo build” in the...

It’s a Colour StyleWriter 2200 and the adapter is the Apple version of Farallon’s iPrint.

Picked up a StyleWriter EtherTalk adapter and am trying to get it to work on my network, but cannot seem to get it to bring up its interface on the 10BaseT side. Test/Power light is green, printer activity light is solid yellow and none of the others are on. It seems to be somewhat working as it...

Published a rough first version to GitHub if anyone wants to check it out: https://github.com/FeralFirmware/TailTalk. Maybe this should be moved to "Hacks and Development"? Or not sure where it belongs honestly hah. Next bit I want to track down is why my Mac clients seem to freeze if they...

Well for reasons I do not fully understand with a working battery the transfer now works great and I'm at ~70MiB of 515 copied without any hiccups. Maybe there is some odd interaction that when the internal battery is borked the PRAM battery is also not charging and that causes odd behaviour...

In the process of rebuilding my PDQ’s battery and found that even with fresh cells I had zero volts at the output terminals. Battery reset program did not make a difference either. I started tracing back and found this odd looking component is open circuit. If I jumper it the battery appears to...

And now write support works! Ferris the Crab was able to make a round trip from my tablet to the PB and back again and still have the same contents. ASP is such an amusing protocol with having the client request the server to ask for packets from it to do a write. Had to implement Icon support...

Hm interestingly on long file transfers I’m seeing my PowerBook just hard lock again. Gets about 30MiB in to a file copy then just halts network activity and everything stops responding on it (no mouse or anything). Following the capture does not reveal anything interesting it just randomly...

Success! After implementing far more AFP commands than I ever thought I'd need to, I have Linux to Mac OS file copying working with AFP 2.0 via EtherTalk (and indirectly to LocalTalk clients via an Asante). Of course have to get my favourite Rust crab copied first, and using it to copy a load of...

Just tried booting Mac OS 9.2 on the PowerBook and it gets much farther, before exploding because I have yet to implement the rest of the directory bitmap types 😅 But that seems to confirm at least that on a clean setup it doesn't stall at the FPGetSrvrMsg call.

At this point I dont _think_ I have any malformed ones left. The only one I am unsure about is FPGetSrvrMsg - Even though that should only be in AFP 2.1 and I am only advertising AFP2.0 and under it still seems to send it. Wireshark seems happy about what I am sending, though. But yes I think...