Date   

Re: monitor 60M for new DXCC

Hasan Schiers N0AN
 

The purpose of my post was to explain to Wolf why, in my estimation,  Dave may have chosen not to include 60 meters in the Suite.(and to agree with it)  My comments were not to start a rehash of this worn out topic on the DXLab list! This is not the place for debate on 60m privileges, I didn't start a debate and won't continue one. This is my last post on the matter. Suffice it to say, while I personally follow the 1500 Hz approach, and as a very active 60m FT8 operator with hundreds of qsos, 99% of the USA stations I work are not transmitting on 1500 Hz exclusively, nor am I aware of any enforcement actions taken against them.

Where, precisely, did the following statement come from, or is it your own conclusion?
Is this word for word from a rule or interpretive guideline (please cite the reference), or your interpretation of something else?

<Begin quote>:
The use of any of the 60 meter "channels" as a 3 KHz wide CW/digital
band or for ACDS (automatically controlled digital operations) is
*ILLEGAL* for *ANY* amateur station licensed by the United States.
<End quote>

If you have such a source, please email me privately, as this whole thing appears to be way off topic for DXLab, and I apologize to the list members for this kind of distraction.

73, N0AN
Hasan



On Thu, Jan 16, 2020 at 7:59 AM Joe Subich, W4TV <lists@...> wrote:
On 2020-01-16 8:08 AM, Hasan Schiers N0AN wrote:

> There has been considerable debate in the USA as to whether operation
> on any other frequency than 5357 kHz with a 1500 Hz tone is
> permissible. Taking this position means only one freq (audio
> included) may be used in the USA. There is no 3 kHz spread allowed,
> single frequency means single frequency, not a band from 200 to 3000
> Hz. So there is no room, according to this way of thinking.

*THERE IS NO DEBATE*  That is exactly what the US Rules state - one
user per channel and that user must monitor in USB for primary users
(US Government).

The use of any of the 60 meter "channels" as a 3 KHz wide CW/digital
band or for ACDS (automatically controlled digital operations) is
*ILLEGAL* for *ANY* amateur station licensed by the United States.

73,

    ... Joe, W4TV


On 2020-01-16 8:08 AM, Hasan Schiers N0AN wrote:
> Wolf, (not speaking for Dave, just my own assessment of the issue you
> raised)
>
> Your comments about being USA centered certainly have merit. At first, I
> had the perspective that you used, i.e.. there is plenty of room in a 3 kHz
> bandwidth ...and I myself have worked tons of DX on 60m with a dipole and
> 80w  It is a super band for FT8 on 5357 kHz
>
> I think the general idea is to prevent 60m (a shared resource in the USA),
> from becoming a mad-house of DX award chasers. Since the resource is so
> limited there is a fear that encouraging mass dx chasing ops will cause
> real issues, again, inside the USA.
>
> Another scary issue:
>
> There has been considerable debate in the USA as to whether operation on
> any other frequency than 5357 kHz with a 1500 Hz tone is permissible.
> Taking this position means only one freq (audio included) may be used in
> the USA. There is no 3 kHz spread allowed, single frequency means single
> frequency, not a band from 200 to 3000 Hz. So there is no room, according
> to this way of thinking.
>
> Secondly, this is a shared resource with other services and we (USA) are
> SECONDARY and must not cause interference to these other services. When I
> examine the entire 3 kHz span around 5357 kHz, I do see commercial or other
> services sending data. We have been told NOT to interfere with those
> services and if they are on 1500 Hz to stop transmitting.
>
> So it's not just narrow (3 kHz) that is the issue. Narrow may, in fact be a
> single audio freq of 1500 Hz (which is often ignored)
> It is also the "shared" allocation on a non-interference basis.
> Both of which are terribly compromised by encouraging DX style/Award Style
> or congested operations on 60m inside the USA
>
> Your USA-centric comments are accurate, but the restrictions and
> limitations imposed are not driven by whim.
>
> ...and before someone asks, "Why doesn't someone like ARRL take this up
> with the FCC?"   The answer is "never ask an authority a question you can't
> afford the answer 'NO' to". The point being,  we could lose the ability to
> use FT8 on 60m altogether if we ask the wrong question to the wrong
> authority. For now, we can use it with care. Encouraging DX operating or
> award operating is not "using it with care".
>
> 73, N0AN
> Hasan
>
>
> On Thu, Jan 16, 2020 at 5:19 AM Wolf, DK1FW <dk1fw@...> wrote:
>
>> Due to the channelized 60m situation in the US I understand ARRLs
>> decision to not issue a 60m DXCC to some extent. After all US hams are
>> ARRL's prime customers.
>>
>> However, there is DXing following personal targets beyond DXCC and a
>> world outside FCC jurisdiction. It is a pity that DXLab is too focused
>> on the US situation.
>>
>> A blunt statement that 60m  "is too narrow for DXing" is simply
>> narrow-sighted (even Dave is not perfect).
>> 30m is only 3 times as wide as 60m and is almost the backbone of DXing
>> during the present sunspot minimum.
>> Monitoring 60m from Europe the band is NEVER overcrowded with DXing and
>> would show almost no actitivity without DXing.
>>
>> Fortunately SpotSpy (in the licensed version - a beer or a pizza) offers
>> 60m DXCC alerts and tracking of 60m worked /confirmed status for those
>> of us, who are interested in 60m DX.
>>
>> 73 de Wolf, DK1FW
>>
>>
>> Am 15.01.2020 um 16:59 schrieb Dave AA6YQ:
>>> + AA6YQ comments below
>>>
>>> How can I monitor 60M for new DXCC's?
>>> Creating a filter in Spotcollector?
>>> I'm not good at SQL.
>>>
>>> + 60m QSOs do not count for ARRL awards like DXCC. DXLab does not
>> support realtime award tracking for DXCC on 60m. The ARRL considers this
>> band to be too narrow for DXing; I agree.
>>>
>>>             73,
>>>
>>>                      Dave, AA6YQ
>>>






Re: monitor 60M for new DXCC

Joe Subich, W4TV
 

On 2020-01-16 8:08 AM, Hasan Schiers N0AN wrote:

There has been considerable debate in the USA as to whether operation
on any other frequency than 5357 kHz with a 1500 Hz tone is
permissible. Taking this position means only one freq (audio
included) may be used in the USA. There is no 3 kHz spread allowed,
single frequency means single frequency, not a band from 200 to 3000
Hz. So there is no room, according to this way of thinking.
*THERE IS NO DEBATE* That is exactly what the US Rules state - one
user per channel and that user must monitor in USB for primary users
(US Government).

The use of any of the 60 meter "channels" as a 3 KHz wide CW/digital
band or for ACDS (automatically controlled digital operations) is
*ILLEGAL* for *ANY* amateur station licensed by the United States.

73,

... Joe, W4TV


On 2020-01-16 8:08 AM, Hasan Schiers N0AN wrote:
Wolf, (not speaking for Dave, just my own assessment of the issue you
raised)
Your comments about being USA centered certainly have merit. At first, I
had the perspective that you used, i.e.. there is plenty of room in a 3 kHz
bandwidth ...and I myself have worked tons of DX on 60m with a dipole and
80w It is a super band for FT8 on 5357 kHz
I think the general idea is to prevent 60m (a shared resource in the USA),
from becoming a mad-house of DX award chasers. Since the resource is so
limited there is a fear that encouraging mass dx chasing ops will cause
real issues, again, inside the USA.
Another scary issue:
There has been considerable debate in the USA as to whether operation on
any other frequency than 5357 kHz with a 1500 Hz tone is permissible.
Taking this position means only one freq (audio included) may be used in
the USA. There is no 3 kHz spread allowed, single frequency means single
frequency, not a band from 200 to 3000 Hz. So there is no room, according
to this way of thinking.
Secondly, this is a shared resource with other services and we (USA) are
SECONDARY and must not cause interference to these other services. When I
examine the entire 3 kHz span around 5357 kHz, I do see commercial or other
services sending data. We have been told NOT to interfere with those
services and if they are on 1500 Hz to stop transmitting.
So it's not just narrow (3 kHz) that is the issue. Narrow may, in fact be a
single audio freq of 1500 Hz (which is often ignored)
It is also the "shared" allocation on a non-interference basis.
Both of which are terribly compromised by encouraging DX style/Award Style
or congested operations on 60m inside the USA
Your USA-centric comments are accurate, but the restrictions and
limitations imposed are not driven by whim.
...and before someone asks, "Why doesn't someone like ARRL take this up
with the FCC?" The answer is "never ask an authority a question you can't
afford the answer 'NO' to". The point being, we could lose the ability to
use FT8 on 60m altogether if we ask the wrong question to the wrong
authority. For now, we can use it with care. Encouraging DX operating or
award operating is not "using it with care".
73, N0AN
Hasan
On Thu, Jan 16, 2020 at 5:19 AM Wolf, DK1FW <dk1fw@...> wrote:

Due to the channelized 60m situation in the US I understand ARRLs
decision to not issue a 60m DXCC to some extent. After all US hams are
ARRL's prime customers.

However, there is DXing following personal targets beyond DXCC and a
world outside FCC jurisdiction. It is a pity that DXLab is too focused
on the US situation.

A blunt statement that 60m "is too narrow for DXing" is simply
narrow-sighted (even Dave is not perfect).
30m is only 3 times as wide as 60m and is almost the backbone of DXing
during the present sunspot minimum.
Monitoring 60m from Europe the band is NEVER overcrowded with DXing and
would show almost no actitivity without DXing.

Fortunately SpotSpy (in the licensed version - a beer or a pizza) offers
60m DXCC alerts and tracking of 60m worked /confirmed status for those
of us, who are interested in 60m DX.

73 de Wolf, DK1FW


Am 15.01.2020 um 16:59 schrieb Dave AA6YQ:
+ AA6YQ comments below

How can I monitor 60M for new DXCC's?
Creating a filter in Spotcollector?
I'm not good at SQL.

+ 60m QSOs do not count for ARRL awards like DXCC. DXLab does not
support realtime award tracking for DXCC on 60m. The ARRL considers this
band to be too narrow for DXing; I agree.

73,

Dave, AA6YQ


Re: monitor 60M for new DXCC

Hasan Schiers N0AN
 

Wolf, (not speaking for Dave, just my own assessment of the issue you raised)

Your comments about being USA centered certainly have merit. At first, I had the perspective that you used, i.e.. there is plenty of room in a 3 kHz bandwidth ...and I myself have worked tons of DX on 60m with a dipole and 80w  It is a super band for FT8 on 5357 kHz

I think the general idea is to prevent 60m (a shared resource in the USA), from becoming a mad-house of DX award chasers. Since the resource is so limited there is a fear that encouraging mass dx chasing ops will cause real issues, again, inside the USA.

Another scary issue:

There has been considerable debate in the USA as to whether operation on any other frequency than 5357 kHz with a 1500 Hz tone is permissible. Taking this position means only one freq (audio included) may be used in the USA. There is no 3 kHz spread allowed, single frequency means single frequency, not a band from 200 to 3000 Hz. So there is no room, according to this way of thinking.

Secondly, this is a shared resource with other services and we (USA) are SECONDARY and must not cause interference to these other services. When I examine the entire 3 kHz span around 5357 kHz, I do see commercial or other services sending data. We have been told NOT to interfere with those services and if they are on 1500 Hz to stop transmitting.

So it's not just narrow (3 kHz) that is the issue. Narrow may, in fact be a single audio freq of 1500 Hz (which is often ignored)
It is also the "shared" allocation on a non-interference basis.
Both of which are terribly compromised by encouraging DX style/Award Style or congested operations on 60m inside the USA

Your USA-centric comments are accurate, but the restrictions and limitations imposed are not driven by whim.

...and before someone asks, "Why doesn't someone like ARRL take this up with the FCC?"   The answer is "never ask an authority a question you can't afford the answer 'NO' to". The point being,  we could lose the ability to use FT8 on 60m altogether if we ask the wrong question to the wrong authority. For now, we can use it with care. Encouraging DX operating or award operating is not "using it with care".

73, N0AN
Hasan


On Thu, Jan 16, 2020 at 5:19 AM Wolf, DK1FW <dk1fw@...> wrote:
Due to the channelized 60m situation in the US I understand ARRLs
decision to not issue a 60m DXCC to some extent. After all US hams are
ARRL's prime customers.

However, there is DXing following personal targets beyond DXCC and a
world outside FCC jurisdiction. It is a pity that DXLab is too focused
on the US situation.

A blunt statement that 60m  "is too narrow for DXing" is simply
narrow-sighted (even Dave is not perfect).
30m is only 3 times as wide as 60m and is almost the backbone of DXing
during the present sunspot minimum.
Monitoring 60m from Europe the band is NEVER overcrowded with DXing and
would show almost no actitivity without DXing.

Fortunately SpotSpy (in the licensed version - a beer or a pizza) offers
60m DXCC alerts and tracking of 60m worked /confirmed status for those
of us, who are interested in 60m DX.

73 de Wolf, DK1FW


Am 15.01.2020 um 16:59 schrieb Dave AA6YQ:
> + AA6YQ comments below
>
> How can I monitor 60M for new DXCC's?
> Creating a filter in Spotcollector?
> I'm not good at SQL.
>
> + 60m QSOs do not count for ARRL awards like DXCC. DXLab does not support realtime award tracking for DXCC on 60m. The ARRL considers this band to be too narrow for DXing; I agree.
>
>            73,
>
>                     Dave, AA6YQ
>
>
>
>
>
>




Re: Best Spot Sources for use

Al Groff
 

I use WB8ZRL.no-ip.org port 7300  here in Iowa
AL, K0VM

On 1/15/2020 4:21 PM, Gilbert Baron W0MN wrote:

I am in MN

Many spot sources I had been using in SC just do not connect. They time out.

IRC does work.

 

On FT8 I usually use only WSJTX as I am looking for states and if WSJTX does not see them well not going to either with CQ only..

 

Looking for recommended sources when on HF, SSB or CW THAT ARE RELIABLE, AND FIT FOR THIS Ara.

 

TIA for suggestions.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: monitor 60M for new DXCC

Wolf, DK1FW
 

Due to the channelized 60m situation in the US I understand ARRLs decision to not issue a 60m DXCC to some extent. After all US hams are ARRL's prime customers.

However, there is DXing following personal targets beyond DXCC and a world outside FCC jurisdiction. It is a pity that DXLab is too focused on the US situation.

A blunt statement that 60m  "is too narrow for DXing" is simply narrow-sighted (even Dave is not perfect).
30m is only 3 times as wide as 60m and is almost the backbone of DXing during the present sunspot minimum.
Monitoring 60m from Europe the band is NEVER overcrowded with DXing and would show almost no actitivity without DXing.

Fortunately SpotSpy (in the licensed version - a beer or a pizza) offers 60m DXCC alerts and tracking of 60m worked /confirmed status for those of us, who are interested in 60m DX.

73 de Wolf, DK1FW


Am 15.01.2020 um 16:59 schrieb Dave AA6YQ:

+ AA6YQ comments below

How can I monitor 60M for new DXCC's?
Creating a filter in Spotcollector?
I'm not good at SQL.

+ 60m QSOs do not count for ARRL awards like DXCC. DXLab does not support realtime award tracking for DXCC on 60m. The ARRL considers this band to be too narrow for DXing; I agree.

73,

Dave, AA6YQ





Re: monitor 60M for new DXCC

aart wedemeijer PA3C
 

On Wed, Jan 15, 2020 at 05:31 PM, Michael Raskin wrote:
but for only one year
That is not working for me thanks for the tip.

Aart


Re: WSJT-X > DXKeeper ...

Mike Flowers
 

Thanks, Dave. I’ll study this.

-- 73 de Mike Flowers, K6MKF, NCDXC - "It's about DX!"

On Jan 15, 2020, at 6:46 PM, Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

Would someone please direct me to the documentation for how to make the connection from WSJT-X directly to DXKeeper.

+ There is no direct connection between WSJT-X and DXKeeper.

+ There are two ways that WSJT-X can interoperate with DXLab. In the "direct" scheme, SpotCollector orchestrates the interoperation,
as described here:

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect>


2. Alternatively, JTAlert can orchestrate the interoperation, as described here>

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert>

73,

Dave, AA6YQ





Re: WSJT-X > DXKeeper ...

Dave AA6YQ
 

+ AA6YQ comments below

Would someone please direct me to the documentation for how to make the connection from WSJT-X directly to DXKeeper.

+ There is no direct connection between WSJT-X and DXKeeper.

+ There are two ways that WSJT-X can interoperate with DXLab. In the "direct" scheme, SpotCollector orchestrates the interoperation,
as described here:

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect>


2. Alternatively, JTAlert can orchestrate the interoperation, as described here>

<https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert>

73,

Dave, AA6YQ


WSJT-X > DXKeeper ...

Mike Flowers
 

Hi Folks,

 

Would someone please direct me to the documentation for how to make the connection from WSJT-X directly to DXKeeper.

 

I have a buddy who wants to do this.

 

Thanks.

 

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

 


Re: Pathfinder frozen

Dave AA6YQ
 

+ AA6YQ comments below

Another question if this is an IE problem why can I open IE and use it but not when it is open in Pathfinder??

+ There are many differences, like the name of the .exe file -- which is what anti-malware monitor.

73,

Dave, AA6YQ


Re: Pathfinder frozen

Kent N6WT
 

Another question if this is an IE problem why can I open IE and use it but not when it is open in Pathfinder??

Thanks
73
Kent
N6WT


On Wed, Jan 15, 2020 at 3:02 PM Kent Olsen <kilo6dko@...> wrote:
Dave
I cannot be sure when this behavior started. I don't typically use Pathfinder, it starts and it is open on 1 of my 4 monitors. The only way I noticed was I saw something that interested me on a QRZ page so I went to look at it and it would not scroll. As I said it is not like the page is unuseable. The next spot I click on it changes to that call but is still frozen. I can't even grab the window and move it. 

Hardware changes none. Software changes many.

I will have to check to see how long it typically takes.


Thanks
73
Kent
N6WT


On Wed, Jan 15, 2020 at 10:17 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Several times.

+ When did this freezing behavior first begin? What changes did you make to your hardware or software around that time?

+ How long does it typically take for Pathfinder to freeze after you start it?

         73,

                Dave, AA6YQ






Re: Clublog errors

w6de
 

Be aware, just because ClubLog will update their data to include a specific operation does not mean it is or will be accepted by the ARRL for credit toward an award.
Check Glorioso Island (FR/G) and there is a list of operators on Glorioso who's operation did not have landing permission and the ARRL does not accept that operation for DXCC credit.
https://clublog.org/test.php?call=DJ8CR/FR/G

My one and only FR/G contact was with one of those operators.

Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Mark Robinson
Sent: 15 January, 2020 01:48
To: DXLab@groups.io
Subject: Re: [DXLab] Clublog errors

ClubLog keeps a very good database and I had a Mount Athos QSO
SV2AUA/SY that wasn't in their database and I supplied them with a scan
of the qsl that I had. They are very helpful and a valuable resource.

https://clublog.org/test.php?call=SV2AUA%2FSY&year=2020&month=1&day=15&hour=01&minute=46

and there is my card


73 Mark N1UK



On 13-Jan-20 6:52 PM, Jim Wysocki wrote:
I've had this happen when loading some of my very old '70's QSOs into
ClubLog. Their records can be corrected by sending them scans of the
old QSL cards. They'll usually add more exceptions to their DXCC
entity assignment rules if presented with some evidence in support of
the changes. A copy of those old QSLs should be sufficient.

GL & 73, Jim W9FI


Re: Pathfinder frozen

Kent N6WT
 

Dave
I cannot be sure when this behavior started. I don't typically use Pathfinder, it starts and it is open on 1 of my 4 monitors. The only way I noticed was I saw something that interested me on a QRZ page so I went to look at it and it would not scroll. As I said it is not like the page is unuseable. The next spot I click on it changes to that call but is still frozen. I can't even grab the window and move it. 

Hardware changes none. Software changes many.

I will have to check to see how long it typically takes.


Thanks
73
Kent
N6WT


On Wed, Jan 15, 2020 at 10:17 AM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Several times.

+ When did this freezing behavior first begin? What changes did you make to your hardware or software around that time?

+ How long does it typically take for Pathfinder to freeze after you start it?

         73,

                Dave, AA6YQ






Re: Best Spot Sources for use

Dave AA6YQ
 

+ AA6YQ comments below

I am in MN

Many spot sources I had been using in SC just do not connect. They time out.

IRC does work.


On FT8 I usually use only WSJTX as I am looking for states and if WSJTX does not see them well not going to either with CQ only..

Looking for recommended sources when on HF, SSB or CW THAT ARE RELIABLE, AND FIT FOR THIS Ara.

+ In addition to DX Summit (via IRC) and WSJT-X, I suggest a nearby cluster, a cluster on the North American west coast, a cluster
in Japan, and a cluster in Europe.

+ I'm using N6WS, JH1RFM, and EI7MRE, all of which have been reliable. I also use K1TTT, but you should choose a cluster closer to
your station.

73,

Dave, AA6YQ


Re: Internet Stack

Dave AA6YQ
 

+ AA6YQ comments below

Today I had some time and researched the internet stack fix. I followed instructions I found on the net and the results seemed to
follow what the instructions called for.

I then tried the ctrl "Sync LOTW QSL's" and again after the process reached the 58 second of the countdown it faulted with the
connection timeout message.

Everything else in DXLabs seems to be working as it should. I'm able to upload Q's to LOTW and Sync LOTW QSL's without getting the
timeout message. I can see where the LOTW rcvd box changes to a Y in recent uploaded Q's.

Is there anything else I might try?

+ In the private email exchange that followed public thread here

<https://groups.io/g/DXLab/message/189768>

+ You initially reported that Google's Chrome Browser also- timed out when attempting to download QSLs from LoTW using the same URL
that DXKeeper uses; this further confirmed the "broken or misconfigured internet stack" theory.

+ Then you reported that Google's Chrome Browser was now able to download QSLs from LoTW, but you couldn't say what you changed to
enable this. You reported that DXKeeper still experienced timeouts.

+ The evidence still points at a broken or misconfigured internet access mechanism in Windows.

73,

Dave, AA6YQ


Best Spot Sources for use

Gilbert Baron W0MN
 

I am in MN

Many spot sources I had been using in SC just do not connect. They time out.

IRC does work.

 

On FT8 I usually use only WSJTX as I am looking for states and if WSJTX does not see them well not going to either with CQ only..

 

Looking for recommended sources when on HF, SSB or CW THAT ARE RELIABLE, AND FIT FOR THIS Ara.

 

TIA for suggestions.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Internet Stack

Julio Peralta
 

Today I had some time and researched the internet stack fix. I followed instructions I found on the net and the results seemed to follow what the instructions called for.

 

I then tried the ctrl “Sync LOTW QSL’s” and again after the process reached the 58 second of the countdown it faulted with the connection timeout message.

 

Everything else in DXLabs seems to be working as it should. I’m able to upload Q’s to LOTW and Sync LOTW QSL’s without getting the timeout message. I can see where the LOTW rcvd box changes to a Y in recent uploaded Q’s.

 

Is there anything else I might try?

 

Julio, W4HY

 


Re: Pathfinder frozen

Dave AA6YQ
 

+ AA6YQ comments below

Several times.

+ When did this freezing behavior first begin? What changes did you make to your hardware or software around that time?

+ How long does it typically take for Pathfinder to freeze after you start it?

73,

Dave, AA6YQ


Re: Prop View Error messages

W0MU
 

Worked in safe mode.  Started digging around in the firewall settings and for some reason propview was blocked. Thanks for the help


Re: Pathfinder frozen

Kent N6WT
 

Dave

Several times.

Thanks
73
Kent
N6WT


On Wed, Jan 15, 2020 at 9:27 AM Gilbert Baron W0MN <w0mn00@...> wrote:

All I can say is good luck with event logs. They are really impossible to make sense of for most. You may see an event (maybe MANY) around the time of the freeze but understanding what it means is another matter.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Kent Olsen
Sent: Wednesday, January 15, 2020 10:13
To: DXLab@groups.io
Subject: Re: [DXLab] Pathfinder frozen

 

Dave 

 

What happens is, when Pathfinder starts it works fine when I click on a spot. After a while, if I try to scroll up or down in the window it will not move. I also cannot maximize or minimize the window. If I click on another spot the page will show the new information but it is still unable to move.

 

I have Windows Defender set to exclude all DXLabs folders. This is the only antimalware I use. If I am to look at the Windows Event Logs what should I look for??

 

Thanks

73

Kent

N6WT

 

 

On Wed, Jan 15, 2020 at 7:57 AM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I am noticing Pathfinder is frozen. I think I remember a post for a fix but I can't find it now??

+ I don't recall anyone every reporting this behavior. Pathfinder is a augmented instance of Internet Explorer; if it's truly frozen, my advice would be to reboot Windows. If it freezes again, I'd check the Windows Event Logs to see what happened at the point in time that Pathfinder froze. Interference from an incorrectly configured anti-malware application is another possibility.

       73,

              Dave, AA6YQ





--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop