We gather spoil Symbian on pocket PC as initial codes symbian already are but we not known how to create a kernel and to start it on pocket PC
If we can start a kernel that of the big problems with GUI won't be as already there are programs for editing GUI and all other
But there will be problems with drivers
stdog21 said:
We gather spoil Symbian on pocket PC as initial codes symbian already are but we not known how to create a kernel and to start it on pocket PC
If we can start a kernel that of the big problems with GUI won't be as already there are programs for editing GUI and all other
But there will be problems with drivers
Click to expand...
Click to collapse
I guess, you'll get the answer from here
Related
How could I convert non pocket pc application
into pocket pc application? Is there any software
to do that? Is is very frustrating that those application
works on desktop pc but not on pocket pc. can
anyone help here. thanks.
You could try to write a i386 virtual machine for PocketPC, and install a Windows (98, 2k, XP) on that virtual machine.
Sorry, just kidding :lol: . No, actually you can't run a PC binary on a PPC. If you have the source code than you can compile it for PPC, if there aren't unsuported features inthe code (usually there are so you have to change the code). It's usually hard work to port an application that was written without thinking of porting it (does the Bridge pattern ring a bell? :wink: )
hello,
I have a hitachi g1000 with windows mobile 2002, i want to rid off from sprint win version with all functions and feature and install a normal winCE.
the problem is, I cant do that, downloaded from micrsoft website trial verision but when run setup.exe it stops and ask tell my windows on PC need some other application and etc and etc. I install one application .NET Framework 2 but still not possible to go on with setup.
I would like to know is it only with me or someone also experince similar problems, please share with me yourexperience if you have installed on your pda win CE and how.
is there any other way to install it on my hitachi, or what I'm doing wrong?
Hello dar22.
It seems you misunderstand the whole Pocket PC OS issue.
You cannot just install Windows CE because it is not a generic operating system like Windows XP.
First, Windows Mobile is a derivative of Windows CE, but it also adds some functions. Even if you could replace your OS pure windows CE cannot run most apps developed for the PPC.
Second, Windows Mobile is custom tailored for every device (so is Win CE) and the result is called ROM image. You can't just install a generic version and then add drivers because they all come together from the manufacturer.
So to conclude this:
Unless the devices OEM provides an upgrade, there is no way to change the OS.
yes I uderstand than the generic WIN CE comes without drivers for a specific PDA, but the whole idea that I don't need that pda's most of it's functions such as camera and phone functions, I need only to have WINCE on it.
Can anybody advice me how to rid off from original Windows Mobile and install instead of that pure win ce version?
I mean what applications should I have on my PC to flash my device with WIN CE?
You still haven't understood me.
When I said 'drivers' I meant such basic things like memory, touch screen, device buttons.
Even those things need specific drivers from the OEM so there is no way to install Win CE on your device, unless:
1) You can dump the original ROM and extract all the drivers.
2) You can get MS Platform Builder (full and legal version), incorporate the drivers and create a special image for your device.
(I think you actually have to be an OEM and have contract with MS for the second part)
I am not sure what you tried to install, but there is no Win CE version you can just flash to any device and it will work.
levenum, thanks for your support, what you think can I install linux instead? I just don't want to have the sprint windows version
Well, you could try looking for linux version, but I am not sure there is one for your device.
You see, for mobile devices it is pretty much the same thing with linux. OEMs do not release even the basic drivers so there are no generic OS for these devices.
There are linux projects for HP iPaqs and also xanadux project (look in the WiKi) for HTC devices, but I don't know of anything for your device.
Perhaps if you specify what exactly bugs you about the OS maybe we can recommend apps and reg tweaks to get around is.
I ran across Windows Mobile SDK and some emulators/images of WM6.1 on microsoft's website and when i ran it, it comes up on the screen as if it were a real ppc, allowing me to install cabs and have them function and all. I can't get the program to allow me to change the BIN it uses as the image. If this could be figured out, could this be used to test ROMs before flashing (I want to get into cooking)?
i dont not believe the emulator support real roms as it dont deal with drivers and other hardware related issues at all
it also comes as standalone so people dont need to install the sdk
http://www.microsoft.com/downloads/...c5-6597-4313-912a-f0cca9c7d277&displaylang=en
Fair warning to you devs out there.. If you update you can no longer deploy applications to your phone (you need a phone with the update).
so emulator only.
Click to expand...
Click to collapse
EDIT:
Turns out you can deploy with the new SDK! I do have lockups though on every other deploy... a simple unplug and re-deploy fixes.
hahaha, thats kind of a big issue that you need the new firmware on phone to test your app but i guess that means the update has to be soon for the hardware
From how its looking now, microsoft wants to give a 1 month head start for devs to "update proof" or "feature match" with the update...
So right now im positive no update for phones before feb 16th and im willing to bet that there wont be an update till very close to march if not past that (they want CDMA phones on board). <--- probably going to announce this at MWC.
Turns out you can deploy with the new SDK! I do have lockups though on every other deploy... a simple unplug and re-deploy fixes.
looks kinda slim...
How to: Test Copy and Paste in Windows Phone Emulator
What’s in the January 2011 Update
The following are included in the Windows Phone Developer Tools January 2011 Update:
Copy and Paste
Copy and paste is now enabled on Windows® Phone 7 in the following controls:
*
System.Windows.Controls.TextBox
*
System.Windows.Controls.PasswordBox
*
Text input fields within the Microsoft.Phone.Controls.WebBrowser control.
Developers can test the copy and paste functionality in the new Windows Phone Emulator. For more information, see How to: Test Copy and Paste in Windows Phone Emulator. End users can use the copy and paste functionality only after receiving the corresponding update to the Windows Phone 7 operating system.
Most applications already published to the Windows Phone Marketplace do not need to be recompiled to take advantage of copy and paste functionality. Copy and paste will work automatically for end users after they receive the corresponding update to the operating system.
Caution:
In applications that have pivot or panorama controls that contain text boxes, users can unintentionally change panes when trying to copy text. To prevent this problem, open your application, recompile it, and then resubmit it to the Windows Phone Marketplace.
Windows Phone Capability Detection Tool
Detects the phone capabilities used by your application. When you submit your application to Windows Phone Marketplace, Microsoft performs a code analysis to detect the phone capabilities required by your application and then replaces the list of capabilities in the application manifest with the result of this detection process. This tool performs the same detection process and allows you to test your application using the same list of phone capabilities generated during the certification process. For more information, see How to: Use the Capability Detection Tool.
Windows Phone Connect Tool
Allows you to connect your phone to a PC when Zune® software is not running and debug applications that use media APIs. For more information, see How to: Use the Connect Tool.
Updated Bing Maps Silverlight Control
Includes improvements to gesture performance when using Bing™ Maps Silverlight® Control. For more information, see Bing Maps Silverlight Control for Windows Phone.
What’s in the WPDT Fix
After installing the Windows Phone Developer Tools Fix, application developers can deploy XAP files over 64 MB in size to physical phone devices for testing and debugging.
Click to expand...
Click to collapse
I have experience as a .net developer, a SQL developer, and a network administrator, but I've never done anything with mobile development. I'll be able to do some damage, but I need someone to point me in the right direction here.
I am not interested in messing with the existing windows CE os AT ALL, only Android. I motivated by this phone because it's the only modern phone who's ESN can be activated on verizion without a data plan.
SO, can an experienced person within the community give me a lay of the land of where I can contribute and get working?
my 2c: Most of the hacking i've done was on PSP, and they always loaded custom firmware by getting into the core / bios area, just like all of the other jailbreak methods. Can we do that?
Gaujo said:
I have experience as a .net developer, a SQL developer, and a network administrator, but I've never done anything with mobile development. I'll be able to do some damage, but I need someone to point me in the right direction here.
I am not interested in messing with the existing windows CE os AT ALL, only Android. I motivated by this phone because it's the only modern phone who's ESN can be activated on verizion without a data plan.
SO, can an experienced person within the community give me a lay of the land of where I can contribute and get working?
my 2c: Most of the hacking i've done was on PSP, and they always loaded custom firmware by getting into the core / bios area, just like all of the other jailbreak methods. Can we do that?
Click to expand...
Click to collapse
well, one major thing that you can help with, is getting drivers for the kin two, because the ones we have are only diag drivers, and do not let us see the phone in windows explorer...the diag drivers only let us see the filesystem in Bitpim.
welcome to the "i know kung-fu but this seems to need jiu-jitsu" group of developpers.
As noted above... drivers.. drivers drivers....
In the other threads you can see my hardware attempts resume about the usb access to the devices and explanation about why we didnt flashed anything yet (tldr; is shop-protected).
The only driver available for flashing (in windows) or linux direct access turned us into a nvflash executable being frozen, doing anything. For the other modes we have not data on how to operate with them.
On your request: yes, you could run android here, as tegra 2500 was made for wince and android (currently they work with froyo), so i guess we could do the move (i would want to backup Win CE anyway... just in case ... for messing around with flashing...).
johnkussack said:
welcome to the "i know kung-fu but this seems to need jiu-jitsu" group of developpers.
As noted above... drivers.. drivers drivers....
In the other threads you can see my hardware attempts resume about the usb access to the devices and explanation about why we didnt flashed anything yet (tldr; is shop-protected).
The only driver available for flashing (in windows) or linux direct access turned us into a nvflash executable being frozen, doing anything. For the other modes we have not data on how to operate with them.
On your request: yes, you could run android here, as tegra 2500 was made for wince and android (currently they work with froyo), so i guess we could do the move (i would want to backup Win CE anyway... just in case ... for messing around with flashing...).
Click to expand...
Click to collapse
I've never edited or created a driver, but if someone will point me in a specific driver, I will hammer away as best I can.
I don't understand what you mean here:
" The only driver available for flashing (in windows) or linux direct access turned us into a nvflash executable being frozen, doing anything. For the other modes we have not data on how to operate with them."
Point 1) The APX mode (booting with USB keys + power) is what we called as flashing "part", which uses nvflash (.exe) as tool to do flashing to the devices.
The driver you can get from nvidia (that one exists) lets nvflash find the device but the kin seems to be writeprotected, so the tool outputs an error while connecting to the KIN. Also, further attemps make nvflash get stuck in the connection process forever (and ever).
Point 2) The other modes (normal or special keys hold) have no known drivers nor known-yet ways to get them. Of course, if i knew how to make one, i would have tried to make it myself, as i tried with the MPMz protocol on the kin, so can't point you in any direction there.
That's what i meant.