> > Graham Norton wrote
> >
> >> A. The good news is that TexMozartp3.tex (see attached) did compile
> >> and generate the same output as in the manual (except for the bar
> >> numbers).
> >> For this to work, the input file and the directory musixtex MUST be
> >> at the same level in the parent directory. This is crucial.
> >
> > Not on my PC. TeXMozartp3.tex goes through just fine, straight out of
> > the box, without any musixtex directory at the same level as the
> > source. I believe all that is required is to have a properly set up
> > installation of TeX and MusiXTeX, with a path variable set to allow
> > execution of all the necessary binaries, and with musixtex.tex and all
> > the musixtex fonts in folders that TeX can find. In MiKTeX, the latter
> > is accomplished by placing the files in the designated user input
> > folder or a subfolders of that, and then "refreshing the filename
> > database."
> >
>
>
> I tried putting TexMozartp3.tex in Downloads, a complely different
> directory which does not contain any musixtex software. (I moved all my
> WIMA downloads elsewhere in a directory Documents/music).
>
> Then I double-clicked on it to bring up Texshop (downloaded from CTAN)
> and it compiled correctly in Tex . Perhaps it was just the initial run
> that needed them in the same position. No need to modify any path
> names or a database.
TeXshop should have something called a "Local Guide" (because LaTeX
recommends that all distributions have a document called that) which should
explain where to put custom packages like musixtex and how to refresh the
FNDB (texhash is probably the command you're looking for).
> >> C. I note that doc/musixdoc.tex (which I cannot latex)
> >
> > When I first tried to latex it (not tex; it's a LaTeX file), latex
> > complained that it couldn't find backgrnd.sty. So I grabbed that file
> > from the musixtex.zip and put it in my user tex input folder,
> > refreshed the filename database, and the file compiles just fine.
>
> No complaints about not being able to find backgrnd.sty ; it stops
> with
>
> !no room for a new count
(this message means TeX has run out of a particular kind of memory)
It sounds like your TeX distro is possibly not using e-TeX - very near the
top of the file, is there the line "entering extended mode". The first three
lines of the log should be roughly:
This is [pdf]TeX, Version 3.1415926[-1.40.9] ("the name of your
distribution")
**musixdoc
entering extended mode
Either that or it's possible that you're using a newer version of LaTeX
which has used slightly more memory and so pushed the documentation over the
limit.
> l 400 \newcount\nofMPsegements
>
> Unfortunately the log file is different and I cannot past the console
> errors.
> >
<snip>
> >
> >> D. Including
> >>
> >> \documentclass{article}
> >> \usepackage{musixtex}
> >>
> >> ....
> >>
> >> \end{document}
> >>
> >> around the example was a good suggestion. For this to work, my input
> >> Mozartp3.tex and the directory musixtex have to be in the same parent
> >> directory (i.e. at the same level).
> >>
> >> Unfortunately it still won't complete, complaining:
> >>
> >> !I can't find 'Mozartp3.aux,'
> >> \enddocument
Your sample is missing \begin{document} after \usepackage{musixtex}. All
LaTeX files get a .aux file on pass one, even though it may be empty.
David
_______________________________________________
[email protected] mailing list
If you want to unsubscribe or look at the archives, go to
http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
