Window font XP Professional

  • Thread starter Thread starter Pierre
  • Start date Start date
P

Pierre

When I opened my PC today I found that all icons on the desktop are labelled with a graphic font (e.g. Wingdings type, e.g. Pierre ). Makes it very hard to work with. The menus as well etc. In the applications as well. Long story short in OExpress the top bar is the same graphic stuff but the icon bar is legible, albeit the font is not the usual one. The list of directories is legible except those in bold (contain one unread msg). When I mark all msgs in this directory as "all read" then the directory is not bold anymore and is in a legible font.

Further test: on this msg the original font was legible but not usual and when I tried to chose another one (under HTML) I see the set of fonts has been reduced to 5. (FixedSys, Marlett, Sydnie (never seen before), System and Terminal). So, I suspect there is something corrupt not with the fonts - under DOS (legible) they seem to be all here - but with the sequence of the system that looks for the appropriate fonts to use in the proper place. I have read that Tahoma is the default font for Explorer for instance.

I noted that the boot takes more time. Probably because the system tries to find the fonts and finally uses Marlett. I am sure it is this one since I tested it on some words (eg Pierre in the example above). I also remember in olde times than under DOS when the font management was corrupt Marlett was pointing its ugly head.

Now, how do I restore this system to proper response? I used McAfee Quick Clean yesterday before closing and it did some registry clean up. Did it erase some required registry keys?

Tx
 
Message from Plato totally useless.
I found out that the system had been corrupted enough that Windows did not
recognize the directory windows/fonts, although DOD did.
In the end the only solution was to "repair" the installation through the
installation CD. Works, now.
Note that this happened after using QuickClean Lite from McAfee, who, on
chat, told me that there as no log of what was removed from the registry
under "registry cleaner". Makes it tough to repair, even manually. Beware of
that operation.
Any way since lacking access to the proper fonts for display most windows
showed text under the Marlett font, which is purely graphics, thus
unreadable, this would have been making manual repair difficult; I could not
even read what I typed.
 
Pierre said:
Message from Plato totally useless.
I found out that the system had been corrupted enough that Windows did not
recognize the directory windows/fonts, although DOD did.
In the end the only solution was to "repair" the installation through the
installation CD. Works, now.
Note that this happened after using QuickClean Lite from McAfee, who, on
chat, told me that there as no log of what was removed from the registry
under "registry cleaner". Makes it tough to repair, even manually. Beware of
that operation.
Any way since lacking access to the proper fonts for display most windows
showed text under the Marlett font, which is purely graphics, thus
unreadable, this would have been making manual repair difficult; I could not
even read what I typed.
Click to expand...

I'm having the same trouble after using a program called Registry Mechanic. I'll try what you suggest to see if it helps.
 
Always make are restore point and backup the registry before using any
of these programs. For the most part registry cleaners cause more harm
than good unless you know what you are doing and are very watchful on
the changes they make.

Here is a good program for backing up the registry, ERUNT.
http://home.t-online.de/home/lars.hederer/erunt/
 
Back
Top