Search results

Cool stuff! It was on my list to make a pcap driver but never got around to it.

I've got one on one of my many back burners, working title TashNode. The architecture is sort of like inetd, except that instead of plain text, a chain of processes communicates up and down using a simple TLV (type, length, value) protocol. I was going to explain this further but I realized I...

All known TashTwenty-based products and where to get them are listed on the project's github: https://github.com/lampmerchant/tashtwenty#pcbs-and-products Not to dissuade you from buying from me, but to do so is a bit DIY at the moment. =) I only have naked PCBs and programmed chips for sale...

All versions of TashTalk require CTS to function correctly, not just 1.x. It's certainly worth checking if you suspect it, as overflow or underflow of the receive buffer can result in all sorts of weird behaviors.

It doesn't, unfortunately - low-voltage programming requires that the RA3/!MCLR pin be used as !MCLR (reset), but TashTalk 1.x uses it as the LocalTalk input, so any PIC that has TashTalk 1.x on it will have low-voltage programming disabled (and it cannot be reenabled without use of a...

True! But it's sort of the way of the world... powerful chips are so cheap. To be fair, it's also a bit ridiculous to be using three 32 MHz chips (backend) and a 48 MHz chip (frontend) for the same purpose... add them all up and you get 144 MHz and four cores, which is even more ridiculous...

Actually, it may not be the wrong thing to do... memory's a little hazy on the details but I think the way Linux works with tun/tap is that you open /dev/net/tun and then use TUNSETIFF to select the specific device to use - and pass the IFF_NO_PI flag to disable an extra frame header of some...

Sorry to hear that! I hope you're able to amend and resubmit soon.

The arrangement is a little bit mad, but some might say that using 8-bit PICs for something like this when the RP2040 and friends exist is a little bit mad, too...

Any news from this endeavor? It's been a while and I thought I might shake the tree...

Starting a new thread so as not to derail the Netatalk 4.0 thread... How big a lift would it be to implement support for user-space AppleTalk in Netatalk? I'm thinking, I suppose, of a modular system along the lines of what TashRouter does, with modules for EtherTalk over tap, EtherTalk over...

Ahah! Beautiful! Thanks for finding that. It would still be nice to find the arrow-with-watch cursor since this is for a non-animated busy cursor, but this is a period-authentic example and that's more important to me.

Good thought. It's not in Word 6.0, though, I need to find and try some other versions...

Thanks for the tip - unfortunately I looked through the downloads and couldn't find the cursor I was thinking of... nearest thing was an arrow with the stem cut off and replaced with a clock. This was a thing from an actual application somewhere. Nah, HyperCard mostly used a full-size...

Does anyone remember having seen a piece of Mac software that had a semi-Windows style "working in background" cursor? That is, an arrow but with a small watch (or perhaps beachball) off to the right side of it. I could swear I've seen this somewhere but I can't remember where. I'm trying...

Hm, I guess it must be the driver doing that, then. Possibly it's changing something it shouldn't, though I don't expect that that specifically would cause the keyboard behavior that @opualuan is seeing.

Looks like TashPad won the arbitration for address 0x2 but both devices are present and accounted for... only thing out of place is that device 2 says its original address was 0x34, which doesn't make any sense, ADB only has 16 addresses. I'm still thinking the driver, not the Wombat. What...

That's very strange. I'm strongly tempted to blame the driver, because I have no earthly idea how the firmware could cause this behavior - the firmware only communicates the state of the buttons to the Mac, it knows nothing of the keystrokes to which they're mapped. Have you tried connecting a...

Order shouldn't matter; ADB is a bus, not a chain. Can you explain this further? I'm not sure I quite grasp what you mean.

Nice, the beige looks great! I can program PICs for you, too, if that makes more economic sense than buying a PIC programmer - but if you like doing builds based on my projects, it may be worth your while to get the programmer.