Am Wed, 01 Feb 2012 15:06:26 -0500 schrieb Bob Tennent:
> There's been a report at
> http://www.mail-archive.com/tex-music@.../ >
> that MikTeX invokes on-the-fly installation for a font-mapping file
> (musix.map) that has already been installed in a personal texmf tree.
> The installation scripting that involves musix.map is as follows:
> xcopy %MIKTEXDIR%\dvips\config\config.ps "%ROOT%"\dvips\config\
> echo copy config.ps to ROOT >> %LOG%
> xcopy %MUSIXTEXDIR%\dvips\musix.map "%ROOT%"\dvips\config\
> echo copy musix.map to ROOT (dvips) >> %LOG%
> echo p +musix.map >> "%ROOT%"\dvips\config\config.ps
> echo add line "f +musix.map" to config.ps file >> %LOG%
> The user is supposed to have added %ROOT% to the MikTeX-managed
> set of texmf trees and updated the FNDB.
> Is this caused by an installation-script bug or a MiKTeX bug?
1. Normally missing map-files doesn't trigger the on-the-fly
installation, but you added a reference to musix.map to a local
config.ps and this probably forces miktex/dvips to find the map.
2. It sometimes happens that miktex wants to install a file that
already exists in the system. Reasons can be:
a) the file is in the completly wrong place and so not in the search
b) The FNDB of the root has not been updated correctly (did you do
it in user AND admin mode??)
c) the file is in the search path but not in the place where miktex
expect it when looking at the on-the-fly database. Then it can
happen that miktex triggers the on-the-fly installation to early
(before having gone throught the complete search path).
In your case miktex is looking for the file in
but it has been installed
So my guess is the user ran again c).
I would at first move the map to
%ROOT%\fonts\map\dvips\musixtex\musix.map, update the FNDB's and
then try again.