Re: MiKTeX 2.9 and Windows 7: strange font problem

Hans Marius Eikseth <[email protected]>
Newsgroups gmane.comp.tex.miktex
Message-ID <[email protected]>
> From: Ulrike Fischer [[email protected]]
> Sent: 2011-07-14 14:35:58 MEST
> To: [email protected]
> Subject: Re: [MiKTeX] MiKTeX 2.9 and Windows 7: strange font problem
> 
> Am Thu, 14 Jul 2011 13:31:12 +0200 (MEST) schrieb Hans Marius
> Eikseth:
> 
> > Well, today is yesterday's tomorrow, so I have uploaded a zipped folder (minimalbeispiel.zip) accessible on the following link:
> > https://files.me.com/hans.marius.eikseth/opuozt
> 
> >>From my previous post, the YAP/MiKTeX error report contains these paths:
> > 
> > Root0: \\ans-fil-rv-1\home-rv$\hans\System\Programdata\MiKTeX\2.9
> > Root1: C:\Users\hans\AppData\Local\MiKTeX\2.9
> > Root2: C:\miktex29
> > Root3: C:\ProgramData\MiKTeX\2.9
> > Root4: C:\Program Files (x86)\MiKTeX 2.9
> > UserInstall: C:\miktex29
> > UserConfig: \\ans-fil-rv-1\home-rv$\hans\System\Programdata\MiKTeX\2.9
> > UserData: C:\Users\hans\AppData\Local\MiKTeX\2.9
> > CommonInstall: C:\Program Files (x86)\MiKTeX 2.9
> > CommonConfig: C:\ProgramData\MiKTeX\2.9
> > CommonData: C:\ProgramData\MiKTeX\2.9
>  
<snip> 
> That's normal. Some of the roots have special names/functions.
> Miktex simply list at first all roots and then the named ones again.
> So Root0=UserConfig. It is also normal that some roots are mentioned
> which are actually not used/or even don't exist, I see them too. 

Thanks for your patient replies!
 
> Now to your problem. 
> 
> Your pdflatex log shows the source of the problem:
> pdfTeX warning: pdflatex (file pdftex.map): cannot open font map
> file. 
> 
> First some background: In a normal windows there exist two types
> user "profiles": the roaming profile and the local profile. In a
> network the roaming profile is normally backup on the server when
> you log out and if you log in on another pc it is copied down. The
> local profile is always only on one pc and it is quite possible that
> it is deleted when you log out - and at my opinion that is happening
> here. 
> 
> The UserData root in the local user profile (here
> C:\Users\hans\AppData\Local\MiKTeX\2.9). UserData contains generated
> files like the filename databases (FNDB), pk-files from fonts and
> also the missing pdftex.map. 

This is most helpful! I think we are very close to finding a solution to this one :)

> pdflatex will recreate missing fndb-files on-the-fly (do you see a
> noticable delay at the start of the compilation) but it will not
> call updmap if the map is missing and so fonts are not found. 
> 
> Do the following: Call on the command line 
>   initexmf -u
> and
>   updmap
> 
> Then try your minimal example again. If it works: Check the content
> of the UserData-root, then log out and log in and check.

Yes, it worked! My minimal example compiled, but it did not compile after a logout/login.

As you suspected, the UserData root content had changed.

After (initexmf -u AND updmap):
content of C:\Users\hans\AppData\Local\MiKTeX\2.9 are folders
dvipdfm
dvips
fontconfig
fonts
miktex
pdftex

After (logout AND login):
content of C:\Users\hans\AppData\Local\MiKTeX\2.9 are folders
fonts
miktex

There! Do you now have further directions for solving this particular environment challenge? Is more information needed?

I am very happy to have come this far, thanks a lot Ulrike!

Best regards,
Hans Marius Eikseth

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev

_______________________________________________
MiKTeX-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/miktex-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.