http://bugs.winehq.org/show_bug.cgi?id=18935
Summary: Peachtree First Accounting 2010 install fails because it can't find AVManagerUnified.dll Product: Wine Version: 1.1.23 Platform: PC URL: http://www.peachtree.com/productsServices/tryPeachtree / OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
The installer aborts with the error Error Number: 0x80040702 Description: Failed to load DLL: SASLib Setup will now terminate.
SASLib.dll and its dependency AVManagerUnified.dll are located in c:\windows\temp{*}\ SASLib.dll fails to load because it can't find AVManagerUnified.dll. Is Wine supposed to search the directory containing a DLL for things that DLL depends on?
http://bugs.winehq.org/show_bug.cgi?id=18935
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic.delanoy@gmail.com
--- Comment #1 from Frédéric Delanoy frederic.delanoy@gmail.com 2011-05-31 18:34:05 CDT --- Tested 2012 demo with 1.3.21 Installation aborts due to error stating that "The procedure GetListBoxInfo could not be located in the DLL USER32.dll"
http://bugs.winehq.org/show_bug.cgi?id=18935
--- Comment #2 from Dan Kegel dank@kegel.com 2011-05-31 23:25:58 CDT --- That's a different bug, please file a new report
http://bugs.winehq.org/show_bug.cgi?id=18935
--- Comment #3 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-05-07 16:29:09 CDT --- I can't find the download for PFA2010.
Can you please retry now bug 27385 is fixed?
http://bugs.winehq.org/show_bug.cgi?id=18935
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |focht@gmx.net Resolution| |FIXED
--- Comment #4 from Anastasius Focht focht@gmx.net 2013-05-09 16:33:52 CDT --- Hello folks,
can't reproduce the problem with a similar product flavour, called "Peachtree Quantum 2010 Accountant Edition".
--- snip --- ... 002f:trace:loaddll:load_builtin_dll Loaded L"C:\windows\system32\msvcr100.dll" at 0x7c4b0000: builtin 002f:trace:loaddll:load_native_dll Loaded L"C:\users\focht\Temp\{51EF69CF-70D3-4142-993D-AA97F36484CC}\FWManager.dll" at 0xcae0000: native 002f:trace:loaddll:load_native_dll Loaded L"C:\users\focht\Temp\{51EF69CF-70D3-4142-993D-AA97F36484CC}\AVManagerUnified.dll" at 0xcba0000: native 002f:trace:loaddll:load_native_dll Loaded L"C:\users\focht\Temp\{51EF69CF-70D3-4142-993D-AA97F36484CC}\SASLib.dll" at 0x340000: native ... --- snip ---
Most likely fixed.
$ wine --version wine-1.5.29-208-gfdedaba
Regards
http://bugs.winehq.org/show_bug.cgi?id=18935
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |
--- Comment #5 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-05-10 01:27:32 CDT --- (In reply to comment #4)
Hello folks,
can't reproduce the problem with a similar product flavour, called "Peachtree Quantum 2010 Accountant Edition".
--- snip --- ... 002f:trace:loaddll:load_builtin_dll Loaded L"C:\windows\system32\msvcr100.dll" at 0x7c4b0000: builtin 002f:trace:loaddll:load_native_dll Loaded L"C:\users\focht\Temp\{51EF69CF-70D3-4142-993D-AA97F36484CC}\FWManager.dll" at 0xcae0000: native 002f:trace:loaddll:load_native_dll Loaded L"C:\users\focht\Temp\{51EF69CF-70D3-4142-993D-AA97F36484CC}\AVManagerUnified.dll" at 0xcba0000: native 002f:trace:loaddll:load_native_dll Loaded L"C:\users\focht\Temp\{51EF69CF-70D3-4142-993D-AA97F36484CC}\SASLib.dll" at 0x340000: native ... --- snip ---
Most likely fixed.
You can't mark a bug as fixed simply based on assumption from a "similar product flavour". Let the OP retry if he still has the program download available.
http://bugs.winehq.org/show_bug.cgi?id=18935
--- Comment #6 from Anastasius Focht focht@gmx.net 2013-05-10 03:21:44 CDT --- Hello Frédéric,
why not? It took me some time to find something similar on the internet, to investigate the problem and even find new problems (-> new bug reports). The product code base is the _same_, the installer technology is the _same_. See the trace log snippet where you can clearly see both dlls mentioned in that bug report.
Many bug reporters simply left the Wine project mainly because of real life, Dan is no exception here. These bugs are effectively abandoned until they get picked up by other people. Alternatively these bugs are simply closed by "x times no reaction -> abandon" sweeps which is of course the last resort.
From my point of view Wine Bugzilla is not really in a satisfactory state of
affairs.
There are many hundreds, heck thousands of open bugs that are candidates for immediate close down (based on my experience) and nothing of value would be lost. Many of them are of poor quality, unwillingness/incapability of reporter to provide additional info, mixed up issues/contradicting info, abandoned software or already fixed. It takes time to understand what the reporter actually meant and to _find_ applications to somehow reproduce the problem - years after the bug was created.
Do you want to put the people away that try to make an attempt to improve the situation? I can certainly push my own agenda (which I sometimes do), only reporting/working on bugs in my own interest. Although these are sometimes interesting things from technical perspective the number would be low. So guess what would be the greater loss?
But if you are inclined please feel free and notify Dan about _all_ his open bugs (several hundreds FYI) and ask him to do something about the situation.
Regards
http://bugs.winehq.org/show_bug.cgi?id=18935
--- Comment #7 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-05-10 04:12:40 CDT --- (In reply to comment #6)
Hello Frédéric,
why not? It took me some time to find something similar on the internet, to investigate the problem and even find new problems (-> new bug reports).
I appreciate the time you spent trying to find similar stuff on the internet for sure, that was not my point. I also spend some of my free time on bug reports, you know.
The product code base is the _same_, the installer technology is the _same_. See the trace log snippet where you can clearly see both dlls mentioned in that bug report.
Well, the same dlls are mentioned, true, but you can't say that the "product code base is the same", unless you have access to the source code (which I suppose you don't). There might be slight variations in the code bases that make the bug appear in one app, and not in a similar app.
Many bug reporters simply left the Wine project mainly because of real life, Dan is no exception here.
Well you closed the bug a mere *2* days after I added my comment: that's quite a (too) short amount of time to react IMHO : that's why I reopened the bug. It's always better to have the OP retest, if possible.
These bugs are effectively abandoned until they get picked up by other people. Alternatively these bugs are simply closed by "x times no reaction -> abandon" sweeps which is of course the last resort.
True, if a bug can't be reproduced due to no download available, and no OP reaction, there's not much one can do about the bug, besides closing it.
From my point of view Wine Bugzilla is not really in a satisfactory state of affairs.
There are many hundreds, heck thousands of open bugs that are candidates for immediate close down (based on my experience) and nothing of value would be lost. Many of them are of poor quality, unwillingness/incapability of reporter to provide additional info, mixed up issues/contradicting info, abandoned software or already fixed. It takes time to understand what the reporter actually meant and to _find_ applications to somehow reproduce the problem - years after the bug was created.
Do you want to put the people away that try to make an attempt to improve the situation?
Of course not. I'm sorry if you felt that way. That certainly wasn't my intention. There's no easy solution for the bad average bug quality, I'm afraid, short of trying to "educate" users. FWIW, I've also been "hurt" more than once by bad bugs, as many other volunteers have also been.
I can certainly push my own agenda (which I sometimes do), only reporting/working on bugs in my own interest. Although these are sometimes interesting things from technical perspective the number would be low. So guess what would be the greater loss?
Most (but not all) people work on bugs they care about. You know I don't particularly care about this app either, yet I bothered to download hundreds of megs, register, test and open a new bug (see comment 1). I could as well have marked this bug "closed - abandoned" back then...
But if you are inclined please feel free and notify Dan about _all_ his open bugs (several hundreds FYI) and ask him to do something about the situation.
Spamming him with hundreds of bug notification messages won't certainly help the situation..
Regards,
http://bugs.winehq.org/show_bug.cgi?id=18935
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED
--- Comment #8 from Dan Kegel dank@kegel.com 2013-05-10 10:04:39 CDT --- When I saw Focht's comment, I felt satisfied that his judgement was correct, and his grep of the log does show that the same dll is being loaded from the same place successfully.
I don't know what installer I was testing back in 2009 :-( since I didn't include an sha1sum and filename, but testing 9cc124ea6c27a22a540fac4abcc25197c0360bee PeachtreeBySage2010.exe (which I seem to have downloaded in April 2012) doesn't run into this; it gets quite a ways, then fails with bug 33554.
So I agree with Focht, let's make a calculated guess that this is fixed.
http://bugs.winehq.org/show_bug.cgi?id=18935
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2013-05-10 13:41:10 CDT --- Closing bugs fixed in 1.5.30.
https://bugs.winehq.org/show_bug.cgi?id=18935
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.peachtree.com/pr |https://archive.org/downloa |oductsServices/tryPeachtree |d/Peachtree2010_201603/Peac |/ |htree-2010.iso
--- Comment #10 from Anastasius Focht focht@gmx.net --- Hello folks,
adding stable download link via Internet Archive for documentation.
https://web.archive.org/web/20160126165042/http://www.sage.com:80/us/sage-50...
https://archive.org/download/Peachtree2010_201603/Peachtree-2010.iso
$ sha1sum Peachtree-2010.iso 5461b349ce6acfbc53121f4ef7c0fb2c020f988b Peachtree-2010.iso
$ du -sh Peachtree-2010.iso 625M Peachtree-2010.iso
Quick test reveals it was still not working with Wine 1.5.29 but fixed with Wine 1.5.30 so my test in comment #4 was kinda on spot with the timing.
--- snip --- $ git log --oneline wine-1.5.29...wine-1.5.30 -- dlls/msi
10975967dfc msi: Set the PrimaryVolumePath and PrimaryVolumeSpaceAvailable properties. b98ef8f087c msi: Treat an empty install location as missing. ce6a037abc9 msi: Fix ComputerName property. 8328562e4ce msi: Assume a transform is applicable if it doesn't specify any products. d5fc4ce7729 msi/tests: Add a trailing '\n' to an ok() call and fix a typo. 1ed6bc2e025 msi: Properly map script function return values to MSI errors. 7129293b9a7 msi: Use next cabinet from the media table instead of failing when there is a mismatch with continuous cabinet. e249b930921 msi: Add tests to show that only msi cab filename is taken in case of mismatch with the one given by previous cab. --- snip ---
Regards