[posted and mailed] Soren O'Neill <[EMAIL PROTECTED]> wrote in news:[EMAIL PROTECTED]:
> Paul A. Rubin wrote: > >> Start LyX, open a document, either print it or try to export it to >> PS, then (without closing LyX or the document) check the temp >> directory LyX is using for that document. Is the DVI file there? If >> so, what's its name? If not, is there a .tex file there? > > I find a directory in /tmp called lyc_tmpdir****/lyx_tmpbuf0/ > Before printing its empty. After trying to print it contains: > > protocol_0.2.aux protocol_0.2.blg protocol_0.2.log > protocol_0.2.tex.dep protocol_0.2.bbl protocol_0.2.dvi > protocol_0.2.tex > > (my document is called protocol_0.2) > I can open up the DVI fine and it looks just fine... Ok, this seems to be narrowing the problem down somewhat. We know that latex is running successfully, and that the DVI file exists where it should. The problem apparently lies in the setup of the call to dvi2ps. > >> >> One other thing: does the log file indicate that latex.exe was able >> to process the source file ok? (If latex.exe didn't produce a DVI >> file, that would explain things.) > > Well it does seem to produce a DVI file alright, is it the path to my > printer which is set wrong ? > As mentioned in Lyx/Preferences/Printer, the Printer Command is set to > dvi2ps > > I have tried to change it to lp, lp0, lpr and hp1300n (my printer > name) - no success ... > I don't think it's the path to dvi2ps, because that appeared to run in an earlier test. In a previous post, you said you got the following error message while trying to print: >> dvi2ps: FATAL-- can't find DVI file "6499i.dvi" I interpret that to mean that dvi2ps was started by LyX (which in particular means that LyX was able to find dvi2ps), but that it was given an incorrect name for the DVI file (or else was not given the correct path to the DVI file). At this point, I probably should ask what operating system you're using. The next two things I suggest are: 1. In Edit | Preferences | Converters, make sure DVI->Postscript is set to dvi2ps -o $$o $$i. Then repeat the experiment you did above, check the temporary directory (as above) to verify that the DVI file was written, and see if the Postscript file was written there. Report back any error message you get. I know you tried exporting once before, but I'm not sure it was the same file. Use protocol_0.2 again, so that we know the document itself is not the source of any problems. 2. If dvi2ps issues an I-can't-find-the-DVI-file error message again, then I suggest writing a script that will just echo its arguments to the screen, making that your converter, and repeating the experiment. That will tell us what path and file name LyX is giving to dvi2ps. -- Paul
