Search results

I'm reverse-engineering the vendor protocol for Kensington pointer devices and had a question for anyone who might have an ADB Turbo Mouse 4.0 or earlier (the 2-button model) on their desk. If anyone is inclined, could you run ADBParser and do a Talk on register 1 and register 2 of the device...

Awesome, I'll try to replicate what they described.

I'm not up to speed on MAME issue tracking but I'd be happy to look into this if it appears to be a utility-side bug. I confess testing on large files was not a priority during development, transfer speeds on real hardware are slow enough I was not expecting much use like that (obviously that...

At least what I see online suggests the flyback on this model is frequently bad so I was hoping to avoid a 1:1 replacement with the same (possibly faulty) part. Probably should have indicated that in the original question, sorry. Maybe a better question to ask: "Are there any tricks to...

Bumping to see if anyone might have insight into this. If there is another forum that might be worth checking that'd be awesome too, I'd like to get this thing either fixed or moved on to a new home with someone who knows more about CRTs than me.

I should have responded earlier to this addition and the work @Arbee did to get the backing added into MAME. It is a super-cool feature for the emulator and I'm glad scuzEMU has been working well for people. Thanks Arbee!

Cool, thanks for reporting that. For file transfers any SCSI ID that the device is on will show the same file list: for example, if you've got HD0.img, HD1.img, and a bunch of CD images in a CD3 folder, you can use 0, 1, or 3 as the SCSI ID to see the "shared" folder files. The ID is more...

It should work fine, like @Daniël described the toolbox is (nominally) the same across devices. I'd be happy to add BlueSCSI to the list once someone tests it out, I don't own one to use myself and I haven't heard of anyone trying it. If you do, it'd be awesome if you post the results!

Thanks. I checked my stash and unfortunately all I have are the Malaysia ones like superjer2000's. If you're willing could you double-check that the diagonal motion is not a problem when directly plugged into the computer as well? The handling of those basic mice should be pretty consistent but...

Could you post the model of the mouse you're using? It's probably hard to quantify, but could you also give an idea of how far the mouse is jumping/skipping? I may be more/less sensitive than others but I am not particularly proud of current mouse behavior, there is definitely room for...

At present support for pointing devices only follows the classic mouse protocol, not the more advanced "Extended Apple Mouse Protocol" or any vendor-specific addons (not sure how/if that part changes things on the ADB communication side). I don't own one of those to test with, but based on...

Of course, and thanks! Not as things stand right now. I think a generic absolute-positioning driver with a standardized interface would be useful in the future (or for other projects) but it isn't important if all you want is keyboard/mouse switching with real ADB peripherals. The idea was to...

Looks like the USB descriptors were not being handled correctly. I think I've got that fixed now. I also disabled all the device handler ID checks for both keyboards and mice, so anything at the relevant addresses should now be grabbed and associated. If you want to test, the main branch has...

Nah no problem with the posts at all, this is all great stuff. A second set of eyes is super helpful to find problems. Awesome, glad that's working! That's interesting and might be a sign something weird is going on with the mouse interview logic (see below). I do not have one of these devices...

Found the problem: I misread Apple's docs and assumed all keyboards used 0x02 as the default handler. The Standard Keyboard (and probably the IIgs) use 0x01. Support for that is now up on Github and an updated build is attached. Doesn't explain the mouse not working but let me know if that's...

Those are great, thank you! I've got all that hardware minus the IIgs keyboard so I'll do similar setups here this weekend and try to diagnose what's up.

The address shuffle is a good sign, at least some communication is happening. If you plug in a USB cable and set up a terminal, 115200 baud, 8-N-1, on startup it should spit out at least some detail on what's happening. If you can capture that and post it, it might indicate what's going on.

That is indeed completely wrong on the schematic and PCB, the negative pin on the DC jack needs to be on the ground plane. If you tie the connection labeled (-) to the ground pin of C1 that should (poorly) fix the problem (though see below note). Sorry about that, it's a straight-up error on my...

Missed this yesterday, I'll see if I can get some light into this.

Definitely be interested to hear if it works, it technically should but it isn't anything I've tested. If it does function it might be a future use case for the I2C connector, something to allow devices to coordinate switching between themselves.