another windows xp problem?

[Frank Ganz]

>-----Original Message-----
>From: Christina Thiele [mailto:cthiele at ccs.carleton.ca]
>Sent: Friday, January 23, 2004 1:53 PM
>To: Techsupport at yandy.com
>Subject: Re: another windows xp problem?
>
>
>John.De-Bruyn at ujf-grenoble.fr writes:
>n>
>> Hello again. I have another strange problem using YandY tex
>on my windows XP
>> laptop. This one started after I installed Microsoft Office.
>After I reboot
>> the computer, when I run DVIWINDO it tells me it cannot find
>the fonts I am
>> using (standard CM fonts). I look where I think the fonts
>are supposed to
>> be, and they appear to be there, but DVIWINDO can't find
>them. I reinstall
>> the fonts and everything is OK again, until I reboot the
>computer again, and
>> the whole business repeats and I have to re-re-install the fonts.
>>
>> As I say, this only started after I installed Microsoft
>office, so my guess
>> is that Office changes something that DVIWINDO uses to find
>the fonts, and
>> reinstalling the fonts changes it back, but I have no idea
>what it might be
>> nor how to stop this from happening.
>>
>> Any suggestions?
>> thanks,
>> John
>>
>> _____________________________________________________
>> John R. de Bruyn          :  jdebruyn at ujf-grenoble.fr
>> Laboratoire de Rheologie  :  phone: +33 (0)4 76 82 51 77
>> 38041 Grenoble Cedex 9    :  fax: +33 (0)4 76 82 51 64
>> France
>>
>>
>
>
>Is there _any_ chance that you're installing things on a machine
>_without_ doing it as the administrator? That is, one has to have
>administrative privileges to install the whole shebang. I believe we
>saw a similar situation several months ago, and it was indeed the
>access issue.
>
>Ch.
>


>After I reboot
>> the computer, when I run DVIWINDO it tells me it cannot find
>the fonts I am
>> using (standard CM fonts).


Dear John,

The best way to tackle any issue is by stating the error message word for word. You haven't done so.

To illustrate why this is important, here's an example of my own exprience:

(1) A user creates a document that uses only CM fonts. The user knows this.
(2) The user opens the DVI file in DVIWINDO and sees an error message. He only knows it has to do with fonts, but not what's wrong specifically
(3) The user jumps to the conclusion that there's a problem with the fonts in the document.

Now somebody else deciphers the error message and establishes, that the fonts that cannot be found are not used in the document, but are fonts another program uses, i.e.: Word (part of Office). For some reason there is a conflict when DVIWINO and Word are open at the same time. Closing Word makes the error go away.

This may not be your situation, but serves as an illustration why it's important to have very good problem descriptions including exact wording of error messages.

So, please make sure to specify the error message word for word.

Thanks,
Frank