Alain wrote:
> 
> By the way, anybody know how to repair the windows fonts folder that 
> stopped to works as intended? I can't install new fonts and the folder 
> acts just like a regular folder. On Win XP.
> 

There's a "Repair Fonts Folder" option in the TweakUI Powertoy.  I don't 
know where MS is hiding it these days--it doesn't seem to be where 
Google thinks it is:

http://windows.microsoft.com/en-US/windows/downloads/windows-xp

...but it does appear to be here:

http://windowsxp.mvps.org/tweakui.htm

I've never used that particular feature, but it might be what you're 
looking for.

--Sherry Shaw


-- 
#macro T(E,N)sphere{x,.4rotate z*E*60translate y*N pigment{wrinkles scale
.3}finish{ambient 1}}#end#local I=0;#while(I<5)T(I,1)T(1-I,-1)#local I=I+
1;#end camera{location-5*z}plane{z,37 pigment{granite color_map{[.7rgb 0]
[1rgb 1]}}finish{ambient 2}}//                                   TenMoons

Post a reply to this message

On 4/6/2011 10:04, Alain wrote:
> By the way, anybody know how to repair the windows fonts folder that stopped
> to works as intended? I can't install new fonts and the folder acts just
> like a regular folder. On Win XP.

I'm guessing you deleted the desktop.ini hidden system file from the 
directory, which is what tells Explorer that it's an unusual folder. See if 
putting these two lines into a file in your font folder called desktop.ini 
and making it hidden and system does the trick. It has the secret GUID code 
that tells Explorer what to invoke to modify what it displays.

[.ShellClassInfo]
UICLSID={BD84B380-8CA2-1069-AB1D-08000948F534}

-- 
Darren New, San Diego CA, USA (PST)
   "Coding without comments is like
    driving without turn signals."

Post a reply to this message

Le 2011/04/11 11:38, Darren New a écrit :
> On 4/6/2011 10:04, Alain wrote:
>> By the way, anybody know how to repair the windows fonts folder that
>> stopped
>> to works as intended? I can't install new fonts and the folder acts just
>> like a regular folder. On Win XP.
>
> I'm guessing you deleted the desktop.ini hidden system file from the
> directory, which is what tells Explorer that it's an unusual folder. See
> if putting these two lines into a file in your font folder called
> desktop.ini and making it hidden and system does the trick. It has the
> secret GUID code that tells Explorer what to invoke to modify what it
> displays.
>
> [.ShellClassInfo]
> UICLSID={BD84B380-8CA2-1069-AB1D-08000948F534}
>

That was it, sort of!

The file WAS there, and it's content /looked/ identical, but it seems 
that there was something wrong with the content, like an invisible 
control character in the string...

Sherry, your proposition was the very first thing that I tried.


Alain

Post a reply to this message

On 4/11/2011 9:49, Alain wrote:
> The file WAS there, and it's content /looked/ identical, but it seems that
> there was something wrong with the content, like an invisible control
> character in the string...

I can't imagine what happened that wound up changing parts of the file. 
Nobody really looks at that except explorer.  The only thing I can think of 
is you dragged the whole directory (or at least something including 
desktop.ini) from a different OS and wound up changing the class id to 
something visually similar but different. (I.e., where the class id might be 
BD48B380... in Vista or some such.)

Odd. Glad to have helped, tho.

-- 
Darren New, San Diego CA, USA (PST)
   "Coding without comments is like
    driving without turn signals."

Post a reply to this message

Le 2011/04/11 14:08, Darren New a écrit :
> On 4/11/2011 9:49, Alain wrote:
>> The file WAS there, and it's content /looked/ identical, but it seems
>> that
>> there was something wrong with the content, like an invisible control
>> character in the string...
>
> I can't imagine what happened that wound up changing parts of the file.
> Nobody really looks at that except explorer. The only thing I can think
> of is you dragged the whole directory (or at least something including
> desktop.ini) from a different OS and wound up changing the class id to
> something visually similar but different. (I.e., where the class id
> might be BD48B380... in Vista or some such.)
>
> Odd. Glad to have helped, tho.
>

Nothing like that.
The text was exactly the same, just did a compare with a copy I made 
while trying to see what was wrong. The file was hide but not system.

It was working. I had a disk crash on my OS drive. I reinstalled on a 
freshly formated drive.
Immediately after the reinstall, the normal functionality was broken.
This mean that the installation process did something wrong, like miss 
set the system flag or something.

As they say: Two identical computers, with the same periferals and OS 
ARE'NT...


Alain

Post a reply to this message

On 4/11/2011 13:03, Alain wrote:
> Immediately after the reinstall, the normal functionality was broken.

Thanks for the info. That's definitely odd. :-)

-- 
Darren New, San Diego CA, USA (PST)
   "Coding without comments is like
    driving without turn signals."

Post a reply to this message