Date   
Re: Key CW with CIV CAT

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 12:02 PM
To: dxlab@...
Subject: [dxlab] Key CW with CIV CAT

Is it possible to key the TS870 using the KY commands and WinWarbler.

Yes.
That is CW operation without any RS232 port and without any other hardware such as Winkeyer?

Correct.
If so can someone point me to the documentation to set this up. Thanks.

See the 4th bullet point in step 1.f of
<http://www.dxlabsuite.com/dxlabwiki/ConfigureCW>


By the way, "CI-V" refers to the bus used in Icom (and some old TenTec) radios to convey commands and responses.
73,

Dave, AA6YQ

Re: My own call in SpotCollector

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 11:44 AM
To: dxlab@...
Subject: [dxlab] My own call in SpotCollector

I cannot recall ever seeing my call sign showing up in the SC window after I call CQ using CW (or any mode for that matter). Does SC filter my own call out. I can do a sh/dx n6wt, in command line in the cluster window, to see that I have been spotted (by the rbn).

No, SpotCollector does not hide or remove Spot Database Entries for your callsign.
Perhaps the other filtering you have enabled is hiding your callsign. Depressing the CTRL key while clicking the Filter panel's X button will remove all filtering. Alternatively, typing
Callsign='N6WT'

into the Filter panel textbox and striking CTRL-S will show all Spot Database Entries for your callsign.
73,

Dave, AA6YQ

Re: DXKeeper setup Club Contest

ART SEARLE <w2nra@...>
 

Thank you, Dave, I just noticed the 16 character limit so I will try the Log QSOs Tab instead of the Capture window

73, Art, W2NRA
DXCC CW Honor Roll

On Nov 10, 2017, at 01:38 PM, "'Dave AA6YQ' aa6yq@... [dxlab]" wrote:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 9:49 AM
To: DXLab Yahoo Group
Subject: [dxlab] DXKeeper setup Club Contest

I'm trying to set up a Club Contest in DXKeeper. I have 2 questions:

1. Where in the Capture window do the (non-searial#) reports go. There is no sequential serial number so I assume not in the "TX#".

>>>Your assumption is incorrect. As documented in

<http://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

>>>TX# records "transmit serial number or exchange". Similarly, RX# records "receive serial number or exchange". Each can record up to 16 alphanumeric characters.

But there is no field in the Capture window that goes to the "rx info" field in DXKeeper.

>>>If you want to log "rx info" with each QSO, you'll have to use the Main window's "Log QSOs" tab with the Contest panel visible. Be sure to enable the "Optimize for realtime QSO entry" option.

2. I placed my TX Exchange in the "TX Exchange" field in the Contest setup but it doesn't carry through to the "tx info" field in DXKeeper's Contest panel.

>>>That's correct. As is shown in

<http://www.dxlabsuite.com/dxkeeper/Help/Contesting.htm>

>>>the "TX Exchange" box on the Configuration window's Contest tab is used to record contest-specific information to enable correct Cabrillo generation.

In Contest setup I'm guessing, instead of the above, I should use the "TX serial#" and "RX serial#" fields and not check Increment "TX Serial#". Right? I think that would work for me.

>>>Based on what you've described, using the Capture window's TX# and RX# items seems reasonable. If the exchange is not an incrementing serial number, then it would not be appropriate to enable the "Increment TX Serial#" option.

73,

Dave, AA6YQ

73, Art, W2NRA
DXCC CW Honor Roll
SKCC #11634Sx5

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. http://www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Commander rig control with WSJT-X locking up

Björn Ekelund, SM7IUN
 

Bill,

WSJT-X does not quite seem to relinquish control entirely when disabling "monitor" after all. 

If I click "stop" to disable "monitor" and then double-click on a spot with split, WSJT-X issues an rig control error popup after a little while.
(I'm using "fake it" for radio control since when using "split" Commander and WSJT-X sometimes ends up having different opinions what VFO B is).
Disabling Split and clicking "Retry" on the popup makes WSJT-X take control over the radio again. Although "monitor" is still off.

Disabling "monitor", Ignoring the popup and clicking on spots I can still get the communication between Commander and WSJT-X to lock up.
Perhaps because I am using "fake it"?

Yes, I know this is a quite niche use case...

73,

Björn SM7IUN




2017-11-07 21:40 GMT+01:00 Björn Ekelund <bjorn@...>:

Thanks Bill,

easy as pie. Much appreciated.

73,

Björn SM7IUN


2017-11-07 21:36 GMT+01:00 bill.8@... [dxlab] <dxlab@...>:
 

HI Bjorn,

WSJT-X and Commander will get into a disagreement on the rig's mode when you use SpotCollector to QSY to a spot. WSJT-X will relinquish control if you click the "Monitor" off before assuming control elsewhere. You can also set a WSJT-X option to have it return to where it was when you click "Monitor" back on again.

73
Bill
G4WJS.



Re: Key CW with CIV CAT

Gilbert Baron W0MN
 

Thanks much for the p[pointer. I should have known that 😊 Now I can use CW until I get my WinKeyer USB and I will end up with only one USB-RS232.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W

 

From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 12:01
To: dxlab
Subject: Re: [dxlab] Key CW with CIV CAT

 

 

On Fri, Nov 10, 2017 at 9:02 AM, 'Gilbert Baron' w0mn00@...
[dxlab] <dxlab@...> wrote:
>
>
>
> Is it possible to key the TS870 using the KY commands and WinWarbler. That is CW operation without any RS232 port and without any other hardware such as Winkeyer? If so can someone point me to the documentation to set this up. Thanks.

http://www.dxlabsuite.com/dxlabwiki/CWConnection

73,

~iain / N6ML

Re: DXKeeper setup Club Contest

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 9:49 AM
To: DXLab Yahoo Group
Subject: [dxlab] DXKeeper setup Club Contest

I'm trying to set up a Club Contest in DXKeeper. I have 2 questions:


1. Where in the Capture window do the (non-searial#) reports go. There is no sequential serial number so I assume not in the "TX#".

Your assumption is incorrect. As documented in
<http://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

TX# records "transmit serial number or exchange". Similarly, RX# records "receive serial number or exchange". Each can record up to 16 alphanumeric characters.
But there is no field in the Capture window that goes to the "rx info" field in DXKeeper.

If you want to log "rx info" with each QSO, you'll have to use the Main window's "Log QSOs" tab with the Contest panel visible. Be sure to enable the "Optimize for realtime QSO entry" option.

2. I placed my TX Exchange in the "TX Exchange" field in the Contest setup but it doesn't carry through to the "tx info" field in DXKeeper's Contest panel.

That's correct. As is shown in
<http://www.dxlabsuite.com/dxkeeper/Help/Contesting.htm>

the "TX Exchange" box on the Configuration window's Contest tab is used to record contest-specific information to enable correct Cabrillo generation.

In Contest setup I'm guessing, instead of the above, I should use the "TX serial#" and "RX serial#" fields and not check Increment "TX Serial#". Right? I think that would work for me.

Based on what you've described, using the Capture window's TX# and RX# items seems reasonable. If the exchange is not an incrementing serial number, then it would not be appropriate to enable the "Increment TX Serial#" option.
73,

Dave, AA6YQ


73, Art, W2NRA
DXCC CW Honor Roll
SKCC #11634Sx5




<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Hanover County, NC

ART SEARLE <w2nra@...>
 

It's New Hanover County

73, Art, W2NRA
DXCC CW Honor Roll
SKCC #11634Sx5

On Nov 10, 2017, at 01:18 PM, "Bill Billingsley billingsley2629@... [dxlab]"

 

Above county in not listed in the NC county pull down on the capture window.  Internet says that it exists. Is it a combined area now?

Bill, N5IR


Hanover County, NC

Bill N5IR
 

Above county in not listed in the NC county pull down on the capture window.  Internet says that it exists. Is it a combined area now?

Bill, N5IR

Re: Key CW with CIV CAT

iain macdonnell - N6ML
 

On Fri, Nov 10, 2017 at 9:02 AM, 'Gilbert Baron' w0mn00@...
[dxlab] <dxlab@...> wrote:



Is it possible to key the TS870 using the KY commands and WinWarbler. That is CW operation without any RS232 port and without any other hardware such as Winkeyer? If so can someone point me to the documentation to set this up. Thanks.
http://www.dxlabsuite.com/dxlabwiki/CWConnection

73,

~iain / N6ML

Re: My own call in SpotCollector

Kent Olsen
 

Art

Sorry, yes it does.

Not sure why it does now.

Thanks
73
Kent
N6WT

On Fri, Nov 10, 2017 at 9:53 AM, Kent Olsen <kilo6dko@...> wrote:
Art

No it does not.

Thanks
73
Kent
N6WT

On Fri, Nov 10, 2017 at 9:44 AM, ART SEARLE w2nra@... [dxlab] <dxlab@...> wrote:
 

After calling CQ type your call in SpotCollector’s Filter-Text-Box and hit the Call button.  Do they show up then?

73, Art, W2NRA
DXCC CW Honor Roll


On Nov 10, 2017, at 11:43 AM, Kent Olsen kilo6dko@... [dxlab] <dxlab@...> wrote:

 

I cannot recall ever seeing my call sign showing up in the SC window after I call CQ using CW (or any mode for that matter). Does SC filter my own call out. I can do a sh/dx n6wt, in command line in the cluster window, to see that I have been spotted (by the rbn).

Thanks
73
Kent
N6WT



Re: My own call in SpotCollector

Kent Olsen
 

Art

No it does not.

Thanks
73
Kent
N6WT

On Fri, Nov 10, 2017 at 9:44 AM, ART SEARLE w2nra@... [dxlab] <dxlab@...> wrote:
 

After calling CQ type your call in SpotCollector’s Filter-Text-Box and hit the Call button.  Do they show up then?

73, Art, W2NRA
DXCC CW Honor Roll


On Nov 10, 2017, at 11:43 AM, Kent Olsen kilo6dko@... [dxlab] <dxlab@...> wrote:

 

I cannot recall ever seeing my call sign showing up in the SC window after I call CQ using CW (or any mode for that matter). Does SC filter my own call out. I can do a sh/dx n6wt, in command line in the cluster window, to see that I have been spotted (by the rbn).

Thanks
73
Kent
N6WT


Re: My own call in SpotCollector

ART SEARLE <w2nra@...>
 

After calling CQ type your call in SpotCollector’s Filter-Text-Box and hit the Call button.  Do they show up then?

73, Art, W2NRA
DXCC CW Honor Roll


On Nov 10, 2017, at 11:43 AM, Kent Olsen kilo6dko@... [dxlab] <dxlab@...> wrote:

 

I cannot recall ever seeing my call sign showing up in the SC window after I call CQ using CW (or any mode for that matter). Does SC filter my own call out. I can do a sh/dx n6wt, in command line in the cluster window, to see that I have been spotted (by the rbn).

Thanks
73
Kent
N6WT

Key CW with CIV CAT

Gilbert Baron W0MN
 

Is it possible to key the TS870 using the KY commands and WinWarbler. That is CW operation without any RS232 port and without any other hardware such as Winkeyer? If so can someone point me to the documentation to set this up. Thanks.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W

 

My own call in SpotCollector

Kent Olsen
 

I cannot recall ever seeing my call sign showing up in the SC window after I call CQ using CW (or any mode for that matter). Does SC filter my own call out. I can do a sh/dx n6wt, in command line in the cluster window, to see that I have been spotted (by the rbn).

Thanks
73
Kent
N6WT

Virtual ports

Steve - N3SL
 

Apologies in advance, as I know this isn't a DXLab problem, but the expertise with this group is notable....


I've just discovered on my Win10 machine that I've lost "recognition" of my virtual ports.  Not sure when it happened, as I've not used them (rig control, RTTY) for a couple of weeks.  And I say "recognition" because within MicroHam Device Router (which I've used for years), I can still query and control my rig (COM3) and key it in CW (COM4), and key it in RTTY (COM5).  However, neither MMTTY nor DXLab Commander even see these ports any longer.  


Any ideas?  I've done reinstall of Device Router, unplugged and reset USB cables, deleted all my JT software (thought it may have been the problem).   One other thing - and not sure if it's "normal" with Win10 - in the Win10 Device Manager I don't have ANY ports listed - i.e. the "Ports" option isn't even there.


Thanks in advance for any assistance!


Steve

DXKeeper setup Club Contest

ART SEARLE <w2nra@...>
 

I'm trying to set up a Club Contest in DXKeeper.  I have 2 questions:

1. Where in the Capture window do the (non-searial#) reports go.  There is no sequential serial number so I assume not in the "TX#".  But there is no field in the Capture window that goes to the "rx info" field in DXKeeper.

2. I placed my TX Exchange in the "TX Exchange" field in the Contest setup but it doesn't carry through to the "tx info" field in DXKeeper's Contest panel.

In Contest setup I'm guessing, instead of the above, I should use the "TX serial#" and "RX serial#" fields and not check Increment "TX Serial#".  Right?  I think that would work for me.

73, Art, W2NRA
DXCC CW Honor Roll
SKCC #11634Sx5

Re: Interaction between apps?

Ed Douglass
 

You are welcome.  Thanks for changing the text, making it clearer for neophytes like me.


On Thu, Nov 9, 2017 at 11:30 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 12:14 AM
To: dxlab@...
Subject: Re: [dxlab] Interaction between apps?

Dave, AA6YQ, says the bridge program that runs between MRP40 and WinWarbler must be "Run as Administrator." See his help page at www.dxlabsuite.com/MRP_DXLab/index.htm <http://www.dxlabsuite.com/MRP_DXLab/index.htm> The executable file name is MRP_DXLab102. It is installed in the WinWarbler folder.

Dave also told me in an e-mail that a program run as administrator will not interoperate with another program not running in administrator mode. A local computer technician confirmed Dave's advice. It seemed logical to me therefore that WinWarbler and MRP40 would have to be run in administrator mode.

On my computer DXLab Suite is installed in C:\. MRP40 is installed in C:\Program Files(x86)\HamRadioSoftware\MRP40 Morse Decoder V66\MRP40v62. I think this is where the program installs itself or where I was advised to install it.

I was not fixated on running the DXLab Suite in administrator mode. I just wanted to see the decoded CW from MRP40 flow into the receive pane of WinWarbler. That's all. It wasn't happening so I asked Dave.

I've run some tests as Dave asked.

I made sure that MRP40, MRP_DXLaab102, and WinWarbler were NOT being run as administrator. On DXLab Suite startup, there were two reports from the MRP-DXKeeper Gateway: MRP Gateway status: not responding and WW status: connected. CW decode was NOT flowing into WW.

I ran MRP-DXLab102 (only) in administrator mode. Again, two reports from the MRP-DXKeeper Gateway: MRP status: connected to MRP40 and WW status: connected. Decoded CW from MRP40 now flowing into the receive pane of WW. Furthermore, I can click on a call sign in the WW receive pane and the call sign appears in the QSO Info Call window of WW and in the Filter window of DXKeeper.

I haven't put WW or MRP40 into administrator mode. It appears that I am getting what I want with just the bridge program in this mode.

So Dave is right that the bridge program must be run in administrator mode but not right that other (DXLab) programs that interoperate with the bridge program have to be run as administrator.

>>>WinWarbler is the only DXLab application that interacts with the Gateway. I have updated

<http://www.dxlabsuite.com/MRP_DXLab/index.htm>

>>>to say

-----------------
The Gateway must be started with "Run as Administrator", or it will be unable to connect with your MRP40 application; this requirement does not make it necessary to start WinWarbler with "Run as Administrator".
-----------------

I thank Dave, W6DE, for making me aware that there is difference between running my computer as the administrator and running a program as administrator. And, yes, I was in over my head.

>>>And yet you eliminated the uncertainty surrounding the correct use of the Gateway. Thanks for running this to ground, Ed!

73,

Dave, AA6YQ


Re: Interaction between apps?

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 12:14 AM
To: dxlab@...
Subject: Re: [dxlab] Interaction between apps?



Dave, AA6YQ, says the bridge program that runs between MRP40 and WinWarbler must be "Run as Administrator." See his help page at www.dxlabsuite.com/MRP_DXLab/index.htm <http://www.dxlabsuite.com/MRP_DXLab/index.htm> The executable file name is MRP_DXLab102. It is installed in the WinWarbler folder.

Dave also told me in an e-mail that a program run as administrator will not interoperate with another program not running in administrator mode. A local computer technician confirmed Dave's advice. It seemed logical to me therefore that WinWarbler and MRP40 would have to be run in administrator mode.

On my computer DXLab Suite is installed in C:&#92;. MRP40 is installed in C:&#92;Program Files(x86)&#92;HamRadioSoftware&#92;MRP40 Morse Decoder V66&#92;MRP40v62. I think this is where the program installs itself or where I was advised to install it.

I was not fixated on running the DXLab Suite in administrator mode. I just wanted to see the decoded CW from MRP40 flow into the receive pane of WinWarbler. That's all. It wasn't happening so I asked Dave.

I've run some tests as Dave asked.

I made sure that MRP40, MRP_DXLaab102, and WinWarbler were NOT being run as administrator. On DXLab Suite startup, there were two reports from the MRP-DXKeeper Gateway: MRP Gateway status: not responding and WW status: connected. CW decode was NOT flowing into WW.

I ran MRP-DXLab102 (only) in administrator mode. Again, two reports from the MRP-DXKeeper Gateway: MRP status: connected to MRP40 and WW status: connected. Decoded CW from MRP40 now flowing into the receive pane of WW. Furthermore, I can click on a call sign in the WW receive pane and the call sign appears in the QSO Info Call window of WW and in the Filter window of DXKeeper.

I haven't put WW or MRP40 into administrator mode. It appears that I am getting what I want with just the bridge program in this mode.

So Dave is right that the bridge program must be run in administrator mode but not right that other (DXLab) programs that interoperate with the bridge program have to be run as administrator.

WinWarbler is the only DXLab application that interacts with the Gateway. I have updated
<http://www.dxlabsuite.com/MRP_DXLab/index.htm>

to say
-----------------
The Gateway must be started with "Run as Administrator", or it will be unable to connect with your MRP40 application; this requirement does not make it necessary to start WinWarbler with "Run as Administrator".
-----------------

I thank Dave, W6DE, for making me aware that there is difference between running my computer as the administrator and running a program as administrator. And, yes, I was in over my head.

And yet you eliminated the uncertainty surrounding the correct use of the Gateway. Thanks for running this to ground, Ed!
73,

Dave, AA6YQ

Re: Interaction between apps?

Ed Douglass
 

Dave, AA6YQ, says the bridge program that runs between MRP40 and WinWarbler must be "Run as Administrator."  See his help page at www.dxlabsuite.com/MRP_DXLab/index.htm  The executable file name is MRP_DXLab102.  It is installed in the WinWarbler folder.

Dave also told me in an e-mail that a program run as administrator will not interoperate with another program not running in administrator mode.  A local computer technician confirmed Dave's advice.  It seemed logical to me therefore that WinWarbler and MRP40 would have to be run in administrator mode.  

On my computer DXLab Suite is installed in C:\.   MRP40 is installed in C:\Program Files(x86)\HamRadioSoftware\MRP40 Morse Decoder V66\MRP40v62.  I think this is where the program installs itself or where I was advised to install it.

I was not fixated on running the DXLab Suite in administrator mode.  I just wanted to see the decoded CW from MRP40 flow into the receive pane of WinWarbler.  That's all.  It wasn't happening so I asked Dave.

I've run some tests as Dave asked. 

I made sure that MRP40, MRP_DXLaab102, and WinWarbler were NOT being run as administrator.  On DXLab Suite startup, there were two reports from the MRP-DXKeeper Gateway:  MRP Gateway status:  not responding and  WW status: connected.  CW decode was NOT flowing into WW.

I ran MRP-DXLab102 (only) in administrator mode.   Again, two reports from the MRP-DXKeeper Gateway:  MRP status:  connected to MRP40 and WW status:  connected.  Decoded CW from MRP40 now flowing into the receive pane of WW.  Furthermore, I can click on a call sign in the WW receive pane and the call sign appears in the QSO Info Call window of WW and in the Filter window of DXKeeper.

I haven't put WW or MRP40 into administrator mode.  It appears that I am getting what I want with just the bridge program in this mode.

So Dave is right that the bridge program must be run in administrator mode but not right that other (DXLab) programs that interoperate with the bridge program have to be run as administrator.

I thank Dave, W6DE, for making me aware that there is difference between running my computer as the administrator and running a program as administrator.  And, yes, I was in over my head.

I hope Joe, W4TV, is relaxing, knowing that I am not running any of the DXLabSuite apps in administrator mode. 

Thanks for the help.

Ed, AA9OZ 
 



On Thu, Nov 9, 2017 at 11:32 AM, 'w6de' w6de@... [dxlab] <dxlab@...> wrote:
 

Art, this is a private reply.

I only posted that reply because it is clear Ed is over his head in computer management.  Not necessarily because the program requires it.  He seems fixated on the need to run with Administrative privileges.   I’m still not sure he understands the difference between running the installer with admin privileges and running with admin privileges.  I chose to not do the work you did in looking up the mrp40 needs—too many users already depending on others to do their learning for them.

 

Best Regards, Dave, W6DE

 

From: dxlab@... [mailto:dxlab@...]
Sent: 09 November, 2017 15:50


To: dxlab@...
Subject: Re: [dxlab] Interaction between apps?

 




Hi Dave, W6DE,

 

I found that hard to believe, so I went to the website.  It clearly says it is needed only for Vista.  Anyone still running Microsoft Vista?

 

73, Art, W2NRA


On Nov 09, 2017, at 10:32 AM, "'w6de' w6de@... [dxlab]" <dxlab@...> wrote:

 

Perhaps MRP40 only needs to installed with administrator privileges.  To do install with Administrator privileges right click the INSTALLER executable and select “Run as administrator.”  This will allow registration of all components necessary to run (thus resolving potential permission issues).

 

Dave, w6de

 

From: dxlab@... [mailto:dxlab@...]
Sent: 09 November, 2017 05:26
To: dxlab@...
Subject: Re: [dxlab] Interaction between apps?

 



I will take away the admin privileges from WW and see if decoded CW comes from MRP40.  Tomorrow.

 

I will ask Norbert Pieper.


On Nov 8, 2017, at 10:59 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Wednesday, November 08, 2017 11:46 PM
To: dxlab@...
Subject: Re: [dxlab] Interaction between apps?

OK, good. So only WW needs to be Run as Administrator because the bridge program between MRP40 and WW has to be run in administrative mode. Is this correct? It seems to be correct because decoded CW now flows into the receive screen of WW.

>>>I suggest that you try not starting WinWarbler with "Run as Administrator'; does WinWarbler still display decoded CW from MRP40 by way of the Gateway?

Does MRP40 have to be run in administrative mode also?

>>>I don't know; I suggest that you ask its author.

73,

Dave, AA6YQ





 

 

 





Re: WinWarbler Launches and then exits.. >>>REPLY

Dave AA6YQ
 

That means one of the applications that Windows starts automatically when booted normally is interfering with WinWarbler's ability to send an "I'm alive" message to the Launcher. When you boot Windows into "Safe mode with networking", no applications are automatically started, so WinWarbler operates unimpeded.

The most likely culprit is your firewall or an anti-malware application that is not configured to consider WinWarbler to be "safe".

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, November 09, 2017 11:56 PM
To: dxlab@...
Subject: Re: [dxlab] WinWarbler Launches and then exits.. >>>REPLY



Winwarbler opens and stays showing green in Launcher.
Left WW open for several minutes to see if any 180 second fail to load message might apperar. None did.

During WW start, there were two error messages:
First: "Error while opening CW serial port 8002 invalid port number"
Second: Had t do with the sound card...did not copy the exact wording.
Neither seemed to effect the start of WW,.


Edward Jahncke (N5KGV)
Vice-President-DDXA
(H) (985) 892-4797
(C) (985) 400-4028

On 11/10/2017 04:20, 'Dave AA6YQ' @AA6YQ [dxlab] wrote:




>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Thursday, November 09, 2017 10:00 PM
To: dxlab@...
Subject: Re: [dxlab] WinWarbler Launches and then exits..

Correct! Launcher indicates that all Modules (when started) are running except WinWarbler.

>>>Please do the following:

1. reboot Windows into "Safe Mode with Networking"

2. start the Launcher

3. direct the Launcher to start WinWarbler

>>>What happens?

73,

Dave, AA6YQ








<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>