Re: DFPORT

Terence,

Might I suggest you go back and read the OP's message? He said he is
compiling some EXAMPLE code and NOWHERE did he mention that he was
interested in COM I/O.

As Craig has pointed out this is a PORTABILITY module and includes many,
many more routines than what your limited experience with the Module would
have you believe.

Ed



Terence wrote:

daniela
I am new to Fortran and I appologize in advance for any trivia I might
ask. I am trying to compile some example code written in Fortran77 that
uses DFPORT, i.e. :
USE DFPORT

What is this library and where can I get it from?
I work on a Windows XP platform.

I researched this subject as best I could over about a six month
period.

My company markets software since 1972, just one program unit of which
reads and writes aynchronous devices through the RS323C ports and which
worked on MS DOS, Windows command lines under Windows on all Intel 286,
386 and pentium computers with all the MS operating systems from DOS.
through Windows 3.1, 95, and up to XP, where it refused to work on only
XP operation systems (so far).

We normally use F77 Fortran and for this one problematic program we
re-wrote the program in F90 and used the CVF (DVF) libraries to bring
in the necessary relationship with the MS API's, using the SPORT
routines provided. These are also available on the Intel version 9
compiler

Note: you HAVE to use F90 or above if you want to refer to a
communications library with the USE instruction.

We found that these routines would not work as WE needed, but they
reportedly do work in other cases cases.

Because we found we could not set some parameters as we required, by
the normal port initialization routine in the SPORT modules, (it
appeared they did not change) we tried to use the MODE command
internally to the program to achieve the same effect. We used the
SYSTEM call to request the MODE command to set up the needed parameters
(baud rate, frame size, number of data and stop bits, parity,time-out
times, etcetera).

We found some port parameters COULD be changed with the MODE command
used internally, others could NOT be changed.
The command seemed to work externally correctly, but internal querying
of the parameters did not give the same values as we set them.

Since we also have the Intel Fortran compiler, we also had a lot of
help from that source (and with the CVF 6.6 compiler). But we were not
able to resolve our problem, to this day.

Note: we COULD communicate between an XP and a 2000 computer, but we
could not change any parameter sucessfully beyond baud rate, and still
get communication. Especially we never got any time-out indications on
disconnecting the cables. On some parity settings there were no
electrical signals on the intergace.

We never got our new program to work on XP operating systems with any
Windows Fortran comper (with appropriate libraries). So our clients
still use a DOS environment for their data collection (using one
dedicated W98 or DOS machine).

The devices our clients want to control are hardware devices where only
certain combinations of signalling parameters were valid for the
equipment.
The manufactures had to come out with a USB-connected device at over 3
times the old price in order to work on windows (and supplied their own
very limited data format Windows XP software for the data collection,
which was unsuitable for our clients).

If you want to work under Windows I think you might have a problem if
the parameters to be used ara unusual. Ours were odd parity, 7 bits,
and 2 stop at any baud rate from 9600 up.

If you have a problem and you are prepared to use DOS mode on an
earlier operating system than XP we can contribute the libraries and
calling conventions for compiling your F77 code.
.
Terence Wright

.

Relevant Pages

  • Re: Seeing VERSIONINFO under Vista?
    ... All operating systems since 1988 have been based on Windows NT. ... Maybe I'll try again with a new Linux distro... ... People told me "You know compiler technology. ...
    (microsoft.public.vc.mfc)
  • Re: hmm..interesting
    ... you've got a discussion of ARM vs Intel architecture here: ... And ARM is rapidly running away from RISC. ... mainstream (many netbooks and smartphones run Linux instead of Windows ... And hardly any C compiler does. ...
    (comp.sys.acorn.hardware)
  • Re: Stalin ported to Windows.
    ... Therefore, the compiler ... Stalin from Scheme sources; it took six hours to generate the C ...   Junia and Reane  got a working Windows port from the C ...
    (comp.lang.scheme)
  • Re: hmm..interesting
    ... work out at more power per Watt than x86. ... mainstream (many netbooks and smartphones run Linux instead of Windows ... the fact that Visual Studio allows you to get away with fairly sloppy ... difficult to find a C compiler that *doesn't* have vendor-specific ...
    (comp.sys.acorn.hardware)
  • Re: C++ programming migration from DOS to Windows
    ... compiler, so the current compiler is quite competitive WRT to ... There are a couple of ports of gcc to Windows. ... Comeau is more or less unique: the best language conformance you can ... IDEs: Microsoft and Borland have both produced decent IDEs in the past, ...
    (comp.lang.cpp)