Fix "may not display properly" error with 2003 SE - Upgrading, Modifying and Unlocking

Not sure how to do this myself, but I came across this snippet of info on how it should be done...
Windows Mobile 2003 Installation Warning
--------------------------------------------------------------------------------
Installing applications on the Windows 2003 2nd Edition results in the following warning being displayed during installation on the Pocket PC:
"The program you have installed may not display properly because it was designed for a previous version of Windows Mobile Software".
According to the Microsoft article at:
http://msdn.microsoft.com/library/d...dnwm2k3/html/screen_orientation_awareness.asp
you can prevent this warning from being displayed by adding the BuildMax key to your CEDevice section of the INF file as shown here:
[CEDevice]
VersionMin=3.00
VersionMax=4.99
BuildMax=0xE0000000
and then rebuilding the CAB files.
Click to expand...
Click to collapse
Hope this helps. I'm no expert at messing about with CAB files, but I'm going to see if I can figure this out.

I wouldn't call it an 'error'. Its actually a notification that the app you've installed wasn't designed for landscapre mode. Surely thats quite handy?
JD

not a good ideia....
iap... i don't think that's a good ideia because the warning is a good help in identifying potential conflicting apps.

I think it's nice to get rid of those msg's for cabs that you put in your extrom.
unfortenately Wince cab manager restricts Maximum os build to 0-999999

M4io said:
I think it's nice to get rid of those msg's for cabs that you put in your extrom.
unfortenately Wince cab manager restricts Maximum os build to 0-999999
Click to expand...
Click to collapse
All you need is this
[CEDevice] VersionMax value should be more than 4.21
So 999999 does not flag "may not display properly" error with 2003 SE :wink:

Shikra said:
All you need is this
[CEDevice] VersionMax value should be more than 4.21
So 999999 does not flag "may not display properly" error with 2003 SE :wink:
Click to expand...
Click to collapse
In practice I found that you have to set VersionMIN to 4.21 build 0
and VersionMax greater or equal to 4.21 build 0. I use VersionMax of 5.9 build 0 using WinCE CAB Manager v1.1.0.4 from OCP Software.

I'm a bit of a tinkerer, as many here are, so I keep playing with my extrom and hard-resetting.
I just thought it might be handy for people like me. I know there's quite a few people out there cooking their own extrom for WM2003SE.

Related

[new release] Package Tool - (first part of the new Rom Kitchen)

Package Tool is an extension to Mamaich's imgfs tools
- Main function of this tool is to build packages for a new Rom Kitchen I'm working on
- Using this tool you can also extract the following information after creating a dump folder using viewimgfs.exe:
Core OS
Value: "Windows Mobile-based Pocket PC" or "Windows Mobile-based Smartphone"
Versions
Shows the version of the packages
SYS
This is the OS version
The example shows Crossbow, CE 5.2 Build:15341 AKU 0
NET
This is the .NET Compact Framework version
OEM
This is the version of the OEM packages
The example shows only one,
but I've also seen ROMs with different versions for each OEM package.
In that case there would be multiple OEM entries
Language
The LANGID and the language of the ROM
DPI
The DPI (dots per inch) of the resources
this also depends on the resolution of the device
Value: 96 or 128 or 131 or 192
Certificates
List of all certificates used for the packages.
The OS is signed my Microsoft and the OEM packages are using a certificate from the OEM
Missing Manifests
This is a list of all packages that are missing inside the dump folder.
It is normal that there are missing packages, because the packages from the boot section (XIP) are missing... don’t worry about them
Missing Files
This lists all missing files.
Someone edited the ROM or removed files from the dump folder!
Example:
Code:
[Selected Path]
C:\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.15341.0
OEM: 2.18.0.0
NET: 2.0.6129.0
[Language]
0409 - English (United States)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM Sign 2005
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
13cb07c1-20b6-567f-dfcc-39d58b95e374.dsm
This tool is very useful for analyzing an unknown ROM, especially to extract the OS version and it will be much more useful after the release of the new ROM Kitchen.
It is also possible to execute the tool using the command line
Usage: PKGTool.exe <path to the dumped ROM>
This would just create packages, without any output
Because of this usage, you can just drag & drop the dump folder onto the tool
About the package names
The names of the packages can be extracted from the dump folders for WM6, but WM5 contains GUIDs instead of names.
To provide the ease of WM6 "Package Names" for previous (i.e. WM5) ROMs, the tool collects all package names inside map.txt and replaces the GUIDs with the actual Package Names.
You must let the tool read a WM6 dump to collect the Package Names before it can replace WM5 GUIDs.
e.g.
- Building packages from a WM5 dump creates: 1bc57b2f-c0f3-46c6-8c2a-257952317eac
- Building packages from a WM6 dump creates: OEM_Lang_0409
- Building packages from a WM5 after it was used for a WM6 ROM also creates: OEM_Lang_0409
Extending the map.txt can be disabled by: Menu - Tools - Expand Map
Download: View attachment package_tool_v1.01.zip
ROM dump converted to packages...
It is exactly the tool I'm looking for.
But... doeas it require any additional dll's? VB runtime or whatever? I have had exactly the same problem with your XIPPort. There are two version published here. One works fine (exe file 2007-01-21), second one (published with sources) produces:
message translated from polish into english:
Application can not be executed, because configuration is not valid. Problem can be resolved reinstalling application.
I've got the same message running PKGTool.exe
Sorry...yes, someone else told me the same...
I think it is cos I installed:
Microsoft Visual Studio 2005 Professional Edition - DEU Service Pack 1 (KB926606)
I will try to get that working... just give me some time
bepe said:
Sorry...yes, someone else told me the same...
I think it is cos I installed:
Microsoft Visual Studio 2005 Professional Edition - DEU Service Pack 1 (KB926606)
Click to expand...
Click to collapse
I have VS too.
Please wait - I'm downloading ENG SP1 now. I'll check if it is the reason.
I will try to get that working... just give me some time
Click to expand...
Click to collapse
Sure ))
yes, it is the reason... see:
http://community.macrovision.com/showthread.php?p=375127
bepe said:
yes, it is the reason... see:
http://community.macrovision.com/showthread.php?p=375127
Click to expand...
Click to collapse
ok. you are right
Ok, I completely removed visual studio and installed it without SP1...
After that I recreated the tool, it should be working now
I've had no problem running the tool (then again i'm running win2k ) but what i'd like to know for now is how to get the OS version/build values
tx
ok, sorry I forgot... the information about the OS might only exists in newer roms
did you have anything after
[Versions]
...
?
bepe said:
ok, sorry I forgot... the information about the OS only exists in newer roms
did you have anything after
[Versions]
...
?
Click to expand...
Click to collapse
The program worked flawlessly m8; I'm asking this to know how to get it myself , that is if you don't mind sharing it
the OS version is written into the dsm files...
open this dsm file using a hex editor:
d0b41563-b345-4444-aa15-986e7c7fff99.dsm
after 0x003C you will see something like:
05 00 01 00 D0 07 FF 39
that’s the OS version and build
Yes. It works after installing VS SP1.
Many thanks.
A Great And Very Useful Tool Bepe.
I Cannot Wait To See Your Finished Kitchen.
Cheers
Congrats Bepe!
Package Tool rules
Very nice
Thanks Bepe
I used to coock by ur previous kitchen
It was easy (even 4 beginer like me) and worked very nice
I hope this one will be more usable
1-Would u pls give us the steps?
2-Do we need to have WM6?
3- Is it for all devices, I have Himalaya?
4- Can we use it now or wait for the finished kitchen?
Sorry for to much ques.
Regards
v1.01 - Fixed a small bug in map handling
@The_hesham:
this is only the first part of the new kitchen…
I only released the tool cos it can also be used to analyze roms
to use this for a kitchen you have to wait for the new version
bepe said:
@The_hesham:
this is only the first part of the new kitchen…
I only released the tool cos it can also be used to analyze roms
to use this for a kitchen you have to wait for the new version
Click to expand...
Click to collapse
Bepe
As I understand I should have ROM already have the following
1- All *.rgu & dsm files are not deleted during cooking. But we delete *.rgu file in order to save space
2- We alraedy have ROM built by ur way mention some time ago (and I succed to cook with it)
Or I misunderstand somthing

POCKET QUICKEN for WM6

Title says it all...Landware made its .cab wm5 compatible only, I hacked it to install to any wm build. Hope some of you will find use for it, as you may know this is NOT pirated, you still need the same activation code as with WM5.
There's no WM6 APPS forum, so I figured this was the best place to post it.
I appreciate this, thanks. I'm a registered user of both the Palm and WM versions. My support inquiries fell on deaf ears.
The current version of Pocket Quicken (v2.5 Build 338a) installs and works well with WM6 without any tweaks. I have it on Cingular 8525 running CUSTEL WM VI Pro v2.5.
patmannyc said:
Title says it all...Landware made its .cab wm5 compatible only, I hacked it to install to any wm build. Hope some of you will find use for it, as you may know this is NOT pirated, you still need the same activation code as with WM5.
There's no WM6 APPS forum, so I figured this was the best place to post it.
Click to expand...
Click to collapse
thanks for the file!!
2010 POCKET QUICKEN for WM6 CAB File imperfect?
I appear to have unexpected result with your Pocket Quicken 2.1_hacked.cab
Sync starting at 8:27 AM 06/09/2010
Device helper not found. Attempting to copy from 'C:\Program Files (x86)\LandWare\Pocket Quicken 2.5 for Pocket PC\pqppc25helper.dll'
The device helper could not be copied because it was not found. Please reinstall and try again.
Communications failure - result code 3f3/2
(This probably means that the device could not be found)
Sync finished at 8:27 AM 06/09/2010
Do you use your Pocket Quicken CAB file in an environment using Quicken for Desktop pc and synchronization with Windows Mobile?

How to fake TRIN100 name for PPC software

Guys,
maybe here someone will help me.
I have company software for my HTC3600 that checks for device name.
The one that is shown as TRIN100 for Trinity for my WM6 ROM.
Maybe you are familiar with the soft that can accept request for this info and give to a program fake name like ABCXYZ?
In other words can you advise something that will allow the attempt to run software designed PARTICULARY for another WM platform?
Thanks for any advise!
First check what have you got in Start->Settings->System->About. There is Device ID Tab.
sorry for misleading
I meant
Start - Settings - Device Information - Identity - Model No.
sand2006 said:
sorry for misleading
I meant
Start - Settings - Device Information - Identity - Model No.
Click to expand...
Click to collapse
I think only try to find "TRIN100" in nbh file with hex editor and change it in some else and then flash on a device, I only in nbh file found the string... no in registry, and in provxml files!!
ervius said:
I think only try to find "TRIN100" in nbh file with hex editor and change it in some else and then flash on a device, I only in nbh file found the string... no in registry, and in provxml files!!
Click to expand...
Click to collapse
yes
that is the straight way
two possible objections
1. if name TRIN100 is used for some low level functional device will not be useful at all )
2. reflashing of this may give nothing only because TRIN100 is hardware name (i am still guessing)
so, the last option is clear for hacked nbh file
but maybe someone has seen software that catches request for this info and substitutes it with any string for calling software?

built ffmpeg dlls for windows mobile are available

In the past, I get many helps from here.
I met lots of troubles while building ffmpeg for winCE. But I'm lucky to build them out finaly. I know some ones prefer to get the dlls directly rather than build it by themselves. So I upload them here: http://www.mediafire.com/?jc4w8mex9mw
Just feel free to get them if you need it.
ok, it may sound a silly question, but what app is suposed to take benefit of that ?
RTSP
Great job! Thanks
Did you build it with rtsp support? I can 't manage opening an rtsp stream: "File not found error"
rtsp.h files are present
In your begin method, in the name you preceed sample.avi with some strange char's what are they for?
Kind regards
Wim
I have also been trying to compile this for the ARM4 platform, would it be possible for you to build for this platform (ARM4i is only for WM5/6 and Im also developing for WM2003/CE.NET 4.2)
Thanks
sorry, rstp seems not supported defaultly.
the strange chars is diretory name. You could change them to "\\Storage Card\\sample.avi" or any others you like.
wimpos said:
Great job! Thanks
Did you build it with rtsp support? I can 't manage opening an rtsp stream: "File not found error"
rtsp.h files are present
In your begin method, in the name you preceed sample.avi with some strange char's what are they for?
Kind regards
Wim
Click to expand...
Click to collapse
I haven't tried it in WM2003. Maybe it works too. please try it and tell me result.
coolsva said:
I have also been trying to compile this for the ARM4 platform, would it be possible for you to build for this platform (ARM4i is only for WM5/6 and Im also developing for WM2003/CE.NET 4.2)
Thanks
Click to expand...
Click to collapse
I am trying to use your bin ffmpeg on windows mobile 6.
when I try to call :
avcodec_find_encoder((enum CodecID)CODEC_ID_FLV1);
it's fail
those my init call:
avcodec_init();
avcodec_register_all();
av_register_all();
av_log_set_callback( ffmpeg_avcodec_log );
any idea ?
wright_hz said:
In the past, I get many helps from here.
I met lots of troubles while building ffmpeg for winCE. But I'm lucky to build them out finaly. I know some ones prefer to get the dlls directly rather than build it by themselves. So I upload them here: http://www.mediafire.com/?jc4w8mex9mw
Just feel free to get them if you need it.
Click to expand...
Click to collapse
Hi,
Been trying to use your FFMPEG.DLL but I need the network capability of FFMPEG, could you recompile with --disable-network removed from your configure?
I have built FFMPEG myself but I keep getting a green screen on any video output, sound works okay. Did you get this? If I switch to your DLL I it works but I can only open local files.
To get libavformat to build I had to change a line in configure (amongst other things) to:
network_extralibs="-lws2"
from:
network_extralibs="-lws2_32"
Thanks!
Hy,
can anybody build ffmpeg with support stream video files from network?
Thanks a lot.
Greatz
mccoffein
Hy,
is anybody out there?
I think the original Youtube app uses ffmpeg - just go to youtube from your mobile, download the cab, install and you'll find ffmpeg.dll in /program files/youtube so you can try use this one...
Hy,
thanks for your answer. I tried this. But ffplay don't work with this dll well.
If have linked in the project below but i dosent work.
I tried to link avcodec, avutil and avformat ... But there is no coming out.
Since you know that it works now i will update this thread.
I have done it. You can see it here: http://forum.xda-developers.com/showthread.php?p=3819157#post3819157
ffmpeg WinCE is now Open Source!
For more informations look at our homepage http://www.ffmpeg-wince.org ...
See you!
Error :"Not a valid Pocket PC application"
hi
I have download the file from here: http://www.mediafire.com/?jc4w8mex9mw extract it and copy the bin, ffmpeg and Sdl directory to my project for wm 6.0
and successfully build the cab file. My cab file has exe and ffmpeg.dll, SDL.dll, swscale.dll files. After installation to my htc device 6.1 device whenever I try to run
file it gives me error message "Not a valid Pocket PC application".
Do have any idea why it is giving such error message.
Thank you.
Hello, I have also downloaded the files and am building testmain.exe using visual studio 2005. The exe is building and is running within the emulator. However on a windows mobile 6.1 classic PDA I am getting the error "testmain" is not a valid Pocket PC application.
Could anyone help me discover what the problem is?
I ran dumpbin /headers on the DLLs and the exe and saw that the header values are different and am wondering could this be causing the problems I have?
Dump of file ffmpeg.dll
----------------------
FILE HEADER VALUES
1C0 machine (ARM)
4.00 operating system version
1.00 image version
3.00 subsystem version
0 Win32 version
Dump of file SDL.dll
----------------------
FILE HEADER VALUES
1C2 machine (Thumb)
4.00 operating system version
0.00 image version
4.10 subsystem version
0 Win32 version
Dump of file swscale.dll
----------------------
FILE HEADER VALUES
1C0 machine (ARM)
4.00 operating system version
1.00 image version
3.00 subsystem version
0 Win32 version
Dump of file testmain.exe
----------------------
FILE HEADER VALUES
1C2 machine (Thumb)
5.01 operating system version
0.00 image version
5.01 subsystem version
0 Win32 version
Thanks,
Menelaos

Transcriber Missing in WM6.1 Classic

hai guys, I noticed after using it a few weeks that I'm missing the Transcriber feature as input option in my WM6.1 Classic, I'm using CE OS 5.2.2021 Build 19199.1.0.0
I searched around here and tried two different Transcriber.Cab's from this site and from www.4winmobile.com bot do not work (Transcriber still doesn't show up; and WM6.1 installer tells me "it may not work, as program is designed for an older version"). No registry entries either (I searched for "transcriber" keyword across entire registry).
Can anyone pretty-please help me out on this one ?
I'm using a hx2495b iPAQ and got the english ROM from a (Korean?) website, which was linked from here (somewhere in a "hx2000"-ROMflashing thread. Everything else seem to work fine.
thx
@
For some HTC models post #23 in this thread provides a solution:
http://forum.xda-developers.com/showthread.php?t=406136&page=3
maybe it also works for you...
KnOeFz said:
For some HTC models post #23 in this thread provides a solution:
http://forum.xda-developers.com/showthread.php?t=406136&page=3
maybe it also works for you...
Click to expand...
Click to collapse
Nope doesnt work, if i read it correctly it's for BLOCK RECOGNIZER and not for TRANSCRIBER - i looked into the CAB-file, and it's pointing to a MSIMNL.DLL (for Netherlands InputModule) so i did it manually to MSIM.DLL (which is 120kbyte in size) - which according to the registry is/was set correctly, but not even in the registry was a TRANSCRIBER pointer/entry. After installing your suggested CAB i got TWO BLOCK RECOGNIZER modules/choices
It seems to me that both relevant DLL's are there (MSIM.DLL w. 120kbyte) and a MSIM.96.DLL (67kbytes in size), just missing the proper registry pointers to "activate" it.
anyone more suggestions?
cheers
@
The download cab under "Deleted from ROM (1...." at
http://forum.xda-developers.com/showthread.php?t=313081
works on my Loox N560 WM6.1. And it looks the full monty!
well, it's getting closer
it shows at least up now in the input selection pull-down menu, but it's kinda "defective" the area is not completely drawn, and it's missing entries. My windows-Installer tells me that this too was "designed for an older version of windows Mobile"
again, I'm using WM6.1 Classic, CE OS 5.2.2021 Build 19199.1.0.0 and in soft-boot the boot ROM reads as version # 5.20.01.C ENG
i got my ROM from here http://www.pdaviet.net/showthread.php?t=23740&page=2
not sure if that helps further
cheers
@
hm, now i got even a weirder effect.
i got myself Calligrapher v8.7 Build 8.379.0810
but the wierd thing is, it installs nicely, but i cannot start it up. Only the Config Manager and the PenCommander start up, but the WriteAnywhere or WritePad will not start, I cant even put in my serial number.
I noticed that at installation it has an option to uninstall the original WM 6.1 TRANSCRIBER (which I'm missing) - that option had a check-mark, but was "grayed out"/disabled.
anyone have an idea ? I'm getting desperate
cheers
@
I'm having the same problem as atlana, I installed Calligrapher 8.7 but cannot get it to launch. Calligrapher support suggested I delete some plug-ins from my Today screen, but even with NO plug-ins I could not launch Calligrapher.
Has anyone come up with a fix? thanks

Categories

Resources