| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
C64 Emulator Bugs
after stumbling about a bunch of VICE bugs myself in the last couple of days i have decided to compile a list with issues current emulators have. the goals for this are
- make people aware that emulators are by far not perfect (yet?)
- make it easier for emulator authors to improve the emulators, by showing problematic programs and possibly provide simple testcases
- allow c64 coders to implement emulator detection if desired
so well, check this: http://hitmen.c02.at/files/docs/c64/c64_emulator_bugs.txt
help welcomed :)
|
|
... 240 posts hidden. Click here to view all posts....
|
| |
assiduous
Account closed
Registered: Jun 2007
Posts: 343 |
A new entry:
[CCS64] Intoxication Intoxication
A: Fails on the title screen in CCS64. Works on the real C64, in Hoxs64 and VICE.
And some updates to a few:
- [vice] Dylan Dog/X-factor Dylan Dog +3
"This one crash after the intro in Vice, but no in CCS."
A: It crashes on my C64C, just like in Hoxs64 and VICE. This suggests an inaccuracy exists in CCS64 because it SHOULDN'T work.
- [vice] Enforcer+4M-Enigma Enforcer +4
"Found another one that doesnt work. When you press fire at the intro and it loads level 1 then it crash. It doesnt even scan in CCS, but works perfect on the real C64."
loading endsequence works
A: It works on the real thing, in Hoxs64, and contrary to the statement above, CCS64. Crashes on loading the first level in VICE.
- [vice] FlyingSharkPreview+-Ikari&FAC Flying Shark Preview +
"Another one here... When running it in Vice it goes into grey screen and gives cpu jam. If I run it on the real c64 and on ccs it works fine."
A: It crashes on my C64C, just like in Hoxs64 and VICE. This suggests an inaccuracy exists in CCS64 because it SHOULDN'T work.
- [vice] Invest-TRC&Blasters Invest
For the list of bugreports for emulators. Invest works perfect on the real c64 without any problems.
A: Doesn't work on the real thing nor in any emulator. I suspect a disk error, as the drive head rattles before the program exits to BASIC. |
| |
Mason
Registered: Dec 2001
Posts: 461 |
Since Im the one who did those bugs:
Invest worked fine on my real C64
Flying Sharks Previw worked fine on my real C64
Dylan Dog works fine my real C64.
|
| |
assiduous
Account closed
Registered: Jun 2007
Posts: 343 |
Did you test with any cartridge? What kind of C64 was it (C64, C64-II, C64C?) and which Kernal was it equipped with? Any expansions used?
The tests I've performed were carried out on a bare C64C (Kernal rev3) and a 1541-II disk drive. In case of a failure, I've always rechecked the title at least once to ensure that the behaviour doesn't vary. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
noticed another problem, check out Info Everybody. its using a "jam" opcode to halt execution. a real c64 would just freeze and show the screen, vice gives a "cpu jam" message, and does not show the proper screen ever. :(
as for the releases which worked on masons but not on assiduous' real c64.... maybe a 1541 (old) vs 1541-II (new) issue? |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
oh how I hate vice's nagging jam and halt messages, simply leave it alone, and let the user alone. so fuckin restricting when you have no reset option after a halt or jam... |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Quote:so fuckin restricting when you have no reset option after a halt or jam...
infact that option is right there in the jam message =D |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: oh how I hate vice's nagging jam and halt messages, simply leave it alone, and let the user alone. so fuckin restricting when you have no reset option after a halt or jam...
Do you know how often I use that JAM for debugging purposes. When you have some more complex conditional code and want to make sure you've reached a particular point in the code I simply put a .byte 2 there in the code. If it JAMs then I reached that code. I also use it for timing, like after a stable IRQ I put a .byte 2, when VICE JAMs I check at which cycle the VIC is on (right there in the monitor). Since I know at which cycle I wanna stop on I simply apply the appropriate delay, instead of fiddeling with inc$d020/dec$d020 to find the correct cycle... |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
using breakpoints would be too easy i guess =D |
| |
Mason
Registered: Dec 2001
Posts: 461 |
Quote: Did you test with any cartridge? What kind of C64 was it (C64, C64-II, C64C?) and which Kernal was it equipped with? Any expansions used?
The tests I've performed were carried out on a bare C64C (Kernal rev3) and a 1541-II disk drive. In case of a failure, I've always rechecked the title at least once to ensure that the behaviour doesn't vary.
I got the old UK model. Also got one of the old 1541 drives.
No expansion used |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: using breakpoints would be too easy i guess =D
Takes longer time because then I must first enter monitor-mode manually, then add the break point on an address I don't know. Hence, simply adding a .byte 2 and do "make run" is MUCH simpler. ;D
I do use break points of course as well but not for the purposes I wrote in the previous post. |
| Previous - 1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | ... | 25 - Next |
