Comment on The driver for my mouse occupies over 1 gb
albbi@piefed.ca 2 weeks agoThat driver was using 0.5% of system resources! I thought it would be worse when I saw "259 blocks free", but overall that's pretty good.
Comment on The driver for my mouse occupies over 1 gb
albbi@piefed.ca 2 weeks agoThat driver was using 0.5% of system resources! I thought it would be worse when I saw "259 blocks free", but overall that's pretty good.
HugeNerd@lemmy.ca 2 weeks ago
Well that’s just a screen shot of the directory listing of the GEOS disk from the 64’s default “OS”, the BASIC interpreter. That 3 block file also contains information that only GEOS sees, the actual executable 6502 code is likely in the 500 bytes, if that. The user manual for the mouse actually contains an assembler listing of the driver. It ain’t big.
The 64, of course, was never designed with a mouse in mind, so Commodore engineers used the analog paddle inputs to encode the mouse XY motion. So the “driver” really just reads the A/D converters for the paddles and fudges some kind of motion information out of it.
It works quite well. The 64 only has a 320x200 display, so it’s not like you need a gaming 1000DPI 1ms mouse.