I have a Symbol MC 75. It is running Windows Mobile 6.5, but there are several updates after the basic Windows Mobile 6.5:
Windows Mobile 6.5
Windows Mobile 6.5.1
Windows Mobile 6.5.3
Windows Mobile 6.5.5
How do I know which one I am running?
I went to the about page for my device and it just says Windows Mobile 6.5. Does that mean I only have the 6.5 or is it not bothering to show me the update version?
NOTE: The CE OS version is: 5.2.21840 (build 21840.5.0.60) in case that helps.
Note 2: The reason I care is that there is a Developer Tool Kit that is targeted for 6.5.3 and I want to know if I can use it.
It looks like builds 5.2.28xxx are for 6.5.3 and 5.2.21xxx are for 6.5
Sources:
source 1 (and in case the google-cached page doesn't show here's the original)
source 2 (read the comments areas too)
Looks like the start button is on the bottom with 6.5.3. Since it is still on the top corner I am guessing I am on 6.5 or 6.5.1.
Tap on Start>Settings>System>About
Related
I'm studying React Native.
Unfortunately Windows 10 Home is not Support Hyper-V. Since, i can't use Android Studio Simulator.
Is there any way to run Simulator.
I have no idea where you got your information that you can't use it.
Android Studio's emulator uses HAXM (Hardware Accelerated Execution Manager) on Intel CPUs, which in return is also used by Hyper-V.
Hyper-V is a very self-absorbed technology that doesn't play well with others (just like many other things Windows offers) and having it ON is actually what screws things up and you need a workaround in that situation.
I also have Win10 Home on one of my computers and tried running the emulator with a default Basic task project on a virtual Pixel 2 with Android 8.1 Oreo. It works.
Sorry, mine was AMD Processor, for AMD HAXM no need, instead have to install Hypervision for AMD Processor in Sdk tool.
It worked.
I use Codewarrior
- V4.7 for HCS12X
- V6.3 for HCS08
in Windows XP.
Moving CW to Windows 10 seems impossible.
It won’t install, and dongle licensing does not work.
I have tried to figure this out on the NXP site, but I find it extremely difficult and confusing.
Which Codewarrior is needed for HCS12X and HCS08 in 32 and 64 bit Windows 10?
Yeah it is nearly impossible. I've struggled lots with this problem. There is an unofficial "hack" someone made - won't link it because my browser says the site is unsafe. However, it would seem that hack only works up to Windows 8, not on Windows 10. I have both IDEs (HCS08 and HCS12) running perfectly on a Windows 7 machine, with dongle license.
We managed to get it running so-so on Windows 10 by doing a dirty hard copy of the hacked installation folder to Windows 10. Various mysterious bugs followed though, so not the best idea.
Another option is to run the Windows XP mode emulator from Microsoft, but it is no longer supported for Windows 10.
So ultimately there are two options left if you are stuck with Windows 10:
Move development to the worst IDE ever released, Codewarrior for Eclipse. Please note that the future of this IDE is uncertain after the NXP merger. They might decide to put their money on their other trash IDE, LPCxpresso.
Port your project to another compiler or MCU.
I would recommend to install it in a VMWare or virtualBox container using Windows 7 as OS.
This makes it possible, that your installation will work even in some years.
I'm using such a container (with WinXP) for an old Visual Basic 6 installation and HEW-IDE.
You should use at least Win7, to avoid the network problems with WinXP (SMB1 can't be connected anymore).
There is a Codewarrior Classic 6.3 community project for RS08, S08, ColdFire V1 for Windows XP, 7, 8, 8.1, and 10. Basically, the installer is repacked will all service packs and patches for USBDM and PEMicro tools.
If you have an obsolete programming tool you will need to use CW 6.3 on XP. Also, if you have these specific family of parts S08: RN, RNA, PA, PT, Kinetis (including Tower), ColdFire V2 you must use the bloated eclipse version CodeWarrior 11
For S12 or S12X CodeWarrior Classic 5.2 for Windows 7 - Windows 10
But when they released 5.2 they removed most of the older derivatives from it, but you can add them back using this procedure CodeWarrior 5.2
I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric
I am using qtp 11.0 32 bit trial version on windows 8.1 pro 64 bit OS. Problem is qtp is not generating the systemutil.run command on recording an application. what the problem would be ? I already tried setting the windows application utility to generate system.util command in tools--> options but still the problem persists
According to QTP11's Product Availability Matrix (which you can only see if you have an HP passport and I suppose you don't have considering that you're using a trial version). Windows 8 and 8.1 are not supported with QTP11. This isn't surprising since QTP 11 was released almost two years before Windows 8.
I know for a fact that QTP11 doesn't support IE11 which is the earliest version of IE supported on windows 8.1.
Since you're using a trial version in any case why not download the latest version (UFT 12)?
QTP was united with Service Test and is now called Unified Functional Testing (UFT) and version 12 does support Windows 8.1.
I have this error message:
The windows phone emulator requires Hyper-V. Your PC is missing the
following pre-requisites required to run Hyper-V:
I cannot run my project on windows 8 phone emulator since days. I searched on internet, still I couldn't solve my problem. Everyone says open Control-panel, then click turn-off or turn on windows features, then choose hyper-v option. When I clicked turn off or turn on windows features there is no option about Hyper-V. Can anyone help me?
My computer features:
windows-8 Professional (64Bit)
intel core i7 processor
8Gb ram
First step
1- turn on hyper-v from bios
read this :
http://blogs.technet.com/b/canitpro/archive/2014/03/11/step-by-step-enabling-hyper-v-for-use-on-windows-8-1.aspx
2- turn on hyper-v from windows
At the Start Screen, swipe the right hand side of the screen and select the Search Charm.
Type turn windows features on or off and select that item.
Select and enable Hyper-V.
If Hyper-V was not previously enabled, reboot the machine to apply the change.
I formatted my os from windows 8 pro to windows 8 enterprise and I solved my problem easily.I know it is not a logic solution but it worked.
In order to run Windows Phone 8 emulator you need to enable Hyper-V technology in the BIOS of your PC. See the detailed article on how to do this.
First you must turn on hyper-v from bios and then turn hyper-v from windows featured list restart and then will work ..