Conference hylndr::cdrom

Q)  Can the existing Bookreader application use the new .ODL and
    .BKB files on the new March 1997 OpenVMS Online Documentation
    Library (ODL) CD-ROM's?

A)  Bookreader cannot read the .ODL files, but can read .BKB files.

    The new ODL CD-ROMs are designed to be used with BNU to present a
    homogeneous user interface to a heterogeneous library.  Even though
    BNU's user interface looks like the familiar Bookreader bookshelves,
    the file formats are different.

    The .BKB files are Bookreader books, and in fact, BNU uses
    Bookreader to display them.  (BNU only displays the .ODL files).
    The .BKB extension is used instead of .DECW$BOOK to promote
    consistency across platforms.  Support for .BKB as a default book
    extension was implemented in Bookreader for several years.

    For customers who cannot meet the system requirements for BNU,
    the March OpenVMS VAX ODL includes a saveset that contains a
    Bookreader library. This library enables access to all Bookreader
    books in the ODL. Instructions for setting up this libary are in
    [README]$README.TXT on Disc 1 of the ODL CD-ROM set.

    The next OpenVMS Alpha Online Documentation Library will also
    include such a Bookreader library. Meanwhile, a library for the
    March OpenVMS AXP ODL is available on the Internet at:

        [TBS]

Q)  What are the requirements to run BNU on my system?

A)  At a minimum, your system environment must include:

        OpenVMS Alpha V6.1 (or later)
        DECWindows Motif V1.2-3 (or later)
        CD-ROM reader(s)
        DECwindows display

    To display HTML books, BNU requires Netscape Navigator V2.02 for
    OpenVMS.  Netscape Navigator also requires DECwindows Motif V1.2-4,
    or an update applied to V1.2-3 of DECwindows Motif (ALPMOTF07_U3012
    for Alpha Systems or VAXMOTF07_U3012 for VAX systems).

Q) Where can I find Netscape Navigator for OpenVMS?

A) The Netscape Navigator for OpenVMS Alpha and VAX is available on the
    Internet Product Suite (IPS) CD-ROM. The IPS CD-ROM ships with the
    OpenVMS V7.1 Operating System kit. It also ships with Enterprise
    Integration Server (EIS) V1.0 (on the disc labeled OVMIPS11). The
    EIS CD-ROMs are included in the March 1997 OpenVMS Alpha Layered
    Product Software Library. The IPS CD-ROM may also be ordered
    separately from Digital.

    Netscape Navigator may also be downloaded from the OpenVMS Internet
    Product Suite website at:

        http://www.openvms.digital.com/openvms/products/ips/

Q) Where can I find documentation for BNU?

A) The "Online Documentation Library User's Guide" includes information
    on installing and running BNU.  This manual is available on Disc 1
    of the Online Documentation Library in three formats:

        [README]ODL_USER_GUIDE.PS       Postscript
        [README]ODL_USER_GUIDE.TXT      Text
        [README]ODL_USER_GUIDE.BKB      Bookreader

    Additional information on customizing BNU and ODL will be included
    in a future Online Documentation Library release.
 

Q)  Why do I get BOOKBROWSER license warning messages (%LICENSE-W-...)
    while installing BNU from the March ODL?  What should I do?

A)  The BNU installation installs or replaces the BOOKBROWSER license.
    BOOKBROWSER permits access to Bookreader books for unlicensed products.

    If you only get %LICENSE-W-... messages, you may safely ignore them.
    However, they may be followed by these Polycenter messages:

        %PCSI-E-OPFAILED, operation failed
        Terminating is strongly recommended.  Do you want to terminate? [YES]

    In this case, you should terminate the installation. The error is a
    result of having an existing BOOKBROWSER license loaded on the system.

    This problem will be corrected in a future release of the OpenVMS ODL.
    The workaround is to deactivate your current BOOKBROWSER license:

        $ LICENSE UNLOAD BOOKBROWSER /PRODUCER=DEC

    and rerun SETUP.COM

Q)  How do I configure BNU to read the new Online Documentation Library?
    Do I need to define logical names like I did for Bookreader?
    If not, how does BNU find the libraries?

A)  Every Online Documentation Library (ODL) shipment contains a setup
    command procedure to configure BNU to read that library. The procedure
    is located at [SETUP]SETUP.COM on disc1 of the CD-ROM set. Each time
    you get a new ODL library, run the setup procedure that comes with it.

    BNU does not use logical names or searchlists to find files. The ODLs
    use relative pathnames for references to files on the same CD-ROM.
    ODL references to files on another CD-ROM rely on X Window System
    resource definitions. The resources are defined by the setup procedure.
    One resource is defined for each volume of the ODL. The resource name
    is simply the volume label of the target CD-ROM. The resource value
    identifies the device where the CD-ROM is mounted. We recommend the
    resource values be logical, rather than physical, device names.
    The default resource value for a CD-ROM is the logical device name,
    DISK$<volume_label>.  This name is defined by OpenVMS when you mount
    the CD-ROM anywhere on the OpenVMS system.

Q)  Can the new format Online Documentation Library CD-ROM's be accessed
    over a network connection via BNU?

A)  No, BNU is designed to access local devices on the system running BNU.
    However, you can transparantly mount remote devices as local devices
    using one of the following mechanisms:

        1.  TCP/IP and NFS
        2.  DECdfs with DECnet or DECnet/OSI
        3.  InfoServer

    If you have none of the above mechanisms available, you can use
    logical names to make remote devices look like local devices to BNU.
    This approach is not supported, but will allow you to access ODL
    shelves and Bookreader (.BKB) books on the remote device. However,
    you may get errors from other browsers such as Netscape Navigator.

    Define the DISK$volume_label logical names to the remote devices where
    the CD-ROMs are mounted.

    For example:

        $ DEFINE/SYSTEM DISK$AXPDOCMAR971 NODEB::DISK$AXPDOCMAR971:
        $ DEFINE/SYSTEM DISK$AXPDOCMAR972 NODEC::DISK$AXPDOCMAR972:

    Note that you do not need to know the physical device name on the
    remote node.