I am actually in the process of migrating 4.2 bsp to 5.0. My bsp was
working very well on 4.2. Now, i have migrated the catalog items, done bsp
migration( linked my bsp against the wince 5.0 libraries). Now, created the
nk.bin in debug mode after compiling the entire bsp without any ...

I have directory containing  ".cpp" and ".c" files (and " .h " ".hpp"_). I am
getting some error because of some compiler option not set correctly while
compiling .c file.
I have used "USER_C_FLAGS=($USER_C_FLAGS) /TP "  

hi?
I'm reviewing a bootloader assembly code from mainstone3 bsp.
From the startup code, I expected there were any branches to call both of
blmain and kernelstart.

Can somebody clarify me on following:
if GSM stack is part of Cellcore of WinCE or
is it part of the RIL driver or does the Windows Mobile device will have 2
processors  or the windows mobile device usually have 2 or more processor and

I did code formatting using the option, edit\advanced\format selection. it
is bydefault formatting the code with tabs. If we want to convert the tabs to
spaces, we have untabify selected lines. It is doing that with four spaces.
Does anyone have any idea about how to change that ...

i am using PXA 270 and i want to transfer nb0 files from PC with Wince 6.0
Eboot Usb Serial .
when i plug usb cable, activesync is trying to connect and after 30-40
seconds "Microsoft Activesync cannot recognize device ..." dialog appears.

Can fatfsd.dll be used in CE6?
But I can't find fatfsd in CE6.0 which originally is in
C:\WINCE500\PRIVATE\WINCEOS\COREOS\FSD\FATFS\. Does that mean we can only
use exfat.dll in CE6 because I can't build out fatfsd.dll~

does NdisMInitializeScatterGatherDma fiunction supported in WINCE 6.0? if not
then what should be the altrernative?
Thanks
-Tushar

A full debug image is just too slow and a full retail image is poor for
debugging.
I'd really like to be able to use a retail build ecxcept for the one driver
I'm debugging.

    I have a problem in building a folder targeting PLATFORM that NMAKE
don't know how to make 'TESTDEV.def'. But other folders with same contents of
SOURCES file except TARGET NAME and SOURCE files to be built, are built
without any error.Here i enclosed the build logs and ...

I'm looking at the behaviour of a serial device driver (my OEM's, not
mine). It's a fairly standard implementaton based on mdd.c,
pdd16550.cpp, com16550.cpp etc etc.
I'd like to be able to determine programatically what the buffer sizes

I am in the process of migrating 4.2 bsp to 5.0.. and i am facing an crash
in the os part..
my serail debug output is this...
************************************************************

We have an application that make use for RIL on Windows mobile. But our
target device is based on Wince5.0. Is it possible to port the RIL layer
to wince5.0. has anyone tried this approch.Or is there is a Windows
mobile RIL compatible layer for wince5.0.

We always set the build option prior to build a os design.
But I couldn't see any detail description for each build option.
For example, there isn't very detail explanation for a 'Enable eboot space
in memory' setting. What is it and how does it is affected to os build?

How do I enable ZONE_MEMORY from OEMInit?
My code is stopping in ProcInit() and I need to see the DEBUGMSG output from
this.
Thanks,