>I have a customer who has installed my VFP7SP1 product on a W2K server. Everything is on the server and the workstations have a shortcut pointing to the .exe. With W2K workstations the program loads from 10 to 15 seconds, depending upon the computer. With WinXP the load times are 70 seconds.
>
>They have done all the usual things, tinkered with Norton AntiVirus (which did have a dramatic effect on one W2K laptop changing load times from 70 seconds to 11). They switched from a mapped drive to a UNC mapping which actually slowed things down from a 10 second load to 15 seconds.
>
>One thing they haven't done is changed the MTU but that is coming. In the meantime, even without messing with the MTU, Win XP seems to be the culprit since W2K doesn't suffer the same malady.
>
>In house testing shows load times of 10 to 15 seconds using a relatively slow wireless connection and Windows XP. Meanwhile, for some reason this user is having problems and I'm sure others will as the 7 or 8 thousand users start upgrading in earnest.
>
>The answer I'm looking for is what the heck is the difference between XP and W2K? Sure the executable could be installed on the workstations but a 10 second load time is acceptable and program maintenance is greatly decreased by having nothing to speak of on the workstations. I searched the archives which gave me several ideas that have been tried but now my well is dry.

If you haven't seen it already check out Re: XP Pro and .Net conflict or XP not quite ready yet Thread #874915 Message #879072