|License:||Free to use|
|Votes:||Marked as obsolete|
|Latest Wine Version Tested:||1.9.20|
Maintainers: About Maintainership
Seemingly everything (opening, editing, exporting, applying lens optimization)
No visual glitches
What does not
Needs native msxml3 to install (use winetricks)
Needs running wine reg add "HKLM\\Software\\Canon\\DPP" to install.
What was not tested
Used dppw3.14.47-updater.exe (32 bit) in 32 bit Wine prefix.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||openSUSE Tumbleweed (rolling release)||Oct 17 2016||1.9.20||No, but has workaround||Yes||Gold||Karl Cheng|
|Show||Ubuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)||Mar 03 2015||1.7.34||Yes||Yes||Gold||beduzar|
|Current||Linux Mint 17.1 "Rebecca" x86-64||Dec 21 2014||1.7.32||Yes||Yes||Gold||Michael|
|Show||Arch Linux x86_64||Dec 11 2013||1.7.8||Yes||Yes||Gold||an anonymous user|
|Show||Arch Linux x86_64||Sep 06 2013||1.7.1||Yes||Yes||Gold||Lukas Jirkovsky|
|Bug #||Description||Status||Resolution||Other apps affected|
|16817||Digital Photo Professional: Cannot install version 3.5.1 of Canon's DPP||NEW||View|
HKLM/Software/Canon/DPPNext you must install msxml3 using winetricks:
wget http://winetricks.org/winetricks sh winetricks msxml3Now you should be able to install DPP using the updater we downloaded earlier. If there is some problem with the installer, such as a crash, a DPP_install.sh script can be used to install DPP manually.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by beduzar on Tuesday March 3rd 2015, 9:41
Without msxml6 the install freezes with the progress bars remaining at zero for ever.
32 bits. Windows 7 version selected.
If that can help...
by tadi47 on Monday January 26th 2015, 13:22
1. $ WINEARCH=win32 WINEPREFIX=~/.wine32 winecfg
2. $ WINEPREFIX=~/.wine32 wine regedit
3. Created the HKLM\Software\Canon\DPP registry key
4. $ WINEPREFIX=~/.wine32 winetricks msxml3
While trying to run dpp withe the following command:
$ WINEPREFIX=~/.wine32 wine ~/.wine32/drive_c/Program\ Files/Canon/Digital\ Photo\ Professional/DPPViewer.exe
I get this message:
err:module:load_builtin_dll failed to load .so lib for builtin L"mscms.dll": liblcms2.so.2: cannot open shared object file: No such file or directory
err:module:import_dll Loading library mscms.dll (which is needed by L"C:\\Program Files\\Canon\\Digital Photo Professional\\DPPViewer.exe") failed (error c000007a).
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\Canon\\Digital Photo Professional\\DPPViewer.exe" failed, status c0000135
Thanks for any help you can give.
by Lukas Jirkovsky on Wednesday February 11th 2015, 11:54
by tadi47 on Thursday February 12th 2015, 16:44
by claude on Saturday November 29th 2014, 9:45
- creation of the HKLM register key
- installation of msxml3
- run of the installer file under Wine (Wine DPP392FR.exe)
- the installer crashed at a certain point, but after creating the launcher on the desktop and copying a number of files in the Canon directory in c:\program files.
- copy the files from the Windows XP canon directory into the Wines corresponding directory.
All this has been previously mentioned... What is interesting however, is the performance evaluation. All those that used DPP know it is quite intensive on CPU when doing a batch conversion from CR2 to JPG. I prepared such a job consisting of 17 CR2 files:
- DPP running in same computer booted in Native Windows XP: completed the job in 65 seconds.
- DPP running under Wine, booted in Mint: 85 seconds (30% more time)
- DPP running in a Virtual Machine (VirtualBox 3.16, Win XP SP3), computer booted Linux, with maximum resources possible allocated to the VM: completed the job in 3 minutes 35 seconds... 2.5 times more than under Wine!
Conclusion: for such a CPU intensive program, there is a huge advantage in running it under Wine compared to a VM - it is worth the trouble of going through the Wine installation.
What came in more as a surprize is the performance penalty compared to when the computer is booted in XP - I was expecting it would run faster in Linux. Performance penalty probably caused by Wine overhead...