Hello Radiosports Fans...
In the IARU, I noticed early in the contest (something less than 100
Qs I believe) that my remaining memory was lower than I expected -
and dropping fast. I also noticed the message "Byte/block array!!"
(or similar - too fast for me to read!) would flash in the callsign
entry block every time I logged a QSO.
After a while, I was concerned about the low memory, so I did a
CTRL-Y to dump the name memory, but the remaining memory display did
not increase. I exited the program and restarted with a small
increase in available memory. For example, the remaining memory was
down to 328; when I re-started, the remaining memory was 1624. The
memory continued to decrease rapidly. I made several program
stops/restarts until the thing apparently ran out of memory
completely and the keyboard was frozen - couldn't even CTRL-ALT-DEL.
This was with 414 Qs in the log.
I turned off the machine, rebooted and re-started TR, but only got as
far as an editable log window and light blue screen with no other
characters on it. Also, again the computer was locked up tight.
After several attempts to get the program going, I decided to look at
the LOGCFG.DAT file. What I found was that the CTRL-Y did not place
a NAME MEMORY DISABLE = TRUE entry into the LOGCFG.DAT file like I
thought it was supposed to do. I added this line with my editor, and
upon restarting TR, had loads of available memory. I just checked
and my log with 900+ Qs has 33,496 available.
So, I see two problems. 1)CTRL-Y not dumping the names and updating
the LOGCFG.DAT and 2)Something goofy happening with the memory usage
associated with the names file.
I realize a multi-mode, multi-band contest such as this has a high
memory requirement for dupe sheets, but I didn't think it would run
out at 400 Qs. I was using version 5.73 on a Compaq 486DX33 with 4
meg of RAM.
Any ideas?
73 de Lee
=-=-=-=-=-=-=-=-=-=-=
Lee Hiers, AA4GA
Cornelia, GA
aa4ga@contesting.com
=-=-=-=-=-=-=-=-=-=-=
|