On Wed, Jun 06, 2007 at 09:57:18AM +0100, Paul wrote:
Hi Chris
On Wednesday 06 June 2007 08:43, Chris G wrote:
Setting Device to point to /dev/ttyS[0|1|2|3] should do it. Protocol "auto" normally senses if it is a two button or scroll mouse.
Thank you! With additions like the above I am now working at 1024x768 and above and I have ye olde Mouse Systems mouse working.
Much of the settings are mentioned in the multitude of xorg man pages. Admittedly, far from easy to find, and a few of them are somewhat cryptic.. But at least we have the source code when head scratching is not enough ;-)
Yes, that's the problem. The xorg.conf man page describes the format of the xorg.conf file but doesn't give any of the actual values (e.g. it doesn't tell you that MouseSystems is a valid driver name). I knew what I needed to change but didn't know the actual values I needed to enter.
On Wednesday 06 June 2007 08:48, Chris G wrote:
The system isn't all that old, it has a PS/2 mouse connector but I don't have a (decent) PS/2 mouse whereas I do have some very usable Mouse Systems optical mice.
Even PS/2 is regarded as "legacy" by some...
It has USB as well! :-)
It's all up and running now and seems pretty OK running Ubuntu 7.0.4, it has 384Mb of memory, a 40Gb hard disk and an AMD K5 (I *think*) processor.
Ooooo... Kinda makes my collection of Pentium 133 & 166 boxen look old.
The oldest I'm currently running is the box I just set up to put in the garage running Slackware. That's actually an AT (as opposed to ATX) format box with a AMD Duron 800Mhz processor I think. It runs Slackware 11 with fvwm2 quite happily. I wanted it there so I could access PDF manuals and update my maintenance records while I actually do things in the garage.