Sony Trinitron WEGA KV-DZ29M91, Руководство по обслуживанию

Страница: 42 / 170

XYGATE
®
Data Protection
™
Reference Manual
Chapter 5. Resolving Issues that can Occur when Installing the XDP Library
XYPRO Technology Corporation
22
Proprietary and Confidential
If you encounter an error message that is emitted by the library attaching macro, read
sections 5.1 and 5.2 first to gain an understanding of the possible issues that can
occur when combining XDP libraries with other libraries or programs. When you have
procedure name conflicts, there are additional sections to read as indicated in Table 1
below.
Table 1: Error Resolution Table
Object Type Message Resolution
Non-Native Procedure call collisions have occurred between
the XDP Library and the non-native application
object and/or its library. Refer to sections 5.4
and 5.4.1 .
Native An existing library has been found when
attempting to install the XDP library into a native
application object. Refer to section 5.3 .
Native Procedure call collisions have occurred between
the XDP Library and the native application object
and/or its library. Refer to sections 5.4
and 5.4.1 .
5.1 The Library Procedure Call Order Issue
When you want to combine multiple intercept libraries, you will most likely have a
procedure name conflict. This occurs because the intercept libraries probably try to
intercept the same Guardian procedures. The library attaching macro detects this
condition and emits an appropriate error message.
To resolve this issue, you must decide the order in which the application needs to call
the procedures, and then you must rename the conflicting procedure names to
something else. This removes the conflict and allows the libraries to be combined or
allows the XDP library to be bound into the program.
A feature of the XDP architecture is that each Guardian procedure that is intercepted is
implemented in XDP as two procedures: one procedure does the encryption work and
the other procedure does the actual I/O. This allows procedures from other intercept
libraries to replace the XDP procedures that do the I/O. The I/O procedure has the text
__XYPRO_ prepended to the procedure name.
For our discussion purposes, we will use the WRITEX procedure as an example to
illustrate what has to be done. XDP actually intercepts many different Guardian I/O
procedures other than WRITEX. A list of those procedures is shown in
Table 2 starting
on page 27 at the end of this chapter. Each procedure conflict must be resolved.