********************************************************* ** ** ** OMEGA ENGINEERING, INC. ** ** OME Series of Data Acquisition ** ** Revision : 2.0.1 ** ** Date : Mar-17-2008 ** ** ** ********************************************************* This CD-ROM last updated on Mar-17-2008 Check for recent updates on ftp://ftp.omega.com ********************************* ** Table of Contents ** ********************************* A. Auto-Run Mechanism. B. Installation Steps. B-1. For DOS users. B-2. For Windows users without MENU (Not Auto-Run). B-3. For Windows users with MENU (Auto-Run). B-4. Plug and Play. C. Relative Resources. C-1. Our Web-Site on the Internet. C-2. The Acrobat Reader 6.0 for Windows. C-3. User Manuals. C-4. Other Documents. D. Layout of this CD-ROM. D-1. Brief Folder Structure. D-2. Detailed Folder Structure. E. Appendix. E-1. LabVIEW? E-2. Do Demo program need other files? ********************************* ** A. Auto-Run Mechanism. ** ********************************* Windows 95/98/NT/2000/XP provides the Auto-Run Mechanism, and this CD-ROM supports it. That is, when the user insert this CD-ROM into the CD-ROM Drive, the Windows 95/98 or Windows NT/2000/XP Operating System will read and interpret the "AutoRun.inf". And then run the program which is specified by the "AutoRun.inf". This CD-ROM provides a MENU (program file), the Auto-Run Mechanism under Windows 95/98 and Windows NT/2000/XP will force this MENU to be shown on the screen. The structure of this MENU is: |--\Install Toolkits (Softwares) / Manual | |--\PCI Bus DAQ Card | | | |--\ISA Bus DAQ Card | | | +--\Others | |--\Browse CD-ROM Contents | |--\Contact Us | |--\View Readme.txt <-- this file | | |--\View Our Web-Site on the Internet | +--\Install Acrobat Reader 6.0 ( The user manual is written in .PDF format, the user need the Acrobat reader to read the user manual. ) The MENU ( program file "\OMEGA\Auto32.exe" ) allows the user to easily install the development toolkits simply using the Point-and-Click method. The MENU will be launched automatically after the user inserts this CD-ROM into the CD-ROM Drive under Windows 95/98 and Windows NT/2000/XP.The Auto-Run mechanism can be enabled/disabled by system settings (set by user). If this MENU does not shown in the screen when the user inserts this CD-ROM, the user can also run the program "\OMEGA\Auto32.exe" manually to force the MENU to be shown. The MENU(program file "\OMEGA\Auto32.exe") supports Windows 95/98 and Windows NT/2000/XP Only. It is a standard Win32 execution file. ********************************* ** B. Installation Steps. ** ********************************* B-1. For DOS user. The MENU (Win32 Program) is not suported in an MS-DOS environment. Step 1. Find the folder that contains the desired Development Toolkit for DOS. Please refer to Section "D. Layout of this CD-ROM." Step 2. Change the directory to desired folder. For example (CD-ROM Drive is "D:" and using the PCI-TMC12) : C:\>d: D:\>cd \OMEGA\PCI\PCI-TMC12\DOS D:\OMEGA\PCI\PCI-TMC12\DOS\>_ Step 3. Run the batch file "Install.bat" to install the Toolkit for DOS. The batch file will show the message to prompt you to install. For example (Use PCI-TMC12): ********************************************************************** ** ** ** This batch file will copy the folder into C:\OMEGA\PCITMC12 ** ** ** ** ** ** The user can also change the destination by specifying the ** ** parameter on the command line. ** ** ** ** For example: ** ** install D:\MyProj ** ** ** ** This will force the copying of the folder into D:\MyProj\PCITMC12** ** ** ********************************************************************** Please press [Ctrl] + [C] to cancel this process, or Press any key to continue . . . Step 4. After the message is shown on the screen, please press [Enter] key to continue installation. And, then the folder of Development Toolkit for DOS will be copied into C:\OMEGA. Or, the user can press [Ctrl] + [C] to cancel this installation. Step 5. After installation, the user can find the folder of Toolkit for DOS under C:\OMEGA. For example (Using PCI-TMC12) : C:\OMEGA\PCITMC12. Note 1. If the message(Step 3) shows as follows ..... Out of environment space ********************************************************************** ** ** ** This batch file will copy the folder into C:\OMEGA\ ** ......... ........... Please configure the system's "Config.sys" to provides more environment space. For example (if the command.com is under C:\) : shell=C:\Command.com /e:4096 Restart the system and run the install.bat again. Note 2. The user can also copy the folder manually. For example (Using PCI-TMC12) : XCopy /s PCITMC12\*.* C:\OMEGA\PCITMC12\*.* B-2. For Windows users without MENU (Program). Step 1. Find the folder that contains the desired Development Toolkit for Windows 95/98 or NT, Please refer to Section "D. Layout of this CD-ROM." Step 2. Change the directory the desired folder. For example (CD-ROM Drive is "D:" and using the PCI-TMC12 under NT): C:\>d: D:\>cd \OMEGA\DOWNLOAD\PCI\TMC12\WinNT\Setup D:\OMEGA\DOWNLOAD\PCI\TMC12\WinNT\Setup\>_ Step 3. Run the installation file "Setup.exe" to install the Toolkit for Windows 95/98 or for Windows NT. Step 4. Please follows the message prompts in order to chooses the directory in which to install, and complete the installation steps. B-3. For Windows user with MENU (Program "\OMEGA\Auto32.exe" ). Step 1. Find out the MENU Item that contains the desired Development Toolkit for Windows 95/98/NT/2000/XP, Please refer to Section "A. Auto-Run Mechanism." Step 2. Change to the desired page. For example (Using the PCI-TMC12): (1) Click the menu item "Install Toolkits (Software) / Manuals" (2) Click the menu item "Plug-in Biards for the PCI-bus" (3) Click the menu item "PCI-TMC12" Step 3. Click the menu item to install the Development Toolkit. For example (using PCI-TMC12 under Windows NT) : (1) Click the menu item "Insall Toolkit for Windows NT" (2) The installation file "Setup.exe" will be launched. Step 4. Please follows the message prompts in order to choose the directory in which to install, and complete the installation steps. B-4. Plug and Play Windows 95/98/2000/XP provides a PnP (Plug and Play) mechanism, and the PCI Bus Series DAQ Cards support this mechanism. After the user plugs the PCI DAQ Card on the main-board, the PnP mechanism will detect the bus to find the new devices. If this mechanism is not launched automatically, the user can also launch the program "Add New Hardware" from the folder "Control Panel" manually. Please follow the message prompts to choose the folder which contains the PnP Information file (.INF), and complete the installation steps. For example (using PCI-TMC12, CD-ROM Drive is D:) : choose the folder "D:\OMEGA\TMC12_Win95\Inf" and then select the information file "TMC12.INF". After completing the setting of the PnP Information file, Windows 95/98 will record the information of the specific PCI DAQ Card in the database, and allocate the resource (I/O Port, IRQ number, DMA) to this card. The PnP mechanism reads the .INF file, and then (1) Causes the PCI Card to be identified by the system. (2) Makes the system allocate resources to this PCI Card. ********************************* ** C. Relative Resources. ** ********************************* C-1. Our Web-Site on the Internet. For the latest information, please refer to our web site. Web Site: http://www.omega.com E-mail : das@omega.com C-2. The Acrobat Reader 5.05 for Windows. The free Adobe Acrobat Reader 5.05 enables you to view, navigate, and browse PDF files, either inside a Web browser or in a stand-alone application. \OMEGA\Ar6\AdbeRdr60_enu_full.exe C-4. User Manuals after install \OMEGA\PCI\Manul\PnPInstall.pdf PnP (Plug and Play) information file installation Manual for PCI Bus DAQ Card under Windows 95/98/NT/2000/XP. \OMEGA\PCI\Manual\ResCheck.pdf The user manual for resources (I/O Port, IRQ number, DMA) checking for PCI/ISA Bus DAQ Card under Windows 95/98/NT/2000/XP. \OMEGA\PCI\Inf\SoftInst.pdf The user manual for Development Toolkit for Windows 95/98 and Windows NT/2000/XP installation. \OMEGA\PCI\Manual\CallDLL.pdf The user manual for programmers to using VC5, VB5, Delphi3 and BCB3 to call the functions of Win32 DLLs. It is for Development Toolkits for Windows 95/98 and NT/2000/XP. ********************************* ** D. Layout of this CD-ROM. ** ********************************* D-1. Detailed Folder Structure : |--\OMEGA | |--\Linux | |--\PCI | | +--\omega-ixpci-0.16.0.tar.gz <-- Linux driver of PCI-1002/1202/1602/180x,TMC12A | +--\PIO | | +--\omega-ixpio-0.19.3.tar.gz <-- Linux driver of PISO-813,PIODA,PIODIO | *--\ISA\ | +--\omega-ixisa-0.16.0.tar.gz <-- Linux driver of A8111 A822 A826 | |--\PCI <-- PCI Bus DAQ Card | |--\Manual <-- The user manual and reference document | |--\PCI-1002 <-- PCI-1002L/PCI-1002H | | |--\DOS Ver(1.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(3.02.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | | |--\LabView Ver(3.00.00) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | | +--\Manual Ver(1.01) <-- User Manual | | | |--\PCI-1202 <-- PCI-1202L/PCI-1202H | | |--\DOS Ver(2.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(2.35.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | | |--\LabView Ver(2.20.01) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | | +--\Manual Ver(3.02) <-- User Manual | | | |--\PCI-1602 <-- PCI-1602/1602F | | |--\DOS Ver(2.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(2.35.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | | |--\LabView Ver(2.20.01) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | | +--\Manual Ver(3.02) <-- User Manual | | | |--\PCI-180X <-- PCI-1800L/PCI-1800H, PCI-1802L/PCI-1802H | | |--\DOS Ver(2.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(2.35.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | | |--\LabView Ver(2.20.01) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | | +--\Manual <-- User Manual | | | +--\PISO-813 | | |--\DOS Ver(1.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(2.02.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | | |--\LabView Ver(2.20.01) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | | +--\Manual <-- User Manual | | | +--\PIO-DIO | | |--\DOS Ver(1.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(2.10.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | | |--\LabView Ver(1.10.00) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | | +-\Manual <-- User Manual | | | *--\PIO-DA | |--\DOS Ver(1.0) <-- Toolkit for DOS | |--\DLL_OCX Ver(2.25.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | Provides demos for VB6, VC6, Delphi4, BCB4, C#.NET 2005 and VB.NET 2005 | |--\LabView Ver(1.10.00) <-- Toolkit for LabVIEW 95/98/ME/NT/2K/XP | +-\Manual <-- User Manual | |--\Dasylab | |--\Dasylab_Win2k_XP_7x <-- Toolkit for Dasylab 7.0 Windows 2000/XP | |--\Dasylab_Win2k_XP_8x <-- Toolkit for Dasylab 8.0 Windows 2000/XP | |--\Dasylab_Win95__7x <-- Toolkit for Dasylab 7.0 Windows 95/98 | *--\Dasylab_WinNT_7x <-- Toolkit for Dasylab 7.0 Windows NT | |--\Daughter_Board <--Hardware Manual of DB-37/DB-20/DN-37/ADP-20,DB-16P/DB-8R, DB-8225, | DB-16R/DB-24R/DB-24RD, DB-24PR/DB-24PRD/DB-16P/DB-24C/DB-24POR, | DB-24SSR/DB-16P/DB-24P | |--\ISA <-- ISA Bus DAQ Card | |--\Manual <-- The user manual and reference document | | | |--\A8111 <-- A8111 | | |--\DOS Ver(1.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(2.03.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi5, BCB3. | | |--\LabView Ver(3.00.00) <-- Toolkit for LabVIEW NT/95/98/2000/XP | | *--\Manual <-- User Manual | | | |--\A822 <-- A822 | | |--\DOS Ver(2.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(3.23.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi4, BCB4. | | |--\LabView Ver(2.20.01) <-- Toolkit for LabVIEW NT/95/98/2000/XP | | *--\Manual <-- User Manual | | | |--\A826 <-- A826 | | |--\DOS Ver(2.0) <-- Toolkit for DOS | | |--\DLL_OCX Ver(3.12.00) <-- Toolkit for Windows 95/98/ME/NT/2K/XP | | | Provides demos for VB6, VC6, Delphi3, BCB3. | | |--\LabView Ver(2.20.01) <-- Toolkit for LabVIEW 95/98/NT/2000/XP | | *--\Manual <-- User Manual ********************************* ** E. Appendix. ** ********************************* E-1. LabVIEW? LabVIEW is a industrial, graphics-based programming system developed by National Instruments. With LabVIEW, the user can quickly design the user interface and control program as a block diagram. NAPVIEW supports many driver VIs and demo VIs which can be used by LabeVIEW 4.0. E-2. Do Demo programs need other files? For DOS: The demo programs of Development Toolkit for DOS do not need any external files to work. They're merely stand-alone executable programs . For Windows 95/98 and NT: All of the demo programs of Development Toolkit for Windows 95/98 and NT needs some device drivers(.sys or .vxd files) and some Win32 DLLs to work(access the device). And some device drivers needs to be registered in the system. For detailed information, please refer to the "Readme.txt" of each Development Toolkit for Windows 95/98 and NT/2000/XP. The Development Toolkit for Windows 95/98 and NT provides demo programs for VB5 ( Visual Basic 6.0 ), VC5 ( Visual C++ 6.0 ), BCB3 ( Borland C++ Builder 3.0 ) and Delphi3 ( Delphi 3.0 ). The demo programs require the proper programming environment to run them successfully. For Visual Basic 6: (needs VB6) These executable demo programs require Visual Basic 5 environment. That is, the user needs to install Visual Basic 5 into the system before running the executable demo programs.(need the device drivers and some Win32 DLLs) For Visual C++ 6: These demo programs for Visual C++ 5 were written in the SDK style, it does not uses the MFC library or others. Thus, the user can run the demo programs stand-alone without other files. (But, also needs the device drivers and some Win32 DLLs) For Borland C++ Builder 4: (needs BCB4) The executable demo programs require BCB3 environment. That is, the user needs to install Borland C++ Builder 3 into the system before running the executable demo programs. The user can also set the PROJECT's OPTIONS to make the executable program run in stand-alone mode. For more information , please refer to the user manual of the Borland C++ Builder 3. (needs the device drivers and some Win32 DLLs) For Delphi 4: The demo programs for Delphi 4 can be run in stand-alone mode. (But, also needs the device drivers and some Win32 DLLs). For Visual Basic.NET 2005: (needs VB.NET2005) These executable demo programs require MS .NET Framework 2.0 environment. That is, the user needs to install Visual Basic.NET 2005 into the system before running the executable demo programs.(need the device drivers and some Win32 DLLs) For Visual C#.NET 2005: (needs CSharp.NET2005) These executable demo programs require MS .NET Framework 2.0 environment. That is, the user needs to install Visual C#.NET 2005 into the system before running the executable demo programs.(need the device drivers and some Win32 DLLs) For LabVIEW 4: (needs LabVIEW4) The executable demo programs require LabVIEW4 environment. That is, the user needs to install LabVIEW 4.0 into the system before running the demo programs. (needs the device drivers and some Win32 DLLs) ******************************************************************