Search results

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.

Thanks @nyef and @pl212 ! I've added your devices to the appropriate documents in TashNotes. Sorry this took me so long, life's been busy. Couple of minor followups: @nyef - Does the Intuos appear only as one device with handler 0x6A, or does it emulate a mouse as well like the ArtZ II is...

Not far at all... by no means let me stop you. Also, feel free to take whatever is useful from TashRouter, hopefully my Python code is more accessible than my PIC assembly. =)

There's only one capital 'T', Tashtari. =)

Nothing big to report in the past week, I've mainly been polishing and rearranging, trying to get things set up for an implementation of DCD (Hard Disk 20) drives. Space is getting kind of tight in the receiver part of the PIC trio that makes up the backend, but I'm hoping it will still be...

TashTalk 2 Hat kits are back in stock again in the Ko-fi shop! If you're interested, please get your orders in this week - after that, shop is going to be temporarily closed until the beginning of October.

Always happy to add more mice (or other devices) to the list! Here's a rundown of the procedure for gathering data on them: Install the immensely useful ADB Parser on your ADB Mac. Identify the device on the bus and note what its original (not current) address is. Keyboards typically have...

I took a break from working on raw GCR writes to get formats working. GCR formats were easy, I just had a bug that was incrementing the sector in the wrong place. MFM formats were a bit tougher, I had to implement support for faking the INDEX signal, which on a real drive indicates when the...

One bug later, MFM writes are working! Still need to fiddle a bit to make sure 720 kB disks are working too, but 1.44 MB disks are working and that's by far the most important thing. I also wrote the backend side of the raw GCR receiver, which ended up being a lot more compact than I had...

Aaaaand 1.44 MB MFM floppy disks are working! (Though read-only only at the moment.) Turns out the backend's MFM transmitter had some serious timing issues that led to some bizarre behavior, now fixed. Hopefully 720 kB floppy disks will Just Work, though I haven't tested them yet because I'm...

This isn't working yet, I suspect the reason is to do with the first sector the Mac sees after formatting a track. It writes a track with address marks and blank data marks and then reads it back, hoping that it will see the first sector it wrote as soon as it switches from writing to reading...

Just skimmed back through this thread with some amusement at all the iterations this idea's gone through... I'm glad I've finally arrived somewhere where I don't foresee a major redesign in the future. (But who knows.)

IT'S ALIIIIIIVE!!! In other words, I just got writes working for the first time this morning. Can now read and write 800 kB GCR floppy disks using the backend (and my prototype frontend)! I'm excited but also tired, it's been a long haul to this point... Nonetheless, I'm thinking about what...

Ah, I see. I think there's some confusion here to be cleared up. There are two ways you can connect an emulated floppy interface into a Mac without modifying its software. One, you can use a device that pretends on the MCI (interface) level to be a floppy drive - this is what the Floppy Emu...