Hi,

After I installed wince 6.0 on a PC with wince 5.0, I can't run any
emulators from Platform builder any more. According to wince 6.0
documentation, wince 6.0 breaks the x86 windows ce 5.0 emulator, and
recommends ARMV4I-based device emulator. I've downloaded and installed
ARMV4I-based device emulator. However, when I try to launch any
emulator here is what I get:

(CoreCon) 09:24:56 10/26/2006 Central Standard Time: Failed to connect
debug message service! Please check the transport settings.
(CoreCon) 09:24:56 10/26/2006 Central Standard Time: Transport service
failed to connect
(CoreCon) 09:24:56 10/26/2006 Central Standard Time: Warning: One or
more services failed to connect. Make sure that the service is properly
configured.


My Target->Connectivity Settings are as follows:

Target Device: CE Device <---- I've tried others - same result
Download: Emulator
Emulator: Transport
Debugger: KdStub

Any help will be appreciated.

Thank you in advance.

Vadim.

Re: Problem Running ARMV4I-based emulator from platform builerder after ce 6.0 rtm install by Steve

Steve
Thu Oct 26 10:27:49 CDT 2006

You will run into lot's of these kinds of connectivity issues, especially
with the emulators, when trying to run them side by side. These sorts of
issues is why I strongly recommend NEVER running any PB version installs
side by side on the same machine. Use another machine or a virtual PC.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: Problem Running ARMV4I-based emulator from platform builerder by Vadim

Vadim
Thu Oct 26 11:08:46 CDT 2006

Steve,

First of all thank you for such a prompt reply.
I was fully aware of the impact of installing 6.0 side by side with 5.0,
however, I have/had no choice in the matter. The installation/release
notes for 6.0 RTM clearly said that side by side installation is
allowed. So, I risked it.
So, are you saying there is no remedy? I am reluctant to uninstall 6.0
since it introduces whole bunch of problems with 5.0 as well (according
to release notes). What do you recommend?

Thanks again,

Vadim.



Steve Maillet (eMVP) wrote:
> You will run into lot's of these kinds of connectivity issues, especially
> with the emulators, when trying to run them side by side. These sorts of
> issues is why I strongly recommend NEVER running any PB version installs
> side by side on the same machine. Use another machine or a virtual PC.
>

Re: Problem Running ARMV4I-based emulator from platform builerder after ce 6.0 rtm install by Barry

Barry
Thu Oct 26 13:00:50 CDT 2006

Vadim, for the new ARM-based DeviceEmulator, you need to specify
"DeviceEmulator" as the download type and transport. The new emulator has a
slightly different interface than the old one, and so requires a different
downloader in Platform Builder.

Barry

"Vadim Tokarskiy" <vtokarskiy@ingenient.com> wrote in message
news:OcCrkyQ#GHA.1196@TK2MSFTNGP02.phx.gbl...
> Hi,
>
> After I installed wince 6.0 on a PC with wince 5.0, I can't run any
> emulators from Platform builder any more. According to wince 6.0
> documentation, wince 6.0 breaks the x86 windows ce 5.0 emulator, and
> recommends ARMV4I-based device emulator. I've downloaded and installed
> ARMV4I-based device emulator. However, when I try to launch any emulator
> here is what I get:
>
> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Failed to connect
> debug message service! Please check the transport settings.
> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Transport service
> failed to connect
> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Warning: One or
> more services failed to connect. Make sure that the service is properly
> configured.
>
>
> My Target->Connectivity Settings are as follows:
>
> Target Device: CE Device <---- I've tried others - same result
> Download: Emulator
> Emulator: Transport
> Debugger: KdStub
>
> Any help will be appreciated.
>
> Thank you in advance.
>
> Vadim.


Re: Problem Running ARMV4I-based emulator from platform builerder by Vadim

Vadim
Fri Oct 27 11:48:04 CDT 2006

The only options in the Platform Builder's (Wince 5.0) in
Target->Connectivity options for Download and Transport:
1. Ethernet
2. Serial
3. Emulator
4. None


I have it set as follows:
Download: Emulator
Transport: Emulator
Debugger: KdStub

Am I doing something wrong?

Thank you in advance for your help.

Vadim.



Barry Bond [MS] wrote:
> Vadim, for the new ARM-based DeviceEmulator, you need to specify
> "DeviceEmulator" as the download type and transport. The new emulator
> has a slightly different interface than the old one, and so requires a
> different downloader in Platform Builder.
>
> Barry
>
> "Vadim Tokarskiy" <vtokarskiy@ingenient.com> wrote in message
> news:OcCrkyQ#GHA.1196@TK2MSFTNGP02.phx.gbl...
>> Hi,
>>
>> After I installed wince 6.0 on a PC with wince 5.0, I can't run any
>> emulators from Platform builder any more. According to wince 6.0
>> documentation, wince 6.0 breaks the x86 windows ce 5.0 emulator, and
>> recommends ARMV4I-based device emulator. I've downloaded and
>> installed ARMV4I-based device emulator. However, when I try to launch
>> any emulator here is what I get:
>>
>> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Failed to
>> connect debug message service! Please check the transport settings.
>> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Transport
>> service failed to connect
>> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Warning: One
>> or more services failed to connect. Make sure that the service is
>> properly configured.
>>
>>
>> My Target->Connectivity Settings are as follows:
>>
>> Target Device: CE Device <---- I've tried others - same result
>> Download: Emulator
>> Emulator: Transport
>> Debugger: KdStub
>>
>> Any help will be appreciated.
>>
>> Thank you in advance.
>>
>> Vadim.
>

Re: Problem Running ARMV4I-based emulator from platform builerder after ce 6.0 rtm install by Doug

Doug
Sun Oct 29 03:14:19 CST 2006

Give this a try:

If you have Macallan or PB for Windows Mobile 5.0 installed and PB 6.0 you
will not be able to use the x86 emulator with the earlier version.

A workaround is to copy emulatortransport_500.dll from "program
files\windows ce platform builder\5.00\corecon\bin" or "program
files\Platform builder for windows mobile\5.00\corecon\bin"
to "program files\common files\microsoft shared\corecon\5.01\bin".

--
-- Doug
///////////////////////////////////////////////////////////////////
// StdDisclaimer.h:
// This posting is provided "AS IS" with no warranties, and confers
// no rights.

"Vadim Tokarskiy" <vtokarskiy@ingenient.com> wrote in message
news:%23Fmvfge%23GHA.4704@TK2MSFTNGP04.phx.gbl...
> The only options in the Platform Builder's (Wince 5.0) in
> Target->Connectivity options for Download and Transport:
> 1. Ethernet
> 2. Serial
> 3. Emulator
> 4. None
>
>
> I have it set as follows:
> Download: Emulator
> Transport: Emulator
> Debugger: KdStub
>
> Am I doing something wrong?
>
> Thank you in advance for your help.
>
> Vadim.
>
>
>
> Barry Bond [MS] wrote:
>> Vadim, for the new ARM-based DeviceEmulator, you need to specify
>> "DeviceEmulator" as the download type and transport. The new emulator
>> has a slightly different interface than the old one, and so requires a
>> different downloader in Platform Builder.
>>
>> Barry
>>
>> "Vadim Tokarskiy" <vtokarskiy@ingenient.com> wrote in message
>> news:OcCrkyQ#GHA.1196@TK2MSFTNGP02.phx.gbl...
>>> Hi,
>>>
>>> After I installed wince 6.0 on a PC with wince 5.0, I can't run any
>>> emulators from Platform builder any more. According to wince 6.0
>>> documentation, wince 6.0 breaks the x86 windows ce 5.0 emulator, and
>>> recommends ARMV4I-based device emulator. I've downloaded and installed
>>> ARMV4I-based device emulator. However, when I try to launch any
>>> emulator here is what I get:
>>>
>>> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Failed to connect
>>> debug message service! Please check the transport settings.
>>> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Transport service
>>> failed to connect
>>> (CoreCon) 09:24:56 10/26/2006 Central Standard Time: Warning: One or
>>> more services failed to connect. Make sure that the service is properly
>>> configured.
>>>
>>>
>>> My Target->Connectivity Settings are as follows:
>>>
>>> Target Device: CE Device <---- I've tried others - same result
>>> Download: Emulator
>>> Emulator: Transport
>>> Debugger: KdStub
>>>
>>> Any help will be appreciated.
>>>
>>> Thank you in advance.
>>>
>>> Vadim.
>>



Re: Problem Running ARMV4I-based emulator from platform builerder by Vadim

Vadim
Mon Oct 30 10:37:49 CST 2006

Doug,

Thank you very much. I'll give it a try and let you know.

Vadim.

Doug Cook (MS) wrote:
> Give this a try:
>
> If you have Macallan or PB for Windows Mobile 5.0 installed and PB 6.0 you
> will not be able to use the x86 emulator with the earlier version.
>
> A workaround is to copy emulatortransport_500.dll from "program
> files\windows ce platform builder\5.00\corecon\bin" or "program
> files\Platform builder for windows mobile\5.00\corecon\bin"
> to "program files\common files\microsoft shared\corecon\5.01\bin".
>

Re: Problem Running ARMV4I-based emulator from platform builder after by Vadim

Vadim
Tue Oct 31 09:11:44 CST 2006

Doug,

It did work. Thank you very much. However, there a few pecularities (
I guess I call them that). If I first start visual studio 2005 project
(i.e. wince 6.0 project) and then Platform Builder (wince 5.0), it
seems that in the connectivity options for the target I get
'DeviceEmulator' (DMA) rather than simply 'Emulator'. However, it is
not a bug deal. The x86 emulator now seems to work just fine. Thank
you very much again.

Regards,

Vadim.


Doug Cook (MS) wrote:
> Give this a try:
>
> If you have Macallan or PB for Windows Mobile 5.0 installed and PB 6.0 you
> will not be able to use the x86 emulator with the earlier version.
>
> A workaround is to copy emulatortransport_500.dll from "program
> files\windows ce platform builder\5.00\corecon\bin" or "program
> files\Platform builder for windows mobile\5.00\corecon\bin"
> to "program files\common files\microsoft shared\corecon\5.01\bin".
>