DALI is supported on Windows 98 / NT / 2000 / XP. This section covers installation instructions for the DALI server, C client libraries, MFC / ActiveX components, and demo programs.
Both the DALI server and the DALI client libraries use OpenSSL. The OpenSSL files can be found in the /OpenSSL directory. You should put the two DLL files located in /OpenSSL/dll into your Windows path (e.g. /Windows/System32). You should then copy the lib files in /OpenSSL/lib into your compiler's default library path, and the entire /OpenSSL/include/openssl directory into your compiler's default include directory.
DALI server software is available as an ZIP file for Windows. This file can be unzipped to the directory of your choice.
The files are organized into directories as follows:
/manual
Contains the DALI user manual in HTML format. Load the index.html file in
your web browser to view the documentation.
/DALIServer
The DALI server directory. Includes the DALIServer.exe binary plus DLLs
required to run the application.
/DALIServer/boards
The board configuration directory. See the Board Configuration section of the
documentation for more information.
/DALIServer/boards-examples
Example board configuration files which can be copied to the board
configuration directory and used as templates for the desired board
configuration.
/DALIServer/alarms
The alarm configuration directory. See the Alarms section of the documentation
for more information.
/DALIServer/alarms-examples
Example alarm configuration files which can be copied to the alarm
configuration directory and used as templates for the desired alarm
configuration.
/DALIServer/etc
Contains miscelaneous configuration files. The default location of the
password file if user authentication will be used.
/DALIServer/ssl
Contains the temporary self-signed SSL certificate for use in testing DALI SSL
support.
Using the DALI Win32 Server --------------------------- Although most users will be using the Linux or QNX version of the DALI server, the Win32 version is included for demostration and development purposes. Many users find it more convenient to run a local server in case the network is down, or the real server is not set up. The DALI Win32 server requires DSCUD to be installed. You will find DSCUD in the /DSCUD directory of the DALI package. During the install program, you do not need to install the developer libraries and should leave this option unchecked. The Win32 DALI server will run in demonstration mode. This mode provides fake I/O channels: only 16 A/D, 4 D/A and 3 DIO are functional, even though server queries will list 32 valid channels for each type. After launching DALIServer.exe, you need to click on the 'Start Server' button to begin listening for clients.
The DALI clients for C/C++/MFC/ActiveX are installed with the DALI server in the following directories.
/Development/ActiveX
ActiveX components for developing web based
GUIs for DALI and Internet Explorer. Also includes a batch file for
registering these components.
/Development/include
Header files for the C/C++ client and MFC / ActiveX DALI clients.
/Development/lib
Windows libraries for the C/C++ client and MFC / ActiveX clients.
The client development files consist of .lib and .h files for use with Microsoft Visual C++ 6.0. They are located in the \lib and \include directories respectively. To install these files, locate your Visual C++ directory. This is commonly set to "C:\Program Files\Microsoft Visual Studio\VC98". Copy the files accordingly: Development\lib\dalic.lib C:\Program Files\Microsoft Visual Studio\VC98\lib Development\lib\dali_w32.lib C:\Program Files\Microsoft Visual Studio\VC98\lib Development\lib\dalictrl.lib C:\Program Files\Microsoft Visual Studio\VC98\lib Development\include\dalic.h C:\Program Files\Microsoft Visual Studio\VC98\include Development\include\dali_w32.h C:\Program Files\Microsoft Visual Studio\VC98\include Development\include\dalictrl.h C:\Program Files\Microsoft Visual Studio\VC98\include If you are using Microsoft Visual Studio .NET, the dali_w32.lib and dalictrl.lib files will not link correctly, and you will have to build them from source in your compiler. 1) Copy dalic.lib and dalic.h to the appropriate directories as described above. 2) Go to the \Development\lib\source\dali_w32\build directory in this package and open the workspace. You should be able to build the dali_w32 release library. 3) Take the dali_w32.lib you have just built and put it in your MSVC default lib directory. Put the dali_w32.h file in the dali_w32\src directory and put it in your default MSVC include directory. Repeat steps 3-4 with the dalictrl library, copying the .lib and .h file to the MSVC directories. Using the Sample Projects ------------------------- Sample projects are located in /Development/Examples. You may open the sample projects from their location (.dsw workspace files.) They should build without error if you have installed the development libs and the ActiveX controls [for the AX demos.] When building the debug version of the samples, you will get a warning related to the microsoft base libraries. These warnings occur because the DALI libraries are linked against the release runtime libraries. They are safe to ignore. The ActiveX controls are more involved to build and run, because they require the user to create a cab file with a signed key file. It is best to begin with the console and MFC demos when learning how to use the client libraries. Most sample projects focus on the dali_w32 and dalictrl libraries. Examples that use only dalic.lib are located in /Development/Examples/DALIC.
Before incorporating the ActiveX controls into your own project you'll
have to register them with the operating system. The /activex
directory that came with DALI includes a register.bat file
which calls regsvr32.exe for each OCX file in that directory. After you
run this the ActiveX controls will be available to applications like
Visual Studio
/samples
Compiled demos and example code showing the features of the components
of Windows software for DALI.