Quoting Rowan Crowe to Lawrence Gordon:
RC>LG> finding both the source and target directories. If, on the other
RC>LG> hand, the program is run from the network, PB crashes with error
RC>LG> 76 Path Not Found messages.  This phenomenon occurs under Novell 3.12
RC> Have you tried replacing your x:\path\path with the 'true' network path
RC> Although I use a network daily, I rarely have to refer to true paths,
RC> so I'm a little rusty , but it's something like
RC> \\SYS:PATH1\PATH2\FILENAME.EXT
Good question. No, I haven't. The reason is that the "target paths" are
part of a two-part configuration file.  The first configuration file
lays out information specific to the user's bulletin board, the second
config file lays out information specific to incoming files (TICs) and
target directories.  When the program operates, it checks the first
config file to make sure that the bbs specific information is correct,
and if so, continues at that point to read the second config file
and process the incoming files.
The target paths are a parameter of the second-config file, and
the program expects them to "equal" the "true" paths.  When the program
executes, the true paths are not found if they exist on a machine other
than the local, and, thus "Error 76" rears its ugly head.
 * WCE 2.0/2081 * 
--- WILDMAIL!/WC v4.12 
---------------