Application Interface Icons Appear Corrupt

arnymars · Nov 22, 2007

I wanted to thank you everyone for in-depth discussion on this urgent for me
issue that was very helpful and productive.

arnymars · Nov 22, 2007

Just wanted to add that looking at ShellIconCash file content with SysImg, I
don't see any Application Toolbal specific icons, in particular from
troublesome applications. They aren't probably stored in any handy file, but
instead always loaded from the relevant Program folder. Thats where
programming stype can speedup application window rendering. However, I guess
there may be indirect link leading to improper rendering.

Still, the combo of all suggested approaches fixed the issue for now, with
Win Theme switching appear to be the leading factor.

PCR · Nov 22, 2007

arnymars wrote:
| Just wanted to add that looking at ShellIconCash file content with
| SysImg, I don't see any Application Toolbal specific icons, in
| particular from troublesome applications.

How many icons showed up for you? I seem to currently have 735. There
appear to be duplicates in there, but I guess certain accompanying info
(color, pixel size, whatever) may be different (& doesn't show in
SysImg). And did you have anything in this Registry key...?...

HKEY_LOCAL_MACHINE\SOFTWARE\
Microsoft\Windows\CurrentVersion\
Explorer\Shell Icons

Mine is empty!

| They aren't probably stored
| in any handy file, but instead always loaded from the relevant
| Program folder. Thats where programming stype can speedup application
| window rendering. However, I guess there may be indirect link leading
| to improper rendering.
|
| Still, the combo of all suggested approaches fixed the issue for now,
| with Win Theme switching appear to be the leading factor.

Glad to hear it. I'm thinking, switching Themes may have a similar
effect to changing an icon size, which causes the RAM cache to (flush,
maybe). Also, could be, when you went to Standby & back, that might have
been equivalent to a Restart not involving a shortcut.

Yep, those URLs of glee's were edifying indeed. I'll need to read
through them a couple more times, though, before I can say any more!

Bill in Co. · Nov 22, 2007

PCR wrote:
> arnymars wrote:
>> Just wanted to add that looking at ShellIconCash file content with
>> SysImg, I don't see any Application Toolbal specific icons, in
>> particular from troublesome applications.
>
> How many icons showed up for you? I seem to currently have 735. There
> appear to be duplicates in there, but I guess certain accompanying info
> (color, pixel size, whatever) may be different (& doesn't show in
> SysImg). And did you have anything in this Registry key...?...
>
> HKEY_LOCAL_MACHINE\SOFTWARE\
> Microsoft\Windows\CurrentVersion\
> Explorer\Shell Icons
>
> Mine is empty!
>
>> They aren't probably stored
>> in any handy file, but instead always loaded from the relevant
>> Program folder. Thats where programming stype can speedup application
>> window rendering. However, I guess there may be indirect link leading
>> to improper rendering.
>>
>> Still, the combo of all suggested approaches fixed the issue for now,
>> with Win Theme switching appear to be the leading factor.
>
> Glad to hear it. I'm thinking, switching Themes may have a similar
> effect to changing an icon size, which causes the RAM cache to (flush,
> maybe). Also, could be, when you went to Standby & back, that might have
> been equivalent to a Restart not involving a shortcut.
>
> Yep, those URLs of glee's were edifying indeed. I'll need to read
> through them a couple more times, though, before I can say any more!

Some ancillary comments relating to this (my experience):

When my ShelliconCache reaches around say 4000 KB or so, I figure it's been
long enough, and delete it to let it rebuild.

It seems to work better that way if that file gets too large, the system
just seems to become a bit more quirky (in relation to rebooting and stable
desktop icons, etc).

Easiest way for me to rebuild it is to: 1) delete the ShelliconCache file,
2) shut down the computer, 3) power it back up, and let the icons get
rebuilt again (which takes a few minutes), and lastly 4) reboot the computer
to finally create the new and smaller ShelliconCache file.

arnymars · Nov 22, 2007

PCR

My key is empty too. I'm not sure why you mentioned this.
As to the size of ShellIconCash, I wonder how it can grow beyond max value
specified in Registry?
Also, I think changing Win Theme has broader effect than changing icon size
only, but the later action can result in ShellIconCash file update, while the
former doesn't necessarily lead to changing any icons or ShellIconCash (if
ever). But its true - it flashes some resources, though Standby doesn't seem
to be associated with RAM flash (if not opposite).

arnymars · Nov 23, 2007

PCR

From Glee's links it appears (between lines) that Max Cached Icons registry
value controls RAM only, but not a disk ShellIconCash damp at Win Exit. I
guess, Win98 bug prevents this control from working on some installations,
probably those not updated with Service Packs & Bug Fixes.

As to an Application Toolbar Icons, it looks like they are loaded from its
..dlls by the application at its Window (re)draw time. Some applications may
later keep them in a damp file in their program folder (that's why there are
loaded wrong every start) or in Win - Applications Data folder. Others load
their toolbar icons every time from .dlls, slowing the window rendering
process. In both scenarions, Win Theme change obviously makes a global
effect, prompting every application to flash there basic theme (before
applying skins) - interesting how in particular?

PCR · Nov 23, 2007

Bill in Co. wrote:
| PCR wrote:
|> arnymars wrote:
|>> Just wanted to add that looking at ShellIconCash file content with
|>> SysImg, I don't see any Application Toolbal specific icons, in
|>> particular from troublesome applications.
|>
|> How many icons showed up for you? I seem to currently have 735. There
|> appear to be duplicates in there, but I guess certain accompanying
|> info (color, pixel size, whatever) may be different (& doesn't show
|> in SysImg). And did you have anything in this Registry key...?...
|>
|> HKEY_LOCAL_MACHINE\SOFTWARE\
|> Microsoft\Windows\CurrentVersion\
|> Explorer\Shell Icons
|>
|> Mine is empty!
|>
|>> They aren't probably stored
|>> in any handy file, but instead always loaded from the relevant
|>> Program folder. Thats where programming stype can speedup
|>> application window rendering. However, I guess there may be
|>> indirect link leading to improper rendering.
|>>
|>> Still, the combo of all suggested approaches fixed the issue for
|>> now, with Win Theme switching appear to be the leading factor.
|>
|> Glad to hear it. I'm thinking, switching Themes may have a similar
|> effect to changing an icon size, which causes the RAM cache to
|> (flush, maybe). Also, could be, when you went to Standby & back,
|> that might have been equivalent to a Restart not involving a
|> shortcut.
|>
|> Yep, those URLs of glee's were edifying indeed. I'll need to read
|> through them a couple more times, though, before I can say any more!
|
| Some ancillary comments relating to this (my experience):
|
| When my ShelliconCache reaches around say 4000 KB or so, I figure
| it's been long enough, and delete it to let it rebuild.

That seems very huge! I've just deleted mine after a few experiments
that led to a crash, & it hasn't regenerated yet. But the one on my full
system backup is 1,002,755 bytes, with a create date of June 30, 2007.

| It seems to work better that way if that file gets too large, the
| system just seems to become a bit more quirky (in relation to
| rebooting and stable desktop icons, etc).

Since finding out about it, apparently I've been deleting it often
enough to keep it reasonable going by your number. But thanks.

| Easiest way for me to rebuild it is to: 1) delete the ShelliconCache
| file, 2) shut down the computer, 3) power it back up, and let the
| icons get rebuilt again (which takes a few minutes),

It's slow enough for me to see the Desktop icons draw twice-- generic
icons get replaced by the ones of my current Theme.

| and lastly 4)
| reboot the computer to finally create the new and smaller
| ShelliconCache file.

Yes, I have yet to do step 4. Wait a minute! Now I have remembered an
old trick-- "START, Shut Down, Cancel button". It has created a new one
without a reboot...

C:\WINDOWS>dir ShellIconCache /a
Directory of C:\WINDOWS
SHELLI~1 639,236 11-23-07 9:14p ShellIconCache

I forget who came up with that. Also, instead of 735, SysImg showed 198
icons in the RAM cache at boot. But that has already grown to 207 now.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

Bill in Co. · Nov 23, 2007

PCR wrote:
> Bill in Co. wrote:
>> PCR wrote:
>>> arnymars wrote:
>>>> Just wanted to add that looking at ShellIconCash file content with
>>>> SysImg, I don't see any Application Toolbal specific icons, in
>>>> particular from troublesome applications.
>>>
>>> How many icons showed up for you? I seem to currently have 735. There
>>> appear to be duplicates in there, but I guess certain accompanying
>>> info (color, pixel size, whatever) may be different (& doesn't show
>>> in SysImg). And did you have anything in this Registry key...?...
>>>
>>> HKEY_LOCAL_MACHINE\SOFTWARE\
>>> Microsoft\Windows\CurrentVersion\
>>> Explorer\Shell Icons
>>>
>>> Mine is empty!
>>>
>>>> They aren't probably stored
>>>> in any handy file, but instead always loaded from the relevant
>>>> Program folder. Thats where programming stype can speedup
>>>> application window rendering. However, I guess there may be
>>>> indirect link leading to improper rendering.
>>>>
>>>> Still, the combo of all suggested approaches fixed the issue for
>>>> now, with Win Theme switching appear to be the leading factor.
>>>
>>> Glad to hear it. I'm thinking, switching Themes may have a similar
>>> effect to changing an icon size, which causes the RAM cache to
>>> (flush, maybe). Also, could be, when you went to Standby & back,
>>> that might have been equivalent to a Restart not involving a
>>> shortcut.
>>>
>>> Yep, those URLs of glee's were edifying indeed. I'll need to read
>>> through them a couple more times, though, before I can say any more!
>>
>> Some ancillary comments relating to this (my experience):
>>
>> When my ShelliconCache reaches around say 4000 KB or so, I figure
>> it's been long enough, and delete it to let it rebuild.
>
> That seems very huge! I've just deleted mine after a few experiments
> that led to a crash, & it hasn't regenerated yet. But the one on my full
> system backup is 1,002,755 bytes, with a create date of June 30, 2007.

I have quite a few applications, AND my desktop is full of icons. Maybe
that's why. I can't ever get it THAT low (1000 KB) anymore (although
fairly close to that after a rebuild).

>> It seems to work better that way if that file gets too large, the
>> system just seems to become a bit more quirky (in relation to
>> rebooting and stable desktop icons, etc).
>
> Since finding out about it, apparently I've been deleting it often
> enough to keep it reasonable going by your number. But thanks.
>
>> Easiest way for me to rebuild it is to: 1) delete the ShelliconCache
>> file, 2) shut down the computer, 3) power it back up, and let the
>> icons get rebuilt again (which takes a few minutes),
>
> It's slow enough for me to see the Desktop icons draw twice-- generic
> icons get replaced by the ones of my current Theme.
>
>> and lastly 4)
>> reboot the computer to finally create the new and smaller
>> ShelliconCache file.
>
> Yes, I have yet to do step 4. Wait a minute! Now I have remembered an
> old trick-- "START, Shut Down, Cancel button". It has created a new one
> without a reboot...
>
> C:\WINDOWS>dir ShellIconCache /a
> Directory of C:\WINDOWS
> SHELLI~1 639,236 11-23-07 9:14p ShellIconCache
>
> I forget who came up with that. Also, instead of 735, SysImg showed 198
> icons in the RAM cache at boot. But that has already grown to 207 now.
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> Should things get worse after this,
> PCR
> pcrrcp@netzero.net

PCR · Nov 23, 2007

---- Original Message ----
From: "arnymars" <arnymars@discussions.microsoft.com>
Newsgroups: microsoft.public.win98.gen_discussion
Sent: Friday, November 23, 2007 12:33 AM
Subject: Re: Application Interface Icons Appear Corrupt

| PCR
|
| My key is empty too. I'm not sure why you mentioned this.

The key was mentioned in...
http://www.geocities.com/SiliconValley/4942/contents.html
...., BUT I see now it also says an initial RAM cache can also be created
from icons in SHELL32.DLL (which I DO have). Anyhow, I'm glad it's not
just mine that's empty!

| As to the size of ShellIconCash,

That's-- ShellIconCache.

| I wonder how it can grow beyond max
| value specified in Registry?

You mean where that URL says...!...

"The shell will not proceed with the save if the icon table is greater
that the maximum size."

I'm not positive what it is refering to! Where do you see Max Cached
Icons refered to?

| Also, I think changing Win Theme has broader effect than changing
| icon size only, but the later action can result in ShellIconCash file
| update,

Right. Switching the Theme is broader & may end up causing the RAM cache
to regenerate, but just changing the icon size forth & back is
sufficient...
http://www.geocities.com/SiliconValley/4942/contents.html
.......Quote...........
Other than freeing individual cache items, there are also
times when the entire cache needs to be cleared out. This
typically happens when you change the system icon size in
the Display Properties. Obviously the images in the image-
lists are now incorrectly sized, so the imagelists need to be
deleted and the whole cache rebuilt from scratch.
.......EOQ..............

| while the former doesn't necessarily lead to changing any
| icons or ShellIconCash (if ever).

Right, but that's-- ShellIconCache.

| But its true - it flashes some
| resources, though Standby doesn't seem to be associated with RAM
| flash (if not opposite).

Well, I was just guessing about that. How do you normally shutdown or
restart? Do you use the START button or a shortcut? Using a shortcut is
not sufficient to cause the ShellIconCache to regenerate. It's possible
going to Stanby & back might do it. (I should test that.) I do know
just...

"START button, Shut Down, CANCEL button"

....will do it! And I suppose it rebuilds the RAM Cache too, if that
hasn't already been rebuit. Here's another quote from that page...

"When the system is shutdown via the shell (not something
like ExitWindows), it will will attempt to save the cache to
disk before proceeding the actual shutdown."

| PCR
|
| From Glee's links it appears (between lines) that Max Cached Icons
| registry value controls RAM only,

Well, the RAM cache does get occasionally written to the ShellIconCache.
So, indirectly both sizes must be affected.

| but not a disk ShellIconCash

ShellIconCache-- I said!

| damp
| at Win Exit.

A proper shut down (not using a shortcut) will cause the ShellIconCache
to be rebuilt from the RAM Cache, when appropriate. You can even cancel
the shutdown, & it will be built, if it had been deleted or Windows
believes it otherwise to be appropriate.

| I guess, Win98 bug prevents this control from working on
| some installations,

You mean this (from that URL)...?...

........Quote..............
There is one small catch to this operation though. The shell will not
proceed with the save if the icon tableis greater that the maximum size.
However, as we've dis-cussed earlier, the icon table never actually
removes any entries - it only marks them as being 'free' when they're
flushed. The result is that once the cache exceeds its maxi-mum size, it
will never be possible to save it (you could get around this by doing a
complete cache flush though).
.........EOQ.....................

I think the complete cache flush is accomplished by changing icon size
forth & back in Display Properties. However, yea, I guess that is a bug
for us to have to do it.

| probably those not updated with Service Packs &
| Bug Fixes.

Nope. I have all of those. Probably it is 3rd party apps that cause the
RAM Cache to occasionally require us to manually flush it.

| As to an Application Toolbar Icons, it looks like they are loaded
| from its .dlls by the application at its Window (re)draw time. Some
| applications may later keep them in a damp file in their program
| folder (that's why there are loaded wrong every start) or in Win -
| Applications Data folder. Others load their toolbar icons every time
| from .dlls, slowing the window rendering process. In both scenarions,
| Win Theme change obviously makes a global effect, prompting every
| application to flash there basic theme (before applying skins) -
| interesting how in particular?

It could be as you say. Some applications are just mangling the RAM icon
cache!

PCR · Nov 23, 2007

arnymars · Nov 24, 2007

PCR

Thanks for fixing my spelling errors - now I get it!
What I mean about bug fixes, obvious from Glee's citation:

"The behaviour of the cache file can vary wildly from system to system. I've
seen some where the file stays relatively static after a certain size is
reached, and other systems where it continues to grow seemingly without end,
and must be deleted periodically. I've found on Win9x systems where the cache
keeps growing and growing, that it's best to delete the file once the stored
icons get over about 1000-1500 in number".

But the "Cash" should not grow beyond max value specified in Registry!
Obviously - it doesn't work on some installations, where MS bug fixes were
not applied. On my PC the "Cash" size is stable.

However, I found that NONE of third party application interface icons are
ever stored in the "Cash". However, changing the Theme followed by flash (of
what RAM registers?) appears to work, but not forever - the issue reappears
after intence PC work - I guess at that point some resources are scarse. It
looks like by not documenting related to icons commands, MS made developers
work more difficult, especially when programs & drivers must interact with OS
at application window rendering. It affected speed of the programs startup
(their interface was excluded from speed optimization via "Cash") - may be
that was the main competitive reason for MS to hide this info.

PCR · Nov 24, 2007

arnymars wrote:
| PCR
|
| Thanks for fixing my spelling errors - now I get it!
| What I mean about bug fixes, obvious from Glee's citation:
|
| "The behaviour of the cache file can vary wildly from system to
| system. I've seen some where the file stays relatively static after a
| certain size is reached, and other systems where it continues to grow
| seemingly without end, and must be deleted periodically. I've found
| on Win9x systems where the cache keeps growing and growing, that it's
| best to delete the file once the stored icons get over about
| 1000-1500 in number".
|
| But the "Cash" should not grow beyond max value specified in Registry!
| Obviously - it doesn't work on some installations, where MS bug fixes
| were not applied. On my PC the "Cash" size is stable.

Well, I must admit I really don't know whether bug fixes are involved. I
don't recall my ShellIconCache on disk ever getting larger than 1 MB--
but I haven't always been looking! Currently, after a delete & reboot it
is...

C:\WINDOWS>dir ShellIconCache /a
Directory of C:\WINDOWS
SHELLI~1 639,236 11-23-07 9:14p ShellIconCache

(Which seems large for a fresh one.) Going by SysImg, the RAM cache
definitely will begin to grow again after it's been flushed. Before a
flush, I had 735 icons in mine. After the flush & reboot today (well,
yesterday now), I spotted only 198. Shortly, it grew to 207-- & now
have I have 338 in there!

| However, I found that NONE of third party application interface icons
| are ever stored in the "Cash".

How many icons are in your cache? I do see 3rd party icons in mine, such
as the Z of ListZapper & the Skull & Crossbones of EndItAll that are in
my QuickLaunch Bar. Looks like all of them are there & in the same
order-- they are icons 34-75!

| However, changing the Theme followed
| by flash (of what RAM registers?)

It's probably in a block of RAM, not in registers.

| appears to work, but not forever -
| the issue reappears after intence PC work - I guess at that point
| some resources are scarse.

How many icons are in the RAM cache when the issue appears?

| It looks like by not documenting related
| to icons commands, MS made developers work more difficult, especially
| when programs & drivers must interact with OS at application window
| rendering. It affected speed of the programs startup (their interface
| was excluded from speed optimization via "Cash") - may be that was
| the main competitive reason for MS to hide this info.

There could be some truth to that.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

PCR · Nov 24, 2007

PCR wrote:
| arnymars wrote:
|| PCR
||
|| Thanks for fixing my spelling errors - now I get it!
|| What I mean about bug fixes, obvious from Glee's citation:
||
|| "The behaviour of the cache file can vary wildly from system to
|| system. I've seen some where the file stays relatively static after a
|| certain size is reached, and other systems where it continues to grow
|| seemingly without end, and must be deleted periodically. I've found
|| on Win9x systems where the cache keeps growing and growing, that it's
|| best to delete the file once the stored icons get over about
|| 1000-1500 in number".
||
|| But the "Cash" should not grow beyond max value specified in
|| Registry! Obviously - it doesn't work on some installations, where
|| MS bug fixes were not applied. On my PC the "Cash" size is stable.
|
| Well, I must admit I really don't know whether bug fixes are
| involved. I don't recall my ShellIconCache on disk ever getting
| larger than 1 MB-- but I haven't always been looking! Currently,
| after a delete & reboot it is...
|
| C:\WINDOWS>dir ShellIconCache /a
| Directory of C:\WINDOWS
| SHELLI~1 639,236 11-23-07 9:14p ShellIconCache
|
| (Which seems large for a fresh one.) Going by SysImg, the RAM cache
| definitely will begin to grow again after it's been flushed. Before a
| flush, I had 735 icons in mine. After the flush & reboot today (well,
| yesterday now), I spotted only 198. Shortly, it grew to 207-- & now
| have I have 338 in there!
|
|| However, I found that NONE of third party application interface icons
|| are ever stored in the "Cash".
|
| How many icons are in your cache? I do see 3rd party icons in mine,
| such as the Z of ListZapper & the Skull & Crossbones of EndItAll that
| are in my QuickLaunch Bar. Looks like all of them are there & in the
| same order-- they are icons 34-75!
|
|| However, changing the Theme followed
|| by flash (of what RAM registers?)
|
| It's probably in a block of RAM, not in registers.
|
|| appears to work, but not forever -
|| the issue reappears after intence PC work - I guess at that point
|| some resources are scarse.
|
| How many icons are in the RAM cache when the issue appears?
|
|| It looks like by not documenting related
|| to icons commands, MS made developers work more difficult, especially
|| when programs & drivers must interact with OS at application window
|| rendering. It affected speed of the programs startup (their interface
|| was excluded from speed optimization via "Cash") - may be that was
|| the main competitive reason for MS to hide this info.
|
| There could be some truth to that.

How does your Registry compare to this...?...

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer
DisableFlushWrites 01 00 00 00
IconUnderline 02 00 00 00
Max Cached Icons "4096"
UseCopyMaxBufferSize 01 00 00 00

Did you spell "Max Cached Icons" correctly-- & with the spaces? (I'm not
precisely sure what the other entries mean.)

arnymars · Nov 24, 2007

PCR

Today I have 602 icons in "Cash", sized total at 1,607 Kb - and the size is
relatively stable. But I didn't monitor it daily, just a few times. I
recently set Reg value to 4096 without any over-the-time effect on actual
"Cash" size.

It looks like only icons, identifying file extentions, and program Shortcut
icons are included in my "Cash". But NONE of trouble applications' interface
(toolbar button) icons - or I just can't notice them? If none, that leaves
application developers on their own, when it comes to program lunch
optimization. The bug (later fixed) seems to be their, otherwise why would
"Cash" grow beoynd Registry set limit?

I have the following for that Registry Key:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer]
"IconUnderline"=hex(0):03,00,00,00
"DisableFlushWrites"=hex:01,00,00,00
"UseCopyMaxBufferSize"=hex:01,00,00,00
"MaxLimit2"="RERROMSLMY39407"
"StartMenuScrollPrograms"="FALSE"
"Max Cached Icons"="4096"

PCR · Nov 24, 2007

arnymars wrote:
| PCR
|
| Today I have 602 icons in "Cash", sized total at 1,607 Kb - and the
| size is relatively stable. But I didn't monitor it daily, just a few
| times. I recently set Reg value to 4096 without any over-the-time
| effect on actual "Cash" size.

Alright, but that's-- Cache! I see today I have 337 icons in mine. And
ShellIconCache has grown to...

C:\WINDOWS>dir ShellIconCache /a
Directory of C:\WINDOWS
SHELLI~1 1,005,595 11-24-07 3:04a ShellIconCache

...., on my 2nd day after deleting it. (That seems fairly huge for just
337!)

| It looks like only icons, identifying file extentions, and program
| Shortcut icons are included in my "Cash". But NONE of trouble
| applications' interface (toolbar button) icons - or I just can't
| notice them?

No. You are right. I don't see Toolbar button icons in mine, either,
like the scissors of "Cut" or the "abc" of "Spelling" in this OE window.
That's right, which makes it unlikely the RAM or disk Icon caches are
responsible for the fuzziness you have described.

It likely is something else about switching or reinstating a Theme that
is your cure. I guess maybe...

(a) Jot down all the values you see in the Item dropdown list at
"Display Properties, Appearance tab", which looks to be a lot of work.
Also, jot down the settings at the Settings tab & its Advanced button.
When the fuzziness recurs, make a comparison, before you switch Themes
for the cure.

(b) I guess, nonetheless, keep an eye on the growth of your RAM icon
cache with SysImg. Does it get to a prohibitive size when the problem
occurs?

| If none, that leaves application developers on their
| own, when it comes to program lunch optimization.

It could be some 3rd party apps require a certain screen resolution to
display optimally. That is set by the slider at "Display Properties,
Settings tab". Also, the Colors selection there may matter. Keep an eye
on those. If the problem shows up & they haven't changed-- maybe they
need changing!

| The bug (later
| fixed) seems to be their, otherwise why would "Cash" grow beoynd
| Registry set limit?

Well, what is the math involved in that? How many icons are too many for
our "Max Cached Icons"="4096"? If 4097 is the number-- you don't seem to
have reached it! But keep an eye on it!

| I have the following for that Registry Key:
|
|
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer]
| "IconUnderline"=hex(0):03,00,00,00
| "DisableFlushWrites"=hex:01,00,00,00
| "UseCopyMaxBufferSize"=hex:01,00,00,00
| "MaxLimit2"="RERROMSLMY39407"
| "StartMenuScrollPrograms"="FALSE"
| "Max Cached Icons"="4096"

I think that's close enough to what I have to be perfectly correct.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net

Application Interface Icons Appear Corrupt

arnymars

arnymars

PCR

Bill in Co.

arnymars

arnymars

PCR

Bill in Co.

PCR

PCR

arnymars

PCR

PCR

arnymars

PCR

Similar threads