In article <lzvM6$I9yGHOFwc5@xxxxxxxxxxxxxxxxxxx>, David Pilling <flist@xxxxxxxxxxxxxxxxxxx> wrote: > 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? I have just done a small number of tests. So far, if DPlngScan$Memory is set to -1, there is no crash, but resetting DPlngScan$Memory to -2, the crashes come back. Chris... -- Chris Johnson To unsubscribe or subscribe goto: //www.freelists.org/list/davidpilling