>Here's an update...
>
>I got down to the client's office yesterday and we picked a random XP machine and started trying some of the suggestions made on this thread. Nothing seemed to make a difference.
>
>Then we started at the top again. When we doublechecked the MTUs, it was clear that the MTU adjustment had not been made on the machine. So, using the DrTCP utility commonly available on the Internet, we changed the MTU to 1454 and rebooted. Automagically, the launching of this FPW2.6 legacy app was back to normal - almost instant.
>
>It turned out that our changing of MTUs was on another non-XP machine that we were troubleshooting earlier for another reason.
>
>So for anyone who may find themselves troubleshooting a similar problem, here's a summary...
>
>1. Windows XP ships with a particular TCP setting called "MTU" with a default value of 1500.
>
>2. There was no noticeable performance problem with VFP, Word, Excel, etc. But with an FPW2.6 compiled .EXE, it took around 60 seconds to launch the app (which normally happens in about 1 second). Once the app was up and running, there was no noticeable performance problem using the FPW app.
>
>3. We used the DrTCP utility to change the MTU value (lower right corner of the dialog). By setting the value to 1454, we got back to normal [quick] performance. Why 1454 instead of the default of 1500 that ships with XP? I can't explain the math. But if you must know, do an Internet search and you'll find many sources that can explain packets, headers, network overhead, etc and do a good job explaining the math behind the 1454 recommendation.
>
>Thanks to everyone who made suggestions on this thread.
>
>Guy

Don't forget to mark your post as the answer to the thread - will make it easier for others to find it later. Might be a good FAQ contribution, too...