| Versions |
  |
|
| Author |
 Topic  |
|
TroNik
362 Posts |
 Posted - 05 oct. 2010 : 23:14:22
|
quote:
Originally posted by jwoegerbauer
With Unlock.mscr you simply overwrite these 2 dlls
#Copy a few files to \Windows to fix Explorer and Microsoft Reader on some devices (ex. Mio Moovs)
Copy(SystemFolder\"CE5\ole32.dll", "\Windows\ole32.dll")
Copy(SystemFolder\"CE5\oleaut32.dll", "\Windows\oleaut32.dll")
and I don't know, whether this really makes sense.
quote:
Originally posted by Osprey
3. The Copy command does not overwrite unless the overwrite? flag (third parameter) is true.
Osprey, remember that there is the ROM based file system and the RAM based one. The above two lines of code successfully copy the files to the RAM based file system since the original ones exist in the ROM based file system (that's the reason I added the code and comment you can find in the SafeXCopy subroutine). You should switch back to how it was in R59 that you first check that it's a CE5 device and that these files don't exist. But still this won't allow mio moov devices to run explorer since the ole* files do exist in ROM. It's just that they are missing some functions. The correct solution is to additionally check that OLE32_MCOMSTM is not defined in ceconfig.h.
quote:
Originally posted by Klasno
2) Is it possible to sync the emulator with your computer and thus gain an activesync/internet connection? My bigger thought with this is that it would be possible to get Virtual Earth maps for devices that can't Activesync this way.
quote:
Originally posted by Osprey
2. My first thought is "probably not," but there is a Network tab when you go to File->Configure; however, it tells me that I need Virtual PC 2007. This emulator is probably a subset of the Virtual PC 2007 code, so perhaps installing the full-blown Virtual PC 2007 will open up more functionality (such as network access). I believe that Microsoft made Virtual PC a free download a few years ago, so you should be able to obtain it freely.
Yes it is. First, in the connection settings of ActiveSync or Windows Mobile Device Center enable "allow connections to one of the following" and select DMA. Second, run "C:\Program Files\Microsoft Device Emulator\1.0\dvcemumanager.exe" and right click -> cradle on the running emulator image.
quote:
Originally posted by bumbum
I really love the idea to create nk.bin from my own device for emulator usage.
There are ways to create firmware images from your device (see g_alin's thread) but the image won't run under device emulator. It has different hardware. If you want to experiment with device emulator here is an image for your device that I created when I made .NET framework to work on your device. Note that the only similarity with your device is that it has the same Windows CE components (ceconfig.h should match). |
http://iphonetoday.googlecode.com/ |
 |
|
|
bumbum
519 Posts |
Posted - 06 oct. 2010 : 00:00:38
|
@jwoegerbauer
I fully accept that you are not interested in ROM-dumping. Anyway, I thank you very much for your testing. This represents the same result than mines.
However, I am still interested to get a solution, grabbing the ROM and run it on emulator. This would make everything easier. For us all! I """believe""" I am short before to present a solution, I've tested nk.bin tools and much others. Everything is working, but not the elementary thing ==> grabbing the ROM from PNA, I used grabit and test_rom.exe, both are working, but if you hexedit, they are close to be empty. That's exactly the problem, to extract the ROM in what ever condition!
--------------------------------------------------------------------
Edit:
quote:
There are ways to create firmware images from your device (see g_alin's thread) but the image won't run under device emulator. It has different hardware. If you want to experiment with device emulator here is an image for your device that I created when I made .NET framework to work on your device. Note that the only similarity with your device is that it has the same Windows CE components (ceconfig.h should match).
@Tronik
I haven't seen that we may posted the same time. Thanks for the files from my device! So what you say is, that without platformbuilder, there's no way to create a bin file working for emulator?! What a pity!
Reasons why I am so interested in this stuff:
1. I've always a lot of devices from friends and colleagues to install Miopocket on. Due to lack of time these devices are often laying around for weeks and the owner has no GPS for that time. I could test only with bin file on emulator without device.
2. In the Mainthread you often read from hopeless cases, people who are too unexperienced to install Miopocket on their device. The ability to help them, by investigating their device on emulator would be great.
3. I am thinking about buying a new device. Problem it is very expensive and OS is WinCe 6.0. So before spending a lot of money and beeing may disappointed, it would help to ask someone to upload bin file for testing before buying.
However I will anyway went trough g_alin's thread. Thanks for that hint!
BTW I don't understand what you mean with different Hardware?
|
Falk F8, only used for real car Navigation, Miopocket Rel. 5? installed / Becker 7928 test device for car and writing desk, always newest Miopocket version / Medion 4435 only test device on writing desk, always newest Miopocket version / Often others |
Edited by - bumbum on 06 oct. 2010 17:31:29 |
|
|
|
Osprey
USA
2764 Posts |
|
|
bumbum
519 Posts |
Posted - 06 oct. 2010 : 17:37:07
|
quote:
Originally posted by Osprey
For anyone interested,
TroNik and I fleshed out the Device Emulator.mscr script a little, making the menus a little more functional: Device Emulator.mscr
You can also just download the whole package over again: MS Device Emulator + Images.zip
@Osprey
Thanks for update! As already reported Device Emulator.mscr is not working on my German Seven. I had to change
DevEmu = "C:\Program Files (x86)\Microsoft Device Emulator\1.0\DeviceEmulator.exe"
DevEmu = "C:\Programme\Microsoft Device Emulator\1.0\DeviceEmulator.exe"
May you should mention that in readme!? |
Falk F8, only used for real car Navigation, Miopocket Rel. 5? installed / Becker 7928 test device for car and writing desk, always newest Miopocket version / Medion 4435 only test device on writing desk, always newest Miopocket version / Often others |
|
|
|
jwoegerbauer
1824 Posts |
Posted - 07 oct. 2010 : 10:33:11
|
@Osprey,
concerning the Emulator-package:
a) as bumbum reported, emulator installs in "C:\Program Files\Microsoft Device Emulator"
FYI: term "Programme" used by bumbum simply is a hard-link to "Program Files" offered in german (Vista / 7) PC's startmenu, querying the HDD - where Vista / 7 is installed on - with explorer really folder "Program Files" is shown.
b) why not supply a simple installer script, perhaps as follows
#InstallWinCeEmulator.mscr
ErrorLevel("warn")
DefaultEmuFolder = "C:\Program Files\Microsoft Device Emulator"
DevEmu = DefaultEmuFolder\"1.0\DeviceEmulator.exe"
DefaultSharedFolder = "C:\Temp\Storage Card"
path = SystemPath("ScriptPath")
If(FileExists(DevEmu))
chc = Array("Reinstall", "Uninstall")
ChoiceDefault("InstallWinCeEmulator", "*** Device Emulator already installed ***", 0,0, chc)
Case(0)
Exit
Case(1)
Call Install
Case(2)
Call Uninstall
EndChoice
Else
Call Install
EndIf
Sub Install
If(NOT DirExists("C:\Temp"))
MkDir("C:\Temp")
ElseIf(NOT DirExists(DefaultSharedFolder))
MkDir(DefaultSharedFolder)
EndIf
chc = Array("32-bit version (x86)", "64-bit Version (x64)")
ChoiceDefault("InstallWinCeEmulator", "*** Designate type of your Windows ***", 0,0, chc)
Case(0)
Exit
Case(1)
Run(path\"vs_emulator.exe")
Case(2)
Run(path\"vs_emulator_x64_vista.exe")
EndChoice
EndSub
Sub Uninstall
DelTree(DefaultEmuFolder)
If(DirExists(DefaultSharedFolder))
DelTree(DefaultSharedFolder)
EndIf
EndSub
IMO, that would ease things.
c) No (device unspecific) image WinCE 5.0 Core available?
|
Edited by - jwoegerbauer on 07 oct. 2010 17:17:57 |
|
|
|
bumbum
519 Posts |
Posted - 07 oct. 2010 : 17:42:11
|
quote:
a) as bumbum reported, emulator installs in "C:\Program Files\Microsoft Device Emulator"
you are perfectly right with that. Looking from the DOS prompt there is only folder program files present, while in Device Emulator.mscr you need to call it "Programme" (before you presented your solution)
My confusion was based on the fact that in XP I saw in explorer
Programme and program files, while in seven ther's is only Programme. |
Falk F8, only used for real car Navigation, Miopocket Rel. 5? installed / Becker 7928 test device for car and writing desk, always newest Miopocket version / Medion 4435 only test device on writing desk, always newest Miopocket version / Often others |
|
|
|
jwoegerbauer
1824 Posts |
Posted - 12 oct. 2010 : 20:07:07
|
@bumbum,
somewhere else I've read you offer "WinCE_5.0_bumbum_image_for_Device_Emulator.rar". My question: how did you build this BIN? Perhaps not me alone, but also many others are interested in knowing how to do this, thus everybody can learn how to create a 1:1 copy of the OS-portion of his device, to be used with emulator. |
|
|
|
bumbum
519 Posts |
Posted - 12 oct. 2010 : 23:07:41
|
quote:
Originally posted by jwoegerbauer
@bumbum,
somewhere else I've read you offer "WinCE_5.0_bumbum_image_for_Device_Emulator.rar". My question: how did you build this BIN? Perhaps not me alone, but also many others are interested in knowing how to do this, thus everybody can learn how to create a 1:1 copy of the OS-portion of his device, to be used with emulator.
jwoegerbauer,
look up to Tronik's post on this page, where he send me the download link of "WinCE_5.0_bumbum_image_for_Device_Emulator.rar", he made with platformbuilder. I am still neither able to produce such an image, nor have offered it somewhere. So I am quite curious where you have seen this offer? If I would offer that, I would rename it to Medion_4435_image_for_Device_Emulator.rar |
Falk F8, only used for real car Navigation, Miopocket Rel. 5? installed / Becker 7928 test device for car and writing desk, always newest Miopocket version / Medion 4435 only test device on writing desk, always newest Miopocket version / Often others |
|
|
|
jwoegerbauer
1824 Posts |
Posted - 13 oct. 2010 : 16:33:13
|
@bumbum,
thanks for clarifying! My confusion came from this post. I'm now using the BIN-file that emulates your Medion E4435, because it comes next to my device:
@All,
DumpRC V1.18 is a tiny (17 KB) WinCE freeware tool you can use to extract the resources embedded (for example icon) in an .EXE-file. It's probably useful to add it to the Tools-section of your copy of MioPocket. BTW, the downloadable ZIP contains both the WinCE and the Win32 version.
|
|
|
|
goat
9 Posts |
Posted - 13 oct. 2010 : 18:03:09
|
Howdy all,
Ran across this utility awhile back, and thought I'd post it. Basically it is a hot driver loader. Haven't played with it any as it is in the wrong OS version for me, and have been working on other things to play with it. It would be interesting if somebody could compile it to work with lower versions of ce.
http://bogong.codeplex.com/ It would certainly be useful to load keyboard drivers for those devices that don't have them and can't reboot.
Another little program I've been meaning to post about is clipboard tool, which is a nice extension for those devices that are keyboard challenged. http://www.area51staff.it/mobility/ Simple drop in install with no problems.
Goat |
Edited by - goat on 13 oct. 2010 18:04:45 |
|
|
|
bumbum
519 Posts |
Posted - 13 oct. 2010 : 18:36:05
|
@jwoegerbauer
quote:
Originally posted by jwoegerbauer
@bumbum,
thanks for clarifying! My confusion came from this post.
Oh, I see. But again, I don't know how van
1. found this upload, cause I offered nowhere
2. why he believes that's the one he should use for tests. Remembering the net. problem it's may not a good idea to use this image for other devices.
May Osprey should include this image in his collection but rename it to Medion_E4435_CE_5.0.bin like you have done
quote:
I'm now using the BIN-file that emulates your Medion E4435, because it comes next to my device:
If you are interested, I've uploaded my extracted files from SMFlash.img here
http://www.mediafire.com/?0bddyvn3u3kzd5k
You might want to compare with yours. |
Falk F8, only used for real car Navigation, Miopocket Rel. 5? installed / Becker 7928 test device for car and writing desk, always newest Miopocket version / Medion 4435 only test device on writing desk, always newest Miopocket version / Often others |
Edited by - bumbum on 13 oct. 2010 18:37:05 |
|
|
|
g_alin
USA
817 Posts |
Posted - 13 oct. 2010 : 22:59:49
|
jwoegerbauer,
(I will answer to you on this thread ... to have continuity ...)
The files recovered can be found inside http://www.4shared.com/file/buo8xc-F/resource_2.html
Some details about the recovery:
1. the firmware image (in general) have two type of 'information': FILES and MODULES
2. FILES are recovered 100%
3. MODULES have the relocation table striped (and all the JUMPs inside are hard coded) -> my software is able to recover some of the DLLs ... but not all. EXE can be made with platform builder (those file don't have relocation table).
bumbum,
"Do you say, what we want is in general absolute impossible, or do you have some hints left?"
Not impossible; more like 'very approximatively' ... as you know M$ is offering (most) of the source code for wince and if the OEM want's to change something is freely able to do so ... When you say: we make an image like the one from GPS is only partially like the one from GPS.
Let me explain you why is partially: from M$ (licence point of view) the information used to calculate the licence price is based on the ceconfig.h file. But there you find only components from M$ (not the changes done by Samsung into kernel or coredll ... or other places). The good news is that usually changes are only at KERNEL level (but theoretically they can change also other components). Beside that you will find files (like BIRDrv.dll ...) that are not in the platform builder -> because are components used by Samsung for Virtual to Real translation (to access flash memory ...).
And additional to that ... some companies are minimizing the components added by Platform Builder (to pay less for license) and add those components 'manually' (at building).
Beside that you need to make some ROM cooking, to add the files extracted from your GPS into the wince image made with Platform builder ... even does on second thought you can add the files to image using the Platform Builder at building time ...
Let me know if you need more info ...
BTW: if you extracted the files using dumprom.exe ... the files are not correctly extracted ... |
|
|
|
jwoegerbauer
1824 Posts |
Posted - 14 oct. 2010 : 14:46:53
|
@goat,
programmatically loading / unloading a driver you can do via executing a simple Mortscript as follows:
#DriverLoad.mscr
ErrorLevel("off")
Prefix = argv[1]
DllFilePathName = argv[2]
If(IsEmpty(Prefix) OR IsEmpty(DllFilePathName))
Exit
EndIf
LoadFlag = argv[3]
If(IsEmpty(LoadFlag) OR ToLower(LoadFlag) ne "/u")
LoadFlag = "/L"
EndIf
DoReset = FALSE
DriverKey = "Drivers"
DriverPath = DriverKey & "\BuiltIn\" & Prefix
If(ToLower(LoadFlag) eq "/u")
#
#delete the driver
RegDeleteKey("HKLM", DriverPath, 1)
#
# re-set flag
DoReset = TRUE
ElseIf(NOT RegKeyExists("HKLM", DriverPath))
#
#add the driver
RegWriteString("HKLM", DriversKey, "BuiltIn", Prefix)
RegWriteString("HKLM", DriverPath, "Dll", DllFilePathName)
RegWriteString("HKLM", DriverPath, "Prefix", Prefix)
RegWriteDWord("HKLM", DriverPath, "Index", 1)
RegWriteDWord("HKLM", DriverPath, "Order", 1)
#
# re-set flag
DoReset = TRUE
EndIf
If(DoReset)
Restart
EndIf
a new compilation of "LoadDriver" you pointed out isn't compellingly necessarily, IMO.
After running such a script
CallScript("DriverLoad.mscr", "SAM", "\path\sample.dll", "/l")
this should be your registry entry:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SAM]
"Dll"="\path\sample.dll"
"Prefix"="SAM"
"Index"=dword:1
"Order"=dword:1
HTH
@All,
A:
How to determine the license level of your Windows CE?
quote:
Originally posted by daniHG
ceconfig.h ???
...
FYI:
Microsoft provides the tool LicenseTool50.exe that reads ceconfig.h and outputs the license level of the OS.
...
Warning: This tool is not intended for Windows CE 5.0 Core !!!
This statement is no longer valid, because a newer version of this Win32 tool is available, than that (obviously) initially used by daniHG.
1) The Windows CE 5.0 Run-Time Assessment Tool V2 (Win32) is an informational tool that you can use to determine which Windows CE license is predicted for the CE run-time image your device is based on.
2) Prior to using the tool, please ensure that your device has an ActiveSync connection with your desktop PC and that a ceconfig.h file in your device's folder \Windows is present.
3) Once you have downloaded the Run-Time License Assessment Tool, browse and select the ceconfig.h file at your device and then start the tool.
FYI, there are three run-time license options for Windows CE 5.0:
Core [$3 US - estimated retail price]
Professional
Professional Plus
Hence it doesn't make any sense to run in Emulator an image that doesn't match your device's license level, except you want to try out the features that come with another license level.
B:
Free Virtual Serial Ports Emulator (VSPE)
(by Eterlogic Software, last update 2010/10/12) is intended to help software engineers and developers to create/debug/test applications that use serial ports. It is able to create various virtual devices to transmit/receive data. Unlike regular serial ports, virtual devices have special capabilities: the same device can be opened more than once. Using VSPE you can share physical serial port data between several programs, create virtual pipes and so on. Version 0.865 includes unspecified updates. It runs under Vista/XP/NT/2000.
|
Edited by - jwoegerbauer on 15 oct. 2010 11:25:01 |
|
|
|
Gremlin
Germany
70 Posts |
Posted - 15 oct. 2010 : 21:44:39
|
@jwoegerbauer
Thanks for calling me a Guru, but even a Guru needs some context to make sense of answeres. ;-)
The point i'm a bit confused about, which didn't came across right, is that the platformbuilder creates an image. The M$ emulator is meant to test those images before deployment. So i would presume that both use the same kind of image.
How come, that the firmware images are of a different type?
Why would anyone take the build and tested image and then convert it into something else? Or do i overlook something?
Regards Gremlin
|
|
|
|
g_alin
USA
817 Posts |
Posted - 15 oct. 2010 : 22:38:52
|
Gremlin,
"Why would anyone take the build and tested image and then convert it into something else? Or do i overlook something?"
That its a very good question ... but there are two 'widely' used formats:
1. NB0 -> or uncompressed partition
2. B000F -> compressed partition
If I am not wrong both of them care available after build (*.nb0 and *.bin)
The OEM platform are coming with 'some helpful softwares' that convert that to another format -> firmware format: header + XIPKERNEL + CHAIN + XIP => and the last one is used for firmware upgrade.
Why so complicated? (I ask my self ...) I don't know ... probably was not specified by M$ and every 'platform manufacturer' choose something that was good for them ... |
|
|
|
Topic |
|
|
|
| This page was generated in 1,64 seconds. |
 |
|
- 
- 
MioPocket >> Tips & Tricks & Wishlist & More
