Thank you all for responses to my question. 
I just emailed the original author about this and am awaiting what he has to 
say on this. 

I downloaded Jon Brase’s MOUSKEYS which is great and I did enjoy reading the 
documentation. Long time I haven’t read any doc like it.
It works, but strangely enough not on the two programs I use. The program 
(EVE.EXE) doesn’t seem to care at all about what MOUSKEYS is set up to. The 
program in question, called EVE.EXE cancels all conventions in DOS and sets it 
all up anew. Amazing.  
As much as I like MOUSKEYS, till now it doesn’t seem to team up with the 
program. 

This makes me thinking that also ERIC’s sketch for a TSR (yes, Eric, you are 
right, it’s all »Chinese« to me) won’t do in this case either. 

So I just will see what the original programer might have to tell, and if of 
interest, allow me to share it with you. 

Thanks, regards, Thomas

> On Sat,20210410- week14, at 03:39, Adam Nielsen via Freedos-user 
> <[email protected]> wrote:
> 
>> DOS itself doesn't use/support any mouse, it is up to an application to 
>> interpret the responses given through the INT 33h API, which is 
>> implemented either by the BIOS or a "driver" (TSR_ like CTMouse. While 
>> probably not completely impossible to add another TSR that would 
>> intercept INT33h and instead feeds simulated keyboard events into INT 
>> 9h. I am not sure that something like this exist, at least neither 
>> myself nor any of my friends/clients ever had a need for such a tool...
> 
> Not quite so helpful but the old XT I had many years ago (an Amstrad
> PC1640) had the mouse connected to the keyboard rather than a serial
> port as was usual for the time, and I believe it worked by sending
> unused key codes in response to mouse actions.  The mouse driver would
> pick up these key codes and handle the int 33h stuff.
> 
> However because of this, the machine could be configured at the
> hardware level to send different key codes for the mouse buttons.  So
> running a DOS application to change the machine's CMOS settings was all
> it took to reassign the mouse buttons to send any keystroke you wanted,
> and the setting would persist across power cycles without needing any
> TSR running.
> 
> I wonder whether the author of the original application being discussed
> here had a similar machine, and assumed all PCs could have their mouse
> buttons configured similarly.
> 
> Cheers,
> Adam.
> 
> 
> _______________________________________________
> Freedos-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 



_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to