Too many startup items

[zman818]

As I add startup items, I often start slamming into the following...

Cannot open '____'. A critical component is either missing or cannot start because program memory is unavailable. <snip>

Soft resets clear it, though oftentimes I'll have to do it repeatedly to get a completely clean boot (if I don't feel like starting the skipped app manually). Different apps get caught up in it at different times. For example, it might be s2u2 on one boot and aebuttonplus on the next. The more startup apps I add, the more often it seems to happen... sometimes to multiple apps in a boot.

Everything is on device storage, so it has nothing to do with the availability of storage card memory.

Any thoughts on specific cause and more importantly, a solution that doesn't involve trimming the # of startup apps? TIA.

[CPTBeaker]

Well, no solution to offer, but confirmation that someone else is getting this also. It's pretty annoying. I get the message and after the boot is complete, it seems like there is plenty of RAM free. I don't understand why sometimes I can boot without any issues and other times I get the error(s).

I'm running CC20 and Adrynalyne's 6.1 v 1.6 ROM

[zman818]

I think it's a timing issue of some sort, and sometimes WM zigs just a little slower and throws off the zag.

I may sit down one of these days and write a mortscript to handle all my startup apps in a more calm, staged (ie, timed) approach (similar to Startup Delayer for Windows). Depending on how sustainable it is I may throw it out here for public consumption.

[CPTBeaker]

I wonder what determines the startup order? Are the items in the startup folder loaded in alphabetical order? If so, I wonder if renaming the items, adding prefixes to force them into a better order (i.e. the smaller items load first, then the bigger ones after, or some other combination...).

Ex.

A_iamsmallloadmefirst.lnk
B_imgoingtoloadnext.lnk
C_iwanttoloadthird.lnk


etc...


Just a thought...

[zman818]

There is a sequence number associated with startup items. Not entirely sure where it's stored (prob the registry), but you can edit it with SKTools.

In the same vein, there is also a "delay between startup items" (also editable with SKTools). The default is 5ms. I changed it to 100ms, and so far (3 boots) I haven't seen the issue re-appear. HTH.

[Adrynalyne]

Welcome to Windows Mobile. This has been an ongoing issue for a while. Sometimes it happens more frequently than others.

[pallen]

Yep, I get this too. I have done a soft reset three times in a row and had three different processes fail to start, then reset a 4th time and everything is good. Its little things like this that Windows Mobile the reputation of being "buggy".