This might be a stupid question but i´m a nOOb, I have a QTEK S9100 and I have some software that I want to install, my problem is that on some software it says that it it for MIPS, ARM or SH devices.
Can ne1 explain what this is and also explain to me wich QTEK S9100 is
ARM, MIPS or SH
thank you for your help
These are types of processor, though I don't know if MIPS and SH are still around.
ARM will work on the Wizard.
Lewis
Thank you very much for the quick answer
is there a way to download a cab file or install direct from a http://url ? tried in internet explorer but couldn't find a way to do it
only if the site you are looking at has cab files as a choice to download.
And dont't forget, some of apps are not working with WM5 yet.
Hi all..! I have a euro niki 100, and just upgraded to Windows mobile 6.1 using the official rom update from HTC.. Speeds etc is better with 6.1..
However, i've encountered one minor issue with this upgrade.. It ships with Esmertec Jbed. And I guess this particular build doesn't play nice with Opera Mini.
The included build (i guess in the rom upgrade) is build 20080131. Opera Mini does work, however, the workarounds for getting it to work as signed (without the annoying nag screens) don't seem to work for me anymore. I think the old Java Vm version is the culprit. Is this version update-able..? I mean, i can't remove the current version using add/remove programs on the device.. Or is there a better Java VM out there, which would allow me to run, say Nokia s60 games aswell..? (read something about that aswell..) Some pointers please..? TIA
121 views and no reply whatsoever..? Wow..
having similar issue but not able to see any solution
Well, at least i have it fixed with the Esmertec jbed version that's in the default wm 6.1 update.
The workaround thats posted everywhere (edit the selector.utf file) doesn't seem to work (anymore?) because another file is missing (either in WM6.1 or in the newer version of Opera Mini, i don't know, would guess the latter..)
Anways, the solution to this "problem" is almost the same as in this thread: http://forum.xda-developers.com/showthread.php?t=380504
In short; edit the selector.utf file as mentioned in the thread.. You should be able to find it in the \Windows\appdb directory on your device. Then, and this differs from the thread mentioned before, don't create or look for a JavaDb folder in your \Application Data directory, cause it doesn't exist. Instead, place the posted policy.utf file in the \Windows\appdb directory for the selector.utf fix to work. Kinda stupid i didn't try this before, but the search on XDA din't help me out there either so..
Now to see how Java games run on this Esmertec Jbed client..
Edit: Credits to truggl for posting his fix and uploading the necessary files..
This is the official cab file of Flash Lite 3.1 for WM6 from Adobe, available as distributable player for Developers.
Note to Mods: Please delete/close this thread if it is a repost.
Finally, the official version without bugs.
All my flash 7 app's work fine with this!
Thank you.
twolf said:
Finally, the official version without bugs.
All my flash 7 app's work fine with this!
Thank you.
Click to expand...
Click to collapse
Does this mean that I can uninstall FP7 and rely on only this? That would be great!!!
Yes, you can. I still didnt found a way to use it on opera or IE, but its working flawlessly on all my apps.
OK, first incompatibility:
I installed WM6.5 on my BA and FEwidgetslite bombs out. Works fine with the OPAL version of 3.1.
Not sure how fewidgets work, but if its similar to throttlehtml it should be as simple as editing the html file it reads to have this code.
(Change the name TESTE and the size 550x400...)
motisu said:
OK, first incompatibility:
I installed WM6.5 on my BA and FEwidgetslite bombs out. Works fine with the OPAL version of 3.1.
Click to expand...
Click to collapse
OTOH, I installed this one and installed the old version of FEwidgets (which needed FP7) and it works GREAT!!
twolf said:
Not sure how fewidgets work, but if its similar to throttlehtml it should be as simple as editing the html file it reads to have this code.
(Change the name TESTE and the size 550x400...)
Click to expand...
Click to collapse
Sorry but I didn'tt understand what I have to change the name to and where it should go. Also, why 550X400, the BA is standard QVGA 320X240?
No, I exported that html code from Flash CS4, its the standart code to read flash lite 3 (not sure youll need all that, maybe just the OBJECT area).
You'll "just" need to change all that has the name TESTE.swf to (not sure whats the name you need) FEwidget.swf(?) with the fewidget size 240x295(?) instead of the 550x400 that my html had.
what do i need to do to make this work with opera? do i need to setup anything else other than installing the .cab file?
pcrot said:
what do i need to do to make this work with opera? do i need to setup anything else other than installing the .cab file?
Click to expand...
Click to collapse
hi, inspecting the CAB I could not find a COM control on any of the dlls, do you know if this release has the ActiveX necesary for IE/opera? or is it just the player?
thanks a lot.
Nico.
never mind, I got my answer...
Not a plugin
nicodega said:
hi, inspecting the CAB I could not find a COM control on any of the dlls, do you know if this release has the ActiveX necesary for IE/opera? or is it just the player?
thanks a lot.
Nico.
Click to expand...
Click to collapse
Hi all
According to the Adobe website this distributable packages is in fact a stand alone player, not a web browser plugin. Can anybody confirm this? I can't get it to work with Opera the way the previous versions did.
Cheers
andrew-in-woking
This is the standalone player only, the official wordings state it all (see below). I got it from here: http://labs.adobe.com/technologies/distributableplayer/
Flash Lite 3.1 Distributable Player.
Flash Lite 3.1 includes the same features as Flash Lite 3.0, such as support for Flash Player compatible video, with some additional enhancements including improved security model for SWF file access. The solution delivers a standalone player for applications, without affecting the Flash Lite browser plug-in or pre-installed standalone player, if present.
The player posted in this thread does not work when you tap the .exe located in \Storage Card\program files\Adobe\FlashLite. You have to use a program to associate .swf with the .exe, then it will open, however from what I've tried so far..everything has been very slow..
I'm disappointed because there is no zoom feature, or quality toggle..there are less options than the previous flash lites.
mikeeey said:
The player posted in this thread does not work when you tap the .exe located in \Storage Card\program files\Adobe\FlashLite. You have to use a program to associate .swf with the .exe, then it will open, however from what I've tried so far..everything has been very slow..
I'm disappointed because there is no zoom feature, or quality toggle..there are less options than the previous flash lites.
Click to expand...
Click to collapse
The Adobe Mobile Packager is also available on this page http://labs.adobe.com/downloads/distributableplayer.html so you can take the .swf and package it yourself to run in Flash Lite 3.1 ...
Thanks, I was hoping for something like that for a long time, but...
Tried it, hated it...
But hey, at least it exists now...
what does "max number of subdirectories exceeded" mean? When I try to compile a flash game I get this error..
I've tried to get this game to work, dice wars:
http://www.gamedesign.jp/flash/dice/dice.html
he is trying to compact all the files and folders he "sees" into a cab file, you need to separate your project with only the files you want in a different folder for him to pack...
I really didnt liked that swf>exe builder...
I'd advice this one:
http://www.bryht.com/flashapp.htm
Its old and only works for qvga/vga, but its so much better to use...
twolf said:
he is trying to compact all the files and folders he "sees" into a cab file, you need to separate your project with only the files you want in a different folder for him to pack...
I really didnt liked that swf>exe builder...
I'd advice this one:
http://www.bryht.com/flashapp.htm
Its old and only works for qvga/vga, but its so much better to use...
Click to expand...
Click to collapse
thanks twolf, it worked!, well, compiling it did, but flash 3.1 did not know how to handle the .swf. it says "Error: ActionScript Stuck"
Atleast I can try with other flash games and movies.
I check out the other flash packager as well.
http://www.nuerom.com/BlogEngine/post/2009/05/17/nueSpinLockPatcher.aspx
http://www.nuerom.com/BlogEngine/post/2009/05/22/nueSpinLockPatcher-11.aspx
nueSpinLockPatcher is a tool to patch out the SWP containing procedures in HTC code – inside both drivers and the kernel. Its a tool designed for ROM cooks and developers – see the download page for links and information.
SWP is a deprecated opcode in armv6 that decreases performance due to the way it locks the bus.
1.1 includes more patching and bugfixes.
good job!!!!!another amazing work!!!!will try and report.
Always great work just do not understand what one would do with this even though I cook my own roms
Hey no2chem ur download on ur site is broken, it redirects on itself :\.
jug6ernaut said:
Hey no2chem ur download on ur site is broken, it redirects on itself :\.
Click to expand...
Click to collapse
I was about to post that. I can only download from IE on the phone.
IE on my desktop is broke, No go with Firefox or Chrome.
I think it's time no2chem put his hotlink protector out to pasture and find a better one. It can be done pretty effectively with .htaccess...
Too bad the OMAP850 isn't an ARM6 core. :'(
Mutiny32 said:
I think it's time no2chem put his hotlink protector out to pasture and find a better one. It can be done pretty effectively with .htaccess...
Click to expand...
Click to collapse
exactly what is wrong with it? version 1.0 was a broken link because I had deleted the file off the server and.. I didn't update it. Did you experience problems with any other files?? and .htaccess isn't really an option, because the files aren't where you _think_ they are.
Am I right that this patcher will not work for a HTC Wizard as it has a Ti OMAP 850 wich supports only the ARMv5 instruction set?
I haven't cooked a patched ROM but I tried to use the patcher. It didn't find anything to patch in the OEMDrivers folder but patched some stuff in nk.exe s000.
Will this patched ROM work with my HTC Wizard?
Hi from EugeniaDevelopment chef,
This project is intended for porting the Windows Embedded CE 6.0 Kernel to Windows Mobile devices, based on Qualcomm MSM chipsets.
As you know, the MSM7 series chipsets are based on ARM11 CPUs.
Or more detailed... they're based on ARM1136EJ-S CPU!
Then... WHY this post?!?
I'd like to share with all the community my hard work for compiling the CE6 kernel for ARM11 devices, supporting ARMv6 instruction set.
The CE6 kernel is based on another kernel architecture, making the devices running it SO FAST...
I would like to say that this kernel IS compatible with current Windows Mobile builds, at least 6.5/6.5.x builds, as 6.5.x builds are alphas of Windows Mobile 7, based on CE6 kernel.
Infact, WM7 will be based on CE6 instead of current WM6.1/6.5/6.5.x that are all based on CE5.2 kernel codebase.
Now, I need some help to cook it in our ROMs because the MSXIPKernel i've generated remoduling all dlls is larger than old 5.2 XIP.
There are even some differencies from 5.2 XIP!
NK.exe is differently used: the base modules of MSXIPKernel are different and device.exe and filesys.exe now are both .dll due to the different architecture of the kernel that now integrates all in an unique process, both files in kernel mode and not in userspace anymore!
So, I've tried myself to port it to my ROMs before posting it there but with no luck.
I'm using the last ErviusVisualKitchen that includes bepe's platformrebuilder.exe... that CRASHES everytime I try to build the ROM with ALL dlls and modules of CE6 kernel.
If I integrate only coredll.dll module the kitchen goes on and builds the XIP and the ROM, but it won't boot because the new coredll looks for device and filesys dlls that in 5.2 are executables.
If I try to integrate new dll modules (device and filesys), the platformrebuilder will crash.
So, I'm asking for your help to making this fabulous project to continue and to make it working for having the FASTEST devices ever!
Here are the dlls, not remoduled with ErviusKitchen.
I decided to give you the original binaries because maybe ErviusKitchen won't remodule them correctly, making platformrebuilder to crash.
Ouh, and.. this kernel will work on all devices that has got Qualcomm MSM7xxx series chipsets..
For example: HTC Touch Diamond, TouchHD, TouchPro, Kaiser, Diamond2, TouchPro2... and more, more devices....
I hope I can get all of your help.
Anyway, you can download it here:
CE 6.0R2 Kernel
...If you want, I can post the entire ROM built with Platform Builder (not working on our HTC devices, as it's build for generic ARM1136EJ-S CPU).
NOTE: As for the device-specific drivers, we have OEMXIPKernel
Thank you all
How to use ?
Try sending a private msg to bepe, see if he can adjust his PRB to account for your kernel.
Okay, thank you
...if anyone has other ideas, write
this is probably the most impotant project on this forum.
Mods please make a sticky.
Converting to module didn't help.
Imageinfo.bin manipulation didn't work also.
Did you try porting it the old way? (XIPPORT)
If THAT doesn't work, try PMing bepe.
Tried to integrate this kernel into my ROM...
I copyed all the .dll's into MSXIPKERNEL
ROM - created without any ERRORS
Now i gonna try it...
Whoops... My mistake - i builded 21054 kernel without errors... 23049 - Platformbuilder error...
OMG stick this NOW, this is ground breaking stuff, da_g,nue2chem,bepe you should all take a look at this thread OMG!!!!
I think you may be a little confused?
It appears you have posted the MSXIPKernel package compiled from Embedded CE 6.0, compiled for ARM.
These CE 6.0 Binaries are not compatbile with CE 5.2, so attempting to use them in a Windows Mobile 6.x ROM as-is will not work. You state that "NOTE: As for the device-specific drivers, we have OEMXIPKernel" - do you mean the existing OEMXIPKernel, compiled against WM 6/CE5.2, if so this will not work at all with CE 6. I assume when you say "Ouh, and.. this kernel will work on all devices that has got Qualcomm MSM7xxx series chipsets.." you mean because it is compiled against ARMv6?
Also, you have posted several incorrect informations,
WM 7 is not based on CE6, but CE7.
WM 6.5.x is not in any way an alpha build of WM7. They are seperate code bases.
In short, to sum it up I don't think this project will be going very far unless you have access to whitepapers documenting the full hardware and are willing to code the OEM bits yourself using this info. I don't think it's worth doing though as you would be using the CE interface, and it would all need to be done over again when WM7 comes around...
Well, PRB doesn't crash for me in my visual kitchen when you add all other files from any other MSXIPKernel (dsm, rgu's etc).
Da_G said:
I think you may be a little confused?
It appears you have posted the MSXIPKernel package compiled from Embedded CE 6.0, compiled for ARM.
These CE 6.0 Binaries are not compatbile with CE 5.2, so attempting to use them in a Windows Mobile 6.x ROM as-is will not work. You state that "NOTE: As for the device-specific drivers, we have OEMXIPKernel" - do you mean the existing OEMXIPKernel, compiled against WM 6/CE5.2, if so this will not work at all with CE 6. I assume when you say "Ouh, and.. this kernel will work on all devices that has got Qualcomm MSM7xxx series chipsets.." you mean because it is compiled against ARMv6?
Also, you have posted several incorrect informations,
WM 7 is not based on CE6, but CE7.
WM 6.5.x is not in any way an alpha build of WM7. They are seperate code bases.
In short, to sum it up I don't think this project will be going very far unless you have access to whitepapers documenting the full hardware and are willing to code the OEM bits yourself using this info. I don't think it's worth doing though as you would be using the CE interface, and it would all need to be done over again when WM7 comes around...
Click to expand...
Click to collapse
I think they are all compatible with CE6.
CE6 has a different kernel architecture, but for drivers it all remains the same.
You're right, I'm not too updated, WM7 (Photon) is NOW based on CE7 Kernel, but if you search further, it initially was based on CE6 kernel Pre-Alphas of WM7 was CE6 based!
...and WM7 won't be usable with our devices, because it NEEDS a multitouch touchscreen, as you can see from minimum requirements by Microsoft.
Yes, for "it will work on all MSM7xxx" I mean that this is compiled against ARMv6.
All MSM7xxx chipsets has got a CPU that supports ARMv6 instructions set.
For example, MSM7201A (Diamond and other devices) has in its core an ARM1136EJ-S (yeah, the "J" was changed by Qualcomm, but it's an 1136EJ-S)!
And... the 5.2 kernel that we have now on our devices is compiled from Embedded CE 5.0 (updated) so it's compatible.
I didn't try porting with XIPPORT as the addresses with the CE6.0 Kernel are changed: it's larger than 5.2!
Well, it wouldnt hurt to TRY, right? I mean, the devices are pretty damn slow compared to android devices running on the same hardware, so if this COULD improve it, why not try it?
I'm sorry,
NK is very device specific, you cannot just take CE 6 NK and hope it'll magically work. We've been able to build CE6 ARM11 and Cortex for a long time, just press a few buttons in PB. But NK consists of OAL (OEM Adapation Layer) stuff, which is pretty device specific. More specifically, when NK gets to OEMInit, it'll simply fail, because this is where most of the initialization occurs, such as GPIO, MDDI client, NAND flash -etc. Even if you did get CE6 NK working, which would require you recompile CE6 with the OAL, which only HTC has, you would have to rewrite all the drivers since CE6 driver model changed a lot, (i.e., no more SetKMode(BOOL); - which HTC uses a lot).
Anyway, this project has been on the table for a while, and through a new (maybe old, well new for me) technique of disassemble-reassemble, we can maybe build an "Assembly" BSP that would let us run CE6. But its a lot of work, since again, ce6 driver model changed
Again, this topic has been repeated several times, so I will say what others have said in the past. If you have no clue about ARM assembly, please save your time, give up, and move on with other projects. A simple search will tell you about many people who got over-excited when they played with CE6 PB.
Da_ag. Why not give it a shot. This could open up the door to future developments beyond our wildest dreams for Windows Mobile. We, XDA as a community if we pull this off, might be able to create our own fully customized versions of Windows Mobile from the Kernel up. Also it would improve speed and usability of our current devices.
Please do not discount this project just because it looks hard. Isn't this the reason XDA was formed in the first place?
no2chem said:
I'm sorry,
NK is very device specific, you cannot just take CE 6 NK and hope it'll magically work.
Click to expand...
Click to collapse
CE6 doesn't even have NK(.exe) anymore say hello to kernel.dll and oal.exe! =)
kholk said:
I think they are all compatible with CE6.
CE6 has a different kernel architecture, but for drivers it all remains the same.
You're right, I'm not too updated, WM7 (Photon) is NOW based on CE7 Kernel, but if you search further, it initially was based on CE6 kernel Pre-Alphas of WM7 was CE6 based!
...and WM7 won't be usable with our devices, because it NEEDS a multitouch touchscreen, as you can see from minimum requirements by Microsoft.
Yes, for "it will work on all MSM7xxx" I mean that this is compiled against ARMv6.
All MSM7xxx chipsets has got a CPU that supports ARMv6 instructions set.
For example, MSM7201A (Diamond and other devices) has in its core an ARM1136EJ-S (yeah, the "J" was changed by Qualcomm, but it's an 1136EJ-S)!
And... the 5.2 kernel that we have now on our devices is compiled from Embedded CE 5.0 (updated) so it's compatible.
I didn't try porting with XIPPORT as the addresses with the CE6.0 Kernel are changed: it's larger than 5.2!
Click to expand...
Click to collapse
alright believe what you like but the facts will not change. no2chem told about it all already so I won't repeat him
Da_G said:
In short, to sum it up I don't think this project will be going very far unless you have access to whitepapers documenting the full hardware and are willing to code the OEM bits yourself using this info. I don't think it's worth doing though as you would be using the CE interface, and it would all need to be done over again when WM7 comes around...
Click to expand...
Click to collapse
you don't need access to so many papers. but they do ease the workload for you
again see what no2chem said... we're going to have lots of fun with this i guess.
I don't understand a thing, with this, you should be able to get CE 6 kernel without the BSP ?
cmonex said:
CE6 doesn't even have NK(.exe) anymore say hello to kernel.dll and oal.exe! =)
Click to expand...
Click to collapse
Right cmonex. I wanted to say that but you written before me
But.. now I've got a question.
IF CE6 doesn't have NK.exe anymore (and from what I see it doesn't have any NK.dll) and it's all based on OEM Adaptation Layer (OAL), THEN we won't use nk.exe anymore, right?
So.. CE5 uses PQOAL, monolithic kernel.
CE6 uses OAL, and it's all modular.
From THIS site, that explains the CE6 Kernel Architecture, I read the following:
"The OAL is linked with the generic kernel code to form the full kernel module."
Click to expand...
Click to collapse
"By splitting up the OAL from the generic parts two interesting things happen. First, the foundation for a well defined interface between the OAL and the kernel module is laid. It is no longer possible to just "extern" some kernel specific function in the OAL, as in the old monolithic architecture where the OEM sometimes use undocumented kernel functions to "backdoor" its way around some OAL "quirks" -something that may affect stability and compatibility of the kernel. In CE 6, the kernel functions are exported to the "oal.exe" as a function table (NKGLOBAL) as part of an initial handshake procedure. In the same way, OAL functions that are needed to support the core kernel are exported to "kern.dll" in a similar function table (OEMGLOBAL). "
Click to expand...
Click to collapse
And from MSDN I read the following:
So what did change? In CE6 we split up three components that previously linked together to make the kernel executable, nk.exe. CE5 the kernel, OAL and the Kernel Independent Transport Layer (KITL) all linked into nk.exe. In CE6 these are broken into kernel.dll, oal.exe and kitl.dll.
The primary reason for this change was updateability. In the past, if Microsoft released a kernel update, the OEM would have to take the updated kernel and link it again with their OAL to produce a new nk.exe. Now the OEM only has to distribute Microsoft’s new kernel.dll.
Click to expand...
Click to collapse
We CAN DO IT if we know how to split NK.exe into OAL and Kernel.
OR.. if we don't want to do never-used work, we need only to extract the OEM Adaptation Layer (OAL) from our current NK.exe.
Then we can link the OAL extracted from 5.2 Kernel to the NEW CE6 kernel.dll
Note that CE5 kernel does support the splitted modules, infact there are some BSPs that are built with OAL.exe/kernel.dll and NOT with NK.exe.
Read that on instructions for how to port a BSP from CE5 to CE6.
If someone can "extract" OAL from a Diamond NK.exe, I'll be happy to try if all works on MY device!
no, you can't just extract OAL from CE5 kernel, its linked at compile time into the fun monolithic kernel we know as NK. The architects of CE6 (in a smart move) seperated the OAL from kernel libs, much like the MDD-PDD model you see in many drivers since CE5.
So in ce6 you can just update the kernel by updating kernel.dll ideally. anyway like cmonex and i have said, just wait, we're working on reversing a bsp for rhod_w soon