Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!dog.ee.lbl.gov!nosc!crash!simpact!cmkrnl!jeh
From: jeh@cmkrnl.uucp
Newsgroups: comp.text.tex
Subject: Re: dvi2tty on VMS
Message-ID: <1991May13.132552.14@cmkrnl.uucp>
Date: 13 May 91 20:25:52 GMT
References: <00948577.653EE440@BINAH.CC.BRANDEIS.EDU>
Organization: Kernel Mode Consulting, San Diego CA
Lines: 34

It sounds as if you've defined a DCL symbol for dvi2tty as a RUN command 
rather than a "foreign command".  eg, you did

	$ dvi2tty == "run ddcu:[dire]dvi2tty"

and then you tried to invoke the program with 

	$ dvi2tty file.dvi

which expands to

	$ run ddcu:[dire]dvi2tty file.dvi

which is not what you want, as RUN only wants one parameter.  

Instead, define the symbol like so:

	$ dvi2tty == "$ddcu:[dire]dvi2tty"

then 

	$ dvi2tty file[.dvi]

should work.

ddcu and dire should of course be replaced by the appropriate device and
directory specs.  Note, the foreign command mechanism defaults to SYS$SYSTEM,
so you need to specify the device and directory even if the image is in your
current default directory. 

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
Chair, VMS Internals Working Group, U.S. DECUS VAX Systems SIG 
Internet:  jeh@dcs.simpact.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,scubed,decwrl}!simpact!cmkrnl!jeh