Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!munnari.oz.au!bruce!monu0.cc.monash.edu.au!monu1!rjl
From: rjl@monu1.cc.monash.oz (    r    lang)
Newsgroups: comp.text.tex
Subject: Re: problem w/dvips54 under msdos
Message-ID: <13016@monu1.cc.monash.oz>
Date: 6 May 91 00:47:43 GMT
References: <3742@intvax.UUCP>
Organization: Dept. Electrical & Computer Systems Engineering, Monash University
Lines: 41

In article <3742@intvax.UUCP>, drstrip@intvax.UUCP (David R. Strip) writes:
> I am trying to run dvips54 under ms-dos 3.30 (dvi files generated by
> sbtex34). I am using the version that is available already compiled on
> simtel20 in the postscript directory (dated Feb 21, I believe and apparently
> derived from the emtex distribution). 
The most recent version is dvips 5.47 - make sure that you have this.
The only known MS-DOS bug with dvips 5.47 is the maketexpk.bat file -
the mfjob file produced won't work because the base= line is misplaced.

> I have modified config.ps to point to
> the correct paths, and I am using a plain vanilla laserwriter, so I left
> resolution (-D) set to 300. When I run dvips on a simple file (one line of
> cmr10 text), and look at the font files it is searching for, the resolutions
> are bizarre. At first they were always .../10797/cmr10.pk.
From your supplied information, I can't tell why it is looking for
such large sizes.
If you sent me a copy of the output of the following, I may be
able to solve the puzzle:
  dvips -d-1  dvifilename

> Also, the supplied config.ps has an "L" parameter that is not documented in
> the dvips.tex file.
These are emTeX font libraries.  They are documented in the dvips.tex file,
but within a TeX conditional.  Find the line '\generictrue' in dvipsmac.tex
and change it to '%\generictrue'.

> 
> Another question: when dvips fires up, if you use the -d64 option, you can
> see that it is trying to open files with names like lj_something. Are these
> emtex font libraries that it is searching for?
Yes.

> Finally, at one point, dvips tried to open cmr10 at 0 pt. What is this?
> Is this another symptom of the same problem that caused the wierd
> resolutions?
No idea.  I need to see the dvips error output.

-- 
Russell Lang   Email: rjl@monu1.cc.monash.edu.au   Phone: (03) 565 3460
Department of Electrical and Computer Systems Engineering
Monash University, Australia