# Weird message on dvi mode [closed]

I am getting the following message when I visualize in dvi mode:

``````MiKTeX Problem Report
Message: Some PostScript specials could not be rendered.
Data: Error: /undefined in H.S
Operand stack:
Execution stack:
%interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1914   1   3   %oparray_pop   1913   1   3   %oparray_pop   1897   1   3   %oparray_pop   1787   1   3   %oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
--dict:1166/1684(ro)(G)--   --dict:0/20(G)--   --dict:80/200(L)--   --dict:95/300(L)--   --dict:17/200(L)--
Current allocation mode is local
MiKTeX GPL Ghostscript  9.00: Unrecoverable error, exit code 1

Source: Libraries\MiKTeX\Dvi\Ghostscript.cpp
Line: 372
MiKTeX: 2.9
OS: Microsoft Windows 8 Business Edition, 64-bit (build 9200)
Invokers: explorer/TeXnicCenter
PowerUser: no
Root0: C:\Users\acb\AppData\Roaming\MiKTeX\2.9
Root1: C:\Users\acb\AppData\Local\MiKTeX\2.9
Root2: C:\ProgramData\MiKTeX\2.9
Root3: C:\Program Files\MiKTeX
UserInstall: C:\Users\acb\AppData\Roaming\MiKTeX\2.9
UserConfig: C:\Users\acb\AppData\Roaming\MiKTeX\2.9
UserData: C:\Users\acb\AppData\Local\MiKTeX\2.9
CommonInstall: C:\Program Files\MiKTeX
CommonConfig: C:\ProgramData\MiKTeX\2.9
CommonData: C:\ProgramData\MiKTeX\2.9
``````

What does it mean?

-
That message is not produced by your `dvi` viewer, but by `ghostscript` which is invoked from the `dvi` viewer, presumably because your `dvi` contains PostScript specials. Try to convert your `dvi` using `dvips` and look at the result with `ghostview`. –  JLDiaz Jan 10 at 19:20
Welcome to TeX.sx! Usually, we don't put a greeting or a "thank you" in our posts. While this might seem strange at first, it is not a sign of lack of politeness, but rather part of our trying to keep everything very concise. Upvoting is the preferred way here to say "thank you" to users who helped you. –  egreg Jan 10 at 19:21

## closed as too localized by Speravir, Marco Daniel, Thorsten, Paul Gaborit, Martin SchröderFeb 18 at 7:23

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Not everything that you might want to do in print (or can do with some particular target format) can be expressed directly in TeX' own DVI language, so there is a \special mechanism to pass commands directly to the backend. Some of the drivers make heroic efforts to emulate the others, but (as you see) not always with success.

In this case, it looks like you used some command that should only be used for pdflatex. Have you tried pdflatex directly, not latex --> DVI --> PDF?

-
I guess your last sentence should read like “Try out the direct production of PDF, i.e. call the profile LaTeX --> PDF.” –  Speravir Feb 18 at 2:39
@Speravir, yes, that was the intent. –  vonbrand Feb 18 at 3:30
In YAP, the DVI viewer, in menu `View` go to `Render method` and select `dvips`. This way the PostScript specials in the DVI will be correctly interpreted.