RB> Only if he is writing a DOS or Win 16 program.  Unfortunately for
RB> JK, Borland chose not to include inportb or outportb in their Win 32
RB> RTL.
 
RB> Of course, the reason is that writing to ports is not defined in
RB> the Win 32 API, since it is illegal under NT.  Borland apparently
RB> decided that this means that the functions should not be included at
RB> all.
Borland didn't do anything.  It was Microsoft who changed the paradigm
for async access to ports.  The 32-bit paradigm is much more robust but
completely different (I just wish that Microsoft had renamed [even
slightly] functions that carry the same name in both systems, like
BuildCommDCB()).
 * KWQ/2 1.2i *
--- FLAME v1.1
---------------