But do they make sure that it works properly on ail Amigas? No. lt therefore seems an obvious thing for alI coders to stick to the rules. especially new coders. OWADAYS the problem lies not J. li in whether to obey the rules or not. but what the rules exactly are. If you take Commodore s words on the subject you might think that everything you do has to be done by using Übraries and devices, not touching anything low level like: he custom chips. Of course. Commodore does not mean this. What the boffins there point out is that as the Amiga is a multitasking machine, if you don't access it via the operating system the Amiga will not be able to cope with handling ail the différent tasks trying to take over the screen. trying to read the keyboard at the same time. trying to use any other aspect of the Amiga's input or output. ln this respect using the operating system is the only way to program the Amiga. But that is only if multitasking is necessary for your program. If you try to make a game muiti-task functions for people who do not need to muiti-task ForhidO and Permit (). Forbid turns off multi-tasking, so any other tasks running are suspended. giving your program 100 per cent of Revenge the rom