Issues, Workarounds & Localization

I spended the last 36 hours trying to debug an issue when attemping to play Eve from a RAMDisk. At first I through that it was data corruption due to complains from the ExeFile client about "modified files" that were fixed after re-copying them from the Hard Disk, and it indeed was, as I found out with Memtest86 that the RAM had errors. Seems it couldn't cope up with the Timmings I set it at and had to relax them a bit. After being happy with Memtest86 results, I still had some minor issues, until I got tired, disabled everything, and tried doing it with the Hard Disk install. And figured out it was reproducible there, too.



The problem is the following:
When using the EVE Launcher (v.2.1.545736) with the default file shortcut:
launcher.exe /forcelauncher

After some 2 or 3 minutes long Hard Disk crunching, it validates the Eve Online installation and allows me to play. Closing it, and opening it again, tells me that the client is ready in just a few seconds. I usually just skip the launcher and go straight for ExeFile. So far no issues.
However, if I use the repair.exe file, it says that some files got "missing blocks" and downloads a 22 MB or so patch...


... and so on.

After letting it do his job, opening the Eve Launcher opens a installation-like window that install some files (That I think are these very same ones that got replaced by the repair utility, at least on the only one I checked before and after repair, en-GB.pak, it got the same CRC32, but different timestamp), then takes again two or three minutes to validate itself. And if I open the repair utility again, this repeats. I would expect that the repair utility would tell me that nothing is wrong instead of going into a loop like this, so I would think that its checksum list wasn't updated to the latest.


Additionally, repair doesn't seem to like some ASCII characters because it creates a new folder to put the "checksums" file at. In the spanish Windows XP SP3, the "Local Settings" folders is called "Configuración local" (Pay attention to that ó, is non standard), and there is were the regular Local Settings\Program Data\CPP\EVE client cache is at, however, the repair utility makes a folder called "Configuración local" with all the other subfolders at Documents and Settings\[myuser].


I would like to know if this behaviator ir reproducible, because I wasn't able to enjoy my RAMDisk thinking it had data corruption issues and wouldn't risk a client crash or BSOD that could make me lose a ship, and now, I have a high degree of confidence that it isn't from my side anymore.

Windows XP SP3 (Spanish)
No application that could cause interference was enabled at the time (Antivirus or whatever else)

close your launcher and it should update correctly I had the same issue then i closed the launcher and it updated fine

Because as my RAMDisk wasn't 100% stable, I was experiencing data corruption issues that made ExeFile complain about modified files while on the RAMDisk everytime I tried to open it, and that I should repair the Eve installation. So I did. After experimenting with several RAM settings I managed to get the launcher and the client consistently working, but I also ran the repair utility just to be sure that it didn't detected altered files after being on for several hours. But it was still complaining. So I spend 13 hours of Memtest86, and another day trying to figure out what caused those missing blocks errors, until I figured out that it the repair utility was wrong, as my data corruption issue had been fixed by then because everything else was working properly.