can't debug on Pocket PC 2003 with eVC++ 3.0 ?

I have trouble debugging on a Pocket PC 2003 device using eVC++ 3.0.

Is that a known problem ?

I never had any problem debugging on Pocket PC 2002 devices using eVC++ 3.0.

The reason I use eVC++ 3.0 is because I want to keep support for older
Pocket PCs (2000 and 2002) and at the time I am not using any specific
feature of 2003. In addition, the C/C++ compiler of eVC++ 3.0 generates
code that is faster than that generated by the eVC++ 4.0 compiler...

Doug
Tue Jan 20 20:03:00 CST 2004

> I have trouble debugging on a Pocket PC 2003 device using eVC++ 3.0.

Trouble? If you got that far you are doing better than me. You are not
supposed to be able to do it at all.
AFAIK you must use eVC4's platform manager for debugging PPC2003 and eVC3's
for older platforms and the two platform managers cannot coexist on the same
OS, but I would love to be wrong about this. Regarding code speed my
subjective (and therefore fallible) impression is the opposite of yours.

Cheers

Doug Forster

"The PocketTV Team" <do-not-reply-by-email@pockettv.com> wrote in message
news:uL7RaA83DHA.632@TK2MSFTNGP12.phx.gbl...
> I have trouble debugging on a Pocket PC 2003 device using eVC++ 3.0.
>
> Is that a known problem ?
>
> I never had any problem debugging on Pocket PC 2002 devices using eVC++
3.0.
>
> The reason I use eVC++ 3.0 is because I want to keep support for older
> Pocket PCs (2000 and 2002) and at the time I am not using any specific
> feature of 2003. In addition, the C/C++ compiler of eVC++ 3.0 generates
> code that is faster than that generated by the eVC++ 4.0 compiler...
>
>

The
Tue Jan 20 20:19:46 CST 2004

"Doug Forster" <doug_ZAPTHIS_AT_TONIQ_ZAPTHIS_co.nz> wrote in message
news:%23x4JwK83DHA.1752@tk2msftngp13.phx.gbl...
> > I have trouble debugging on a Pocket PC 2003 device using eVC++ 3.0.
>
> Trouble? If you got that far you are doing better than me. You are not
> supposed to be able to do it at all.
> AFAIK you must use eVC4's platform manager for debugging PPC2003 and
eVC3's
> for older platforms and the two platform managers cannot coexist on the
same
> OS, but I would love to be wrong about this. Regarding code speed my
> subjective (and therefore fallible) impression is the opposite of yours.

My impression about speed is not an impression. It just based on actual
timings measurements, and was independently confirmed by the PocketMVP
developers. But the results may depend on the type of application. In our
case, video.

I'm no so sure avout eVC++ 4.0 no co-existing with eVC++ 3.0 . I have had
both installed on the same development system for quite a while, and never
had problems.

The
Tue Jan 20 20:39:46 CST 2004

> and the two platform managers cannot coexist on the same
> OS, but I would love to be wrong about this.

I did some more tests, and I found no problem, both eVC++ 3.0 and 4.0 can
co-exist. But the project files format are not compatible, so you need
separate project files.

But that's off topic. My question was about debugging on a Pocket PC 2003
using eVC++ 3.0. I wonder why MSFT broke the compatibility there...

Suvrat
Tue Jan 20 23:50:03 CST 2004

Yeah, unfortunately that does not work. I had to per-force install evc4 just
because I needed to debug code on Pocket PC 2003. And, yes, evc3.0 and
evc4.0 are co-existing on my machine with no problems whatsoever.

Suvrat


"The PocketTV Team" <do-not-reply-by-email@pockettv.com> wrote in message
news:eAIcTf83DHA.1752@tk2msftngp13.phx.gbl...
> > and the two platform managers cannot coexist on the same
> > OS, but I would love to be wrong about this.
>
> I did some more tests, and I found no problem, both eVC++ 3.0 and 4.0 can
> co-exist. But the project files format are not compatible, so you need
> separate project files.
>
> But that's off topic. My question was about debugging on a Pocket PC 2003
> using eVC++ 3.0. I wonder why MSFT broke the compatibility there...
>
>

Doug
Wed Jan 21 13:30:15 CST 2004

Sure. No problem with eVC3 and eVC4 - just the platform managers. I use a
separate partition / OS - one for each environment, then you can have both
but you have to reboot between.

"The PocketTV Team" <do-not-reply-by-email@pockettv.com> wrote in message
news:eAIcTf83DHA.1752@tk2msftngp13.phx.gbl...
> > and the two platform managers cannot coexist on the same
> > OS, but I would love to be wrong about this.
>
> I did some more tests, and I found no problem, both eVC++ 3.0 and 4.0 can
> co-exist. But the project files format are not compatible, so you need
> separate project files.
>
> But that's off topic. My question was about debugging on a Pocket PC 2003
> using eVC++ 3.0. I wonder why MSFT broke the compatibility there...
>
>

The
Wed Jan 21 16:43:15 CST 2004


"Doug Forster" <doug_ZAPTHIS_AT_TONIQ_ZAPTHIS_co.nz> wrote in message
news:ugjA7TF4DHA.1636@TK2MSFTNGP12.phx.gbl...
> Sure. No problem with eVC3 and eVC4 - just the platform managers. I use a
> separate partition / OS - one for each environment, then you can have both
> but you have to reboot between.

I have both on the same XP-pro partition and I don't need reboot to switch
between eVC++ 3.0 and 4.0. And I can connect to Pocket PC 2000, 2002 and
2003 without having to reboot the OS.

So using separate partitions does not seem necessary... at least for me.