|  |     I hate to sound like a grump, it's just that this question has come up
    a lot. If you are looking for a conference that
    seems to have moved, FELINE is not the appropriate place to ask (nor
    are FELINE's moderators). The FIRST thing to do is to check EASYNOTES.LIS.
    If your system manager doesn't keep a copy of this file (which is updated
    weekly) on your system, you can pull this file to your account by issuing
    the following command:
	$ copy anchor::net$library:easynotes.lis []
    and you can find the file you are interested in by either typing the
    file or looking at it in your favorite editor or by using the DCL
    search command like this:
    	$ sea easynotes.lis CANINE
    and you will get back something that looks like this
Dogs				DOGS::CANINE				     977
Dogs				easynote.confs.personal.Canine		     977
    Notice the number in the right hand column. This is the note number in
    TURRIS::EASYNET_CONFERENCES that the file is introduced in, and that
    all information about the file's movement is kept. If EASYNOTES.LIS
    indicates that you were looking the right place, the SECOND thing to
    so is to check out the appropriate note in the EASYNET_CONFERENCES
    conference. When public conferences are announced or moved, the
    moderator is obligated to post that information in EASYNET_CONFERENCES;
    If a node is going to be unavailable for a period of time, that
    information will sometimes be placed into that note as well. If a node
    address changes, moderators will sometimes explain how to access the
    conference  should a remote system's node database not be up-to-date.
    If you still can't get into the conference you want, your last choice
    is to compute the node address in the following manner:
    	1. Check the remote node's address on your system:
    	  $ MCR NCP
    	  NCP> SHOW NODE DOGS
    	  Under the heading of NODE you will see something like:
    	  1.1 (DOGS)
    	2. Check the master network data base
    	  $ MCR NCP
    	  NCP> TELL ANCHOR SHOW NODE DOGS
    	  19.190 (DOGS)
    	3. If these numbers match, you can either wait a while (the
    	conference's host system might not be up) or contact the moderator
    	or post a *REPLY* in EASYNET conferences's note that is concerned
    	with the conference that you are interested in asking what is going
    	on. Before you do that, however, it might be good if you have
    	pulled and read CAFEIN::NOTES$LIBRARY:NOTES_PROBLEMS.HINTS. This
    	document explains some of the common errors and what to do about
    	them. 
    	4. If these numbers do not match, you will need to compute the
    	network address and use that to access the conference until your
    	system's node database is updated. Compute as follows:
    	19.190 = 19*1024 + 190 = 19646
    	5. At the notes prompt, enter
    		NOTES> MODIFY/ENTRY CANINE/FILE=19646::CANINE
    	   or
    		NOTES> OPEN 19646::CANINE/NONOTEBOOK
    Deb
    P.S. I would like to advise many of you to pull both EASYNOTES.LIS and
    CAFEIN::NOTES$LIBRARY:NOTES_PROBLEMS.HINTS to your own directory and
    read them both thoroughly. They provide a lot of information that will
    make you a more knowledgeable NOTES user.
 |