Sys_Error: Z_Malloc: failed on allocation of 32832 bytes from the main zone
Shutdown tty console
this error displayed by et 2.55… i need help . i know that is a bug from 2.55 was fixed to 2.60. we play 2.55…
Sys_Error: Z_Malloc: failed on allocation of 32832 bytes from the main zone
Shutdown tty console
this error displayed by et 2.55… i need help . i know that is a bug from 2.55 was fixed to 2.60. we play 2.55…
Easy answer: upgrade.
You also might try increasing your com_hunkmegs and com_zonemegs failing that.
Hello mr software developer,
I’m having a problem with your software, I know you fixed it in version2 but I use version 1, so please could you fix it and release version 1.5
Hi mr user,
I’ve fixed the bug, find the fixed version labelled version2.
Hi mr software developer,
But I use version 1
Hi mr user,
but when I fix bugs I release a new fixed version in this case version 2 in the hope people will upgrade so they won’t experience the problem anymore
Hi mr software developer,
But I use version 1
…
oh great answer…i love it… we play 2.55 + Jaymod maybe that is a prob from Jaymod? hihihi…
we do not want play 2.60 ok…
my question is…it gives a other one solution without upgrade to 2.60
Yes, the other solution is to turn on your CAPS-LOCK key which will prevent malloc
failures and make 2.55 work perfect with software not developed for it. :disgust:
Yes, the other solution is to turn on your CAPS-LOCK key which will prevent malloc
failures and make 2.55 work perfect with software not developed for it. :disgust:[/quote]
I heard you have to press INSERT at the same time otherwise it just won’t work
Nope. It is a known bug in 2.55. AFAIK, it is the reason that 2.56 was released, which is a pretty clear indication that there is no workaround
we do not want play 2.60 ok…
my question is…it gives a other one solution without upgrade to 2.60
You could use 2.56, but I don’t see why you would want to.
Ugh, try to give some help (even though it was probably wrong), and then I get blamed on his problem. Fun.
how nice, but it still doesn’t change the fact that 2.55 is too buggy and insecure to be used as a server base, even 2.56 would be a better choice although I can’t understand why anyone would want to play or host a 2.55 server or 2.56 when 2.60 fixes so many bugs
I can’t understand why anyone would want to play or host a 2.55 server or 2.56 when 2.60 fixes so many bugs
Neither do I. I ask this question to many who do run these servers and I cannot get a solid answer.
etpub does afaik!
If we’re gonna plug, so does Jaymod, for that matter 
it’s the only real answer I’ve ever been able to get out of any of the 2.55 server admins I’ve queried