Re: DXView after Win10

Sebastian <w4as@...>

Dave, I wasn’t able to solve the issue with the link you sent. It appears DISM's command line syntax has changed in Windows 10.

However, I found this site which was very helpful: <>

Sometimes the simple things are right in front of you. Resetting the default file associations in Windows 10 was a piece of cake. Once I did that, the problem with running DXView was solved. I should note that I also use DX Atlas with DXView, and it appears that may have had something to do with the problem I experienced.

After resetting the associations, and closing and running DXLab several times, the window asking how to handle an extension appeared again. The file extension is .kml, for keyhole markup language. This is used by at least Google Earth and I suspect perhaps is also used by DX Atlas.

Windows 10 believes DXView.exe is probably the default program to use with that extension, as it is the first program which appears in the list of programs to associate it with.

Instead, I chose the text editor I use Notepad++, an excellent and free (GNU) source code editor. As soon as I did that, the text editor displayed a file with the name LoadPlottedInfo.kml, which looks like an xml file. Because of the formatting, I chose not to post it here. If you’d like, I can send it direct to you. It references, as well as; hopefully this file won’t pop up from time to time.

73 de Sebastian, W4AS

On Jul 30, 2015, at 7:47 PM, ' Dave AA6YQ' [dxlab] <> wrote:

AA6YQ comments below
-----Original Message-----
From: []
Sent: Thursday, July 30, 2015 7:35 PM
Subject: [dxlab] DXView after Win10

After I upgraded to Windows 10, upon opening DXView for the first time, a window popped up asking about about how a certain file extension should be opened in the future. Unfortunately, I don�t recall the extension (only that it was something I hadn�t seen before). Since DXView would not run until I cleared that window, I told Windows 10 that extension should be opened with DXView.

Now DXView opens and runs correctly, until I exit it. When I run DXView again, Launcher shows dxv as red, and a window pops up saying that DXView is already running - even though it appears not to be running, but it is listed in Task Manager.

After I clear that �ghost� DXView in Task Manger, once I load DXView I still get the message that it is already running, and again there are two instances of it in Task Manager.

Dave, what types of files can DXView open, so I can attempt to change the association?

In the context of a Windows "file association", in which Windows associates an application to use when opening a file of a particular type (denoted by its file extension) -- e.g. when you double-click on a file in Windows Explorer -- DXView is incapable of displaying any file type.
Googling "File associations Windows 10" produced no "how to" information, but did reveal that there were defects in this functionality being corrected this spring. This article provides information relevant to Windows 8.1 that might be helpful:

You could also try searching for "File associations" in the Windows 10 Help. You should be able to view a list of file types and the application associated with each. When you find the file type whose associated application is DXView, direct Windows to remove this association.

After that's sorted, I would reboot Windows 10. Hopefully that will clear the other behavior your report above.

Join to automatically receive all group messages.