In message <2ea12d4650.martin@xxxxxxxxxxxxxxxxxxx>, Martin Wuerthner <public@xxxxxxxxxxxxxxx> writes
The Filecore problem is quite drastic but is really a follow up error and outside the control of OP. It is probably caused by invalid parameters OP passes to RISC OS in response to the faulty document, which cause an abort inside FileCore. This should never happen, so
One thing I put a lot of effort into was making OP do a block save of memory when saving (or loading) documents - so it says "please save this chunk of memory as a file". I suppose my thought was that OP had written over RISC OS private memory.
It's a great pity that all memory outside applications own memory space isn't protected (and impossible to unprotect). I've said before how many bugs I found when porting OP to Windows just through the greater memory protection.
-- David Pilling email: david@xxxxxxxxxxxxxxxxxxx web: http://www.davidpilling.net post: David Pilling P.O. Box 22 Thornton Cleveleys Blackpool. FY5 1LR UK fax: +44(0)870-0520-941 To unsubscribe or subscribe goto: //www.freelists.org/list/davidpilling
