While putting together a tutorial on how to contribute test cases to Wine (http://kegel.com/wine/sweng/), I noticed that the current version 9 of WinZip doesn't install under vanilla Wine; it aborts with the message WinZip was unable to locate a recent version of the Windows HTML help viewer, which is required to display WinZip help. ...
Seems like a bit of a showstopper. What's the plan for addressing this? Is it a 0.9 feature? - Dan
On Sun, 07 Nov 2004 05:12:38 -0800, Dan Kegel wrote:
Seems like a bit of a showstopper.
No more than any other missing feature is. WinZip isn't special.
What's the plan for addressing this? Is it a 0.9 feature?
Somebody needs to implement HTML help :) We have actually started on this, there is itss.dll which is partly (fully?) implemented and hhctrl.ocx but that's just stubs. It's not much use without an HTML control, Mike has done some good work on this lately with making it auto-download the control if it's not present.
So it's being worked on slowly. It definitely should not block 0.9, we already have way too much stuff piled onto that release.
thanks -mike
On Sunday 7 November 2004 14:12, Dan Kegel wrote:
While putting together a tutorial on how to contribute test cases to Wine (http://kegel.com/wine/sweng/), I noticed that the current version 9 of WinZip doesn't install under vanilla Wine; it aborts with
I noticed that the WinZip installer actually fails because it can't retrieve version information from hhctrl.ocx. This patch adds version information and voila, WinZip installs. You still can't use HTML help though unless you install Internet Explorer or use a native hhctrl.ocx + Mozilla ActiveX control.
-Hans
Changelog: Add version information.
Hans Leidekker wrote:
On Sunday 7 November 2004 14:12, Dan Kegel wrote:
While putting together a tutorial on how to contribute test cases to Wine (http://kegel.com/wine/sweng/), I noticed that the current version 9 of WinZip doesn't install under vanilla Wine; it aborts with
I noticed that the WinZip installer actually fails because it can't retrieve version information from hhctrl.ocx. This patch adds version information and voila, WinZip installs. You still can't use HTML help though unless you install Internet Explorer or use a native hhctrl.ocx
- Mozilla ActiveX control.
Hey, that fixed that problem! Can you submit that patch to wine-patches, or is it not ready?
But winzip 9 still doesn't install, at least with default settings; now the wrong value for default destination comes up in the installation dialog box, "%SystemDrive%\Program Files\WinZip". Seems like some environment variable isn't being expanded somewhere?
And even if you put in C: instead of %SystemDrive%, installation goes a little further, but fails with "WinZip internal error in file install.c line 930". Here's the log it created:
--------------- WinZip Error Report Log
To help solve this problem, please send this file by e-mail to support@winzip.com.
Please include as detailed as possible a description of what you were doing before the problem occurred, so we can try to reproduce the problem here. In particular, please tell us what steps led to the problem, and whether it occurs always or sometimes after these steps are followed.
Thank you
WinZip internal error in file install.c line 930
about: 004046a5 output_context_info: 0041ee08
WZDLL: unzip(): 20032100 IBSDLL: IBSIsDownload(): 00000000 Return address = 004203d5 Return address = 004473c0 Return address = 00480865 Return address = 004811cd Return address = 0048121d Return address = 004a8362 Return address = 4037dd85 Return address = 4001c59d
Windows 98 4.10 build 2222 A Current date/time: 11/7/2004 3:52 PM WinZip(R) 9.0 SR-1 (6224) compiled: Aug 11 2004 Module name = C:\Program Files\WinZip\WINZIP32.EXE Command line: "C:\Program Files\WinZip\WINZIP32.EXE" /installS /f:"Z:\home\dank\demo\build\winzip90.exe" User Interface Selected: Classic Memory in use = 28% Total physical memory = 416268 Kbytes Physical memory available = 204360 Kbytes Total virtual memory = 2097087 Kbytes Virtual memory available = 2097023 Kbytes Country code: 1 Language: English Code-page: 1252 Font: ---------------
- Dan
Dan Kegel wrote:
And even if you put in C: instead of %SystemDrive%, installation goes a little further, but fails with "WinZip internal error in file install.c line 930". ...
Hrm. Even WinZip 8.1 is failing now in the same way, even after I blow away ~/.wine. Here's part of the output of WINEDEBUG="+shell,+process,+dialog" ./wine 'C:\WinZip\winzip32.exe' with WinZip 8.1. Notice the suspicious-looking line: SHGetFileInfoW (L"10 10 10 10.10 10 10 10", ... The dialog call is for the error box.
This error persists even after installation; you get it every time you run the app. - Dan
trace:shell:SHGetFolderPathW returning 0x80070002 (final path is L"c:\windows\profiles\dank\My Documents") trace:shell:SHGetFolderLocation -- (new pidl (nil)) trace:shell:SHAlloc 42 bytes at 0x402508b8 trace:shell:SHAlloc 16 bytes at 0x4024ab68 trace:shell:SHFree 0x402508b8 trace:shell:SHFree 0x4024ab68 trace:shell:SHGetFileInfoW (L"C:\" fattr=0x80 sfi=0x4072f68c(attr=0x4086716c) size=0x2b4 flags=0x4115) trace:shell:PathIsRelativeW (L"C:\") fixme:shell:SHGetFileInfoW set icon to shell size, stub trace:shell:PathFindExtensionW (L"C:\") trace:shell:HCR_MapTypeToValueW L"" 0x400cffae trace:shell:SHGetFileInfoW icon=0x120e index=0x00000000 attr=0x4086716c name=L"" type=L"" ret=0x4023ad98 fixme:listview:LISTVIEW_SetColumnOrderArray iCount 9 lpiArray 0x4072f92c trace:shell:SHGetSettings (0x4072f948 0x00000480) trace:shell:SHGetSettings -- 0x0000 trace:shell:SHGetFileInfoW (L"10 10 10 10.10 10 10 10" fattr=0x0 sfi=0x4072f3b0(attr=0x4072f3e4) size=0x2b4 flags=0x4010) trace:shell:PathIsRelativeW (L"10 10 10 10.10 10 10 10") trace:shell:PathCombineW (0x4072ef68,L"Z:\home\dank\demo\build",L"10 10 10 10.10 10 10 10") trace:shell:PathIsRelativeW (L"10 10 10 10.10 10 10 10") trace:shell:PathAddBackslashW (L"Z:\home\dank\demo\build") trace:shell:PathCanonicalizeW (0x4072ef68,L"Z:\home\dank\demo\build\10 10 10 10.10 10 10 10") trace:shell:PathFindExtensionW (L"Z:\home\dank\demo\build\10 10 10 10.10 10 10 10") trace:shell:HCR_MapTypeToValueW L"" 0x400cfd51 trace:shell:SHGetFileInfoW icon=0x40254618 index=0x00000000 attr=0x4072f3e4 name=L"" type=L"" ret=0x4023b5f0 trace:dialog:DIALOG_GetCharSize dlg base units: 8 x 16 trace:dialog:GetDialogBaseUnits base units = 8,16 trace:dialog:DIALOG_ParseTemplate32 DIALOGEX 0, 0, 250, 97, 0 trace:dialog:DIALOG_ParseTemplate32 STYLE 0x80c800c0 trace:dialog:DIALOG_ParseTemplate32 EXSTYLE 0x00000000 trace:dialog:DIALOG_ParseTemplate32 CAPTION L"WinZip" trace:dialog:DIALOG_ParseTemplate32 FONT 8, L"MS Shell Dlg", 0, FALSE trace:dialog:DIALOG_GetCharSize dlg base units: 7 x 14 trace:dialog:DIALOG_CreateIndirect units = 7,14 trace:dialog:DIALOG_CreateControls32 BEGIN trace:dialog:DIALOG_GetControl32 L"Static" L"" 4541, 6, 6, 238, 16, 50020000, 00000000, 00000000 trace:dialog:DIALOG_GetControl32 L"Static" L"" 4542, 6, 25, 238, 8, 50020000, 00000000, 00000000 trace:dialog:DIALOG_GetControl32 L"Static" L"If this is a recurring problem and you would like WinZip to create a log file with details about the error so that you can report this problem to the developers, you can do so now." -1, 7, 43, 232, 27, 50020000, 00000000, 00000000
Dan Kegel wrote:
But winzip 9 still doesn't install, at least with default settings; now the wrong value for default destination comes up in the installation dialog box, "%SystemDrive%\Program Files\WinZip". Seems like some environment variable isn't being expanded somewhere?
Check the registry, does this string appear in it somewhere? If so we probably need to set the key to type EXPANDSZ or whatever it's called ...
On Monday 8 November 2004 11:59, Mike Hearn wrote:
But winzip 9 still doesn't install, at least with default settings; now the wrong value for default destination comes up in the installation dialog box, "%SystemDrive%\Program Files\WinZip". Seems like some environment variable isn't being expanded somewhere?
What version of Wine are you using? It installs fine for me on CVS from yesterday. I have grown into a habit of doing:
$ rm -rf ~/.wine && wine <program.exe>
because the rate of change in Wine is so high that you can expect the registry (and the rest of .wine) to be out of sync with Wine's code within a couple of days.
Check the registry, does this string appear in it somewhere? If so we probably need to set the key to type EXPANDSZ or whatever it's called ...
I recall that there were some changes related to these environment variables recently. My guess is that Dan's .wine is from before those changes.
-Hans
Hans Leidekker wrote:
What version of Wine are you using? It installs fine for me on CVS from yesterday. I have grown into a habit of doing:
$ rm -rf ~/.wine && wine <program.exe>
because the rate of change in Wine is so high that you can expect the registry (and the rest of .wine) to be out of sync with Wine's code within a couple of days.
Yeah. All the more reason to get .wine versioning figured out soon.
thanks -mike
Hans Leidekker wrote:
But winzip 9 still doesn't install, at least with default settings; now the wrong value for default destination comes up in the installation dialog box, "%SystemDrive%\Program Files\WinZip". Seems like some environment variable isn't being expanded somewhere?
What version of Wine are you using? It installs fine for me on CVS from yesterday. I have grown into a habit of doing:
$ rm -rf ~/.wine && wine <program.exe>
I figured it out, finally. I had been doing an out-of-tree wine build, where you make a directory next to the wine sources, and do ../wine/configure make depend && make This works great and keeps your source tree pristine. You can even run out of the build directory without installing, which is handy when developing.
However, if you run without installing, when the wine executable notices you have no .wine directory, and creates one using wineprefixcreate, it can't quite handle the out-of-tree build. I get the error cp: cannot stat `/home/dank/demo/build/tools/wine.inf': No such file or directory This caused all sorts of things to be missing in the registry, which explains lots of the problems I had.
The workaround is to copy wine/tools/wine.inf to build/tools, then run wine for the first time (or blow away ~/.wine and run wine). - Dan
-
Dan Kegel -
Hans Leidekker -
Mike Hearn