I have a windows CE based navigation system with bluetooth. It has 2 settings the navigation mode which is a shell over windows ce and desktop mode where you the windows ce desktop.
In the navigation mode I can see the ODBkey bluetooth dongle.
I have installed FESmobile under desktop mode and the program works. The only problem I have is that bluetooth doesn't seem to work under desktop mode.
Does anyone have an idea?
windows CE based navigation
Re: windows CE based navigation
The device I have only wants to pair to phones.
So looking now if there is one that wants to pair to OBDKey.
Did anyone succesfully got FESmobile working on a windows CE based navigation?
So looking now if there is one that wants to pair to OBDKey.
Did anyone succesfully got FESmobile working on a windows CE based navigation?
-
wojtassslg
- Posts: 8
- Joined: 20 Apr 2011, 23:18
Re: windows CE based navigation
I have the same problem. Device GoClever 4330a WindowsCE 5.0.
I installed FESmobile2.2.cab with ActiveSync 4.5, WinCE CAB Installer on XP operating system.
When you come to the end of the belt installation, the program will automatically be removed from the installation place.
After recording a program FESmobile2.2.cab MSCEInf on SD card error pops up and the program will not open.
Do FESmobile 2.2 work at all on WindowsCE, if not, then if and when we can expect a compatible version?
I installed FESmobile2.2.cab with ActiveSync 4.5, WinCE CAB Installer on XP operating system.
When you come to the end of the belt installation, the program will automatically be removed from the installation place.
After recording a program FESmobile2.2.cab MSCEInf on SD card error pops up and the program will not open.
Do FESmobile 2.2 work at all on WindowsCE, if not, then if and when we can expect a compatible version?
-
it would be pretty cool to start grub.exe directly from NT based Windows.
Its questionable how well this could work? Does NT based Windows mess with BIOS / hardware like some Linux drivers do? I mean, will there be the same hardware based issues like at Linux?
Its questionable how well this could work? Does NT based Windows mess with BIOS / hardware like some Linux drivers do? I mean, will there be the same hardware based issues like at Linux?