>>Hello,
>>I have a client who is experiencing the "fast machine" syndrome in FPW26. I downloaded the Slowstart program from the Web and tested it on my FPW2.6 apps and it worked just fine. When I loaded it on my client's server,I received the message:
>>
>> Slowstart11.exe not a foxpro exe file
>>
>> An investigation revealed that my client's Fpw2.6 version was 2.6A whereas mine was 2.6. Was there something I've missed in an update? that could have made this much of a difference?
>>
>> As my system runs on WIN98 I had no problem with the program name being more than 8 characters. I renamed the Slowstart11.exe to Slowstar.exe at the client's location. That's the only change made.
>>
>>Has anybody else experienced this problem and if so, what was your solution? Any help would be greatly appreciated.
>>
>>TIA
>>
>>Barry
>
>Hi Barry,
>I've been using FoxStart not Slowstart (I believe there is some difference apart from the icon) with FPW2.6a No problems. If you can't get hold of it I can send it.
>Sounds though like your foxpro app is calling Slowstart.exe and not the other way around, so I'd check the set-up first.
>HTH
Hi Dave,

Thanks for responding. I also tried Foxstart with the same result. My calling sequence was as follows:

G:\fpw26\foxprow.exe\g:\pyr_sup\slowstar.exe -t 2 "G:\pyr_sup\pboa"

(I'm doing this from memory as I'm not at the client site now), but I'm pretty sure that's how it's structured. I did the same thing on my laptop and it worked fine. Any other ideas?

TIA