Re: DOS 4gl problem

In article <502@rhlab.UUCP> kuhn@rhlab.UUCP (mjk Michael Kuhn) writes: >Informix-4GL 1.10.06E IBM PS/2 Series >While running an application I get this error > > DOS/16M: Unexpected interrupt = 000D at 0090;09C6 > > code=0000 ss=0328 ds=0328 es=0000 > ax=0000 bx=0000 cx=094e dx=0000 > sp=58D* bp=58EA si=0005 di=0001 > >Whose problem is this? > Hardware, DOS, Informix maybe, maybe, and maybe. A DOS/16M unexpected interrupt just means that you did something naughty in protected mode. It's the moral equivalent of a core dump in UNIX. It could be something illegal you've done in the code. It could be a hardware/BIOS incompatibility. It could be programs colliding in extended memory. It could even be sunspots. You may need to set the DOS16M environment variable to identify the machine type (I think to "2" for 286-based PS/2s and "3" for 386/486), especially if it's a newish model. Also, try running "PMINFO" and see if DOS/16M is identifying the CPU and memory types/amounts properly. In other words, just approach the problem as you would a core dump in UNIX (well, assume no debugger): isolate the offending code, check it carefully, perhaps rewrite using variations on the theme. >Michael J. Kuhn Consultant phone:410-254-7060 >Email: rhlab!kuhn@uunet.uu.net or uunet!rhlab!kuhn > c/o Baltimore Rh Typing Laboratory, Inc. phone:410-225-9595 -- Alan Denney aland@informix.com {pyramid|uunet}!infmx!aland "In the cafeteria just after lunch, (well, not *just* after, more like *during* lunch, about 12:28; say 12:30, give or take a few minutes), I leaned back in my chair (it was one of those aluminum chairs, good strength-to-weight, like titanium but not quite; but then of course titanium would be a bit of an overkill). Anyway, I heard one of the girls talking about how boring she thought engineers could be."