|
Post by billgrantford on Feb 6, 2023 21:32:09 GMT 1
I've seen 2 errors related to illegal opcode:
1.) Illegal opcode FF at 6D00:F977 This code was related to closing a customer ticket with 69 lines of parts. The ticket will not close, I have to use a 32 bit system to close the ticket.
2.) Illegal opcode 63 at 2020:1A5C This Code I see when adding parts to a ticket, in the 6x something line item. We can use a 32 bit system to continue the work, once we add a single part we can continue on the 64 bit system adding part lines.
Both Codes only appear on the 64 bit system ADMIN=ON IDLELOW=25000
Thanks Mike
|
|
|
Post by Jos on Feb 6, 2023 22:55:08 GMT 1
Sorry to say, but illegal opcodes FF and 63 don’t clarify the actual cause. Those are just illegal the moment your program tries to execute them. Essentially merely an indication the program is running haywire.
It shouldn’t matter vDos running in 32 or 64-Bit Windows. ADMIN=ON or IDLELOW=25000 is neither relevant.
I could send you my vDos development version. A recent report revealed a mishap promoting an exception in protected mode in certain circumstances. Could be your program relies on such an exception. Addressing an array index beyond its dimensions, to then extend that and try again…
Jos
|
|
|
Post by billgrantford on Feb 7, 2023 14:54:14 GMT 1
Yes I would be interested in trying the development version on one of these systems. In the mean time I will review the logic in our code to see if anything is old coding methods.
Mike
|
|