A thought!!! [WinCE]

I was thinking about WinCE once. How can any improvement is possible in WinCE. I thought one part. Basically this part can be implemented by OEM as well but because of the special attribute of Microsoft to make OEM less worried about writing code and after that also they should get better performance by the WinCE compare to other competitive company.

Here I am going to suggest Microsoft that include DMA as native driver. These days every OEM always use DMA controller to do most of their transfer stuff and there is sort of standard in it too.Using those feature they can ask users to just fill some of their prototype and get the best DMA driver of it.

In the driver, even there can implement fuzzy logic which will increase the performance of the WinCE. As everybody know he benefit of fuzzy but many of coder don't use this technique as it is some what complex because it will affect RAM performance too. I guess MS can do it.

What should be prefix name? [WinCE]

One day, I was writing a sample driver. In the registry file platform.reg, while making entry for my sample driver, by mistake, I used S8M as prefix and it works fine.
I was surprised. Because I referred the link http://msdn.microsoft.com/en-us/library/aa447463.aspx
Which clearly says that "When you implement the stream interface, you designate the three-letter prefix. It can be any three letters, although you should use a common prefix, if your driver is the same class of device as other drivers".

It means it should not support other type of prefix.But it does. Just by seeing at the logic, I think that is correct way as other name like SM8 or 8SM does not work.
I am thinking whether it is wrong or write. But logically I agree this bug or wrong logic is correct but at the same time, MS should clearify in the same in their msdn part too. I think the time has come when people rely on article to resolve their problem. At this time it is must.
I would like everybody to share their reason to support or not support.

How to remove all prints from WinCE Image!!! [WinCE]

It is a common practice to remove all prints from the image which is going to ship to customer.

Now, depending on the requirement you can disable prints.
 Like, if you want to disable debugmsg and retailmsg, then set WINCE_SHIP=1. It does not mean that it will work for other OAL prints related funtion. But if you want that there should not be any prints at all then, you need to disable com port itself.

You need to check function OEMWriteDebugByte, which is taking care of debug port.

A Shortcut to Build your image!!!! [WinCE]

Hi,

Many times we see a problem of this dll is missing. What we do. We just find out the module compile it again and get dll and then build rel then make image. But think a scenario, when you have to include a dll which you can get only after sysgen the project. Looks cumbersome but there is a solution for it. The solution will give just a temporary solution so don't blindly rely on it.
Simply open ce.bib, then comment the particular dll by using semicolon(;).
Then run the command by opening the command window from menu bar(I guess name is like release to with msdos option. )
romimage                                                                   /location of ce.bib/ce.bib

This will give output file. Also you always need to modify ce,bib whenever you wan to build an image.

Why we should not use platform builder to include or exclude a module!!! [WinCE]

Many time we wish to remove or add a module in project. We usually follow two technique.
1. Edit the dirs file
2. Right click the module in platform builder and select exclude from build.

Both works fine.
But in few scenario, second option can cause problem.
Suppose you have two folder lets say A and B.
After building A, we get A.lib. And similarly after building B, we get B.dll but this B.dll uses A.lib to build successfully. Now if you want to remove B, so you would like to remove A and B, both. So you might use the sequence, First A then B or B first then A.
So in the same way, actually module get deleted from dirs file also. So once you plan to include, the module will be added at the end of dirs file. Hence once you choosed B first and then A. In that case, either the b.dll will not be build successfully or it will be build with old A.lib, hence your changes in A.Lib will not be reflected(if you are not going to build A.lib again).

Hence  it is wisely suggested that always edit dirs directly.