This is a multi-part message in MIME format.
------=_NextPart_000_0024_01C16836.3CB1EA20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am using a PCI 2 comport card.
Like someone said earlier Com3=3DCom6 and Com4=3DCom7 for me. That is =
not the proper WL syntax, but I have my .ini file reflecting the above. =
I am running my radio and TU on those ports and use the Com1 for PTT, CW =
key, and FSK keying (MMTTY) and works fine. Which leaves Com2 available =
for something.
73,
Dave, K7JJ
----- Original Message -----=20
From: Gil Baron=20
To: jjreisert@alum.mit.edu ; clive@gw3njw.fsworld.co.uk ; =
WriteLog@contesting.com=20
Sent: Thursday, November 08, 2001 8:26 AM
Subject: Re: [WriteLog] WL Compatibility
At 07:32 11/8/2001, Jim Reisert wrote:
--- Clive Whelan <clive@gw3njw.fsworld.co.uk> wrote:
> Unfortunately, as I have just discovered PCI i/o cards, only=20
> permit COM5 up, and WL only permits COM4 down, seems like a non=20
> starter?
Not true on either count.
It is true that WIN98 will say you are on COM 5-8 on a PCI card. XP =
and WIN2000 do it correctly. It is also true as you point out that it =
dose not matter with the ini change.
1. I bought the cheapest PCI 2S1P card I could find at CompUSA.
Windows XP installed it at COM3 and COM4.
2. Writelog *can* access COM5-8 but you need to add a few lines
to writelog.ini to do it - search the reflector archives.
73 - Jim AD1C
=3D=3D=3D=3D=3D
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <jjreisert@alum.mit.edu>, http://www.ad1c.com
__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
Gil Baron http://members.home.com/gbaron
W0MN 44.08208 N 92.51263 W 1055'
"Baila como nadie te ve"=20
------=_NextPart_000_0024_01C16836.3CB1EA20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#000080 size=3D2>I am using a PCI 2 =
comport=20
card.</FONT></DIV>
<DIV><FONT face=3DArial color=3D#000080 size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#000080 size=3D2>Like someone said =
earlier Com3=3DCom6=20
and Com4=3DCom7 for me. That is not the proper WL syntax, but I have my =
.ini file=20
reflecting the above. I am running my radio and TU on those ports and =
use the=20
Com1 for PTT, CW key, and FSK keying (MMTTY) and works fine. Which =
leaves Com2=20
available for something.</FONT></DIV>
<DIV><FONT face=3DArial color=3D#000080 size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#000080 size=3D2>73,</FONT></DIV>
<DIV><FONT face=3DArial color=3D#000080 size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#000080 size=3D2>Dave, K7JJ</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000080 2px solid; MARGIN-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 title=3Dgbaron@home.com href=3D"mailto:gbaron@home.com";>Gil =
Baron</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Djjreisert@alum.mit.edu=20
href=3D"mailto:jjreisert@alum.mit.edu";>jjreisert@alum.mit.edu</A> ; <A =
title=3Dclive@gw3njw.fsworld.co.uk=20
=
href=3D"mailto:clive@gw3njw.fsworld.co.uk";>clive@gw3njw.fsworld.co.uk</A>=
; <A=20
title=3DWriteLog@contesting.com=20
href=3D"mailto:WriteLog@contesting.com";>WriteLog@contesting.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, November 08, =
2001 8:26=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [WriteLog] WL=20
Compatibility</DIV>
<DIV><BR></DIV>At 07:32 11/8/2001, Jim Reisert wrote:<BR>
<BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">--- Clive Whelan =
<<A=20
=
href=3D"mailto:clive@gw3njw.fsworld.co.uk";>clive@gw3njw.fsworld.co.uk</A>=
>=20
wrote:<BR><BR>> Unfortunately, as I have just discovered PCI i/o =
cards,=20
only <BR>> permit COM5 up, and WL only permits COM4 down, seems =
like a=20
non <BR>> starter?<BR><BR>Not true on either =
count.</BLOCKQUOTE><BR><BR>It=20
is true that WIN98 will say you are on COM 5-8 on a PCI card. XP and =
WIN2000=20
do it correctly. It is also true as you point out that it dose not =
matter with=20
the ini change.<BR><BR><BR><BR>
<BLOCKQUOTE class=3Dcite cite=3D"" type=3D"cite">1. I bought the =
cheapest=20
PCI 2S1P card I could find at CompUSA.<BR> Windows =
XP=20
installed it at COM3 and COM4.<BR><BR>2. Writelog *can* access =
COM5-8=20
but you need to add a few lines<BR> to =
writelog.ini to do=20
it - search the reflector archives.<BR><BR>73 - Jim=20
AD1C<BR><BR><BR><BR>=3D=3D=3D=3D=3D<BR>Jim Reisert AD1C, 7 =
Charlemont Court, North=20
Chelmsford, MA 01863<BR>USA +978-251-9933, =
<jjreisert@alum.mit.edu>,=20
<A href=3D"http://www.ad1c.com/"=20
=
eudora=3D"autourl">http://www.ad1c.com</A><BR><BR>_______________________=
___________________________<BR>Do=20
You Yahoo!?<BR>Find a job, post your resume.<BR><A=20
href=3D"http://careers.yahoo.com/"=20
=
eudora=3D"autourl">http://careers.yahoo.com</A><BR>______________________=
_________________________<BR>WriteLog=20
mailing list<BR>WriteLog@contesting.com<BR><A=20
href=3D"http://lists.contesting.com/mailman/listinfo/writelog"=20
=
eudora=3D"autourl">http://lists.contesting.com/mailman/listinfo/writelog<=
/A></BLOCKQUOTE><X-SIGSEP>
<P></X-SIGSEP><FONT face=3D"Courier New, Courier">Gil Baron <A=20
href=3D"http://members.home.com/gbaron"=20
eudora=3D"autourl">http://members.home.com/gbaron</A><BR>W0MN 44.08208 =
N=20
92.51263 W 1055'<BR>"Baila como nadie te ve"=20
<BR></FONT></P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0024_01C16836.3CB1EA20--
|