Dear Max et al, Having returned from a long holiday yesterday, I downloaded the 1st October version of GNU for the first time after having posted my original mail with the subject line above (on 12th Sept). And this time everything just works fine! In fact, the problematic GNU executable from 7th Sept (which I had renamed and kept in the directory for future reference) is ALSO working now!? I guess there was a file missing in the directory which the Sept version was searching and not finding, therefore the error message after installation???
I just wanted to confirm that whatever you guys have done between mid Sept and now fixed my problem, thanks a lot for all your support and help - much appreciated! PS: By the way, I notice that the 3D performance on my old computer has also improved considerably. Coincidence or intended? Kind regards, --- On Thu, 24/9/09, Massimiliano Maini <[email protected]> wrote: From: Massimiliano Maini <[email protected]> Subject: Re: [Bug-gnubg] Installation & Application Error Problem - Help Needed To: "birol morgül" <[email protected]>, [email protected] Date: Thursday, 24 September, 2009, 9:36 AM I think I've found the issue. I've changed my PC at office (still XP) and I've experiencing the same problem. With gdb and a debug exe I got this: D:\Documents\gnubg>gdb gnubg-nogui-py-sse2-nomt-O3.exe-debug.exe GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-mingw32"... (gdb) run Starting program: D:\Documents\gnubg/gnubg-nogui-py-sse2-nomt-O3.exe-debug.exe [New thread 2980.0x208] warning: LDR: LdrpWalkImportDescriptor() failed to probe D:\Documents\gnubg\python26.dll for its manifest, ntstatus 0xc0150002 gdb: unknown target exception 0xc0150002 at 0x7c966668 Program received signal ?, Unknown signal. Program exited with code 030005200002. You can't do that without a process to debug. (gdb) quit I've reinstalled python and now I have the msvcr90.dll and also a file named: Microsoft.VC90.CRT.manifest Adding this into gnubg's install dir seems to solve the problem. I guess that on PCs where python was installed 9and the dll registerd or whatever) the problem was not occurring. I'll make it available in the next install archive. MaX. 2009/9/23 birol morgül <[email protected]> > > > Hi > > I think my problem is not related with Vista. > > My computer has XP and GNUBG do not work. Previous version (before 4 > september 2009 ) GNUBGs work very well. > Maybe there is problem in my XP. (But I do not think) > All other programs work in my XP. I did not meet any problem up to now. > > Other 2 computers: (of my children) > > In Computer with Vista, GNUBG works and the computer with Vista has those > DLLs in it. > > In computer with XP , GNUBG works and there are not those DLLs in it > > Maybe there is another problem > maybe problem is not related with those DLLs. > Maybe it is necessary to install XP in my computer again. > > Thank you > > BM
_______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
