@max1zzz Since 72 pin isn't possible, I would rather prefer a custom RAM board with brand new connectors than dodgy reclaimed 30 pin sockets. IDC like connectors seems doable and period-correct, so…
If the RAM board has open source gerbers or you do provide them, it's not really an issue imho...
I seem to remember the opposite.
The way the Carrera works is that it's patch some handlers in the operating system. There is a system specific detection that applies different patches for different Mac Models, and a few other things (Virtual Memory, RAM size maybe). If you are using a custom...
That's how it's done for ADB pointing devices with Quack. There is a lightweight ADB Manager inside than handle the mouse part. Obviously Quack lacks the keyboard part as it was not designed to provides keyboard services
I do that upside down and got some results but with qfps it's anoying because not all pins heat at the same time so sometimes a few of them get bent when the CPU fall off
With PDIP and PLCCs as well, most of them are working after. Tap gently on the PCB with some wood something to get the part...
indeed, that 34 address is weird
ADB Parser should move the Apple logo to the last active device. When the keyboard is glitching, is the Apple moving on $3 or $F ? (Try to not move the mouse)
Doesn't make much sense here as well.
Could this be that the collision system doesn't work for some reason and both devices share the same ADB address ? Indeed trying with a real keyboard would help
How many keyboard does ADB Parser show ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.