🚀 go-pugleaf

In article <987@acer.stl.stc.co.uk> ah2@stl.stc.co.uk (Amos Hornsby) writes:
#>I have just taken delivery of my update to version 2.0 of WriteNow.
#>Unfortunately there seems to be a big problem. We are running AUFS (AppleTalk
#>to UNIX File Server) under CAP on a Sun 3/260 as our file server
#>WriteNow 2.0 will not open its own documents if they are on the
#>server. On selecting a document to open and clicking open we get the
#>error message:

This isn't exactly the same problem, however, I note that
WriteNow 2.0 (I didn't use WriteNow as much before 2.0 so
I'm not sure if it was true then) often has problems finding
the WriteNow application when you click on WriteNow files
in other folders than the one in which the application resides.
I'm not sure whether this is a problem with the System (6.0.2 on
my Mac II) or with WriteNow itself.

For example, I keep a WriteNow shell in my VersaTerm folder as I
find WriteNow is easier to use to format and print downloaded text
files than is MacWrite, which is the default. Sometimes, that
shell opens with no problems. At other times, the system is
unable to find the application, and I have to go to another
folder and open and close another WriteNow file. Sometimes, with
two WriteNow documents in the same folder, one will launch the
application and another won't.

Has anyone else had this experience and is there a solution?

Steve Goldfield