One or two of you have mentioned having this error, and loss of the
LOG.TMP file. I saw the same error this morning! Better yet, I
think I know how to prevent it.
I was doing a TR READ on the W1AW log from last weekend. Near the end
of the log, I turned on SMARTDRV (the disk cache) and shortly thereafter
the error occurred. Runtime 103 is a file access error.
So, the current method of prevention is DO NOT USE THE DISK CACHE. This
is another arguement for not running the program under windows-95 as
I think the disk caching is automatic.
I have captured the address where the failure occurred and see if I
can do something to prevent the program from crashing - and possibly
recover from this error in the future.
You still might be okay during normal contest activity. When doing
the TR READ on this file, my rate was around 5000 QSOs/hour so the
disk activity is probably fairly extreme. However, since a couple of
you have experienced this problem under actual conditions, it is still
a possibility.
73 Tree N6TR
tree@contesting.com
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|