[Bug 44445] 64-bit SIGMA Photo Pro 6 (.NET 4.0 app) crashes on startup

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Feb 9 21:50:09 CST 2018


https://bugs.winehq.org/show_bug.cgi?id=44445

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|SIGMA Photo Pro 6: Crashed  |64-bit SIGMA Photo Pro 6
                   |when trying to start        |(.NET 4.0 app) crashes on
                   |                            |startup
                 CC|                            |focht at gmx.net
           Keywords|                            |dotnet, win64
         Resolution|---                         |DUPLICATE
           Hardware|x86                         |x86-64
             Status|NEW                         |RESOLVED
          Component|-unknown                    |ntdll

--- Comment #4 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

you mangled multiple known problems for 64-bit together here.

First, the installer provides both - 32-bit and 64-bit variants of the app.
Which one gets installed depends if you are running the installer from a 32-bit
or 64-bit WINEPREFIX.

32-bit WINEPREFIX:

--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/SIGMA/SIGMA Photo Pro 6

$ file *.{dll,exe}
Common.dll:                 PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
CtmListView.dll:            PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
DownloadManager.dll:        PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
FileIOManager.dll:          PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
HuffmanDll.dll:             PE32 executable (DLL) (GUI) Intel 80386, for MS
Windows
ImageProcessingManager.dll: PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
MainProcess.dll:            PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
MemoryManager.dll:          PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
ParameterManager.dll:       PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
PreferenceManager.dll:      PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
SurfaceManager.dll:         PE32 executable (DLL) (GUI) Intel 80386, for MS
Windows
VersionCheckManager.dll:    PE32 executable (DLL) (console) Intel 80386
Mono/.Net assembly, for MS Windows
dotNetFx40_Full_setup.exe:  PE32 executable (GUI) Intel 80386, for MS Windows
FileConverter.exe:          PE32 executable (GUI) Intel 80386 Mono/.Net
assembly, for MS Windows
SIGMA_PhotoPro6.exe:        PE32 executable (GUI) Intel 80386 Mono/.Net
assembly, for MS Windows
uninst.exe:                 PE32 executable (GUI) Intel 80386, for MS Windows
--- snip ---

The app works fine in 32-bit WINEPREFIX but that's obviously not what the
initial bug report was about.

64-bit WINEPREFIX:

--- snip ---
$ pwd
/home/focht/wine64/drive_c/Program Files/SIGMA/SIGMA Photo Pro 6

$ file *.{dll,exe}
Common.dll:                 PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
CtmListView.dll:            PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
DownloadManager.dll:        PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
FileIOManager.dll:          PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
HuffmanDll.dll:             PE32+ executable (DLL) (GUI) x86-64, for MS Windows
ImageProcessingManager.dll: PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
MainProcess.dll:            PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
MemoryManager.dll:          PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
ParameterManager.dll:       PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
PreferenceManager.dll:      PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
SurfaceManager.dll:         PE32+ executable (DLL) (GUI) x86-64, for MS Windows
VersionCheckManager.dll:    PE32+ executable (DLL) (console) x86-64 Mono/.Net
assembly, for MS Windows
FileConverter.exe:          PE32+ executable (GUI) x86-64 Mono/.Net assembly,
for MS Windows
SIGMA_PhotoPro6.exe:        PE32+ executable (GUI) x86-64 Mono/.Net assembly,
for MS Windows
uninst.exe:                 PE32 executable (GUI) Intel 80386, for MS Windows
--- snip ---

The app crash in a 64-bit WINEPREFIX is expected since it's a pure 64-bit .NET
executable -> bug 38661 (NOTE: the Wine-Staging patchset doesn't apply anymore
as the loader sequence was reworked -> main exe entry point = incorrect).

--- quote ---
I tried to reproduce this in wine but after installing .NET 4.0, when i try to
install SPP wine keeps telling me that i need wine-mono but then SPP fails with
the same error as before.

When i install wine-mono first, .NET complains about .NET is already installed.
--- quote ---

Then you worked on a broken 32-bit WINEPREFIX or used incorrect steps. You
either use 'winetricks -q dotnet40' which takes care of everything or let the
app install .NET Framework 4.0 but you need to uninstall Wine-Mono prior. You
can't have both at the same time.

For a 64-bit WINEPREFIX you can't get a proper 64-bit .NET Framework 4.0
installation as of now - 'winetricks' doesn't support it.
'winetricks' will install a full 32-bit .NET Framework 4.0 and almost complete
64-bit Framework (broken). It's possible to repair that manually, providing a
working 64-bit Framework though. 

Anyway, marking this as dupe of bug 38661 since that's what the initial
backtrace is about.

$ sha1sum SPP_6.5.4_setup.exe 
9450782a4794a53e4bc2771f4fa049bc1be44252  SPP_6.5.4_setup.exe

$ du -sh SPP_6.5.4_setup.exe 
85M    SPP_6.5.4_setup.exe

$ wine --version
wine-3.1-193-g354fa7eb79

Regards

*** This bug has been marked as a duplicate of bug 38661 ***

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list