http://bugs.winehq.org/show_bug.cgi?id=33408
Bug #: 33408 Summary: CAJViewer 7.2 needs MDAC while installing Product: Wine Version: 1.5.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: litimetal@gmail.com Classification: Unclassified
0. download and type $wine 'CAJViewer 7.2.self.exe' 1. just click Next 2. Before the installation finished, the installer reportered that MDAC 2.8 is needed, but I closed that dialog, and the installation finished successfully. 3. I don't know if it has more influnce than an annoying dialog.
winetricks mdac28 to workaround it.
By the way, this bug doesn't block bug 33404
http://bugs.winehq.org/show_bug.cgi?id=33408
lizhenbo litimetal@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, Installer URL| |http://viewer.d.cnki.net/CA | |JViewer%207.2.self.exe
http://bugs.winehq.org/show_bug.cgi?id=33408
--- Comment #1 from lizhenbo litimetal@gmail.com --- Still in wine 1.7.11
https://bugs.winehq.org/show_bug.cgi?id=33408
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net, | |super_man@post.com
--- Comment #2 from super_man@post.com --- This bug could be one of those wontfix.
https://bugs.winehq.org/show_bug.cgi?id=33408
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Summary|CAJViewer 7.2 needs MDAC |Many applications need |while installing |Microsoft Data Access | |Components 2.7 ('winetricks | |-q mdac27' is a workaround) Ever confirmed|0 |1 Severity|normal |enhancement
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
--- quote --- This bug could be one of those wontfix. --- quote ---
well, there are also "provide MFC implementation" type tickets which I personally consider a huge waste of time for any takers. Arguing with people about the scope of Wine and what are realistic goals is something I leave for some mailing list.
Refining summary, making it a rather large meta feature request since it's a framework/collection of various technologies and components.
Seriously taken you would need to add dependencies of many other tickets here which is not feasible at all.
--- snip --- 0016:Call advapi32.RegOpenKeyExA(80000002,00573980 "Software\Microsoft\DataAccess\",00000000,00000001,0033f864) ret=27009bd8 0016:Ret advapi32.RegOpenKeyExA() retval=00000000 ret=27009bd8 0016:Call advapi32.RegQueryValueExA(00000070,005739b8 "FullInstallVer",00000000,0033f860,00000000,00000000) ret=27009bff 0016:Ret advapi32.RegQueryValueExA() retval=00000002 ret=27009bff ... 0016:Call msvcr71._mbscmp(7c220078 "",004db1a8 "2.70.7713.4") ret=7c144dbb 0016:Ret msvcr71._mbscmp() retval=ffffffff ret=7c144dbb ... 0016:Call winex11.drv.SetWindowText(000100c8,0016ec58 L"???????MDAC (Microsoft Data Access Components) 2.7?????,?????????????") ret=7e9eec3b --- snip ---
Either add a registry key, faking MDAC installation >= 2.70.7713.4 which obviously can't work at runtime if the app requires MDAC or use 'winetricks -q mdac27'.
Since 'winetricks' provides an easy workaround, lowing severity.
--- snip --- 000b:Call advapi32.RegOpenKeyExA(80000002,00573980 "Software\Microsoft\DataAccess\",00000000,00000001,0033f864) ret=27009bd8 000b:Ret advapi32.RegOpenKeyExA() retval=00000000 ret=27009bd8 000b:Call advapi32.RegQueryValueExA(00000074,005739b8 "FullInstallVer",00000000,0033f860,00000000,00000000) ret=27009bff 000b:Ret advapi32.RegQueryValueExA() retval=00000000 ret=27009bff ... 000b:Call msvcr71.strlen(0033f890 "2.71.9040.2") ret=7c16a55d 000b:Ret msvcr71.strlen() retval=0000000b ret=7c16a55d ... 000b:Call msvcr71._mbscmp(005739e0 "2.71.9040.2",004db1a8 "2.70.7713.4") ret=7c144dbb 000b:Ret msvcr71._mbscmp() retval=00000001 ret=7c144dbb --- snip ---
Regards
https://bugs.winehq.org/show_bug.cgi?id=33408
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gsagostinho@hotmail.com
--- Comment #4 from Anastasius Focht focht@gmx.net --- *** Bug 37201 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=33408
Hin-Tak Leung htl10@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |htl10@users.sourceforge.net
https://bugs.winehq.org/show_bug.cgi?id=33408
dpat@syn-net.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dpat@syn-net.org
--- Comment #5 from dpat@syn-net.org --- (In reply to Anastasius Focht from comment #3)
--- quote --- This bug could be one of those wontfix. --- quote ---
well, there are also "provide MFC implementation" type tickets which I personally consider a huge waste of time for any takers. Arguing with people about the scope of Wine and what are realistic goals is something I leave for some mailing list.
Is there any "official" documentation on how the Wine projects intend to handle something like Microsoft Data Access Components (specifically MDAC 2.7 / MDAC 2.8)?
I couldn't find anything in the FAQ[1]. MDAC is only mentioned in the Wine User's Guide in the context of "Using Windows ODBC drivers" and MSSQL support[2].
I still wonder if Wine will and/or wants to support features provided by the Microsoft Data Access Components.
[1] https://gitlab.winehq.org/wine/wine/-/wikis/FAQ [2] https://gitlab.winehq.org/wine/wine/-/wikis/Wine-User%27s-Guide#using-window...