Microsoft KB Archive/103032

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 09:26, 20 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Article ID: 103032

Article Last Modified on 12/3/2003



APPLIES TO

  • Microsoft Visual FoxPro 3.0 Standard Edition
  • Microsoft FoxPro 2.5b
  • Microsoft FoxPro 2.5a
  • Microsoft FoxPro 2.5b
  • Microsoft FoxPro 2.6 Standard Edition



This article was previously published under Q103032

SYMPTOMS

When you are running FoxPro for Windows under the Microsoft Windows NT operating system, the error message "RUN/! command failed" occurs when you are using the RUN command to execute an MS-DOS command.

CAUSE

When the FoxPro RUN command is used without the /N parameter, FoxPro will stop execution and wait until the RUN command has completed successfully and the MS-DOS session is closed. However, because Windows NT is a preemptive multitasking operating system, it switches control back and forth between FoxPro and the RUN command. This can cause FoxPro to time out while it is waiting for the RUN command to complete.

NOTE: This problem affects the SetupWizard in the FoxPro Distribution Kit, which also uses a RUN command, causing it to fail at the point where compression starts.

RESOLUTION

Use the /N parameter on the RUN command to stop FoxPro from waiting for the RUN command to complete. The following is an example of using the RUN command with the /N parameter to execute FOXRUN.PIF. This example also uses the /C parameter to send a specific command to the command shell.

   RUN /N FOXRUN.PIF /C DIR
                

STATUS

This behavior is by design.


Additional query words: VFoxWin FoxWin 2.50 winnt multi-task errmsg err msg setup wizard dk

Keywords: kberrmsg KB103032