🚀 go-pugleaf

Try disabling packet burst, that is according to one of Novell's TID's.  I
found that unbinding unnecessary protocol's from my adapters actually fixed
the agonizing delay problem.  Espescially when I took Netbeui off my
adapter.

Hope this helps...
Stan :)

Einar Tvete <einar.tvete@miclis.no> wrote in article
<32DF4DCB.C60@miclis.no>...
> I have a costumer that is complaining about bad performance using Novell
> 4.10 and Client32. I have updated the Client32 to version 2.11, but it
> did not solve the problem. If she is running the program on one machine,
> it opens up in abour 4 seconds. If the program is already running on
> another machine, it opens up in 17 seconds.
> This makes me think about a similar problem on Win/NT server. If you try
> to open a file for exclusive use that is already in use, it takes NT 1
> second to perform retries until it gives up and returns to the
> application.
> My application tries first to open a file exclusively to perform some
> checking for then (or on error) to open it for shared use.
> 
> My question is: Does Novell 4.10 with Client32 automatically retry to
> open a file that is in use?
> 
> -- 
> Einar Tvete, Miclis AS
> einar.tvete@miclis.no
> http://www.miclis.no
>