Xref: utzoo comp.sys.ibm.pc:31479 comp.text:4368
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!newstop!texsun!letni!sneaky!merch!spudge!johnm
From: johnm@spudge.UUCP (John Munsch)
Newsgroups: comp.sys.ibm.pc,comp.text
Subject: Re: DOSTEX HELP! Please
Message-ID: <1916@spudge.UUCP>
Date: 12 Jul 89 17:31:43 GMT
References: <7685@cs.Buffalo.EDU>
Reply-To: johnm@spudge.UUCP (John Munsch)
Followup-To: comp.sys.ibm.pc
Organization: Friends of Guru Bob
Lines: 28

In article <7685@cs.Buffalo.EDU> ugleung@cs.Buffalo.EDU (Leung Lee) writes:
>
[ First problem deleted because I don't have an answer. ]
>
> And also, the dvieps printer driver does not work looking for certain
>fonts.  As far as I know the fonts are all there, perhaps it wants a
>different set, but no suffixes are reported so I wouldn't know which,
>I have pk and tfm fonts.

If the dvieps is based on the Beebe driver code (as so many drivers are) then
you could use the flag -d16 in order to get it to spit out the name of any
files that it fails to load.  That's what I had to do with my dvijep driver.

The flags are -d# where # is any of the following added together:
	1	(DVIJET only) print page bitmap in hex
	2	display page coordinates and metrics of each output char
		and print each character bitmap in hex
	4	(DVIJEP only) display updated page coordinate of each char
		after each call to fixpos()
	8	print file name and open mode of each successful file open
	16	print file name and open mode of each unsuccessful file open
	32	show discarded off-page text
	64	trace virtual font caching
	128	trace character setting (lots of output)

If it isn't based on the Beebe driver code then I'm sorry but I can't help.

John Munsch