You should disable all interrupts to avoid QDOS writing on the second screen.. why would you need to use an interrupt routine? If you run your demo always on the same type of system (e.g. plain QL) you should be able to adjust timing in your code.
If you allow interrupts, even if you remove all other polled tasks from the chain, QDOS will still access the second screen area, for example it will increment the SV.POLLM variable. Daniele > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > d.com] On Behalf Of omega > Sent: Thursday, February 22, 2007 12:37 PM > To: [email protected] > Subject: [ql-users] Programming question > > Hello all, > > I want to present kind of "demo" for QL on the retro-computing > competition called Forever see: http://forever.zeroteam.sk > I did some graphics already on PC and it looks good (looks cool in fact > :-). But, I need to write special screen hadler with following conditions: > > 1) I need to use both screens of the QL without affecting of the 2nd > screen by system variables. > (if there must be some variables, how much is the minimum for > functionality interrupt handler?) > 2) I still need to call my routine every interrupt (50/60Hz) > 3) It must run on unexpanded QL with standard QDOS (sandyQboard > optional), no aurora, no Q40, Q60, no (S)GC. Plain, pure, virging QL only. > 4) Safe return to Qdos is not required. > > Anyone has any idea if it's possible? > > One more question, anyone tried to develop QL apps on PC? For example > have you tried Easy68k? Currently I'm using macroassembler AS (by Alfred > Arnold). > > Thanks, Jan > _______________________________________________ > QL-Users Mailing List > http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
