Willy wrote:
>In addition to my previous post, here are the test results
>from the "bernie.arachne.cz CTMSs".
Perhaps you should have sent this to me directly? I'll answer here anyway
(so people know *why* things worked as they did for you).
>1: installed, but didn't work at all (it was not visible, but reacted
> on the buttons sometimes).
This was only in text-mode (edit for instance) I assume. the lack of a "T"
in the name makes text-mode unusable (it still works but there's no mouse
cursor visible).
>2: worked alright, maybe a bit too fast in QPV and QPNG.
Too fast? So you could actually see a diffrence when I optimized the code -
I wonder if that was stupid of me, but no program should depend on the
mouse driver to be slow IMHO. Myself I see no diffrence.
>3: worked, but in QPV, it was way too slow (looks like it's glued),
> in QPNG it was slightly better.
Yes in QPV you scroll one pixel at a time (or something like that). This
was something expected - "S" doesn't allow the program to set the speed.
>All with driver defaults, except trying to force COM1 and IRQ3 and 4,
>with no result.
Hmm.... hmm... hmm... Have you tried 1.6a?
>/U worked alright, but only with the correct version.
Yes - this information will be added (I was already going to).
>Reminder: the originals (DRMOUSE, CTMOUSE 1.61) never gave me such
>trouble (only 7k in UMA, what are you trying to fix ?).
7K? So the memory used is going up (1.6a uses 6K IIRC). I'm trying to get
it down in memmory use - under 3K and still usable in graphical programs
(that don't change the speed) is doable rather easily.
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...
