Thus it was written in the epistle of Dennis Handly,
> Ted Ashton ([log in to unmask]) wrote:
> : It used Xlibtrap to trap such errors as non-acceptable enumerated values
> : and suchlike.
>
> The proper PA-RISC method is to use try/recover and escape.

Yeah, I know, but this program was working fine with XLIBTRAP . . . :-/

> :  AbortFlag is set to 0 and the program dies thusly:
> : **** Bound violation or range error (TRAPS 12).
>
> Where is it doing the range check and what are the allowable ranges?
>
> strread seems to return a 0 on errors, is that valid??

That's the problem.  It appears that even though PASESC.PUB.SYS still contains
the line:

  PasErr_620    = 40632512;  PasErr_BoundsViolation    = 40632512;

bounds violations are not getting handed to XLIBTRAP.  The only way to catch
them is a Try/Recover.  Looks like I've got some recoding before me.

:-(,
Ted
--
Ted Ashton ([log in to unmask]), Info Sys, Southern Adventist University
          ==========================================================
...from the time of Kepler to that of Newton, and from Newton to Hartley,
not only all things in external nature, but the subtlest mysteries of life
and organization, and even of the intellect and moral being, were conjured
within the magic circle of mathematical formulae.
                                        -- Coleridge, Samuel Taylor (1772-1834)
          ==========================================================
         Deep thoughts to be found at http://www.southern.edu/~ashted