firstname.lastname@example.org wrote: > Just about this demo : > > Ninja (the coder of the demo) was ofcourse JOKING in that demo... ofcourse? > ofcourse the VIC doesn't overheat.. mostly becoz it is hardwired, > meaning that is fetches a byte *anyway* wether it has to or not. Eh? The VIC doesn't fetch very much character data in the border, if you ask me. Never heard of badlines in the border. > So displaying more gfx doesn't require more memory-fetches. Also it would be > nonsense to think that displaying 26 instead of 25 lines (just 4% more) could > possibly heat up the chip =) It's not those 4% extra fetches that might be the issue, it's the way the VIC is fooled into doing them. One thing *is* clear, and that's that this effect isn't very stable. Often, it just crashes, because the memory isn't refreshed as it should anymore. The VIC is totally confused, and it might very well generate an internal bus conflict because of that. The VIC's innards are a bit clouded, there's no way to tell. -- Martijn van Buul - Pino@dohd.org - http://www.stack.nl/~martijnb/ Geek code: G-- - Visit OuterSpace: mud.stack.nl 3333 Kees J. Bot: The sum of CPU power and user brain power is a constant. Message was sent through the cbm-hackers mailing list
Archive generated by hypermail 2.1.1.