Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Word slow when typing
1 view
Skip to first unread message
ke...@yahoo.com
Jan 8, 2004, 4:30:25 PM1/8/04
to
I am having a problem with performance in Microsoft Word documents on one
of our servers. I am logged in using Novell client 4.90sp1 on an XP box,
and we have two servers that are right here on site. They are both
NW5.1sp6, but on one server(the older one), Word is operating at a normal
speed, but on the other, there are huge delays that occur while typing in
a document, so I guess that pretty much rules out the client. I enabled
client file caching on the problem server earlier, but it seemed to be
causing problems with users not dropping connections to virus signatures
that they download from the server, plus the server that is operating
fine with Word doesn't have it enabled. Any idea what other settings
might tweak the Word performance?
of our servers. I am logged in using Novell client 4.90sp1 on an XP box,
and we have two servers that are right here on site. They are both
NW5.1sp6, but on one server(the older one), Word is operating at a normal
speed, but on the other, there are huge delays that occur while typing in
a document, so I guess that pretty much rules out the client. I enabled
client file caching on the problem server earlier, but it seemed to be
causing problems with users not dropping connections to virus signatures
that they download from the server, plus the server that is operating
fine with Word doesn't have it enabled. Any idea what other settings
might tweak the Word performance?
Brad Doster
Jan 17, 2004, 3:29:51 PM1/17/04
to
In article <RZjLb.9535$VM1....@prv-forum2.provo.novell.com>, wrote:
> Word is operating at a normal
> speed, but on the other, there are huge delays that occur while typing in
> a document
>
I doubt very much this is server, or even network related. Maybe Virus Scan > Word is operating at a normal
> speed, but on the other, there are huge delays that occur while typing in
> a document
>
software? Anyway, Word is installed on the local workstation, right? If
so, the only time it might be talking to the server is when you are opening
or saving a file, not while editing. As a test, you might try not logging
in to the network, then running Word -- chances are the behavior will be the
same.
bd
NSC Volunteer SysOp
www.InsightNetSolutions.net
Ke...@yahoo.com
Jan 21, 2004, 4:34:22 PM1/21/04
to
Well, it is only happening to word documents that are located on one
server. Yes, Word is installed locally, but if I edit a word document on
my desktop for instance, it types perfectly, same with the other server
that I am attached to (a drive maps to both servers at login). Another
thing is that the problem is a little worse from an XP computer than one
running windows 2000, but not much. The problem also exists when I try to
type in a word document located on this server when I connect from a
windows 98 machine, so I gotta believe it is server related. These tests
were using novell client 4.90 sp1, client 3.32 sp2 and client 3.4. If I
enable client file caching on the server that is having the word
problems, it completely solves the problem, but the server starts to get
loaded with “Station X (task XX) has timed out on its op-lock (type = 2)”
errors and the whole network slows down, so that doesn’t do me any good.
Thanks again!!
server. Yes, Word is installed locally, but if I edit a word document on
my desktop for instance, it types perfectly, same with the other server
that I am attached to (a drive maps to both servers at login). Another
thing is that the problem is a little worse from an XP computer than one
running windows 2000, but not much. The problem also exists when I try to
type in a word document located on this server when I connect from a
windows 98 machine, so I gotta believe it is server related. These tests
were using novell client 4.90 sp1, client 3.32 sp2 and client 3.4. If I
enable client file caching on the server that is having the word
problems, it completely solves the problem, but the server starts to get
loaded with “Station X (task XX) has timed out on its op-lock (type = 2)”
errors and the whole network slows down, so that doesn’t do me any good.
Thanks again!!
Ke...@yahoo.com
Jan 21, 2004, 5:03:47 PM1/21/04
to
Forget it, I found out it was a problem specific to one file. Thanks
anyway
anyway
Brad Doster
Jan 21, 2004, 9:36:46 PM1/21/04
to
In article <7HCPb.3234$P5....@prv-forum2.provo.novell.com>, wrote:
> Forget it, I found out it was a problem specific to one file. Thanks
> anyway
>
OK, glad you found the culprit!> Forget it, I found out it was a problem specific to one file. Thanks
> anyway
>
0 new messages