[Dx4win] DX4WIN Digest, Vol 97, Issue 16

[Dez Watson]

As a fellow JT65 and DX4WIN user I've also brought this up in the past.

For JT65 QSO's I use Logger32, for now.

73

Dez, G3WW / G0DEZ

----- Original Message ----- 
From: <dx4win-request at mailman.qth.net>
To: <dx4win at mailman.qth.net>
Sent: Thursday, May 17, 2012 4:03 PM
Subject: DX4WIN Digest, Vol 97, Issue 16


> Send DX4WIN mailing list submissions to
> dx4win at mailman.qth.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.qth.net/mailman/listinfo/dx4win
> or, via email, send a message with subject or body 'help' to
> dx4win-request at mailman.qth.net
>
> You can reach the person managing the list at
> dx4win-owner at mailman.qth.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of DX4WIN digest..."
>
>
> Today's Topics:
>
>   1. JT65 Signal Reports? (Tom Clark)
>   2. Re: PCIe LPT port problem (Pete Smith N4ZR)
>   3. PCIe LPT port problem solved! (Paul Peters)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 16 May 2012 13:16:10 -0400
> From: Tom Clark <tom.k3io at gmail.com>
> Subject: [Dx4win] JT65 Signal Reports?
> To: dx4win at mailman.qth.net
> Message-ID: <4FB3E0DA.30403 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Previously I asked for a slight modification to the "599" signal report
> in DX4WIN for JT65 users. In JT65, the signal report is the
> signal-to-noise ratio in dB. Actually it is the signal/(signal+noise)
> ratio, so the value is ALWAYS negative.  S/N = -10 dB is a strong
> signal, S/N=-25 dB is weak.
>
> The requested change is that the field allow a minus (-) sign, with a
> format "-nn" in addition to the implicit positive number.
> In addition to the sign, the numeric range needs to be widened;
> RST=00-10 is rejected,  while RST=11 and higher passes the test.
>
> Has anything happened on my earlier request? Is there any hope for us
> JT65 users other than sticking signal reports into notes fields? Are
> there any other JT65 users that are similarly frustrated?
>
> 73 de Tom K3IO  (ex W3IWI)
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 16 May 2012 16:09:42 -0400
> From: Pete Smith N4ZR <n4zr at contesting.com>
> Subject: Re: [Dx4win] PCIe LPT port problem
> To: dx4win at mailman.qth.net
> Message-ID: <4FB40986.6060600 at contesting.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I think their tech guy may have been blowing smoke, Paul(s) - I have a
> StarTech PEX1P PCIe Parallel Adapter Card - 1 Port, SPP, EPP, ECP
> (S262-8032) that I just got from Tigerdirect for a new Win7 PC.  While I
> haven't tried to use it with the antenna switching control side of
> DX4WIN, it works fine doing the same job for N1MM Logger, which also
> needs to know the port address.
>
> If your new machine is a 64-bit Win 7 machine, as even nearly the
> cheapest Dells may be now, then you may need a different port driver.
> In any case, it should be installed in the same folder as your DX4WIN
> executable, so that definitely is one place to look for a solution.
> Otherwise, I need to defer to Paul on the driver issue and how it is
> integrated with DX4WIN.
>
> 73, Pete N4ZR
> The World Contest Station Database, updated daily at 
> www.conteststations.com
> The Reverse Beacon Network at http://reversebeacon.net, blog at 
> reversebeacon.blogspot.com,
> spots at telnet.reversebeacon.net, port 7000 and
> arcluster.reversebeacon.net, port 7000
>
>
> On 5/16/2012 9:02 AM, Paul van der Eijk wrote:
>> Forwarding message for VE7BZ
>>
>> --Paul, KK4HD
>>
>> The day finally came when the old XP machine that has powered DX4WIN for
>> so many years died -- and it was replaced with a Win7 box. While I have
>> most things restored, I am stuck with an LPT port problem.
>>
>> I thought I could simply install a PCI (Express) LPT port card and get
>> going once again, but such is not the case due to the manner in which
>> Win7 or the card -- I'm not sure exactly which handles the port
>> addressing. The card in question is a StarTech model called PEX1P and
>> according to their tech support person it's not mappable -- so they
>> could not tell me the real port address.
>>
>> When I look at the card in Device Manager the Resource tab tells me the
>> I/O Range is D010 - D017 and D000 - D003. Again according to StarTech,
>> the only card they can give a real address for is a mappable model such
>> as their PCIPM card -- but it's not available in PCI (Express) -- only
>> straight PCI.
>>
>> One more thing. I am running DX4WIN v8.05, but when I run the
>> 'lptdriver.exe' file from within the Drivers folder the executable
>> always suggests installing the program in a folder labeled c:\dx4w803 --
>> not 805. I have restarted the computer according to the instructions
>> given when installing on a 64-bit system but DX4WIN always starts with
>> an error message saying it can't find the LPT port.
>>
>> So -- yes I need some help to sort out the problem. If you've had
>> experience with this issue I'd sure appreciate your insight and or
>> suggestions.
>>
>> 73 de Paul, VE7BZ
>> ______________________________________________________________
>> DX4WIN mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/dx4win
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:DX4WIN at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 16 May 2012 15:07:26 -0700
> From: Paul Peters <paul.stoneyground at gmail.com>
> Subject: [Dx4win] PCIe LPT port problem solved!
> To: DX4WIN at mailman.qth.net
> Message-ID:
> <CAEAyHzCPg7gykS1ef2xw5kTmFDejGO_+mBTrk-==3j8XyZs=OQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I am pleased to report that using the suggestion put forward by Larry, 
> K8UT
> earlier today I now have LPT port keying fully operational on my new 
> 64-bit
> Win7 machine. The solution was so obvious it was hard to see --simply 
> enter
> the odd looking address range in the portmap.ini file and save the file.
> The problem was more between the keyboard and the chair than in the new
> computer and for that I take full responsibility.
>
> For the record, I am using StarTech single port parallel card model PEXIP
> which is PCI Express. The address range shown in Device Manager was listed
> as D010 - D017 and D000 - D003. My portmap file entry is LPT1=$D010
>
> My thanks to all who offered their suggestions.
>
> 73 de Paul, VE7BZ
>
>
> ------------------------------
>
> _______________________________________________
> DX4WIN mailing list
> DX4WIN at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
>
>
> End of DX4WIN Digest, Vol 97, Issue 16
> **************************************