|
Post by bjonte on Feb 4, 2017 21:25:09 GMT
That sounds interesting! Is the game C128 specific? Yes, it will be a C128 exclusive title. Thanks for the heads-up about VICE compatibility. I have a serial port server running on my C128 that I can use to load programs from my development machine so I will luckily not need to swap SD-cards to do testing. It is more problematic with compatibility on NTSC and 16 kB VDC since I don't own such machines. I have friends with 16 kB VDC so that's covered but I will probably need to buy an NTSC machine at some point.
|
|
|
Post by bjonte on Feb 3, 2017 22:35:10 GMT
Is there a trick to do a soft reboot without having the auto boot kick in? I want to exit with a reset but if the disk autoboots the program will start running again...
|
|
|
Post by bjonte on Feb 3, 2017 21:52:56 GMT
I'm working on a game and I may end up writing something unexpected at some point. It would be handy to be able to check the values in the emulator.
|
|
|
Post by bjonte on Feb 3, 2017 19:02:59 GMT
I did a routine that copied it to main RAM, but I suspect I will be needing something less cumbersome in the future. I managed to compile a version of VICE so maybe I can hack some support for it in the monitor.
|
|
|
Post by bjonte on Feb 3, 2017 17:57:05 GMT
I have the a DCR so most of it keeps the color, but the keyboard starts to get a bit yellowish. I'll hopefully replace the capacitors in a couple of weeks though. That'll feel good.
|
|
|
Post by bjonte on Feb 2, 2017 19:14:47 GMT
Is there a way to dump the internal VDC registers to the screen in VICE somehow? I can only find how to dump VDC RAM or the I/O registers.
|
|
|
Post by bjonte on Feb 2, 2017 19:07:14 GMT
It is very easy to accidently run code in the wrong RAM bank or access data in the wrong bank. How do you cope with that? Have you developed some kind of assertions or runtime checks to verify consistency at assemble- or runtime?
|
|