external compiler support for parallel port I/O on NT

[Lawrence Shing]

I am interested in I/O with the parallel port on NT. I am able to use
inp, outp in CVI, and they operate the parallel port as expected.

I then generated a library file with a function called tmp_outp() which
just calls outp. This also works in CVI, and the port reacts.
However, when I generate a .lib for use in an
external compiler (for Borland), the function tmp_outp() is called
without an error, EXCEPT, they do not operate the parallel port.

I believe the .lib file I create is OK, because I can link it in a simple
CVI program and operate the parallel port.

Another alternative is to use TVic libraries to do the I/O, but
I was hoping to just use the CVI libraries, since they also include
all the
GPIB, DAQ calls I require.

any clues?

Lawrence Shing

[Peter Charlton]

I have am also experiencing problems using inp and outp on a parallel port
device. (Under 95/98 and NT).

With run debug options on anything other than None my programs work fine.
However when set to none (as is forced when creating standalone executable)
no errors messages are generated but calls do not function correctly!!! if
at all!!!

Help!!!!
Peter Charlton


"Lawrence Shing" wrote:
>>I am interested in I/O with the parallel port on NT. I am able to use>inp,
outp in CVI, and they operate the parallel port as expected.>>I then generated
a library file with a function called tmp_outp() which>just calls outp.
This also works in CVI, and the port reacts.> However, when I generate a
.lib for use in an>external compiler (for Borland), the functi
on tmp_outp()
is called>without an error, EXCEPT, they do not operate the parallel port.>>I
believe the .lib file I create is OK, because I can link it in a simple>CVI
program and operate the parallel port. >>Another alternative is to use TVic
libraries to do the I/O, but>I was hoping to just use the CVI libraries,
since they also include>all the GPIB, DAQ calls I require.>>any clues?>>Lawrence
Shing

[Steven Wellink]

I have a similar problem when using CreateProcess SDK-function which I use
as alternative for ANSI-C system to allow me to redirect stdout/stderr. (To
an anonymous pipe, I can read from). Works fine when debugging is turned
on, but fails in standalone executable!

Any progress on this subject? (I though the only difference between debugging
on/off was the user-protection...)

Regards,
Steven Wellink