I used to tear my hair out at times with the same problem. I found, that if it was not running correctly or I was having problems editing a line, I would put as the first line in the entire program a REM statement.
I found that sometimes by adding a few random characters, or taking some away on that line seemed to move the code around in memory enough to enable it to spring back in to life again! Not 100% why, put the paging issue sounds highly likely. Andy Saturday, August 12, 2006, 11:14:06 AM, you wrote: Calvin> I was wondering if anyone could help me out with some Calvin> problems I`m having with the SAM. I`ve virtually quit three big Calvin> projects already because of memory corruption in Basic Calvin> and having just started on project four I`m finding I Calvin> don`t want to put too many months in if it`s gonna happen again :( Calvin> The problem rears it`s head once Basic code reaches a certain Calvin> size, usually I think about 55 - 65K, I know it must be a paging problem Calvin> but there must be something that can be done (?) Calvin> It appears that it`s much more likely to happen if there is any Calvin> graphics etc within the code, stored in string$... I know that Calvin> you can write bigger programs than this, and the manual and Calvin> ads back in the day proudly boasted of 400K + Calvin> programs, which would be amazing :) Calvin> anyhow, I`d appreciate it if any of you Machine Code guys could help Calvin> me out on this. Calvin> Cal Calvin> All New Yahoo! Mail Tired of [EMAIL PROTECTED]@! come-ons? Calvin> Let our SpamGuard protect you.
