[help]VMWare Crash when quit cabal client

[dezon]

Hi guys!

Ok, reading there, don't found an solution, just some comments but nothing that can help me... So I'm posting a new thread here!:winky:

1 - A bug is, I'm playing like 3 or 4 minutes, then I get disconnected.

1 - If i quit the game without stop the cabal service in the CentOS, the VMware crashs and close the CentOS and return to first page of VMware, that show to make a new Vistual Machine etc...

Thanks anyway:construct

[MentaL]

[cypher]

I should have watched my mouth and not said/talked shit to DeadlyData telling him things like your are not welcome here because then I become the one who is truly not welcome here.

[Yamachi]

First things first, please don't use the [Release] tag for a help thread. Now, moving onto your questions:

1 - http://forum.ragezone.com/showthread.php?t=442195 <-- Easily answered by using search. Please remember. The reason you DC when buying pots is that the information stored server-side is for the CN client, which is different from the info stored client-side in your NA client. Specifically, it's a confliction between the price the client thinks pots should be, and the price the server thinks they should be. Just edit the server prices to match the client prices. You can find a dump of the ENC files (which you'll need if you want to sync your server with your client) in the Release section. The server-side item information is stored in /Data/Data_World/worldXX-npc.scp

As for questions 2 and 3, you have not given us enough information to help. Some logs would be nice.

[dezon]

:: Sorry for posted with "RELEASE" ::
This is the bug that I receive when I quit the game without stop the service of cabal in CentOS Terminal:

Thanks:juggle:

anyone please?

[cypher]

I should have watched my mouth and not said/talked shit to DeadlyData telling him things like your are not welcome here because then I become the one who is truly not welcome here.

[dezon]

do not double post, vmware crashed report it to the coresponding website.

Haha... who double posted?
I just edited the post and do not made a double post!
thanks to all you that helped me
thanks to all that dont helped me too
:vegeta:

[cypher]

I should have watched my mouth and not said/talked shit to DeadlyData telling him things like your are not welcome here because then I become the one who is truly not welcome here.

[chumpywumpy]

Nobody is going to figure it out from that error as it is just a general crash report unfortunately. I saw your other post with the vmware logs in it and the only thing i could find that was even close was to do with 64-bit SQL servers and VMWare Fusion. Even the .dmp file would be all but useless to 99% of people (who aren't vmware developers).

Nobody else is reporting such crashes so i think i would just chalk it up to something in your machine that vmware doesn't like. You can try things like updating drivers but to be honest i would suggest a complete reinstall of windows as that will probably cure it and it will be faster that weeks of tinkering.

[[hidden]]

i noticed that it happens when you exit while playing on the same pc as vmware.

you seem to disrupt its internal communication process, such that it crashes as a result.

things to consider.

do you have enough memory, cpu and net to play in the same pc where your hosting your server?

if no, then you better avoid playing at the same system, or you will cause a server rollback whenever that crash happens, and your players wont like it very much ^^