Hi, I think it's not easy to find conflicted dll files, but providing mini-dump file could be easy way to give useful resource to debug this problem.
Steps to provide mini-dump file: 1. Download Process Explorer. It's only 1.2 MB archived file. Unzip and execute procexp.exe. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx 2. Run QGIS 2.2 64-bit 3. After the R6034 error message is displayed (do not click OK button), select qgis-bin.exe in the tree of Process Explorer, right-click it and click "Create Minidump..." in the context menu. Then specify output file path in the file dialog. 4. Share the written qgis-bin.dmp file. It may be large (around 16MB), so it's better to zip it and use storage service (e.g. Google Drive, DropBox, etc). Attached image is for visual. Regards, Minoru howtodump.png<https://docs.google.com/file/d/0B-D5Y8MiZKrnd1hsVTA2c2Jodk1WQ3VtOWRDa0xLRVdzVHRB/edit?usp=drive_web> 2014-02-27 21:59 GMT+09:00 Tijan49 <[email protected]>: > Hello Jurgen, > Sorry for my ignorance, but how can I verify that no DLLs in system32 are > in conflict with Dlls shipped with qgis ; > Thank you > Jean > > Le 27/02/2014 09:02, Jürgen E. Fischer a écrit : > > Hi, >> >> On Thu, 27. Feb 2014 at 06:32:18 +0000, Lester Anderson wrote: >> >>> Think the next step is to test whether the 32-bit version exhibits this >>> issue or not. Never had this problem with v1.8. >>> >> >> >>> Still get the same issue if you go through OSgeo4W method. As I say, need >>> to verify if it is just the 64 bit version or both! >>> >> And verify that you don't have any DLLs in system32 that conflict with >> DLLs shipped whit QGIS. >> >> >> Jürgen >> >> > > _______________________________________________ > Qgis-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-user >
_______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
