run Phierha (Pixia), graphics editing program, on Ubuntu, Kubuntu, have running on one installation (on same machine) for quite some time; new installation ran it well for a month and suddenly started erroring on dlls that are part of the program package; tried reinstalling, no go. Registry looks same as for the other installation; in particular, all the dlls that are erroring are all registered, in the same way and with the correct path.
Any ideas, anyone? Thanks for any help.
dll errors on program dlls--works on same distro, machine
Re: dll errors on program dlls--works on same distro, machin
Start with fresh wineprefix, reinstall your program: http://wiki.winehq.org/FAQ#head-faf9617 ... 522d490faf
Did that before my original post.
The result does much the same thing, with this difference, it will load an image and one may edit it, without any complaint, but cannot save to any of the formats, the dlls of which gave errors, which is unfortunately, every thing but mac and a couple of other esoteric formats--these are the errors to which I referred originally.
Each of the dlls in folder 'file_r' provides the code for saving the images in different formats. All the normal ones, including the native Phierha format, pxa, have dlls which give errors on loading the program. The only ones left are apparently usable in principle, but not by me, or LINUX.
It seems as if these have been blocked by some prior claim on the format, possibly in XnView, or FastStone Image Viewer, which I also have installed. These latter two mostly work, but that is no different from the other installations I've done, none of which had this problem.
The only difference here is that I have FoxitReader installed, and have hacked it to make an entry on the context menu. I can't understand how this could cause this problem, and am not enthusiastic about undoing it--it was time consuming to do (KDE seems to want to prevent true editing of the command line for this).
Hope this is informative, and thanks for your help.
The result does much the same thing, with this difference, it will load an image and one may edit it, without any complaint, but cannot save to any of the formats, the dlls of which gave errors, which is unfortunately, every thing but mac and a couple of other esoteric formats--these are the errors to which I referred originally.
Each of the dlls in folder 'file_r' provides the code for saving the images in different formats. All the normal ones, including the native Phierha format, pxa, have dlls which give errors on loading the program. The only ones left are apparently usable in principle, but not by me, or LINUX.
It seems as if these have been blocked by some prior claim on the format, possibly in XnView, or FastStone Image Viewer, which I also have installed. These latter two mostly work, but that is no different from the other installations I've done, none of which had this problem.
The only difference here is that I have FoxitReader installed, and have hacked it to make an entry on the context menu. I can't understand how this could cause this problem, and am not enthusiastic about undoing it--it was time consuming to do (KDE seems to want to prevent true editing of the command line for this).
Hope this is informative, and thanks for your help.
I'm not so sure about that. You said yourself about FoxitReader... If you don't want to wipe it, use different wineprefix altogether: http://wiki.winehq.org/FAQ#head-faf9617 ... 522d490fafjhthayer wrote:Did that before my original post.
You will note that most of the .dlls involved, which must be linked in the same fashion, i.e., an entry in the registry, load just fine, no errors. Right in the middle of the registry list of the program dlls that are used are the ones about which it complains--about 8 out of 13 of them, the rest all functioning with no errors. This should not be any different in prefix than the same installation on my other Lucid installation (on the same machine) which works perfectly well, as did this one for the first couple of weeks it was up and running. All of the programs running on WINE on this machine use the default prefix, and all were installed in the same way to prevent such problems. You are entitled to question whether I understood what you meant, as I am asking for the help, of course.
In any case, the particular matter is moot, since I attempted to uninstall the program once again, and this time, the installer barfed out errors, saying that it couldn't and then that it (msiexec) wasn't installed, and things have gone from bad to worse. Trashing the whole thing is undoubtedly the easiest way out, but I like to know, where possible, what went wrong.
Thanks,
Joe
In any case, the particular matter is moot, since I attempted to uninstall the program once again, and this time, the installer barfed out errors, saying that it couldn't and then that it (msiexec) wasn't installed, and things have gone from bad to worse. Trashing the whole thing is undoubtedly the easiest way out, but I like to know, where possible, what went wrong.
Thanks,
Joe
For completeness, I will recount my lack of progress.
The aspect of this which can be considered notable is that the Phierha package I used (I generally download a new copy any time I reinstall) is actually different--between the previous version and this one, Isao Maruoka apparently changed to the newer msi installer, which is the one provided as a service on XP, and the package available via winetricks no longer works for this (similarly to the MS Office problem). Unfortunately, there is some kind of disjuncture between the WINE version and what is included in the .msi package; further, the repair options of the MS package are not available in the WINE replacement. Not at all sure which way to go from here.
Thanks for any ideas.
The aspect of this which can be considered notable is that the Phierha package I used (I generally download a new copy any time I reinstall) is actually different--between the previous version and this one, Isao Maruoka apparently changed to the newer msi installer, which is the one provided as a service on XP, and the package available via winetricks no longer works for this (similarly to the MS Office problem). Unfortunately, there is some kind of disjuncture between the WINE version and what is included in the .msi package; further, the repair options of the MS package are not available in the WINE replacement. Not at all sure which way to go from here.
Thanks for any ideas.
For anyone interested in this thread--this problem has a couple of points:
1. UNINSTALLING: Beware of which installer one uses, be sure to use the same one for uninstalling. Sometimes, the uninstall key doesn't have the correct command--that was the case with Phierha--see the MsiExec documentation, which is not precisely followed by the WINE version. The install flag, /I, and the uninstall flag, /X, are followed, but not the others. You may need to use the wineconsole command to execute it, and be sure to quote the flag and the GUID separately. Programs that explicitly provide uninstall commands usually work sufficiently well. Those that don't must either be hand weeded out of the registry, or use an uninstaller (I have used TUn with good results); excess registry garbage can foul up a reinstall very easily.
2. INSTALLATION ORDER: I found all of the Windows programs to be fairly sensitive to which application was installed last. In this case, the errors were only eliminated by installing the three PDF viewers and two image viewers first, then another four graphics programs, and finally, Phierha. Pixia I found to follow the same pattern. This way, they all work, at least so far.
1. UNINSTALLING: Beware of which installer one uses, be sure to use the same one for uninstalling. Sometimes, the uninstall key doesn't have the correct command--that was the case with Phierha--see the MsiExec documentation, which is not precisely followed by the WINE version. The install flag, /I, and the uninstall flag, /X, are followed, but not the others. You may need to use the wineconsole command to execute it, and be sure to quote the flag and the GUID separately. Programs that explicitly provide uninstall commands usually work sufficiently well. Those that don't must either be hand weeded out of the registry, or use an uninstaller (I have used TUn with good results); excess registry garbage can foul up a reinstall very easily.
2. INSTALLATION ORDER: I found all of the Windows programs to be fairly sensitive to which application was installed last. In this case, the errors were only eliminated by installing the three PDF viewers and two image viewers first, then another four graphics programs, and finally, Phierha. Pixia I found to follow the same pattern. This way, they all work, at least so far.
