WINCE 6 activesync

Hello,
I follow all the steps printed in the good tutorial of domodom,, but today
activesync is still not working ( works with CE5.0).

I regenerate an image in visual studio where i check :
- CoreOS/cebase/Application-enduser/ActiveSync
- CoreOS/cebase/CoreOs services/USB Host support/ USB remote NDIS Class
Driver
-Device driver/USB function/USB function client/Mass storage, RNDIS client
and serial.

When i run the image, active sync detects anything, and no connection is
detected by the mini2440.

Please have you any ideas ?
thks

fred

Hello,

My activesync still not work although i think i follow all the domdom's
steps.

I note an other pb: when i build the CE image in visual studio by selecting
"Build\ build mini2440 release", the image is generated, but is alway at
22Mb, even if i change some components in the catalog. If i build selecting
"advanced build settings\sysgen", i have random compilation failure ( no
specific module, it could be wininet.dll, ole32.dll ... depends on time
.... ).

Please can you give me some advice ?
Thank you
Fred

Try to make a sysgen clean.
And delete the old nk.bin to be sure that the nk.bin is generated.
domodom

Hi domodom,
I kill all the re-generated directories, and my compilation passes
successfully. But the actual nk.bin always stays at 22Mb, and activesync
still not work.
I check all the items of CEBase/core os services/Usb host support (
including Remote ndis driver ).

some remarks :
-In the mini2440, i cannot find regedit to look into the registry...

What are the dll i need in the mini2440 to execute activesync ?

Thank you for your help
fred

Another test you can make is to use the english BSP downloadable on this
site. Activesync should work.
I don't have better idea... (for the moment ?) 
Domodom

Hello,
i try this and i have the same behaviour.
I note someting else in visual studio : in the Third party, i would like to
ckeck usbfunctions. when i select it, a red cross appears... is it an
installation problem of the bsp or the compiler ?

Fred

During boot, i get the following message :

Exception 'Data Abort' (4): Thread-Id=04160002(pth=83a82600),
Proc-Id=00400002(pprc=82008308) 'NK.EXE', VM-active=048b0002(pprc=839ffe10)
'explorer.exe'
PC=c092b790(sc2440usbfn.dll+0x0000b790)
RA=c092b788(sc2440usbfn.dll+0x0000b788) SP=d2adfdc0, BVA=00000007

I really think there is a pb with the "sc2440usbfn.dll".
I try to recompile it manually, but i get the same error...

I work on the subject again, and i ask me if the problem doesn't come from
my software configuration : i use visual studio 2005 on WINDOWS VISTA :
does anyone use vista as OS ???

Fred

Yes I'm running on vista, and cant figure out how the make this os to
compile.

Did you install Service pack for Vs2005 for vista?
http://www.microsoft.com/downloads/details.aspx?familyid=90e2942d-3ad1-4...

now it's working....
VS2005 was not faulty but i had to install all packages of windows ce, up
to wince R3.
And now ( maybe due to the correct framework ) all demos of friendlyarm
work ( i2c, leds, screen, button )...

Fred

I installed VS2005 succesfully.
I also installed CE Tools and all the releases from MS Site up to R3.
When I open the BSP I get a list of errors.
Look at this image   http://www.eyegps.gr/vs2005.png

Any ideas ?
Am I missing sth ?

Thanks

My problem seems to be just like fred_from_france's. But I have already
installed wince 6 up to R3. I still have the problem that no connection or
unknown device is detected in my pc while connected to mini2440 running
wince 6