MS .NET Framework 1.1 MEMORY FIX

[fester]

http://support.microsoft.com/default...b;en-us;833610

The problem is high memory condition (while BTV is running) caused by MS .NET software - not btv. To get the fix you actually have to contact MS

RESOLUTION
You can resolve some of this problem by making the Framework allocate memory in smaller sizes for large objects. This hotfix adjusts the allocation size for the large object heap segments from 64 megabytes (MB) per segment to 16 MB. This hotfix also addresses a fragmentation problem in the loader heap of the .NET Framework.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS

[Eric3a]

Did you get the download? I am running high memory load, bute don't know if it's a function of BTV (TP3) or .net.
Would love to try it if you've got a copy.
Eric

[fester]

no - i didnt get the download. ever since i started using the latest build a week or two ago i started seeing a bit of strange behavior after about 4 days. so i read some of the memory specific posts and non mentioned this .NET issue. right now i'll prob wait for .NET SP1 or just go back to the old build... or just grin and bear it

[Eric3a]

Ok thanks;
I'll wait for the service pack then
Eric

[mcowger]

Given that SP2 is almost out, it probably wont be included in a Windows XP SP, but in a later hotfix.