Original/initial draft: Well, starting multiple copies of Fldigi will open multiple windows. Regardless of how many copies of Fldigi can be started, all use the same configuration directory to store settings. Presumably this station had different radios for the different bands. Mike wanted the ability to retain settings for their different uses, notably soundcard inputs/outputs and rig control (if used). One of those radios might be using a SignaLink/RigBlaster/something else to send and receive messages. Another radio maybe using virtual audio cables (typical for SDR radios), a different SignaLink/RigBlaster/something else and Hamlib for rig control. If multiple Fldigi/Flmsg are started using the same configuration settings directory, when the last window is closed, those will be the configuration settings that are retained. Last settings saved will be loaded when the program is restarted. Additional windows will have to be configured again. Not convenient, especially with many uses. 2nd revision: Starting multiple copies of Fldigi will open multiple windows. Regardless of how many Fldigi windows can be opened, all use the same configuration directory for settings. Presumably this station had different radios for different bands. Mike wanted Fldigi & Flmsg to retain settings for their different uses. Most notably would be soundcard inputs/outputs and rig control (if used). One of those radios might be using a SignaLink/RigBlaster/other soundcard interface to send and receive messages. Another radio maybe using virtual audio cables (typical for SDR radios) and Hamlib for rig control. If multiple Fldigi & Flmsg windows are open and they all use the same settings directory, when the last window is closed, the settings of the last window are saved. The last settings will be loaded when the program is restarted. Additional Fldigi & Flmsg windows will have to be configured allover again. Not convenient, especially with many different uses on a single PC. 3rd revision: Starting multiple copies of Fldigi & Flmsg will open multiple windows. Regardless of how many windows can be opened, all use the same user configuration directory for settings. Presumably this station had different radios for different bands. Mike wanted Fldigi to retain settings for each different use. Most notably, soundcard inputs/outputs and rig control (if used). One of those radios might be using a SignaLink/RigBlaster/other soundcard interface. Another radio maybe using virtual audio cables (typical for SDR radios) and Hamlib for rig control. When multiple Fldigi & Flmsg windows all use the same settings directory, last window closed wins. The last instance writes its settings to the settings directory. When the program is restarted, those settings are loaded. Additional Fldigi & Flmsg windows will have to be configured allover again. Not convenient, especially with many different uses on a single PC, in a pinch, or during a real operating event. 4th revision: Starting multiple copies of Fldigi & Flmsg will open multiple windows. Regardless of how many windows can be opened, all use the same user configuration directory for settings. Presumably this station had different radios for different bands. Mike wanted Fldigi to retain settings for each different use. Most notably, soundcard inputs/outputs and rig control (if used). One radio might be using a SignaLink/RigBlaster/other soundcard interface and have no rig control. Another radio maybe using virtual audio cables (typical for SDR radios) and Hamlib for rig control. When multiple Fldigi & Flmsg windows use the same settings directory, last window closed wins. The last instance writes its settings to the configuration directory. When the program is restarted, those settings are loaded. Additional Fldigi & Flmsg windows have to be configured allover again. Not convenient, especially with many different uses on a single PC, in a pinch, or during a real operating event. 5th revision: Starting multiple copies of Fldigi & Flmsg will open multiple windows. Regardless of how many windows can be opened, all use the same user configuration directory for settings. Presumably this station had different radios for different bands. Mike wanted Fldigi to retain settings for each use. Most notably, soundcard inputs/outputs and rig control (if used). One radio might be using a SignaLink/RigBlaster/other soundcard interface and have no rig control. Another radio maybe using virtual audio cables (typical for SDR radios) and Hamlib for rig control. When multiple Fldigi & Flmsg windows use the same settings directory, last window closed wins. When the program is restarted, those settings are loaded. Additional Fldigi & Flmsg windows have to be configured allover again. Not convenient, especially with many different uses on a single PC, in a pinch, or during a real operating event. Final published version: Starting multiple copies of Fldigi & Flmsg will open multiple windows. Regardless of how many windows can be opened, all use the same user configuration directory to store settings. Mike wanted Fldigi to retain settings for each use. Settings such as soundcard inputs/outputs and rig control (if used). One radio might be using a SignaLink/RIGblaster/other soundcard interface and have no rig control. Another radio maybe using virtual audio cables (typical for SDR radios) and Hamlib for rig control. When multiple Fldigi & Flmsg windows use the same settings directory, last window closed wins. When the program is restarted, those settings are loaded. Additional Fldigi & Flmsg windows have to be configured all over again. Not convenient, especially with many uses on a single PC, in a pinch, or during a real operating event.