Search results

Yeah I wouldn't be shocked if either the G3 or the cache was being driven too hard too instead of the bus. I'm not sure how common it was for them but this unit is on a green PCB, most of the pictures I've seen of Newer's stuff had black/dark brown soldermask: maybe a cost-reduction step taken...

Okay I think I have this fixed. Tl;dr version is I needed to set DIP switch 3 on the CPU upgrade to ON. To explain here's a long(ish) narrative of the troubleshooting, along with the red herrings I ran into along the way. The "incompatible" message from the driver in my previous post was fixed...

Found it in Gauge PRO. It is active, listed as "Enabled (I/O Incompatible)", which isn't an encouraging way of describing it.

That's a great question; I honestly don't know. I have the MAXpowr 2.0.5 extension installed but some Googling seems to indicate that Newer was addressing that via ROM updates that required an RMA (see here) rather than software. Is there a way to check if this is applied?

I've got a Newer Tech MAXpowr G3 upgrade card (400/200 DT351) on a PowerTower Pro logic board. When verifying checksums on larger DiskCopy self-mounting images, each time the calculation ends with different (and wrong) checksum values. Swapping RAM or loading the .smi files off the network...

Glad this got bumped, I missed it initially. Will be adding this to my systems to zap that prompt. Thank you for putting this together and sharing the source!

Feels like it is very dependent on how the computer was stored. Drives that work fine seem to be more common in computers that are clean, less yellowed, etc... climate controlled storage basically. Most of the drives in systems I've gotten out of sheds/barns/whatever are dead. Obviously there...

Unfortunately I do not have any for sale myself. To be completely candid, I do this kind of hardware tinkering just as a hobby and I have lots of other work/life/project pressures that will cause me to stop working on things for fairly long periods at a time (ask anyone with a scuznet, heh). A...

Support has been added for emulating different varieties of Kensington Turbo Mice, which can now be toggled in the configuration system. This has been letting me use my 5.0 with the Turbo Mouse 4.0 driver. I also fixed up a major bug with the config so it should now actually be usable. Release...

Agreed. Also consider older 4:3 Dell LCDs, they frequently supported sync on green. This list looks pretty comprehensive if you want specific models: http://ps-2.kev009.com/sog/

Development work is slowly continuing. Highlights of recent items: Experimental support added for Kensington Turbo Mouse trackballs, enough for 5.0 (4-button) models to be recognized by Mouse Works 5.7. This is early and there certainly are bugs present, but I figured some users might want to...

What I've got so far can be found here for now. Comments welcome. I'll continue to flesh this out further.

It is! 😁 Plus I figured the community would benefit from other devices being able to emulate these trackballs, the Kensington drivers seem pretty good. Goal was to document well enough it could fit in with the superb ADB protocol documentation @Tashtari has already collected GitHub.

That new register 2 is great, it looks more like the one from 5.0 after configuration but with some interesting differences in specific values. I think I have enough to try making an emulated device and see if the Turbo Mouse 4.0 driver is willing to talk to it. That behavior matches what the...

Perfect, that is exactly what I needed, thank you! Response is notably different from 5.0. Reg 2 looks like it kind of has a similar format, but values that didn't appear to do anything on mine are different on 4.0. Hmm. If you don't have the drivers loaded, which device shows as active when...

Thanks, very much appreciated. Out of curiosity do you know what version of the driver you're using that handles 3.0 but not 4.0? If it doesn't work with the earlier devices I'd like to experiment with that version locally as well.

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