ConwayLife.com

I'm on 64-bit Windows 7. For some reason, 64-bit Golly 2.6 won't recognize python27.dll. I looked in GollyPrefs and saw that there's a path there that is certainly valid and works with Golly 2.5 and 32-bit Golly 2.6.

In a very reckless move that I probably shouldn't have done I tried deleting GollyPrefs and seeing if that works, but nope.

On a more minor note, the 64-bit version of Golly takes forever and a half to start up (about 20 seconds, while other versions take about two or three)
The buttons also don't look right. What I mean is that they should look like this: but they just look like this: I guess I'll just use 32-bit Golly for now.

SuperSupermario24 wrote:I'm on 64-bit Windows 7. For some reason, 64-bit Golly 2.6 won't recognize python27.dll. I looked in GollyPrefs and saw that there's a path there that is certainly valid and works with Golly 2.5 and 32-bit Golly 2.6.

A 64-bit Golly requires a 64-bit Python, so you can't use the python27.dll that works with 32-bit Golly.

As for the other problems, I've got no idea what might cause Golly to start up slowly, or why the buttons look different. I built the 32-bit Golly for Windows on an XP system using wxWidgets 2.8, but the 64-bit Golly was built by one of the other devs so I'll ask if they see the same problems.

One clue would be nice to know: when your 64-bit Golly creates the GollyPrefs file, which version of wxWidgets does it list (near the top of the file)?

Hm, I thought I would've had the 64-bit version of Golly 2.5, but I guess not. That makes sense.

The line you're asking about says this when I start the 64-bit version:
wx_version=wxWidgets 3.0.0

while it says this on the 32-bit version:
wx_version=wxWidgets 2.8.12

You mentioned using 2.8, so maybe that has something to do with it?