i920 File Caching Settings [PATCH RELEASED!]

[Guest tedkord]

... especially here in 2011 with Android at the top of the mobile UI foodchain.

Said the guy sporting a Fascinate... :(

Seriuosly, my experience with the Omnia II is the reason I don't have a Fascinate right now. I'm wary of ANY Samsung handset now.

Edited March 9, 2011 by tedkord

[Guest amdzero]

Said the guy sporting a Fascinate... :(

Seriuosly, my experience with the Omnia II is the reason I don't have a Fascinate right now. I'm wary of ANY Samsung handset now.

totally understandable, and I'll be the first one to say that team Samsung+Verizon also dropped the ball on the Fascinate. But luckily we have some SERIOUSLY talented devs to include Adrynalyne (one of the great i910 chefs) who has brought Froyo to an already BAD ASS phone!

[Guest Bryan W.]

That is actually using CoOkie Home Tab, which slows down the phone a bit more. I'll try to cook a scaled down version of sense, and lets see if ppl like it.

can you make a cab of this?

I don't want to flash a new rom just to check out a few ideas.

[Guest tedkord]

totally understandable, and I'll be the first one to say that team Samsung+Verizon also dropped the ball on the Fascinate. But luckily we have some SERIOUSLY talented devs to include Adrynalyne (one of the great i910 chefs) who has brought Froyo to an already BAD ASS phone!

Adryn is the man. Used his and BGILL55's ROMs on my i910 back in the day. Android lured some seriously talented chefs away from the i910.

BGILL actually got an i920 initially, but dumped it for a droidX, I believe. A shame. While he wasn't one of the innovators, he was one of the best at taking the best of all others work, and tying it together (imo).

[Guest Bryan W.]

Ok, I think I have pinned down the performance issue, and perhaps why Samsung made no proper drivers...

It is known our microprocessor is the S3C6410, and it has the ability to render opengl 1 & 2.

A little more digging reveals there is a 'cpu core' inside these microprocessors. This same core might be used in different microprocessor models. Our microprocessor uses the ARM1176JZF-S core. This core is used in like 4 more Samsung microprocessor models, and 2 microprocessor models in some off brand.

It might be interesting to note, that in NO HTC device exists any ARM1176JZF-S core . Why???

Well, I found in a few minutes, that HTC runs on Qualcomm microprocessors, that run the ARM1136EJ-S core. Among other things, what comes with this core, they ALL HAVE CO-PROCESSORS. Yup, they have a chip to assist in rendering. All HTCs do, and other devices and brands as well...

No Samsung device (based on the same core as in our phone at least) has a co-processor. So although the core has the ability to render opengl 1 & 2, it simply doesn't have the juice to do it with any performance.

O2 - note microprocessor http://pdadb.net/index.php?m=specs&id=...20_omnia_ii_8gb

02's microprocessor - http://pdadb.net/index.php?m=cpu&id=a6...samsung_s3c6410

-note in description lack of mention of co-processor

-quick google of all microprocessors containing this core also lack microprocessor or are used in a htc device

TP2 - note microproc http://pdadb.net/index.php?m=specs&id=...htc_rhodium_500

tp's microproc - http://pdadb.net/index.php?m=cpu&id=a7...ualcomm_msm7600

- note mention of coprocessor

- I repeated this over may devices and found results to be consistent.

So the solution.. give up on a magical driver and cut the eye candy.

In searching, I found this thread regarding another Samsung phone with poor graphics performance, and no drivers.

http://forum.xda-developers.com/showthread.php?t=912937

Edited March 9, 2011 by Bryan W.

[Guest amdzero]

can you make a cab of this?

I don't want to flash a new rom just to check out a few ideas.

Here is a link to CHT:

http://forum.xda-developers.com/showthread.php?t=792303

if you try it you might also install the CHT Editor tab, link is in that same post.

[Guest Bryan W.]

Here is a link to CHT:

http://forum.xda-developers.com/showthread.php?t=792303

if you try it you might also install the CHT Editor tab, link is in that same post.

Silly question I'm sure.. It requires that sense be preinstalled, and I don't have it on this rom. Also, I read I have to find the one made for the omnia.. Do you happen to know where that is?

[Guest dgyahn]

I personally think they key is to get the basic UI minus the eye candy.

Gchris Titanium has limitations. All I really want is a nice layout for my home screen that is fast.

However, I don't know how much Sense is designed to have its graphics disabled. That and the i920 ram is gimped. That is like buying a sports car for looks and trying to take everything off to make it a Geo Metro so one could save gas... If this could be done with Sense, I'd love it, lol.

Even SPB takes more cpu... nothing is as fast as Titanium. To me, updating gchris might be a solution, but I haven't put the effort since the general populace is in love with the whole Sense thing. There are nice Titanium plugins out there, and you know what? They pale in downloads to Sense despite its performance problems.

To me, a fast phone beats bleeding edge tech that hardly works in the real world. I think dumbing down Sense to make it work quick is worth a go, and really the best way it can succeed on our phone.

My ideas:

Make ROM overall save as much ram as possible.

Enable overclock scripts.

Disable Sense CPU and graphical intensive features.

--The text page has some blending effect... I vote we disable that if possible. Same idea for the rest.

--Are the backgrounds of each page a picture, straight color, or some sort of graphic dithering? Cut it, set it to black.

Disable lesser important Sense features that take RAM.

Optimize page pool for Sense (I read about this I have to admit I don't know how it works)

Or any of those performance features mentioned in other threads.

Just brain storming... Disable all pages.. to save ram and cache. They are slow anyways. Just make shortcuts to the real apps in the favorites section or whatever its called. Real apps are faster than 'page apps' on that slider anyways. For music make shortcut to Samsung music app, or calendar to samsung calendar app.. Etc.. or MS apps, really is up to personal taste.. I like Samsung apps.

If possible, setup the main screen like in this (example). For those who want a preview of a text or email like the pages did on the slider, well S2U2 does that nicely before you even unlock.

This puts the emphasis on just the home page. Possibly saves on screen real estate if that bar can be turned off. Your start bar on bottom contains notifications, so we dont need to see them again in Sense slider. If that not possible well obviously I don't know how sense works. :(

As you can tell.. I prefer the real apps over the mini apps on the slider.. I just want a nice home page, access to messages, and quick access to my most used apps. Now that I think of it, I might do a little research and see if disabling all pages, but home, is possible and see what happens.

Oh.. and, please, if AMD allows it, include the dialer skin changer.

That's my problem with Sence on the O2. Everything is just so darn S...L...O...W. You have to tweak the snot out the software to get Sence to run with some efficiency. The eye candy was great but you had to wait forever just to do simple tasks. M2D rocked on my original Omnia i910. It's a shame we can't get this to perform well on our O2s. Anyway that's why I use SPB Mobile Shell. I can get a Sense type today screen and don't have the issues of trying to get the OS to run on my device. We've got a lot of OS front ends to choose from, Titanium, Samsung Today, SPB Mobile Shell and many Today Plug-ins. I would like to have Sense on my phone but what's the use if it performs like a rock. I use Lightwaver's x-920 ROM with SPB MS and DROID PRO+ 3.0 by DOC3000 & MSKIP. As I've said in other posts this rocks on my phone and will be my setup for some time. The ROM is lean and mean enough with all the functionality of the original Samsung apps built in. I've got plenty of free memory and its's fast enough for me. Anyway my phone looks great, give me all the functionality I need and just plain works. And isn't that what counts?

Edited March 9, 2011 by dgyahn

[Guest Bryan W.]

I can't find a straight cab of sense.. Perhaps its some great secret or can only be baked in..

xlightwaverx, if you already have a rom that has most of the tweaks and all already, I would like to beta and help find fixes..

I don't know how to do as much as you, mainly anything that that is done on the cooking side... I'd just like to tinker if I may. Would you share your latest compilation?

Check out these posts:

http://forum.ppcgeeks.com/cdma-tp2-develop...tml#post2066455

reg tweaks, I think you are already aware of these, but just further proof of valididy

http://forum.ppcgeeks.com/cdma-tp2-develop...tml#post2066459

some users test different branch builds of winmo to find the fastest..

Edited March 10, 2011 by Bryan W.

[Guest xlightwaverx]

I can't find a straight cab of sense.. Perhaps its some great secret or can only be baked in..

xlightwaverx, if you already have a rom that has most of the tweaks and all already, I would like to beta and help find fixes..

I don't know how to do as much as you, mainly anything that that is done on the cooking side... I'd just like to tinker if I may. Would you share your latest compilation?

Check out these posts:

http://forum.ppcgeeks.com/cdma-tp2-develop...tml#post2066455

reg tweaks, I think you are already aware of these, but just further proof of valididy

http://forum.ppcgeeks.com/cdma-tp2-develop...tml#post2066459

some users test different branch builds of winmo to find the fastest..

file system cache - 4MB

file system filter cache - 65536 sector

glyph cache - 64 kb

Weird, the default glyph cache is 4096 sectors if I remember correctly. That drops it significantly. I'll try it, though I am entering them manually, not with the tool. I am running a cooked CHT Sense 2.5.1920, and it runs pretty smooth. I'll see what changes. Thanks for the update. I'll see if I can get a release tonight for the new Sense. That glyph cache is for all graphics on the system, not just icons.

X

Edit:

Ok, I've managed to come up with a working patch for the i920. I've re-flashed my Current CHT ROM with XMenu on top of it. Straight from boot, the XMenu would lag on Sense. After the patch, it flies. Data access has increased, and over graphic speed as increased. Let me know what you folks think. Feel free to run some benchmark tests and post them here! I'll check the forum tomorrow from my cell.

It is uninstallable and SHOULD NOT BRICK your phone, but use it at your own risk, for I am not taking any responsibility. NOTE: Data writing has been altered a bit. After installing patch and rebooting, make sure you give your device a few seconds before turning off or putting to sleep after saving a file. :(

Get it HERE. [xLightWaverx.at.Modaco.XDA.i920.GPU.and.File.Access.Booster.v1.0.cab]

X

Edited March 10, 2011 by xlightwaverx

[Guest tedkord]

file system cache - 4MB

file system filter cache - 65536 sector

glyph cache - 64 kb

Weird, the default glyph cache is 4096 sectors if I remember correctly. That drops it significantly. I'll try it, though I am entering them manually, not with the tool. I am running a cooked CHT Sense 2.5.1920, and it runs pretty smooth. I'll see what changes. Thanks for the update. I'll see if I can get a release tonight for the new Sense. That glyph cache is for all graphics on the system, not just icons.

X

Edit:

Ok, I've managed to come up with a working patch for the i920. I've re-flashed my Current CHT ROM with XMenu on top of it. Straight from boot, the XMenu would lag on Sense. After the patch, it flies. Data access has increased, and over graphic speed as increased. Let me know what you folks think. Feel free to run some benchmark tests and post them here! I'll check the forum tomorrow from my cell.

It is uninstallable and SHOULD NOT BRICK your phone, but use it at your own risk, for I am not taking any responsibility. NOTE: Data writing has been altered a bit. After installing patch and rebooting, make sure you give your device a few seconds before turning off or putting to sleep after saving a file. :(

Get it HERE. [xLightWaverx.at.Modaco.XDA.i920.GPU.and.File.Access.Booster.v1.0.cab]

X

Sorry too report that this .cab made my i920 unusably slow. In either Sense or SPB.

In Sense, the weather animation took almost 20 seconds to load. Thumbing between the tabs was impossible, the bottom tabs wouldn't move, then after 5 or 10 seconds would jump to where I stopped. It took about 2-3 times as long to boot up, too.

The good news? A simple uninstall fixed everything.

[Guest Bryan W.]

Ok, I've managed to come up with a working patch for the i920. I've re-flashed my Current CHT ROM with XMenu on top of it.

He's running a different ROM I think. I don't see a rom on the front page that has CHT in it.

I want to flash and give it a go. Is it v2.0Test? I don't think so, it has a newer Sense in it.

Lol, just so you know, I stayed up late waiting.. I'm excited to see it work. :(

Edited March 10, 2011 by Bryan W.

[Guest dgyahn]

Ok, I've been running this for a couple of hours now and it does seem that some programs load faster. I'm using X-920 V1.0 with SPB Mobile Shell. Loading times were noticeably faster for both Opera and Google Maps. I'll keep testing and report back later.

[Guest xlightwaverx]

Ok, I've been running this for a couple of hours now and it does seem that some programs load faster. I'm using X-920 V1.0 with SPB Mobile Shell. Loading times were noticeably faster for both Opera and Google Maps. I'll keep testing and report back later.

Ok, I just did some thinking. I believe the results of the BoosterCab will depend on how much of a PP your current ROM has. I may be opening up too much throttle for a low PP ROMs, and in turn, it will bog the system down. Please report PP with results so that I may adjust. I may even do separate releases for each PP listed.

Here is what is contained in the Booster Cab:

REGEDIT4


[HKEY_LOCAL_MACHINE\System\GDI\GLYPHCACHE]

"limit"=dword:00002000

[HKEY_LOCAL_MACHINE\Drivers\Display\Active\Built In LCD]

"BufferMode"=dword:00000003

[HKEY_LOCAL_MACHINE\System\GWE]

"EnableAnimations"=dword:00000000


[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]

"BufferSize"=dword:00000040

"CacheDll"="diskcache.dll"

"CacheSize"=dword:00002000

"Dll"="fatfsd.dll"

"EnableCache"=dword:00000001

"EnableCache4Way"=dword:00000001

"EnableCacheWarm"=dword:00000001

"Flags"=dword:00010000

"FriendlyName"="FAT FileSystem"

"MaxCachedFileSize"=dword:00020000

"Paging"=dword:00000001

"UpdateAccess"=dword:00000000

"Util"="fatutil.dll"


[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]

"DirsToExclude"=hex(7):5c,00,6d,00,78,00,69,00,70,00,5f,00,69,00,6e,00,69,00,74,\

  00,64,00,62,00,2e,00,76,00,6f,00,6c,00,00,00,5c,00,6d,00,78,00,69,00,70,00,\

  5f,00,73,00,79,00,73,00,74,00,65,00,6d,00,2e,00,76,00,6f,00,6c,00,00,00,5c,\

  00,6d,00,78,00,69,00,70,00,5f,00,6e,00,6f,00,74,00,69,00,66,00,79,00,2e,00,\

  76,00,6f,00,6c,00,00,00,5c,00,6d,00,78,00,69,00,70,00,5f,00,6c,00,61,00,6e,\

  00,67,00,2e,00,76,00,6f,00,6c,00,00,00,5c,00,63,00,65,00,6d,00,61,00,69,00,\

  6c,00,2e,00,76,00,6f,00,6c,00,00,00,5c,00,70,00,69,00,6d,00,2e,00,76,00,6f,\

  00,6c,00,00,00,5c,00,44,00,6f,00,63,00,75,00,6d,00,65,00,6e,00,74,00,73,00,\

  20,00,61,00,6e,00,64,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,\

  00,5c,00,64,00,65,00,66,00,61,00,75,00,6c,00,74,00,5c,00,75,00,73,00,65,00,\

  72,00,2e,00,68,00,76,00,00,00,5c,00,44,00,6f,00,63,00,75,00,6d,00,65,00,6e,\

  00,74,00,73,00,20,00,61,00,6e,00,64,00,20,00,53,00,65,00,74,00,74,00,69,00,\

  6e,00,67,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,2e,00,68,00,76,\

  00,00,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,5c,00,50,00,72,00,\

  6f,00,66,00,69,00,6c,00,65,00,73,00,5c,00,67,00,75,00,65,00,73,00,74,00,5c,\

  00,54,00,65,00,6d,00,70,00,6f,00,72,00,61,00,72,00,79,00,20,00,49,00,6e,00,\

  74,00,65,00,72,00,6e,00,65,00,74,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,\

  00,00,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,5c,00,50,00,72,00,\

  6f,00,66,00,69,00,6c,00,65,00,73,00,5c,00,67,00,75,00,65,00,73,00,74,00,5c,\

  00,43,00,6f,00,6f,00,6b,00,69,00,65,00,73,00,5c,00,00,00,5c,00,57,00,69,00,\

  6e,00,64,00,6f,00,77,00,73,00,5c,00,50,00,72,00,6f,00,66,00,69,00,6c,00,65,\

  00,73,00,5c,00,67,00,75,00,65,00,73,00,74,00,5c,00,48,00,69,00,73,00,74,00,\

  6f,00,72,00,79,00,5c,00,00,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,\

  00,5c,00,41,00,63,00,74,00,69,00,76,00,65,00,73,00,79,00,6e,00,63,00,5c,00,\

  00,00,5c,00,77,00,69,00,6e,00,64,00,6f,00,77,00,73,00,5c,00,6d,00,65,00,73,\

  00,73,00,61,00,67,00,69,00,6e,00,67,00,5c,00,00,00,5c,00,54,00,65,00,6d,00,\

  70,00,5c,00,00,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,5c,00,53,\

  00,79,00,73,00,74,00,65,00,6d,00,5c,00,50,00,75,00,73,00,68,00,52,00,6f,00,\

  75,00,74,00,65,00,72,00,5c,00,63,00,6c,00,69,00,65,00,6e,00,74,00,71,00,75,\

  00,65,00,75,00,65,00,73,00,2e,00,76,00,6f,00,6c,00,00,00,00,00

"NumDirsToExclude"=dword:0000000f

"ReplStoreCacheSize"=dword:00002000

"ReplStoreDoImmaculate"=dword:00000000

"ReplStoreHostVolume"=""

"ReplStoreName"="ReplStor"

"ReplStorePath"="\\ReplStorVol"


[HKEY_LOCAL_MACHINE\System\StorageManager\PocketFS]

"BufferSize"=dword:00000040

"CacheDll"="diskcache.dll"

"CacheSize"=dword:00002000

"Dll"="PocketFS.dll"

"EnableCache"=dword:00000001

"EnableCache4Way"=dword:00000001

"EnableCacheWarm"=dword:00000001

"Flags"=dword:00010000

"FriendlyName"="Pocket File System"

"MaxCachedFileSize"=dword:00020000

"Paging"=dword:00000001

"UpdateAccess"=dword:00000000

"Util"="fatutil.dll"

[/codebox]

Please allow yourself to change these values if you wish, and see if the performance changes. I am using very basic settings, and in reality all I am doing is the following:

Adjusting Graphics Cache

Adjusting Graphics Buffer

Adjusting FATFS Data Read Rate (This should be 15MB more read-in during Benchmark Test)

Adjusting PocketFS Data Read Rate (May not hold results)

Turned on File Caching for System.

Adjusting Flags to allow Immediate Write of DATA (in PP)

I hope this helps.

X

Edited March 10, 2011 by xlightwaverx

[Guest yieldsign2]

So, I don't want to react too quickly, and will wait a few days for a real answer...

But this patch did WAY more for my phone than the overclocking did. I am now using it at 900mhz and your patch and I truly believe it is running way faster than it has for the past few days since installing the ROM. Seems just about everything is faster... I think!

I'm on AMDZero's ultralite + sense rom

[Guest tedkord]

Ok, I just did some thinking. I believe the results of the BoosterCab will depend on how much of a PP your current ROM has. I may be opening up too much throttle for a low PP ROMs, and in turn, it will bog the system down. Please report PP with results so that I may adjust. I may even do separate releases for each PP listed.

X

What PP size do you have in your ROM? I think AMD's ZeroSense come with a 16mb pool, but I dropped it to 12mb (or 12mb down to 8mb). AMD, if you're reading this, what's the PP size in your newest Ultralight+sense?

[Guest amdzero]

What PP size do you have in your ROM? I think AMD's ZeroSense come with a 16mb pool, but I dropped it to 12mb (or 12mb down to 8mb). AMD, if you're reading this, what's the PP size in your newest Ultralight+sense?

12MB PP for ultralite and ultralite+sense.

[Guest xlightwaverx]

12MB PP for ultralite and ultralite+sense.

Same here, 12PP. Not sure why it is bogging his phone down.

In my research, I have read where changes in these registry settings are only relevant in the boot.rgu file, and remain useless if changed within the system registry. Is there something done with the boot.rgu that is different than the other registry information that gets added in? I see drastic changes when I alter these settings, especially glyph*.

Any information would be greatly appreciated.

X

Edited March 11, 2011 by xlightwaverx

[Guest amdzero]

Same here, 12PP. Not sure why it is bogging his phone down.

In my research, I have read where changes in these registry settings are only relevant in the boot.rgu file, and remain useless if changed within the system registry. Is there something done with the boot.rgu that is different than the other registry information that gets added in? I see drastic changes when I alter these settings, especially glyph*.

Any information would be greatly appreciated.

X

Not to my knowledge. I messed with the glyph caches before back when ZeroSense was DC23, but I didn't see a difference so I stopped cooking them in. AFAIK all the .rgu files (except boot.rgu) are merged and put into two files: Default.hv and User.hv

Boot.hv is separate. Try cooking these settings in and see.

[Guest tedkord]

Same here, 12PP. Not sure why it is bogging his phone down.

In my research, I have read where changes in these registry settings are only relevant in the boot.rgu file, and remain useless if changed within the system registry. Is there something done with the boot.rgu that is different than the other registry information that gets added in? I see drastic changes when I alter these settings, especially glyph*.

Any information would be greatly appreciated.

X

Hey, X. I downloaded your latest v.2.0 ROM last night and loaded it into Wes's ROM tool, and it reports 16mb PP, not 12. I think I was at 8mb, 12 at most. I'm going to flash each of your's and AMD's latest and try this patch when I get the time. I also D/L'ed AMD's Ultralight+Sense test 4, and upped the PP to 16mb in it. I'll see what happens.

Oh, I forgot to add before, when I applied this patch yesterday, I also lost my Storage Card when I searched for it. When I tried to check my USB settings, it wouldn't load so I couldn't check or change them.

And, prior to installing this cab, I already had glyphe cache tweaked up, to 2mb I believe.

Edited March 11, 2011 by tedkord

[Guest ZuinigeRijder]

Everything that mentioned has been done, minus the attaching of Samsung apps to relevant shortcuts, but that would take about 15 minutes. Sense runs fast after all the tweaking is done. My only issue that I am trying to dissolve is that fact that every once in a while, when the CPU hits 100%, Sense lags a bit (usually at album or weather tabs if you stop a bit) Nothing serious, but I just want to release a Sense ROM with 0 problems, and the caching thing seemed the most relevant because we have the ability to tweak these settings, yet no one seems to have tried it yet.

We have the ability to control three important caching features that gets thrown into the PP. If Sense is more graphically intensive, then I guess we adjust those cache settings and lower the others.

Seems like a no brainer. My apologies if I want to share the information with the public instead of hording it for my next release. I figured you folks would be interested and trying different settings since you all have the how-to (pretty much) and the more of us working on it the better.

X

Maybe this link is interesting:

Sense and high CPU

At least also someone who experienced high CPU with sense, because Album was searching on the SD card........

[Guest xlightwaverx]

Maybe this link is interesting:

Sense and high CPU

At least also someone who experienced high CPU with sense, because Album was searching on the SD card........

Thanks Z, but I threw those settings in, rebooted, and it's still being a pain.

X

[Guest tedkord]

OK, it looks like something I've got installed is the problem. I upped the PP in AMD's ultralight+sense to 16mb and flashed, then the first thing I installed was your patch - everything worked fine. I don't know if it was any quicker, but it wasn't bogged. Seemed nice and smooth.

Then, I started installing all my ususal stuff, and when I was done, same thing - super slow and laggy, storage card missing, etc...Once I uninstalled the patch, back to normal. SInce it worked initially, I'm assuming it must be a conflict with something I installed.

[Guest xlightwaverx]

Same here, 12PP. Not sure why it is bogging his phone down.

In my research, I have read where changes in these registry settings are only relevant in the boot.rgu file, and remain useless if changed within the system registry. Is there something done with the boot.rgu that is different than the other registry information that gets added in? I see drastic changes when I alter these settings, especially glyph*.

Any information would be greatly appreciated.

X

K found this on a Microsoft Blog.

What about these registry keys?

Someone told me that changing the registry keys "CompactionPrio256" and "CompactionCritPrio256" fixes the problem. Unfortunately, that can't be correct. There are two things you need to know. First, in Windows CE, smaller numbers are higher priority. Compaction defaults to 255, which is the lowest possible priority. Making the number lower would increase the priority. That's the opposite of what you think you want to do.

More importantly, though, changing those registry keys doesn't do anything. It is the file system that loads and creates the registry. But the file system needs some information before the registry is loaded. So there is a very small bit of data (a "boot strap" registry) that is loaded before the user changeable registry is loaded. The real versions of these values are in that pre-registry. The ones you see are kind of like reflections of those real values. You can change them to your heart's content, but you're only changing the reflection. You're not changing the actual values the file system uses. There's no end user way to change the real values.

The good thing is we (chefs) can control what goes into that bootstrap registry (boot.rgu). Anything that is [HKEY_LOCAL_MACHINE\System\StorageManager\*] is placebo if done manually. All other settings have a real and true effect.

X

[Guest amdzero]

K found this on a Microsoft Blog.

What about these registry keys?

Someone told me that changing the registry keys "CompactionPrio256" and "CompactionCritPrio256" fixes the problem. Unfortunately, that can't be correct. There are two things you need to know. First, in Windows CE, smaller numbers are higher priority. Compaction defaults to 255, which is the lowest possible priority. Making the number lower would increase the priority. That's the opposite of what you think you want to do.

More importantly, though, changing those registry keys doesn't do anything. It is the file system that loads and creates the registry. But the file system needs some information before the registry is loaded. So there is a very small bit of data (a "boot strap" registry) that is loaded before the user changeable registry is loaded. The real versions of these values are in that pre-registry. The ones you see are kind of like reflections of those real values. You can change them to your heart's content, but you're only changing the reflection. You're not changing the actual values the file system uses. There's no end user way to change the real values.

The good thing is we (chefs) can control what goes into that bootstrap registry (boot.rgu). Anything that is [HKEY_LOCAL_MACHINE\System\StorageManager\*] is placebo if done manually. All other settings have a real and true effect.

X

Interesting...