I should add that after the app has been started and teh user logs in, then they have predictable normal speed using teh application. The problem is only limited to startup... so it seems.

Guy


>Hi,
>
>I've seen some threads here and on other forums discussing how Fox applications can be extremely slow on XP. Most of the common answers suggest antivirus as the prime culprit. And some have suggested adjusting the TCP/IP setting "MTU" which we have also tried with no noticeable improvement.
>
>I've got a situation where antivirus software not installed so it can't be the issue.
>
>Here's what is happening at one client of mine.
>
>In the normal course of daily business, they run a few fox apps (.EXEs) written in different versions from FPW2.6 up to VFP7.0. Data is located on an NT Server 4.0, sp6a. They have various ages of PCs ranging from P-166, 32MB RAM, Win98, up to P4 1.8ghz 256MB RAM, W2K Pro, and their Fox applications run fine on all of these (with the newer machines running a bit faster as you'd expect).
>
>Now, as part of the never ending quest to keep current they bring in new machines to swap out some of the oldest machines. The new PCs are P4 2.5ghz, 256-512MB RAM, XP Pro. Some from Gateway, some from Dell.
>
>Every one of these new XP machines (40 of them so far) takes about 60 seconds to launch a certain FPW2.6 application. This is incredible, since an old P166 with 32MB RAM can launch this same application in about 2 seconds. (And 1-2 seconds is normal on every other machine in the building.) Upon application launch, the EXE is only painting the menu, opening up a small user/password table and presenting a login dialog. I am stumped at what could be causing such a long delay.
>
>For what it's worth, VFP 6/7 apps don't seem to have this same slow down with the new machines.
>
>Other than Anti-virus, or MTU adjustments, does anyone have any ideas what might be causing a gross delay in the simple launching of an FPW2.6 EXE.
>
>Thanks,
>Guy