-
^_^
[Help] Joinserver Crash
Hello iam using s3ep2 files.
i have joinserver from 1.00.16 luciano files, allways when i open joinserver on links, it crashes, screen:

i tryed like some 10 differents joinservers, and allways the same error:

i have just fresh instaled win xp:
Microsoft Windows XP Professional Corporate SP2 Integrated April, validated.
frameworks 3.5
and other stuff, what can be the problem???? in windows???
help please.
-
-
Live your Life
Re: [HELP] Joinserver Crash
im with "1.00.16 luciano files" and i have no problems :S
i think is in you OS ..
-
^_^
Re: [HELP] Joinserver Crash
khm, on other server iam using almoust the same configuration without problems, so i gues need to reinstall windows again...
-
Hybrid
Re: [HELP] Joinserver Crash
buy a new computer and change your residence, loled advices,
if you are not using repacks of OS, then it's not OS problem, check cmd line arguments, change join server, check ini configs
-
^_^
Re: [HELP] Joinserver Crash
i had muserver on that same pc, just made reinstall with full format and other win wersion, so hardware might be ok, just smth is f%$#@ witth os, hope so...
anyway, will reinstall today again, and hope all be ok...
-
Valued Member
Re: [HELP] Joinserver Crash
i have the same problem, how did u solve it?
-
Novice
Re: [Help] Joinserver Crash
I have the same problem with dynamic volumen hard disk.
-
Re: [Help] Joinserver Crash
Whats your operative system bit?
-
Proficient Member
Re: [Help] Joinserver Crash
i hawe same problem about halw of years didint solve it ...........
-
Apprentice
Re: [Help] Joinserver Crash
I'm also with this problem and I managed to open the joinserver be that someone has managed to get a solution to this problem?
-
4ever Alone = my religion
Re: [Help] Joinserver Crash
The problem is with your ODBC!
Check all the paths and names in ODBC, so that they would fit the server files.
Or try other odbc.reg files.
Or configure ODBC on your own.
If any files are crashing then it's definitely the ODBC problem, since other problems would start it, but would show an error inside of the .exe you're running - except when the files are infected or files/system has been damaged.
But I'm 99% sure that it's ODBC problem!