@                 Histo-Scope V3.0.1 Release Notes for OpenVMS/AXP  D There are a few known warning or error messages that are printed by G Histo-Scope when run on the AXP.  All, but one, can be safely ignored,  C since the operation of Histo-Scope is correct despite the messages.   M   1)  When linking a program to be "scoped" by Histo-Scope with the HISTO_SHR G       Shareable Image and the Histo-Scope object library the following         message is printed:   0         %LINK-W-SHRWRNERS, compilation warnings N              in shareable image file LIB:[LIB.HISTO.V3_0_1.AXP]HISTO_SHR.EXE;1;         %LINK-W-MULDEF, symbol MATH$RINT_G multiply defined F              in module DPML$SHR file SYS$COMMON:[SYSLIB]DPML$SHR.EXE;2       I       To our knowledge, these warning messages can be ignored and have no        negative side-effects.    J   2)  When running a program that calls HS_HISTOSCOPE to automatically runB       the Histo-Scope process, the following messages are printed:  )         hs_histoscope - starting histo... /         Error starting Histoscope: illegal seek   I       Despite the illegal seek message, Histo-Scope is started correctly.     E   3)  On VMS, it is possible for Histo-Scope to abort with an Access  E       Violation error in the following specific circumstances:  When  K       using the Create Variable window to create a new Ntuple variable, if  K       the user changes the variable definition and then presses the Create  M       button rather than the Modify button, Histo-Scope will put up a dialog  M       which asks whether to replace the variable definition.  When answering  M       YES to this question, it is likely that Histo-Scope will abort with an  L       access violation error.  We believe this is a problem in the Motif or I       X libraries on VMS, and we do not have a fix for this problem.  We  M       suggest using the Modify button to change variable definitions instead  1      of pressing the Create button a second time. 