TashTalk USB

[NJRoadfan]

Netatalk (and I presume Apple's AFP server) all mangle the longer AFP 3.x Unicode names down to 31 characters for AFP 2.x clients using some digits of the CNID value at the end to keep them unique and somewhat linked to the parent file.

 

[Bolacore]

I did see that, but I mistakenly thought that since Finder appeared to display longer ones OK that things were a little flexible. It turns out they very much are not haha. I play a bit loose with file IDs currently in that they’re ephemeral on each start. I think I was likely going to bolt some hash on the end, or just finally commit to making them persistent.

 

[Bolacore]

And release 0.4.5 is building now with the change: https://github.com/FeralFirmware/TailTalk/releases/tag/0.4.5

 

[Iesca]

So far it's behaving perfectly now. Been copying files back and forth, launching applications from the server, everything working great. The truncation on long filenames currently appears is in the middle of the filename rather than near the end, but this is a minor quibble. Wonderful work, and thank you so much! Once I get another crossover cable, I'll be trying it out with cheesestraws' AirTalk modules!

 

[iigs123]

I was able to build and run TailTalk on Windows 11 using the pull request #11 on github. I had to manually install the CP210x_VCP_Windows driver to get it to recognize the usb device, and install npcap. But it seems to work. Even the gui works.

 

[Bolacore]

I was able to build and run TailTalk on Windows 11 using the pull request #11 on github. I had to manually install the CP210x_VCP_Windows driver to get it to recognize the usb device, and install npcap. But it seems to work. Even the gui works.

Nice!! Glad to hear it works. So it’s sharing files just fine then? If so I’ll merge it in and have it part of the official releases from now on.

So far it's behaving perfectly now. Been copying files back and forth, launching applications from the server, everything working great. The truncation on long filenames currently appears is in the middle of the filename rather than near the end, but this is a minor quibble. Wonderful work, and thank you so much! Once I get another crossover cable, I'll be trying it out with cheesestraws' AirTalk modules!

I kinda winged it on where to place the truncation ID. I thought having the extension at the end be unchanged (so it would be FILE~ABCD.txt vs FILE.txt~ABCD) might make sense for humans, but maybe not. What do you think?

 

[iigs123]

I'll do some additional testing. If you don't mind, I can comment on the PR. I can also work on some little changes if its is okay - like getting pap-print working a little better with an imagewriter...

 

[Bolacore]

I will never say no to improvements and feedback I have admittedly not tested pap-print with anything but the one LaserWriter I own, so I’d love to see it be extended to make ImageWriters work too.

I was hoping at one point to maybe make a little CUPS backend for it, or something like that so people could use the printers too with their modern machines.

 

[iigs123]

I'm slowly tinkering with the code on Windows. I'm newish to rust and not very familiar with AppleTalk so it is slow going. So far I've noticed the pcap usage is a little different than linux/macos but I do have some hacked ethernet code connecting on windows. I do see some oddness with ethernet & localtalk not seeing some other devices, and, some large copies seem to hang at times. It will likely be some time before I have anything new that is PR worthy.

Do you have some preferred way to chat about these things if I'm able to make progress? Here in this thread? I try not to waste anyone's time.

 

[Bolacore]

Here is fine for me, or even a GitHub issue maybe? Either works. I have no idea how it behaves on Windows but I know under Linux I could copy a 500 MiB file over EtherTalk repeatedly without issues. LocalTalk I did the same tests but with 30MiB ones over and over and that seemed good too.

I am wondering if you are hitting some framing issue - I have auto recovery but maybe it functions differently under windows.

I’d be more than happy to accept any PR that makes the Windows experience better, thank you so much for working on it!

 

[Iesca]

Just chiming in again to say that everything is still working flawlessly! If you get it going with Windows as well, that would be very exciting. Perhaps looking at a PC AppleTalk card would provide some insight?