[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hylndr::cdrom

Title:	Topics for Discussion about CDROM
Notice:	ConOLD problems=150.; ConDist problems=151.
Moderator:	WMOENG::PACKARD

Created:	Thu Mar 14 1991
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	437
Total number of notes:	2500

437.0. "Questions about using BNU..." by CHOWDA::GLICKMAN (writing from Newport,RI) Tue May 27 1997 21:10

    I just put this into the BOOKREADER notes conference and popped into here
    and thought I should put a note here as well.
    
     I have two questions about using BNU:
    
    (1) On OpenVMS 6.1 VAX, do I absolutely have to use it to see the MAR 97
        documentation and beyond?  Or can i use the prior to OpenVMS 6.1
        VAX kludge for the following reason:  
    
    (2) What about backwards compatiblity?  I.e, I install BNU and then
        want to read the DEC 96 documentation.  Will it work?
  
    	Appreciating any responses.
    
    	Thanks.

T.R	Title	User	Personal Name	Date	Lines
437.1	who used to work over the casino on green for nusc/nrl/csc	HYLNDR::BROWN		`Wed May 28 1997 13:13`	49
	(1) On OpenVMS 6.1 VAX, do I absolutely have to use it to see the MAR 97 documentation and beyond? Or can i use the prior to OpenVMS 6.1 VAX kludge for the following reason: What kludge are you referring to? The duplicate shelf structure in old-style bookreader format perhaps? Is so, then you are implying that all old-style bookreader on-line discs are kludges, no? (2) What about backwards compatiblity? I.e, I install BNU and then want to read the DEC 96 documentation. Will it work? Yes. BNU is a shelf navigation utility -- nothing more. It replaces Bookreader in new release only for reading/traversing shelves. Bookreader is still required/used to view individual "books" that are in Bookreader format. The BNU shelf format is also different from bookreader format shelves so there isn't real upward/backward compatibility between the two. The BNU shelf format allows viewer specification information (sorta like the "Associate" function in File Manager) so that multiple book formats can be supported. (Its up to individual engineering groups to select which of the supported formats they will generate their on-line documentation in). If you have BNU format shelves, as in current releases, then you need to utilize BNU to traverse the shelf structure. If you have Bookreader format shelves, as in older releases, then you need to utilize Bookreader to traverse the shelf structure. Since most (almost all?) books are in Bookreader format -- and this is likely to be the case for awhile -- the Bookreader program will be a required component of the on-line doc strategy for some time to come. It just so happens that it isn't being used to navigate the shelf files any longer. That said, putting in an old release of docs simply requires using bookreader directly to view the shelfs -- just as you've always done. Under new releases, there has been some effort to include a set of Bookreader format shelves so that Bookreader can still be utlized to walk shelves and view books. The only problem with this duplicate set of shelfs is that it cannot include references to books that are not in Bookreader format. Currently I believe there are only a couple of books in HTML or other non-bookreader formats that require the BNU shelf structure.
437.2	BNU, VAXclusters and physical v. logicals drives	CHOWDA::GLICKMAN	writing from Newport,RI	`Mon Jun 02 1997 21:10`	22
	Another question. We installed BNU on a VAXcluster. BNU seems to look for the physical DAD device and it can't even find that. Can BNU use a logical device name so all the members of that VAXcluster can see the documentation? As it stands now when I try each VAX I can the names of the documentation and when I click on any one of them nothing happens. In the DECterm window where I start BNU I see these messages: $BNU Error opening bookshelf. Title: Hardware Documentation File: /DAD5/hardware/hardware.odl Reason: no such device. Error opening bookshelf. Title: Operating System Documentation File: /DAD6/opsys/opsys.odl Reason: no such device. Appreciating any assistance with this situation! Thanks,
437.3	redefine the volume label attribute	DONVAN::KRAETSCH		`Wed Jun 04 1997 12:21`	16
	When you installed the March ODL, you were asked where each CD will be mounted at run-time. Instead of answering with the DAD5 device name, accept the default DISK$VAXDOCMAR972, etc. This logical is defined by the MOUNT command when the volume is mounted. To achieve the same effect, you can edit DECW$SYSTEM_DEFAULTS:BNU.DAT and change the volume label resource. For example: BnuLibrary.VAXDOCMAR972: DISK$VAXDOCMAR972 When BNU sees a %<volume_label> reference, it looks for a BnuLibrary.<volume_label> resource in the BNU.DAT file to find the (physical or logical) name of device where that CD is mounted. In a future version of BNU, <volume_label> will be translated internally to DISK$<volume_label> on VMS without looking in the resource file.