>We somehow developed this issue after years of running (this exact SAME code) with no problems. Lately on all 20 computers running this code, we experience this behaviour :
>
>Ocasioanlly (as in it works most times) when a RUN command (that executes a DOS command, like nPrint, or a PGP command line call or calling a batch file that FTPs something) the DOS box freezes. VFP is obviously frozen as well but what's really weird is that WIN2k is sort of frozen as well. You can still click the task bar and move the mouse around but you can't run any new programs and if you try to kill the DOS window or the VFP program (assuming the task manager was up , because if it wasn't you cannot bring it up) the whole computer freezes completely.
>
>Any ideeas ? (we are working towards getting rid of the DOS code but there is a lot of legacy code hanging around)
>
>A few more details.
>I tried replacing the RUN command with the CreateProcess API command with the same results.
>I removed all security patches on seleted computers and they still behave the same.
>On further investigations it seems the computer is not frozen, the interface is as some of the SysInternals tools allow me to connect with the computer. I'm not really sure what to look at though.
>
>Thank you
>
>Sorin

Sorin,
I think DOS code is waiting for some type of input, not finding something etc.
Check what happens if you go to console and explicitly try the command there.
Cetin