Search results

Just a little straw poll, who would be interested in a US-side (other parts of the world can play too, but with international shipping) run of kits for TashRecorder? I apparently bought ten of the op amps at some point but didn't follow through and I'm not sure what else I'd do with them...

TashTalk hat kits came and went quickly... I'm working on getting them stocked elsewhere so you all don't have to depend on me having spare time. Will update as soon as I have news. Also, I made a small addition to the TashTalk repo that I thought might be worth a mention - a simple program...

It took me a lot longer to do this than I said it would, but I finally got the time and spoons and plastic sandwich bags together aaaaand... TashTalk hat kits are back in stock! Get 'em while they're hot! (Get some other stuff too, maybe?) https://ko-fi.com/tashtari/shop

Nice builds! I don't mind you forking the repo, but you're also welcome to contribute your design to the existing one (maybe add a folder called "pcb-smt" in the root directory and put the files in there).

There's a cdev that hooks shutdown and sends a signal to the PowerKey to power off immediately, it's all automatic.

Interesting, this same setup only works with the NeXT mouse, not with any other two-button mice you tried?

Glad to hear it's working! If it's booting off your TashTwenty, it's been upgraded to a 512ke, the 512k-without-the-e requires a floppy. Not sure what CayMac is providing on their SD cards (assuming you're using the one that it came with) but it certainly could have two partitions, with the...

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...