Hi All, I've been using NoiseNinja 2.10 (http://www.picturecode.com/nn_standalone.htm) on Linux (Debian unstable, kernel 2.6.11) using wine. It used to work fine, then Debian updated their packages, and wine broke (that's the price I pay for using Debian unstable, I guess). I then found out packages were also available from winehq.org. I've added them to my system as described here: http://www.winehq.org/site/download-deb All was fine for some time. A few days ago a new version came, and Noise Ninja no longer works. I've deleted my .wine directory and had wine re-create it, then I re-installed Noise Ninja. The installer worked, the program did not. I installed another Windows app that I used to run with my old installation (LTSpice, http://ltspice.linear.com/software/swcadiii.exe): both installer and app worked fine, so wine is basically OK. I don't know what else to do now, I've read the FAQ and adjusted Windows emulation settings as suggested there, to no avail. Also, tried running the program with 'Windows-like' path (C:\Program Files...) and by changing to the EXE file's directory and running it there with wine NoiseNinja.exe. Is this time to raise a bug report? I'm a software guy myself (though not C, so won't be able to debug and fix this), so I know how annoying unjustified bug reports are. Since the provided Debian packages don't contain bug_report.pl, I've downloaded the source and tried running the utility from there. It complained about my version of the wine binary being a stripped one, with no debug symbols. Is there a debug-enabled packaged version available, or do I have to compile it myself? If the latter, will the apt-get build-dep wine ; apt-get --build source wine method give me a non-stripped version? Thanks in advance, Kofa
> All was fine for some time. A few days ago a new > version came, and Noise > Ninja no longer works. I installed another Windowsapp> that I used to run with > my old installation both installer and app > worked fine, so wine is basically OK. > > I don't know what else to do nowWelcome to the world of Wine. Things work perfectly one month, and the next month, they break. File a bug, ask for help, and if you're lucky (am I mean LUCKY), then somebody will give you a hand. I've been dealing with this type of thing since I began using Wine over a year and 1/2 ago. I've also raised the issue to the developers coming close to a "flame war", but in the end, nothing was resolved. http://winehq.org/?issue=294#Fixing%20Bugs In any case, for the rest us users, we can try to help each other. So, send over the output, and if we have an idea of what's going on, we'll reply with some pointers. :) Hiji __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hi Kofa!
Yes there are many experts (not me, I'm also just a person who tries to
use
it with alternate success so maybe I've got some practical experience) that
can help You, but we need more info.
It is not enough to tell "the program doesn't work". The problem
should be
described more exactly, especially:
1) Start the program from a shell and look for the console output. Normally
there are many warnings about function stubs and other, not every message is
fatal but some of them may indicate the problem. However, for example when
a wine debugger is started, it's a serious problem somewhere and the console
output is the most valuable thing. So what's there in Your case ?
2) What does (or doesn't) the program do ? Please be more specific:
- It even doesn't open its initial window.
- It opens the window but crashes/freezes later.
- It performs some basic interaction with an user but is otherwise unusable
(describe why, what's wrong)
- It almost works but something serious disables its regular usage
(unable to save its results etc.)
We are looking for some of the symptoms above. Maybe we can find where the
problem is and a real developer will then fix it much more quickly.
With regards, Pavel
Pavel Troller wrote:> So, my intuition was totally wrong :-). However, now it would be good to > examine the address at which the result has to be stored, or to disassemble > some bytes before the indicated instruction to find why EAX was zero.I'll leave that to the pros, I guess :-) Kofa
Am Sa, Nov 05, 2005 at 11:09:32 +0100 schrieb Kov?cs Istv?n:> I've been using NoiseNinja 2.10Hi Kofa, I just tried the program in a WineTools setup and it seems to work. So try using WineTools to make a base setup and the install Noise Ninja again. Tell us if it works for you. Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"