🚀 go-pugleaf

dorourke@polyslo.UUCP(David Orourke) writes in comp.sys.mac

>In article <5270@cup.portal.com> Tim_M_Dierks@cup.portal.com writes:
>>As we recently discovered to our glee, MacWrite 4.x works fine when shared.
>>Just set the shared bit and you're off.  The only restriction is that MacWrite
>>has to be in a directory that noone using the program has write access to.
>>As long as noone can write to that directory, it should work.  As far as I
>>can see, any software that will run in a write-protected environment can be
>>shared by setting the shared bit.
>
>	{Some Additional Information about his configuration ,etc. }
>
>   The basic summary of this is that I don't think MacWrite handles it's
>temp files correctly.  Notice that more than one copy doesn't solve this
>problem, since all of the copies try and create temp files in the system folder.
>Is my memory correct?  Or has Apple fixed this in version 4.5 or 4.6!
	
	As of Version 4.6 of MacWrite, it supports a NetWorked/Shared environment by
numbering the files that it uses based on the number of currently open items.
For example the first person to open MacWrite will be assigned Undo1, etc.
	It works and almost exactly like Apple said it should.


+---------------------------------+-----------------------------------+
+                                 +  Any thing I say may be taken as  +
+   Leonard Rosenthol             +  fact, then again you might decide+
+   President, LazerWare, inc.    +  that it really isn't, so you     +
+                                 +  never know, do you??             +
+   leonardr@uxe.cso.uiuc.edu     +                                   +
+   GEnie:  MACgician             +                                   +
+   Delphi: MACgician             +                                   +
+                                 +                                   +
+---------------------------------+-----------------------------------+