[Bug 51750] New: FoxPro for Windows 2.6a crashes on some systems with "Divide by Zero" exception
https://bugs.winehq.org/show_bug.cgi?id=51750
Bug ID: 51750 Summary: FoxPro for Windows 2.6a crashes on some systems with "Divide by Zero" exception Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Created attachment 70641 --> https://bugs.winehq.org/attachment.cgi?id=70641 Crash log
Split off from bug 50618.
Instructions: 1) Download from https://winworldpc.com/download/c3a23335-4f6f-c2a3-11c3-a4c2b14b5404 (https://winworldpc.com/product/foxpro/26) 2) Extract 3) Unpack *.img:
find -iname "*.img" -exec 7z x {} ;
4) run setup.exe 5) go to c:\fpw26, run FOXPROW.EXE
https://bugs.winehq.org/show_bug.cgi?id=51750
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://winworldpc.com/down | |load/c3a23335-4f6f-c2a3-11c | |3-a4c2b14b5404 Keywords| |download, win16
https://bugs.winehq.org/show_bug.cgi?id=51750
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Currently, the program doesn't work on other PCs either, see bug 50618. But it used to work with older wine versions (4.0.1), while for me it doesn't work with older wine versions either. Very strange.
https://bugs.winehq.org/show_bug.cgi?id=51750
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Created attachment 70642 --> https://bugs.winehq.org/attachment.cgi?id=70642 +relay,+seh log on wine-6.16
0104:Call USER.5: INITAPP(02ff) ret=02ef:e2a0 ds=02ff 0104:Ret USER.5: INITAPP() retval=00000001 ret=02ef:e2a0 ds=02ff 0104:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000F18E ip=0000f18e tid=0104 0104:trace:seh:dispatch_exception info[0]=00000000 0104:trace:seh:dispatch_exception info[1]=ffffffff 0104:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised 0104:trace:seh:dispatch_exception eax=0000f184 ebx=00000040 ecx=00000000 edx=00000001 esi=000025a0 edi=000025a2 0104:trace:seh:dispatch_exception ebp=00000000 esp=00005866 cs=02ef ds=02ff es=02ff fs=0063 gs=006b flags=00010286 0104:trace:seh:call_stack_handlers calling handler at 6643DB50 code=c0000005 flags=0 0104:Call KERNEL32.CreateThread(00000000,00000000,664049a0,000f0400,00000000,00000000) ret=66404aae 0104:Call ntdll.RtlCreateUserThread(ffffffff,00000000,00000001,00000000,00000000,00000000,664049a0,000f0400,0149f3c0,0149f3c8) ret=7b073f09
Not sure if this is a/the problem, but it doesn't look good.
https://bugs.winehq.org/show_bug.cgi?id=51750
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- Would be interesting to see if it works for someone on wine-4.0.1, and if so, take a look at a +relay,+seh log from that machine.
https://bugs.winehq.org/show_bug.cgi?id=51750
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- Still present as of wine-7.20.
https://bugs.winehq.org/show_bug.cgi?id=51750
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |53630
https://bugs.winehq.org/show_bug.cgi?id=51750
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Interestingly enough, it works using winevdm (https://github.com/otya128/winevdm) through wine. Although using their 16bit dlls in wine does NOT help. Some issue with the CPU possibly...?
Someone willing to help investigate?
https://bugs.winehq.org/show_bug.cgi?id=51750
--- Comment #6 from Fabian Maurer dark.shadow4@web.de --- Turns out, it is the CPU. Running through qemu-user doesn't help though.
Problem is, that foxpro uses the Win386 dos extender, which has issues when the CPU is too fast (> 333MHz). There's actually a bunch of reports of that issue on Windows, and it doesn't work on my XP VM either.
There is a patch though: https://web.archive.org/web/20060827063240/https://download.microsoft.com/do...
This one makes it run on Wine as well, confirming this is indeed the underlying issue.
Not sure how to fix that, or whether we can even properly fix that. Although it would be nice to have it working in Wine... Weird is, that is seems to work at least on some modern processors, doubt other users have < 333Mhz processors.
Further reading, for those who are curious: https://www.os2museum.com/wp/watcom-win386/
https://bugs.winehq.org/show_bug.cgi?id=51750
Jim JSladek@juno.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |JSladek@juno.com
--- Comment #7 from Jim JSladek@juno.com --- As requested in BUG 53630, my cpu is Intel Core2 E8400. Yes, it's an oldie and that may be why wine is still working (sort of).
I first had failure to start issues with wine 6.0 - BUG 50618 - and returned to wine 4.0.1. I eventually upgraded from wine 4.0.1 perhaps into the wine 7 series and found that it worked until wine 7.16 - BUG 53630 - when I started getting immediate "insufficient memory" failures.
My OS is PCLinuxOS and their repo just added wine 7.20, however, because of problems with wine 7.20 they encountered with FoxPro (worse than 7.19), they altered the repo to install wine 7.0.1 stable which works with FoxPro in all respects except for failure to print output from scripted dialog - BUG 47933 (wine 4.0.1).
I know you only asked for my cpu data, but I thought I'd summarize the whole picture of where I'm coming from.
-
WineHQ Bugzilla