03-01-2006 03:39 PM
03-02-2006 07:58 AM
03-02-2006 09:09 AM
Hi Robert,
Thanks for the quick response.
Yeah I've sifted through all of that stuff with a fine tooth comb just hoping that I would see TCIB.C or TCIB.ASM or even a document describing how to interface with the GPIB.COM driver without using the language interface.
TCIB.OBJ is the language interface that I am currently using. The reason I need the source code for the OBJ file is so that I can modify it to work with the Borland DPMI/16 server. Another acceptable solution for me would be if you had a documents describing the various structures and functions needed to communicate with the GPIB.COM driver. The best solution would be if you had a DPMI/16 compatible version of the language interface, but I determined that this was very unlikely. Any further help would be greatly appreciated.
Thanks.
Trevor Lea
03-02-2006 06:14 PM - edited 03-02-2006 06:14 PM
For DOS-based GPIB application, an alternative solution is use the Universal Language Interface. The ULI comes with a TSR (Terminate Stayed Resident) program, which wraps NI-488.2 DOS API into the standard DOS INT21h API - actually as file I/O calls. Although I have no experience to use the old layer with any DOS extenders, DMPI programs may be able to call DOS API which is implemented as in x86 real mode.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E18756A4E034080020E74861
このメッセージは 03-03-2006 09:16 AMに Makoto が編集しています。
03-03-2006 09:38 AM
Makoto,
Thank you very much. I believe that this will do the trick if the communication performance turns out to be adequate. Most of the DOS int 21 functions are supported by the Borland DPMI server, so this should work fine.
Thanks again,
Trevor Lea