I've tried to run Oolite 1.76.1 on my Windows 7 Home Premium laptop. It's 64-bit.
When I try to run it, I get a pop-up asking if I want to let the program make changes to my computer. When I answer 'yes', the screen flashes briefly, and an Oolite icon appears on the taskbar before vanishing.
I've tried disabling my Norton firewall based on previous threads, without success.
Here's the latest log:
18:47:12.515 [log.header]: Opening log for Oolite version 1.76.1 (x86-32 test release) under Windows at 2012-05-28 18:47:12 +0200.
4 processors detected.
Build options: spoken messages, mass/fuel pricing, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.
Note that the contents of the log file can be adjusted by editing logcontrol.plist.
18:47:12.878 [display.mode.list.native]: Windows native resolution detected: 1366 x 768
Which folder is Oolite installed in? Can you please give us the system specs complete with graphics card type and drivers version? What other processes are running at the time? Also, are older versions of the game running OK? Is there an stderr.txt file remaining in the oolite.app folder after the crash? If yes, please post the contents here. Finally, have you tried the -nosplash switch in the command line?
Is it possible that Nortons has quarantined Oolite, I wonder? Check the Nortons history - it should tell you if that's the case. If so, you'll need to make an exception in Nortons and tell it to restore Oolite. Oh, and welcome aboard!
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
Which folder is Oolite installed in? Can you please give us the system specs complete with graphics card type and drivers version? What other processes are running at the time? Also, are older versions of the game running OK? Is there an stderr.txt file remaining in the oolite.app folder after the crash? If yes, please post the contents here. Finally, have you tried the -nosplash switch in the command line?
Thanks for the quick reply. In answer to your questions -
It's in C:\\Oolite.
Specs:
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120330-1504)
Language: English (Regional Setting: English)
System Manufacturer: TOSHIBA
System Model: Satellite C660
BIOS: Phoenix SecureCore Version 1.80
Processor: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz (4 CPUs), ~2.4GHz
Memory: 6144MB RAM
Available OS Memory: 5938MB RAM
Page File: 2848MB used, 9026MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I'm not 100% sure I know exactly how to do the last thing you suggested - I created a shortcut and added -nosplash after the .exe like this: "C:\Oolite\oolite.app\oolite.exe -nosplash". When I tried this, an Oolite window (blank, white) opened and closed quickly.
Is it possible that Nortons has quarantined Oolite, I wonder? Check the Nortons history - it should tell you if that's the case. If so, you'll need to make an exception in Nortons and tell it to restore Oolite. Oh, and welcome aboard!
I've had a look through the history & quarantine log, and I can't see it there.
Thanks! Glad to be here; hopefully I can get Oolite running to remind me of being an 80s child...
I am a bit perplexed. There does not seem to be any clear clue as to why it crashes. The only thing that comes to mind at this stage is graphics drivers version. A quick look at Intel's website shows that the latest driver version for Windows 7 Home Premium 64 bit for the HD series of chipsets is at version 8.15.10.2622 (21/01/2012) while you have 8.15.10.2189 (not sure when that is from). I would suggest making a recovery point (so that you can return to your previous working condition in case something goes wrong) and attempting an installation of the newer drivers.
I am a bit perplexed. There does not seem to be any clear clue as to why it crashes. The only thing that comes to mind at this stage is graphics drivers version. A quick look at Intel's website shows that the latest driver version for Windows 7 Home Premium 64 bit for the HD series of chipsets is at version 8.15.10.2622 (21/01/2012) while you have 8.15.10.2189 (not sure when that is from). I would suggest making a recovery point (so that you can return to your previous working condition in case something goes wrong) and attempting an installation of the newer drivers.
Thanks - I just tried to update from the Intel website and received this message:
A customized computer manufacturer driver is installed on your computer. The Intel Driver Update Utility is not able to update the driver. Installing a generic Intel driver instead of the customized computer manufacturer driver may cause technical issues. Contact your computer manufacturer for the latest driver for your computer.
I'm a bit nervous therefore about getting the newer driver.
EDIT: I've found an updated driver on the Toshiba site. Will check it out.
Last edited by gypsyjackson on Mon May 28, 2012 5:54 pm, edited 1 time in total.
I know what you mean, that's why I thought a recovery point (or any other means of falling back to the present condition) would be a good idea. It looks like others have had similar concerns and this is what the intertubes have to say about it: http://answers.yahoo.com/question/index ... 020AAZOsEN
Hmmm. Wouldn't let me apply new drivers. I tried to download the latest Toshiba pack, but when I ran it, it didn't seem to apply. Also tried to get the Intel generic one, but when I ran it, it told me the pack wasn't validated for my computer - and to check Toshiba...
![[EliteWiki]](/images/elitewikismall.png){kind=small}
Capt. Murphy's OXPs