the correct one would be AssignFIle..
That is bogus and nonsense at the same time, Jamie.
In mode TP this code should compile.
106 indicates a conversion error, see manual.
The real reason is probably related to real(48) or codepage.
Take your antics elsewhere...
You are pretty ignorant at times Thaddy, actually most of the time.
Being an old program like it is, I used OLD documentation which falls under IO errors, 106 = bad Input..
cause by incorrect file handling and reading the input data incorrectly..
Assuming it worked in the past there is no reason why Read and Readln won't still read the numerical values now.
of course there is always the chance of the wrong line endings being used but I doubt that.
Like I said, bad File handling due to improper file control..
and not using the proper Assignfile over assign can cause random issues , I've seen it and obviously you haven't. So much for being so savy in code.
I am sure you will reply to increment your POST numbers, that seems to be the tool of the trade these days to gain popularity is the POSTed message you have left. Many of them not worth reading.
And btw, I looked at your Safe Pointer code, what a mess, I think I'll overwrite it with proper code that does lard up the CPU.