Tidwald
Center for Advanced Studies
Gallente Federation
0
   |
Posted - 2011.11.10 14:44:00 -
[1] - Quote
Mohr Cowbell wrote:Salpun wrote:
Sisi currently works for me. Using the sisi launcher forcing a repair did not add the new functionality. Did the Win7 64bit files not get updated?
The new files are there and a launcher exe that is 458 KB is size is in the folder but does not run anything when clicked on.
Same issue here on Win7-64. When I run the launcher, I can see the process appear in task manager for about a second, then it goes away. I also tried right-clicking the shortcut and selecting Run as Administrator.
Exactly the same here, but on Win7-32.
|
Tidwald
Center for Advanced Studies
Gallente Federation
0
|
Posted - 2011.11.14 19:58:00 -
[2] - Quote
CCP Mandrake wrote:Finally, after serveral cups of coffee, i've finished reading all posts and got some pointers going forward making the launcher.
......
7. It need to behave nicely in a Windows environment - IT MUST NOT go changing access permissions to the 'C:\Program Files\CCP\SiSi' directory same applies to 'C:\Program Files\CCP\EVE' when rolled out to live.
When first run, launcher.exe asks for elevated privileges to lowerfolderprivs. I have no problems with allowing the elevated privileges when there is a clear need - such as when applying an update. But, changing the folder permissions to side-step the in built security is not acceptable.
When first run, after being updated with the SiSiLauncher, launcher appeared to download an update, ask for elevated privileges to run the updater (which is what I would expect), and an error dialog pops up "Errors occurred" - the logfile contains the following:
Traceback (most recent call last):
File "launcher.py", line 29, in module
File "localization\__init__.pyc", line 34, in LoadLocalizationData
File "localization\localization.pyc", line 31, in __init__
File "localization\localization.pyc", line 58, in _LoadLanguageData
File "xml\dom\minidom.pyc", line 1911, in parse
File "xml\dom\expatbuilder.pyc", line 922, in parse
IOError: [Errno 2] No such file or directory: 'launcher/localization.xml'
That file 'launcher/localization.xml' exists, and existed before launcher was run.
Why are you changing the folder permissions? It can't be to allow the updater to run, as it correctly asks for elevated privileges. The main eve program correctly uses more appropriate locations for logs 'C:\Users\xxxxxx\Documents\EVE\logs' and specific folders under 'C:\Users\xxxxx\AppData\Local\CCP\EVE'. The launcher appears to write its main log to the later location so there really is no need to change the permissions on the Sisi folder under "Program Files". |