RTI_SET_DEBUGGER (AREV64)
At 04 FEB 2024 08:09:50PM Barry Stevens wrote:
trying to run RTI_SET_DEBUGGER "1" from TCL and EVAL CALL RTI_SET_DEBUGGER("1")
I get a not found/error loading msg.
$RTI_SET_DEBUGGER is in SYSOBJ but not in VOC, which is attached from my ARE3.12 .\SOURCE folder
Should all by ARE3.12 VOC application related entries be copied to a VOC in one of the OI10 related folders and that VOC should be attached.
Having a few issues (reported) and was wondering if all related.
What AREV related file should I have attached and from where?
Any that should have had the contents copied from AREV3.12
I did find my SYSPRINTERS data was not what was in AREV
At 04 FEB 2024 08:35PM Donald Bakke wrote:
trying to run RTI_SET_DEBUGGER "1" from TCL and EVAL CALL RTI_SET_DEBUGGER("1")
I get a not found/error loading msg.
$RTI_SET_DEBUGGER is in SYSOBJ but not in VOC, which is attached from my ARE3.12 .\SOURCE folder
Should all by ARE3.12 VOC application related entries be copied to a VOC in one of the OI10 related folders and that VOC should be attached.
Having a few issues (reported) and was wondering if all related.
What AREV related file should I have attached and from where?
Any that should have had the contents copied from AREV3.12
I did find my SYSPRINTERS data was not what was in AREV
When you type RTI_SET_DEBUGGER 1 in TCL, do you immediately get the message or is it after you close TCL?
At 04 FEB 2024 11:23PM Barry Stevens wrote:
trying to run RTI_SET_DEBUGGER "1" from TCL and EVAL CALL RTI_SET_DEBUGGER("1")
I get a not found/error loading msg.
$RTI_SET_DEBUGGER is in SYSOBJ but not in VOC, which is attached from my ARE3.12 .\SOURCE folder
Should all by ARE3.12 VOC application related entries be copied to a VOC in one of the OI10 related folders and that VOC should be attached.
Having a few issues (reported) and was wondering if all related.
What AREV related file should I have attached and from where?
Any that should have had the contents copied from AREV3.12
I did find my SYSPRINTERS data was not what was in AREV
When you type RTI_SET_DEBUGGER 1 in TCL, do you immediately get the message or is it after you close TCL?
After I close TCL
At 04 FEB 2024 11:44PM Barry Stevens wrote:
trying to run RTI_SET_DEBUGGER "1" from TCL and EVAL CALL RTI_SET_DEBUGGER("1")
I get a not found/error loading msg.
$RTI_SET_DEBUGGER is in SYSOBJ but not in VOC, which is attached from my ARE3.12 .\SOURCE folder
Should all by ARE3.12 VOC application related entries be copied to a VOC in one of the OI10 related folders and that VOC should be attached.
Having a few issues (reported) and was wondering if all related.
What AREV related file should I have attached and from where?
Any that should have had the contents copied from AREV3.12
I did find my SYSPRINTERS data was not what was in AREV
When you type RTI_SET_DEBUGGER 1 in TCL, do you immediately get the message or is it after you close TCL?
Saw you post.
Did the macro thing
run prog with debug (debugger as normal)
got the arev debug screen
closed
did the alt - got a 'ding'
ran the prog and OI closed when debug hit
At 05 FEB 2024 07:27AM bshumsky wrote:
Hi, Barry. I suppose your reason for doing this is so you can run the "real" (graphical) OI debugger for your AREV64 routines? If so, you must have the engine "visible" on the desktop, in addition to calling RTI_SET_DEBUGGER. This is controlled by the CFG_CTO record. I believe you mentioned you have just a "." in field 1. What do you have (if anything) in field 2? That controls the port number (not relevant in this case), and the startup and shutdown flags - you must set them both to "1" before you start the AREV64 form so that its engine is visible…
- Bryan Shumsky
At 05 FEB 2024 02:55PM Barry Stevens wrote:
Hi, Barry. I suppose your reason for doing this is so you can run the "real" (graphical) OI debugger for your AREV64 routines? If so, you must have the engine "visible" on the desktop, in addition to calling RTI_SET_DEBUGGER. This is controlled by the CFG_CTO record. I believe you mentioned you have just a "." in field 1. What do you have (if anything) in field 2? That controls the port number (not relevant in this case), and the startup and shutdown flags - you must set them both to "1" before you start the AREV64 form so that its engine is visible…
- Bryan Shumsky
Where?
At 05 FEB 2024 03:04PM bshumsky wrote:
If you're using the OI Console, you should be able to set those flags in System Configuration menu, on the "Configuration Records" maintenance screen. If you are editing it by hand, you'll call up the proper CFG_CTO record in SYSENV, and in field 2, values 3 & 4 should each be set to "1" (for a visible engine) or left blank (for the default invisible engine).
You could also look for "CFG_CTO" in the Revelation Wiki, and the top result describes the layout of that record.
Hope that helps,
- Bryan Shumsky
At 05 FEB 2024 03:11PM Barry Stevens wrote:
If you're using the OI Console, you should be able to set those flags in System Configuration menu, on the "Configuration Records" maintenance screen. If you are editing it by hand, you'll call up the proper CFG_CTO record in SYSENV, and in field 2, values 3 & 4 should each be set to "1" (for a visible engine) or left blank (for the default invisible engine).
You could also look for "CFG_CTO" in the Revelation Wiki, and the top result describes the layout of that record.
Hope that helps,
- Bryan Shumsky
Awesome, thanks
At 05 FEB 2024 03:58PM Barry Stevens wrote:
If you're using the OI Console, you should be able to set those flags in System Configuration menu, on the "Configuration Records" maintenance screen. If you are editing it by hand, you'll call up the proper CFG_CTO record in SYSENV, and in field 2, values 3 & 4 should each be set to "1" (for a visible engine) or left blank (for the default invisible engine).
You could also look for "CFG_CTO" in the Revelation Wiki, and the top result describes the layout of that record.
Hope that helps,
- Bryan Shumsky
Awesome, thanks
Yep, that worked.
I see the ne 'replacement' code which I had never bothered to look at before.
I now understand they are CTO commands - hope I dont need to read and understand the CTO manual!!!