Thanks for referencing that other thread!

Great! With /* Define if using video enabled on SEGV signals. */ // #define ENABLE_VOSF 1 there is no segfault when I start BasiliskII with gdb. I'm still using MSYS/mingw32. The configure option --disable-vosf mentioned here does not seem to exist. What does "video on SEGV signals support"...

One more alternative: https://github.com/rakslice/macemu/tree/sheepshaver_mingw32_wip It it for MSYS2/mingw32. BasiliskII runs fine from gdb with -ggdb -O0. I tried that and got a segfault, too. So may be its my setup. I'm using MSYS/MinGW from http://www.mingw.org/. Should I be using MSYS2 and Min...

Thanks for your suggestions. I'll have a look at rakslice's repository.

kanjitalk755 wrote:BTW, if you use Windows10, how about WSL?
I tried under WSL, I succeeded to run BasiliskII from gdb with -ggdb -O0.

This would be a Linux binary of BasiliskII using a Windows X server, right?

I can keep that one, but doesn't Control Left --> Option give you that also? It does. But I still hope that the control key can eventually become Control again. And I find it easier to remember that the "special" menu key can be used for all those special characters. Actually, in my keyco...

Well, I'd like to stay with Menu --> Option because that would my to type all special characters that my AutoHotkey script does not provide. Otherwise, I agree. Should I manage to run BasiliskII in gdb, I will try to look into how Ctrl Left influences Alt Right, because I think Control Left --> Cont...

Shift Left --> Shift Control Left --> Control Logo Left (useless) Alt Left --> Command Space --> Space Alt Right --> Option Logo Right (useless) Menu --> Option Control Right --> Control Shift Right --> Shift Yes, that would be good. But I'm not sure we have found a way to achieve that with keycode...

Then which key did you use for the Option key? I use my virtual Mac very sparingly. I got along without one :smile: This works fine for you. But it can not be used for a general keycodes file for distribution. As far as I am aware, the Menu key is not available on all Windows keyboards. That's true...

The reason I redefined the mapping of Alt Right in your keycodes files was that I couldn't get the AutoHotkey script to work when both Alt and Win keys were pressed by AltGr as happens with this mapping: 230 55 # Alt Right (--> Command) My redefinition of AltGr (Alt Right) was ment to avoid that vir...

I am not sure, but I suppose this makes it possible to use some of your familiar Windows key combos for special characters inside BasiliskII. Wouldn't it be a lot of work to do that for all (100+) special characters? A mixture of Windows and Mac key combos does not seem a good idea. Generally, I th...

Your new keycodes defines identical mappings for Alt Left and Alt Right: 226 55 # Alt Left (--> Command) 44 49 # Space 230 55 # Alt Right (--> Command) In the Tastatur app, pressing Alt Left will highlight both Alt keys. But pressing Alt Right will highlight both Alt keys plus both Windows Logo (Mac...

cxmon does not look like a potential substitute for GDB to me. I have found references to using cxmon for BasiliskII only in the context of the JIT compiler. Could you possibly point me to the part of the documentation you are referring to? To check whether the JIT compiler might cause the GDB probl...

I understand that pressing the Left Alt key highlights the Command keys in the Tastatur app and that it works as expected. (Note that on a Mac keyboard the name "Alt" is used for the Option key, the key between the Control and Command.) True, I'm using the labels on the keys of my keyboar...

Sorry, I should have reported that Basilisk starts (just as without gdb) and complains that the keycodes file specified in the configuration is not available. Therefore, the configuration file and the ROM file are found and read. The segfault does occur after Basislik has opened a blank window. So I...

In reality, the paths specified as option arguments contain blanks, so the line looks more like $ gdb --args BasiliskII.exe --config "path to config file" --rom "path to ROM file" I added single quotes but got $ gdb --args 'BasiliskII.exe --config "path to config file" ...

I'm trying to debug BasiliskII in Windows 10 with MinGW (GCC 8.2.0). To this end, I have downloaded the sources of SDL2 and BasiliskII as described in Build kanjitalk755's BasiliskII code in Windows . After sucessfully compiling and installing both, I was able to run this version of BasiliskII witho...

It is difficult to test things I can not see myself. To prevent confusion on my side, do not edit the keycodes files. We will start from the beginning. Start with this keycodes file. It has the regular SDL2 to Mac mappings: https://ronaldpr.home.xs4all.nl/keycodestest/BasiliskII_keycodes.zip I will...

Oh, stupid me! Good thing you spotted that! Actually, there are two sources of confusion you pointed out: A wrong entry in keycodes file and a difference in keyboard layout and thus key names. With #230 55 # Command (<- Windows Alt Right, Alt Gr) 230 58 # Option (<- Windows Alt Right, Alt Gr) pressi...

Thanks, emendelson. Unfortunately, the new binary gives the same results as the older one with the redefined keycode 230 55 # Command (<- Windows Alt Right, Alt Gr) Pressing Alt Gr highlights both Ctrl and both Alt keys in the MacOS key application, the labels of the number keys don't change when Al...

I just found this when browsing through what I assume to be the source used to build BasiliskII 30-09-2019: Feature request: For SDL2, in keycode mode, allow remapping of modifier keys. Wouldn't that explain why all attempts to remap Alt Gr failed?

Switching to full-screen works, but does not change the way keys are handled. (As a side note: I have a two monitor setup, BasiliskII uses one of them in full-screen mode. Parts of it look like I should be wearing old red-green pseudo 3D glasses. I guess the proportions don't match.) Is there a SDL2...

Looking closer at the "Keys" application (its German name is "Tastatur") was a good suggestion. 1. In the "Keys" application ("Tasten" in German?) in BasiliskII: When you press the Alt Gr key on your physical keyboard, does the middle one of the three modifier...

So am I :lol: The procedure you describe is what I have been doing. The only difference is that I'm not using the GUI. I'm using a text editor for the configuration file and the keyboard file. I can't tell why the value for keyboardfile is ignored, but any other combination than a value BasiliskII_k...

I applied the changes to your second keyboard file named keycode. I had to rename it though, because the value to keyboardfile seems to be ignored. I ran another check to verify I'm modifying the proper keyboard file. I changed 4 0 # A to 4 1 # S and the A key produces an s. But the change from 230 ...

So, if you want to replace the Alt key by the Alt Gr key as option key in BasiliskII, you could try to change the line: 226 58 # Option to: 230 58 # Option Thanks for your new keyboard file! First, I successfully tested whether the keyboard file is used at all by changing the Mac keycode of key 5 t...