MiKTeX and proTeXt ⇒ pdflatex: No .pdf produced

[leo_ch]

Dear all,

Everything was going ok while writing my document. All the sudden, the figures are not found since I think it wants .eps and not .jpeg,etc...

I can see from line 92 in the .log file that the "driver file" is now dvips...

I'm enclosing my .log file and I would be very happy if someone could give me a hand...

Thanks

[localghost]

[…] Everything was going ok while writing my document. All the sudden, the figures are not found since I think it wants .eps and not .jpeg,etc […]

Nothing happens without your assistance. It's a fact that you compiled with LaTeX and not with PDFLaTeX.

[…] I can see from line 92 in the .log file that the "driver file" is now dvips […]

Somewhere in your code there is the »dvips« driver chosen. Browse your packages in the preamble and delete this driver option. The log file indicates that this option might be given for the xcolor package. Other typical packages would be geometry, graphicx or hyperref.


Thorsten

[leo_ch]

Dear localghost,

Thank you for your interest in my problem.

Regarding the first possible mistake, I am compiling with pdflatex (C:\Program Files\MiKTeX 2.9\miktex\bin\pdflatex.exe) and not with latex.

Code: Select all

\documentclass[a4paper,12pt]{report}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\usepackage{lmodern}
%\usepackage{xcolor}
\usepackage{eurosym}
\usepackage{graphicx}%[pdftex]
\usepackage{subfigure}
\usepackage{fancyhdr}
\usepackage{nomencl}%\usepackage{inputenc}
\usepackage{geometry}%[a4paper, margin= 3cm]

\usepackage{url}
\usepackage{wrapfig}
\usepackage{booktabs}
\usepackage{setspace}   
\usepackage{amssymb,amsfonts}                         
%,sanitize={name=false,description=false,symbol=true}

\usepackage{listings}
\usepackage[acronym,nonumberlist=true]{glossaries}
\usepackage{textcomp}
\usepackage{bigints}

\usepackage{color}
\usepackage{verbatim}
%\usepackage[colorlinks]{hyperref}

\definecolor{light-gray}{gray}{0.975}

I cannot see where my mistake might be...

[localghost]

[…] Regarding the first possible mistake, I am compiling with pdflatex (C:\Program Files\MiKTeX 2.9\miktex\bin\pdflatex.exe) and not with latex.[…]

The log file clearly says the other thing. These are the first and the last line of the log file you attached.

This is pdfTeX, Version 3.1415926-1.40.11 (MiKTeX 2.9) (preloaded format=latex 2011.6.21) 21 JUN 2011 16:40

[…]

Output written on Thesis.dvi (41 pages, 345604 bytes).

So everything indicates that you just didn't compile with PDFLaTeX. The included packages don't show a driver option. So this is the only possible cause for the problem. Well then?

[leo_ch]

I still get the same .log file

I have double checked that it is pdflatex in the arguments for the compiler :\

[localghost]

The settings are unimportant. Much more important is the build profile you have selected in the toolbar of the main window. Make sure that there is 'LaTeX => PDF' displayed in the menu as shown in the attachment.

[leo_ch]

Yep that is the chosen option...

Any ideas??

[localghost]

Open a command line window, move to the directory where your thesis is located, and try to compile from there and see what happens.

Code: Select all

pdflatex Thesis

If this works, there is definitely a problem with TeXnicCenter (TXC) on your machine. Then forget TXC and try another editor like TeXworks. It is integrated into MiKTeX 2.9 but probably has to be installed subsequently by the MiKTeX Package Manager.

If this doesn't work either, there might be something wrong with the MiKTeX formats or settings. In this case a remote diagnose is not possible for me (Wind0ws is not my primary OS). So my advice ends here.

[leo_ch]

Dear localghost,

I have tried your suggestion and still it is doing format=latex

I am a bit desesperate since this is my master thesis lol

I will try to reinstall everything and see what happens... In texmaker the error persists.

Thank you very much for your help!!

[localghost]

[…] I will try to reinstall everything and see what happens... In texmaker the error persists. […]

Before you do so, you should try to fix it from the command line.

Code: Select all

initexmf --dump

or

Code: Select all

initexmf --admin --dump

It's less time consuming.