Activity for Jonas Hultén
-
Jonas Hultén posted a comment on ticket #1963
That worked, so the other option to start with RAMLink needs to be removed then. You can close this ticket.
-
No, the bug isn't fixed. I downloaded revision 45040 and tried the test case I provided. It still prints VICE EMULATION. So the problem remains. This is how I start VICE (with a valid RAMLink image) to reproduce it. ~/temp/vice-edge/vice/src/x128 -80 -directory ~/temp/vice-edge/vice/data -pal +confirmonexit -intfrom int_test.bin -intfunc 1 -ramlink -ramlinkbios ramlink201.bin -ramlinkmode 1 -ramlinksize 8 -ramlinkimage ramlink_scratch.rl -ramlinkimagerw
-
m 48000 is completely stable, since I have an internal function ROM. That's how I found this problem in the first place. I developed an internal function ROM and found that it didn't work with the RAMLink because that shadowed the internal function ROM on my machine (but not in VICE). m88000 is a bit random since I currently don't have an external function ROM connected. If you intended me to test without an internal function ROM I don't understand what you are looking for. This is strictly an issue...
-
Ah, no that's a misunderstanding. I just numbered them 1 and 2 myself. RAMLink1 (in the C128) is a revision 2D RAMLink2 (in the C64) is a revision H
-
It goes to 227 on my C128 and then turns border red.
-
RAMLink1 (RL DOS 2.01): C128 stops green at 3030 C128 in C64 mode stops green at 177 RAMLink2 (RL DOS 2.00): C64 stops green at 177
-
I used 2.01 both on real HW and in VICE.
-
Sorry, I missed the config. 3.7.1 r44603M (GTK3 3.24.33, GLib 2.72.4, Cairo 1.16.0, Pango 1.50.6) Linux 5.15.0-88-generic 98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64
-
RAMLink kernal doesn't override internal function ROM
-
Ah, my bad. latest from github works. Please close this ticket.
-
How odd. I pulled latest from the master branch and I still get the compile error. That particular file doesn't seem to have been modified since 2013.
-
Compile error in Mint 19
-
Yes, as expected, the windows show up when the upper parts of the screens are aligning in the display settings.
-
I'm not at home to test until Friday, but I guess I won't need to test the alternate screen setup now when you have reproduced it.
-
Moving the management pane across restarts preserves the new position. The debugging window isn't behind the main window, but I think I see the problem now. I removed the config directory and retried. When activating the debug windows they end up on the left screen and I have Code::Blocks on the middle. The problem is that they may end up outside the visible area so I can't see or reach them. This is the setup: +-----+ [here] | | +-------+ | C:B | +-------+ | | | | | | | | | | | | +-------+ +-----+...
-
libwx_gtk2u_aui-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_aui-2.8.so.0 (0x00007f2a9b48a000) libwx_gtk2u_xrc-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_xrc-2.8.so.0 (0x00007f2a9b1db000) libwx_gtk2u_qa-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_qa-2.8.so.0 (0x00007f2a9afbc000) libwx_gtk2u_html-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-2.8.so.0 (0x00007f2a9ad07000) libwx_gtk2u_adv-2.8.so.0 => /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-2.8.so.0 (0x00007f2a9aa2a000) libwx_gtk2u_core-2.8.so.0...
-
I'm not sure how to know which wxGTK is used. >dpkg -l libwxgtk* | grep -e '^i' | grep -e 'libwxgtk-*[0-9]' ii libwxgtk2.8-0:amd64 2.8.12.1+dfsg2-ppa1~ubuntu16.04.1 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime) ii libwxgtk3.0-0v5:amd64 3.0.2+dfsg-1.3ubuntu0.1 amd64 wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime) I have the OS language set to Swedish. Code::Blocks doesn't turn up in Swedish though.
-
Left: HP display 1920x1200 Middle: Tilted ASUS display 1200x1920 Right: HP display 1920x1200 Video card: NVidia Geforce GTX 760 Drivers: xserver-xorg-video-nouveau 1:1.0.12-1build2 X11
-
I managed to get the callstack window visible by enabling it on a laptop and merging...
-
Sure, I have attached the config file. I have three monitors.
-
Yes, I have tried deleting and restoring the default perspective as well. I'm aware...
-
Debugging windows not visible
1