How to get vga device emulation
none of the shortcuts emulate a hidpi device, i.e. vga. i created my own shortcut using the command line args, set video to 480x640x16 and it gave a vga screen, but it was not 'hidpi', it was the same as running sevga on a true vga device, i.e. not what the user normally sees.
anyone got proper emulation of a wm2003se vga device?
[342 byte] By [
jamier] at [2008-1-12]
With Visual Studio 2005 Beta 2, you have an entry called "Pocket PC 2003 SE VGA Emulator". This will load a Hi DPI 2003 SE VGA image and will behave exactly the same way as a VGA device. There is a similar entry for the Smartphone emulator.
Thanks Carl
I'm using the community preview of the standalone emulator. I assume I cannot do it with this, and need to install the full vis studio you mention?
If so, do you think i could assume the final standalone emulator will have a hidpi image? I'd rather not install visual studio on this workstation.
Jamie
We are in the process of creating a new set of images for the Device Emulator Preview available on Microsoft Betaplace that include the following images:
Standard, HIDPI, and Square images for PPC
Standard and QVGA images for Smartphone.
We will include these images for these form factors for both Windows Mobile 5.0 (Magneto) and Windows Mobile 2003 Second Edition (OzoneUpdate).
If you don't want to wait for that simply copy the BIN file over and create the shortcut manually, specifying /video 480x640x16 etc. You can also adjust the skin - simply use the 2003_SE skin and resize it to 200%. Run the device emulator directly to see the possible command line parameters.
You can also use this approach to experiment beyond VGA. The HiRes BIN image supports resolutions up to 1 MB - with 16 bits per pixel that's up to 800x640. (However the true limit seems to be 800x600). This is a good way to test the resolution and orientation awareness of your program.
Hi,
Are the VGA device image for the standalone emulator now available?
I've the same problem...
Thanks,
Xavier
I'm looking for the same thing: Windows Mobile 5.0 VGA images for the standalone emulator (either v1 or v2 CTP) (without any Visual Studio). 
Haven't found it yet, I guess it doesn't exist...
By the way, that's a shame that the Localized Windows Mobile 5.0 Pocket PC Emulator Images aren't working with the standalone emulator. 
The only Windows Mobile VGA emulator images I'm aware of ship with the Windows Mobile 5.0 SDKs.
You should be able to use these images with the standalone emulator.
Thanks for your answer Michael, but you need Visual Studio 2005 for installing the
Windows Mobile 5.0 SDK for Pocket PC. So unless taking the ROMs after decompiling the msi file, there seems to be no way out...
Hi all!
I have the rom files (thanx to WiX) (several .BIN, .XML, .BMP & .ibd files), but I don't know how to open them with the Microsoft Device Emulator 2.0 Preview. Could anyone help?
Hi
By starting DeviceEmulator.exe with the correct set of arguments (get the command line options with "DeviceEmulator /?") At the very minimum specify the bin file.
for instance: DeviceEmulator.exe romfile.bin /memsize 128
I got a:
Device Emulator [X]
Error: Invalid or missiong ROM image.
[OK]
error.
I tested with all of the 4 ROM images. I checked them, the files are not corrupted.
Maybe there is a way of registering the ROM images in the registry, & then use the GUI to load them?
There must be something wrong with your ROM files.
I can successfully launch the PPC VGA emulator with the following command:
cd <location of the BIN files>c:\Program Files\Microsoft Device Emulator\1.0\DeviceEmulator.exe PPC_USA_VGA.BIN /language 2055 /memsize 128 /video 480x640x16
I was using the 2.0 version, but I tried the 1.0 too, didn't work.
I'm using a shortcut:
target: "C:\Program Files\Microsoft Device Emulator\1.0\DeviceEmulator.exe" Pocket_PC_PE_Emulator_VGA.bin /language 2055 /memsize 128 /video 480x640x16
start in: C:\Program Files\WM03ROMS\Pocket_PC_PE_Emulator_VGA
still the same error message
weird... :-(
WiX didn't say there was any problem after decompressing the MSI file, so the BIN files should be OK (the others file seem alright).
I had some POCKET~3, POCKET~4, ... file names, I renamed them (according to the xml file), but it didn't change anything. It's probably comming from here.
Any other idea? If not, thanks for your help.
