[comp.text.tex] Is virmf preloaded

hsong@nvuxl.UUCP (g hugh song) (12/24/90)

Strange.  I created my "localsite.mf" instead of "U_Wash.mf".  Then
I checked ".../mf/inputs/cmmf.mf" and ".../mf/inputs/mf.mf.mf" for the line
saying "input localsite".  Then
I created ".../mf/bases/cmmf.base" and ".../mf/bases/mf.base".   Then
I hardlinked ".../bin/cmmf" to ".../bin/virmf"  

Now I expect to make fonts in 100dpi for my DECStation dpi spec.
Alas! Executing 

$ cmmf '\mode:=DecHundredDpi;\mag:=magstep\(0\); input cmr10'

did not find the newly created mode "DecHundredDpi".  So I did the following.

$ cmmf '\mode:=help;\mag:=magstep\(0\); input cmr10'

This did not recognize the new mode at all.   So what's wrong?  I even
repeated the above precedure without introducing
"DecHundredDpi" but with different dpi values (100dpi) for existing 
"mode_def sun" (this has originally 82dpi).

$ cmmf '\mode:=sun;\mag:=magstep\(0\); input cmr10'

gave cmr10.82gf instead of cmr10.100gf which is expected.  
Now I removed ".../mf/bases/cmmf.base", and executed 'cmmf" command.
Alas, it did not complain anything, started to create fonts for 
"mode_def proof"which is the default when virmf does not find the proper mode.

So what am I missing?

TeX gurus (Dirk, Ken, Tom, DHosek)! Please help me to figure out this puzzle.

My system env is Dec Station 5000/200 with cc 1.31, TeX3.0.
What's wrong?  Please check on your site.   All this happend while I 
was installing, guess what, SeeTeX by Dirk Grunwald.  His machine is 
Not reachable from my site.  So I could not ftp the preinstalled fonts.
Does anybody know the internet addres of "foobar.colorado.edu"?

Thanks a lot.

	-hsong-
	nvuxl!hsong@bellcore.bellcore.com

PS: On Csh command line, you need to type "nvuxl\!hsong@..."

ken@csis.dit.csiro.au (Ken Yap) (12/27/90)

>Strange.  I created my "localsite.mf" instead of "U_Wash.mf".  Then
>I checked ".../mf/inputs/cmmf.mf" and ".../mf/inputs/mf.mf.mf" for the line
>saying "input localsite".  Then
>I created ".../mf/bases/cmmf.base" and ".../mf/bases/mf.base".   Then
>I hardlinked ".../bin/cmmf" to ".../bin/virmf"  
>
>Now I expect to make fonts in 100dpi for my DECStation dpi spec.
>Alas! Executing 
>
>$ cmmf '\mode:=DecHundredDpi;\mag:=magstep\(0\); input cmr10'
>
>did not find the newly created mode "DecHundredDpi".  So I did the following.
>
>$ cmmf '\mode:=help;\mag:=magstep\(0\); input cmr10'
>
>This did not recognize the new mode at all.   So what's wrong?  I even
>repeated the above precedure without introducing
>"DecHundredDpi" but with different dpi values (100dpi) for existing 
>"mode_def sun" (this has originally 82dpi).
>
>$ cmmf '\mode:=sun;\mag:=magstep\(0\); input cmr10'
>
>gave cmr10.82gf instead of cmr10.100gf which is expected.  
>Now I removed ".../mf/bases/cmmf.base", and executed 'cmmf" command.
>Alas, it did not complain anything, started to create fonts for 
>"mode_def proof"which is the default when virmf does not find the proper mode.
>
>So what am I missing?

Sounds like you did the right things, but are you sure that MF is
looking in the right directory for the base file? In the last step,
since you removed your cmmf.base and MF still managed to continue, this
suggests that MF was reading the default cmmf.base living in some lib
directory.  If you examine the log file that MF leaves behind, you can
see the date of the base file in the banner, like this:

This is METAFONT, C Version 2.0 (base=cmmf 90.11.27)  27 DEC 1990 14:14
					   ^^^^^^^^

If the date is way back, then MF is not reading your base file but the
default one. See the man page about the MFBASES env var.