Hello,

The way to import a driver into your catalog is as follows.

In platform builder

1) File-> Manage Catalog Features-> Import

2) From here you will navigate to the driver that you want to import.

3) For instance I will navigate to this driver

C:\WINCE420\PUBLIC\lpd_Drivers\lpd_LH7A400_Audio_rel_100

4) From here you doubleclick on the .cec file

5) Click OK, now the driver has been added to your catalog.

6) Just to be sure that it is there, right click under catalog and click refresh.

Hope this helps.

Hi again,

I think cec file is being created under the directory you specified when I run the msi file. But when I try to install the msi file, it gives me the error and no cec file is created. I think the steps you specified must be run after the cec file is created.

When I start the Platform Builder it gives an output telling that catalog file couldn2t be initiailized. Can it be the source of the problem?

Thanks,

scinel,

This is pretty weird. Have you been able to install any of our *.msi files yet? We haven't had any problems with this that I know of. So I'm wondering if you need to reinstall your version of Platform Builder. Also, when you installed Platform Builder, did you install support for the ARM processors? Is you version of Platform Builder an evaluation version? If so, has it time-bombed out?

You are right that the *.msi file installs the *.cec file into the respective directory. If the install is failing, you might not have the directory created. Aaron, perhaps you can provide scinel with a zip file of the appropriate directory if his Platform Builder install is okay.

--mikee

Hi,

I can't any *.msi files yet. I have a problem with the Platform Builder. I have installed it to 2 other computers, but the same problem continued.

When I start the Platform Builder, it gives a warning "Unable to initialize catalog". I have investigated these errors from internet, and found one who has the same problems with me. If you want you can check it out from the bottom link.

http://msdn.microsoft.com...;exp=&sloc=en-us

I would be very glad if you can send me a zip file,

Thanks,
Sertaç Cinel

We have managed to solve the problem.

The problem occurs because our regional settings are configured as Turkish. When we adjust it to English(United States) the Platform Builder worked with no problem.

scinel,

I'm _very_ sorry that you encountered that problem. That must have been really frustrating. Could you please register your problem with Microsoft? I would like to make sure that they are aware of this issue.

Within Platform Builder, go to:

Help => Technical Support

This should bring up a list of phone numbers that you can call. Platform Builder itself comes with two free support calls through Microsoft. Since you are reporting what is most likely a bug, calling them shouldn't use up one of your two items.

I hope that your development proceeds smoothly from now on.

Best regards,
--mikee

Mikee,

We had reported the problem to Microsoft already. I also wanted to reported this to you to help anybody that can encounter with this problem. Because it's very bad to have such a "silly" problem. Now we can continue our design at last.

I have another question to you. Is it possible to run Windows PocketPC 2003 on Logic cards? If it is possible do we need a new BSP?

scinel,

Theoretically, yes it is possible to run PocketPC 2003 on the Logic hardware. In most cases though, this isn't an option. I'll try and explain why.

PocketPC uses Windows CE as its underlying operating system. From there, a special group inside Microsoft's mobile technology center tweaks the operating system, packages it with a certain set of applications, ensures that it includes a standard API, and calls it PocketPC. So, basically Microsoft treats PocketPC as a vertical market space (if you can put your marketing ears on for a minute ).

Because of the high-level of integration/optimization within PocketPC, Microsoft only supports ARM and XScale base processors with it. This is as opposed to Windows CE which also supports SH, x86, etc.

Since our A40x Card Engines are ARM-based, theoretically PocketPC could be built to run on them.

The problem is, Microsoft only licenses PocketPC to _very_ high volume customers. Examples are the Hewlett Packerd iPaq device. So, unless you are shipping a device in that kind of volume, Microsoft isn't very likely to work with you on porting/supporting PocketPC to your particular device.

Is there a particular feature you feel you need from PocketPC that you aren't finding in WindowsCE?

--mikee

Michael,

Thank you for your detailed answer to my question. We did not know the differences between Pocket PC and Win CE very well. But your answer clarified lots of things in our minds.