http://bugs.winehq.org/show_bug.cgi?id=12018
Summary: SPSS 16 eval for Windows won't install Product: Wine Version: CVS/GIT Platform: Other URL: http://www.spss.com/registration/index.cfm?Demo_ID=37 OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
Install fails when it tries to run regsvr32, which fails with "Runtime Error!" and fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC80.CRT" (the runtime library's needed because of the dll that regsvr32 is registering, not regsvr32 itself).
This is the second app in the last couple days that has had this problem.
http://bugs.winehq.org/show_bug.cgi?id=12018
Yolande Haneder yolande@haneder.biz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yolande@haneder.biz
http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #1 from Anastasius Focht focht@gmx.net 2008-03-15 10:47:38 --- Created an attachment (id=11402) --> (http://bugs.winehq.org/attachment.cgi?id=11402) patch which prevents load failure of SxS-aware Microsoft runtimes
Hello,
you probably ran the setup with default Windows 2000 config. The installer ships newer Visual C++ library DLLs which are to be installed as as shared assemblies. Usually developers just include the appropriate Micro$oft merge modules into their msi project which take care of installing CRT, MFC and ATL runtime as shared side-by-side assemblies (WinSxS).
For pre-Windows XP versions there are special considerations taken. Windows 2000 and earlier have no concept of side-by-side assemblies nor fusion. Hence the shared assemblies get installed into system32 folder. Additionally they are installed into WinSxS in case the user later decides to upgrade the OS (in Windows 2000 and earlier they have no use).
In Windows XP and later shared assemblies are *never* to be installed in system32 (automatically taken care by installer).
When one of these newer SxS-aware runtimes are loaded, some checks for sxs/manifest related things are done:
- existence of specific activation context API - existence of some loaded in-memory libraries (fusion/.NET related) - load path (detect if loaded from system directory)
Attached patch works around this problem. In pre-Windows XP configurations it pretends that the checked activation context entry is not available (which is really the case in native Windows 2000 and earlier). This will keep the SxS-aware runtimes happy and no further checks are done.
Another solution would be to install the app with Windows XP+ configuration which prevents shared assemblies from being put into system32.
I think the patch should be taken into consideration because wine should support all windows versions (and their side-effects) correctly.
Regards
http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #2 from Yolande Haneder yolande@haneder.biz 2008-03-15 12:34:18 --- (In reply to comment #1)
Another solution would be to install the app with Windows XP+ configuration which prevents shared assemblies from being put into system32.
This error does also come up in XP. Do you think the patch would be of some help?
http://bugs.winehq.org/show_bug.cgi?id=12018
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #3 from Anastasius Focht focht@gmx.net 2008-03-15 14:48:01 --- Hello,
--- quote ---
Another solution would be to install the app with Windows XP+ configuration which prevents shared assemblies from being put into system32.
This error does also come up in XP. --- quote ---
Because you didn't do the install on clean ~/.wine. Remove your ~/.wine (from previous winecfg Windows 2000 install), set winecfg to Windows XP, install.
--- quote --- Do you think the patch would be of some help? --- quote ---
No of course not. I post this stuff by pure chance, just for fun... Wenn ich sowas lese, vergeht mir echt die Lust ...
Regards
http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #4 from Dan Kegel dank@kegel.com 2008-03-15 15:38:03 --- Thanks for the analysis! Switching to winxp mode on a clean .wine, or applying that tweak, makes install succeed.
Lass niemand dich entmuntigen. Deine Arbeit ist hervorragend.
http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #5 from Anastasius Focht focht@gmx.net 2008-03-16 07:51:27 --- Hello,
it seems I have caused some discussion with my comments [ironic sic!]. I'm not subscribed to any mailing list at all but I do read them sometimes ...
I don't like backstabbing talk so let's just clear things up here - although bugzilla is the wrong place for this (no, I won't subscribe).
To english readers: the german comment "Wenn ich sowas lese, vergeht mir echt die Lust ..." can be literally translated to "When I read such things, the joy of continuing my work is declining".
First: I'm not a wine developer at all (by definition). I'm a software engineer/expert who happens to be attracted by various problems/challenges surrounding the wine project. My goals/intentions are different from the majority of wine users/developers.
I usually have a rather stressful 10 hour job which differs from the work here (customers demanding quality software solutions for their problems). When I find some time in the evening or on weekends, I spend my already limited spare time on tracking down interesting problems/bugs which sometimes require a lot of knowledge and experience.
You might have seen me on various bugzilla reports, commenting/explaining issues, offering workarounds/fixes. See, I put considerable work into this: endless debugging sessions, writing analysis, offering solutions - frankly speaking: heart and soul.
That are several cases where only few people can actually judge the amount of work that is needed to solve specific problems. In fact if you see various patches/workarounds they might look easy at first glance but until you get there, many obstacles had to be overcome.
Granted, you might not understand the specific problems/explanations/issues regarding the bugs at all. That's ok because they are usually aimed at developers or for my own documenting purposes. On several occurrances, I even need to defend my findings/conclusions a second, a third time, putting additional hours into because the problem/fix might not be that obvious at all (hard to verify).
I wrote this analysis after the usual 10 hour work day and additional hours devoted to various projects of my interest. You frankly dismissed my writeup with "No, XP config doesn't work" and "Is this patch useful at all?" after putting the usual heart and soul into this ... I felt attacked, my work degraded.
I've experienced this several times, users make the *same* obvious errors again and again, working an tainted ~/.wine, not specifying combination of native overrides (guesswork), using old wine version and so on. Do you actually can imagine how much additional time I waste sometimes to verify my work over and over again because of such "false positive" reports? This time is lost for no good.
But even then I try to act polite, pointing out the obvious errors (see that .NET 2.0 bug, where the user actually admitted his fault, congratulating the wine people). I can understand people like Vitaly Margolen who was constantly working in this area of conflict, overreacting sometimes.
You seem to be a regular user contributor with a certain level of experience on how to file bug reports, testing bugs/patches with new releases, giving feedback. I don't expect you to understand the problem at all but I expect some level of professionalism which follows the *basic* wine guidelines.
If you actually felt attacked I apologize. Though I don't really see any abusive tone when re-reading my post, maybe I should explicitly add "irony" tags next time. But again: the joy of solving riddles is actually one of the main reasons I stayed here for some time. Don't make the joy go away...
Regards
http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #6 from Yolande Haneder yolande@haneder.biz 2008-03-16 08:29:31 --- I have in return to apologize to close the issue:
I am not a programmer. I do not know anything about software engineering. I am the daughter of a programmer (now retired), married to a Java developper, able to code in c/C++ and always sending sharp comments about my questions here.
I am learning bits and pieces all through my childhood and now, with just listening to conversations about programming, never learnt about the whole and how things belong together.
Wine is doing a great work. Although my software does not work on Wine because of the directory check, It is showing some nice signs of life on crossover.
Please don't be upset about me. You will currently not be able to replicate it on wine but believe me, if I ask a question it's not to upset anybody. I am just touching water. To replicate and for some advance functions of the .NET you have to remove the directory check because important installation files are otherwise not going to Z:/tmp
The issue is on XP using regasm. To reach it you have to get the .NET working on XP, some software can do it.
I wish you luck in the future.
http://bugs.winehq.org/show_bug.cgi?id=12018
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|download |patch
--- Comment #7 from Austin English austinenglish@gmail.com 2008-12-18 10:01:16 --- Do you still have a copy Dan? Seems only SPSS 17 is available on the website now...
http://bugs.winehq.org/show_bug.cgi?id=12018
--- Comment #8 from Anastasius Focht focht@gmx.net 2008-12-18 13:20:48 --- Hello,
--- quote --- Do you still have a copy Dan? Seems only SPSS 17 is available on the website now... --- quote ---
I also have v16 demo copy lying around. For every unfinished/unresolved bug I tend to keep the installers.
--- snip --- $ ls -lsa
202776 -rwxrwxr-x 1 focht focht 207429816 2008-03-13 20:25 SPSS16.0.1EvalVersion_a.exe
$ sha1sum SPSS16.0.1EvalVersion_a.exe afb23e1abfac44c28b4fb5163d519cb4fc244e99 SPSS16.0.1EvalVersion_a.exe --- snip ---
Currently it won't install anyway due to bug 15887 (mark as depends on).
The original problem should be gone because Wine has winver XP by default for quite some time now. My comment/patch regarding winver < XP and SxS assemblies still applies - which was the original reason for the bug.
Regards
http://bugs.winehq.org/show_bug.cgi?id=12018
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |15887
http://bugs.winehq.org/show_bug.cgi?id=12018
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|CVS/GIT |unspecified
--- Comment #9 from Austin English austinenglish@gmail.com 2009-01-19 15:14:25 --- Removing deprecated CVS/GIT version tag. Please retest in current git. If the bug is still present in today's wine, but was not present in some earlier version of wine, please update version field to earliest known version of wine that had the bug. Thanks!
http://bugs.winehq.org/show_bug.cgi?id=12018
Bug 12018 depends on bug 15887, which changed state.
Bug 15887 Summary: msi_cabextract FDICopy fails: Unable to Install Word Perfect Office http://bugs.winehq.org/show_bug.cgi?id=15887
What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE
http://bugs.winehq.org/show_bug.cgi?id=12018
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|patch |download Status|NEW |RESOLVED Version|unspecified |0.9.58. Resolution| |FIXED
--- Comment #10 from Anastasius Focht focht@gmx.net 2011-04-28 07:27:26 CDT --- Hello,
installer works if you don't set winver < WinXP (then my analysis from comment #1 still applies) You also need winetricks vcrun2005 for atl80.dll.
$ wine --version wine-1.3.18-233-gcff8753
Setting version to first reported date.
Regards
http://bugs.winehq.org/show_bug.cgi?id=12018
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org 2011-04-29 13:16:03 CDT --- Closing bugs fixed in 1.3.19.
http://bugs.winehq.org/show_bug.cgi?id=12018
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86 OS|other |Linux