I'm just fixing the documentation in the MEGA65 user guide material now.
There is also 45 pages of "introduction to BASIC" which is coming along nicely now.
LG
Paul.
I'm just fixing the documentation in the MEGA65 user guide material now.
There is also 45 pages of "introduction to BASIC" which is coming along nicely now.
LG
Paul.
Yes, I quite agree that if we did it, it would be user-selectable.
I didn't realise that it was also a problem on the C64. I had figured that the IRQs would just be deferred, and get serviced after.
LG
Paul.
We could even periodically update it, but that is probably overkill.
But you are right that the C65's funny way of handling its internal drive causes a big problem for the TI/TI$ variables, as the CPU might be stopped for some time. That said, the DOS interface is so horribly innefficiently built, that apart from when seeking a new track or sector, the interruputs will be able to happen.
LG
Paul.
Yes, I believe so. We just need to implement a similar piece of magic for the MEGA65 to do this. I've got some ideas on this. It's just a matter of me having the time to attack it, along with everything else that needs to be done.
LG
Paul.
Yes, we currently have TI$ and the RTC. I am thinking about how I can automatically inject the current time into a running C65, ideally automatically. This just needs a Hypevisor scheduled interrupt "hyperrupt" that gives the hypervisor the chance to inject the value after the C65 ROM has started up and initialised TI/TI$. Then it would just transparently be there. You are welcome to file a github issue, so that I don't forget to do it.
LG
Paul
Hallo,
ich habe es gerade für dich gemacht, dass man einfach im MEGA65 Configure Utility, den RTC liesen und aktualisieren kann. Sowieso:
Bitte melde dich an, um diesen Anhang zu sehen.
Ist noch nicht perfekt, aber es geht.
LG
Paul.