Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 30 .. 33 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 77 post(s) |
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 20:11:00 -
[571] - Quote
Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part.
Two things that had to be done in order to FIX the problems.
ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe.
The other thing that had to be done was in my router I had to turn off SPI filtering.
Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher.
These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly.
One this was done I could run the repair client and the launcher worked.
Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
|
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 20:13:00 -
[572] - Quote
Castle cheesecake wrote:okay so i downloaded the whole clientt, installed it, still same problem.
repair.exe didnt work either
this is going on day 2 ccp, come on, need some help here
If you downloaded a completely new client you should be able to go directly into the bin directory and execute "ExeFile.exe" directly to launch the client provided that they have deployed the complete new client update in the latest build. |
Shaden Nightwalker
Tryblium Sanguinis
0
|
Posted - 2012.03.14 20:14:00 -
[573] - Quote
"Neutron Blaster turret color will adapt to the racial style of the ship they're fitted to."
Does not work with Tech 2 Neutron Blasters mounted un Tech 3 Ships . |
Castle cheesecake
State War Academy Caldari State
10
|
Posted - 2012.03.14 20:17:00 -
[574] - Quote
Alunis wrote:Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part.
Two things that had to be done in order to FIX the problems.
ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe.
The other thing that had to be done was in my router I had to turn off SPI filtering.
Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher.
These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly.
One this was done I could run the repair client and the launcher worked.
Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
how do you figure if that solution would work for others? im no computer genius, or even knowledgeable in any way.
i heard about this turning off your antivirus, but i dont have "ESET Security 5" so i dont think thats the case for me. |
Lucas Quaan
Sniggerdly Pandemic Legion
14
|
Posted - 2012.03.14 20:20:00 -
[575] - Quote
CCP Donut Golem wrote:Acthiliak wrote:So why do I suddenly have to launch a launcher that adds zero features or functionality to my previous Eve experience, but goes a step further from being absolutely useless and actually becomes an annoyance because now I have to click extra buttons arbitrarily and the launcher doesn't close itself when I click Play, so yet another arbitrary click has to be made.
What was the point of this launcher? Please check the Settings menu for an option to hide the Launcher if there is no update available. Yeah, only that setting doesn't actually do anything.
The wording on that tab could use some work too. Saying "The EVE Launcher can be configured to only appear if an update is available, and to not automatically close when the EVE client is started" (emph mine) and then have a check-box to do the exact opposite, i.e. force it to close, is ass-backwards. It's a nice check-box, though. |
Kashti Nada
Center for Advanced Studies Gallente Federation
0
|
Posted - 2012.03.14 20:20:00 -
[576] - Quote
Roughly eleven times out of twelve patching EVE has proven to be a total clusterfuck. It's like they have monkeys for devs punching at the keyboard and when they manage to get something to compile through some incredible fluke they release it with no quality assurance whatsoever. So I wasn't surprised to find out patching the client failed...
What I want to know is whether it is safe to reboot my machine this time or has it been rendered unbootable. |
Lovelocke
Enlightened Industries Test Alliance Please Ignore
74
|
Posted - 2012.03.14 20:20:00 -
[577] - Quote
Alunis wrote:Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part.
Two things that had to be done in order to FIX the problems.
ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe.
The other thing that had to be done was in my router I had to turn off SPI filtering.
Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher.
These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly.
One this was done I could run the repair client and the launcher worked.
Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
Just done this and the patch loop has stopped and launcher seems to be working! I'll post in a moment if it works. |
Augustus Ogana
EntroPraetorian Academy EntroPraetorian Aegis
1
|
Posted - 2012.03.14 20:24:00 -
[578] - Quote
Alunis wrote:Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part.
Two things that had to be done in order to FIX the problems.
ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe.
The other thing that had to be done was in my router I had to turn off SPI filtering.
Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher.
These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly.
One this was done I could run the repair client and the launcher worked.
Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
PLAYERS: THIS WORKS.
CCP: PAY LOVESLOCK 1B ISK PLUS 3 FREE MONTHS
He/she just saved your incompetent apathetic butts. |
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 20:26:00 -
[579] - Quote
Castle cheesecake wrote:Alunis wrote:Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part.
Two things that had to be done in order to FIX the problems.
ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe.
The other thing that had to be done was in my router I had to turn off SPI filtering.
Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher.
These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly.
One this was done I could run the repair client and the launcher worked.
Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
how do you figure if that solution would work for others? im no computer genius, or even knowledgeable in any way. i heard about this turning off your antivirus, but i dont have "ESET Security 5" so i dont think thats the case for me.
I'm stating that this is what I had to do in order to fix the problem on my end.
I don't know that it will work for everyone however the two things I turned off or made exceptions for both watch the transport of streams inbound and it cured the errors because the firewall and the router firewall were no longer touching the traffic inbound from CCP.
If you have a firewall on your system / AV product then it could very well be doing protocol filtering and you should turn it off and test to see if that fixes the issue you're having. As far as your router goes, if you don't know how to access it then you might need to contact the vendor or check their website and get direction on looking up if the router does have SPI filtering and if it is on by default and how to turn it off.
That's the only way you can test my solution to see if it works for you.
I was getting the same errors that everyone else was getting. So my guess is that because of how the new launcher streams the client updates that any type of filters correcting traffic can and will cause issues.
|
Lovelocke
Enlightened Industries Test Alliance Please Ignore
74
|
Posted - 2012.03.14 20:29:00 -
[580] - Quote
ALUNIS'S SUGGESTION WORKS!
The ESET suggestion! Follow this, launcher ran and it updated! It works!!!!!!!!!!!!!!!!!!!!!!!!! |
|
Jaden Plymoth
Iacio Iaculum
0
|
Posted - 2012.03.14 20:30:00 -
[581] - Quote
Lovelocke wrote:Alunis wrote:Ok this is terrible to have to go through this many hoops in order to have fixed a problem that isn't a problem on my end but a poor lack of sight on CCP's part.
Two things that had to be done in order to FIX the problems.
ESET Security 5 had to be told to give exceptions under protocol filtering for ExeFile.exe, launcher.exe, and repair.exe.
The other thing that had to be done was in my router I had to turn off SPI filtering.
Stateful packet inspection has caused issues with rsync in the past under UNIX applications and it also seems that it can and will create issues for Eve's new launcher.
These are not things I enjoy having to turn off because I do like to keep a properly secured system but these are the current exceptions that I had to make for Eve in order to get it working properly.
One this was done I could run the repair client and the launcher worked.
Again, I point out that these issues many of us posted on back in January on Sisi and we told CCP that the launcher in it's current state was not ready to be deployed. Until I can remove these exceptions for Eve and turn SPI back on I consider the client broken and a security risk due to poor coding and QA control.
Just done this and the patch loop has stopped and launcher seems to be working! I'll post in a moment if it works.
Well, if this is truely the thing causing the patch loop, then I'm royally screwed as I dont have the authorization to change router settings where I'm at.
|
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 20:33:00 -
[582] - Quote
Lovelocke wrote:ALUNIS'S SUGGESTION WORKS!
The ESET suggestion! Follow this, launcher ran and it updated! It works!!!!!!!!!!!!!!!!!!!!!!!!!
Any firewall / AV Software that does protocol filtering as part of it's package (all the major AV and Security packages do), is looking for the same sort of errors that SPI filtering also watches for at the router level.
So if you have a AV / Security package and/or a router that uses SPI filtering you need to turn these off for the moment.
THIS IS ONLY A WORKAROUND.
CCP should not be using a protocol that does NOT error check such as rsync. This is why everyone is having problems. |
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 20:38:00 -
[583] - Quote
Jaden Plymoth wrote:Well, if this is truely the thing causing the patch loop, then I'm royally screwed as I dont have the authorization to change router settings where I'm at.
Which is why the delivery system that CCP has picked to make their new launcher work is wrong in the first place.
A great many people will not have access to the router or know how to make these changes.
It's one thing to be able to turn off the firewall / security software but quiet another to dig into a router or get someone to change the router setup to fix this sort of problem. |
Lovelocke
Enlightened Industries Test Alliance Please Ignore
74
|
Posted - 2012.03.14 20:38:00 -
[584] - Quote
I didn't do anything to my router, only added the protocol exception to ESET NOD32. Make sure it's not an exclusion but the actual protocol filtering as said. |
Jacek Alabel
Cut Throats And Wise Guys Black Thorne Alliance
1
|
Posted - 2012.03.14 20:48:00 -
[585] - Quote
Tribal Solidarity wrote:Fix for EVE on Linux if it's not been properly documented here. Install latest version of Wine, on Debian get it from testing, Ubuntu use the PPA here - https://launchpad.net/~ubuntu-wine/+archive/ppaNow you'll need to get rid of your $HOME/.wine directory to make sure you have a totally clean install, use rm -rf for this but be warned it will wipe out all of your Wine-installed programs. Run wine-cfg to force Wine to create your .wine directory and configure itself. Install latest winetricks then run the following 2 commands winetricks vcrun2008 winetricks vcrun2010 That should be it, everything should work now.
I am afraid for me it made no difference. Which version of wine are you running? I have wine-1.4-rc6. I cleaned everything, used winetricks to install corefonts and 2 vcrun packages and then did full clean EVE install but I am still getting "abnormal program termination error" |
Lovelocke
Enlightened Industries Test Alliance Please Ignore
74
|
Posted - 2012.03.14 20:49:00 -
[586] - Quote
Also just an FYI, if you load eve via the ExeFile.exe in the bin folder, and you're in Windows 7, pin this to your taskbar and then you can load up multiple clients by just right clicking it and loading up another, means you bypass that launcher.exe. |
Rightism
Ministry of War Amarr Empire
0
|
Posted - 2012.03.14 20:59:00 -
[587] - Quote
Hello
I have an ingame problem with my mission :
I accepted it from an agent. I jump to it. When I am in the system where I have to do the job, I cannot jump to the location : when I click on the link in the mission description, there's no more "jump to" sub menu. So I cannot do the mission.
What can I do ?
The mission is : My sweet privateer Agent : Aneng Tzashrah System site of the mission : Deepari
Thank you.
Rightism |
Arag Odalin
Center for Advanced Studies Gallente Federation
0
|
Posted - 2012.03.14 21:03:00 -
[588] - Quote
Has someone run that "eve-premium_007867_350962..." thing and will it work properly (I personally like to know additionally if it will work on a MAC) ? I'm just d/l it and will aport if it will not work as it takes 4+ hours to d/l with my connection.
Thanks a lot.
|
Augustus Ogana
EntroPraetorian Academy EntroPraetorian Aegis
1
|
Posted - 2012.03.14 21:05:00 -
[589] - Quote
Problem: 1.9 launcher gets to 15% patch built, then starts again, over and over. Possible CAUSE: Antispyware / antimalware / antivirus software is not allowing updates. SOLUTION: For ESET 5:
- Go to Advanced Settings, Web and email, Protocol Filtering, Excluded Applications.
- If you've been trying like mad to fix it before now, then launcher.exe, eve.exe, and exefile.exe may already be in this list. Just check the boxes and hit OK.
- If those 3 exes aren't in the list: Click Add button and add each, one at a time. For launcher it needs launcher.exe in the (eve)\launcher folder, not the shortcut or anything you may have downloaded from a forum link and moved to your eve folder. Ah, good times.
- Presuming you're at 1.9 you can now run the launcher and patch. If your launcher gets updated at this point, you may have to repeat the above steps before getting the launcher to say Play.
Problem: Walked away like a rational person after seeing smoke on the 1.5 horizon. Your probable situation is a mix of these problem/solutions: - all client settings may be gone (you need to find your pre-1.5 %appdata% bla bla eve_folder_tranquility folder; copy everything from its settings subfolder into your newer blabla_tranquility\derp\settings folder.) - launcher.exe, launcher shortcut, and repair are all acting stupid, throwing logs about missing extensions, broken shortcut, and/or pretending CCP is dumb enough to compile without 64 bit support. (you should run (eve)\bin\exefile.exe and hope for the best, it should work now, though you might have to come back for the other problem/solution above) - stuff I didn't run into (sorry, good luck) |
Stephen Ambrye
Life. Universe. Everything. Clockwork Pineapple
0
|
Posted - 2012.03.14 21:15:00 -
[590] - Quote
Augustus Ogana wrote:So to recap two solutions to 1.5 launchers being totally broken on Windows, maybe/not specific to Win7-64: Problem: 1.9 launcher gets to 15% patch built, then starts again, over and over. Possible CAUSE: Antispyware / firewall / antimalware / antivirus software is not allowing updates. SOLUTION: For ESET 5:
- Go to Advanced Settings, Web and email, Protocol Filtering, Excluded Applications.
- If you've been trying like mad to fix it before now, then launcher.exe, eve.exe, and exefile.exe may already be in this list. Just check the boxes and hit OK.
- If those 3 exes aren't in the list: Click Add button and add each, one at a time. For launcher it needs launcher.exe in the (eve)\launcher folder, not the shortcut or anything you may have downloaded from a forum link and moved to your eve folder. Ah, good times.
- Presuming you're at 1.9 you can now run the launcher and patch. If your launcher gets updated at this point, you may have to repeat the above steps before getting the launcher to say Play.
If you don't have ESET 5, you may have a similar option in your security software, boiling down to "let this app act like there aren't ***** living on my disk. Give it security douche immunity. This vampire is invited." Or you can take the bad, dumb, and easy risk of temporarily disabling security to just get it over with. Next one: Problem: Walked away like a rational person after seeing smoke on the 1.5 horizon. Your probable situation is a mix of these problem/solutions: - all client settings may be gone (you need to find your pre-1.5 %appdata% bla bla eve_folder_tranquility folder; copy everything from its settings subfolder into your newer blabla_tranquility\derp\settings folder.) - launcher.exe, launcher shortcut, and repair are all acting stupid, throwing logs about missing extensions, broken shortcut, and/or pretending CCP is dumb enough to compile without 64 bit support. (you should run (eve)\bin\exefile.exe and hope for the best, it should work now, though you might have to come back for the other problem/solution above) - stuff I didn't run into (sorry, good luck)
i did all of this, and while the launcher went up to about 45% this time, it still encountered an error.
|
|
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 21:16:00 -
[591] - Quote
Augustus Ogana wrote:So to recap two solutions to 1.5 launchers being totally broken on Windows, maybe/not specific to Win7-64: Problem: 1.9 launcher gets to 15% patch built, then starts again, over and over. Likely cause: Antispyware / firewall / antimalware / antivirus software is not allowing updates. Solution: For ESET 5:
- Go to Advanced Settings, Web and email, Protocol Filtering, Excluded Applications.
- If you've been trying like mad to fix it before now, then launcher.exe, eve.exe, and exefile.exe may already be in this list. Just check the boxes and hit OK.
- If not (those 3 above aren't in the list): Click Add button and add each, one at a time. For launcher it needs launcher.exe in the (eve)\launcher folder, not the shortcut or anything you may have downloaded from a forum link and moved to your eve folder. Ah, good times.
- Presuming you're at 1.9 you should fly smoothly now. If your launcher gets updated at this point, you may have to repeat the above steps before getting the launcher to say Play.
If you don't have ESET 5, you may have a similar option in your security software, boiling down to "let this app act like there aren't ***** living on my disk. Give it security douche immunity. This vampire is invited." Or you can take the bad, dumb, and easy risk of temporarily disabling security to just get it over with. If you have a separate firewall with the SPI filtering feature, it may also interfere. Thanks to Alunis for finding all this out.Next one: Problem: Walked away like a rational person when 1.5 did a pratfall. Your probable situation is a mix of these problem/solutions: - all client settings may be gone (you need to find your pre-1.5 %appdata% bla bla eve_folder_tranquility folder; copy everything from its settings subfolder into your newer blabla_tranquility\derp\settings folder.) - launcher.exe, launcher shortcut, and repair are all acting stupid, throwing logs about missing extensions, broken shortcut, and/or pretending CCP is dumb enough to compile without 64 bit support. (you should run (eve)\bin\exefile.exe and hope for the best, it should work now, though you might have to come back for the other problem/solution above) - stuff I didn't run into (sorry, good luck)
I think you forgot to mention a very large hammer or explosive device to be involved in this solution.. |
Alunis
Focused Annihilation Detrimental Imperative
5
|
Posted - 2012.03.14 21:18:00 -
[592] - Quote
Stephen Ambrye wrote: i did all of this, and while the launcher went up to about 45% this time, it still encountered an error.
Do you have a router and if so have you checked to see if it has SPI filtering turned on?
If so, turn it off. SPI filtering does the same thing as ESET and other firewalls that protocol filter. |
Augustus Ogana
EntroPraetorian Academy EntroPraetorian Aegis
1
|
Posted - 2012.03.14 21:19:00 -
[593] - Quote
Alunis wrote:I think you forgot to mention a very large hammer or explosive device to be involved in this solution..
The forum is my hammer, and my explosive device. It's implied. ;) |
Augustus Ogana
EntroPraetorian Academy EntroPraetorian Aegis
1
|
Posted - 2012.03.14 21:34:00 -
[594] - Quote
My earlier post on Windows launcher problems and solutions, is updated with proper credit and more snark.
@Stephen Ambrye et al, If you can't find the right security setting or aren't sure how to change your router/firewall settings, another thing to try is:
- Connect your computer directly to your modem (meaning, get the router out of the mix)
- Do updates until you can play
- Reconnect your router
File this under "dumb, bad and easy" but if router security features are the problem, this will get you playing quickly. |
Jaden Plymoth
Iacio Iaculum
0
|
Posted - 2012.03.14 22:03:00 -
[595] - Quote
Ok, I just spent the last 2 freakin hours downloading the new offline installer for the UP TO DATE version of the client. Guess what, there was an error while installing and it ran repair.exe. And now I"m right back to square frickin 1. The client is still running yesterday's version, the launcher was showing v1.05. Upon launching the client (from the .exe in the bin folder), it prompts to download a 20mb file, which in turn updates the launcher to v1.09. I open the damned launcher, hoping to God its going to fething update, but guess what. It tells me the client is ready to go without even checking for an update file, while the client continues trying to update the launcher to v1.09. I'm back in my God damned updating loop ON A FRESH INSTALL. I have now spent the last 8 hours trying to get this damned client to update in the hopes that I can play.
I have disabled all security on my local machine, and I have no way of accessing my network's router or going direct to a modem as I'm on a militarily secured network, so therefore I have no way of confirming if that is my problem.
Quote:02:26:31: Debug: src/helpers.cpp(140): 'CreateActCtx' failed with error 0x000000 7b (the filename, directory name, or volume label syntax is incorrect.). INFO - IsLowerFolderPrivsRun: False INFO - IsLowerFolderPrivsRun: False INFO - logging started INFO - server address: 'Tranquility' INFO - Getting Info from http://client.eveonline.com/patches/win_launcherinfoTQ_inc.txt INFO - Initialized launcher info for server: 'TQ' INFO - Cache dir: u'C:\\Program Files (x86)\\CCP\\EVE\\launcher\\cache' WARNING - Localization returned language of choice as 'en-us' WARNING - Settings returned language of choice as 'en' WARNING - Settings is not using defaults from the info files INFO - Initializing app with language: 'en' INFO - Log sending is enabled INFO - Running from u'C:\\Program Files (x86)\\CCP\\EVE' INFO - Working directory u'C:\\Program Files (x86)\\CCP\\EVE\\launcher' INFO - Remote version: 1.05 INFO - Local version: 1.09 INFO - Data URL: http://cdn1.eveonline.com/EveOnlineLauncher/launcherupdate_1_05.dat INFO - Updater URL: http://cdn1.eveonline.com/EveOnlineLauncher/updater8.exeINFO - cache dir: C:\Program Files (x86)\CCP\EVE\launcher\cache INFO - launcher is up to date INFO - Cache dir: u'C:\\Program Files (x86)\\CCP\\EVE\\launcher\\cache' INFO - checksum db: 'C:\\PROGRA~2\\CCP\\EVE\\launcher\\cache\\checksums' INFO - Getting Info from http://client.eveonline.com/patches/win_launcherinfoTQ_inc.txt INFO - server: 'TQ' INFO - folder: u'C:\\Program Files (x86)\\CCP\\EVE' INFO - hashdb: ChecksumDB at 'C:\\PROGRA~2\\CCP\\EVE\\launcher\\cache\\checksum s'> INFO - cachedir: u'C:\\Program Files (x86)\\CCP\\EVE\\launcher\\cache\\Download' INFO - update needed: False INFO - landing page: 'http://client.eveonline.com/launcher/en?server=tranquility ' backup page: u'C:\\Program Files (x86)\\CCP\\EVE\\launcher\\html\\Launcher_{la nguageID}.html' INFO - initializing BrowserWrapper with url: http://client.eveonline.com/launcher/en?server=tranquility INFO - cefbrowser initialized INFO - Registered backupUrl base as u'C:\\Program Files (x86)\\CCP\\EVE\\launche r\\html\\Launcher_{languageID}.html' INFO - SetClientUpToDate True
This is what happens when I run it in console mode. Now I don't know about anyone else, but it certainly looks like theres a few broken things in there, such as the initial debug message and the fact that 'Remote Version' says 1.05 and 'Local Version' says 1.09. Will somebody please tell me wtf is going on with this thing so I can fix it sometime in the next week!
Again, I am using Windows 7 Home Premium x64 |
Pila Ferant
Royal Amarr Institute Amarr Empire
0
|
Posted - 2012.03.14 22:10:00 -
[596] - Quote
As requested I once again delete everything related to EVEOnline on my Mac (10.7 Lion). Downloaded (Yet Again) the client and installed. Still getting this the "EVE Online Error" with two buttons "Open console" and "Terminate".
Syslog shows the following python traceback:
http://pastebin.com/uApmgeLX
Please, for the love of all that is good resolve this issue as it is driving me crazy..... A work around or something. This launcher is a total and complete failure, and I'm paying money to play a game that at this point is completely non-functional.. I can't even get too the Launcher screen... Seriously getting very very irritated by this. I have ask dozens of times about THIS EXACT ISSUE and I have yet to receive even a Response from a DEV telling me that they are looking into it.
I'm giving you Devs a chance to redeem yourselves by ATLEAST RESPONDING before I contact my Credit Card company and start disputing charges. |
Hayta Five
Red Horizon Inc Cascade Imminent
0
|
Posted - 2012.03.14 22:33:00 -
[597] - Quote
My problem is resolved, thanks to the suggestions cited above in this thread. Thank you for those!
I use the free AVG anti-virus package. I added the three exe's mentioned above in the Resident Shield exceptions list, but nothing happened. Only after completely shutting down AVG (under extra >advanced > temporary shut-down), the launcher worked like a charm and I'm able to play Eve now. |
crowdfart
Native Freshfood Minmatar Republic
0
|
Posted - 2012.03.14 22:37:00 -
[598] - Quote
mine is broken to
windows 7 ultimate ..
when i try to run eve from program files it says
the version of this file is not compatible with the verson if windows your running, check your computers system inforamtiont o see whether you need an x86 (32 bit or a x64 ( 64 bit ) version of the program, and the contact the software publisher
repair completed successfully but when i click close it pops up with
see log file
repair.exe.log says
Exception in thread Thread-2: Traceback (most recent call last): File "threading.pyc", line 530, in __bootstrap_inner File "threading.pyc", line 483, in run File "zsync\readFromUrl.pyc", line 117, in DownloadPart File "zsync\readFromUrl.pyc", line 136, in _DownloadPart File "zsync\zsync.pyc", line 762, in callback FileSyncError: data corruption
No handlers could be found for logger "zsync"
thoughts ?
|
Lovelocke
Enlightened Industries Test Alliance Please Ignore
74
|
Posted - 2012.03.14 22:44:00 -
[599] - Quote
crowdfart wrote:mine is broken to
windows 7 ultimate ..
when i try to run eve from program files it says
the version of this file is not compatible with the verson if windows your running, check your computers system inforamtiont o see whether you need an x86 (32 bit or a x64 ( 64 bit ) version of the program, and the contact the software publisher
repair completed successfully but when i click close it pops up with
see log file
repair.exe.log says
Exception in thread Thread-2: Traceback (most recent call last): File "threading.pyc", line 530, in __bootstrap_inner File "threading.pyc", line 483, in run File "zsync\readFromUrl.pyc", line 117, in DownloadPart File "zsync\readFromUrl.pyc", line 136, in _DownloadPart File "zsync\zsync.pyc", line 762, in callback FileSyncError: data corruption
No handlers could be found for logger "zsync"
thoughts ?
Try the anti-virus suggestion.
Which anti=-virus are you using? Go to it's options and look for something which allows you to add an exclusion in the Protocol for launcher.exe, repair.exe, exefile.exe, eve.exe. Add the exclusions, run the repair, run launcher. If this fails then delete all the cache from the local appdata folder and try again. |
Augustus Ogana
EntroPraetorian Academy EntroPraetorian Aegis
1
|
Posted - 2012.03.14 23:07:00 -
[600] - Quote
This post about Windows launcher problems and solutions is now updated with router bypass and AVG methods. Thanks, Hayta Five! |
|
|
|
|
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 30 .. 33 :: one page |
First page | Previous page | Next page | Last page |