open All Channels
seplocked Linux
blankseplocked [Solved] Incursion fails to start under Linux
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Whitehound
The Whitehound Corporation
Frontline Assembly Point
Posted - 2010.11.30 17:43:00 - [1]
 

Edited by: Whitehound on 26/01/2011 23:09:19
Hello,

I was hoping to find a thread about it, but I must be alone with my problem.

I am using WINE 1.2.1 under Debian 5 with an NVidia GTX260. It worked well for as far as I can remember and with Incursion it now fails to start. Only the splash screen shows and then ExeFile.exe sits idle in the background.

Has anyone else had this problem and found a solution?

Aria Athias
Posted - 2010.11.30 19:44:00 - [2]
 

Debian 5/AMD64 with a GTX260 as well, but with Wine 1.3.7. I haven't had any major issues with Incursion yet. I'd try updating Wine first, using a deb from the Ubuntu repo to avoid most hassle.

My start script is pretty much just wine explorer /desktop=Eve,1680x1050 "D:\Programs\Eve\eve.exe" - Without the virtual desktop it eventually crashes. With, it's perfectly stable.

EFTPOS
Caldari
Posted - 2010.12.01 04:32:00 - [3]
 

ubuntu here wine 1.2.1

i got the same error after incursion patch and still cant get in ive tried the repair tool and get the following error:

Error:
Traceback (most recent call last):
File "repairPanel.pyc", line 325, in _Start
File "repair.py", line 294, in RunTask
File "repair.py", line 204, in TaskRestoreFolder
File "zsync\zsync.pyc", line 160, in RestoreFolder
File "zsync\zsync.pyc", line 305, in GetDownloadRangeSet
File "zsync\zsync.pyc", line 279, in GetFileRestorers
File "zsync\fileSync.pyc", line 348, in __init__
File "zsync\fileSync.pyc", line 120, in IsComplete
File "zsync\fileSync.pyc", line 103, in GetFoundRanges
File "zsync\fileSync.pyc", line 147, in _UpdateRanges
File "zsync\fileSync.pyc", line 219, in _UpdateCurrentData
File "zsync\fileSync.pyc", line 228, in _ReadChunk
MemoryError

Mr M
Posted - 2010.12.01 04:39:00 - [4]
 

Works fine here under Debian Squeeze with wine 1.1.42.
Have you tried to clear the cache? That sometimes mess things up.

EFTPOS
Caldari
Posted - 2010.12.01 04:44:00 - [5]
 

i personaly have cleared the cashe and reset the name of the jukebox folder as a precaution wine is in windows xp mode and after the incursion patch applied eve runns the launcher runs to the black screen and locks up

Whitehound
The Whitehound Corporation
Frontline Assembly Point
Posted - 2010.12.01 12:49:00 - [6]
 

I have found my problem.

Debian has released minor updates to the X11 core files one or two days before Incursion was released, which simply trashed the NVidia driver. After un- and reinstalling the NVidia driver is it now working again.

DJ Rubbie
Caldari
Dreddit
Test Alliance Please Ignore
Posted - 2011.01.19 09:15:00 - [7]
 

Originally by: EFTPOS
ubuntu here wine 1.2.1

i got the same error after incursion patch and still cant get in ive tried the repair tool and get the following error:

Error:
Traceback (most recent call last):
File "repairPanel.pyc", line 325, in _Start
File "repair.py", line 294, in RunTask
File "repair.py", line 204, in TaskRestoreFolder
File "zsync\zsync.pyc", line 160, in RestoreFolder
File "zsync\zsync.pyc", line 305, in GetDownloadRangeSet
File "zsync\zsync.pyc", line 279, in GetFileRestorers
File "zsync\fileSync.pyc", line 348, in __init__
File "zsync\fileSync.pyc", line 120, in IsComplete
File "zsync\fileSync.pyc", line 103, in GetFoundRanges
File "zsync\fileSync.pyc", line 147, in _UpdateRanges
File "zsync\fileSync.pyc", line 219, in _UpdateCurrentData
File "zsync\fileSync.pyc", line 228, in _ReadChunk
MemoryError


You are probably running the old repair tool that lives in your game folder. The patcher downloads the repair.exe and you should just leave that running, or try copying that into your eve installation.


 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only