SEE
BlueZone API Support for details.|
Configuring BlueZone |
Chapter 5 |
HLLAPI is an acronym for High Level Language Application Program Interface. HLLAPI was developed so that external programs can be written to interact with a host session. This is accomplished by using the BlueZone emulator acting as the “middleware” between the HLLAPI application and the host session.
BlueZone ships with four HLLAPI DLL files:
WHLLAPI.DLL – BlueZone 32-bit HLLAPI DLL – Uses the DDE Server interface to communicate with the BlueZone emulator. Note that BlueZone's DDE Server Interface must be enabled in order for this DLL to work.
SEE
BlueZone API Support for details.
WHLAPI32.DLL – BlueZone 32-bit HLLAPI DLL – Uses “Shared Memory” to communicate with the BlueZone emulator.
PCSHLL.DLL – Exactly the same as WHLAPI32.DLL but named differently to automatically work with HLLAPI apps that are specifically “programmed” to communicate with a HLLAPI DLL named PCSHLL.DLL.
WHLAPI16.DLL – BlueZone “Thunking” DLL - Used as a bridge between older 16-bit DOS HLLAPI applications and the BlueZone WHLAPI32.DLL.
There are three types of third party HLLAPI applications that are supported by BlueZone:
Windows 32-bit HLLAPI Application
Windows 16-bit HLLAPI Application
DOS HLLAPI Application
Configuring BlueZone to work with a third party HLLAPI application is really quite simple. Your knowledge of, and your ability to change the configuration of your HLLAPI application is really the key to making it work with BlueZone.
To configure BlueZone to interact with a third party HLLAPI application, you will need a Windows workstation with the HLLAPI application properly installed and BlueZone Desktop installed as follows:
Change the following setting from No to Yes, in the SETUP.INI file before installing BlueZone:
[BZSetup]
SetPath=Yes
During installation the BlueZone Setup program will add the BlueZone Program Directory to the Windows “Path Environment Variable” if the workstation OS is Windows NT/2000/XP.
NOTE
This change
requires a system re-boot to take effect.
Make sure that you have selected the High Level Language (HLLAPI) Communications component and if you are configuring a DOS HLLAPI application, be sure to also select the BlueZone DOS HLLAPI Tools component. Otherwise this component is not needed.
Illustration 5-16
NOTE
The DOS HLLAPI Redirector will require a
system re-boot to take effect.
There are a few things you must know and do in order for BlueZone to work properly with your HLLAPI application. All HLLAPI applications need to know the name and location of your emulator’s HLLAPI DLL. Specifically, BlueZone's HLLAPI DLL.
Does your HLLAPI application, have a way to change the name and the location (path) of your emulator’s HLLAPI DLL?
No - If not, you will have to re-name the BlueZone HLLAPI DLL and manually copy it to the location where your HLLAPI application is expecting to find it. Chances are you already have a HLLAPI DLL in this location that is used by your current emulator. Temporarily rename the DLL so that you do not over write it with the BlueZone DLL. Proceed to question 2.
Yes - Launch the Configuration Interface of your HLLAPI application and change the name and location of the HLLAPI DLL to point to the BlueZone HLLAPI DLL (WHLLAPI.DLL). Proceed to question 2.
BlueZone's HLLAPI DLL is called WHLLAPI.DLL and can be found in the main BlueZone installation directory. The default installation directory for BlueZone is C:\Program Files\SEAGULL\BlueZone.
Is there a HLLAPI.DLL from a competitor's emulator already installed on the same workstation that you are using to test BlueZone's HLLAPI interface?
Yes - If so, you will have to temporarily rename that DLL while testing BlueZone to prevent conflicts, then proceed to question 3. Or, it might be easier to install and test BlueZone on a workstation that does not have a competitor's emulator installed. Conflicts with existing emulators is a common problem when tying to configure BlueZone to work with a HLLAPI application.
No – Proceed to question 3.
Is your HLLAPI application a Windows 32-bit application, a Windows 16-bit application, or a DOS application?
Windows 32-bit - Proceed to the Windows 32-bit HLLAPI Application section.
Windows 16-bit - Proceed to the Windows 16-bit HLLAPI Application section.
DOS on Windows 95/98/ME - Proceed to the DOS HLLAPI Application - Windows 95/98/ME section.
DOS on Windows 2000/XP - Proceed to the DOS HLLAPI Application - Windows 2000/XP section.
After you have BlueZone Desktop installed with the proper components, launch a BlueZone Display session. Then follow these steps:
On the BlueZone MenuBar, select Options:API. You will be presented with the API Properties dialog.
Check the, Enable DDE Server Interface checkbox. Click the OK button. BlueZone is now listening for a DDE connection.
On the BlueZone MenuBar, select Session:Connect, to establish a connection to your host.
Configure your 32-bit HLLAPI application to connect to BlueZone's HLLAPI DLL (WHLLAPI.DLL). This could involve changing the applications settings so that it is looking for the BlueZone DLL called WHLLAPI.DLL, or you may have to rename the BlueZone DLL to the name that your application is programmed to look for.
Launch your HLLAPI application and execute a command that will send or receive data from your host.
Check to see if your HLLAPI application is interacting with BlueZone.
On the BlueZone MenuBar, select Options:API. You will be presented with the API Properties dialog.
Check the, Enable DDE Server Interface checkbox. Click the OK button. BlueZone is now listening for a DDE connection.
On the BlueZone MenuBar, select Session:Connect, to establish a connection to your host.
Configure your 16-bit HLLAPI application to connect to BlueZone's "Thunking" DLL (WHLAPI16.DLL). This could involve changing the application's settings so that it is looking for the BlueZone DLL called WHLAP16I.DLL, or you may have to rename the BlueZone DLL to the name that your application is programmed to look for.
Launch your 16-bit HLLAPI application and execute a command that will send or receive data from your host.
Check to see if your HLLAPI application is interacting with BlueZone.
On the BlueZone MenuBar, select Options:API. You will be presented with the API Properties dialog.
Check the, Enable DDE Server Interface checkbox. Click the OK button. BlueZone is now listening for a DDE connection.
Check the Auto-Launch the BlueZone DOS HLLAPI Redirector checkbox.
On the BlueZone MenuBar, select Session:Connect, to establish a connection to your host.
Make sure the DOS HLLAPI Redirector is running by checking the Windows Taskbar for a small yellow light bulb. This is the indication that the DOS HLLAPI Redirector is running.
Launch a DOS shell. Change to the working directory of where your DOS HLLAPI application is located.
At the DOS command prompt, launch the BlueZone VxD application by typing VECT7F.EXE. You should receive the following message:"DOS Virtual Machine Vector 0x7f Redirector".
Launch your DOS HLLAPI application and execute a command that will send or receive data from your host.
Check to see if your DOS HLLAPI application is interacting with BlueZone.
On the BlueZone MenuBar, select Options:API. You will be presented with the API Properties dialog.
Check the, Enable DDE Server Interface checkbox. Click the OK button. BlueZone is now listening for a DDE connection.
On the BlueZone MenuBar, select Session:Connect, to establish a connection to your host.
Launch a DOS shell. Change to the working directory of where your DOS HLLAPI application is located.
At the DOS command prompt, launch the BlueZone VxD application by typing BZHLLINT.EXE. You should receive the following message:"The DOS HLLAPI interrupt has been successfully intercepted".
Launch your DOS HLLAPI application and execute a command that will send or receive data from your host.
Check to see if your DOS HLLAPI application is interacting with BlueZone.