T
tangymeatsauce
I work in a library where we have a pool of around 20 internet
computers for public use. We recently completely upgraded these
machines to brand new 3 ghz boxes running Windows XP (SP2) about a
month ago. In that upgrade we also decided to make the jump from
Office 2000 to 2003. All has been fine, except occasionally a patron
will be working in Word only to have the app lock up and go "not
responding". Unlike some other posters who've had short intermittent
lockups, Word never comes back from these freezes and we always have to
end task, which of course results in the patron losing their work. We
haven't been able to trace it to a particular PC and obviously we can't
really tell what the patrons are doing when Word locks up.
As a stopgap we implemented an every-2-minute autosave on all the
machines with Word, but we're pretty frustrated with this. Has anyone
seen this type of behavior from Word 2003 before?
computers for public use. We recently completely upgraded these
machines to brand new 3 ghz boxes running Windows XP (SP2) about a
month ago. In that upgrade we also decided to make the jump from
Office 2000 to 2003. All has been fine, except occasionally a patron
will be working in Word only to have the app lock up and go "not
responding". Unlike some other posters who've had short intermittent
lockups, Word never comes back from these freezes and we always have to
end task, which of course results in the patron losing their work. We
haven't been able to trace it to a particular PC and obviously we can't
really tell what the patrons are doing when Word locks up.
As a stopgap we implemented an every-2-minute autosave on all the
machines with Word, but we're pretty frustrated with this. Has anyone
seen this type of behavior from Word 2003 before?