The sluggish response I've usually found to be related to the improper
specification of parameters on the SMARTDRV command in AUTOEXEC.BAT. When
running in DOS mode, you need to set up some form of disk caching in memory
so that TR's disk write does not get in the way of the CW generation.
I forget the exact settings, but a /? will bring up the help file (or help
smartdrv, whichever). What you want is the setting for the drive containing
your log that essentially states that DOS will return control to the program
after the data is written to the cache, but BEFORE it is written to disk.
Thus, TR sees what amounts to an instant-response disk write and can get on
with sending the CW.
Another area causing hiccups in TR is if you have autosave to floppy turned
on. I never tell TR to periodically save to floppy, because floppy write
takes forever. Rather, I direct the "floppy" save function to a file on a
hard drive (ideally a different physical drive than the logging drive), and
have the smartdrv cache enabled for that drive (if different) as well. The
theory on this is that failures are rare in occurrences compared with QSOs,
etc...
If you had smartdrv or equivalent properly set, I have no idea what caused
your sluggish response. Smartdrv has fixed every such problem I've had.
This includes a networked, 4-position multi-multi, with an internet spotting
feed 5th computer, with a 386 as the slowest computer in the TR network. It
CAN be made to perform very well.
73,
Gary W2CS
| -----Original Message-----
| From: owner-trlog@contesting.com [mailto:owner-trlog@contesting.com]On
| Behalf Of Mike Heideman
<<SNIP>>
|
| We also experienced very sluggish response. While typing in a
| callsign the
| letters would take several seconds to appear. There were also
| multi-second
| delays in beginning to send CW, so much that sometimes the other
| station would
| start resending their callsign or exchange before our CW began. This was
| using a network of 6 computers, mixed 486 and Pentium machines, using SCP,
| TRMASTER, bandmaps, TR-Log 6.58. Minimum available memory seemed
| to be around
| 60K. Two of the CW computers were computer-interfaced.
|
<<SNIP>>
--
FAQ on WWW: http://www.contesting.com/FAQ/trlog
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|