Hi all,
I have some problems with Miktex installed on Windows Vista Business SP1/32 bit. I use ghostscript, ghostview and texniccenter, when I compile a document with the following profiles: Latex=>DVI, Latex=>PDF everything works fine; the system crashes when I compile with profiles Latex=>PS and Latex=>PS=>PDF. The error is reported into a widow that states: "Dvi-to-Postscript converter has stopped working". What can I do? I need Latex=>PS=>PDF to include my images into the final PDF...
Thanks in advance,
Lucian
MiKTeX and proTeXt ⇒ Problems with Miktex under Vista
NEW: TikZ book now 40% off at Amazon.com for a short time.
- localghost
- Site Moderator
- Posts: 9202
- Joined: Fri Feb 02, 2007 12:06 pm
Problems with Miktex under Vista
It seems that dvips causes the problem, but I can't offer a direct solution. If you want PDF output, you may convert your graphics files to PDF and include them as usual. If the origin of the files is JPG or PNG, keep them. They will be accepted when compiling directly to PDF. Perhaps you can tell us more about these files (creation, format, processing, ...).
Best regards and welcome to the board
Thorsten¹
Best regards and welcome to the board
Thorsten¹
How to make a "Minimal Example"
Board Rules
Avoidable Mistakes
¹ System: TeX Live 2025 (vanilla), TeXworks 0.6.10
Board Rules
Avoidable Mistakes
¹ System: TeX Live 2025 (vanilla), TeXworks 0.6.10
Re: Problems with Miktex under Vista
Hi Thorsten,
thanks for reply. Actually, teh document I have is almost empty - it does not contain any image, but the structur (chapter) of the document. Usually I convert all images to eps with Gimp and I include them in LaTeX. It worked under Windows XP; however, the process fails (indeed, it seems to be dvips' fault).
Lucian
thanks for reply. Actually, teh document I have is almost empty - it does not contain any image, but the structur (chapter) of the document. Usually I convert all images to eps with Gimp and I include them in LaTeX. It worked under Windows XP; however, the process fails (indeed, it seems to be dvips' fault).
Lucian