Recent content by Bolacore

0.8.1 building now: https://github.com/FeralFirmware/TailTalk/releases/tag/0.8.1

@MindWalker found it! I did not realise $PATH doesn't contain Brew's path when run as an app, whoops. Fix going in now. @iantm will have the keep awake button too - seems to be working well in my first test :)

My ImageWriter showed up today, and I have a LocalTalk board from @defor arriving soon. Hopefully I can replicate this and we can get it working - thanks again for your patience :) It looks like it's pretty trivial to do a simple "Keep Awake" button. For the first true 1.0 version I want to...

Missed this earlier sorry! That _should_ be the only thing you need to do - TailTalk just tries to run "gs --version" at start up and if that succeeds it considers it present. If you do "gs --version" in a shell, what does it return? Ooo I'll have a look at how to do this in macOS, that would...

That's cool! I had no idea this was even an option on the 630s - how much did you pay for it if you dont mind me asking? Kinda want to start looking out for one for my 630 too. Does it fit in with the network comm card too, or do you have to sacrifice any slots to use it?

There were a few posted - that was the one TailTalk was looking up the LCII I believe. The one I was looking at was tailtalk_capture_LC_IWII.pcap:

Sorry this was not TailTalk but rather the LC II querying the ImageWriter - TashTalk is purely a passive listener in this case. The ImageWriter _does_ respond as @iigs123 sees the device show up in Chooser. Thats what is throwing me.

Yeah we are for sure wrong there (been on my list for a while now), but, what's odd is that TashTalk should still see the packets coming back from the ImageWriter when it was just a passive listener for the LC II < - > ImageWriter NBP queries. It is very odd that we can see the NBP Lookups but...

Huh that's bizarre. If it doesn't work even with Tashtari's tool then it probably isn't our software at fault, but I cant see a reason why it wouldn't pick up the packets. Any chance you could test a direct connection as one last thing? _just in case_ it's something with the other topology. And...

Thanks! Any chance you could try Tashtari's capture tool? Just to rule out anything funny TailTalk might be doing: https://github.com/lampmerchant/tashtalk/blob/main/tashtalkcap/tashtalkcap.py. Curious if that can see the ImageWriter response or not.

Oh that would be kinda interesting - do you consistently see that framing / aborted warning after every tailtalk generated (Or even the LC II one when the IW would respond) NBP lookup?

ahh yeah that seems like just the CRC then - I think this is likely us not using the broadcast request option. Out of curiosity if you have just these two in the network (So your modern machine direct to the ImageWriter) does it see it then? In the LC case I dont see any responses back either -...

Interesting, nothing looks that different beyond it using NBP broadcast requests which we dont do yet. Any chance you could take a capture of the ones TailTalk makes for comparison? I assume that was the one that had the extra 0x91 0x5E right?

Anything interesting of note different between those two caps? I think I remember @NJRoadfan mentioning a few of the quirks of the IW II in that we should use DDP Long headers for NBP as otherwise it responds to all of them (or did I have that backwards?). I'm sure he would have a good idea...

Ahh sorry I didn’t think anyone would want them in the pcap - should they be there? It’s easy enough to add it back in.