Date   

SC and RBN

KU7Y <ku7y.cw@...>
 

Seems like every time I play with this program I find more things it will do!

I have the RBN going to SC and that's working fine. And the standard filters work right also.

But..... I'd like to limit the RBN spots to just one or two sites. WA7LNW and maybe N7TR. I **think** I can do that using SQL filters. Where can I find the info needed to so this?

To add more to the issue.... I want to keep all the other spots, so just need to filter the RBN, not the other ones. Not sure if that can be done or not.

Thanks for a fantastic group of programs.

OK, back in my hole,

Ron, KU7Y
SOWP 5545M
Arizona Outlaws Contest Club
Brenda, AZ (Winter)
Caldwell, ID (Summer)
ku7y@...
http://www.hatpinsandmore.com
KX3 #0062


DXKeeper 10.3.7 won't launch resolved

Chuck, WS1L
 

A complete check disk found and replaced some bad sectors. All now works
as it should.

A review of Event Viewer shows no 1005 errors in the Application Log until
today.

DXKeeper had no errorlog.txt, and Launcher had one with a single entry from
back in 2011.

I'll keep a careful eye on the hard drive, and start checking into
replacing it.

73 de Chuck, WS1L


--


===================
Chuck Chandler
chandlerusm@...
===================


Re: Winkey and <stop>

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 6:34 PM
To: dxlab@...
Subject: [dxlab] Re: Winkey and <stop>


Hi,
by using Winkeyer2 software, it sends "clrPTT" [N].

There is no clrPTT command mentioned in the Winkeyer2 (v23) datasheet. Do
you mean "PTT Off", which is <18><0> ?

73,

Dave, AA6YQ


Re: DXKeeper 10.3.7 won't launch

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 6:14 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper 10.3.7 won't launch


OK, the free space check found no issues. It is likely a good idea to
replace the hard drive. I have seen some RAM disks available - is anyone
using them?

I use a 160 GB Intel SSD as the C: drive on my laptop; it screams.

The process below got DXKeeper running as 10.3.7, just as it should.
Thanks!!

I have the Windows disk for WXP Pro, SP3 - my PC is a reconditioned Tiger
Direct IBM ThinkCentre, so there is a certificate of authenticity to match
the PC. Re-installing on a new HD should be doable.

What is the best way to make a full backup? Does the WXP backup utility
handle this or do I need something like Ghost? It's been years since I've
had to do this.

I have never relied on Windows backup. I used Ghost for several years,
but found it full of defects and user hostile; it may have improved since
then. I now use StorageCraft's ShadowProtect to backup all PCs to an
on-premises server (daily incrementals with one full backup each week); it's
easy to use and reliable. I use Mozy for continuous daily online backup.

73,

Dave, AA6YQ


Re: Winkey and <stop>

f6gcp
 

Hi,
I will have a look on this... "Hang" parameter could be the parameter I missed in WW. Currently I don't have the same bahaviour while running CW when WW is openned than running Winkey in standalone...
Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@...> wrote:

Hi Pat,

Then I think you just need to reduce your "Tail" setting, and increase
"Paddle Hang".

GL/73,

~iain / N6ML


On Sun, Aug 5, 2012 at 1:48 PM, f6gcp <f6gcp@...> wrote:



Hi Ian,

thanks on information. I have checked running Winkey2 software, and it
shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't
know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@> wrote:



On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is
quite
ok for CW operation using the keyer, and to avoid trcv to go to
receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as
set
to 500ms is a too long (the pile_up "TU" to confirm qso could be
missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the
PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to
immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


Re: reverse beacon network?

Dave AA6YQ
 

AA6YQ comment below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Sam Morgan
Sent: Sunday, August 05, 2012 6:14 PM
To: dxlab@...
Subject: [dxlab] reverse beacon network?


what host address and port do I use in spot collector to use reverse beacon
net?

Host Address: telnet.reversebeacon.net
Port: 7000
Usage: <http://www.dxlabsuite.com/RBN/index.htm>
73,

Dave, AA6YQ


Re: Winkey and <stop>

f6gcp
 

Hi,
by using Winkeyer2 software, it sends "clrPTT" [N].
73
Pat

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 5:45 AM
To: dxlab@...
Subject: [dxlab] Winkey and <stop>


Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Using the opcode "stop" (while running the winkey test software), the PTT is
immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?

What commands are sent to the WinKey when the "WinKey Test Software" is
directed to "stop"?

73,

Dave, AA6YQ


reverse beacon network?

Sam Morgan
 

what host address and port do I use in spot collector to use reverse beacon net?
--

GB & 73
K5OAI
Sam Morgan


Re: DXKeeper 10.3.7 won't launch

Chuck, WS1L
 

OK, the free space check found no issues. It is likely a good idea to
replace the hard drive. I have seen some RAM disks available - is anyone
using them?

The process below got DXKeeper running as 10.3.7, just as it should.
Thanks!!

I have the Windows disk for WXP Pro, SP3 - my PC is a reconditioned Tiger
Direct IBM ThinkCentre, so there is a certificate of authenticity to match
the PC. Re-installing on a new HD should be doable.

What is the best way to make a full backup? Does the WXP backup utility
handle this or do I need something like Ghost? It's been years since I've
had to do this.

73 de Chuck, WS1L


On Sun, Aug 5, 2012 at 3:41 PM, Dave AA6YQ <aa6yq@...> wrote:

**


If Chkdisk can't correct the damage to DXKeeper 10.3.7, then the procedure
below will get you a new DXKeeper1037.exe

Unless there's some other explanation for the low-level damage to your
files, you might consider replacing your hard drive. This would certainly
be
a good time to make -- and verify -- a full backup.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 4:34 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper 10.3.7 won't launch

OK, as soon as the check disk finishes I'll do that!

Thanks, Dave!!

On Sun, Aug 5, 2012 at 3:26 PM, Dave AA6YQ <aa6yq@...> wrote:

**


AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 9:59 AM
To: dxlab@...
Subject: [dxlab] DXKeeper 10.3.7 won't launch

Via Launcher it times out at 180 seconds, followed by the windows error
box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the
same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the
same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

If there's an errorlog.txt file in your Launcher and/or DXKeeper
folder,
please attach them to an email message and send them to

aa6yq (at) ambersoft.com

The most likely possibility is that your antivirus or firewall is
preventing DXKeeper 10.3.7 from starting; make sure these applications
consider DXKeeper "safe".

If that's not it, then in your DXKeeper folder,
1. delete DXKeeper1037.exe

2. make a copy of the file DXKeeper1032.exe and name this copy
DXKeeper.exe
(if you haven't done this already)

3. start the Launcher, and direct it to upgrade DXKeeper again

73,

Dave, AA6YQ


--

===================
Chuck Chandler
chandlerusm@...
===================

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2437/5179 - Release Date: 08/05/12




--


===================
Chuck Chandler
chandlerusm@...
===================


[Non-text portions of this message have been removed]


Re: LOTW/DXKeeper Station Location match

Alan Swinger
 

Yep; agree. If it does not work for anything New, will advise . . . and will be really befuddled!
Enjoy the Olympics and Good DX! - alan

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
alanswinger
Sent: Sunday, August 05, 2012 12:00 PM
To: dxlab@...
Subject: [dxlab] Re: LOTW/DXKeeper Station Location match


Dave - I did follow the LoTW Certif transfer insts, and had TQSL and TQSL
Cert saved on a DVD after I renewed them last yr. I also checked the
station_data files on both PCs and they were the same except for unique
computer user names. So, I Edited the Station Location file in TQSL Cert on
the new PC to make it is the same as the Old PC and the Station File, and
also made sure Keeper reflected the edit.
I uploaded all QSOs in Keeper since I put the new PC on line (7/5-8/5/12) to
LoTW this morning. LoTW confirmed receipt so I snch'd QSOs and QSLs, and got
the following message:
- LOTW OPerations: 4 QSLs processed; 4 Log entries updated, 0 errors. No new
confirmations of previously unconfirmed entity-bands or entity-modes.

I expected nothing new, so the message is correct from that aspect, and
appears that the upload and responses are correct. Also checked the LoTW
Sent Boxes and all show a Y and today's date.

Therefore, it appears that all is working properly. Other than receiving a
LoTW QSO confirmation, is there anything else to check?

That all sounds good, Alan, but the proof of the pudding will be when one
of the QSOs logged and uploaded from your new laptop gets confirmed via
LotW.

73,

Dave, AA6YQ


Updated eQSL AG and LotW Databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


Re: Winkey and <stop>

iain macdonnell - N6ML
 

Hi Pat,

Then I think you just need to reduce your "Tail" setting, and increase
"Paddle Hang".

GL/73,

~iain / N6ML

On Sun, Aug 5, 2012 at 1:48 PM, f6gcp <f6gcp@...> wrote:



Hi Ian,

thanks on information. I have checked running Winkey2 software, and it
shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't
know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@...> wrote:



On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is
quite
ok for CW operation using the keyer, and to avoid trcv to go to
receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as
set
to 500ms is a too long (the pile_up "TU" to confirm qso could be
missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the
PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to
immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


Re: Clublog

Richard B Drake
 

This happened once again and then I realized that eQSL uploads fail on the same QSO's as Clublog. Thus, I suspect that this is really an Internet connection failure which will happen from time to time. The Clublog error message indicating a dupe should probably be a "Failed connection" message instead..

73, Rich - W3ZJ

Dave AA6YQ wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Rich - W3ZJ
Sent: Sunday, August 05, 2012 11:24 AM
To: DXLab
Subject: [dxlab] Clublog


Two of my last three QSO's (D3AA on 15M CW and UN/UA4WHX on 17M CW) were
rejected by Clublog as Duplicates. I have never worked either of those
stations before on those bands/modes. I later did a manual upload to
Clublog and those were accepted as two "new" QSO's:


Dear W3ZJ,

Congratulations - your ADIF file has been imported without warnings. A total of 2 new QSOs have been uploaded.

* Software: DXKEEPER
* File name: ClubLogUpload.ADI (488 B)
* New QSOs: 2

I saw this once a couple of days ago also but didn't report it. Who is
messing up here DXLab or Clublog?


If there are no previous QSOs in your log and the ClubLogUpload.ADI file created by DXKeeper doesn't contain duplicates, then I don't see how it can be a DXKeeper problem.
73,

Dave, AA6YQ


Re: request: special callsign in SC

Dave AA6YQ
 

+++ AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
iain macdonnell - N6ML
Sent: Saturday, August 04, 2012 4:23 PM
To: dxlab@...
Subject: Re: [dxlab] Re: request: special callsign in SC


On Sat, Aug 4, 2012 at 12:45 PM, Dave AA6YQ <aa6yq@...> wrote:



AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
iain macdonnell - N6ML
Sent: Saturday, August 04, 2012 3:27 PM
To: dxlab@...
Subject: Re: [dxlab] Re: request: special callsign in SC

snip<

Dave, I wonder if there's a case for a built-in "SpecialNeed" tag that
gets
included in the "stock" <NEEDFILTER> ?

I don't yet understand what you're suggesting, Iain. Please elaborate.
I was thinking that <NEEDFILTER> could be augmented to include an
expression something like [or Tags like '*SpecialNeed*'], so that
users could add Special Callsigns with that tag, and have matching
spot db entries displayed after clicking the "Need" button, without
requiring a custom SQL filter.

+++ Thanks, Iain. I've added this to SpotCollector's enhancement list.

73,

Dave, AA6YQ


Re: Winkey and <stop>

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 5:45 AM
To: dxlab@...
Subject: [dxlab] Winkey and <stop>


Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Using the opcode "stop" (while running the winkey test software), the PTT is
immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?

What commands are sent to the WinKey when the "WinKey Test Software" is
directed to "stop"?

73,

Dave, AA6YQ


Re: Winkey and <stop>

f6gcp
 

Hi Ian,

thanks on information. I have checked running Winkey2 software, and it shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@...> wrote:

On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


Re: Clublog

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Rich - W3ZJ
Sent: Sunday, August 05, 2012 11:24 AM
To: DXLab
Subject: [dxlab] Clublog


Two of my last three QSO's (D3AA on 15M CW and UN/UA4WHX on 17M CW) were
rejected by Clublog as Duplicates. I have never worked either of those
stations before on those bands/modes. I later did a manual upload to
Clublog and those were accepted as two "new" QSO's:

Dear W3ZJ,

Congratulations - your ADIF file has been imported without warnings. A total of 2 new QSOs have been uploaded.

* Software: DXKEEPER
* File name: ClubLogUpload.ADI (488 B)
* New QSOs: 2

I saw this once a couple of days ago also but didn't report it. Who is
messing up here DXLab or Clublog?

If there are no previous QSOs in your log and the ClubLogUpload.ADI file created by DXKeeper doesn't contain duplicates, then I don't see how it can be a DXKeeper problem.
73,

Dave, AA6YQ


Re: DXKeeper 10.3.7 won't launch

Dave AA6YQ
 

If Chkdisk can't correct the damage to DXKeeper 10.3.7, then the procedure
below will get you a new DXKeeper1037.exe

Unless there's some other explanation for the low-level damage to your
files, you might consider replacing your hard drive. This would certainly be
a good time to make -- and verify -- a full backup.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 4:34 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper 10.3.7 won't launch


OK, as soon as the check disk finishes I'll do that!

Thanks, Dave!!

On Sun, Aug 5, 2012 at 3:26 PM, Dave AA6YQ <aa6yq@...> wrote:

**


AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 9:59 AM
To: dxlab@...
Subject: [dxlab] DXKeeper 10.3.7 won't launch

Via Launcher it times out at 180 seconds, followed by the windows error
box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the
same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the
same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

If there's an errorlog.txt file in your Launcher and/or DXKeeper
folder,
please attach them to an email message and send them to

aa6yq (at) ambersoft.com

The most likely possibility is that your antivirus or firewall is
preventing DXKeeper 10.3.7 from starting; make sure these applications
consider DXKeeper "safe".

If that's not it, then in your DXKeeper folder,
1. delete DXKeeper1037.exe

2. make a copy of the file DXKeeper1032.exe and name this copy
DXKeeper.exe
(if you haven't done this already)

3. start the Launcher, and direct it to upgrade DXKeeper again

73,

Dave, AA6YQ




--


===================
Chuck Chandler
chandlerusm@...
===================






------------------------------------

Yahoo! Groups Links



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1424 / Virus Database: 2437/5179 - Release Date: 08/05/12


Re: Update to DXKeeper 10.3.7 won't launch

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 4:33 PM
To: dxlab@...
Subject: [dxlab] Update to DXKeeper 10.3.7 won't launch


I posted earlier that DXK 10.3.7 won't launch. I've done some more
checking.

First off, I've been away and had the radio PC off. I turned it on
Saturday and ran N1MM Logger to play a bit in the NAQP. This morning was
my first try to launch DXLabs, except I did have Spot Collector running
before the contest, as well as after.

Here's a list of what I've done so far.......

I determined that Google Chrome won't launch for some reason. It simply
keeps popping up '...needs to close' boxes and never launches.

I did another re-boot, and then realized the GMail notifier was running, so
I terminated that. Chrome still won't launch.

Next step: remove Chrome using Add/Remove in Control Panel. The radio PC
rarely, if ever, browses the web anyways. Followed by a re-boot.

DXKeeper 10.3.2 launches OK from the icon. 10.3.7 again fails with the
same error box. This time IE brought up a website saying the error was on
the hard drive. Using Eventviewer I got the event description:

Windows cannot access the file ...DXKeeper 1037 for one of the following
reasons:
Problem with network connection
Problem with disk
Problem with storage drivers
Disk is missing.

Checking the hard drive properties showed plenty of free space... 21 GB
used, 444 GB free. Next step is to error check and repair the disk.
So far, Windows has replaced bad clusters in the file
DXView/Databases/LOTW.mdb, in DXKeeper.exe, and in several other places.

Still working on the free space, which will take a while. I'll update when
done.....

Best of luck on the recovery, Chuck (fingers crossed here!). Does the
Windows event log indicate any history of disk errors, or was this a
one-time event?

73,

Dave, AA6YQ


Re: DXKeeper 10.3.7 won't launch

Chuck, WS1L
 

OK, as soon as the check disk finishes I'll do that!

Thanks, Dave!!

On Sun, Aug 5, 2012 at 3:26 PM, Dave AA6YQ <aa6yq@...> wrote:

**


AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Chuck Chandler
Sent: Sunday, August 05, 2012 9:59 AM
To: dxlab@...
Subject: [dxlab] DXKeeper 10.3.7 won't launch

Via Launcher it times out at 180 seconds, followed by the windows error box
'DXKeeper has encountered an error and needs to close'. After that I
re-booted the PC, same behavior.

Double-clicking the DXKeeper.exe from Windows Explorer brings only the same
error box.

Double-clicking the 1037 version from Windows Explorer brings only the same
error box.

Double-clicking the 1032 version launches normally.

Also, sometimes the error box reads "Google Chrome has encountered an
error..." although Chrome is not running.

That is in addition to the DXKeeper error, not in place of.

For now, I've pointed the Launcher to version 10.3.2, and all is well.

If there's an errorlog.txt file in your Launcher and/or DXKeeper folder,
please attach them to an email message and send them to

aa6yq (at) ambersoft.com

The most likely possibility is that your antivirus or firewall is
preventing DXKeeper 10.3.7 from starting; make sure these applications
consider DXKeeper "safe".

If that's not it, then in your DXKeeper folder,
1. delete DXKeeper1037.exe

2. make a copy of the file DXKeeper1032.exe and name this copy DXKeeper.exe
(if you haven't done this already)

3. start the Launcher, and direct it to upgrade DXKeeper again

73,

Dave, AA6YQ




--


===================
Chuck Chandler
chandlerusm@...
===================


[Non-text portions of this message have been removed]

100341 - 100360 of 209546