http://bugs.winehq.org/show_bug.cgi?id=34867
Bug #: 34867 Summary: Unhandled exception: divide by zero... Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: kazikkazimierczak@gmail.com Classification: Unclassified
Created attachment 46475 --> http://bugs.winehq.org/attachment.cgi?id=46475 The messages from wine.
Helo,
When I start to run parity.exe wine crashes. My system is Ubuntu 13.10 and it contians:
wine-gecko1.4:amd64 1.4.0-0ubuntu2 amd64 Microsoft Windows compatibility layer (embedded web browser) wine-gecko1.4:i386 1.4.0-0ubuntu2 i386 Microsoft Windows compatibility layer (embedded web browser) wine1.4 1.4.1-0ubuntu7 amd64 Microsoft Windows Compatibility Layer (Binary Emulator and Library) wine1.4-amd64 1.4.1-0ubuntu7 amd64 Microsoft Windows Compatibility Layer (64-bit support) wine1.4-i386 1.4.1-0ubuntu7 i386 Microsoft Windows Compatibility Layer (32-bit support) winetricks 0.0+20130702+svn1032-1 all package manager for WINE to install software easily
Could you help me?
Rgds, Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #1 from Austin English austinenglish@gmail.com 2013-11-06 15:13:44 CST --- Please retest in 1.7.5.
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #2 from Kazik kazikkazimierczak@gmail.com 2013-11-10 15:30:47 CST --- Created attachment 46496 --> http://bugs.winehq.org/attachment.cgi?id=46496 errors for 1.7.4
The erroros after starting wine-1.7.4
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #3 from Kazik kazikkazimierczak@gmail.com 2013-11-10 15:36:53 CST --- (In reply to comment #1)
Please retest in 1.7.5.
I didn't test with 1.7.5, because there are no avaliable packages for my Linux Ubuntu 13.10 (there are 1.7.4. only)
$ dpkg -l | grep wine wine-gecko1.4:amd64 1.4.0-0ubuntu2 amd64 Microsoft Windows compatibility layer (embedded web browser) wine-gecko1.4:i386 1.4.0-0ubuntu2 i386 Microsoft Windows compatibility layer (embedded web browser) wine-gecko2.24:amd64 2.24-0ubuntu1~ppa1 amd64 Microsoft Windows compatibility layer (embedded web browser) wine-gecko2.24:i386 2.24-0ubuntu1~ppa1 i386 Microsoft Windows compatibility layer (embedded web browser) wine-mono0.0.8 0.0.8-0ubuntu1~ppa2 all Microsoft Windows compatibility layer (.NET compatibility) wine1.4 1.4.1-0ubuntu7 amd64 Microsoft Windows Compatibility Layer (Binary Emulator and Library) wine1.4-amd64 1.4.1-0ubuntu7 amd64 Microsoft Windows Compatibility Layer (64-bit support) wine1.4-i386 1.4.1-0ubuntu7 i386 Microsoft Windows Compatibility Layer (32-bit support) wine1.7 1.7.4-0ubuntu4~saucy1 amd64 Microsoft Windows Compatibility Layer (Binary Emulator and Library) wine1.7-amd64 1.7.4-0ubuntu4~saucy1 amd64 Microsoft Windows Compatibility Layer (64-bit support) wine1.7-i386 1.7.4-0ubuntu4~saucy1 i386 Microsoft Windows Compatibility Layer (32-bit support) winetricks 0.0+20130707~precise1~ppa1 amd64 Microsoft Windows Compatibility Layer (winetricks)
Do you have any idea?
Rgds., Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Version|unspecified |1.7.4 Summary|Unhandled exception: divide |16-bit app "parity.exe" |by zero... |fails on startup with | |divide by zero
--- Comment #4 from Anastasius Focht focht@gmx.net 2013-11-10 16:05:32 CST --- Hello folks,
looks like an old 16-bit app. What is "parity.exe"? Is there a download available?
Regards
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #5 from Kazik kazikkazimierczak@gmail.com 2013-11-11 05:35:39 CST --- (In reply to comment #4)
Hello folks,
looks like an old 16-bit app. What is "parity.exe"? Is there a download available?
Regards
Hi,
I attached Parity-install.zip. Unpack the file, and run INSTALL.EXE. Then, after installing, run parity.exe.
Rgds., Kazik (In reply to comment #4)
Hello folks,
looks like an old 16-bit app. What is "parity.exe"? Is there a download available?
Regards
Hi,
The installation is here. ftp://195.245.68.6/outgoing/kz/
- unpack the file Parity-install.zip - run INSTALL.EXE - in destination directory run parity.exe
The error is at the beginning - during starting parity.exe.
Regards, Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #6 from Kazik kazikkazimierczak@gmail.com 2013-11-17 15:18:37 CST --- (In reply to comment #1)
Please retest in 1.7.5.
I can't find wine 1.7.5 or 1.7.6 packages for Ubuntu 13.10. I was traing to install from repository - the way as follow:
$ sudo add-apt-repository ppa:ubuntu-wine/ppa $ sudo apt-get update $ sudo apt-get install wine1.7 winetricks
... bat there still is 1.7.4.
I have to wait few days.
Thanks, Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #7 from Kazik kazikkazimierczak@gmail.com 2013-11-25 15:12:52 CST --- Created attachment 46640 --> http://bugs.winehq.org/attachment.cgi?id=46640 Wine 1.7.6 errors
The attachment contains the log/errors just after starting parity.exe.
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #8 from Kazik kazikkazimierczak@gmail.com 2013-11-25 15:24:01 CST --- The wine 1.7.6 didn't help. The errors for 1.7.6 are at one my post before.
Summary: System: Ubuntu 13.10 $ uname -r 3.11.0-13-generi $ cat /etc/debian_version wheezy/sid
ii wine-gecko2.24:amd64 2.24-0ubuntu1~ppa1 amd64 Microsoft Windows compatibility layer (embedded web browser) ii wine-gecko2.24:i386 2.24-0ubuntu1~ppa1 i386 Microsoft Windows compatibility layer (embedded web browser) ii wine-mono0.0.8 0.0.8-0ubuntu1~ppa2 all Microsoft Windows compatibility layer (.NET compatibility) ri wine1.7 1.7.6-0ubuntu2~saucy1 amd64 Microsoft Windows Compatibility Layer (Binary Emulator and Library) ii wine1.7-amd64 1.7.6-0ubuntu2~saucy1 amd64 Microsoft Windows Compatibility Layer (64-bit support) ii wine1.7-i386 1.7.6-0ubuntu2~saucy1 i386 Microsoft Windows Compatibility Layer (32-bit support) ii winetricks 0.0+20130707~precise1~ppa1 amd64 Microsoft Windows Compatibility Layer (winetricks)
Could you look at it, please?
Thank for your help. Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #9 from Kazik kazikkazimierczak@gmail.com --- Helo,
How do you see it - are there the chances of repairing this error?
Thx, Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #10 from Kazik kazikkazimierczak@gmail.com --- Do not really have here someone who could fix it, what worked before?
Kazik
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #11 from Austin English austinenglish@gmail.com --- (In reply to Kazik from comment #10)
Do not really have here someone who could fix it, what worked before?
Kazik
When did it work?
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #12 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #11)
(In reply to Kazik from comment #10)
Do not really have here someone who could fix it, what worked before?
Kazik
When did it work?
It doesn't install for me in 1.2, 1.4.1, 1.6, or wine-1.7.15-112-g2aad5d7 in a clean wineprefix. Fedora20, wine32.
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #13 from Kazik kazikkazimierczak@gmail.com --- (In reply to Austin English from comment #12)
(In reply to Austin English from comment #11)
(In reply to Kazik from comment #10)
Do not really have here someone who could fix it, what worked before?
Kazik
When did it work?
It doesn't install for me in 1.2, 1.4.1, 1.6, or wine-1.7.15-112-g2aad5d7 in a clean wineprefix. Fedora20, wine32.
It worked still as I remember - 2-3 years ago. The installation program actually does not end properly. But ignore it. Cancel the installation and run the parity.
Rgrds, Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #14 from Austin English austinenglish@gmail.com --- (In reply to Kazik from comment #13)
It worked still as I remember - 2-3 years ago. The installation program actually does not end properly. But ignore it. Cancel the installation and run the parity.
Rgrds, Kazik
Thanks. With that trick, it installs in wine-1.7.15-112-g2aad5d7. It crashes on start, so I tried wine-1.2 There, I get the divide by zero, but the GUI does start up. So there's a separate regression. I'll file a bug for it.
https://bugs.winehq.org/show_bug.cgi?id=34867
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, win16 URL| |ftp://195.245.68.6/outgoing | |/kz/
https://bugs.winehq.org/show_bug.cgi?id=34867
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #15 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #14)
(In reply to Kazik from comment #13)
It worked still as I remember - 2-3 years ago. The installation program actually does not end properly. But ignore it. Cancel the installation and run the parity.
Rgrds, Kazik
Thanks. With that trick, it installs in wine-1.7.15-112-g2aad5d7. It crashes on start, so I tried wine-1.2 There, I get the divide by zero, but the GUI does start up. So there's a separate regression. I'll file a bug for it.
Well, there may be a regression, but it's still somewhat of a race or random, some commits will fail to run but after a retry or two, do work.
But, win16 land, I don't see this being fixed anytime soon..
http://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #16 from Kazik kazikkazimierczak@gmail.com --- Hi,
Parity - this application previously behaved correctly. When you modifying code, something has been broken. I do not know what, I'm a vet, I treat animals and this is for me the secret knowledge. I do not use Widows and use Linux only, and this problem complicates me my job - I can't upgrade my Linux etc,. I hope, you are able to repair it.
Mnay thank for your hard job, Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #17 from Kazik kazikkazimierczak@gmail.com --- (In reply to Austin English from comment #15)
(In reply to Austin English from comment #14)
(In reply to Kazik from comment #13)
It worked still as I remember - 2-3 years ago. The installation program actually does not end properly. But ignore it. Cancel the installation and run the parity.
Rgrds, Kazik
Thanks. With that trick, it installs in wine-1.7.15-112-g2aad5d7. It crashes on start, so I tried wine-1.2 There, I get the divide by zero, but the GUI does start up. So there's a separate regression. I'll file a bug for it.
Well, there may be a regression, but it's still somewhat of a race or random, some commits will fail to run but after a retry or two, do work.
But, win16 land, I don't see this being fixed anytime soon..
I'm sorry, but I do not understand this way of working - it's worked and has been broken?
Rgds., Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #18 from Kazik kazikkazimierczak@gmail.com --- (In reply to Austin English from comment #15)
(In reply to Austin English from comment #14)
(In reply to Kazik from comment #13)
It worked still as I remember - 2-3 years ago. The installation program actually does not end properly. But ignore it. Cancel the installation and run the parity.
Rgrds, Kazik
Thanks. With that trick, it installs in wine-1.7.15-112-g2aad5d7. It crashes on start, so I tried wine-1.2 There, I get the divide by zero, but the GUI does start up. So there's a separate regression. I'll file a bug for it.
Well, there may be a regression, but it's still somewhat of a race or random, some commits will fail to run but after a retry or two, do work.
But, win16 land, I don't see this being fixed anytime soon..
I would like to ask - is the hope that it will be that fixed?
I'm waiting a year...
Rgrds., Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #19 from Kazik kazikkazimierczak@gmail.com --- Hi,
Are there any chances of fixing this bug? (Bug no. 34867)
Thanks, Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
Sagawa sagawa.aki+winebugs@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sagawa.aki+winebugs@gmail.c | |om
https://bugs.winehq.org/show_bug.cgi?id=34867
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #20 from super_man@post.com --- This bug could be easy to fix if someone could figure out where the divide by 0 comes.
Meanwhile you could do regression testing. It means building wine against different versions of wine and running the program. Wine faq has a quide how to do it.
still an issue 1.7.50
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #21 from Kazik kazikkazimierczak@gmail.com --- Hi,
I would like only to ask - are there developers who know how to fix?
Rgds., Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #22 from Sagawa sagawa.aki+winebugs@gmail.com --- Created attachment 53165 --> https://bugs.winehq.org/attachment.cgi?id=53165 hack
Hello, Could you try this patch? It just ignores division by zero on Floating Point Unit (FPU) in Win16 code.
In detail, Wine doesn't handle Win16 FPU exceptions properly yet. I think they should be resolved by win87em.dll. But, I gave up implementing that because I'm not sure about how to call 16-bit routine like Windows 3.0 from 32-bit handler.
The exception is emitted form RLZRUN10.RTS (Realizer 1.0 runtime?). So, the patch might help another application written by Realizer, too.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #23 from Kazik kazikkazimierczak@gmail.com --- I can't - I'm sorry. I'm a veterinarian and cure the animals - I wrote about it. I have no idea - no knowledge about programming - I'm just a user of wine and 16-bits application only. I sent a description regarding wine and serious error only.
My opinion now: Can you write programs? I doubt it. I'm sorry about it, but my application worked before and you (programmers) destroyed it. My first notification was months ago, and has not yet been repaired.
It's a shame for you. Are you programmers - or you want to be a programmer? Probably all of you are amateur in this technology.
In the future I will avoid such Linux solutions
My conclusion - you probably want money for this, for all what was worked before and have been spoiled by you.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #24 from Austin English austinenglish@gmail.com --- (In reply to Kazik from comment #23)
I can't - I'm sorry. I'm a veterinarian and cure the animals - I wrote about it. I have no idea - no knowledge about programming - I'm just a user of wine and 16-bits application only. I sent a description regarding wine and serious error only.
You filed a bug and wanted support. You got support, and now are rejecting it?
My opinion now: Can you write programs? I doubt it. I'm sorry about it, but my application worked before and you (programmers) destroyed it. My first notification was months ago, and has not yet been repaired.
A patch was uploaded for you to test. That would be how it gets repaired, but again, you're not exactly making that easy.
It's a shame for you. Are you programmers - or you want to be a programmer? Probably all of you are amateur in this technology.
Insulting those you seek help from isn't a very good idea.
In the future I will avoid such Linux solutions
My conclusion - you probably want money for this, for all what was worked before and have been spoiled by you.
Not sure how you got that conclusion, no one has asked for money. Again, you filed a bug, Sagawa uploaded a patch (for free), and now you're complaining? Are you a troll or an actual vet?
If you change your mind and want to test the patch, see http://wiki.winehq.org/Patching. Or close the bug as abandoned if you no longer care about the bug you filed.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #25 from super_man@post.com --- (In reply to Sagawa from comment #22)
Created attachment 53165 [details] hack
Hello, Could you try this patch? It just ignores division by zero on Floating Point Unit (FPU) in Win16 code.
In detail, Wine doesn't handle Win16 FPU exceptions properly yet. I think they should be resolved by win87em.dll. But, I gave up implementing that because I'm not sure about how to call 16-bit routine like Windows 3.0 from 32-bit handler.
The exception is emitted form RLZRUN10.RTS (Realizer 1.0 runtime?). So, the patch might help another application written by Realizer, too.
I am not trying to analyze what's happening. Running parity.exe gives me different results. Sometimes I get a hang
"err:ntdll:RtlpWaitForCriticalSection section 0x7bcdc640 "loader.c: loader_section" wait timed out in thread 0039, blocked by 0038, retrying (60 sec) " Sometimes running the exe it doesnt output any console output.
But I was able to run the exe with the hacky patch. I just need to try multiple times and it finally starts. With pure wine you still get the divide by zero.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #26 from Kazik kazikkazimierczak@gmail.com --- Hi,
And the conclusions? You found the errors. And you didn't try to fix them? Congratulations wellbeing. But there is a question - who is the programmer - especially all of you or me? When I read all the answers, I started to doubt.
This case is a good example of how not to seriously traet promises to solve the problems by the opensource community, I think it's a shame for you.
In my small company such treatment the customer or the client has no place - no chance for such approach.
I hope, that my sharp words will let you get back to the reality
Rgds., Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #27 from super_man@post.com --- (In reply to Kazik from comment #26)
Hi,
And the conclusions? You found the errors. And you didn't try to fix them? Congratulations wellbeing. But there is a question - who is the programmer
- especially all of you or me? When I read all the answers, I started to
doubt.
This case is a good example of how not to seriously traet promises to solve the problems by the opensource community, I think it's a shame for you.
In my small company such treatment the customer or the client has no place - no chance for such approach.
I hope, that my sharp words will let you get back to the reality
Rgds., Kazik
Would you work for me for free? If you dont do that, shame on you. It just shows how lazy you are.
I quess you work in a company that gives its prodcuts for free.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #28 from Kazik kazikkazimierczak@gmail.com --- My small company (I'm the owner) is a typical commercial company. We don't receive subsidies from the government. For us - our customers are the most important. Sometimes, amount of money I pay for the development of opensource, but the wine-community gets noting, I'm sure.
Besides - especially to 'super_man' - no one forces you to work for the wine-project for free and spoiled what worked before... Find other hobbies... you are an amateur. The community and the users expect good job and good quality.
Rgds., Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #29 from Austin English austinenglish@gmail.com --- (In reply to Kazik from comment #28)
My small company (I'm the owner) is a typical commercial company. We don't receive subsidies from the government. For us - our customers are the most important. Sometimes, amount of money I pay for the development of opensource, but the wine-community gets noting, I'm sure.
Besides - especially to 'super_man' - no one forces you to work for the wine-project for free and spoiled what worked before... Find other hobbies... you are an amateur. The community and the users expect good job and good quality.
Bugzilla is for discussing bugs, not your views/rants on open source.
https://bugs.winehq.org/show_bug.cgi?id=34867
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #30 from Fabian Maurer dark.shadow4@web.de --- Still present as of wine-4.9.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #31 from Fabian Maurer dark.shadow4@web.de --- Created attachment 64627 --> https://bugs.winehq.org/attachment.cgi?id=64627 Updated hack
Attaching updated hack for wine-4.9. Still works. However, the racecondition is still there - it often deadlocks, but try often enough and it's start.
@Sagawa If you still read this after all this time, what do you think would be the proper way to fix things? Do you have some pointers?
https://bugs.winehq.org/show_bug.cgi?id=34867
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #32 from Sagawa sagawa.aki+winebugs@gmail.com ---
From my point of view, we need the following parts to achieve FPU handling in
16-bit code: Part 1) Set the exception handler into TDB (task data base) inside win87em's _fpmath (BX=3). Win16's TDB has a member named int75. I think it is a good place to save the handler. I'm not sure whether TDB.int75's handler is compatible with win87em's argument. Part 2) Call TDB.int75 handler when the FPU exception occurs. We need investigate where we should call the handler and how do that.
Since I'm not familiar with Win16 exception handling, above assumptions should be verified.
Another point of view, Open Watcom v2 has setup routine for win87em[1]. [1] https://github.com/open-watcom/open-watcom-v2/blob/5d9c9c3109647a5c55880b961...
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #33 from Fabian Maurer dark.shadow4@web.de --- Thanks for your comment! Although I have to admit, I don't know what the linked routine is supposed to do exactly. Do you happen to have links for documentation on those FPU functionality?
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #34 from Sagawa sagawa.aki+winebugs@gmail.com --- I think reading FPU handler code is useful for writing Wine's code because it tells us what the code expects in the stack.
About win87em.dll, please refer Windows 3.1 SDK document. I'm not sure whether the document is open access. Wine's implementation is also helpful to you.
Regarding FPU exception, Intel IA-32 Architectures Software Developer's Manual[1] is the best. FPU handling is described in Chapter 8 and Appendix D, Volume 1.
[1] https://software.intel.com/en-us/articles/intel-sdm
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #35 from Kazik kazikkazimierczak@gmail.com --- Hi,
I would like to ask about the results of your work - any conclusions?
Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|ftp://195.245.68.6/outgoing | |/kz/ | Keywords|download |
--- Comment #36 from Fabian Maurer dark.shadow4@web.de --- @Kazik Not sure if you're talking to me, but I didn't get it working. Problem still present as of wine-5.2. Download link is down, removing it.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #37 from Kazik kazikkazimierczak@gmail.com --- Install is there: http://serwer1982068.home.pl/Parity-install.zip
Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |https://web.archive.org/web | |/20200228081625/http://serw | |er1982068.home.pl/Parity-in | |stall.zip
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #38 from Kazik kazikkazimierczak@gmail.com --- I would like to ask about the chance to run the old wine version (that was running corectly) in the chroot environment - I am thinking of preparing an environmental chroot, in which it worked properly before. What are the chances of such idea to succeed? Will it depend on the actual kernel? I'm using x86_64 now.
Rgds, Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|16-bit app "parity.exe" |Parity 1.5 (16-bit Win 3.x |fails on startup with |app) fails on startup with |divide by zero |divide by zero
--- Comment #39 from Anastasius Focht focht@gmx.net --- Hello Kazik,
--- quote --- I would like to ask about the chance to run the old wine version (that was running corectly) in the chroot environment - I am thinking of preparing an environmental chroot, in which it worked properly before. What are the chances of such idea to succeed? --- quote ---
I've read through the whole comment thread from 2013 and there is nowhere a mention which exact "working" Wine version is meant.
Your comment #13 from 2014-03-30
--- quote --- It worked still as I remember - 2-3 years ago. --- quote ---
I've tested down to Wine 1.3.34 (~2011) and the problem was always present. Austin's comment #14 says Wine 1.2 (2010) also had the divide-by-zero, although non fatal?
Alternatively you could build a custom Wine version based on Wine 5.x or 6.x with the hack from comment #31 applied. But even then it won't run reliably, see comment #31.
$ sha1sum Parity-install.zip ce7b2e6ca38b9662d0fd922be9523fedbff05596 Parity-install.zip
$ du -sh Parity-install.zip 1004K Parity-install.zip
$ wine --version wine-6.0-rc3
Regards
https://bugs.winehq.org/show_bug.cgi?id=34867
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|super_man@post.com |
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #40 from Kazik kazikkazimierczak@gmail.com --- Hi, I would like to express my best wishes to all programming enthusiasts who support the wine project. In a few days it will be 10 years since I reported a problem here that has not been resolved to this day. To tell you the truth, I received a few hints, but due to my profession (I'm not a programmer), I couldn't follow them - they were too mysterious or difficult for me. So I hope that in the next 10 years there will be a talented and clever programmer who will solve this problem. Because for now, it seems that you are bringing shame to the programming community with your behavior. Nevertheless, I wish you well - and remember - the user is the most important, because you have forgotten about it.
Kazik
https://bugs.winehq.org/show_bug.cgi?id=34867
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #41 from Zeb Figura z.figura12@gmail.com --- (In reply to Kazik from comment #40)
I would like to express my best wishes to all programming enthusiasts who support the wine project. In a few days it will be 10 years since I reported a problem here that has not been resolved to this day. To tell you the truth, I received a few hints, but due to my profession (I'm not a programmer), I couldn't follow them - they were too mysterious or difficult for me. So I hope that in the next 10 years there will be a talented and clever programmer who will solve this problem. Because for now, it seems that you are bringing shame to the programming community with your behavior. Nevertheless, I wish you well - and remember - the user is the most important, because you have forgotten about it.
Please remember that Wine is community-driven project, and nobody is paid to work on any given bug. We have many thousands of bugs like this, and all of them depend entirely on volunteer time and interest to fix. This often means that the harder bugs—like this one—will unfortunately go unfixed for years.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #42 from Kazik kazikkazimierczak@gmail.com --- In my company (and elsewhere) you would be fired for such an approach. The customer is the most important. Amateurism cannot be tolerated. Remember this.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #43 from Fabian Maurer dark.shadow4@web.de --- Well, in my company you would get fired if you used your time working on non-company projects. Therefore, we need to work our job and do work on Wine in our free time. Again, most of us are not paid to work on Wine. If your company paid Wine devs to fix this bug specifically, I bet it would be fixed already.
Please understand that there is thousands of open bugs and only a small team of core developers working on Wine. This is just one of many bugs, and, I'm sorry, this one isn't special to most people expect for you.
https://bugs.winehq.org/show_bug.cgi?id=34867
--- Comment #44 from Zeb Figura z.figura12@gmail.com --- (In reply to Kazik from comment #42)
In my company (and elsewhere) you would be fired for such an approach. The customer is the most important. Amateurism cannot be tolerated. Remember this.
Did you miss the part where I said "volunteer" and "community"? Nobody is paying developers to work on these bugs. They're doing it in their free time because they have an interest in fixing bugs and helping the project. There is nothing, metaphorically, to be fired from.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla