Posted by Grant Foraker on July 24, 2012 at 13:27:27: Uploaded files: 4
Wrote a program to force an E32 and ran it in Comet16 and Comet32.
Comet16 - the first 6 lines gives me 90%+ of what I need to know to find the problem. The User Address lines comes into play the rest of the time. A user can capture the error screen and send it to me. Usually I don't have to remote connect and check QERRLOG.
Comet32A - the pop up only has two of the six items I want to see. No help at all.
Comet32B - I have to connect to the customer and check ErrLog to get more info. The program name and E32 are correct. The file is usually right but sometimes not. The rest is worthless.
1) the LUN is wrong
2) the KEY is missing
3) the DIR is missing (not usually important)
4) the "Opcode" is always 75, so why bother. I want to see the Sys Function
So now I have to compile the program to get a source list with addresses and start debugging from there. A step that was less than 10% in Comet16 has been elevated to 99% in Comet32
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.