> During CQWW I noticed the memory count in the upper right corner getting very
> low. I had one time when I got a "runtime error". I think this is my fault,
> here's the conditions.
Hmm - I have tested the program running into the ground memory wise, and
haven't seen any runtime errors. Anytime you see one - it means it is
probably a bug on my part. If there any numbers displayed (1234:5678),
let me know. Also the runtime error number.
> Running the band map and two radios, up at about 1200 contacts and the band
> map is pretty full, which I find will improve the situation if you delete the
> calls you have worked. (I'm figuring there's an awful lot of memory
> operations going on with the bandmap active.)
>
> Also, there were three or four times the bandmap went blank for no reason
> (none that I could see). Reloading brought things back.
I haven't seen this - unless maybe you are using an Icom and the band
changes to NON if you get a read error?
> Is there a "hi-mem" command I should set in the autoexec.bat? Forgive the
> mumbling, I just finished 40 hours of headset time. It's still a wonderful
> contest logging program. 73 de Bill
If you run the program MEMMAKER - it will automatically optimize your
AUTOEXEC.BAT file to free up as much memory below 640K as possible.
Tree
--
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
|