> > if you have more than 16k (I think) of label definitions, then BASIC crashes > > horribly. > > That reminds me. The Sam is very fussy about the programs it reads in from > tape. After a program has been loaded, if xos, xrg, yos and yrg are not in > memory or if the gap between numeric and string variables is less than 512 > bytes then the Sam crashes horribly. I don't know whether this counts as a > bug or not...
Never knew that. Mind you, I never use tape. Has anybody else ever noticed that sometimes when you change into MODE 3, I think, you still get 256 pixels across, as if xrg were 256, even tho you've not touched xrg since you switched on? That's another one, btw Simon. > > > There's also one in the INPUT routine, which I think everybody knows about - > > I didn't know about that one... :-) Well well well. Try it - fiddle about with INPUT #2, I think it goes wrong when the screen tries to scroll up - ie when you go off the bottom of the screen. > > The Sam also has a hardware bug, namely the "break" button. For about You're not kidding. The Messenger had a proper one - you had to plug this PCB into the Euroconnector (having taken your printer interface out, of course) and it had a new NMI button with debounce. > 50p they could have put in some debouncing circuitry, which I would have > thought was essential for an NMI trigger. Since they didn't, you have to > be extremely careful when you press it so as not to blow away the machine > stack, and you can abandon almost all hopes of resuming the program after > the interrupt (although, because of a huge stack-cleaning hack, the snapshot > software manages most times). It always used to work for me, but never does now. Not that I'm bothered. Nige
