>I will check with the client, I am not a networking protocol expert, what grief would it cause if they were both loaded?

Nothing in particular - we run mixed IPX/NetBEUI at lots of our client sites. What -can- cause problems is both Microsoft's IPX/SPX compatible stack and Novell's native IPX stack, at least in my experience.

NetBEUI does create a tremendous amount of traffic, and is usually unnecessary in an environment using IPX or TCP/IP (you can do NetBIOS over IPX or IP, making netBEUI an extra burden, and both IPX and IP packets are routable (can travel across a router/brouter/gateway), unlike NetBEUI.) Your network administrator should be making the decision about what protocols to use on the LAN; as a general rule of thumb, however, using fewer protocol stacks is a good thing, since each protocol stack uses some system memory, and each incoming packet must be examined and evaluated by each stack to determine who's responsible for handling it. In addition, the more protocols in use, the more packets need to be sent on the network in general.

>
>Thanks for your response.
>
>>Could it be that you have IPX _and_ NETBEUI protocols loaded in the stations?
>>
>>Good luck.
>>
>>Marc
>>
>>
>>
>>
>>>I have a 2.5b app which has been running very well for some time. Clients have recently upgraded the hardware to p11 333s. These are running on a Novell 3.12 network with client32 and win95 all patch applied to win95 and the Novell server. The machines run, but very very slowly, worse than the 486 machines that they replaced. The 486 machine that remain on the system will out perform the new machines. I have read much documentation of high speed machines under foxpro 2.x that fail on startup. I have applied the divide by zero patch to the esl. I have had them try the Microsoft client rather than Novell's client 32, so far no luck . We have rewritten the app in vfp 5.0 but the clients are not ready for that yet. Any solutions or suggestions would be gratefully received.