Measurement Computing Personal488 rev.3.0 - Manual (Page 64)

5-10 Using IEEE 488 04-09-01 Personal488 for Windows 95/98/Me/NT/2000
Differences Between 32-bit and 16-bit Driver488 Software
General Differences
The following “bulleted items” are the general differences between the 32-bit Driver488 software
(for Windows 9x and Windows NT) and the16-bit Driver488 software (for Windows 3.X).
With the 32-bit driver:
•
There is no RS-232 serial support.
•
The function Hello now returns two lines of ID: One for the Dynamic Link Library (DLL)
and one for the device driver.
•
The library function prototypes have changed to reflect standard Windows types.
•
The include file has been renamed to: IOTIEEE.H
Specific Differences
The following highlight the specific differences in the API command functions, between the 32-bit
Driver488 software and the16-bit Driver488 software.
Functions Obsolete for 32-bit Drivers
The parameters that these functions set are now set by a provided Windows Control Panel configuration
utility and have therefore been made obsolete for the 32-bit driver.
ClockFrequency
DmaChannel
IntLevel IOAddress
LightPen
SysController
Functions Supported by 32-bit Drivers
The following functions are supported by 32-bit drivers, but not by 16-bit drivers.
MakeNewDevice
OnEventVDM (Console mode applications)
TermQuery
TimeOutQuery
Functions that are Enhanced in the 32-bit Drivers
These are updated functions:
ControlLine
Hello KeepDevice
Programming Language Support
Driver488/W95 and Driver488/WNT both provide native language support for Microsoft Visual C++,
Visual Basic, Borland C++ and Borland Delphi. The following sections describe support for these 32-bit
languages. In some cases, instructions are provided for particular versions of the language.
Although instructions are provided, compiler manufacturers may change their methods, thereby making the
instructions obsolete for a particular compiler. This does not mean that the language and version lack
support. It does, however, indicate that modifications may be needed as directed by the manufacturer of the
compiler.
Microsoft Visual C++
This section is based on use with 32-bit Microsoft Visual C++ V6.0. The procedure may need modified for
other versions of Visual C++ . If this is the case, refer to Microsoft documentation for the required
changes.
Although the project build procedures may differ, earlier 32-bit versions of Visual C++ (V2.0 or later)
should function well.
If using versions earlier than V2.0, e.g., V1.0 or V1.56, support can only be attained by using the 16-Bit
Driver488/W95 Compatibility Layer [see section below] since these versions of Visual C++ are 16-bit
only. In this case, the Visual C++ support from the Driver488/W31 should be used to develop and build
the application.