On 9/8/05 09:21, "David Riddle" <email@hidden> wrote:
>> We learned on a 300+ AD OD roll out that Office wouldn't save to
>> "home" either on Windows 2003 servers in spite of having confirmed
>> 777 on temp folder etc. In order to get the machines out we had to
>> reimage back to 10.4.1 X 300+ and then saving would work. All in
>> all, a miserable and frustrating experience and certainly one that
>> undermined both loyalty and credibility.
>>
>
> I have to say ..with what or with who?
>
> This may be coming to light more now, but many of us have suffered
> from this for ages.. this is a Microsoft problem that has been swept
> under the carpet IMHO, *not* an Apple or exclusively a 10.4 issue. It
> also *can* even be erratic
It's both. Apple has a habit of changing things like file locking for carbon
applications, (as in, the API way is gone, just rewrite your application to
use .lck files), and the fact that MS can't constantly modify Office every
time Apple changes something on them.
Hopefully, with Mac OS X 10.4 being the "API Stable" version of OS X, this
will make it simpler for MS to clear up quite a few things.
In any case, changing anything when you talk about codebases the size of
Office OR OS X is not a simple task. Even minor bugfixes can take months.
--
John C. Welch Writer/Analyst
Bynkii.com Mac and other opinions
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Client-management mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/client-management/email@hidden
This email sent to email@hidden
