SEE
How
to Capture a HLLAPI Trace|
Configuring BlueZone |
Chapter 5 |
One method for troubleshooting is to use the trace facility that is built into BlueZone. If you are having difficulty in determining if your HLLAPI application is connecting to BlueZone, you can launch BlueZone, start a BlueZone HLLAPI trace, connect your HLLAPI application to BlueZone, stop the trace, and look at the trace to see what transpired.
SEE
How
to Capture a HLLAPI Trace
The following is the beginning of a BlueZone HLLAPI trace. Note that the Return Code equals 0 (RetCode:0). This means that the HLLAPI application has successfully connected to the BlueZone emulation program.
SEAGULL BlueZone v3.4 Build 455 API Trace Started 08/26/2004 at 13:47:47.701
Time: 13:47:53.605
Event: WinHLLAPI-In Task:0 Status:0 Func:21 Data:1384668 Len:0 RetCode:0
Time: 13:47:53.605
Event: WinHLLAPI-Out Task:0 Status:0 Func:21 Data:1384668 Len:0 RetCode:0
A return Code of 1 would indicate that your HLLAPI application has not successfully connected to the BlueZone emulation program.
Possible causes of a Return Code of 1 are:
You have not changed to "SetPath=Yes" in the [BZSetup] section of the SETUP.INI file so that BlueZone is included in your workstations's "Path".
You have not rebooted your workstation after changing the "SetPath=Yes" setting.
You do not have the BlueZone DDE Server Interface enabled.
Your HLLAPI application is still trying to connect to a competitor's HLLAPI DLL installed on this workstation.
If your HLLAPI application is looking for a particular HLLAPI DLL name, you may have renamed the correct BlueZone HLLAPI DLL with the wrong or incorrectly typed name.
You have renamed the wrong BlueZone HLLAPI DLL. Make sure that you are renaming the correct DLL. If your HLLAPI application is 32-bit, you should rename WHLLAPI.DLL (DDE) or WHLAPI32.DLL (Shared Memory). If your HLLAPI application is 16-bit, you should rename WHLAPI16.DLL.