>Recently I updated my computer operating system from Win 95 to Windows NT 4.0 -
>Microsoft’s latest and greatest offering for the desktop. Most things seem to work well under
>NT 4.0 with one very critical failure or oversight. That pertains to creating distribution disks
>on a FoxPro for Windows 2.6 application.
>
>The known problem according to Microsoft Knowledge Base article Q103032 - "PRB: RUN/!
>Command Failed with Windows NT", states that using the RUN command without the /N
>parameter FoxPro stops execution until the RUN command completes and the MS-DOS
>session is closed. The article goes on to say that "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."
>
>The very critical piece to this as far as I am concerned is highlighted and states:
>
> 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.
>
>Is there any solution to this problem? I hate to call Microsoft and pay $95 for a problem
>they know about but have not fixed. Microsoft needs to realize that not everyone, especially
>clients purchasing custom software, have the hardware required for their latest releases.