PRB: COPY FILE <filename> TO LPT1 Causes Invalid Seek Offset

 Last reviewed: September 10, 1997
Article ID: Q157635
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0b, 5.0, 5.0a

SYMPTOMS

In Windows 95, using the COPY FILE command to copy a file to LPT1 causes the "Invalid Seek Offset" error in Visual FoxPro 5.0 and 3.0b if the port is not captured. If the port is captured, the error "Invalid Path or File Name" appears. However, in Windows NT 3.51 and Windows NT 4.0, using the COPY FILE command to copy a file to LPT1 first returns a warning message that the file will be overwritten unless SAFETY is set to OFF, then the message "Error Writing to File" appears.

STATUS

Microsoft is researching this behavior and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a simple text file in Visual FoxPro as Test.txt.

  2. In the Command window, type in the following code: 

          COPY FILE Test.txt TO LPT1:

Under Windows 95, you get an "Invalid Seek Offset" error message dialog box when the port is not captured. If it is captured, the error "Invalid Path or File Name" appears. 
Keywords          : buglist3.00b buglist5.00 FxprgGeneral vfoxwin vfpbug5.0a kbprg kbbuglist kbprg
Version           : 3.0b 5.0 5.0a
Platform          : WINDOWS
Issue type        : kbbug

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.