No I dont believe -4 would start to wrap around... as gabriel said, its only a size of 40.. anything out of that allocated space should present an error right then and there in blitz. However, slotman you are slightly correct. It would appear that integrated video cards that use shared memory store their data in the relative space that blitz will start storing these banks. Atleast on xp pro with intel cards onboard. Blitz when it would "work" with these out of bounds data points would simply be poking memory that wasnt used by system processes or hardware. On integrated sets, im sure those programs reclaimed(especially the shared ram as vram for graphics) the allocated space... making handles in blitz now point to data that it itself can no longer make heads or tails out of. This was a two part problem, slight coding mistake, and blitz not reporting errors like it should.
(for the pros) Random errors, help, ideas?
Blitz3D Forums/Blitz3D Programming/(for the pros) Random errors, help, ideas?The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.