Where is Amiga CTRL+c (d, e, f)?

[hexaae]

Hi,
using emulated WB 3.9 I've noticed that CTRL+C or CTRL+D, E, F do nothing. Why? The strange thing is that key catchers (like MCPPrefs...) correctly recognize CTRL+C, but from Shell is ignored...

[thomas]

Probably because you have configured a joystick port as Keyboard Layout B which means that the right Ctrl key is used as fire button. Use the left Ctrl key instead or configure another keyboard layout for the joystick port.

[hexaae]

Well, obviously it's not my case And MCPPrefs also catches CTRL+C as key combo...
The settings are ok, it's just that usual CTRL+C is ignored. Have to break from within Scout only
It's like the emulator doesn't send the correct sequence or interrput (?)...

[Toni Wilen]

Easy test: boot with WB 1.3. If CTRL+D works, it is your 3.9 AmigaOS installation (perhaps some tweaking program etc..), if not, it is emulation keyboard configuration.

[hexaae]

Another test I can do? Can't use ROM and WB 1.3.
I tried also to re-edit keys with Amiga keymap editors but still nothing... CTRL+C, D are ignored even if the keys are recognized.

[Toni Wilen]

You don't need 1.3 ROM, WB 1.3 disk (or any bootable disk with 1.3-style bootblock) is only requirement (because it always opens the shell window)

I am 99.99% sure it has nothing to do with emulation. Emulator only sees hardware keycodes, AmigaOS does the rest.

[hexaae]

So should work even booting 3.9 but without SSeq. I can test this... right?
Yes, it seems strange to me too but WB it's ok and always worked fine with these settings on a real A1200 + B1260... Can't see what's wrong with keyboard.
Mmmh, the fact that I edited my Keyboard layout on Vista, with 'Microsoft Keyboard Layout Creator 1.4' (obviously CTRL+C from MSDOS do works) and created an 'Italiano - Custom' profile can have something to do with it? Have to try with std Italiano... Stay tuned...

No, as expected has nothing to do with WinUAE keyboard detection...

[hexaae]

Very strange... booting without SSeq "C:List ALL" gets stopped by lctrl+c... but I still can't understand what's wrong with fully loaded WB... mmmh... only thing that could change input behaviour is MCP but worked fine on real A1200... let me test this...

- 2 mins later -
Hey!! It's the crappy 'winuaeclip' that steals the break signal!! Without running this everything works as expected with CTRL+C, D, E, F... Ok, I've sent a mail to the author accordingly with AmigaPrograms/winuaeclip.txt