| Well, gosh, looks like I wrote a little too soon...
The virtual address space layout shows the ACCVIO PC 00108E9D falls
into VAXCRTL.EXE
7FF517B0 00000200 0007EBFF MAIN ECP$INTEGRATE 0,0
7FF51700 00116800 001347FF GLOBAL PSPA$READ 21,48
7FF50EB8 000FE800 001167FF GLOBAL SHR VAXCRTL 4,5
so the ACCVIO is at VAXCRTL+A69D (OVMS VAX v6.1).
The customer did get a number of xxxTIME VAXCRTL.OLB routine link
errors during install of ECP v4.0 (partial log below). Am doing
the work to upgrade an old X6.0 system to v6.1 then install ECP v4.0
to see if any of this is duplicatable.
|
| The virtual address space layout shows the ACCVIO PC 00108E9D falls
into VAXCRTL.EXE
7FF517B0 00000200 0007EBFF MAIN ECP$INTEGRATE 0,0
7FF51700 00116800 001347FF GLOBAL PSPA$READ 21,48
7FF50EB8 000FE800 001167FF GLOBAL SHR VAXCRTL 4,5
so the ACCVIO is at VAXCRTL+A69D (OVMS VAX v6.1).
The customer did get a number of xxxTIME VAXCRTL.OLB routine link
errors during install of ECP v4.0 (partial log below). Am doing
the work to upgrade an old X6.0 system to v6.1 then install ECP
v4.0 to see if any of this is duplicatable.
From customer:
"When I upgraded the ECP software from v3.1 to v4.0 I got
several warnings when ECP$PLAN and ECP$INTEGRATE were linked:"
%LINK-W-MULDEF, symbol CTIME multiply defined
in module C$TIMEF file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;3
%LINK-W-MULDEF, symbol LOCALTIME multiply defined
in module C$TIMEF file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;3
%LINK-W-MULDEF, symbol ASCTIME multiply defined
in module C$TIMEF file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;3
%LINK-W-MULDEF, symbol GMTIME multiply defined
in module C$TIMEF file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;3
%LINK-W-MULDEF, symbol MKTIME multiply defined
in module C$TIMEF file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;3
%LINK-W-MULDEF, symbol DIFFTIME multiply defined
in module C$TIMEF file SYS$COMMON:[SYSLIB]VAXCRTL.OLB;3
|