[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] -888-:
Thank you everyone for mirrors, your kind words and all reports.

Hopefully ther are no bugs and 4.888 will be good (albeit 'unofficial') end of the line for "ROMeOS R.I.P." series ;)

Oh I know now what you mean!

The Alarm2 sound right after main storage is cleared (only after hard reset).

That is actually WinMo feature AFAIK, a notification that clearing is done and device is waiting for you to proceed. If thats the sound youre talking about, well it is not exactly a bug, it has been like that in every WinMo as far as I can remember.

It can be disabled easily in registry (and some operators do that) but unfortunately it really has to be cooked-in, no CAB can "fix it" for you, sorry.

Hang.tuah probably disabled that in 4.6.0 per your request, but because of the unsolved mysterious A/S sync bug in 4.6.0 I have intentionally avoided any settings from there thus I haven't notice this change (because I think A/S bug of 4.6.0 is probably "hidden" just there right in the settings and not in any file itself, since so many people were trying to find it and no one have spotted any corrupted or wrong files).

/edit2

you said after Soft Reset?

Thats strange. I did many soft resets, I didnt have any sounds at all (except for vibrator noise) with or without notifications on/off (on a plain ROM, nothing added)

Are you using the correct Sept.22 ROM? I remember in earlier "work version" (ie the one I mistakenly uploaded first) I was going to add Vista start up and shut down sounds, but I ditched that idea (wav files too big, not everyone would want it, so I moved it to eXt.Pack).

Lot of Luck and Fortune to You

(just my loose translation of 888 meaning)

enjoy!

YW :)

I apologize for lack of other links, I tried to upload to rapidshare but it almost never works from my work IP.

Thanks to ndn715 there is rapidshare mirror now (thank you!)

For the "normal use" there isn't anything visually different from what you've seen in all ROMeOs 4.x.x, I didn't want to change anything much (because it was supposed to be ROMeOS not eOS) so any visual changes I did are just "touch ups" here and there to make it more eye-pleasant or consistant - that is in my opinion, but of course we all have different standards of 'beauty' (ie I replaced the designed-by-color-blind-man grey highlight color of HTC's default kaiser theme with more visible and IMHO more pleasant green highlight color; just things like that, I can't even remember all of them because I tinker with almost everything all the time). You still have the same Kaiser / Diamond choice of "skinning" retained from/as in 4.6.0, same layouts (folders, icons) and stuff like that is all hang.tuah's ROMeOS, any thing else "under the hood".

I admit I tested only M2D on sakajati's first manila ROM, haven't much time to look into it yet. It certainly is very eye-pleasing.

My problem with it was right away when installed MSVC and it crapped out (constantly actually). To me MSVC itself is somewhat "ultimate test" (I have to have working MSVC).

But yes, you're right about spb's and others. I don't use HTC's own Home either (just to see the large clock I have PDC for that, and all other features of Home... well, lets just say I do have windows at home, so I can see what is the weather outside much faster than I can select Weather on HTC Home ;))

Kaiser is great, but it would be better with twice as much RAM and maybe faster CPU too (then we wouldn't have had this conversation at all ;) )

PagePool: dynamic vs set-size

Some reading links HERE

This is not my opinion, but just so you know:

The major consensus is that the set-size pp is more stable.

The major consensus is that the dynamic pp is faster or "smoother" overall.

But some people say it is the other way around, the dynamic pp is more stable and set-size is "smoother".

The deafult kaiser pp (as set by HTC on shipped ROMs) is 6 MB.

Many people deem 6MB to be too small (majority seem to favor 12-16 MB pp).

With my bad english:

The difference is that with dynamic pp you allow Windows to manage it and use as much RAM as it wants (out of the total available RAM).

With set-size pp Windows "gets" only whatever size you gave it.

Larger pagepools are prone to problems similar to what you may understand better as equivalent to fragmented harddisks, because some programs don't unload properly their stuff from memory after they are closed. But since they are large, Windoze can load more there, while on a smaller pp when it gets fragmented it will be only that small much.

Page Pool supposed to help with this unloaded stuff, but when itself gets fragmented it may cause overall performance slow-down (specially when it is large, less with smaller ones).

So for example if you have dynamic pp (in theory the best solutions) and at some moment Windows itself inflates it to some larger size (because it needed it at that moment), and the apps after they were closed did not unload everything properly, you will still be stuck with this fragmented *and* yet large size page pool, hampering your device's performance until you restart Windoze - which is the same as it would happen in this cenario with any "set-size" larger page pool of 16, 24 or 32 MB (even though you have dynamic pp). In some odd case scenario the dynamic pp can even gobble-up your entire RAM too, whilst it wouldn't happen with set-size pp (again - just in theory).

But if you use small "set-size" pp (ie 6MB) it also can happened that it is just not enough for whatever Windoze needed at some moment, and your app may croak (as MSVC like to do in that case) or it maybe use the rest of the RAM; in that scenario the stuff that may be leftover there (the unloaded program's DLLs and such) will still affect your device's performance too. There is of course much more to it, ie execute-in-place etc, Im just trying to make it simple (so don't quote me on it pls :) ).

By "the unloaded stuff" I mean the memory addresses that aren't freed after use, physically occupied by data that is obsolete or no longer needed - but still there.

I don't know is my explanation any proper, but

my point is that there is no golden solution

.

It all depends on the circumstances at the given moment.

Feel free to correct me, Im just a n00b :)