Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-06-19 Thread Geert Janssens
Hi, When you say you do a test run of v2.6.1, and afterwards v3.5 again, does that mean you have both of them installed simultaneously on your system ? I see a few potential issues in the information you have provided so far: 1. "The procedure entry point 'inflateValidate' could not be found in

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-06-12 Thread Oliver Heidelbach via gnucash-user
Okay, so I installed cygwin and ran GNUCash with gdb like proposed. I just renamed the current 3.5 program directory, not uninstalled it though. There was no new .gnucash directory in my home directory. I then re-renamed the two directories previously renamed (see below). I did a test start

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-06-09 Thread Oliver Heidelbach via gnucash-user
Hello, thank you for your detailed answer. Am 27.05.2019 um 15:53 schrieb Geert Janssens: Unfortunately I can't interpret the Sysinternals stuff either. Will gnucash 3.x start for a different user on your system ? That is, can you log in as a user that never has used gnucash before and then

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-05-27 Thread John Ralls
The useful part of the stack trace is at the bottom: libstdc++-6.dll!__cxa_throw+0x5c msvcrt.dll!free+0x39 libgnc-core-utils.dll!_ZN5boost9iterators6detail23operator_arrow_dispatchIRNS_10filesystem15directory_entryEPS4_E5applyES5_+0x11 msvcrt.dll!free+0x46

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-05-27 Thread Geert Janssens
Unfortunately I can't interpret the Sysinternals stuff either. Will gnucash 3.x start for a different user on your system ? That is, can you log in as a user that never has used gnucash before and then try to start gnucash ? If it does, it may be tripping over some metadata on your PC or the

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-04-21 Thread Oliver Heidelbach via gnucash-user
Yes, I had Cygwin installed and now deinstalled it accoording to their uninstall instructions including removing the registry entries. Same problem as before unfortunately. The following is the call stack from the Sysinternals Process Explorer: wow64cpu.dll!CpuGetContext+0x4

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-04-20 Thread Jimmy R via gnucash-user
I'm using Win 7 with no problem If I recall correctly...and Im guessing here I had the same problem..its been a while. I had a one Visual C++ missing between releases. They *must *be installed in sequential order. If you have one missing in between I had to uninstall the latter versions , install

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-04-20 Thread Geert Janssens
Do you have other applications on your system that use guile (like Lilypond for example) ? Regards, Geert Op donderdag 18 april 2019 13:26:08 CEST schreef Oliver Heidelbach via gnucash-user: > I reinstalled the current version again to see the log. > > It does not write any log file since

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-04-18 Thread Oliver Heidelbach via gnucash-user
I reinstalled the current version again to see the log. It does not write any log file since the Visual C++ runtime pops with that error. I don't know if this helps, but I tried to run guile.exe from the command line and this happened: ### C:\Program Files

Re: [GNC] Cannot run v3 on Windows 7 since a year

2019-04-09 Thread Colin Law
Have a look in the gnucash trace file after you try to start it. https://wiki.gnucash.org/wiki/Tracefile Colin On Tue, 9 Apr 2019 at 10:25, ohei2 via gnucash-user wrote: > > Hi, > > I just tried to install v3.5 on my Win7 64bit. It installed and on the the > first attempt to start it I get > >

[GNC] Cannot run v3 on Windows 7 since a year

2019-04-09 Thread ohei2 via gnucash-user
Hi, I just tried to install v3.5 on my Win7 64bit. It installed and on the the first attempt to start it I get /This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information/ I also tried an uninstall and