Re: Emulator and device problems with CF 2.0 and Visual Studio 200
- From: "Ilya Tumanov [MS]" <ilyatum@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 May 2005 12:37:46 -0700
Yes, you can change the CPU ID in your image to 2336 (PROCESSOR_ARM920).
You should know how to do it because you've changed it to 2577
(PROCESSOR_STRONGARM).
If not - look up CEProcessorType in PB help.
No, we're not shipping any other CABs, but we're considering removing CPU ID
from ARM CAB.
That comes at a price, so there's a chance we won't do it. I would advise
using default ID of 2336 on all CE5 ARMV4I images.
Best regards,
Ilya
This posting is provided "AS IS" with no warranties, and confers no rights.
"Olov N" <Olov N@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A6D1263-4337-4072-A6A8-9FF605DB6AC8@xxxxxxxxxxxxxxxx
> Hello,
>
> I'm experiencing the same problem. The cab file (NETCFv2.wce5.armv4i.cab)
> won't install on our device, a CE 5.0 device (PXA255 - CPU type: 2577
> 0xA11).
>
> Is there something we can do to make it install (we are building the ce
> image ourselves)?
> Will there be other CFv2 cab files available?
>
> Best regards
> Olov
>
> "John Roberts" wrote:
>
>> Hi Ilya,
>>
>> I reported this back to the company who is porting Windows CE 5.0 for us
>> and
>> it does appear to be a bug in the CE image. They are providing another
>> one
>> with the problem fixed and I'll let you know if there are any problems.
>>
>> Thanks for looking into this.
>>
>> - John
>>
>> "Ilya Tumanov [MS]" <ilyatum@xxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:426d5e74$1@xxxxxxxxxxxxxxxxxxxxx
>> > CF CAB expects CPU type to be 2336 (ARM920) for CE5 ARMV4I, thus it
>> > won't
>> > install on this device.
>> >
>> > What kind of device is it? Is it CE 5.0 device?
>> >
>> > Did you created CE image for it with platform builder or it came this
>> > way
>> > from some vendor? Thanks.
>> >
>> >
>> >
>> > Best regards,
>>
>>
>>
.
- Follow-Ups:
- References:
- Prev by Date: Re: TypeLoadException
- Next by Date: Re: TypeLoadException
- Previous by thread: Re: Emulator and device problems with CF 2.0 and Visual Studio 200
- Next by thread: Re: Emulator and device problems with CF 2.0 and Visual Studio 200
- Index(es):
Relevant Pages
|