Thanks to N6EE and N7BT for the suggestion to re-install WL.
To start that process, I again re-booted the *%#$ machine (2nd time today)
and tested WL just to see if it it's still acting up. Behold, now WL does
the SAVE AS perfectly. No re-install needed.
The magic of Windoze! This could turn into a religion. It's already been
called a cult.
This was obviously a Win10 issue because N1MM also crashed when I tried to
open a new database. I really don't like N1MM. The Win update only happened
yesterday so I haven't tried out a whole lot of other programs so see if
this problem is more wide spread.
Anyway, I guess when all else fails .. re-boot .. again ... and again !
Aloha, Alan AD6E / KH6TU
On Fri, Sep 30, 2016 at 5:49 PM, Ron Lodewyck <rwlodewyck@gmail.com> wrote:
> Alan,
>
> I just reinstalled the Writelog Version 12.08 update and that seems to
> have cured the flaky behavior. That's based on a few minutes testing
> Writelog, so I am holding my breath.
>
> GL and 73,
> Ron N6EE
>
>
> On Fri, Sep 30, 2016 at 8:42 PM, Ron Lodewyck <rwlodewyck@gmail.com>
> wrote:
>
>> Hi Alan,
>>
>> I also just had the Microsoft autoupdater install another (2nd in a week)
>> Windows 10 update earlier today. And now Writelog is acting very screwy.
>> It has crashed twice and my COM ports keep getting disconnected. I will do
>> what I did with the last Windows 10 update which resulted in the Bandmap
>> dispalying nada, i.e. I will go ahead and reinstall Writelog version 12.08
>> update. That fixed the Bandmap problem. Let's hope a Writelog reinstall
>> fixes this flaky behavior problem.
>>
>> GL,
>> Ron N6EE
>>
>>
>> On Fri, Sep 30, 2016 at 7:12 PM, Alan Maenchen <ad6e@arrl.net> wrote:
>>
>>> I'm having new trouble setting up for CQP.
>>>
>>> Using latest WriteLog version 12.09F
>>> I can open a new log and set everything correctly. It all plays very
>>> nicely but SAVE AS causes it to crash without saving anything. Opening an
>>> existing log also works fine but SAVE AS again causes it to crash.
>>>
>>> This was all working fine in the Salmon Run.
>>>
>>> I updated Win 10 yesterday.
>>>
>>> Note: If I bring up N1MM+ and try to save a new database ... it also
>>> crashes. So this seems to be a recent Win 10 problem. If I make a new log
>>> in the existing database it seems to work (so far) but I really don't like
>>> N1MM
>>>
>>> Any ideas?
>>>
>>> 73, Alan AD6E / KH6TU
>>>
>>>
>>>
>>> _______________________________________________
>>> NCCC mailing list
>>> THIS EMAIL LIST IS A NO-FLAME ZONE! See guidelines at:
>>> http://lists.contesting.com/mailman/listinfo/nccc
>>> Post to: nccc@contesting.com (never publish this address)
>>> Manage your subscription at: http://lists.contesting.com/ma
>>> ilman/options/nccc
>>> Archives at: http://lists.contesting.com/mailman/private/nccc/
>>>
>>
>>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|