[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] -888-:
When you flashed the ROM you should not install anything else with UC yet, but complete WinMo setup, then hard reset it and then use UC to install the apps.

It looks like this from what youre describing, I had the same problem when I didn't do it that way. .

Also the ROM reboots twice when you just flashed it after different ROM (I know it sounds weird but I observed it when flash it after eOS 4.888, HyperDragon ROM and when I flash it after Garmin's ROM too). When I flash it after itself it didn't do that. But that might be SPL-version related too, I have to repeat it again with different SPL to make sure

Another thing is that sometimes UC may look like it froze while it didn't, its just installing huge app like CardWorld or such, specially when installing from a class 2 SD cards. The installation time I listed in the ReadMes are for class 4 card, so that's another factor, and I know that for a fact because at first I was testing from my old slow 2GB card (probably "class 1" or less if there was one) and after 20+ minutes "Featured" setup was somewhere little more than in the half and I actually thought it froze too, while when I copied the xUC folder and SDconfig to my 8GB class 4 card the whole "Featured" UC process was completed in 15+min. So that might look like UC froze while it actually is still working (installing)and there are few really long 'gaps' that look like it stopped or froze while it is really working hard :)

I don't say it is not the ROM's problem, it might as well be some flaw I haven't notice before, after all FiRe has some updated (thus different) Windows files from 20755 build and its not always that Msoft's newest is always better, sometimes Msoft does make it worse instead of better with newer versions. So it may be related too, however there are no known special like this or anyhow specific to this build problems with 20755 (at least I haven't read anything about it yet), and also if that would be the case then we all should have been observing the same problem from begining, while I can assure you it worked fine during my tests and even now before I typed this reply I hard reset and run "Featured" UC fine without any problems on my Kaiser. So this tells me it must be something else IMHO and thats why I mentioned at the begining about additional *hard resetting* after flashing the ROM and initial (first) setup, without UC. Have you did it this way? Or did you just go with UC setup right after flashing this ROM? Please give me all the details, let's figure it out :)

edit/ when there is setup error UC would never try installing same app again, it just stops installing anything at all at that moment and once you acknowledge the error (if displayed) it just ends and go for reset, or it just do nothing and appear frozen (actually the error is display but is hidden underneath), that's all - so it is impossible to happen as described if it is just UC error - you shouldn't have googlemaps appear installing again for the second time, hmm. Very strange.

I have just installed and uninstalled ubook two times without any problems, and I tested it and it works fine too (but BTW I will be removing this particular uBook's cab from eXtPacks anyways, because I just noticed something I didn't realize before).

What else possibly be the difference between your and my files - corrupted ext.pack rar perhaps? Please redownload it and install uBook again and let us know.

Let me ask you this: has the Transcriber & Block recognizer worked fine for you in previous version of eOS4.888.F or September eOS4.888? Because if it did then that would tell us the problem occurs due to the WinMo files from 20755 build in eOS4.888.FiRe (I don't use them at all, and I must admit I have never test transcriber or recognizers in any ROM, I actually forgot those things were there in WinMo at all :o )

@ tugas2khas remarks Dwazzue

any news?