This is a multi-part message in MIME format.
------=_NextPart_000_005D_01BF35E4.C6948120
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Since I don't contest every weekend my memory may be a bit skewed but It =
seems that 6.45 runs a bunch slowrer than previous versions.
I noted this in SSCW and turned off bandmapping and everything else =
defaulted but uneeded with minimal improvement. Never got floppy backup =
to work at all.
In SSSSB I noted it took much longer to write a Q to the log and clear =
for the next Q.=20
I don't recall this delay in the past so I wonder if this is related to =
the floppy problem. I did get a floppy light at the appropriate Q for =
the first instance of floppy backup, which never went out, although no =
disk access ever occured.
*********************************************************************
Len Revelle lenrev@mc.net
N9IJ n9ij@cs.com
AMA 60055 http://user.mc.net/~lenrev
*********************************************************************
----- Original Message -----=20
From: nsacon=20
To: trlog@contesting.com=20
Sent: Monday, November 22, 1999 07:43 PM
Subject: [TRLog] Cursor delay
I was bothered by a delay in moving from the call window to the =
exchange window in either CQ or S&P mode this weekend. After entering =
the callsign in the call window and hitting enter, the cursor would =
delay for about the same amount of time it takes for the returning =
station to give the introductory exchange phrase "N7RX, please copy my =
number". It was more troublesome in S&P mode than CQ mode, since I could =
hit enter while giving the calling station my information in CQ mode and =
I'd have the exchange window by the time was done. In S&P mode, I had =
sometimes had to write to my brain buffer until I got control of the =
exchange window.=20
I never noticed this before. I did switch to a new computer (Thinkpad =
600E) for SS and ran TR in MS-DOS re-boot mode because TR would not work =
as a Win95 DOS window (but that's another story). I'm not writing to a =
floppy or using TR to control a contest card. I did have it set up to =
key the xmtr for CW SS for the first time and the only thing I can think =
of is that I altered by config file in a way I'd never done before when =
I set-up for parallel port keying. Otherwise, I'm using only the plain =
vanilla logging features - no packet, no multiple radios, no radio =
control or etc.
Is this delay normal? Can anybody think of why its happening and what =
I can do to stop it? Oh yeah, its v. 6.45.=20
TNX in advance
73
Neal N7RX
------=_NextPart_000_005D_01BF35E4.C6948120
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2722.2800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Since I don't contest every weekend my memory may be =
a bit=20
skewed but It seems that 6.45 runs a bunch slowrer than previous=20
versions.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2> I noted this in SSCW and turned off =
bandmapping and=20
everything else defaulted but uneeded with minimal improvement. Never =
got floppy=20
backup to work at all.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>In SSSSB I noted it took much longer to write a Q to =
the log=20
and clear for the next Q. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>I don't recall this delay in the past so I wonder if =
this is=20
related to the floppy problem. I did get a floppy light at the =
appropriate Q for=20
the first instance of floppy backup, which never went out, although no =
disk=20
access ever occured.</FONT></DIV>
<DIV>********************************************************************=
*<BR> =20
Len=20
Revelle =
=20
<A=20
href=3D"mailto:lenrev@mc.net";>lenrev@mc.net</A><BR> &nbs=
p; =20
N9IJ &nb=
sp; &nbs=
p;=20
<A =
href=3D"mailto:n9ij@cs.com";>n9ij@cs.com</A><BR> &n=
bsp;=20
AMA 60055 <A=20
href=3D"http://user.mc.net/~lenrev";>http://user.mc.net/~lenrev</A><BR>***=
******************************************************************<BR></D=
IV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:neal@sacon.net"; title=3Dneal@sacon.net>nsacon</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:trlog@contesting.com"=20
title=3Dtrlog@contesting.com>trlog@contesting.com</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, November 22, 1999 =
07:43=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [TRLog] Cursor =
delay</DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D3>I was bothered by a delay in moving from the call =
window to=20
the exchange window in either CQ or S&P mode this weekend. After =
entering=20
the callsign in the call window and hitting enter, the cursor would =
delay for=20
about the same amount of time it takes for the returning station to =
give the=20
introductory exchange phrase "N7RX, please copy my number". It was =
more=20
troublesome in S&P mode than CQ mode, since I could hit enter =
while giving=20
the calling station my information in CQ mode and I'd have the =
exchange window=20
by the time was done. In S&P mode, I had sometimes had to write to =
my=20
brain buffer until I got control of the exchange window. =
</FONT></DIV>
<DIV> </DIV>
<DIV>I never noticed this before. I did switch to a new computer =
(Thinkpad=20
600E) for SS and ran TR in MS-DOS re-boot mode because TR would not =
work as a=20
Win95 DOS window (but that's another story). I'm not writing to a =
floppy or=20
using TR to control a contest card. I did have it set up to key the =
xmtr for=20
CW SS for the first time and the only thing I can think of is that I =
altered=20
by config file in a way I'd never done before when I set-up for =
parallel port=20
keying. Otherwise, I'm using only the plain vanilla logging features - =
no=20
packet, no multiple radios, no radio control or etc.</DIV>
<DIV> </DIV>
<DIV>Is this delay normal? Can anybody think of why its happening and =
what I=20
can do to stop it? Oh yeah, its v. 6.45. </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>TNX in advance</DIV>
<DIV>73</DIV>
<DIV>Neal N7RX</DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_005D_01BF35E4.C6948120--
--
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
|