Jonas Hultén

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