The description for Event ID ( 0 ) in Source ( oolite ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 2009-11-19 09:16:35.812 oolite[2672] File NSUserDefaults.m: 626. In [NSUserDefaults +standardUserDefaults] Improper installation: No language locale found.
It doesn't matter whether I try with trunks or 1.73.4.
(32bit XP)
Other than that, the game runs normally. It clogged my event logs, though.
The easy solution to that is recompile the gnustep-base dll to not produce the "No language locale found message". The message is intended for complete gnustep-base installations only, whereas we knowingly distribute Oolite with a minimal GNUstep configuration. I just tried this and can confirm it works.
The harder but cleaner way would be to actually find why the message is produced and see if we can suppress or bypass it within Oolite's code instead of GNUstep's.
I've never compiled Oolite, so both ways are a blur to me.
"No language local found".. seems trivial, I must say. Only, I don't know does that mean that some language file is missing, or does it imply regional settings.
"No language local found".. seems trivial, I must say. Only, I don't know does that mean that some language file is missing, or does it imply regional settings.
If I understand correctly what GNUstep tries to do on startup, it looks for a specific file within a very specific and deeply nested folder structure. Other parameters might be required as well, I have not investigated in too much detail. It is actually more convoluted than it looks, but all this is not required for our intents and purposes.
I just used that command line switch in .GNUstepDefaults and the logs are not bloating any more.
This is not just "one annoyance less".
One of these days (this line is getting really old...) when I release this tool, ppl will start batch-verifying, and I don't want to be responsable for their event logs bloating with junk-reports.
Before you ask, I'll pack it with its own .GNUstepDefaults that would be switched for Oolite's one while verifying (to supress the log-popups and these event log reports).