Search results

Ohh shoot, I didn’t mean to duplicate their work 🫠 Shall I close mine instead? And I can’t really understand either. PAP honestly seems a better fit for it, especially as the StyleWriter doesn’t even really use the flow control of ADSP either. Seems kinda silly to swap to a protocol where you...

Inspired by your change I pushed up one for ADSP: https://gitlab.com/wireshark/wireshark/-/merge_requests/25649. Would be nice if we can have it verify sequence numbers and such eventually but this works plenty well for my uses for now. I'm honestly really surprised nobody ever added support...

It was one of the most frustrating experiences ever but I now have TailTalk able to directly print to my Colour StyleWriter 2200 with the official EtherTalk adapter, which should also work with the LocalTalk adapters and GreyShare (I think). Thankfully lpstyl documented most of the interesting...

I think that's just talking about the EtherTalk adapters though right? I cant see the localtalk reference unless I'm just looking right past it. The one I was curious about was this...

Ahh that is great to know thank you! On another note too - any chance you know if the LocalTalk adapters for the later Colour StyleWriters use ADSP? I'm working on getting support added for the official Apple StyleWriter EtherTalk adapter to print to my CS 2200 which I know does and same with...

Yeah I figured it'd likely be the same way I'm using that for querying the LaserWriters to bridge to IPP. Always love a good excuse to break out my Inside AppleTalk book though :) The only extra thing I think I'd do is bridge straight to IPP rather than rely on CUPS to try and keep it platform...

That should be really quite easy to do, as we'd essentially be doing the exact same thing Netatalk does. I'll take a look at what we'd need to add (PAP listener of course) but I bet we could add this for the next release.

Happy to help, and sorry you hit it at the society meeting! This is a project I am really proud of and it makes me happy seeing others use it. It's still early days so I am sure there's some other silly bugs still hiding, but it's honestly good fun fixing things.

Patch merged here: https://github.com/FeralFirmware/TailTalk/pull/31 - should now expand ~/ to $HOME/ and in case there's any issue with using the dir it'll halt startup and display an error instead of just swallowing the error. Release 0.7.1 is also out now with it and app images should be...

Ahh that would do it then! I had honestly never typed it in manually so I had not even thought to check. I ran it locally here and it ends up just trying to do $CWD/~/.tailtalk. Will have a patch up here for it soon. One of the other things I'll add too is catching those volume errors at startup...

That’s kinda interesting. When you chose the path, did you type it in manually, or use the filesystem picker? If you did it manually I think I might know what’s going on - I see ~ in the log path versus /Users/…/ and I don’t think I’m resolving that to your home directory so I think it’s trying...

Sorry it's giving you trouble! Any chance you could record a packet capture of it (Just need to tick the PCAP option on the GUI and then DM it to me if possible) as well as provide the log files for one of the runs that you hit this on (File -> "Open log directory" on the top menu). What does...

I think I could build in that translation - it was pretty easy to get Netatalk running via TashTalk when hooked up to TailTalk, but I was not yet doing the long to short conversion. I've started building in a routing table equivalent to what the kernel has so we can route packets to the...

I have a PR up here if either of you (@Iesca / @NJRoadfan) want to give it a try: https://github.com/FeralFirmware/TailTalk/pull/29. I am so thankful for the kinda hidden process-but-dont-actually-print PostScript option because I would have gone through so many page prints trying to get this...

At least for my version yes, I don’t think I’ll likely ever change the USB chip out unless it went out of production. But there was another device here that is based on a Pi Pico that speaks TashTalk that I know of: https://github.com/hanshuebner/tashtalk-pico. I am unsure if he plans to mass...

Nice that is fantastic to hear! I needed an excuse to fire up my Apple II again On another note - is anyone interested in using these devices with LaserWriters or other printers? I’m toying with adding an extra option to the GUI where it will try and auto discover these and make them available...

I think that's the other question I have honestly - Would it make sense to have the userspace daemon be a dumb one in that clients must be routing table aware (i.e "Send this exact packet via interface X" and the daemon does nothing more than fire it off just as you asked) or keep it like it is...

One of the things I was curious about too is what you thought about using protobuf for the definition for the userspace daemon < - > atalkd/netatalk components. I thought it would be interesting to have a well defined format for it so the daemon side could be swapped fairly easily. This is what...

Hah I will admit I have never touched meson before, so it was mostly me trying to get it to compile and bring over the C library I was exposing to hook in to and start the Rust side runtime. It probably should be waaaay less by someone who knows what they are doing :) The C code was kinda a lot...

One thing I've found that really helps is ChipQuik - it's not super cheap but it has a really low melting temp compared to regular solder and for anything thats not a huge chip it makes it really easy to desolder things, often dont even need hot air. I am by no means a hot air rework specialist...