Re: Word looks for another server on the network

Tech-Archive recommends: Fix windows errors by optimizing your registry

In article <C1A30236.1EBC9%henryn@xxxxxxxxxxxxxxx>, henryn
<henryn@xxxxxxxxxxxxxxx> wrote:

Elliot Roper:

Thank you for your response on this thread:
<snipped lots I can't add much to and agree with>

About moving an installation, there's a very clear model describing where
application "state" is stored-- in the home directory basis of the current
user-- and it works very well. (There would be chaos if it didn't!) It
seems reasonable to have Office state stored both in both ~/Documents (The
MUD) and ~/Library/Preferences, and I'm quite capable of making sure these
are properly transferred, as proven by the seamless transfer of my complex
Entourage installation and data.

Microsoft has only with Word 2004 become slightly less arrogant in that
department. The previous version (v.X) flung almost everything into
/Applications/Microsoft Office/Office... and similar places. I suspect
it was a follow-on from porting it from Windows 95 versions of Office,
where there was no clear notion of multiple users.

Depending on how the user's upgrade path occurred, they may still be
using templates in those directories. Another is the Word Startup
folder. You can change it, but the default is still /Applications....
(I think - my installation has a lot of historical baggage back into
v.X so I can't be sure)

Word 2004 is a bloated mess, also carrying loads of historical baggage.
I doubt very much we can persuade anyone to look at the source to
determine where your loop occurs without a clear simple exploit
example.

They are too far along with the next version, (which you can infer from
various public blogs of MacBU people). Those blogs suggest it will
interface to the OS in a different way. (Xcode development instead of
Code Warrior, XML, Universal Binary, more Applescript and no VB etc.)

You can imagine how deep the alligators are ;-)

So even *with* a clear reproducible example crasher, I'd not give good
odds of getting it fixed in Word 2004. On the other hand, having the
crasher *might* be of help in making the next version more solid.

One way or another, I think we might have got about as far as we can
sensibly go with this problem. It has been a most useful exchange, and
I have learned quite a bit. Not least a few more unix magics.

--
To de-mung my e-mail address:- fsnospam$elliott$$
PGP Fingerprint: 1A96 3CF7 637F 896B C810 E199 7E5C A9E4 8E59 E248
.