Recently upraded a client's system from release 1.12 to release 2.03 and NPP package. With release 2.03, AREV takes much longer to load when there is more than one user on the system. Also, attaching qfiles is very slow. Attaching 12 qfiles now takes 4 to 5 minutes as compared to seconds with release 1.12.

Background indexing under release 2.03 locks up the user's keyboard for excessively long periods of time, sometimes to the point that the user will reboot the station in sheer frustration. This problem is impacting user's ability to do their work in a timely manner.

The server for this network is a Win95 system running Lantastic v7.0 ,Two workstations are Win98 machines running Lntastic v8.0. The remaining workstations on the network are a mix of Win95 machines and older machines runnig under DOS.

Any help in improving system performance would be greatly appreciated.

Frederick Kurz

[email protected]

Frederick,

Apart from the DOS machines, if I was in your situation, I would strive for equivalent versions of Lantastic and Windows on all PCs.

Running just Windows 98 peer-to-peer all around, using TCP/IP, if there were less than 7 users might be one option. More than this and I'd be considering a dedicated server. If you have to keep the DOS PCs then add netbeui to the protocols.

Slow performance is usually due to either a bad cable, one slow PC on the network, or a topology condition which is not standard (ie. unusual cable lengths / old network cards / etc…) Also check that all your protocol versions match.

Perhaps if you isolate one workstation at a time and re-check performance you can rule out bad hardware (network cards) or cabling somewhere.

Steve

Steve,

Thanks for your suggestions. I'm not directlly responsible for the network,but I will discuss them with the network administrator. Prior to upgrading from Arev 1.12 to 2.03/NPP we did not experience any problems with program loading times or background indexing tying up a workstation. When we started adding W98 workstations to system we started having problems with 1.12 and decided to upgrade to 2.03. This solved the problems with 1.12 and W98, but we took a real performance hit. Once an application has finally loaded them system performance is what we expected.

Also, is there a way to reduce the time background indexing runs once it starts? Once the background process starts the operator's keyboard does not respond and after running for a long period of time the operator assumes the machine is locked up. The operator then does a cold boot.

Thanks,

Frederick Kurz

[email protected]

View this thread on the forum...