Am 05.11.2020 um 17:35 schrieb Petru Calenici:
> Am 05.11.2020 um 15:10 schrieb Petru Calenici:
>
> Another shot in the dark, but a good practice in any case: Do you
> explicitly _un_-install previous gretl installations before installing
> the new one? (E.g. in system settings, apps & features or what it's called.)
>
> Thanks for bearing with us, hopefully in the end this will solve a more
> general problem. But of course there's also a chance that your system is
> simply screwed up ;-)
>
> cheers
>
> sven
Yes, I did. Every time I installed the new version I uninstalled the one on my computer
using the unins000 program in the gretl folder.
_______________________________________________
Let me just add a remark here on the list for users who are reading this
in the future: From what I heard this problem was then resolved
off-list. The problem was real (in a third-party library shipped with
gretl on Windows), but apparently needed a certain Windows version and a
certain perhaps not very common CPU type. I think it was an internal
version upgrade of that helper library which solved the problem.
So if anybody using a current version of gretl on Windows (snapshot or
at least the upcoming release 2020e) has a similar problem, then it's
either a new bug or a regression, but not this very same bug which
should be squashed by now.
thanks
sven