Oolite Bulletins

Q6600 Geforce 8800 GT Windows XP SP3

Tried 1.65 and 1.72.2 versions. No OXPs.

cmd.exe screen blinks and nothing else happens. Error log isn't created. No config file is created. In fact, no new files are created.

It seems I'm the only one that has this problem here on forum. I've got absolutely no idea what to do... Help

A few thoughts..

Are you installing to the default location or did you change it to somewhere else?

Have you tried uninstalling and reinstalling it? Sometimes (rare) you can just be unlucky and have an install fail. (This one I'm guessing you have tried, but thought I'd mention it anyway)

Are you using one of those third-party programs that manage installs and uninstalls instead of the built in Windows tool?

Are you sure your system is currently virus/adware/spyware/trojan free?

Tried default installation folder and c:\oolite - same result.

Tried reinstalling. Nothing.

I don't use any installation programs. Just run Oolite-1.72.2-test.exe

I'm sure my system is clean. NOD32 + COMODO FW are on 24/7.

Tried starting it with 1024x768 and 1680x1050. Nothing.

I've seen this once on my own system, a long time back.. wish I could remember what fixed it.. curse this fossilised brain of mine..

I'll put some thought into it, see what I can come up with.. in the meantime, in a few hours the Brits on this board will be waking up, hopefully they will have some more ideas to contribute..

If I run oolite.exe it'll create stderr.txt containing:

2009-08-05 22:51:58.562 oolite[3912] File NSUserDefaults.m: 626. In [NSUserDefaults +standardUserDefaults] Improper installation: No language locale found

Reinstalled Nvidia drivers and DX9. Nothing's changed.

Some quick research indicates that you will get that error message by running the executable directly..

From another thread:

Your log looks very similar to what you get if you try to run oolite.exe directly. (normally found in c:\Program Files\Oolite\oolite.app\)

This doesn't work because windows isn't normally set up with the right information oolite needs.

What you need to do instead is to run the .bat file in the directory above:

Code: Select all

c:\Program Files\Oolite\RunOolite.bat

That .bat file sets up the right information for oolite to do its job, then calls oolite.exe.

Have you tried RunOolite.bat?

RunOolite.bat is the correct way to lauch the game at the moment (this is fixed in the upcoming 1.73 release) what happens when you run that batch file?

@echo off
set GNUSTEP_PATH_HANDLING=windows
set GNUSTEP_LOCAL_ROOT=C:\Program Files\Oolite\oolite.app
set GNUSTEP_NETWORK_ROOT=C:\Program Files\Oolite\oolite.app
set GNUSTEP_SYSTEM_ROOT=C:\Program Files\Oolite\oolite.app
set HOMEPATH=C:\Program Files\Oolite\oolite.app
oolite.app\oolite.exe %1 %2 %3 %4

That's what I'm normally running.

-------------------------

I was able to run it in Safe Mode. 256 colors. 0 graphic accelleration. Text is unreadable. It created config file, but still doesn't run in Windows Normal Mode.

If I run Runoolite.bat from cmd.exe window it says Access is denied... I wonder if it's supposed to be like that.

So.. the batch file runs, but then the game fails to launch.. hmm.. I'm about at the limit of my Oolite troubleshooting knowledge for this area of problems. The boards Windows Guru is another_commander, hopefully he will see this thread soon and be able to throw some more light on things..

Oh, a belated welcome to "the friendliest board this side of Reidquat" to you!! Hopefully you'll soon be plying the spaceways!

Thanks alot!
I'm sure it's something simple, but I still gotta figure it out.

Here's what it looks like in Safe Mode. Might be drivers after all. Is there an alternative to original Nvidia drivers? I've got the latest now - 190...

asterisk wrote:

Here's what it looks like in Safe Mode. Might be drivers after all. Is there an alternative to original Nvidia drivers? I've got the latest now - 190...

Try reverting back to an older version of your driver. It will be faster too. The whole PhysX-stuff will slow down the whole thing and your latest ForceWare driver (190.x) uses a lot more ressources than the older versions. On my machine (GeForce Go 7950 GTX 512MB) I've had to step back to very old drivers (FW 86.14) to get the best performance. Newer drivers are working and some things really look better, but they are hungry :-)

Oh, and could you try it in Admin mode (installation+init)?

My work PC plays it fine and it's got latest drivers. Oh, the memories...

I'm gonna try admin installation as soon as I get back home.

If nothing else works, I'll reinstall OS.

@asterisk: Can you please post the file Latest.log, found in [OoliteInstallDir]\oolite.app\Logs immediately after running the game and failing? We have had cases where people were reporting that they had latest drivers while there were some apparent remnants of an older driver installation messing things up and Oolite was able to pick this up in its log. Also, if there is an stderr.txt inside your game folders after the game exits, please post that too.

^ Those files aren't being created.

I think I figured out the problem. It has something to do with restrictions in cmd.exe (terminology?)

For example, I can't run "control userpasswords2" in cmd.exe window. It gives me "Access is denied" error. But I can run "control userpasswords2" through Run menu. I figured out I get "Access is denied" for many things I run in cdm.exe

That explains why oolite can't even creat log files, since something in my system restricts it to start.

Does anyone know how to lift all the restrictions in cmd.exe?

Opengl drivers don't work in safe mode, hence the 'censored' look.

The batch file should just work by double clicking on it, you might be able to get round your cmd.exe restrictions that way...

Still, you might want to try Diziet Sma's trunk builds instead. For 1.73 we managed to do away with the batch file and you can simply click on Oolite.exe to start the game.

Hope this helps!

I'm 95% positive it's my OS problem. Not the game. It works flawlessly on my N10Jh and work computer, both of which don't have restrictions (term?) in cmd.exe

I'm not sure what DS's trunk build is, how I go about it or where I download 1.73 version from...