bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Error message on start up of latest build


From: Christopher D. Yep
Subject: Re: [Bug-gnubg] Error message on start up of latest build
Date: Mon, 05 Jul 2004 16:11:27 -0400

At 02:04 PM 4/22/2004 +0100, Jon Kinsey wrote:
address@hidden wrote:

Build: Version 0.14.2-dev 1.1565 040419 (build Apr 20 2004)
On start up I get in dos box :

*Failed to open texture: textures/felt.png
Failed to open texture: textures/felt.png
Failed to open texture: textures/felt.png
Failed to open texture: textures/alder.png
Failed to open texture: textures/hinge.png
Failed to open texture: textures/felt.png
*
If I close this box gnubg also closes.
I can minimize it and carry on as normal though

You need to get the latest texture files:
http://users.skynet.be/bk228456/texturesZip.exe

BTW are you starting in 2d or 3d mode? (the message shouldn't appear in 2d mode)

Jon

Windows XP
Build: Version 0.14.3-dev 1.1621 040703

I recently downloaded the above version of gnubg (my previous version was from Jan. 2004, so I haven't been keeping up with all the changes to gnubg since then). On start up I get the same behavior as Michael reported in April (above).

Two solutions were suggested (#1 and #2 below):

1. Get the latest texture files (http://users.skynet.be/bk228456/texturesZip.exe). However, this is now a dead link.

2. Within the GUI, select Settings, Appearance, then choose any pre-defined board design, then Save Settings. However, as soon as I click "Appearance," gnubg immediately crashes.

3. I then tried my own solution. In the textures directory I made copies of one of the existing .png files (I randomly chose base3.png). I renamed these copies felt.png, alder.png, and hinge.png. (I assumed that gnubg was looking for these files, so at the minimum I wanted to have these files exist.) This did not solve the problem (the dos error box still occurs; also if I click on "Appearance," gnubg still immediately crashes).

What is the current work-around for this problem?  Thanks.

Chris






reply via email to

[Prev in Thread] Current Thread [Next in Thread]