02 June 2007, 22:40 | #1 |
Bug hunter
Join Date: Jul 2006
Location: Italy
Age: 48
Posts: 2,171
|
Where is Amiga CTRL+c (d, e, f)?
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... |
03 June 2007, 10:01 | #2 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 7,030
|
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.
|
03 June 2007, 10:47 | #3 |
Bug hunter
Join Date: Jul 2006
Location: Italy
Age: 48
Posts: 2,171
|
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 (?)... |
03 June 2007, 11:03 | #4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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.
|
03 June 2007, 11:21 | #5 |
Bug hunter
Join Date: Jul 2006
Location: Italy
Age: 48
Posts: 2,171
|
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. |
03 June 2007, 11:35 | #6 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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. |
03 June 2007, 11:40 | #7 |
Bug hunter
Join Date: Jul 2006
Location: Italy
Age: 48
Posts: 2,171
|
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... Last edited by hexaae; 03 June 2007 at 12:00. |
03 June 2007, 11:50 | #8 |
Bug hunter
Join Date: Jul 2006
Location: Italy
Age: 48
Posts: 2,171
|
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 Last edited by hexaae; 03 June 2007 at 12:59. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
A600 will not do a warm reset - Ctrl-Amiga - Amiga | kipper2k | support.Hardware | 25 | 02 May 2024 05:17 |
WinUAE 2.0.1 Input panel: map Ctrl to CapsLock | Photon | support.WinUAE | 8 | 21 September 2015 10:43 |
Amiga 4000D Ctrl-A-A not working. | Turran | support.Hardware | 10 | 28 January 2013 10:42 |
Ctrl + Function Keys no longer working in 2.4.0+? | killergorilla | support.WinUAE | 4 | 20 September 2012 15:53 |
All versions of Winuae after 2.1.0 freeze mouse when I Ctrl-F12 to Fullscreen | KoasKid | support.WinUAE | 6 | 09 July 2011 02:07 |
|
|