https://bugs.winehq.org/show_bug.cgi?id=50618
Bug ID: 50618 Summary: FoxPro for Windows 2.6a fails to start Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: JSladek@juno.com Distribution: ---
Created attachment 69308 --> https://bugs.winehq.org/attachment.cgi?id=69308 Terminal output with both start conditions
Any attempt to start foxprow.exe with or without an appended program script results in a program crash. Attached are copies of terminal output for both types or foxprow start.
https://bugs.winehq.org/show_bug.cgi?id=50618
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal
--- Comment #1 from Austin English austinenglish@gmail.com --- Not critical. Does this have a free demo/download available?
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #2 from Jim JSladek@juno.com --- Maybe https://winworldpc.com/product/foxpro/26
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #3 from Jim JSladek@juno.com --- Problems started immediately after the following updates were made:
wine32.32bit 4.0.1 -> 6.0.3
wine-mono 4.7.5 -> 5.1.1
wine64 4.0.1 -> 6.0.3
winegecko 2.47 -> 2.47.2
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #4 from Jim JSladek@juno.com --- Created attachment 70612 --> https://bugs.winehq.org/attachment.cgi?id=70612 Updated output with actual program file start
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #5 from Jim JSladek@juno.com --- Comment on attachment 70612 --> https://bugs.winehq.org/attachment.cgi?id=70612 Updated output with actual program file start
Problem only occurs with wine32-32bit and wine64 updated. Other wine file updates previpously mentioned have no adverse effect.
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #6 from Jim JSladek@juno.com --- According to PCLinuxOS software testing, FPW failed in releases 4.12, 5.0.5, 6.0, 6.0.1 & 6.16 - the common problem being that 16-bit support was dropped above release 4.0.4
That appears to be the answer to the problem. It's not a bug, but a wine configuration decision.
https://bugs.winehq.org/show_bug.cgi?id=50618
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- Fails for me even in wine-2.20 with a "dive by zero" exception. Anything else you did to have it working with older wine version?
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #8 from Jim JSladek@juno.com --- As far as I can recall, FPW has worked under wine up through 4.0.1 - the PCLinuxOS software tester has started it with 4.0.4, but nothing successfully above wine 4.
I have done nothing to enable the running of FPW in wine. I don't recall which earlier versions I had been running, because at one point I was running FPW in a Win95 VM. The only function in FPW that had not worked under wine was the print output from scripted dialog (Bug 47933).
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #9 from Fabian Maurer dark.shadow4@web.de --- Does it work when you downgrade to wine 4.0.1 again? If so, even in a clean WINEPREFIX? Because if not, there might be some other issue here...
https://bugs.winehq.org/show_bug.cgi?id=50618
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win16
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #10 from Jim JSladek@juno.com --- The tests that I have run thus far:
On my main system, I have wine401 installed - when wine was upgraded to wine6 recently, I saw the failure. I immediatly returned that system via image restoration to the system using wine401. And I am no doing any further testing on thta system.
On a test system with the same OS, that was upgraded to wine6, FPW, of course, didn't work and I have been working with the PCLOS software people to try and determine the problem. That is where I received the list of versions they held that did or did not work; ie. anything they held above wine404 failed.
I received a copy of wine404 to try and I removed wine6 using synaptic and installed the received wine404 via command line. It worked as expected. I have no way of going back to wine 401 at this point other than restoring this test version.
I made a comment this morning on my other bug report (47933) with reference to wine no longer supporting 16-bit after wine404, to which a return comment denied the discontinuing of 16-bit support and that it may have been accidentally broken at some point.
According to the comments I received from PCLOS, wine412 failed. So the 16-bit failure in wine occurred somewhere between 404 and 412 .........
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #11 from Fabian Maurer dark.shadow4@web.de --- Made new issue for my bug: bug 51750.
https://bugs.winehq.org/show_bug.cgi?id=50618
--- Comment #12 from Jim JSladek@juno.com --- I have no idea what happened, but the pclos software testers got a stable wine601 and ran FoxPro against it and IT RAN WITHOUT FAILURE.
Whatever you wine devs did, keep doing it.
https://bugs.winehq.org/show_bug.cgi?id=50618
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1
--- Comment #13 from Fabian Maurer dark.shadow4@web.de --- What's the state on this? Please retest as soon as wine-7.23 is out, this should work fine now.
-
WineHQ Bugzilla