| Pages: [1] 2 3 4 5 6 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Valar CCP
   |
Posted - 2004.11.24 15:27:00 -
[1]
Number of users have been having problems with starting the Exodus client and from the reports we have been getting most of the time the issue is that people have downloaded the full build installer (519mb) instead of the patch 1754-2941 (103mb) and installed over their Castor install.
If you try to launch the EXODUS client and it crashes, hangs on the splash screen or nothing happens, this is most likely the issue.
The workaround for this is to delete your Eve folder, or use Add/Remove programs to uninstall Eve, and then reinstall from the full installer.
If that is not the issue, a second workaround to try is to set memoryMapping=0 or memoryMapping=2 in cache\prefs.ini.
Another possible workaround is to decrease audio hardware acceleration or disable sounds by putting "audio=0" in your prefs.ini. If that works, please leave feedback here with info about audio drivers and soundcard.
If the above workarounds doesn't work then I recommend that you send in a bugreport.
Directions about what is needed for a useful bugreport:
1. Logserver log
2. DXDiag file
3. Crashdump (if its generated)
4. Detailed description of what happened and what you did (Regarding this issue, how you installed/patched)
Using the logserver
(to prevent having problems with this, its recommended that you either restart your computer or check taskmanagers tasklist for dead instances of Eve)
1. Find your Eve folder in Windows Explorer
2. When you have the Eve folder open, find "logserver.exe" and launch it (Eve can't be running)
3. Select "File" -> "New Workspace"
4. Start Eve like you would normally do
5. When Eve crashes (or when you kill the process if it hangs) select "File" -> "Save workspace as..." and save the workspace in a place you'll find it again.
Saving a DXDiag
1. Select "Start" -> "Run..."
2. Type "dxdiag" and press Enter
3. Select the "Save all information..." button and save the file in a place you'll find it again.
Finding the crashdump
1. Locate a subfolder of you Eve folder called "Logs" (f.ex "C:\Program Files\CCP\EVE\Logs"
2. Find the file with the most recent time stamp.
The bugreport
1. Find the "Bug Reporting" button in the "Eve insider" menu on the left hand side
2. Give the bugreport a title that describes the problem. For example if you client is crashing on startup, then "Client crashes on startup" would be a good title. On the other hand "OMGBBQ I CANT PLAY" is not a good title.
3. Select the client build number. For example, the Exodus release client is "Shiva 2942".
You can find out your build name by looking into "boot.ini" file in you Eve folder, or the lower left corner of the login screen.
4. Description would be a short description of what the problem is.
Example: "When I double click my Eve icon it hangs on the splash screen."
5. Reproduction step are a very, very important part of the bugreport. Write exactly what you did to make the problem happen. This will help the programmers see where the problem is, and hopefully make it happen on their own computers. Reproduction steps are required for your report to be useful, even if you have attached logs to your report.
6. The computer field is for a short description of your computer hardware and driver versions. You do not have fill in this field if your problem is not hardware related, but its best to do it anyway.
7. For most reports to be useful we need atleast some of the files mentioned above. If you need to send in multiple files, please compress them and add the archive to the report.
8. Then its time to submit the report. If the file you are adding is very big, it might take a while for anything to happen after you press the button. Note that the file size limit for bugreports is ca. 2 MB.
------
Valar
Quality assurance department
CCP games |
Valar CCP
|
Posted - 2004.11.24 15:27:00 -
[2]
Number of users have been having problems with starting the Exodus client and from the reports we have been getting most of the time the issue is that people have downloaded the full build installer (519mb) instead of the patch 1754-2941 (103mb) and installed over their Castor install.
If you try to launch the EXODUS client and it crashes, hangs on the splash screen or nothing happens, this is most likely the issue.
The workaround for this is to delete your Eve folder, or use Add/Remove programs to uninstall Eve, and then reinstall from the full installer.
If that is not the issue, a second workaround to try is to set memoryMapping=0 or memoryMapping=2 in cache\prefs.ini.
Another possible workaround is to decrease audio hardware acceleration or disable sounds by putting "audio=0" in your prefs.ini. If that works, please leave feedback here with info about audio drivers and soundcard.
If the above workarounds doesn't work then I recommend that you send in a bugreport.
Directions about what is needed for a useful bugreport:
1. Logserver log
2. DXDiag file
3. Crashdump (if its generated)
4. Detailed description of what happened and what you did (Regarding this issue, how you installed/patched)
Using the logserver
(to prevent having problems with this, its recommended that you either restart your computer or check taskmanagers tasklist for dead instances of Eve)
1. Find your Eve folder in Windows Explorer
2. When you have the Eve folder open, find "logserver.exe" and launch it (Eve can't be running)
3. Select "File" -> "New Workspace"
4. Start Eve like you would normally do
5. When Eve crashes (or when you kill the process if it hangs) select "File" -> "Save workspace as..." and save the workspace in a place you'll find it again.
Saving a DXDiag
1. Select "Start" -> "Run..."
2. Type "dxdiag" and press Enter
3. Select the "Save all information..." button and save the file in a place you'll find it again.
Finding the crashdump
1. Locate a subfolder of you Eve folder called "Logs" (f.ex "C:\Program Files\CCP\EVE\Logs"
2. Find the file with the most recent time stamp.
The bugreport
1. Find the "Bug Reporting" button in the "Eve insider" menu on the left hand side
2. Give the bugreport a title that describes the problem. For example if you client is crashing on startup, then "Client crashes on startup" would be a good title. On the other hand "OMGBBQ I CANT PLAY" is not a good title.
3. Select the client build number. For example, the Exodus release client is "Shiva 2942".
You can find out your build name by looking into "boot.ini" file in you Eve folder, or the lower left corner of the login screen.
4. Description would be a short description of what the problem is.
Example: "When I double click my Eve icon it hangs on the splash screen."
5. Reproduction step are a very, very important part of the bugreport. Write exactly what you did to make the problem happen. This will help the programmers see where the problem is, and hopefully make it happen on their own computers. Reproduction steps are required for your report to be useful, even if you have attached logs to your report.
6. The computer field is for a short description of your computer hardware and driver versions. You do not have fill in this field if your problem is not hardware related, but its best to do it anyway.
7. For most reports to be useful we need atleast some of the files mentioned above. If you need to send in multiple files, please compress them and add the archive to the report.
8. Then its time to submit the report. If the file you are adding is very big, it might take a while for anything to happen after you press the button. Note that the file size limit for bugreports is ca. 2 MB.
------
Valar
Quality assurance department
CCP games |
porkbelly
|
Posted - 2004.11.24 16:06:00 -
[3]
Any workarounds you may come up with are also appreciated.
What it is! |
porkbelly
|
Posted - 2004.11.24 16:06:00 -
[4]
Any workarounds you may come up with are also appreciated.
What it is! |
Grimpak
|
Posted - 2004.11.24 16:16:00 -
[5]
if you are a ATI user with a 256mb card and using windowsXP, and your client freezes on the startup, there is a workarround.
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
-------------------
 Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
Grimpak
|
Posted - 2004.11.24 16:16:00 -
[6]
if you are a ATI user with a 256mb card and using windowsXP, and your client freezes on the startup, there is a workarround.
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
porkbelly
|
Posted - 2004.11.24 16:19:00 -
[7]
Originally by: Grimpak
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
Did you experience this yourself? What version of DX do you have?
What it is! |
porkbelly
|
Posted - 2004.11.24 16:19:00 -
[8]
Originally by: Grimpak
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
Did you experience this yourself? What version of DX do you have?
What it is! |
Hideki
|
Posted - 2004.11.24 16:25:00 -
[9]
I have/had the same problem as Grimpak. I also have a 256mb ati card on windows xp - running DX9c, and windows xp SP2.
-----------------------------------------------
I am Hideki, I have spoken and you will listen. |
Hideki
|
Posted - 2004.11.24 16:25:00 -
[10]
I have/had the same problem as Grimpak. I also have a 256mb ati card on windows xp - running DX9c, and windows xp SP2.
-----------------------------------------------
I am Hideki, I have spoken and you will listen. |
Grimpak
|
Posted - 2004.11.24 16:31:00 -
[11]
Edited by: Grimpak on 24/11/2004 22:12:15
Originally by: porkbelly
Originally by: Grimpak
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
Did you experience this yourself? What version of DX do you have?
it is a bug that has been pretty well documented here (can't get the smileys/buttons working in my firefox browser btw) : http://oldforums.eveonline.com/?a=topic&threadID=117332&page=1 .
had experienced this bug myself since day 1 of exodus testing and the client still has it.
Oh and the DX version is the most recent (9.0c I belive). Same goes to the drivers (using a ATI 9600 with the catalyst 4.11 ones)
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
Grimpak
|
Posted - 2004.11.24 16:31:00 -
[12]
Edited by: Grimpak on 24/11/2004 22:12:15
Originally by: porkbelly
Originally by: Grimpak
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
Did you experience this yourself? What version of DX do you have?
it is a bug that has been pretty well documented here (can't get the smileys/buttons working in my firefox browser btw) : http://oldforums.eveonline.com/?a=topic&threadID=117332&page=1 .
had experienced this bug myself since day 1 of exodus testing and the client still has it.
Oh and the DX version is the most recent (9.0c I belive). Same goes to the drivers (using a ATI 9600 with the catalyst 4.11 ones)
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
porkbelly
|
Posted - 2004.11.24 16:42:00 -
[13]
Originally by: Grimpak
it is a bug that has been pretty well documented here
Ok. It's the "out of memory" error, and it's fixed with the '95 compatibility mode. How extraordinary. Could you send me a log, with and without this mode set. I only need the log up to the login screen. At your convenience, to [email protected]. Thanks.
What it is! |
porkbelly
|
Posted - 2004.11.24 16:42:00 -
[14]
Originally by: Grimpak
it is a bug that has been pretty well documented here
Ok. It's the "out of memory" error, and it's fixed with the '95 compatibility mode. How extraordinary. Could you send me a log, with and without this mode set. I only need the log up to the login screen. At your convenience, to [email protected]. Thanks.
What it is! |
Grimpak
|
Posted - 2004.11.24 16:45:00 -
[15]
sent the log once, but ok. I'll make one again
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
Grimpak
|
Posted - 2004.11.24 16:45:00 -
[16]
sent the log once, but ok. I'll make one again
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
Therax
|
Posted - 2004.11.24 16:52:00 -
[17]
Originally by: Grimpak
if you are a ATI user with a 256mb card and using windowsXP, and your client freezes on the startup, there is a workarround.
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
You are my new God. I tried everything I could think of except that... Its strange how that seems to be the solution to lots of games that act up on XP :(.
|
Therax
|
Posted - 2004.11.24 16:52:00 -
[18]
Originally by: Grimpak
if you are a ATI user with a 256mb card and using windowsXP, and your client freezes on the startup, there is a workarround.
This is a bug that has not been solved yet, and to bypass it, just set the program to win95 or win98 compatibility mode.
You are my new God. I tried everything I could think of except that... Its strange how that seems to be the solution to lots of games that act up on XP :(.
|
Grimpak
|
Posted - 2004.11.24 16:56:00 -
[19]
Originally by: porkbelly
Originally by: Grimpak
it is a bug that has been pretty well documented here
Ok. It's the "out of memory" error, and it's fixed with the '95 compatibility mode. How extraordinary. Could you send me a log, with and without this mode set. I only need the log up to the login screen. At your convenience, to [email protected]. Thanks.
sent. details are on the mail
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
Grimpak
|
Posted - 2004.11.24 16:56:00 -
[20]
Originally by: porkbelly
Originally by: Grimpak
it is a bug that has been pretty well documented here
Ok. It's the "out of memory" error, and it's fixed with the '95 compatibility mode. How extraordinary. Could you send me a log, with and without this mode set. I only need the log up to the login screen. At your convenience, to [email protected]. Thanks.
sent. details are on the mail
-------------------
Quote:
Fragm's Oversized Ego Cannon barely scratches the forums, inflicting omgnoonecares damage
|
porkbelly
|
Posted - 2004.11.24 18:04:00 -
[21]
Originally by: Grimpak
sent. details are on the mail
Got it, thanks. We'll hit MS over the head with this one.
What it is! |
porkbelly
|
Posted - 2004.11.24 18:04:00 -
[22]
Originally by: Grimpak
sent. details are on the mail
Got it, thanks. We'll hit MS over the head with this one.
What it is! |
Deoglith
|
Posted - 2004.11.24 18:24:00 -
[23]
Edited by: Deoglith on 24/11/2004 18:34:58
Weird though as i have a 9800 xt with 256 mb im running xp with dx 9c, and sp2, latest ati drivers and its working fine, i wonder if its actualy a ati fast writes issue and when you switch to run in 9X start mode the problem is solved because and i might be wrong 95,98 dosent support fast writes anyway. |
Deoglith
|
Posted - 2004.11.24 18:24:00 -
[24]
Edited by: Deoglith on 24/11/2004 18:34:58
Weird though as i have a 9800 xt with 256 mb im running xp with dx 9c, and sp2, latest ati drivers and its working fine, i wonder if its actualy a ati fast writes issue and when you switch to run in 9X start mode the problem is solved because and i might be wrong 95,98 dosent support fast writes anyway. |
Hakera
|
Posted - 2004.11.24 19:24:00 -
[25]
http://exscape.org/exodusfix/
is a fix for a common issue amongst many posted by Jarjar
Dumbledore - Eve-I.com |
Hakera
|
Posted - 2004.11.24 19:24:00 -
[26]
http://exscape.org/exodusfix/
is a fix for a common issue amongst many posted by Jarjar
Dumbledore - Eve-I.com |
Balsak
|
Posted - 2004.11.24 19:46:00 -
[27]
Edited by: Balsak on 24/11/2004 20:24:38
Edited by: Balsak on 24/11/2004 20:05:56
Edited by: Balsak on 24/11/2004 20:02:07
I have this problem at the eula screen as well. Win98 compatability mode doesn't fix it. I did have this problem a little while ago when I did a reinstall of the game but the 98 compatability mode fixed it. The Exodus patch has brought this problem back but 98 mode doesn't fix :(
My system:
Win2k
AMD 1900XP
512 Megs ram
Nvidia 5600 356 meg video card
SB Live soundcard
Abit Motherboard
Direct X 9c
Any other possible fixes for this problem would be greatly appreciated.
Oh yeah. Video drivers tried are 53.03, 61.77 and 61.82.
|
Balsak
|
Posted - 2004.11.24 19:46:00 -
[28]
Edited by: Balsak on 24/11/2004 20:24:38
Edited by: Balsak on 24/11/2004 20:05:56
Edited by: Balsak on 24/11/2004 20:02:07
I have this problem at the eula screen as well. Win98 compatability mode doesn't fix it. I did have this problem a little while ago when I did a reinstall of the game but the 98 compatability mode fixed it. The Exodus patch has brought this problem back but 98 mode doesn't fix :(
My system:
Win2k
AMD 1900XP
512 Megs ram
Nvidia 5600 356 meg video card
SB Live soundcard
Abit Motherboard
Direct X 9c
Any other possible fixes for this problem would be greatly appreciated.
Oh yeah. Video drivers tried are 53.03, 61.77 and 61.82.
|
porkbelly
|
Posted - 2004.11.24 21:54:00 -
[29]
Edited by: porkbelly on 24/11/2004 21:56:49
Gentle readers:
Would those of you having this problem please do the following experiment (we have not been able to reproduce this problem in-house) :
in prefs.ini (in the cache folder) set
memoryMapping=0 or
memoryMapping=2
(1 is the default.).
Please let me know if that changes anything.
What it is! |
porkbelly
|
Posted - 2004.11.24 21:54:00 -
[30]
Edited by: porkbelly on 24/11/2004 21:56:49
Gentle readers:
Would those of you having this problem please do the following experiment (we have not been able to reproduce this problem in-house) :
in prefs.ini (in the cache folder) set
memoryMapping=0 or
memoryMapping=2
(1 is the default.).
Please let me know if that changes anything.
What it is! |
| |
|
| Pages: [1] 2 3 4 5 6 :: one page |
| First page | Previous page | Next page | Last page |