> Date: Wed, 31 Mar 1999 10:41:18 -0400 (AST)
> From: Pantelis Andreou <[EMAIL PROTECTED]>
> The problem I have is that process of getting a postscript
> file is quite complex.
For me it's running dvips and telling it the name of dvi-file
maybe adding some options like -e0 or -tletter
> First mtx will run only if you are in the mtx directory, but at least your
> file can be at any other directory.
> Second pmx will run only if you are in the pmx directory and unless the
> pmx file is in the pmx directory the pmxb command will not work. Then,
> unless I move the file to where I keep musixflx.exe
> musixflx will not work. Of course I can move musixflx.exe into the pmx
> directory but that is a temporary solution.
Either put those directories which contain binaries like musixflx.exe,
pmxa.exe, pmxb.exe, mtx.exe into the path or copy these files to
a common directory for binaries like c:\sys, d:\bin, e:\tools, ...
In the same way it is advisable to put pmx.tex, musixlyr.tex, ...
either into the directory which contains all MusiXTeX specific
TeX-sources or to tell your TeX-system which directories should be
looked up for (additional) TeX-sources.
Having done this it should be easy to adapt a procedure which
does what you want like it has be published in this list not
long ago in a thread started by Andr� van Ryckgehem under the
misleading subject "newbie pmx". Find this thread in the
archive[*] using the new search engine (:-) and follow it.
> It would be prefered if one could run the whole process from any
> directory. Does anyone have a solution?
That's the common way this problem is solved for most applications:
tell them where it can find it's documents, binaries, fonts, ...
> I did see in the FAQ's of mtx that there a mtx.bat but will that work in
> WinNT?
Maybe you find the key to all this in the introductory literature of
WinNT or maybe DOS (under WinNT)?
-- Werner
[*] The archiv of the mailing list is pointed at by
http://www.gmd.de/Misc/Music/
