enabling the debugger with Shift+F12 (laptop)

[jotd]

On my HP laptop, without an external keyboard, I have to press "function" modifier key before I can press a function key.

Works fine to bring winuae interface (function+F12) but fails to call the debugger (function+shift+F12). It just ignores function in that case, and does something else, like disabling wifi.

Any other people with the problem? any way to remap the key with some other key?

[DamienD]

Originally Posted by jotd

Any other people with the problem?

Nah, on both my laptops <F1 - F12> keys are standard presses... no need to press <Fn> first

I have seen what you mentioned on a few recent laptops and IMHO it sucks big time. <F1 - F12> should be the default and then you only have to press <Fn> in order apply stuff like Wi-Fi / Sleep / Screen Output / blah / blah / blah.

What laptop is it that you have? Is there no utility to swap things around / customise?

Not sure how it's a WinUAE issue; though I'm sure Toni could come up with a solution. Obvious, quick workaround is to plug in a standard keyboard.

[ross]

Originally Posted by jotd

On my HP laptop, without an external keyboard, I have to press "function" modifier key before I can press a function key.

on many laptop you have to enter BIOS setup and change settings

ciao!

EDIT: if I don't remember badly on HP You have to press ESC (or F10?) at powerup to enter Startup Menu and BIOS settings

[ShK]

Originally Posted by jotd

On my HP laptop, without an external keyboard, I have to press "function" modifier key before I can press a function key.

Works fine to bring winuae interface (function+F12) but fails to call the debugger (function+shift+F12). It just ignores function in that case, and does something else, like disabling wifi.

Any other people with the problem? any way to remap the key with some other key?

Does END+F12 works?

[jotd]

@all didn't think about that BIOS stuff. I could definitely switch that behaviour by the bios. And no END+F12 doesn't work.

Actually WinUAE crashes when switching wifi/bluetooth off (plane mode), probably because my bluetooth mouse disappears in the process.

And of course standard keyboard fixes it, but I can't carry an extra keyboard at my sons basketball training that would be too nerdy.

EDIT: BIOS allows to change that, so I did that and it works now, thanks, I guess WinUAE can ignore this issue now (I have a lot of crashes with version 3.4 though, but I'll narrow it down in another post)

[emufan]

you're looking for a way to start the build-in debugger?
if so, look at the attached image. F11 choosen as an example.

[jotd]

that's even better! thank you (and I thought I knew WinUAE very well, which I do, but there are so many features)

[dissident]

Well, since I installed WinUAE 4.0.0 on my laptop I can't enable the debugger via Shift+F12 anymore.

I tried to use F11 for enabling the debugger via Input/configuration #1 but still nothing happens.

Does anyone have the same problem and/or knows a solution?

[ross]

Originally Posted by dissident

Well, since I installed WinUAE 4.0.0 on my laptop I can't enable the debugger via Shift+F12 anymore.

I tried to use F11 for enabling the debugger via Input/configuration #1 but still nothing happens.

Does anyone have the same problem and/or knows a solution?

Hi dissident, try latest beta.
I had the same problem in some 4.0 version.

[dissident]

Originally Posted by ross

Hi dissident, try latest beta.
I had the same problem in some 4.0 version.

Hi ross, thanks for the quick reply. I tried it with the 4.1.0 beta version. The same result. The debugger isn't activated.

[ross]

Originally Posted by dissident

Hi ross, thanks for the quick reply. I tried it with the 4.1.0 beta version. The same result. The debugger isn't activated.

END+F12 works?
I started using this because it does not trigger Lev2 IRQ on Amiga.

But sure Toni can help you

[dissident]

Originally Posted by ross

END+F12 works?
I started using this because it does not trigger Lev2 IRQ on Amiga.

But sure Toni can help you

No, END+F12 doesn't work either. Or do I have to config it via input/configuration #1? If so, then with which key code number?

[ross]

Originally Posted by dissident

No, END+F12 doesn't work either. Or do I have to config it via input/configuration #1? If so, then with which key code number?

No, is enabled by default..

[dissident]

Originally Posted by ross

No, is enabled by default..

Okay, thanks for your hints, ross.

Hi Toni, do you have any hints?

[Toni Wilen]

"winuae.exe -log -inputdevicelog 1 -inputlog 1" and check if you see something like this when pressing shortcut:

"STATE=00000 MAX=00001 AF=0 QUAL=010000 'Activate the built-in debugger'"

[dissident]

Originally Posted by Toni Wilen

"winuae.exe -log -inputdevicelog 1 -inputlog 1" and check if you see something like this when pressing shortcut:

"STATE=00000 MAX=00001 AF=0 QUAL=010000 'Activate the built-in debugger'"

Sorry, I don't get it. How can I call winuae.exe with the arguments -log -inputdevicelog 1 -inputlog 1? Via the commands in a configuration file?

Is "STATE=00000 MAX=00001 AF=0 QUAL=010000 'Activate the built-in debugger" then written into the logfile after pressing Shift-F12 or END-F12 ?

[DamienD]

Originally Posted by dissident

Sorry, I don't get it. How can I call winuae.exe with the arguments -log -inputdevicelog 1 -inputlog 1? Via the commands in a configuration file?

Either edit your WinUAE desktop shortcut to be <path>\WinUAE -log -inputdevicelog 1 -inputlog 1

Or run a Command Prompt, change to your WinUAE path and type:

[dissident]

Originally Posted by DamienD

Either edit your WinUAE desktop shortcut to be <path>\WinUAE -log -inputdevicelog 1 -inputlog 1

Hey, DamienD. Thanks for your hint. Changing the desktop shortcut worked fine. I ran WinUAE 4.1.0 beta 5 and got the result attached if I press Shift-F12.

So it seems this is what Toni told. But the debugger doesn't appear still.

[Toni Wilen]

I guess the only possible question is: which beta works and which does not? Make sure to use something really basic, like A500 KS 1.3 in KS hand screen.

[dissident]

Originally Posted by Toni Wilen

I guess the only possible question is: which beta works and which does not? Make sure to use something really basic, like A500 KS 1.3 in KS hand screen.

I've tested it with your public beta 7 version from 10.10.18:

-Quickstart/Model A500/KS 1.3 hand screen/Start in Quickstart mode disabled:
*Windowed display, Debugger can be entered with Shift-F12
*Full Windowed display, Debugger can be entered with Shift-F12
*Full Screen display, Debugger can't be entered with Shift-F12

-Quickstart/Model A500/KS 1.3 hand screen/Start in Quickstart mode enabled:
*Windowed display, Debugger can be entered with Shift-F12
*Full Windowed display, Debugger can be entered with Shift-F12
*Full Screen display, Debugger can't be entered with Shift-F12

So it seems that the full screen display mode prevents entering the debugger.

This is confirmed using my KS1.2-hand screen config with this beta version.