After switching to a new MikTeX installation on a new computer, I am having a problem with an additional PFB font. The font used to work on the old computer, but I can't see why it doesn't work on the new computer.

I installed MikTeX 2.9 for x64.

1. I placed a map file astr1.map with the following text content

astr1 LAstrologyPi-One <astr1___.pfb

into a new subfolder "astrology" of C:\Program Files\MiKTeX 2.9\dvips

2. For specifying the font, I use the TeX command

\font\as=astr1

3. The file astr1___.pfb is in a new subfolder "astrology" of folder C:\Program Files\MiKTeX 2.9\fonts\type1

4. In C:\Program Files\MiKTeX 2.9\miktex\config, I appended at the end the following line:

Map astr1.map

5. In a command shell, I started updmap

6. After that, I started initexmf --admin -u

When starting TexWorks and processing the TeX command \font\as=astr1, the console logs:

Running miktex-makemf.exe...
miktex-makemf: The astr source file could not be found

Later on, the font cannot be used. I was able to process the same TeX document in an older release on an older machine, however.

Why does it log "astr not found" and not "astr1 not found"? Is there a (new) problem with trailing digits in font names?

Is my procedure correct so far (I want to install the font in the admin branch, not in the local branch of the file system)?

What is going wrong?

Can I inspect a list of all installed fonts that are available on my MikTeX installation?

-
 Welcome to TeX.sx! You don't have to sign with your name since it automatically appears in the lower right corner of your post. – Torbjørn T. Jan 7 '12 at 17:59 Since you have some responses below that seem to answer your question, please consider marking one of them as ‘Accepted’ by clicking on the tickmark below their vote count. This shows which answer helped you most, and it assigns reputation points to the author of the answer (and to you!). – Martin Schröder Jan 7 '12 at 22:24

map files should go into C:\Program Files\MiKTeX 2.9\fonts\map\dvips

-
 Thanks. I created C:\Program Files\MiKTeX 2.9\fonts\map\dvips\astrology\astr1.map and updated everything in admin mode. The result remained the same miktex-makemf: The astr source file could not be found as the TeX statement \fonts\as=astr1 is to be processed. – Rüdiger Jan 7 '12 at 19:22 Did you updated the file name data base with the MiKTeX setup? – Herbert Jan 7 '12 at 19:31 Yep. After the described change, I issued initexmf --admin --update-fndb, then initexmf --admin --edit-config-file updmap, then initexmf --admin --mkmaps and finally again the update-fndb. I checked the font existence with the tex standard file tex testfont, entering astr1. The same message was issued as reported above (this is the message that also comes when entering a bogus font name like dasdad). On the other hand, the map file C:/Program Files/MiKTeX 2.9/fonts/map/dvips/astrology/astr1.map is correctly detected with kpsewhich astr1.map. What's happening? – Rüdiger Jan 7 '12 at 19:53 Why is the trailing 1 of the font name astr1 swallowed in the error message (The astr source file could not be found) ? Does this give any clue? – Rüdiger Jan 7 '12 at 19:56 \fonts\as=astr1 that is not possible, the LaTeX name of the font must have only letters. Use astr LAstrologyPi-One
show 8 more comments

A trailing '1' in the symbolic font name is not allowed. I used astr1 as symbolic font name in the map:

astr1 LAstrologyPi-One <astr1___.pfb

This used to work in my earlier MikTeX release (2.7) but is not valid in 2.9 any more.

Changing the map to

astr LAstrologyPi-One <astr1___.pfb

additionally requires the name of the TFM file to be adapted: It works if the TFM file name is made equal to the symbolic font name (astr.tfm), not to the real font name (astr1___.tfm).

For the details, see the comments to Herbert's answer above - he was just one minute before the complete solution! Thanks again, Herbert.

-