CDMA Touch Pro XIPs 20764 20771 20954 21015 21018 21028 21032 21109 - Page 27

FormerPalmOS · #**261** (**permalink**) 03-18-2009, 11:51 PM

Just downloaded your 21028 kitchen. Not sure when I'll cook - lotta stuff on the Honey Do list...

Larik · #**262** (**permalink**) 03-18-2009, 11:59 PM

Quote:

Originally Posted by FormerPalmOS

OK - what you posted is "the usual" result from XIPPorterEx with the remove CacheFilt.dll and remove Mencfilt.dll checkbox enabled, plus the other usual modules removed. No other changes. In other words, it's a slightly size-reduced XIP but no tweaks. If the ONLY difference between a working ROM for you and non-working is this, then there is obviously some dependency.

I haven't cooked with 21028 yet. lllboredlll has and unless he hasn't bothered to report it, I don't think he's had the problem you are having. Which implies that the dependency could also involve the SYS build plus the XIP.

So anyone that's used this XIP - please report a) what SYS you cooked with (version AND source) and b) if it's working fine or if you are seeing strange issues.

I made exactly the same changes to 20771 and have been running for a week now with zero strangeness, nothing wierd.

One more question - are you using the default .VM and .SYS, or are you using the modified ones I included in the XIP .ZIP file? Where in the build process do you do G'Reloc.exe and what exactly is the command line? Have you dumped your ROM and looked at the virtual memory map (imgfstodump.exe creates memorymap.txt - can be useful to see if there is an overlap in any of your modules with the XIP module VM space. Just another thought. This feels like a filesystem bug though...

I was using your .VM and .SYS. and ROM with both: Bored and Scott's kitchens.
Thanks!!!
Larik

**xweaponx** · #**263** (**permalink**) 03-19-2009, 01:21 AM

FPOS,

Have you plans of constructing a 21038 with your secret ingredients?

jucytec · #**264** (**permalink**) 03-19-2009, 01:27 AM

If i recall from ConFLipper 38 was fake...

I did cook with it tho... using 28 XIP,.. it was the same speed

**lllboredlll** · #**265** (**permalink**) 03-19-2009, 01:29 AM

Quote:

Originally Posted by xweaponx

FPOS,

Have you plans of constructing a 21038 with your secret ingredients?

If you dump his 21028 xip and patch the dsm it will show as 21038

FormerPalmOS · #**266** (**permalink**) 03-19-2009, 08:40 AM

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).

EDIT - Balance of post removed, attachment moved to OP.

jucytec · #**267** (**permalink**) 03-19-2009, 01:39 PM

Quote:

Originally Posted by FormerPalmOS

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.

Tried the REG, it did not work

Trying the 32 SYS...

I'm on 21028 SYS

jucytec · #**268** (**permalink**) 03-19-2009, 02:55 PM

Interesting...

The 21032 XIP still came back with the flashing error, but I only had 1 icon that did it. i erased that icon and all is good...

What the heck is causing this? Let me try 21028

FormerPalmOS · #**269** (**permalink**) 03-19-2009, 03:19 PM

I think there is something screwey going on with the filesystem. Gut feel is that the File Explorer dialog window (what you see when you click Start --> Programs) thinks that the file entry has changed. That would explain why all links added after boot flicker, but not why just one does - unless something in 21032 is better.

Did you try 21032 PLUS the regedit, or 21032 by itself?

Also check the attributes of all mxip*.*, *.dsm, *.rgu files in your dump directory just before imgfsfromdump.exe in the kitchen. If the aforementioned files aren't all hidden, system and read-only it can cause wierdness that is really tough to explain.

I'm running out of ideas - but thanks for your patience and testing and reporting...

jucytec · #**270** (**permalink**) 03-19-2009, 05:19 PM

Quote:

Originally Posted by FormerPalmOS

I think there is something screwey going on with the filesystem. Gut feel is that the File Explorer dialog window (what you see when you click Start --> Programs) thinks that the file entry has changed. That would explain why all links added after boot flicker, but not why just one does - unless something in 21032 is better.

Did you try 21032 PLUS the regedit, or 21032 by itself?

Also check the attributes of all mxip*.*, *.dsm, *.rgu files in your dump directory just before imgfsfromdump.exe in the kitchen. If the aforementioned files aren't all hidden, system and read-only it can cause wierdness that is really tough to explain.

I'm running out of ideas - but thanks for your patience and testing and reporting...

This happens to any icons that are entered AFTER the initial flash...

Whats more...

Any icons that are entered into the Start... Settings folder will LOCKUP your device...

no2chem FastCharge, Touch Response are two programs that enter a shortcut in the settings menu...

when these programs are installed it locks up the device in SYS/XIP 21028/21032/21038

Same configuration is rock solid on 21018 and lower...

Removing the icons work fine.