SCANCODE 590 (beta)
Posted: Sun Jan 25, 2015 5:24 am
Hello all; new member, here.
I'm running MS-DOS 5.0 on an HP Compaq 8000 Elite SFF. I downloaded scncd590.zip, and installed and successfully ran SCANCODE in methods 1, 2 and 3 as a command line to simulate Alt-Lsft-1. This keyboard input is needed to select a parallel printer through an ATEN AF142 ParaHub switch. The command also works well when called from a batch file (.bat).
However, when I call SCANCODE from a Synergy DBL runtime (Synergy/MS-DOS runtime version 4.52e, DEC's Dibol variant - URL: http://www.synergex.com) using “xcall spawn” (a command to run an external DOS command) – the runtime crashes and dumps the core. Same results if calling a .bat batch file that contains the SCANCODE command. It crashes with all three methods, 1, 2 and 3. The dumped core (DBLCORE.$$x) is in machine language and hence can't be used to isolate the error that causes the crash.
Does anyone know of a fix or workaround for this? I read the doc files and searched this forum but couldn't find any.
Thanks
I'm running MS-DOS 5.0 on an HP Compaq 8000 Elite SFF. I downloaded scncd590.zip, and installed and successfully ran SCANCODE in methods 1, 2 and 3 as a command line to simulate Alt-Lsft-1. This keyboard input is needed to select a parallel printer through an ATEN AF142 ParaHub switch. The command also works well when called from a batch file (.bat).
However, when I call SCANCODE from a Synergy DBL runtime (Synergy/MS-DOS runtime version 4.52e, DEC's Dibol variant - URL: http://www.synergex.com) using “xcall spawn” (a command to run an external DOS command) – the runtime crashes and dumps the core. Same results if calling a .bat batch file that contains the SCANCODE command. It crashes with all three methods, 1, 2 and 3. The dumped core (DBLCORE.$$x) is in machine language and hence can't be used to isolate the error that causes the crash.
Does anyone know of a fix or workaround for this? I read the doc files and searched this forum but couldn't find any.
Thanks