Search results for query: *

Is there a BIOS or DOS call to return the address (e.g. '0x378' or '0xd010'(PCIe)) of any LPT ? I need to be able to determine this at run time, rather than using the Device Manager and then hard coding it before hand.

Never mind. I unpacked with 7-ZIP and installed Fortran 5.1. I'll try it tomorrow. Thanks for all your help. Joe.

DOSBOX X just allows for printer output. I need full access to the bidirectional parallel port for read/write data, write control, and read status/sense. I have found the windows driver Inpout.sys for /windows/system32/drivers and a c++ program to read/write lpt1 directly in windows7, so I will...

Thanks. DOSBOX does not handle the parallel port. I can't use it for some of my programs, so I don't bother with it at all. I will check out the link you gave. Repeating: the Fortran 4.1 version that I have works perfectly under Windows 7x86, but does not work under Windows 7x64 I have checked...

TMP E:\FORTRAN and LIB E:\FORTRAN were set in the Environment Variables. Joe.

I get an f1042 error during a compile running under Win7x64 with NTVDMx64 installed: E:\DECBAL>FL /FPi /c /Fs DECBAL.FOR Microsoft (R) FORTRAN Optimizing Compiler Version 4.00 Copyright (c) Microsoft Corp 1987. All rights reserved. DECBAL.FOR fatal error C1042: cannot open compiler...

Using your link, I did not come across the word "download" anywhere. But, my question begs.

I have been using Intel Fortran v4 for about 30 years now from MS-DOS thru Windows 2000, XP, 7x86 with no problems at all. But now with Windows 7x64 I get a message to the effect that 16 bit programs/compilers/ will not run on Windows 7x64, and, further, nothing can be done about this as far as...

I am using MS Fortran 4.1 from 1987. As it is, my two lines of code (the Read and the Format) work fine. All of the excess data input beyond the CRLF can be ignored. The next read starts at the next sequential record which is correct. I was just confused by all the extra data input and afraid of...

There is no difference. I left out the OPEN statement. CHARACTER*1 BUFFER(1024) ... OPEN(UNIT,FILE='....') ... READ(UNIT,100)BUFFER 100 FORMAT(1024A1) ... WRITE(*,900)BUFFER 900 FORMAT(1X,1024A1) ... I did trim the write statement to 128 chars so as not to fill the screen. However, I just found...

Yes, I am reading a .txt file with an open(unit,file='xxx.txt') This defaults to sequential formatted with no record size. Each read is reading to the iolist "length", and repeating the format(A) without stopping at the EOR. The key is the iolist, in this case buffer, which has no explicit...

Using a FORMAT(A) results in the repetition of the edit descriptor; the buffer is filled until an EOF. The syntax of Aw where w is omitted results in a w equal to the number of chars in the iolist, in this case 1024. I'm still trying other things.... Thanks, Joey.

Thanks xwb, I cannot understand gullipe's code. Apparently, my simple fortran code needs to be changed to something complex for the sake of "structural elegance". I am using MS fortran 4.1 and it doesn't appear to support this structure. I will try using just the single A format and hope that...

character*1 buffer(1024) ... ... data buffer/1024*'z'/ ( as a telltale to show how much has been read per read) ... ... read(unit,100)buffer 100 format(1024a1) ... .... I had thought that an EOR would stop the read with only the one record and the rest of the buffer would be z's, but it...

Using MS Fortran 4.1, I am trying to read variable length formatted sequential records from a file. Each record is terminated by a CRLF. I set up a buffer of 1024 bytes (expected max), and want to read each record one-at-a-time, but I can't seem to properly set up the read and format statements...