| |
cadaver
Registered: Feb 2002
Posts: 1160 |
VICE $d011 24/25 row startup bug
When preparing a program that boots from EasyFlash and then does vertical scrolling I came across a curious bug that if the cart program booted by writing a value like $00 in $d011 on startup (ie. 25 row mode was never enabled), then the border would stay in 25 row mode even if it was supposed not to. By first enabling 25 rows then disabling it, it would go correctly into 24 row mode.
This is usually never an issue since Kernal initializes 25 row mode. I saw this in as late x64 versions as 3.1 (though x64sc 3.1 worked properly), and since C64Mini runs x64 2.4, the bug would also appear on it.
Anyone remember when this was fixed for good? Tried a search in the VICE bugtracker but no luck. |
|
| |
Count Zero
Registered: Jan 2003
Posts: 1966 |
Nearly makes me start an own thread on it :)
Please post any examples you have that render execution on C64mini/maxi buggy or crashy :)
We surely find ways to annoy the makers enough and urge them to more updates (defensive lie of a mini/maxi hater...)
BTT: svn log --search your_comment_fragment
If you have a checkout and know halfway what to look for maybe? Surely compyx or grp know better though. |
| |
Krill
Registered: Apr 2002
Posts: 3070 |
https://vice-emu.pokefinder.org/index.php/Hall_of_Shame doesn't mention C64mini/maxi, so they're fully GPL-compliant at least? =) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11499 |
The product is called "The 64 (mini)" :)
I only remember i worked a bit on the startup defaults at some point, and might have fixed one thing or another - dont remember what and when exactly. |
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
Thanks! Cloned the git mirror; the fix should be somewhere in 2017-2018 but didn't find it outright. Could have been a semi-related change fixing it like Groepaz says. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11499 |
did you confirm it was actually fixed in x64? |
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
Actually not :) Must have hallucinated that I tested on x64 3.2 and it was no longer there, because now when I tested, it was. And also still in 3.3. No surprise couldn't find the fix commit then.. |
