MiKTeX and proTeXt ⇒ Epstopdf error: file not converted

[kaisquared]

Hello,

I'm having some troubles using the epstopdf package (or the epspdfconversion package). I need to include eps figures exported from Matlab into a beamer presentation, and so I wanted to use epstopdf in order to automate the conversion.

However, I get an error and the log file displays the following message:

Code: Select all

system(epstopdf [file_path]/[file_name].eps)...disabled.

! Package graphics Error: File `[file_path]/[file_name].pdf' not found.

See the graphics package documentation for explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.410 \end{frame}

Using draft setting for this image.

Apparently, the execution of epstopdf is disabled for some reason, which explains why the pdf output file cannot be found. Do you have any idea why?

I could manually convert the eps files without any trouble, via the command line or with a drag and drop (I'm using Vista), so the executable is not at fault. Is it a security mechanism activated by default?

Many thanks!

[kaisquared]

It seems to be linked to write18, which allows TeX to call external programs during the compilation. Could you tell me more about that?

I use TeXnicCenter, and my parameters for the "command line arguments to pass to the compiler" are:

Code: Select all

--enable-write18 --shell-escape -interaction=nonstopmode "%pm"

But I get a message in the log file telling me the application couldn't launch because the side-by-side configuration is incorrect (possibly wrong translation, the message is in French – this probably means the error has something to do with windows, not the compiler itself). What is wrong with my method?

[localghost]

When using MiKTeX, you only need the switch --enable-write18 to get external programs executed. If this alone doesn't help, provide a minimal working example (MWE) and attach a sample file if necessary.


Best regards
Thorsten¹

[kaisquared]

Thanks Thorsten.

I fiddled around with it a bit and now it works. I don't know what exactly changed (I seem to remember trying --enable-write18 only), but now it does. Great!