I am going insane on this.
I want to open an EPS file using Gimp 2.8.2 installed on a Windows 7 32-bit system (I think the PC itself is 64-bit but for some reason we have 32-bit Windows installed).
I first tried using the instructions on the Gimp site. Installed Ghostscript, created the path variable, all nothing doing. Totally useless Gimp message saying "Unable to open the file" (I knew that already).
Hunted all over the Internet and finally came across this Bugzilla report. Comment 48 suggested that I should just be able to install 2.8.14 with Postscript support and it should work out of the box.
So I uninstalled Gimp, checked the file had gone from the directory list, and installed the new version. Still can't open the EPS file, and it now crashes Gimp with a message just saying "Plugin crashed: "file-ps.exe".
Just to make sure the images are actually ok I went to my Ubuntu system and installed Gimp (2.8.10 this time), opened the eps file... and it works like a charm, no problem.
If anyone has a solution I would be deeply grateful
check out that post:
http://blog.tjitjing.com/index.php/2013/05/solution-error-open-eps-in-gimp-64-bit-with-ghostscript.html
Solution
If you have not already, download and install Ghostscript 64-bit
Copy gsdll64.dll from your Ghostscript bin folder (Eg: C:\Program
Files\gs\gs9.07\bin) to the GIMP bin folder (Eg: C:\Program
Files\GIMP 2\bin)
In the GIMP bin folder first a) Rename the file
libgs-8.dll to libgs-8.old, and then b) Rename gsdll64.dll to
libgs-8.dll
Restart GIMP and opening EPS images should now work
It worked fine for me with GIMP 2.8.14 and gs9.16 on windows 7 64 bit with a fresh install of GIMP from the Gimp web site.
Related
In the installation instructions for Windows at GoCV we've the below line:
Download and run the MinGW-W64 compiler installer from https://sourceforge.net/projects/mingw-w64/?source=typ_redirect.
I downloaded the mentioned file, but could not find executor file, and could not find anything like x86_64-7.3.0-posix-seh-rt_v5-rev2 as mentioned in the instuctions, any help?
The installation of MinGW-w64 is simple. Either download the installer from
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/mingw-w64-install.exe
or the appropriate package (as a 7-zip archive) directly:
https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/7.3.0/threads-posix/seh/x86_64-7.3.0-release-posix-seh-rt_v5-rev0.7z/download
Some people (including me) experienced random connection problems with the installer at some point, so the second options might be more straightforward.
I have a fresh win 10 installation with Delphi XE2.
I tried to install CnPack but there was no chance (It says couldn't find wizard):
Also registry is OK and the file is in there and the permissions are OK.
Its version is CnWizards_1.1.3.896 which is currently the latest version.
I have tried older versions as well but there was no chance.
Any idea ?
I had the same problem and I got it to resolve to do this.
I downloaded the Source file and the Installer file.
I used this version 1.1.3.896.
First I open the source in Delphi and Compile, Build and Install the following components.
CnPack_DXE2.dpk. (Compile and Build)
CnWizards_DXE2.dpr (Compile and Build)
dclCnPack_DXE2.dpk (Compile, Build and Install)
Execute the Installer file.
Now, this is the secret for me.
Replaced the files (CnWizards_DXE2.dll).
In the Third Step, it creates CnWizards_DXE2.dll (CnWizards\bin). Copy this file and paste in the local installation ([program files\CnPack\CnWizards]).
I created the mini tutorial in Portuguese for this situation, if necessary I can send it for you.
Sorry, my English is not good.
Bye for now
I can't install the nvidia installation in cuda toolkit. I don't have a nvidia card. Does that means I can't use emgu.cv? I been on this all yesterday and emgu.cv is still giving me problems.
Here the link that still shows my problem:
Exception initializing Emgu.CV
Actually you can. Run the installer. Then go to the directory where it has unzipped all the files and choose nvcuda.dl_ and using command prompt expand it into nvcuda.dll.
Place this dll in system32 folder.
This should solve the 'nvcuda.dll not found' error.
I need to use the traincascade and createsamples utilities.
I need to do this on many computers and do not want to have to build them myself as these computers do not have any development tools.
I have searched for instructions a lot, but they all say things like 'run the installer and install to Program Files' . Except that I don't see any installer. I have downloaded a 200MB exe OpenCV-2.4.0.exe, but on running it just extracts to some folder. That folder contains sources and cmake files, but I do not want to build myself. The library files are there, but no exe files (for traincascade and createsamples).
build a 64 bit version and a 32 bit version on the lowest os you can find(xp, vista or 7), then build your own installer.
I have a simple 3D application programmed in C++ and D3D9 using MSVC++ 2008 Express. Some weeks ago, I had to format my hard disk, so the DirectX SDK is not currently installed.
However, I found that the exe file that I found in my "Debug" folder for the project does not run. The error it gives is:
"This application has failed to start because d3dx9d_38.dll was not found. Re-installing the application may fix this problem."
Of course, it worked after I installed the SDK. Then I compiled a "release build" thinking that that was the solution. Then I uninstalled the SDK and tried to run the .exe file.
Still gave me the error.
So how does one make such .exe files run on machines without the SDK?
I think you cannot run the app without the SDK. See XBMC, which requires the SDK to run.
However, you could try simply placing the required dll file from your SDK in the same directory as the executable.
I followed the solution as stated here.
I copied the d3dx9_38.dll file into my Release folder. It still didn't work. However, I renamed the dll file to "d3dx9d_38.dll. Then it worked.
Wondering why I had to rename to the debug version of the file even though it was a RELEASE build...