Forum unknown
· Amiga at Work
#excellence!
5 messages in this thread
It's not my copy – I work at a store and was helping a customer with it. I
will investigate and get back to you w/details.
I know it had to do with importing pictures – and possibly running out of RAM
in the process, but I can't give exact steps at this point.
Oh, it is possible to guru in cases like that…but its not (to my knowledge)
ProWrite that is guruing, its the system. ProWrite can handle memory down to
only a few bytes free, but if it gets below about 16K or so of CHIP memory
the system has problems (simple things like trying to drag a screen down will
hang the system). Thats why ProWrite starts to warn you when memory gets
very low (something like "Getting Low On Memory–Please Save Your Work").
ProWrite was designed to use any amount of memory your Amiga has, it
_doesn't_ allocate a fixed size buffer, but simply allocates and deallocates
memory as it needs it, and only as much as is need at any given time.
James Bayless
New Horizons Software, Inc.
OK sorry then it's probably not your fault. Darn. :-]
OK sorry then it's probably not your fault. Darn. :-]
Oh, it is possible to guru in cases like that…but its not (to my knowledge)
ProWrite that is guruing, its the system. ProWrite can handle memory down to
only a few bytes free, but if it gets below about 16K or so of CHIP memory
the system has problems (simple things like trying to drag a screen down will
hang the system). Thats why ProWrite starts to warn you when memory gets
very low (something like "Getting Low On Memory–Please Save Your Work").
ProWrite was designed to use any amount of memory your Amiga has, it
_doesn't_ allocate a fixed size buffer, but simply allocates and deallocates
memory as it needs it, and only as much as is need at any given time.
James Bayless
New Horizons Software, Inc.