i can even confirm that i can get eo running on windows 98 if i want ... windows is not the problem
the problem is the virtual/dedicated ram
i can not say for sure , but my guess is that he is using 100% virtual ram
problem with virtual ram is that you can not create extra swap (also called hd ram or virtual ram) to offload the dedicated ram and that makes your game laggy
i can provide you a xp server if you like that works for 100% as can be confirmed by differend clients
then there are a few things you need to check
when does a player get dc ?? instand after sucessfully logged in ?? ( then it is definaly a ram problem as your server file crashed when trying to allocate a few mb of ram for the client)
does it happends when they try to connect ?? then it is a network problem and probaly a firewall problem ( depends on the vps system that get used is it your firewall or a root firewall .. )
does it happends on random times ?? then it is a ram problem , as it try to allocate ram but can not allocate the needed ram and provide a dc (out of sync error)
so it stays basicly the same , its the ram that provide the most problems , ram is what is causing the lagspikes and out of sync errors and dc problems
the speed itself is fine even with a 10mbit line for a XX amount of players ofcourse
so depending when the dc happends can we see what the problem is and what solution you need to use
Greetings From PowerChaos
*edit*
here is a bit of error codes from the QEMU that is used (its from 1.5 so even a newer version)
its just for information purpose as i can not say mutch about it as i never used this software
please note , i removed a part from the todo/hack list to show only the intresting parts
Quote:
|
Originally Posted by todo
Code:
General:
-------
- cpu_interrupt() win32/SMP fix
- warning for OS/2: must not use 128 MB memory (merge bochs cmos patch ?)
- config file (at least for windows/Mac OS X)
- basic VGA optimizations
- do not resize vga if invalid size.
- fix all remaining thread lock issues (must put TBs in a specific invalid
state, find a solution for tb_flush()).
linux-user specific:
-------------------
- remove threading support as it cannot work at this point
|
Quote:
|
Originally Posted by hacks
Code:
2.1. Scalars
If it's host memory-size related, size_t should be a good choice (use
ssize_t only if required). Guest RAM memory offsets must use ram_addr_t,
but only for RAM, it may not cover whole guest address space.
Use target_phys_addr_t for guest physical addresses except pcibus_t
for PCI addresses. In addition, ram_addr_t is a QEMU internal address
space that maps guest RAM physical addresses into an intermediate
address space that can map to host virtual address spaces. Generally
speaking, the size of guest memory can always fit into ram_addr_t but
it would not be correct to store an actual guest physical address in a
ram_addr_t.
3. Low level memory management
Memory allocated by qemu_vmalloc or qemu_memalign must be freed with
qemu_vfree, since breaking this will cause problems on Win32 and user
emulators.
|
Greetings From PowerChaos
and give it a try , also make sure u do the configs right although iam sure u did them right coz u have made too many servers but we all do mistakes so check it again
