with certain types of UARTS, Windows does not properly implement
hardware handshaking with the controller. Some of the handshaking
functions, therefore, have been taken over by our DLLs. This
change affects Windows 3.x (16-bit) and Windows 95 (32-bit). It
does not affect Windows NT.
A change was made to the Windows 95 device driver GALIL.VXD to fix
a problem with Data Record Access on the DMC-1700. If you used
FIFO as the access method and chose a relatively slow refresh rate
(> 128ms), the response time from the API function
DMCRefreshDataRecord would be much to slow. This problem has been
corrected.
A new error code, DMCERROR_BUSY, was added to inform you if the PC
can not write to the controller because it is busy. Formally, this
condition would be reported as a DMCERROR_TIMEOUT.
2.61 January 27, 1997
The DMCSERxx.DLLs were modified so that they send one character at
a time to the controller, instead of a stream. This is because on
most PCs with buffered UARTS, the UARTS do not handshake properly
with the controller and characters can be lost. A problem was also
fixed in DMCSER32.DLL with the DMCClear function. This function
would return a non-zero return code even if there was no error.
The DMCCommand function was enhanced to allow commands strings up
to 1024 characters in length to be sent to the controller at one
time. The previous limit was 256.
The device drivers were modified to allow a cleaner shutdown of the
interrupt thread when terminating a session (calling DMCClose).
This will insure that the interrupt thread does not get hung if
interrupts are not properly configured.
Two new functions, DMCArrayDownload and DMCArrayUpload, were added
to facilitate in downloading and uploading array data to/from the
