Bug: Powerconnect in Openmsx detection?

Page 1/2
| 2

By Wlcracks

Champion (410)

Wlcracks's picture

20-01-2020, 16:36

i can reproduce this every time.

Powerconnect in MSX

Login or register to post comments

By Manuel

Ascended (16129)

Manuel's picture

20-01-2020, 19:45

Haha! Can you try with a recent development build?

And if that still reproduces the issue, can you enable keyboard logging?
See https://openmsx.org/manual/commands.html#kbd_trace_key_presses

By sdsnatcher73

Paladin (799)

sdsnatcher73's picture

20-01-2020, 19:59

Here is a Windows build from the latest commit: openMSX.0.15.0-636-g3c01256b9.zip

By Louthrax

Prophet (2172)

Louthrax's picture

20-01-2020, 20:23

My (really) 2 cents on this: a joystick or some USB device is mapped to the keyboard (at least the "=" key), and the power connection causes some noise on that device...

By Wlcracks

Champion (410)

Wlcracks's picture

20-01-2020, 21:18

Louthrax wrote:

My (really) 2 cents on this: a joystick or some USB device is mapped to the keyboard (at least the "=" key), and the power connection causes some noise on that device...

Almost right, i was pressing = with my "third arm" duh.
No nothing connected, original dell laptop, legal windows 10, no mods only cdrom->harddrive mod.
When i open notepad, and insert the plug nothing happens (no ==== -ing)

This build you pointed me is the same response.

keylog:
when started inserting the plug only the first 2 lines appeared.When i exit the openmsx window the third appeared.

---
Key released, keyCode: 0x400123, keyName: F10,RELEASE
Key pressed, unicode: 0x0000, keyCode: 0x0003d, keyName: EQUALS
Key released, keyCode: 0x40003d, keyName: EQUALS,RELEASE
---

Btw i am not bothered by this "bug". So no worries. Just reporting.

By Manuel

Ascended (16129)

Manuel's picture

20-01-2020, 22:03

So, openMSX gets something reported by SDL, the keypress of the =... quite funny. Please do test with the latest development build. It uses the latest SDL2 library, which may not show this behaviour.

By Wlcracks

Champion (410)

Wlcracks's picture

21-01-2020, 14:59

i used the zip file above, i don't know where to find a development build.

By sdsnatcher73

Paladin (799)

sdsnatcher73's picture

21-01-2020, 18:57

Wlcracks wrote:

i used the zip file above, i don't know where to find a development build.

That was the latest development build you downloaded, normally you can get one from https://openmsx.dev/ but it’s quite a bit behind (so I started building my own).

Did I understand you correctly if I say the issue happened with that build as well?

By Manuel

Ascended (16129)

Manuel's picture

21-01-2020, 18:58

If you used that zip file, openMSX shows a version number different than "0.15.0", but more something like "0.15.0-636-g3c01256b9". In that case you are already using a development build Smile

By Wlcracks

Champion (410)

Wlcracks's picture

23-01-2020, 15:51

When i start this one in windows, and press menu i get this:
And lockes up.
In the terminal same error "warning: Error executing delayed command: Invalid keycode: WORLD_92"

yeah...

By Sylvester

Champion (409)

Sylvester's picture

23-01-2020, 17:51

@Wlcracks, had the same problem, in my case i had an _osd_menu.tcl in my openMSX/shared/scripts directory (probably from an old version). After removing it, openMSX did start without the error.

Page 1/2
| 2