🚀 go-pugleaf

In article <84864@felix.UUCP> kehr@felix.UUCP (Shirley Kehr) writes:
>In article <962@wpi.wpi.edu> tron@wpi.wpi.edu (Richard G Brewer) writes:
> 
><WORD doesn't like it when you run 6.02 with MultiFinder and TOPS.  Period.
....
> 
>What happens? We just upgraded all machines to 6.02 and some people have
>already been running Word 3.02 with TOPS for some time. I'm one of the
>few who refuses to use TOPS, so I can't test anything.
>
>Shirley Kehr

We just moved from the Omninet networking system to Appletalk/Appleshare.
We're using CAP on a Pyramid 9825 as the file server until Cayman works the
bugs out of their AFP-NFS translation stuff (it's O.K., we always break
things - even thoroughly debugged software!). MS Word (3.02 no less)
occasionally munches files as they are being saved and crashes while
exiting with or without saving changes...

I've warned our Word users to save alternately to two files using SAVE AS
but (sigh) they don't always do that and then they come complaining to me.
We're using system 6.0.2 and Appleshare, and I am concerned about the sudden
problems we are having with Word - especially in light of the recent change
to Appleshare.

I have been watching the articles that have been posted (thanks all!) and I
am wondering if Word has a problem dealing with networks under 6.0.2, or
what??? No other applications we use are giving us this kind of grief.

I am aware of a bug in CAP50 which could explain some of the file munching,
but not the frequent crashing. In any case, I'll withhold final judgement
on the viability of Word as our word processor of choice until I get the 
CAP patches and install them.

I would like to hear from other users of MS Word using Appleshare/CAP, and,
please the deity, maybe even from Microsoft.

				Matt Hardin
				SilentRadio Headquarters, Los Angeles
				UUCP: {csun,pyramid,pcabell}!srhqla!mdh
				Smart mailers use: mdh@srhqla.UUCP