dvi/yap/ps

Gena Hahn <[email protected]>
Newsgroups gmane.comp.tex.miktex
Message-ID <[email protected]>
I have a strange problem. I like to compile to dvi (it is MUCH smaller 
and MUCH faster to look at than pdf). So I like to look at the results. 
I have been running MikTex 2,9 on my Win7/32 Dell (single-core intel) 
laptop for a few years and have ben able to do what I wanted. I ran 
under Linux in my office. Then I had to change to Windows (University 
de-facto standard and related committees, sigh) and had MikTex 2.9 
installed (at least the technicians did it). Then the problems started - 
most of my dvi files, perfectly fine on the Dell, posted "could not 
render postcript..". I complained, the technicians still do not know, 
after 2 years.
Now the Dell is approaching the end of its life and so I have a Win7/64 
HP (quad core i5) and am installing things on in. MikTex 2.9, for 
example. Lo and behold - the same problem appears, I cannot see my dvi 
files.
I have got it down to one possible problem: \usepackage{hyperref}
When active, dvi will not show. When stopped (%\use...), the file will 
not compile IF hyperreference is used in the text. But if the same 
preamble is used on a file where hyperreference does not appear in the 
text, it compiles and I can see the dvi.

Do you have an idea of to fix the problem? That is, keep the package AND 
compilation AND dvi viewability?

Thanks
gena
p.s
yap on 32 bit dell is dated 1-12-2010,
on the 64 bit HP it is 30-7-2011

Could a part of the problem be that on the 64bit machines the files are 
not in bin but bin\x64?


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.