Relocating DXLab Applications from One PC to Another, or Surviving a New Installation of Windows

This step-by-step process describes how to copy one or more DXLab applications from one PC to another; these instructions can also be used when you're planning to upgrade your PC to a new version of Windows by performing a "clean install" that erases your C: drive. If you are using the ARRL's Logbook of the World (LotW), also see Moving LotW from one PC to another.

To copy one or more DXLab applications from a source PC to a destination PC,

  1. if the source and destination PCs are connected via a network, then create a folder named SafeStorage in a place on the destination PC that won't be affected by the copy process -- e.g. not within any to-be-copied DXLab application's destination folder; if the source and destination PCs are not connected via network, create a folder named SafeStorage on removable media (CD, DVD, removable hard drive, thumb drive) that can be written by your source PC and read on your destination PC.

  2. within SafeStorage, create a folder for each to-be-relocated DXLab application

  3. copy the following data files from their folder on the source PC to their folder in SafeStorage

    1. from Commander's folder

      • device data files for frequency-dependent devices, specified in the Data File panel of each device's tab in the Configuration window (if you've created such files)

      • filter group data files created using the Data File panel on the Configuration window's Filter Groups tab

      • memory files you've saved via the Config window's Memory tab

      • custom S-meter files in Commander's Smeter folder

      • BandSegments.txt (if you created it from DefaultBandSegments.txt)

      • Radios.txt (if you modified it)

      • any files containing user-defined control sequences, sliders, and control sets

    2. from DXKeeper's folder

      • log file(s); the current log file is designated in the Log File panel on the Configuration window's Log tab

      • log backup files; these reside in the folder specified in the Backup Folder panel on the Configuration window's Log tab

      • DXCC database - DXCC.mdb in the DXKeeper's Databases sub-folder (if you've made your own modifications)

      • if you have used the DXCC Credit Manager to download your DXCC credits, the DXCC Award Credit folder and its contents

      • Bands.txt (if you created it from DefaultBands.txt)

      • Modes.txt (if you created it from DefaultModes.txt)

      • Satellites.txt (if you created it from DefaultSatellites.txt)

      • any custom Log Page Display layout files you may have created; the one currently in use is specified in the Log Page Display layout file panel on the Configuration window's Log tab

      • any scripts you may have created
      • any reports you may have created
      • any files that store the parameters describing user-defined items

      • if you have downloaded eQSL images, the eQSL image folder and its contents

    3. from DXView's folder

      • DXCC database - DXCC.mdb in DXView's Databases sub-folder (if you've made your own modifications)

      • GridDXCC database - GridDXCC.mdb in DXView's Databases sub-folder (f you'd downloaded and installed it)

      • LotW database - LotW.mdb in DXView's Databases sub-folder (if you'd downloaded and installed it)

      • eQSL database - eQSLAG.mdb in DXView's Databases sub-folder (if you'd downloaded and installed it)

      • RDA database - RDA.mdb in DXView's Databases sub-folder (if you've downloaded and installed it)

      • USAP database - USAP.mdb in DXView's Databases sub-folder (if you'd downloaded and installed it)

      • Translation database - Translation.mdb in DXView's Databases sub-folder (if you've downloaded and installed it)

      • Overrides database - Overrides.mdb in DXView's Databases sub-folder (if you've downloaded and installed it)

    4. from Pathfinder's folder

      • any search files you've modified or developed in Pathfinder's Searches sub-folder

    5. from PropView's folder

      • Bands.txt (if you created it from DefaultBands.txt)

    6. from SpotCollector's folder

      • spot database, the pathname for which is specified in the Spot Database File panel on the Configuration window's Spot Database tab

      • SolarHistory.txt

      • DXCC database - DXCC.mdb in the SpotCollector's Databases sub-folder (if you've made your own modifications)

      • Special Callsigns - SpecialCallsigns.mdb in the SpotCollector's Databases sub-folder

      • sub-band definition file specified in the Sub-band Definition panel on the Configuration window's General tab (if you changed it)

      • any audio files you modified or created in SpotCollector's Sounds sub-folder

      • any macros you created and saved in files

      • any Special Callsign lists you created and saved in files

    7. from WinWarbler's folder

      • your minilog(s) (file named YourCallsign.ADI in your WinWarbler folder)

      • MMTTY.ini
      • USERPARA.ini

      • PSKBands.txt (if you created it from DefaultPSKBands.txt)

      • RTTYBands.txt (if you created it from DefaultRTTYBands.txt)

      • any macros you've saved in files in WinWarbler's Scripts sub-folder

      • any .wav files you created for phone voice keying (specified in the .wav file folder setting on the Configuration window's Phone tab)

    8. from DXLabLauncher's folder

      1. in the Launcher's Configuration window, click the Workspaces button

      2. in the Workspaces window

        • click the Create Empty Workspace button and specify a unique workspace name (e.g. RelocationBackup)

        • Select the new workspace name, and click the Save Settings to Workspace button

      3. Save the contents of the Launcher's Workspaces folder (which includes the new workspace you created, as well as any previous workspaces you created

  4. install the Launcher on the destination PC via http://www.dxlabsuite.com/download.htm

    1. if you install the Launcher on the destination PC into the same pathname as the Launcher is installed on the source PC, restored settings containing pathnames will not require manual updating in steps 8 and 10 below

      • if the Launcher is installed in c:\program files on your source PC and your destination PC is running Windows Vista, 7, 8, or 10 you should not do this, as these versions of Windows consider c:\program files to be a protected folder

  5. use the Launcher to install DXLab applications in the desired folders on the destination PC by specifying that location in the application's Program Path setting in the Launcher's Configuration window, and then clicking the application's Install button (requires Launcher version 1.5.0 or later)

  6. use the Launcher to load settings from the Workspace you saved in step 3h
    1. terminate the Launcher

    2. copy the Workspace folder (e.g. RelocationBackup) in SafeStorage to the Launcher's Workspace folder on the destination PC

    3. start the Launcher

    4. in the Launcher's Configuration window, click the Workspaces button

    5. in the Workspaces window

      • select the desired Workspace by clicking on its name (e.g. RelocationBackup)

      • click the Load Settings from Workspace button

  7. restore each file saved in step 3: copy that file from SafeStorage into the appropriate location in each re-installed applications's folder structure on the destination PC:

    1. into Commander's folder
      • device data files for frequency-dependent devices
      • filter group data files
      • memory files
      • custom S-meter files to Commander's Smeter folder

      • BandSegments.txt (if you modified it)

      • Radios.txt (if you modified it)

      • any files containing user-defined control sequences, sliders, and control sets

    2. into DXKeeper's folder
      • log file(s) into DXKeeper's Databases sub-folder
      • log backup files

      • DXCC.mdb into DXKeeper's Databases sub-folder (if you modified it)

      • Bands.txt (if you modified it)

      • Modes.txt (if you modified it)

      • Satellites.txt (if you modified it)

      • custom Log Page Display layout files
      • script files
      • report files
      • files that store the parameters describing user-defined items
    3. into DXView's folder

      • DXCC database - DXCC.mdb into DXView's Databases sub-folder (if you modified it)

      • GridDXCC database - GridDXCC.mdb into DXView's Databases sub-folder (if you'd downloaded and installed it)

      • LotW database - LotW.mdb into DXView's Databases sub-folder (if you'd downloaded and installed it)

      • eQSL database - eQSLAG.mdb into DXView's Databases sub-folder (if you'd downloaded and installed it)

      • RDA database - RDA.mdb into DXView's Databases sub-folder (if you've downloaded and installed it)

      • USAP database - USAP.mdb into DXView's Databases sub-folder (if you'd downloaded and installed it)

      • Translation database - Translation.mdb into DXView's Databases sub-folder (if you've downloaded and installed it)

      • Overrides database - Overrides.mdb into DXView's Databases sub-folder (if you've downloaded and installed it)

    4. into Pathfinder's folder
      • search files into Pathfinder's Searches sub-folder (if you modified them)

    5. into PropView's folder

      • Bands.txt (if you modified it)

    6. into SpotCollector's folder

      • spot database into SpotCollector's Databases sub-folder

      • SpecialCallsigns.mdb into SpotCollector's Databases sub-folder

      • SolarHistory.txt

      • sub-band definition file (if you modified it)
      • audio files (that you modified)
      • macros files

    7. into WinWarbler's folder

      • minilog file(s)
      • MMTTY.ini
      • USERPARA.ini

      • PSKBands.txt (if you modified it)

      • RTTYBands.txt (if you modified it)

      • macro files
      • .wav files

  8. if in step 5, DXLab applications were installed into folders on the destination PC that are different than the installation folders on the source PC, update each application's Program Path in the DXLab Apps tab on the Launcher's Configuration window

  9. if your DXLab applications on the source PC use any fonts not installed on the destination PC, install those fonts on the destination PC

  10. Configure Windows to not automatically power down any USB ports

  11. run each DXLab application on the destination PC, and update its settings to reflect the data file locations
    1. in Commander

      • device data files for frequency-dependent devices, specified in the Data File panel of each device's tab in the Configuration window

      • filter group data file, specified in the Data File panel on the Configuration window's Filter Grps tab

      • user-defined control sequences, sliders, and control sets

    2. in DXKeeper

      • log file, designated in the Log File panel on the Configuration window's Log tab

      • log backup files, whose folder is specified in the Backup Folder panel on the Configuration window's Log tab

    3. in SpotCollector

      • spot database, the pathname for which is specified in the Spot Database File panel on the Configuration window's Spot Database tab

      • sub-band definition file specified in the Sub-band Definition panel on the Configuration window's General tab (if you changed it)

      • audio files specified in the Audio Alarm panel on the Configuration window's General tab (if you changed them

      • Log file reference for award purposes panel on the Configuration window's Spot Database tab: if your DXKeeper log was relocated, then

        • if Log last opened by DXKeeper is selected, then running DXKeeper will convey the relocated log's location to SpotCollector

        • if Use log in specified pathname is selected, specify the pathname of the relocated log

        • if Query operator when DXKeeper log changes is selected, then running DXKeeper will convey the relocated log's location to SpotCollector

    4. in WinWarbler

      • any .wav files you created for phone voice keying (specified in the .wav file folder setting on the Configuration window's Phone tab)

  12. In Pathfinder's Configuration window, note the Emulation shown in the Internet Explorer panel; if this is less than 11, then

    1. click the Internet Explorer panel's Update Emulation button

    2. a small User Account Control window seeking your approval may appear; this window may only be visible on the Windows Taskbar, in which case you should open it from there.

    3. accept Pathfinder's offer to terminate
  13. run each DXLab application on the destination PC and verify correct operation

Post a question or suggestion on the DXLab Discussion Group

Getting Started with DXLab

MovingBetweenPCs (last edited 2024-04-27 17:39:50 by AA6YQ)