Cooperating with Logger32 when it also cooperating with another external program

•	Logger32 can work simultaneously with 5 -th external programs. Such programs are my program BUREAU_ALL_QRZ_COM_FI.exe and programs by N2AMG which could include :

•	L32 - Fldigi_Gateway.exe cooperating with the program fldigi.exe tested here version v 3.21.76 , by W1HKJ . Fldigi used to operate digital modes and it seems better than MMVari decodes . Compare it to the practice with MMVari leave readers.

•

LOTW_Eqsl_Utility.exe by N2AMG is used to retrieve data from Logger32 and transfer to LOTW , to the page e- QSL , the page CLUB -LOG and the HRD- NET . It is possible to also retrieve data from this page data about compatible QSO and synchronization with Logger32 . The program can also send the last QSO to the author's website station - so that the log is available on-line .

•	programs by N2AMG or JA1NLX for collecting personal information such QRZLookup station . These programs will discuss separately here .

•	Programs what I'm talking about above are configured and set to run automatically with the Logger . It is do in a window achieved by pressing the menu Tools - Configuration utility.

Window to declare external programs
and their autorun
with Logger32

•

Programs for cooperate well with Logger32 and not interacted in a wrong way , must be conform the appropriate conditions for co-operation , and must be provided with adequate procedures for booting various external programs . For proper cooperating , to each program is assigned by Logger32, when it start , the session number .

•	Communication is do in the one communication channel , using the in the Windows API message SendMessage , PostMessage , ReciveMessage .

•	The big problem occurs when an external program calls Logger32 in an asynchronous manner . i.e. at any times.

•	From my observation of the behavior of the Logger32 , when it cooperating with several programs at the same time , what is automatically run when start Logger32 , I shows that these programs are switching on almost simultaneously , without any delay .

•	It would be good for another external program , to begin start session only when the previous session was end and this session, and it is stable.

•	Unfortunately, there is no such control mechanisms and therefore we have to use another method.

•	Such a method for establishing the session may be time to introduce a method Delay start the next session of the connection ., so that all the processes of connection in the previous session was ended and stabilized .

•	N2AMG programs are not perhaps assume such a delay start , because there is no such parameter in the configuration file .

•	I in my program BUREAU_ALL_QRZ_COM_FI.exe, I admit this delay_time start . For this is used the file delay_time.txt , in which this time is given in msec. This value cannot be set in a configuration window . This parameter should be changed in any text editor.

•	This time is measured by the program Sleep_Exec_Bureau_all_qrz_com_fi.exe , what after this time delay run right program BUREAU_ALL_QRZ_COM_FI.exe ..

•	If Logger32 works with only one external program , ie the BUREAU_ALL_QRZ_COM_FI.exe is recommended here, the value 3000 msec. This allows you to stabilize Logger32 windows .

•

When Logger32 works with other external programs such as L32_FldigiGateway.exe by N2AMG and Fldigi , recommended here this value is about 15000 msec. , This time 15 sec was tested on Windows XP. I get good cooperation at time = 8 sec . However, this depends heavily on the CPU load and if the computer is strong .

•

Typical symptoms that this time it is too small, it is appearance of the phenomenon , that after clicking in a window or Logger32 or Fldigi caused to hide the window BUREAU_ALL_QRZ_COM_FI.exe . Also, clicking on the window BUREAU_ALL_QRZ_COM_FI.exe may cause the disappearance of the window Fldigi . Also , you may receive an error to divide by zero . The reason is that if any external program is trying to show a message and user must press the OK button , then Windows has the unpleasant feature that at this time blocks possibilty click OK in a other message from another program . If the second external program already established at this time connection , and try to display the message before pressing OK in the message in the 1st program , then occurs interlocking , and displaying the error. So best way it there wait until the first external program stabilize the connection and displays all messages to the user , and the user has approved them . Only then is the moment to run the second external program . BUREAU_ALL_QRZ_COM_FI.exe should start as the last , ie number 2 or 3 sessions . This behavior of Windows will not occur ever in Linux because Linux is a system with a real- time division with the expropriation after this time is exceeded . Windows has never been a true multi-tasking system with real- time division .

•

The user must choose this time by experiment , because this value strongly depends on the speed of the computer and that the firewall learns , that must allow packets without the constant questions about the user 's consent . At the beginning until the firewall to teach ( for firewall should choose to remember your selection ) , you can give here a higher value , eg . 30 sec = 30000 msec. You can also run any program first by hand outside of the main menu Logger32 .

Manual run external program

Here I will present reports on testing different set of programs on different computers. They will basically screenshots with descriptions. These reports are prepared for the start of the period's most important programs. At this point, plese user to do report from time operation positive or negative. If you get any problems, please report them to me by e-mail

sp9auv@wp.pl

For cooperate was selected two programs :

Window for declare two external
programs cooperating with
Logger32 and the way that is run
automatically with Logger32 .
There are cooperating with Logger32
two programs

The screen with the cooperation of the two
external programs with Logger32 :
1- L32-FldigiGatewa/Fldigi and
2- BUREAU_ALL_QRZ_COM_FI in Windows XP 32 bit

Icon L32-FldigiGateway when connected Fldigi to Logger32 hides and goes to the bar system's tray. Then you can call on your desktop using the right mouse button on the icon and selecting Show:

It is yet to see Main bookmark in the window L32-FldigiGateaway - which must be reported connection and frequency

The Main bookmark in the
L32-Fldigi-Gateway

For cooperating was chosed three programs

Window for declaring external
programs and the way
automatic run ,
when Logger32 start

Time_delay for run BUREAU_ALL_QRZ_COM_FI.exe was set to 8000 msec = 8 sec, but on your computer can be quite different. You will need to select this experimentally , when do same tests.

View window when Logger32 cooperating with three programs :
1= L32-Fldigi_Gateway/Fldigi ,
2 = LOTW-E-QSL-Utility
3 = BUREAU_ALL_QRZ_COM_FI.exe
Anothers descritions in this screen is as above picture

Program LOTW-eQSL Utility by N2AMG is used to retrieve data from Logger32 and send them to the server LOTW or e-QSL. It can also retrieve data from these pages and sync them with Logger32. In addition, the servers can work with CLUB-LOG or HRD-NET. Also has the ability to transmit these data to the FTP server and there you can share your log in ON-LINE mode on your website, ie every QSO will be done immediately visible on the station website . To be able to use this software you must first install the software on your computer. After releasing the instalation program setup.exe version 4.1.98 we may see a message as shown below.

At this point, the installation program reports to us that our system files is outdated , and proposes the update by pressing OK. At this point, you should immediately choose Cancel , because if you pres OK to change, your Windows XP will no longer worked properly ever . I tried to give OK , but it was on a virtual Windows XP computer, and I had a fresh copy of the virtual machine, so you just I deleted the virtual machine and have restored it from backup . What caused this message, I am not able to figure out - but surely it should not be installed on XP . At this point will simply change the system DLLs . Once installed, you can get such a message - no entry for the procedure. Besides, the author acknowledges that the program PrivateKeyControl.exe in this package may be recognized as having the virus , (this is just so . False -positive ) by some antivirus . But why the program is trying to change the system DLL path in the system, which has been regularly updated. If you sure you want to make install on a real computer Windows XP , I recommend before installing LOTW - eQSL_Utility create a restore point in a Windows XP

The program BUREAU_ALL_QRZ_COM_FI.exe is able to recognize run other external programs such QRZ Lookup. These programs include a program by N2AMG and JA1NLX named:

1.	QRZLookup.exe

2.	QRZ Subscriber Lookup.exe

3.	QRZHTTPLookup.exe

4.	QRZSubscriberXMLLookup.exe

5.	QRZXMLLookup.exe

6.	Lookup_HamQTH_ADIF.exe

7.	Lookup_HamQTH_XML.exe

8.	Lookup_QRZ_XML.exe

Configuration while
start another
program type QRZLookup

If you run another program QRZ_Lookup on the screen of my program screen will appear :

Message , that run also
another program
QRZ_Lokup

Simultaneous running two programs is not recommended, because it has twice the number of downloads from QRZ.COM, and when displaying messages through these programs, you may receive erroneous action programs because Windows has a unpleasant feature described here. If there appers such message you should perform the appropriate configuration steps described in the installation and configuration. Probably not perform these tasks during installation

Navigation: Programs cooperating with Logger32 > Cooperating program with Logger32 and showing no QSL bureau > Purpose of the program BUREAU_NOT_PRESENT > Programs work with Logger32 and QRZ_COM >

Cooperating with Logger32 when it also cooperating with another external program

Expand all elements Collapse all elements