Welcome, Guest. Please login or register.


Author Topic: BoxSoft Mouse Interface (Read 36619 times)

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #105 on: 2014.October.31. 18:44:09 »
Meanwhile I'll adapt a serial trackball with a PS/2 ball mouse. Also I have a touch surface from a laptop that I can connect.

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 32.0 Firefox 32.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #106 on: 2014.October.31. 23:20:16 »
I've tested almost all PS/2 mouses I've found. Even the slowest ones double, quadruple or more  the DPI of the Neos mouse, that have the best feeling moving "slowly" but accurately pixel by pixel.

All do strange jumps to the following position, then they seem to work like the internal joystick cursor, that jumps by character cell to character cell, but very fast.

That about velocity, but all have the wrong response to direction, as I described earlier.

Correcting the directions in a ball mouse is easy, but I don't know how to do it on an optical mouse.

Better could be to modify a Mouse.xr driver especially for that PS/2 to MSX converter, dividing the resolution and correcting the directions in the software.

But for me can be a hard work...

Online Zozosoft

  • EP addict
  • *
  • Posts: 13176
  • Country: hu
  • OS:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
    • http://enterprise.iko.hu/
Re: BoxSoft Mouse Interface
« Reply #107 on: 2014.October.31. 23:23:42 »
The russian MSX converter have a resolution jumper. And also support joy mode.

I try to build one, but currently don't detect the mouse :oops:

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 32.0 Firefox 32.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #108 on: 2014.October.31. 23:37:26 »
Mine is www.KMTech.co.uk from Ebay, and also has a resolution jumper, but without it the DPI is even greater....

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Unknown Unknown
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #109 on: 2014.November.07. 15:32:58 »
I have the trackball almost finished, and today arrived the Neos replacement. At the side a PS/2 touch surface rescued from a broken laptop.
« Last Edit: 2014.November.07. 15:37:45 by gflorez »

Offline Z80System

  • EP addict
  • *
  • Posts: 3835
  • Country: hu
  • OS:
  • Mac OS X 10.10.0 Mac OS X 10.10.0
  • Browser:
  • Chrome 38.0.2125.111 Chrome 38.0.2125.111
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #110 on: 2014.November.07. 19:03:57 »
These things surprisingly goes well to each other ...

(Maybe this was a direct translation of a hungarian expression what does not mean anything in english...)

So ... these thing surprisingly pass to each other ... :) Or such ...
« Last Edit: 2014.November.07. 19:51:58 by Z80System »
Z80 System

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #111 on: 2014.November.07. 22:54:07 »
Yes, they mix and match like an orthopaedic leg and a false teeth...... Joke :lol:

If you expand view of the picture you can see the frame of the touch surface is indeed a chunk from a laptop, raw cut with a shaw.....

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #112 on: 2014.November.08. 11:05:20 »
Ok, now the "new Neos" mouse(and all PS/2 device thrown to the adapter...) works fine but still only with the 3352 bytes driver. Why?

When I run the little test program, all the other usable versions(2842, 3178 and 3196) give the error:

*** Device does not exist.
150 OPEN £1:"mouse:"

Even when some of they show the driver loaded when you write :help.

Zozo, I've seen the 3352 bytes version is a relocatable module, can you extract it to compare with the disassembly of the 3178 version?

Do the other versions work for you? May be the problem my "actual" configuration?
« Last Edit: 2014.November.08. 14:17:12 by gflorez »

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #113 on: 2014.November.08. 22:49:34 »
I've extracted it by myself. I will disassemble it and compare the code, but I'm not good at it....

Org is at 0x12DB(4827dec).

Online Zozosoft

  • EP addict
  • *
  • Posts: 13176
  • Country: hu
  • OS:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
    • http://enterprise.iko.hu/
Re: BoxSoft Mouse Interface
« Reply #114 on: 2014.November.09. 00:30:13 »
Try :PB command after loading MOUSE.XR then start the BASIC program.

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #115 on: 2014.November.09. 12:37:28 »
 I've tried several times to load Paintbox, but it freezes. So then I tried only with the Mouse.xr drivers. Maybe I have to execute :mouse then...
« Last Edit: 2014.November.09. 12:49:32 by gflorez »

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #116 on: 2014.November.09. 13:34:03 »
No, ":mouse" doesn't work on any case, neither ":help mouse". The info is only shown with ":help" alone.

Neither Kevin Mount, the author of the "PS/2 to MSX mouse adapter", answers me... 

I think the only way is to modify the driver that works. First making "Fire" button work, and then doing two versions, one for the Neos alone, and the other for the adapter.

I'm yet disassembling.

Online Zozosoft

  • EP addict
  • *
  • Posts: 13176
  • Country: hu
  • OS:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
    • http://enterprise.iko.hu/
Re: BoxSoft Mouse Interface
« Reply #117 on: 2014.November.09. 14:15:45 »
Not a :MOUSE, use :PB! This is originaly command from the Paintbox to MOUSE.XR, which is add the MOUSE: device to the system.
Then you can open MOUSE: channel.

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows XP Windows XP
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #118 on: 2014.November.09. 15:20:35 »
Ok, then. Now all versions applicable work for me. Curious, they load the driver but don't run it... and then the wrong command ":pb" produces "***Channel exists", but makes it work....

It could be interesting to know why this behaviour an how to fix it.

May be the relocatable extension does better the task and the others not?
« Last Edit: 2014.November.09. 18:28:50 by gflorez »

Offline gflorez

  • EP addict
  • *
  • Posts: 2452
  • Country: es
  • OS:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 33.0 Firefox 33.0
    • View Profile
Re: BoxSoft Mouse Interface
« Reply #119 on: 2014.November.09. 21:33:08 »
Observing the two codes:

3352 bytes version:

label_12e4h:  ld a, c
                  cp a, 4h
                  jr z, label_1312
                  cp a, 3h
                  jp z, label_133b
                  cp a, 8h
                  ret nz
                  call label_14ee
                  ld a, (1353h)
                  set 6, a
                  res 7, a
                  ld (1353h), a
                  ---------

 

And the 3178 bytes version:

loc_C0A9: ld a, c
                  cp 4
                  jr z, loc_C0E9
                  cp 3
                  jp z, loc_C112
                  cp 2
                  ret nz
                  ld a, (de)
                  cp 2
                  ret nz
                  inc de
                  ld a, (de)
                  dec de
                  cp 50h ; 'P'
                  ret nz
                  inc de
                  inc de
                  ld a, (de)
                  dec de
                  dec de
                  cp 42h ; 'B'
                  ret nz
                  call sub_C2C5
                  ld a, (byte_C12A)
                  set 6, a
                  res 7, a
                  ld (byte_C12A), a
                  ------------


It seems that only suppressing a few lines from the very first routine the driver auto-activates itself at the loading.