Re: [MiKTeX] Error in common of YAP and ps2pdf: MiKTeX and XP(sp2) hiccup?

[Hans M. E. <hei...@on...>]

> -----Original Message-----
> From: mik...@li...=20
> [mailto:mik...@li...] On Behalf=20
> Of Alan Ristow
> Sent: Tuesday, August 07, 2007 11:48 PM
> To: A place for MiKTeX users to discuss MiKTeX related questions.
> Subject: Re: [MiKTeX] Error in common of YAP and ps2pdf:=20
> MiKTeX and XP(sp2) hiccup?
>=20
>=20
> Hans Marius Eikseth wrote:
<snip>
> > 3: Exceptional instance of successfully running ps2pdf, is when I
> > a) Open DOS console window
> > b) change directory to C:\Program Files\MiKTeX 2.6\miktex\bin
> > c) issue: ps2pdf "%some path where I have access%myfile.ps" ["%some=20
> > path where I have access%myfile.pdf"]
> >=20
> > My incredible stumpedness stems from that issuing
> >=20
> > "C:\Program Files\MiKTeX 2.6\miktex\bin\ps2pdf" "%some path where I=20
> > have access%myfile.ps" ["%some path where I have access%myfile.pdf"]
>=20
> Perhaps you already tried this at some point -- I only=20
> vaguely remember=20
> the start of the thread -- but do you have "C:\Program Files\MiKTeX=20
> 2.6\miktex\bin" in your PATH environment variable (without=20
> the quotes)?=20
> If not, add it. Once it is in your PATH, you *should* be able=20
> to invoke=20
> ps2pdf by simply typing "ps2pdf" at the command prompt without=20
> specifying the complete path name. Once you know it's in your=20
> PATH, try=20
> the following:
>=20
> (1) Open a DOS console and type "ps2pdf" (without the complete path)=20
> then <return>. You should get a message about the usage of ps2pdf.
>=20
> (2) Navigate to a directory that contains a ps file you wish=20
> to convert,=20
> then type "ps2pdf <filename>.ps" at the command prompt. Does=20
> it convert=20
> the file to pdf?
>=20
> Alan

Thanks for trying, Alan.

Unfortunately, 'C:\Program Files\MiKTeX 2.6\miktex\bin' is listed first =
in
my PATH variable! I can use latex and dvips to my hearts content, =
without
specifying absolute paths, because of this PATH.

This is my exact problem: I need to navigate to this directory to invoke
ps2pdf (and get a hint on usage in absence of arguments). If I, from the =
DOS
console standing on 'C:\Program Files\MiKTeX 2.6\miktex\bin>' invoke =
ps2pdf,
everything is ok and I can manipulate a ps file on some complicated file
server path. If I issue a 'cd ..', followed by=20
 ps2pdf "mypath\myfile.ps"
the only thing happening is 'ps2pdf:no alternate file name' - not any =
hint
on usage or any such thing. As described in my last post, not even a=20
"C:\Program Files\MiKTeX 2.6\miktex\bin\ps2pdf" "mypath\myfile.ps"
will work, unless I stand exactly in C:\Program Files\MiKTeX =
2.6\miktex\bin
. This is what is so hard to swallow, because I don't then understand =
how I
can get my UltraEdit to invoke ps2pdf - and the infeasibility of a =
workflow
including a sequence of 1) start DOS command window 2)navigate to =
miktex/bin
3)invoke ps2pdf with full arguments : to me it seems horrifying. And so
unnecessary, given it is right there in my PATH to begin with. But I'm
starting to repeat myself, sorry ;)

Best regards,
Hans Marius Eikseth