I have successfully installed WDP 3.6.5.14 on a PC networked to my Falcon 4 PC. The networked PC with WDP does not have BMS installed on it. I have done this with older WDP versions in order to load my Callsign.ini file for campaign missions from the networked PC. I can not now load the WDP program, because the initial screen asks for my callsign, which it can not then find on the networked PC. The callsign text box will not accept the path to the Falcon BMS PC Callsign.ini file nor allow the program to load without a valid callsign found on the networked PC. Is there a way to overcome this impediment and get to the program where I can direct WDP to the correct .ini file and Falcon BMS Launcher file??
I have the same situation. With version 3.6.3 I am able to manually edit the setup file for the path of the Falcon install. That is the last version I am able to do that. Newer versions don’t seem to allow me to use the network path.