I've downloaded 3.0.9b for Windows... now what?

PowerWyrm · October 13, 2008, 16:33

Whenever I click on angband.exe nothing happens at all... no window pops up, I just get the hourglass cursor for a few seconds then nothing. The process "angband.exe" appears in the task manager, but the window isn't created. This didn't happen with the 3.0.9a release...

PowerWyrm · October 13, 2008, 17:01

Update... 3.0.9a USED to work, but it seems only 3.0.6 and earlier works now. The only thing that happened recently is Windows Updater upgrading XP from SP2 to SP3.

Donald Jonker · October 13, 2008, 19:18

Forgive me if is terribly obvious, but have you tried restarting your PC? I occasionally have that same problem and a restart always clears it up.

Pete Mack · October 13, 2008, 20:33

I second donald. There's some wierd resource leak that cause angband to take longer and longer to start. 3.0.6 is not affected, apparently, but NPP and many other variants are. If someone could catch it in a debugger there would be at least a chance of debugging.

takkaria · October 14, 2008, 00:42

Quote:

Originally Posted by Pete Mack

I second donald. There's some wierd resource leak that cause angband to take longer and longer to start. 3.0.6 is not affected, apparently, but NPP and many other variants are. If someone could catch it in a debugger there would be at least a chance of debugging.

I have a suspicion it's compiler-related, too. 3.0.6 was compiled with MS VC++. No releases I've made have been compiled this way; and given that the Windows code is mostly untouched, this seems the most likely explanation. (NPP may use a different compiler, too.)

ChodTheWacko · October 14, 2008, 02:24

Quote:

Originally Posted by PowerWyrm

Whenever I click on angband.exe nothing happens at all... no window pops up, I just get the hourglass cursor for a few seconds then nothing.

If you see angband in your taskmgr, try killing/stopping programs until it starts.
Something is blocking it. On my XP box, I must close all dos prompts before angband pops up.

- Frank

October 13, 2008, 16:33	#1
PowerWyrm Prophet Join Date: Apr 2008 Posts: 2,955	I've downloaded 3.0.9b for Windows... now what? Whenever I click on angband.exe nothing happens at all... no window pops up, I just get the hourglass cursor for a few seconds then nothing. The process "angband.exe" appears in the task manager, but the window isn't created. This didn't happen with the 3.0.9a release... __________________ PWMAngband variant maintainer - check http://powerwyrm.monsite-orange.fr (or http://www.mangband.org/forum/viewforum.php?f=9) to learn more about this new variant!

October 13, 2008, 17:01	#2
PowerWyrm Prophet Join Date: Apr 2008 Posts: 2,955	Update... 3.0.9a USED to work, but it seems only 3.0.6 and earlier works now. The only thing that happened recently is Windows Updater upgrading XP from SP2 to SP3. __________________ PWMAngband variant maintainer - check http://powerwyrm.monsite-orange.fr (or http://www.mangband.org/forum/viewforum.php?f=9) to learn more about this new variant!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Angband Borg 3.0.9 and windows	Zappa	Vanilla	38	October 27, 2010 20:31
Windows v3.0.9 hanging?	JustinH	Vanilla	1	August 27, 2008 14:30
Opening a savefile in Windows	Zero	Vanilla	13	June 28, 2008 05:55
Terms/Additional Windows	Rimmer	Vanilla	4	March 30, 2008 15:56
Windows Compiling and Makefiles	APWhite	Vanilla	11	August 22, 2007 21:22

October 13, 2008, 19:18	#3
Donald Jonker Knight Join Date: Jun 2008 Posts: 593	Forgive me if is terribly obvious, but have you tried restarting your PC? I occasionally have that same problem and a restart always clears it up.

October 13, 2008, 20:33	#4
Pete Mack Prophet Join Date: Apr 2007 Location: Seattle, WA Posts: 6,766 Donated: $40	I second donald. There's some wierd resource leak that cause angband to take longer and longer to start. 3.0.6 is not affected, apparently, but NPP and many other variants are. If someone could catch it in a debugger there would be at least a chance of debugging.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)