https://bugs.winehq.org/show_bug.cgi?id=47933
Bug ID: 47933 Summary: FoxPro for Windows 2.6a will not print output from scripted dialog. Product: Wine Version: 4.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs@winehq.org Reporter: JSladek@juno.com Distribution: ---
Created attachment 65436 --> https://bugs.winehq.org/attachment.cgi?id=65436 General format for program sections
Access to and use of my databases is all under a program written using the FoxPro language. After opening the desired database and index, I use the command "REPORT FORM <report format filename> TO PRINTER" to send the report to the printer. The "TO PRINTER" clause can be substituted by "TO FILE <filename>" .... however ..... in BOTH cases, while running it in WINE, the output fails with a "printer not ready" error. Additionally, if I replace the "TO clauses" with "PROMPT", a printer selection (or to file) dialog comes up, but I still get the same "printer not ready" error regardless which selection I make.
Using the "PREVIEW" option to the REPORT FORM command instead of "TO PRINTER" I can view the entire formatted report, but there is no way that the preview can be redirected to any other type of output.
It appears to me that the way the command set is structured, the only way to get a report output is through the "report form / printer" interface. It also appears that the "to file" direction is through that same interface.
There were a couple of submnissions concerning this problem in the 2008 time frame. The only solution offered was to adjust tyhe TIME function for faster processors in the FoxPro config file. I tried this, but it has no effect on the problem.
https://bugs.winehq.org/show_bug.cgi?id=47933
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |printing Component|programs |spooler
https://bugs.winehq.org/show_bug.cgi?id=47933
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Component|spooler |-unknown
--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com --- Please attach the FULL log. https://wiki.winehq.org/Bugs
https://bugs.winehq.org/show_bug.cgi?id=47933
--- Comment #2 from Jim JSladek@juno.com --- Created attachment 65661 --> https://bugs.winehq.org/attachment.cgi?id=65661 Terminal Output from start of program to point of failure
The terminal output is the same whether it is the report sent to printer (which fails) or report is displayed.
The only difference is that terminal output of report sent to printer locks at the time of failure whereas terminal output of report sent to display continues to quitting the process and closing FoxPro with no incident reported on terminal output.
https://bugs.winehq.org/show_bug.cgi?id=47933
--- Comment #3 from Jim JSladek@juno.com --- Created attachment 65662 --> https://bugs.winehq.org/attachment.cgi?id=65662 Screenshot at point of failure of the program running in FoxPro
This screenshot shows the point of failure indicating the line of code that initiates the failure, ie. the alleged "printer not ready".
The same program/process runs through printer output withpout failure in WinXP.
https://bugs.winehq.org/show_bug.cgi?id=47933
--- Comment #4 from Jim JSladek@juno.com --- I normally do not print from any other wine programs, but I tested printing from 'notepad' this morning and there is printer output.
In terminal, the same "error" lines shown with FoxPro exist are shown with 'notepad'.
https://bugs.winehq.org/show_bug.cgi?id=47933
--- Comment #5 from Jim JSladek@juno.com --- Needinfo????? I don't have any more info than what I have posted. Please explain.
https://bugs.winehq.org/show_bug.cgi?id=47933
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|1 |0 Status|NEEDINFO |UNCONFIRMED CC| |z.figura12@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47933
Detlef Riekenberg wine.dev@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine.dev@web.de
--- Comment #6 from Detlef Riekenberg wine.dev@web.de --- (In reply to Jim from comment #5)
Needinfo????? I don't have any more info than what I have posted. Please explain.
https://bugs.winehq.org/show_bug.cgi?id=47933
--- Comment #7 from Jim JSladek@juno.com --- According to PCLinuxOS software testing, FPW totally failed (see bug 50618) in current wine releases due to cessation of 16-bit support above release 4.0.4
It is very likely that there will be no interest in resolving this bug - it may as well be dropped from the queue.
https://bugs.winehq.org/show_bug.cgi?id=47933
--- Comment #8 from Zebediah Figura z.figura12@gmail.com --- (In reply to Jim from comment #7)
According to PCLinuxOS software testing, FPW totally failed (see bug 50618) in current wine releases due to cessation of 16-bit support above release 4.0.4
It is very likely that there will be no interest in resolving this bug - it may as well be dropped from the queue.
16-bit support was never dropped; it was probably accidentally broken at some point.
-
WineHQ Bugzilla