tag:blogger.com,1999:blog-1927614691473343854.post4989218110134562948..comments2023-10-25T09:48:36.026+01:00Comments on Back to the QL: Simple MindsBack 2 the QLhttp://www.blogger.com/profile/00363758412258646531noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1927614691473343854.post-81990849131163831832012-02-02T05:26:10.198+00:002012-02-02T05:26:10.198+00:00If getting the same speed on all systems is import...If getting the same speed on all systems is important, a classic way of doing this on the QL is having your interrupt 2 handler to keep a timer (increment a counter), and your program periodically waits for the tick. This would work at least on HW systems (excluding maybe US QLs, they use a different interrupt 2 frequency) and on Q-emuLator, probably on other emulators as well if they provide accurate 50Hz interrupt timing. A related method is to use the STOP assembly instruction to wait for the next interrupt.PhotoSynthhttps://www.blogger.com/profile/02016069217009878973noreply@blogger.comtag:blogger.com,1999:blog-1927614691473343854.post-57378291461132551292011-11-05T20:12:56.333+00:002011-11-05T20:12:56.333+00:00"Does the Boot need to know its ROM?"
-..."Does the Boot need to know its ROM?"<br /><br />- only if the boot is going to need functionality not in a QDOS JM rom - and probably it will.<br />-if a JM rom is catered for it will need to know the drive it is loaded from or at least where to find boot2.<br /><br />"Will Boot need to know the screen size"<br />- not unless it is going to open a window bigger than 512x256. It is easy to find the screen size, mode etc by peeking the console driver for channel #0 through the system variables.Artificerhttps://www.blogger.com/profile/12473961441434051807noreply@blogger.com