Date   

WSJT-X slows Patfinder launc

Mark
 

I find that if wsjt-x and jtalert are running, Pathfinder can take a very, very long time to launch.  I have 32G of RAM, an SSD and a fast i7 processor.  OS is win 10.

When ft8 stuff is not running, Pathfinder loads normally.

73,

Mark, K6FG


Re: Prop View Error messages

W0MU
 

Sent earlier today.


Re: QSL msg in QSL queue for LotW - SOLVED

Carlo - IK2RPE
 

Dave, NO messages are present there.
After several other checks I discovered that being the QSOs imported from JTAlert and WSJT-X the message was coming from JTAlert "QSL message" window that keeped it. Cancelling it there everything is now OK.

73

Carlo IK2RPE

-----Messaggio originale-----
Da: DXLab@groups.io <DXLab@groups.io> Per conto di Dave AA6YQ
Inviato: domenica 12 gennaio 2020 18:50
A: DXLab@groups.io
Oggetto: Re: [DXLab] QSL msg in QSL queue for LotW

+ AA6YQ comments below

In DxKeeper/QSL when I click "Add Requested" ONLY for LotW (NOT for eQSL) in the QSOs to upload to LotW, in the "QSL msg" field a message appears that I used once but that I DO NOT want is becoming a default one. I know that I can edit it, in the QSO and cancel it, before doing the upload, but I wish to cancel this message as a default.
I have not found **where** to intervene (it is for example not in the capture window).

+ the "Default QSL Message" is selected or specified on the Configuration window's Defaults tab.

73,

Dave, AA6YQ


Re: Hi new to dxlab suite I've tried several installs.

K7OI-Mark
 

Hello Dave
Thank You

I factory reset my HP laptop after saving personal stuff to a 2T drive.
I then reinstalled DxLabs Launcher and then each app from there and I'm extremely amazed by the functionality now.


I'm sure your laughing. 73's

K7OI Mark 


Re: Prop View Error messages

Dave AA6YQ
 

+ AA6YQ comments below

On Mon, Jan 13, 2020 at 08:56 PM, W0MU wrote:

No Errorlog.
+ OK. Please make a screen shot showing the PropView error message, attach the screen shot to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

      73,

             Dave, AA6YQ


Re: Prop View Error messages

W0MU
 

No Errorlog.


Re: Prop View Error messages

Dave AA6YQ
 

+ AA6YQ comments below

When PV loads I get an error message that the resource is not available. If I click on either the current or forecast button I get the same error. If I enter config and go to those sites they come back with the proper pages and text.

+ Is there an errorlog.txt file in your PropView folder?

+ If so, please attach it to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Prop View Error messages

W0MU
 

When PV loads I get an error message that the resource is not available.  If I click on either the current or forecast button I get the same error.  If I enter config and go to those sites they come back with the proper pages and text. 


Re: Clublog errors

BILL KENNAMER
 

Some of those errors shown are correctly classified as errors.

On Monday, January 13, 2020, 5:52 PM, Jim Wysocki <wysocki1@...> 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

On 1/13/2020 1:51 PM, Gilbert Baron W0MN wrote:
>
> Interesting and probably not important as these are very old.
> Strangely though Clublog calls them broken but DXKEEPER does not. They
> are either so old or not QSLed that I think it best to simply ignore
> or delete from log.
>
> I am not sure why I even bother with CLUBLOG. I just thought I would
> upload in case it is a help to someone.
>
> Below is what I got from them.
>
> Dear W0MN,
>
> While processing your ADIF file for Club Log, the following possible
> problems were detected. Your log may be correct, but if necessary you
> can resolve these problems and create a new ADIF. If you make changes,
> it's recommended that on your next upload you use the option to clear
> your existing log, to avoid leaving prior records in Club Log.
>
> If you would like to discuss these problems, then please open a
> discussion on the reflector, or reply to this email to ask the
> volunteer team for help. You can disable these emails from the
> Settings page if you prefer.
>
> Google Groups Reflector: https://groups.google.com/group/clublog
>
> Information on DXCC mappings:
> https://clublog.freshdesk.com/solution/categories/59801
>
> Ask for help from the volunteer team: https://clublog.freshdesk.com/
>
> 73 de Michael G7VJR
>
> * Software: DXKEEPER
>
> * File name: ClubLogUpload.ADI (923.04 KB)
>
> * New QSOs: 3,693
>
> Callsign: VK9      Date: 1970-09-28 00:00:00          Band:
> 20              QSL: Yes
>
> VK9 is an invalid QSO, either under the ARRL DXCC rules or because it
> is outside the known dates of a valid operation. Club Log is storing
> this QSO, but marking it as invalid. For more information, please see
> http://clublog.freshdesk.com/solution/articles/53820-invalid-mappings
>
> Note: There are comments about VK9 in the Club Log database, which may
> provide further details. See
> https://clublog.org/test.php?c=VK9&t=23328000.
>
> Callsign: 5H3       Date: 1970-09-28 00:00:00          Band:
> 20              QSL: Yes
>
> Your log claims ZANZIBAR. Overriding your choice and using TANZANIA.
>
> Callsign: CR6       Date: 1970-09-28 00:00:00          Band:
> 20              QSL: Yes
>
> Your log claims PORTUGAL. Overriding your choice and using ANGOLA.
>
> Callsign: GU0     Date: 1970-09-28 00:00:00          Band:
> 20              QSL: Yes
>
> Your log claims GUERNSEY. Overriding your choice and using ENGLAND.
>
> Callsign: P46S     Date: 1984-11-24 20:17:00          Band:
> 15              QSL: Yes
>
> Your log claims ARUBA. Overriding your choice and using SINT MAARTEN,
> SABA, ST EUSTATIUS.
>
> Callsign: KH7X    Date: 2017-11-19 23:52:00          Band:
> 20              QSL: No
>
> Your log claims HAWAII. Club Log has a specific exception for KH7X and
> will use UNITED STATES OF AMERICA.
>
> See https://clublog.org/test.php?c=KH7X&t=1511135520 for details.
>
> Callsign: EZ0T     Date: 2018-05-27 22:04:55          Band:
> 20              QSL: No
>
> 'EZ0T' is not known to have been active from TURKMENISTAN on this
> date. As a precaution, this QSO will be stored but marked as invalid
> for DXCC. If this callsign is valid, it can be whitelisted - you are
> invited to send feedback. For a detailed explanation, please see:
> http://clublog.freshdesk.com/solution/articles/77534-whitelists
>
> Outlook Laptop Gil W0MN
>
> Hierro candente, batir de repente
>
> 44.08226N 92.51265W EN34rb
>
> *From:* DXLab@groups.io <DXLab@groups.io> *On Behalf Of *Tony Dixon G4CJC
> *Sent:* Monday, January 13, 2020 07:00
> *To:* DXLab@groups.io
> *Subject:* Re: [DXLab] DXview remains in memory
>
> [Edited Message Follows]
>
> Thanks Dave, but my Windows 10 is running fine reliably and without
> any other (noticeable) problems.
> I have found  simple way to get the effect. I now have DXView pinned
> to the Task Bar. Click on it to open it.  it can be seen in Task
> Manager as an App. When it's opened fully, close it from the Task Bar
> by clicking on the X in the corner of the popup.
> It the moves from the Apps in Task Manager to Background Processes.
>
> Like I said, the work round is not to close DXView from the task bar.
> Simple.
> Cheers
> Tony G4CJC
>
> Outlook Laptop Gil W0MN
>
> Hierro candente, batir de repente
>
> 44.08226N 92.51265W EN34rb
>
>
> --
>
> W0MN EN34rb 44.08226 N 92.51265 W
>
> Hierro candente, batir de repente
>
> HP Laptop
>




Re: Clublog errors

Jim Wysocki
 

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

On 1/13/2020 1:51 PM, Gilbert Baron W0MN wrote:

Interesting and probably not important as these are very old. Strangely though Clublog calls them broken but DXKEEPER does not. They are either so old or not QSLed that I think it best to simply ignore or delete from log.

I am not sure why I even bother with CLUBLOG. I just thought I would upload in case it is a help to someone.

Below is what I got from them.

Dear W0MN,

While processing your ADIF file for Club Log, the following possible problems were detected. Your log may be correct, but if necessary you can resolve these problems and create a new ADIF. If you make changes, it's recommended that on your next upload you use the option to clear your existing log, to avoid leaving prior records in Club Log.

If you would like to discuss these problems, then please open a discussion on the reflector, or reply to this email to ask the volunteer team for help. You can disable these emails from the Settings page if you prefer.

Google Groups Reflector: https://groups.google.com/group/clublog

Information on DXCC mappings: https://clublog.freshdesk.com/solution/categories/59801

Ask for help from the volunteer team: https://clublog.freshdesk.com/

73 de Michael G7VJR

* Software: DXKEEPER

* File name: ClubLogUpload.ADI (923.04 KB)

* New QSOs: 3,693

Callsign: VK9      Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

VK9 is an invalid QSO, either under the ARRL DXCC rules or because it is outside the known dates of a valid operation. Club Log is storing this QSO, but marking it as invalid. For more information, please see http://clublog.freshdesk.com/solution/articles/53820-invalid-mappings

Note: There are comments about VK9 in the Club Log database, which may provide further details. See https://clublog.org/test.php?c=VK9&t=23328000.

Callsign: 5H3       Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

Your log claims ZANZIBAR. Overriding your choice and using TANZANIA.

Callsign: CR6       Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

Your log claims PORTUGAL. Overriding your choice and using ANGOLA.

Callsign: GU0     Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

Your log claims GUERNSEY. Overriding your choice and using ENGLAND.

Callsign: P46S     Date: 1984-11-24 20:17:00          Band: 15              QSL: Yes

Your log claims ARUBA. Overriding your choice and using SINT MAARTEN, SABA, ST EUSTATIUS.

Callsign: KH7X    Date: 2017-11-19 23:52:00          Band: 20              QSL: No

Your log claims HAWAII. Club Log has a specific exception for KH7X and will use UNITED STATES OF AMERICA.

See https://clublog.org/test.php?c=KH7X&t=1511135520 for details.

Callsign: EZ0T     Date: 2018-05-27 22:04:55          Band: 20              QSL: No

'EZ0T' is not known to have been active from TURKMENISTAN on this date. As a precaution, this QSO will be stored but marked as invalid for DXCC. If this callsign is valid, it can be whitelisted - you are invited to send feedback. For a detailed explanation, please see: http://clublog.freshdesk.com/solution/articles/77534-whitelists

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

*From:* DXLab@groups.io <DXLab@groups.io> *On Behalf Of *Tony Dixon G4CJC
*Sent:* Monday, January 13, 2020 07:00
*To:* DXLab@groups.io
*Subject:* Re: [DXLab] DXview remains in memory

[Edited Message Follows]

Thanks Dave, but my Windows 10 is running fine reliably and without any other (noticeable) problems.
I have found  simple way to get the effect. I now have DXView pinned to the Task Bar. Click on it to open it.  it can be seen in Task Manager as an App. When it's opened fully, close it from the Task Bar by clicking on the X in the corner of the popup.
It the moves from the Apps in Task Manager to Background Processes.

Like I said, the work round is not to close DXView from the task bar. Simple.
Cheers
Tony G4CJC

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: Clublog errors

Dave AA6YQ
 

+ AA6YQ comments below

Interesting and probably not important as these are very old. Strangely though Clublog calls them broken but DXKEEPER does not.

+ DXKeeper does not consider a callsign of the form LLD to be prima facie invalid (where L is a letter and D is a digit).

+ DXKeeper does not maintain a database of callsigns known to be invalid for DXCC because the ARRL does not publicize such a list.

73,

Dave, AA6YQ


Clublog errors

Gilbert Baron W0MN
 

Interesting and probably not important as these are very old. Strangely though Clublog calls them broken but DXKEEPER does not. They are either so old or not QSLed that I think it best to simply ignore or delete from log.

 

I am not sure why I even bother with CLUBLOG. I just thought I would upload in case it is a help to someone.

 

 

Below is what I got from them.

 

 

Dear W0MN,

 

While processing your ADIF file for Club Log, the following possible problems were detected. Your log may be correct, but if necessary you can resolve these problems and create a new ADIF. If you make changes, it's recommended that on your next upload you use the option to clear your existing log, to avoid leaving prior records in Club Log.

 

If you would like to discuss these problems, then please open a discussion on the reflector, or reply to this email to ask the volunteer team for help. You can disable these emails from the Settings page if you prefer.

 

Google Groups Reflector: https://groups.google.com/group/clublog

Information on DXCC mappings: https://clublog.freshdesk.com/solution/categories/59801

Ask for help from the volunteer team: https://clublog.freshdesk.com/

 

73 de Michael G7VJR

 

* Software: DXKEEPER

* File name: ClubLogUpload.ADI (923.04 KB)

* New QSOs: 3,693

 

Callsign: VK9      Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

VK9 is an invalid QSO, either under the ARRL DXCC rules or because it is outside the known dates of a valid operation. Club Log is storing this QSO, but marking it as invalid. For more information, please see http://clublog.freshdesk.com/solution/articles/53820-invalid-mappings

Note: There are comments about VK9 in the Club Log database, which may provide further details. See https://clublog.org/test.php?c=VK9&t=23328000.

 

Callsign: 5H3       Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

Your log claims ZANZIBAR. Overriding your choice and using TANZANIA.

 

Callsign: CR6       Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

Your log claims PORTUGAL. Overriding your choice and using ANGOLA.

 

Callsign: GU0     Date: 1970-09-28 00:00:00          Band: 20              QSL: Yes

Your log claims GUERNSEY. Overriding your choice and using ENGLAND.

 

Callsign: P46S     Date: 1984-11-24 20:17:00          Band: 15              QSL: Yes

Your log claims ARUBA. Overriding your choice and using SINT MAARTEN, SABA, ST EUSTATIUS.

 

Callsign: KH7X    Date: 2017-11-19 23:52:00          Band: 20              QSL: No

Your log claims HAWAII. Club Log has a specific exception for KH7X and will use UNITED STATES OF AMERICA.

See https://clublog.org/test.php?c=KH7X&t=1511135520 for details.

 

Callsign: EZ0T     Date: 2018-05-27 22:04:55          Band: 20              QSL: No

'EZ0T' is not known to have been active from TURKMENISTAN on this date. As a precaution, this QSO will be stored but marked as invalid for DXCC. If this callsign is valid, it can be whitelisted - you are invited to send feedback. For a detailed explanation, please see: http://clublog.freshdesk.com/solution/articles/77534-whitelists

 

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Tony Dixon G4CJC
Sent: Monday, January 13, 2020 07:00
To: DXLab@groups.io
Subject: Re: [DXLab] DXview remains in memory

 

[Edited Message Follows]

Thanks Dave, but my Windows 10 is running fine reliably and without any other (noticeable) problems. 
I have found  simple way to get the effect. I now have DXView pinned to the Task Bar. Click on it to open it.  it can be seen in Task Manager as an App. When it's opened fully, close it from the Task Bar by clicking on the X in the corner of the popup.
It the moves from the Apps in Task Manager to Background Processes.


Like I said, the work round is not to close DXView from the task bar. Simple.
Cheers
Tony G4CJC

 

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: DXview remains in memory

Dave AA6YQ
 

+ AA6YQ comments below

Thanks Dave, but my Windows 10 is running fine reliably and without any other (noticeable) problems.
I have found simple way to get the effect. I now have DXView pinned to the Task Bar. Click on it to open it. it can be seen in Task Manager as an App. When it's opened fully, close it from the Task Bar by clicking on the X in the corner of the popup. It the moves from the Apps in Task Manager to Background Processes.

+ I have replicated this behavior on my Windows 10 system. Letting the mouse cursor hover over DXView's icon in the Window's Task Bar and then clicking the X button in the upper-right corner of the resulting popup causes DXView's windows to disappear, but DXView remains running in the background. In contrast, right-clicking DXView's icon in the Windows Task Bar, and selecting "Close all windows" correctly terminates DXView, as does clicking the X button in the upper-right corner of DXView's Main window or directing the Launcher to terminate DXView. This is clearly a defect in Windows; if you want to pursue it further, please engage with Microsoft Support - and post your findings here.

73,

Dave, AA6YQ


Re: DXview remains in memory

Tony Dixon G4CJC
 
Edited

Thanks Dave, but my Windows 10 is running fine reliably and without any other (noticeable) problems. 
I have found  simple way to get the effect. I now have DXView pinned to the Task Bar. Click on it to open it.  it can be seen in Task Manager as an App. When it's opened fully, close it from the Task Bar by clicking on the X in the corner of the popup.
It the moves from the Apps in Task Manager to Background Processes.


Like I said, the work round is not to close DXView from the task bar. Simple.
Cheers
Tony G4CJC


Re: Hi new to dxlab suite I've tried several installs.

K7OI-Mark
 

I have very little experience with electronic apps such as this. And seeing what this does in a broken state is impressive. Thank you for your work and kind words.
Bite the bullet it is.
73s
K7oi
I'll be back:)

On Sun, Jan 12, 2020, 23:34 Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Wow i have everything working now except a couple of glitches. By finding and downloading online the files that were missing.
I'm getting every apps functionality
Spots
Commander
Dxkeeper
Dxview
Pathfinder
Etc.

Seems it could be fixed another way I supposed not.

It might be a few days as I don't have to much on this computer right now and I would rather it worked properly.

+ If  you don't have much on the computer, now is the optimum time to bite the bullet, backup whatever files are critical, and then cleanly re-install Windows. Otherwise, the threat of "glitches" will be ever present - and they have a nasty habit of revealing themselves at the worst possible time.

Thank you for your help 73s

I would like to stay subscribed to your group.

+ You are of course welcome to continue participating here. Do understand that until you rebuild your system,  your reports of functions and features that don't work will be considered likely symptoms of running on a broken system, prompting a repetition of the advice already given here.

       73,

                Dave, AA6YQ






Re: Hi new to dxlab suite I've tried several installs.

Dave AA6YQ
 

+ AA6YQ comments below

Wow i have everything working now except a couple of glitches. By finding and downloading online the files that were missing.
I'm getting every apps functionality
Spots
Commander
Dxkeeper
Dxview
Pathfinder
Etc.

Seems it could be fixed another way I supposed not.

It might be a few days as I don't have to much on this computer right now and I would rather it worked properly.

+ If you don't have much on the computer, now is the optimum time to bite the bullet, backup whatever files are critical, and then cleanly re-install Windows. Otherwise, the threat of "glitches" will be ever present - and they have a nasty habit of revealing themselves at the worst possible time.

Thank you for your help 73s

I would like to stay subscribed to your group.

+ You are of course welcome to continue participating here. Do understand that until you rebuild your system, your reports of functions and features that don't work will be considered likely symptoms of running on a broken system, prompting a repetition of the advice already given here.

73,

Dave, AA6YQ


Re: Hi new to dxlab suite I've tried several installs.

K7OI-Mark
 

Wow i have everything working now except a couple of glitches. By finding and downloading online the files that were missing.
I'm getting every apps functionality 
Spots 
Commander
Dxkeeper
Dxview
Pathfinder 
Etc.

Seems it could be fixed another way I supposed not.

It might be a few days as I don't have to much on this computer right now and I would rather it worked properly.
Thank you for your help 73s

I would like to stay subscribed to your group.

K7OI

On Sun, Jan 12, 2020, 22:02 Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments bellows

Hi
I did not create a image before the process. I have installed the log book and other apps b4 and knew them to be safe.

As to how the uninstall document disapearred.
I assumed the apps could be uninstalled by deleting them from the c drive.
When that didn't work I went to control panel uninstall apps.

When that wouldn't remove them I deleted every file I could find cleaning up dxlabs for a what I thought would be a fresh install

I'm not computer literate but pretty smart.

Things should work for normal people.

+ Deleting the files of an installed Windows application before you first uninstall that application creates an unreliable mess. This is not unique to DXLab.

Is there a fix ?

+ Yes:

1. make offline copies of all of your critical files (your log, pictures, documents, files, application installers, device drivers, etc.)

2. verify the integrity of each the offline copies created in step 1

3. erase your c: drive

4. re-install Windows

5. restore the files you backed up in step 1

6. carefully follow these step-by-step instructions:

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

and

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

       73,

           Dave, AA6YQ





Re: Hi new to dxlab suite I've tried several installs.

Dave AA6YQ
 

+ AA6YQ comments bellows

Hi
I did not create a image before the process. I have installed the log book and other apps b4 and knew them to be safe.

As to how the uninstall document disapearred.
I assumed the apps could be uninstalled by deleting them from the c drive.
When that didn't work I went to control panel uninstall apps.

When that wouldn't remove them I deleted every file I could find cleaning up dxlabs for a what I thought would be a fresh install

I'm not computer literate but pretty smart.

Things should work for normal people.

+ Deleting the files of an installed Windows application before you first uninstall that application creates an unreliable mess. This is not unique to DXLab.

Is there a fix ?

+ Yes:

1. make offline copies of all of your critical files (your log, pictures, documents, files, application installers, device drivers, etc.)

2. verify the integrity of each the offline copies created in step 1

3. erase your c: drive

4. re-install Windows

5. restore the files you backed up in step 1

6. carefully follow these step-by-step instructions:

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

and

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

73,

Dave, AA6YQ


Re: Hi new to dxlab suite I've tried several installs.

K7OI-Mark
 

Hi 
I did not create a image before the process. I have installed the log book and other apps b4 and knew them to be safe.

As to how the uninstall document disapearred.
I assumed the apps could be uninstalled by deleting them from the c drive.
When that didn't work I went to control panel uninstall apps.

When that wouldn't remove them I deleted every file I could find cleaning up dxlabs for a what I thought would be a fresh install

I'm not computer literate but pretty smart. 

Things should work for normal people.

Is there a fix ?

On Sun, Jan 12, 2020, 21:29 Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Ok Dave here you go
I'm not sure how I uninstalled these with out the uninst... Folder.

+ Why were the "uninstallation" files not present?

Besides my fresh install I removed everything I could.

+ It's a mistake to remove files from an application that has not been uninstalled from Windows.

And actually got all my installed apps functioning properly but didn't know how to update and now I do. So that being said my current install of newest release have some issues.
Here is list
Commander
Dxkeeper
Dxkeeper good install
Dxlablauncher
Dxview
Pathfinder
Pathfinder good install
Propview
Spotcollector
Winwarbler.

Problem now is good install is c:\dxlabs\app name is pathfinder etc.
The ones containing no directory I'm not sure if it installed correctly or not. But are working except a few missing mbd bmp filed. As I deleted everything when I cleaned it up best I could.
I'm sure not what you feared.

+ If I understand you correctly, Windows is badly confused about what's installed, and where - to the point where a reliable installation of DXLab is not possible.

+ Did you create an "image backup" just before beginning the process of installing DXLab applications?


      73,

                   Dave, AA6YQ 





Re: Hi new to dxlab suite I've tried several installs.

Dave AA6YQ
 

+ AA6YQ comments below

Ok Dave here you go
I'm not sure how I uninstalled these with out the uninst... Folder.

+ Why were the "uninstallation" files not present?

Besides my fresh install I removed everything I could.

+ It's a mistake to remove files from an application that has not been uninstalled from Windows.

And actually got all my installed apps functioning properly but didn't know how to update and now I do. So that being said my current install of newest release have some issues.
Here is list
Commander
Dxkeeper
Dxkeeper good install
Dxlablauncher
Dxview
Pathfinder
Pathfinder good install
Propview
Spotcollector
Winwarbler.

Problem now is good install is c:\dxlabs\app name is pathfinder etc.
The ones containing no directory I'm not sure if it installed correctly or not. But are working except a few missing mbd bmp filed. As I deleted everything when I cleaned it up best I could.
I'm sure not what you feared.

+ If I understand you correctly, Windows is badly confused about what's installed, and where - to the point where a reliable installation of DXLab is not possible.

+ Did you create an "image backup" just before beginning the process of installing DXLab applications?


73,

Dave, AA6YQ