problem installing Therm 5.2 and cc32inst.exe

[djh]

I'm trying to install Therm 5.2 from http://windows.lbl.gov/software/therm/therm.html but I see:

Code: Select all

$ wine THERM52Setup.exe
fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls"
xcb_io.c:452: _XRead: Assertion `dpy->xcb->reply_data != 0' failed.
wine: Assertion failed at address 0xffffe410 (thread 0009), starting debugger...

I googled and found hints that I need to use wine-tricks but when I tried, I see:

Code: Select all

$ winetricks cc580
Executing sha1sum --status -c /home/dhoworth/winetrickscache/cc32inst.exe.sha1sum
Executing wine /home/dhoworth/winetrickscache/cc32inst.exe /T:c:\winetrickstmp /c
kscache/cc32inst.exe: xcb_io.c:452: _XRead: Assertion `dpy->xcb->reply_data != 0' failed.
wine: Assertion failed at address 0xffffe410 (thread 000b), starting debugger...
...
Executing wine /home/dhoworth/.wine/drive_c/winetrickstmp/comctl32.exe
wine: cannot find '/home/dhoworth/.wine/drive_c/winetrickstmp/comctl32.exe'
Note: command 'wine /home/dhoworth/.wine/drive_c/winetrickstmp/comctl32.exe' returned status 2.  Aborting.

I've used wine before for various things and it has just worked I just installed it on this Suse 10.3 machine using YaST and it says it is wine-0.9.44. I can provide the full debugger log if wanted but I suspect this is something obvious that I'm just not seeing I should probably mention that I'm using ssh to access the machine.

Thanks, Dave

[dimesio]

I've used wine before for various things and it has just worked I just installed it on this Suse 10.3 machine using YaST and it says it is wine-0.9.44.

That version is ancient. Upgrade to the latest development release.

[djh]

That version is ancient. Upgrade to the latest development release.

I know it's old but that's the version that comes with the distro on that machine. I prefer to run the distro version because then I get the security updates. If I do have to upgrade, I prefer stable versions rather than bleeding edge versions and FAQ 2.1 also suggests using the latest stable version.

So are you saying that this is a known bug that is not fixed in the stable release but is in the development release? Or is it a totally unknown bug that needs investigation? Or are you just saying the equivalent of the windows support person "have you rebooted the machine?"

Thanks, Dave

[Frédéric Delanoy]

On Fri, Aug 7, 2009 at 12:24 PM, djh<[email protected]> wrote:

dimesio wrote:

That version is ancient. Upgrade to the latest development release.

I know it's old but that's the version that comes with the distro on that machine. I prefer to run the distro version because then I get the security updates. If I do have to upgrade, I prefer stable versions rather than bleeding edge versions and FAQ 2.1 also suggests using the latest stable version.

So are you saying that this is a known bug that is not fixed in the stable release but is in the development release? Or is it a totally unknown bug that needs investigation? Or are you just saying the equivalent of the windows support person "have you rebooted the machine?"

Thanks, Dave

Well, the fact is this version is nearly 2 years old... and lots of
changes have happened in Wine since then...
It could be difficult for someone to know how this particular version
worked, what bugs it contained, ...
Hence, it's unlikely someone will pick that version and try to fix
your problem, since it might have been fixed already...

[vitamin]

I know it's old but that's the version that comes with the distro on that machine. I prefer to run the distro version because then I get the security updates.

Wine is not one of those applications. It's being released every 2 weeks and the only "stable" versions of it (wine-1.0.x) were guaranteed to run only few targeted apps.

Upgrade to the latest Wine version (wine-1.1.26) or at least (wine-1.1.25). Then try your app again.