Originally Posted by FormerPalmOS (Post 782501)

No plans for 21038 given Conflipper's comments.

On the 21028 / 20132 flashing icons issues, I did a compare between 21028 XIP and 21032 XIP and noticed the following things:

1) The MSXIPKernel manifest (.dsm) is different, obviously in version number but also the embedded signature is different.

2) MSPART.DLL, PM.DLL and REGENUM.DLL have changed. No other modules have changed.

Finally, I don't think it matters, but just in case, I did have to remove the HTC signature in the OEMXIPKernel manifest. I've restored that here (had to give up 16K of program memory).

So 1) try the attached 21032 XIP and see if it works better then 2) try the 21028A XIP. If 21032 XIP solves the problem then the problem is in one of the changed modules. If 21028A solves the problem then it's the OEMXIPKernel manifest.

Also, can someone with the flicker problem send me a dump of your registry for the HKLM\System\StorageManager key? Not the whole reg, just that key. I have one other idea for what may be causing this and why I don't see it. If someone wants to give this a try, grab the attached ffff.....zip and get it into your kitchen somehow. It fills in some gaps in the file system settings, removes some useless crap in the registry, and some other useful things (Bluetooth connection attempt notification).

In order, I'd try the registry edits below first (you can try just importing it, but I suspect it must be cooked in), then the XIP8A (with 21028 then the other XIP.

Once this is nailed down (if any of this solves the problem) I'll update the OP .

If none of this works, here's my last suggestion. If it happens in 21032 but not 21028 (or vice-versa) do a diff of the two SYS and tell me what changed. This will be a pain in the butt, since you have to actually look at the SYS module DLLs to see if it's just a few address pointers that changed here and there because of G'Reloc.exe, or if the code base changed.

Originally Posted by FormerPalmOS (Post 789617)

Awesome dude - thanks again for your help. Someone else had tried the .rgu and said it did NOT fix the problem. I guess I should add a note to the start of the thread to include the necessary reg edits.

Quick question - were the blinking app icons installed to your device or SD card by any chance?

Originally Posted by FormerPalmOS (Post 782501)

No plans for 21038 given Conflipper's comments.

On the 21028 / 20132 flashing icons issues, I did a compare between 21028 XIP and 21032 XIP and noticed the following things:

1) The MSXIPKernel manifest (.dsm) is different, obviously in version number but also the embedded signature is different.

2) MSPART.DLL, PM.DLL and REGENUM.DLL have changed. No other modules have changed.

Finally, I don't think it matters, but just in case, I did have to remove the HTC signature in the OEMXIPKernel manifest. I've restored that here (had to give up 16K of program memory).

So 1) try the attached 21032 XIP and see if it works better then 2) try the 21028A XIP. If 21032 XIP solves the problem then the problem is in one of the changed modules. If 21028A solves the problem then it's the OEMXIPKernel manifest.

Also, can someone with the flicker problem send me a dump of your registry for the HKLM\System\StorageManager key? Not the whole reg, just that key. I have one other idea for what may be causing this and why I don't see it. If someone wants to give this a try, grab the attached ffff.....zip and get it into your kitchen somehow. It fills in some gaps in the file system settings, removes some useless crap in the registry, and some other useful things (Bluetooth connection attempt notification).

In order, I'd try the registry edits below first (you can try just importing it, but I suspect it must be cooked in), then the XIP8A (with 21028 then the other XIP.

Once this is nailed down (if any of this solves the problem) I'll update the OP .

If none of this works, here's my last suggestion. If it happens in 21032 but not 21028 (or vice-versa) do a diff of the two SYS and tell me what changed. This will be a pain in the butt, since you have to actually look at the SYS module DLLs to see if it's just a few address pointers that changed here and there because of G'Reloc.exe, or if the code base changed.