I also got a runtime error with 6.49, but with OH0R(space)
I reset, rebooted to dos from w95, ran TRLog, typed in OH0R<enter> and never
had a problem after that.
Afterwards, I realized I probably should have written down the runtime error
number, right? Is that useful?
I still wish there were two callsign and exchange fields for radio1 and
radio2 for us eternal S&P'ers.
73,
dale, kg5u
-----Original Message-----
From: owner-trlog@contesting.com [mailto:owner-trlog@contesting.com]On
Behalf Of Marion J. Henson
Sent: Monday, May 29, 2000 12:41 PM
To: trlog@contesting.com
Subject: [TRLog] V6.49 Runtime Error
Never experienced this problem with earlier versions but twice when I
tried to log QSO's with RM6A and once when logging DF0NF my computer
locked up with error message of Runtime error. Control/Enter had no
affect. Had to push the RESET button to restart computer. No data
appears to have been lost -- just time to recycle things. Was using DOS
window with Windows 98 first time so switched to DOS prompt at
start-up. Same result. Bug in program? Or was I the only one to
experience this? Why?
***W6NKR***
--
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
--
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
|