>Try changing the fox runtime library (fpw2600.esl). Use one you know its
>fine. Also, recompile in Windows 95.
>
>
>HTH
>
>
>
>>
>>Anyone had trouble with shelling out to DOS when using FPW 2.6 in the
>Windows '95b environment???
>>
>>I am using Windows '95 version 4.00.950b. It is the latest version
>shipping with Micron workstations. My application creates a report by
>building it in a text file (.dat). Then it does !copy .dat to
>LPT1. The DOS window appears and immediately the workstation locks up
>(i.e., a continuous sand timer). You have to do CTRL+ALT+DEL to get out.
>>
>>I took over maintenance of this app and am now trying to upgrade to VFP 5.0
>but I cannot get away from the calls I'm getting on the old version and its
>printing problems long enough to complete the upgrade. The report is so
>complex, the FPW Report Builder couldn't handle it; that is why the previous
>programmers resorted to calling to DOS and passing it a text file.
>>
>>So far the following have been checked and are NOT an answer for this
>problem:
>>
>>1. No, the report CANNOT be rewritten to use the FPW Report Builder.
>>2. No, saying PRINT to LPT1 doesn't work either.
>>3. No, it is NOT a problem with the MICRON BIOS settings; or at least that
>is what MICRON says. They say Win '95b and FPW 2.6 are incompatible in this
>matter and that Microsoft should provide a patch.
>>4. No, copying the COMMAND.COM from Win '95a onto a Win '95b machine WILL
>NOT WORK. We tried. It locked up the machine.
>>
>>
>>Remember, this is not a printing problem (i.e., the problem is with the
>printer, etc...). What I am describing here happens ANYTIME I use DOS
>commands from WITHIN my application. When I use DOS commands from the
>FoxPro command window, I don't have the problem. The problem only occurs
>when an application is running.

Could you use the Foxpro Copy File command instead?? Or even use a Low level command to copy the file??