Unsolved [DOSBOX] Mouse 2 ?

[jomofcw]

@dragu thanks for your answer again.
In a comment from your link :
"In Linux I would translate the USB Mouse output to the COM interface to simulate a serial mouse. That works well, despite of a little laggy 2nd mouse."

It would be the solution, but I really dunno how to do that, sadly :-(...
As it's kinda an hadware things, perhaps @Substring or @rockaddicted could help ?

[jomofcw]

Perhaps usefull ? http://www.tldp.org/HOWTO/Serial-HOWTO-10.html#ss10.4

[Substring]

@jomofcw can't you add a serial2=directserial realport:/dev/input/mouseX with the /dev/input/mouseX being the right input device ? I know nothing about dosbox configuration

[jomofcw]

@substring I've tryed it with "serial1" and it doesn't work. I'll try with "serial2" instead, to see.

[Substring]

@jomofcw You should check how mice are handled in dosbox : if it emulates a PS2 port or several DB9 serial ports.

[jomofcw]

@substring if I understand it well, it does both. Default/main is PS2, but the "serial" cfg enable us to get some DB9 equivalent.

[voljega]

@jomofcw dosbox.conf says that about the serial parameters :

[serial]
serial1: set type of device connected to com port.
Can be disabled, dummy, modem, nullmodem, directserial.
Additional parameters must be in the same line in the form of
parameter:value. Parameter for all types is irq (optional).
for directserial: realport (required), rxdelay (optional).
(realport:COM1 realport:ttyS0).
for modem: listenport (optional).
for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
transparent, port, inhsocket (all optional).
Example: serial1=modem listenport:5000
Possible values: dummy, disabled, modem, nullmodem, directserial.
serial2: see serial1
Possible values: dummy, disabled, modem, nullmodem, directserial.
serial3: see serial1
Possible values: dummy, disabled, modem, nullmodem, directserial.
serial4: see serial1
Possible values: dummy, disabled, modem, nullmodem, directserial.

[jomofcw]

@voljega yup, seen.

That's why I think that solution is about the "realport" option.
ttySx is link to physical DB9 port linux. That's why I would like to test with ttyUSBx, but it probably need to be defined.
I will make few more test case tonight.

[Dragu]

As it reads in the description, mouse 1 is the input from driver, so for mouse 1 you have no special needs.
For mouse 2, they dont talk about driver, they just analyze the input from another RS232 different from COM1, so COM2-x.
With serial mouse, true RS232 works with voltages -12 +12, no TLL level. So if you connect a serial mouse to an serial 5V UART, the problem will come from the mouse. There are some boards that use MAX232, a chip that makes from 5V TLL 10V RS232.

[jomofcw]

@dragu I'm not sure to understand all of that ... (on devrait peut être en discuter en Français sur IRC à l'occasion ).
Perhaps there is confusion : Recalbox is installed on a Rasp Pi 3b, so the only ports I have, out of the box, are USBs.

[Dragu]

Le protocol de transmission entre une souris USB et une souris sérielle RS232 est différent, et donc déja là il se peut un problème. De toute façon, je doute que tu arrive avec une souris USB, aussi à cause du protocol. Les souris sérielles attendent un voltage différent de 5V. Alors il ya des Chips qui transforment +5V en - et + 10V. Comme le Max232. Si tu essai avec un câble USB - Sériel qui comporte ce chip, ça doit d'abord fonctionner sur une prise USB de ton PC. Après tu peut tester sur PI.