Posted by Barbara Brazil on May 16, 2005 at 15:26:33:
In Reply to: NEW INSTALLATION OF COMET 2005 posted by STEVEN HAGEN on May 16, 2005 at 13:17:07:
Steve:
Well, believe it or not, some of what you're seeing makes sense. Running of the utilities relies heavily on COMMON data being passed back and forth from QTILITY and it's overlays (the utilities themselves). By skipping QTILITY and jumping directly in to one of the overlays, you've messed this communication up. The utilities all check for valid COMMON and if they don't see what they expect, they bail out and return to QTILITY. Of course, now you've gotten there thru the back door, so things really didn't get initialized properly. All bets are off from here on. So, don't waste any time fretting over this behavior.
What's troubling is why you can't run QTILITY directly. Is the E00 being reported by QTILITY or QMONITOR? If it's from QMONITOR it's a problem with RUN. If it's from QTILITY, get the source to QTILITY in the latest XTL folder. Compile it to a listing file and find out what's going on at the address where the error is reported. We'll take it from there.
bb