Arto,
I did not have gaps between parts of the message. The delay came after the
entire "TU WC1M" message was sent, and the length of the delay was strictly
related to the size of the log. Your problem sounds more like an
interruption in PC-generated CW caused by Windows multitasking switching
from WL to some other activity. I don't have that problem because I use the
W5XD+ outboard keyer. The multitasking problem usually manifests itself as
abnormally long dots or dashes. It's normally caused by backround tasks,
such as printer drivers, stealing cycles. You might be able to solve this
problem by killing non-essential background tasks. But the fact that your
delay occured in the exact same place and was between two words leads me to
believe that there's something else going on. Were you sending the message
with the Insert key, the "exchange" key or did you have the Enter key option
enabled?
73, Dick WC1M
> -----Original Message-----
> From: Arto Liimatta [mailto:oh2kw@pp.kolumbus.fi]
> Sent: Friday, June 02, 2000 12:44 PM
> To: dick.green@valley.net; WriteLog
> Cc: Wayne Wright W5XD
> Subject: Re: [WriteLog] Slow Aurtomatic Save
>
>
> Hi,
>
> I noticed the same. Especially if you had copied only part of the
> call, lets say 2KW of my OH2KW, and
> WL was sending out 2KW 599 00x, there was a long gap after 2KW
> and 599. The gap was unnoticable,
> if the call was long like OH2KW. The long GAP caused that many
> stations started to answer as the call was just a part copy.
> My laptop was 266MHz DELL Latitude. The gap was quite a long even
> if the log was small. tried to turn off all
> possible things that I had turned on (beamhedings, check
> partial), no help.
>
> 73 de Arto OH2KW (in WPX XX9TKW)
>
> ----- Original Message -----
> From: Dick Green <dick.green@valley.net>
> To: WriteLog <Writelog@contesting.com>
> Cc: Wayne Wright W5XD <w5xd@alum.mit.edu>
> Sent: Friday, June 02, 2000 7:56 AM
> Subject: [WriteLog] Slow Aurtomatic Save
>
>
> >
> > I thought I should report that AutoSave slows down pretty
> severely when the
> > log gets big on a machine with a relatively slow hard drive. In
> WPX, I was
> > using a four-year old Toshiba 100MHz Pentium notebook. The hard drive is
> > pretty slow on this machine compared to state-of-the-art
> notebooks. Reponse
> > using WL was excellent in all respects except when the log got
> over about
> > 2000 QSOs and would get flushed to disk. It turned out that the delay
> > sending "TU WC1M" with the W5XD+ outboard keyer was just enough
> for the log
> > to get saved withiout interfering with operating, but I could
> see that once
> > I got over about 2500 QSOs the delay would be too long. Luckily
> (sort of),
> > the contest ended for me just short of that. I tried my 3K QSO log from
> > ARRLDX on that machine and the AutoSave was too slow to be practical.
> >
> > The only solution I can see to this is to turn off AutoSave,
> but that makes
> > me nervous -- especially with a large log in memory. I suppose
> the delay is
> > primarily caused by flushing the entire log to disk. Any chance
> record I/O
> > could be implemented so that only the changes would have to be written?
> >
> > 73, Dick WC1M
> >
> >
> > --
> > WWW: http://www.writelog.com/
> > Submissions: writelog@contesting.com
> > Administrative requests: writelog-REQUEST@contesting.com
> > Problems: owner-writelog@contesting.com
> >
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|