This CD-ROM last updated at Dec-25-2015 Update ftp://ftp.icpdas.com/pub/cd/IOCard/ ********************************* ** Table of Contents ** ********************************* A. Auto-Run Mechanism. B. Installation Steps. B-1. For DOS users. B-2. For Windows users without MENU. B-3. For Windows users with MENU. B-4. Plug and Play. C. Relative Resources. C-1. Our Web-Site on the Internet. C-2. The Acrobat Reader 4.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? E-3. All of the files on this CD-ROM are Read-Only. ********************************* ** A. Auto-Run Mechanism. ** ********************************* Windows 95/98 and Windows NT 4.0 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 4.0 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 4.0 will force this MENU to be shown on the screen. The structure of this MENU is: |--\Install Toolkits (Softwares) / Manual | |--\ISA Bus DAQ Card | | ( A626/628,A82x, A8111, A812, DIO Series | | TMC-10, ISO Series .... ) | | | |--\Motion Card | | ( Encoder-300, Servo-300, Step-200 ) | | | | | |--\DASYLab | | | +--\The Others | |--\Browse CD-ROM Contents | |--\Contact Us | |--\View Readme.txt <-- this file | | |--\View Our FTP-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 "\NAPDOS\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 4.0. 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 "\NAPDOS\Auto32.exe" manually to force the MENU to be shown. The MENU(program file "\NAPDOS\Auto32.exe") supports Windows 95/98 and Windows NT 4.0 Only. It is a standard Win32 execution file. ********************************* ** B. Installation Steps. ** ********************************* B-1. For DOS user. All of the files on this CD-ROM are Read-Only, and this may cause some problems. Please refer to the Section "E-3. All of the files on this CD-ROM are Read-Only." for detailed information. 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 suing the TMC10) : C:\>d: D:\>cd \NAPDOS\ISA\TMC10\DOS D:\NAPDOS\ISA\TMC10\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 TMC10): ********************************************************************** ** ** ** This batch file will copy the folder into C:\DAQPro\TMC10 ** ** ** ** ** ** 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\TMC10 ** ** ** ********************************************************************** 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:\DAQPro. 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:\DAQPro. For example (Using TMC10) : C:\DAQPro\PCITMC12. Note 1. If the message(Step 3) shows as follows ..... Out of environment space ********************************************************************** ** ** ** This batch file will copy the folder into C:\DAQPro\ ** ......... ........... 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 TMC10) : XCopy /s PCITMC12\*.* C:\DAQPro\TMC10\*.* 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 TMC10 under NT): C:\>d: D:\>cd \NAPDOS\DOWNLOAD\PCI\TMC10\WinNT\Setup D:\NAPDOS\DOWNLOAD\PCI\TMC10\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 "\NAPDOS\Auto32.exe" ). Step 1. Find out the MENU Item that contains the desired Development Toolkit for Windows 95/98 or NT, Please refer to Section "A. Auto-Run Mechanism." Step 2. Change to the desired page. For example (Using the TMC10): (1) Click the menu item "Install Toolkits (Softwares) / Manuals" (2) Click the menu item "PCI Bus DAQ Card" (3) Click the menu item "TMC10" Step 3. Click the menu item to install the Development Toolkit. For example (using TMC10 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 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 TMC10, CD-ROM Drive is D:) : choose the folder "D:\NAPDOS\PCI\TMC10\Win95\Inf" and then select the information file "TMC10.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.icpdas.com E-mail : Service@icpdas.com C-2. The Acrobat Reader 4.0 for Windows. The free Adobe Acrobat Reader 4.0 enables you to view, navigate, and browse PDF files, either inside a Web browser or in a stand-alone application. \NAPDOS\AR5\ar505enu.exe C-4. User Manuals. \NAPDOS\PCI\Manual\PnPInstall.pdf PnP (Plug and Play) information file installation Manual for PCI Bus DAQ Card under Windows 95/98. \NAPDOS\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 and Windows NT. \NAPDOS\PCI\Manual\SoftInstall.pdf The user manual for Development Toolkit for Windows 95/98 and Windows NT installation. \NAPDOS\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. \NAPDOS\PCI\Manual\NAPVIEW.pdf The user manual for NAPVIEW for Windows 95/98 and NT. C-5. Other Documents. \NAPDOS\Y2K\7000Y2K.pdf 7000 Series Modules - Y2K Compliance ********************************* ** D. Layout of this CD-ROM. ** ********************************* D-1. Brief Folder Structure : |--\NAPDOS | |--\ISA <-- ISA Bus DAQ Card | A-626/628, A-8111, A-812PG, A-821PGH/PGL, A-822PGH/PGL, | A-823PGH/PGL, A-826PG, DIO-(24/48/64/96/144), TMC-10 , | ISO-813, ISO-AD32H/AD32L, ISO-DA8/DA16, ISO-LD(LDH/LDL), | ISO-(P32C32/P64/C64/730/P16R16DIO/P8R8DIO) | | | | |--\DASYLab <-- DASYLab 6.x driver,DASYLab 7.x driver,DASYLab 8.x driver,Manual.pdf,ReadMe.txt | | |--\Motion <-- Motion Card | Servo-300, Step-200, Encoder-300 | PISO-PS300 | | | |--\Others <-- DSP-25,PC488,SYS,Win31,WAI16 |--\Linux <-- ixpci-0.6.4.tar.gz,ixpio-0.18.0.tar.gz D-2. Detailed Folder Structure : |--\NAPDOS | | | |--\ISA <-- ISA Bus DAQ Card | | | |--\A-626_628 <-- A-626, A-628 | | |--\DLL_OCX | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT/2000 | | |--\Manual | | |--\ocx | | | | | | |--\A-812 | | |--\DOS <-- Toolkit for DOS | | |--\Lv2K | | |--\Manual <-- User Manual | | |--\OCX | | |--\Win2k | | |--\Win95 <-- Toolkit for Windows 95/98 | | | Provides demos for VB5, VC5, Delphi3, BCB3 | | |--\WinNT <-- Toolkit for Windows NT | | | Provides demos for VB5, VC5, Delphi3, BCB3 | | | | | | |--\A-821 | | |--\DLL | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\OCX | | | | |--\A-822 | | |--\DLL_OCX | | |--\DOS <-- Toolkit for DOS | | |--\LabVIEW | | |--\Manual <-- User Manual | | | | | | | |--\A-823 | | |--\DLL | | |--\DOS <-- Toolkit for DOS | | |--\lv2k <-- A-823PGL/PGH LabVIEW Development Toolkit | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\ocx | | | | | | | | | |--\A-826 | | |--\DLL | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\OCX | | | | | | | | | |--\A-8111 | | |--\DLL_OCX | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual | | | | | | | |--\DIO <-- DIO-(24/48/64/96/144) | | | P16R16-DIO/P8R8-DIO | | |--\DLL | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\Lv2000 <-- Toolkit for LabVIEW Win2000 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\ocx | | | | | | | | |--\ISO <-- ISO-(P32C32/P64/C64/730/P16R16DIO/P8R8DIO) | | |--\DLL | | |--\DOS <-- Toolkit for DOS | | |--\lv2k <--ISO LabVIEW Development Toolkit | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\OCX | | | | | |--\ISO-813 | | |--\Diag | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\ocx | | |--\Win95 <-- Toolkit for Windows 95/98 | | | Provides demos for VB5, VC5, Delphi3, BCB3 | | |--\WinNT <-- Toolkit for Windows NT | | | Provides demos for VB5, VC5, Delphi3, BCB3 | | | |--\ISO-AD32 | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\OCX | | |--\Win95 <-- Toolkit for Windows 95/98 | | | Provides demos for VB5, VC5 | | |--\WinNT <-- Toolkit for Windows NT | | | Provides demos for VB5, VC5 | | | |--\ISO-DA <-- ISO-DA16, ISO-DA8 | | |--\DOS <-- Toolkit for DOS | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\LvNT <-- Toolkit for LabVIEW NT | | |--\Manual <-- User Manual | | |--\OCX | | |--\Win95 <-- Toolkit for Windows 95/98 | | | Provides demos for VB5, VC5, Delphi3, BCB3 | | |--\WinNT <-- Toolkit for Windows NT | | | Provides demos for VB5, VC5, Delphi3, BCB3 | |--\ISO-LD <-- ISO-DA16, ISO-DA8 | | |--\DOS <-- Toolkit for DOS | | |--\ISOLD_2K | | |--\ISOLD_98 | | |--\ISOLD_NT <-- Toolkit for Windows NT | | | Provides demos for VB5, VC5, Delphi3, BCB3 | | |--\Manual <-- User Manual | | |--\OCX | | | | | |--\Manual | | |--\Calling_DLL_functions_in_LabVIEW.pdf | | |--\Calling_DLL_functions_in_VB_VC_Delphi_BCB.pdf | | |--\ISA_AddDevice.pdf | | |--\ISA_AddDevice_Win2K3_cht.pdf | | |--\ISA_AddDevice_Win2K3_eng.pdf | | |--\OCX(ActiveX)_Installation_in_VB_Delphi_BCB.pdf | | |--\PCI_ISA_PnP_Driver_Installation_in_Win9x_2K_XP.pdf | | |--\Software_Installation_Guide_in_Win32.pdf | | |--\Troubleshooting_for_ISA_DAQ_card_050829.pdf | | |--\TroubleShooting_PCI_ISA_in_Win32_Resource_Conflict.pdf | | |--\Use_TurboC_With_PIODIO.pdf | | |--\using_dll_ in_vc++.net_2005_cht.pdf | | |--\using_dll_ in_vc++.net_2005_eng.pdf | | |--\Using_DLL_in_CShape.NET_2005_cht.pdf | | |--\Using_DLL_in_CShape.NET_2005_eng.pdf | | |--\Using_DLL_in_VB.NET_2005_cht.pdf | | |--\Using_DLL_in_VB.NET_2005_eng.pdf | | | | | |--\TMC10 | | |--\DOS <-- Toolkit for DOS | | | +--\Install.bat <-- Batch file for installation | | |--\Lv95 <-- Toolkit for LabVIEW 95/98 | | |--\Manual <-- User Manual | | |--\OCX | | |--\Win95 <-- Toolkit for Windows 95/98 | | | Provides demos for VB5, Delphi3, BCB3 | | |--\WinNT <-- Toolkit for Windows NT | | | Provides demos for VB5, Delphi3, BCB3 | | | |--\MOTION | |--\ENC300 | | |--\DOS <-- Toolkit for DOS | | | |--\C | | | |--\lib | | | |--\manual | | | | | +--\Manual <-- User Manual | | +--\ENC3.PDF <-- Hardware & Toolkit Manual | | | | | |--\Win95 <-- Toolkit for Windows 95/98 | | | Provides demos for VB5, Delphi3, BCB3 | | +--\WinNT <-- Toolkit for Windows NT | | Provides demos for VB5, Delphi3, BCB3 | | | |--\Manual <-- The user manual | | |--\CallDLL.pdf | | |--\NAPVIEW.PDF | | |--\PnPInstall.pdf | | |--\ResCheck.pdf | | |--\SoftInst.pdf | | | |--\SERVO300 | | |--\DOS | | |--\Manual | | |--\Win95 | | |--\WinNT | | | |--\STEP200 | | |--\DOS | | |--\Manual | | |--\Win95 | | |--\WinNT | | |--\DASYLab <-- DASYLab 6.x driver,DASYLab 7.x driver,DASYLab 8.x driver,Manual.pdf,ReadMe.txt |--\Linux | |--\Others |--\DSP-25 |--\PC488 <-- ISA Bus IEEE-488 Coard |--\SYS |--\W31 <-- A628/A821,A822,DIO,DIO144,TMC10 |--\WAI16 ********************************* ** 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. The Development Toolkit for Windows 95/98 and NT provides demo programs for VB5 ( Visual Basic 5.0 ), VC5 ( Visual C++ 5.0 ), BCB3 ( Borland C++ Builder 3.0 ) and Delphi3 ( Delphi 3.0 ). demo programs for some programming languanges require the proper environment to works well. For Visual Basic 5: (needs VB5) These executable demo programs require the Uisuel environments of the Visual Basic 5 to work well. 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++ 5: 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 3: (needs BCB3) The executable demo programs require the BCB3 environment to work well. 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 3: The demo programs for Delphi 3 can be run in stand-alone mode. (But, also needs the device drivers and some Win32 DLLs). For LabVIEW 4: (needs LabVIEW4) The demo programs require the LabVIEW4 environment to work well. 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) E-3. All of the files on this CD-ROM are Read-Only. All of the files on this CD-ROM will be changed to Read-Only automatically. This may cause some problems when the user tries to overwrite the file. For example, when the user opens the project and compiles this project . The compiler will try to overwrite the output files. And this will cause problems. To solve the problem, the user can use the program "attrib.exe" to reset the attributes of these files. This program "attrib.exe" is the companion file of MS-DOS. (Windows 95/98 and NT also contains this program.) For example (Using the A-821 Development Toolkit for DOS, after installaion): C:\DAQPro\A821\>attrib /s -r *.* This command will remove the attribute "Read-Only" for all the files (Including all of the files under sub-directories). In the installation batch file (Insall.bat of all of the Toolkits for DOS), if we add the following command line to try to remove the attribute "Read-Only" after these files have be copied into the user's harddisk. This process may cause the problem "Bad command or file not found" if the program "attrib.exe" doesn't exist in the user's system. For proper usage well, please check that the program does exist in the user's system, and the directory is included in the search path. ********************************* *********************************