I hope this is sorted in V³, since running out of ram should display
an error not bomb out the machine
erm, this is a system problem, not Voyager :)
If the system nukes, due to low chip-mem situations, there is nothing we can
do in Voyager to somehow 'override' this with an error message :)
Hello Jon
I'm using NC2, sometimes I get in the Genesis window error messages
saying
m_clalloc: max amount of memory already used (255120 bytes).
sana_read (UKonline): not enough mbuffs
Not chip memory ;) You have the right situation for it to happen,
usually when a packet arrives out
Hi!
I've just put V on its own screen in 256 colors and it works very
well, without any noticeable delay compared to the previous 32 colors
WB screen, but I've noticed one thing: the transfer anim doesn't show
up. Now it's not a vital thing: I'm not going to get mad and kill all
my neighbours
Chris Wiles..:
erm, this is a system problem, not Voyager :)
If the system nukes, due to low chip-mem situations, there is nothing we can
do in Voyager to somehow 'override' this with an error message :)
Sure, AmigaOS doen't like extremely low chipram situations. Once you
get down to 10
At some time around Tue, 29 Jun 1999 00:31:01 +0100
Ken Walsh had a brainwave about [netconnect] Re: Genesis error messages:
Hello Jon
Around Gensis / prefs / options / advanced Max. Memory
You could try doubling what's there 1024 works fine here.
right done that I'll see how
On 29 Jun 99 23:55:33 +0200, Terry Mahon wibbled...
I know nothing about the sender, a [EMAIL PROTECTED] Point is I
cannot access any of his/her inordinately long files. They end in
". pcx" Is this a PC kind of file.
PCX is a hideously bloated PC image format. You can get a datatype to
I received a message from Chris Wiles, a reply follows,
I hope this is sorted in V , since running out of ram should display
an error not bomb out the machine
erm, this is a system problem, not Voyager :)
Then why is it that only Voyager takes the system down with it? Other
programs I
