Test Server Feedback

[I cannot log onto test server on two machines for the last two months. I have tried many approaches and have ready through the forums, but no fix has yet to be seen.

Here has what I have done so far.

* Install with Autoinstall.exe
* Used blank directory in SISI-Launcher clicked play, let patch.
* Used Offline / package installer method.
* Copy and paste TQ server into seperate folder and tried to patch / use server address in end of shortcut.

Between each one of these things I have clean removed the installation and deleted the temporary directories the launchers/repair tools created the patching that always fails.

In sisi-launcher / Repair.exe It get's to step four and parses and error which fails the install.

---

Sisi-launcher/repair tool dialogue


(1/7) Downloading index: Initializing ...
(1/7) Downloading index: 100.0%, 573.65 KB/573.65 KB, 95.70 KB/s, 00m01s
(2/7) Hashing files: Initializing ...
(2/7) Hashing files: 100.0%, 00m00s
(3/7) Downloading recipes: Initializing ...
(3/7) Downloading recipes: 100.0%, 10.31 KB/10.31 KB, 2.06 KB/s, 00m00s
(4/7) Calculating patch: Initializing ...
bin\_trinity_deploy.dll, missing 198 out of 198 blocks
bulkdata\1000001.cache2, missing 3 out of 3 blocks
Traceback (most recent call last):
File "repairTool\progressPanel.pyc", line 83, in _TaskRun
File "repairTool\repairUI.pyc", line 97, in Start
File "repairTool\repairLogic.pyc", line 184, in Repair
File "repairTool\repairLogic.pyc", line 333, in Restore
File "zsync\zsync.pyc", line 376, in RestoreFolder
File "zsync\zsync.pyc", line 557, in GetFileRestorers
File "zsync\fileSync.pyc", line 121, in IsComplete
File "zsync\fileSync.pyc", line 104, in GetFoundRanges
File "zsync\fileSync.pyc", line 148, in _UpdateRanges
File "zsync\fileSync.pyc", line 220, in _UpdateCurrentData
File "zsync\fileSync.pyc", line 229, in _ReadChunk
OverflowError: Python int too large to convert to C long
Total Runtime: 0h00m03s

---

Furthermore I opted to try to look into the log file, but that too is tricky. As soon as close out the error message / repair tool completely the temp folder deletes it's inner contents despite the launcher previously claiming to have made a valid log file.

So, I went into the temp folder before closing out the program and found the repair.exe log in - C:\Users\M0D\AppData\Local\Temp\nsoF667.tmp - which says

' No handlers could be found for logger "carbon" '

i stoped useing the SISI-Launcher its the main thing that keeps messing up logon.
i now use on the desk top icon "C:\Program Files\CCP\Singularity\eve.exe" /server:Singularity
works better.