Hi, I have asked Andrew Rawnsley. He says...
Just a comment that changing the value of DPlngScan$Memory to -1 instead of -2 in the run file seems to cure the problem. I certainly haven't been able to trigger it with that set, whereas with -2 it happens quite frequently.
I wonder if you previously tested on a non-xM Beagleboard (256Mb) where as the xM has 512Mb?
As I read it $Memory is -1 on RISC OS 5 or bigger i.e. Dynamic Areas and -2 on other machines i.e. wimp slot.
Question for Tank, what sort of Beagleboard, 256 or 512? -- David Pilling email: david@xxxxxxxxxxxxxxxxxxx web: http://www.davidpilling.net post: David Pilling, P.O. Box 22, Thornton-Cleveleys, Blackpool. FY5 1LR. UK To unsubscribe or subscribe goto: //www.freelists.org/list/davidpilling