Hi Michael,
> Just as exercise you could first convert
> he latest cutemouse into a JLM
You misunderstood me. I want a JLM which talks
to the real BIOS and/or hardware on one end and
pretends to be a PS2 BIOS mouse on the other.
The existing cutemouse driver would be loaded
AFTER the JLM, see the fake PS2 BIOS mouse and
be happy - even if your actual mouse / touchpad
talks a protocol language not known to ctmouse,
good old cutemouse will now understand it ;-).
The existing ctmouse driver already does a lot
of work for drawing mouse cursors and talking
to DOS programs - none of which depends on the
type of mouse hardware you have. This is why I
suggest to use a JLM as helper but keep normal
ctmouse on the DOS side... Of course you could
save a few bytes of DOS RAM by turning ctmouse
into a JLM but that would be too much work. The
many links between ctmouse and other hard- and
software make it pretty hard to port to a JLM.
You can get more RAM for less work by turning
DOSLFN into a JLM :-). Note that turning e.g.
DISPLAY into a JLM will hardly help you at all
because 4 + 3.5 + 2 = 9.5 kilobytes of its DOS
RAM footprint is for giving DOS apps access to
copies of the font in DOS RAM. Of course it is
a very interesting idea to give DISPLAY some
command line option which makes it show NONE
or only 1 AT A TIME of the fonts to DOS apps,
saving 5.5 or even 9.5 kilobytes of DOS RAM :-)
Using either option would reduce compatibility:
Programs which use graphics mode but show text
might show distorted text ("one font" option)
or would show text in the BIOS font instead of
your custom (eg. CP858 with Euro sign) font...
Still I think it would be very good to have the
option as user - because now, you only have a
choice between "do not use Euro sign at all or
let DISPLAY eat more than 10 kB of your RAM".
> I have a logitech mx518 optical mouse with the
> main features two buttons and one wheel.
Those will be supported by ctmouse 2.1beta4 already,
please try that first...
> Plus a lot extra buttons I am not using that much on Windows.
> www.logitech.com/index.cfm/mice_pointers/mice/devices/187&cl=us,en
Wow 8 buttons: Forward, Back, Scrollup, Scrolldown, Menu
plus 3 usual buttons ;-). And 1800/800/400dpi resolution.
> Can't imagine how these other buttons could become
> useful for me in DOS as there is no much application
> development. It's connected by a USB to PS2 converter.
That should work, but indeed the question is what you
or other people would do with the extra buttons in DOS.
I mean you could load some TSR which lets you simulate
keyboard keypresses by mouse buttons, would that help?
> My second input device is medion/logitech USB idr
> receiver and a cordless mouse I am using for remote
> control from sofa. :) So I vote for USB mouse/keyboard
> support.
Your BIOS should already support those and make them
visible to DOS as "normal PS/2" devices anyway... How
many wheels and buttons does that cordless mouse have?
Eric
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
