+ AA6YQ comments below
The slow startup could be waiting for TQSL to contact the mothership if he didn't stop that as you recommended previously.
+ On startup, DXKeeper directs Windows to start TQSL with a command line argument that directs it to place "LoTW News" in the file
LoTWNews.txt
+ in your DXKeeper folder, and then continues with its initialization.
+ Four times per second, an event fires that causes DXKeeper to check for the creation of the LoTWNews.txt file. If the file exists, DXKeeper displays its contents; otherwise, DXKeeper increments a counter. If that counter reaches 120 (after 30 seconds), DXKeeper informs you that TQSL is unable to contact LoTW, and stops checking for the creation of the LotWNews.txt file.
+ I don't know why those 120 checks for the existence of a file over the course of 30 seconds would prevent Windows from conveying a message from Pathfinder to DXKeeper, not do I understand why it would cause an observable slowdown in DXKeeper's startup. I see neither of those effects here, so it must be specific to particular versions of Windows and/or differences in operating environment.
73,
Dave, AA6YQ
