how can the build-tool build a dll when source file says "TARGETTY

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Cxport thread busy Hi, Is Cxport.dll only associated with network based devices or with input devices too, such as mouse, keyboard or USB? I have set NoIdleTimerReset but still there is high CPU activity. Is PS2 based mouse/keybd/USB power aware. Any suggestions would be greatly appreciated. Ansuya Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84880
  - 2
    - PB's emulator inside a virtual machine For the record: it can be done - I'm doing it under VMWare. Thanks to Barry Bond (appropriately enough, his title is "Architect") for the encouragement at the MEDC, even if his idea didn't pan out. -- #include <standard.disclaimer> _ Kevin D Quitt USA 91387-4454 96.37% of all statistics are made up Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84879
  - 3
    - remove unwanted project I added some projects to my platform and want to remove them. I right click on the project, but the "remove" menu item is disabled. Tapping on delete button also doesn't work. I searched the form and found a thread about DIRS related to this issue. But I haven't found any DIRS that have my projects in it. Any suggestion on this? Thanks! Richard Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84878
  - 4
    - repllog.exe and rnaapp.exe Hello, I have a problem of the rnaapp.exe is excecuted everytime i retun from suspend mode. It than shows the message box of "connecting to host" even if no USb cable is attached. It would like to eliminate it. Can someone please explain me what is the sequence in the system which initiates the load of repllog.exe, which than loads rnaapp.exe. Please, any help would be appreciated. Oren. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84876
  - 5
    - USB device not recognized on power-up (CE-5.0) If either a USB mouse, or USB touchscreen, (drivers included into OS image), is connected to the USB-2.0 port upon power-up they aren't initialized. I have to disconnect and reconnect them then they're recognized and work However, if a standard memory stick is plugged in upon power-up it is recognized. Any ideas what could be wrong, or how to correct this? Thanks Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84863
  - 6
    - Compile SD_API_SUCCESS function with error. Hi all, I use SD_API_SUCCESS in my function like this : " SD_API_STATUS My_function (para,.....) { SD_API_STATUS RequestStatus; ...... ...... if (!SD_API_SUCCESS(RequestStatus)){ return RequestStatus; } } " When I build my driver, system report : error C2220: warning treated as error - no 'object' file generated : [01:0000000036:WARNN ] d:\wince500\public\common\oak\drivers\sds\xxxx.cpp( warning C4715: 'My_function': not all control paths return a value I also found that if I comment the SD_API_SUCCESS function and let My_function return RequestStatus directly, like this : " SD_API_STATUS My_function (para,.....) { SD_API_STATUS RequestStatus; ...... ...... return RequestStatus; } " then, it can be build successfully. Do you know what's the matter in My_function ? Thanks for your help. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84861
  - 7
    - Why are SYSGEN vars not set? Hello experts I'm using PB5.0 and wonder whether this is a bug or desired behaviour: If I create a new custom platform based on my BSP and add some standard components e.g. "Standard Shell" to the platform, the PB IDE automatically adds e.g. "Minimal GDI Configuration" to my platform. I think this is a very useful feature. But if I call "Open Release Directory" and do a set command, I see that SYSGEN_MINGDI isn't set. Is this ok? SYSGEN_MINGDI does only get set, if I add "Minimal GDI Configuration" directly to my platform. Why is there a difference? Is this a bug? -- Michael Reim reim AT helmut-fischer DOT de Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84859
  - 8
    - 80X flash memory with winCE well guys can any 1 tell me, whether the flash memory having 80x data transfer rate will work with windows CE. i m using PCM 6892 card. and since years i have been using 45X Flash memory, but when i inserted 80X flash, it shows "invalid system disk". i also checked that, if i load the same flash with linux image, it works fine with the same board. so now can any 1 tell me whether 80X is supported with winCE5.0 ? thanx in advance Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84858
  - 9
    - Problems with corrupted hv-files generated from regcomp during makeimg Hello together, we have serious problems with corrupted hv-files generated from regcomp during makeimg. For building our Windows CE 4.2 image we call cepb from a batch file during our automatic build process. For a couple of builds (about 30%) the resulting nk.bin does not boot correctly on the target device (the filesystem does not start up correctly and the device hangs). The difference between a "good" and a "corrupt" image is only within the .hv-file within the flat release directory (boot.hv, default.hv and user.hv). These are generated from regcomp.exe during makeimg from the reginit.ini file. The difference of the binary hv-files is not only in the beginning part of the file (where there seems to be some random information (mostly the environment variables from the build machine), which are used for padding the files) but also in the back of the file, where the essential information seems to be. We have this difference even if we call regcomp.exe in the flat release directory ("regcomp reginit.ini .") as opposed to calling makimg (from the same build command line). Anyone ever had similar problems? Any idea on how to avoid these problems? In the meantime we have changed the registry settings a little bit, so that we have a different reginit.ini as input. The first tries worked, but who knows if the problem appears again. We can provide our reginit.ini and even the whole flat release directory to Microsoft for further investigation. Regards, Thomas Hensler BTW: We use PB 4.2 with the QFEs installed (which once patched regcomp.exe already). Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84857
  - 10
    - How to cancel/abort IObex::BindToDevice or BthAuthenticate? We are developing a Bluetooth device with MS Window CE 5.0 Bluetooth stack and are now seing a huge problem. We have found that the IObex::BindToDevice method and the BthAuthenticate seem to be blocking calls until the peer device sends an accept or reject. Yet we have not found anyway to cancel/abort such these calls or configure any timeout values for these. Does anyone know if it is possible and if so, how? If it is not possible, how is this API suppose to work properly? Thanks, Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84856
  - 11
    - Halt phenomenon after OEMInit() in AU1200 I am using AMD Alchemy AU1200(MIPS) processor. After executing OEMInit(), no more debug message, just halted. The debug message as follows. DEBUG MESSAGE -------------------------------------------------------------------------------- KitlTransport requested active mode. (PRId 04030201) @ 396MHZ Booting Windows CE version 5.00 for (MIPS32) MIPS16 Instructions NOT Supported &pTOC = 8110109c, pTOC = 829f1444, pTOC->ulRamFree = 82a64000, MemForPT = 00000000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 21909, Secondary pages: 0, Filesystem pages = 10954 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 82a65000, extension: 00006000, length: 05595000 Windows CE KernelInit Updated eptr->e32_vsize to = 000b1000 Scheduling the first thread. <END> ----------------------------------------------------------------------------------- Thanks in advance. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84854
  - 12
    - struct ROMHDR and pTOC When I debug bootloader I was so much confused by the struct ROMHDR and the pointer pTOC. would someone please tell me who will change pTOC and where pTOC is made point. I didn't see pToc got changed explictlly. the most important is I find the information about struct ROMHDR in MSDN is too much simply to get understaood, would someone please explain every single member in that struct in detail for me? thanks so much! Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84853
  - 13
    - FAT Cache Pre-Warming Hello, how often is the pre-warming function of the FATFS cache triggered? Once during boot or repeatedly during runtime? Regards Peter Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84852
  - 14
    - Difference between Data cache and FAT cache Hello, as I have seen there are now two registry keys to configure the cache oft the FATFS (DataCacheSize, FatCacheSize). Can somebody explain the difference between Data cache and FAT cache? Regards Peter Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84851
  - 15
    - where have the thai language lib use for pb4.2! i use the wince50 lib of thai but can display all of them! where have the thai language lib use for pb4.2! i use the wince50 lib of thai but can display all of them! Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84835
  - 16
    - waking threads Hi, Why do mouse, keyboard keep on giving WaitForSingleObject every few seconds even though their dwTimeout is INFINITE... I have checked via remote kernel tracker and I see every few second either USB or some other thread unblocks and Waits for object and again blocks. Is there a way to increase this wait (it is infinite?) and there is no user input, no pressing of mouse, nothing. Is it related with idle timer settings in reg files. But then how can the system is go into idle mode when the threads keep on waking... Thanks, Ansuya Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84833
  - 17
    - genblt library Does anyone understand what the genblt library does in CE 5.0 ? It is linked into GPE, but doesn't appear to be activated unless registry key HKLM\Drivers\Display\GPE UseGenBlt is set. Doesn't look like anyone does that as far as the supplied drivers. Don't see anything in the help either. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84832
  - 18
    - Scandisk in CE.Net 4.2 I am working with WinCE 4.2 and am attempting to use the ScanVolumeEx api to perform a periodic scan of the internal CF drive on the embedded device. When testing with a known good CF, the scan returns with no problems found. When testing with a known corrupt CF (fails chkdsk on PC). (Note: CF is FAT16) I have experienced two different issues. 1) I get "Datatype Misalignment" exception during 2nd call to HeapAlloc in GetFreeDirEntry(..) function in scandisk.cpp. (2nd call @ end of dir entry) (Note: after numerous attempts at debugging, hundreds of FILE*.CHK files were created on the root drive. At some point I began getting too many files in root and GetFreeDirEntry(..) faulted prior to calling the HeapAlloc() and exceptions stopped.) 2) With a known bad CF, scandisk does not detect failures that chkdsk detects and returns with No problems found. Does CE 5.0 have new and improved scandisk capabilty? Are there fixes for 4.2? Are there other utilities available? Any ideas? Thanks -- JMarti Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84826
  - 19
    - Slow Build Platform Under XP servicePack 2 Hi, I work on a fast (for me) PC (pentium 4 3.60 GHz with A 10000rpm SATA disk & 1Giga memory) The installed OS was WindowsXP servicePack 1. I build my platform CEPC projects very fast! about 5 minutes! I was very happy! Yesterday I Install ServicePack 2 and my build time slow down to 00:07:30 minutes (???!!!). I try to shutdown Firewall, Security control and so on. But nothing works(sigh!!) I disinstall ServicePack 2 and my build time return to about 5 minutes! May anyone help me Thank Ruggero Bandera Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84822
  - 20
    - Debug build error in Shell.exe --____OSGGVNVQDWWTHZGAXUFB____ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I'm using WinCE 5.0. My release build works fine. But debug build hangs = while loading shell.exe. The debug messages are as follows: Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:21:58 ProcessorType=3D02d0 Revision=3D6 sp_abt=3Dffff5000 sp_irq=3Dffff2800 sp_undef=3Dffffc800 OEMAddressTable = =3D 800b9d44 OEMInit ++ OEMInit -- Booting Windows CE version 5.00 for (ARM) &pTOC =3D 800c2d9c, pTOC =3D 80f6ab08, pTOC->ulRamFree =3D 80fc9000, = MemForPT =3D 00000000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 3309, Secondary pages: 0, Filesystem pages =3D = 1654 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 80fca000, extension: 00001000, length: 00ced000 Sp=3Dffffc7cc ARMInit done. Windows CE KernelInit Updated eptr->e32_vsize to =3D 000bc000 Scheduling the first thread. 0x81cb7024: KernelInit2: pCurThread=3D81cb7024 hCurThread=3D01cb7266 = hCurProc=3D01cb7002, KernelInit =3D 800df650 0x81cb7024: Detecting VFP...0x81cb7024: VFP Not Found! 0x81cb7024: Updated eptr->e32_vsize to =3D 00006000 0x81cb7024: first =3D 01f30000, last =3D 02000000, SharedDllBase =3D = 03190000 0x81ca1288: CertMod.dll not found, using old OEM Trust Model 0x81ca1288: FileSystem Starting - starting with clean file system 0x81ca1288: FS: initializing ROM/RAM file system 0x81ca1288: SC_CreateAPIHandle: pvData =3D=3D NULL 0x81ca1288: FS: Registering file system ROM, index 2, flags 0x00000031 0x81ca1288: FS: Mount complete (ROM, index 2, flags 0x00000031) 0x81ca1288: Succeeded on CheckFile 0x81ca1288: RestoreFile(0xe1c8cf02) called fDelete =3D TRUE 0x81ca1288: FS: Registering file system StoreMgr, index 3, flags 0x00000001= 0x81ca1288: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MA= CHINE\init\BootVars 0x81ca1288: FSREG: Logging in default user. 0x81ca1288: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACH= INE\init\BootVars 0x81ca1288: SetCurrentUser: Logging out (nobody), logging in default 0x81ca1288: FS: Using default path "\profiles\" 0x81ca1288: BuildPath: profiles 0x81ca1288: BuildPath: profiles\default 0x81ca1288: SetCurrentUser: User hives not supported -- using same = registry for all users 0x81ca1288: FS: Using default path "Windows\" 0x81ca1288: FS: Using default path "Windows\" 0x81ca1288: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\= init\BootVars 0x81ca1288:=20 Initializing Database 0x81ca1288: DB:Validation: Name already exists DB_notify_events 0x81ca1288: DB:CeCreateDatabase failed 0x81ca1288: DB:Validation: Name already exists DB_notify_events 0x81ca1288: DB:CeCreateDatabase failed 0x81ca1288: ERROR: c:\macallan\private\winceos\coreos\filesys\dbase\initdb.= c line 535: 0x81ca1288: Conflict with existing database DB_notify_events = on line 385 0x81ca1288: Filesystem initialized! 0x81ca1288: FILESYS: Waiting for kernel to be ready to launch apps 0x81ca4b68: InitMUI: DISABLED (-1039860968) 0x81ca1288: FS: Creating signal event SYSTEM/DevMgrApiSetReady 0x81ca1288: FS: Creating signal event SYSTEM/PowerManagerReady 0x81ca1288: FS: Creating signal event SYSTEM/GweApiSetReady 0x81ca1288: FS: Creating signal event ReleaseFSD 0x81ca1288: FS: Creating signal event system/events/notify/APIReady 0x81ca1288: FS: Creating signal event SYSTEM/ShellAPIReady 0x81ca1288: FILESYS: Launching apps 0x81ca1288: FILESYS: Launching shell.exe 0x81c7da70: Prefetch Abort: Thread=3D81c7da70 Proc=3D80fbc5e0 'shell.exe' 0x81c7da70: AKY=3D00000005 PC=3D0002b000(shell.exe+0x0001b000) RA=3D03e21db= 4(toolhelp.dll+0x00001db4) BVA=3D0002b000 FSR=3D000004f0 0x81c7da70: Prefetch Abort: Thread=3D81c7da70 Proc=3D80fbc5e0 'shell.exe' 0x81c7da70: AKY=3D00000005 PC=3D0007f7c4(shell.exe+0x0006f7c4) RA=3D03e21fb= 0(toolhelp.dll+0x00001fb0) BVA=3D0007f7c4 FSR=3D000004f0 Any help is appreciated. Thanks Anand --____OSGGVNVQDWWTHZGAXUFB____ Content-Type: multipart/related; boundary="____FQSXIGXTRURSEYLMRUNN____" --____FQSXIGXTRURSEYLMRUNN____ Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"= > <META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD> <BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma"> <DIV>Hi,</DIV> <DIV>I'm using WinCE 5.0. My release build works fine. But debug build = hangs while loading shell.exe.</DIV> <DIV><BR>The debug messages are as follows:</DIV> <DIV>Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at = 18:21:58<BR>ProcessorType=3D02d0  Revision=3D6<BR>sp_abt=3Dffff5000 = sp_irq=3Dffff2800 sp_undef=3Dffffc800 OEMAddressTable =3D 800b9d44<BR>OEMIn= it ++<BR>OEMInit --<BR>Booting Windows CE version 5.00 for (ARM)<BR>&pT= OC =3D 800c2d9c, pTOC =3D 80f6ab08, pTOC->ulRamFree =3D 80fc9000, = MemForPT =3D 00000000</DIV> <DIV> </DIV> <DIV>Old or invalid version stamp in kernel structures - starting = clean!<BR>Configuring: Primary pages: 3309, Secondary pages: 0, Filesystem = pages =3D 1654</DIV> <DIV> </DIV> <DIV>Booting kernel with clean memory configuration:<BR>Memory Sections:<BR= >[0] : start: 80fca000, extension: 00001000, length: 00ced000<BR>Sp=3Dffffc= 7cc<BR>ARMInit done.<BR>Windows CE KernelInit<BR>Updated eptr->e32_vsize= to =3D 000bc000<BR>Scheduling the first thread.<BR>0x81cb7024: KernelInit2= : pCurThread=3D81cb7024 hCurThread=3D01cb7266 hCurProc=3D01cb7002, = KernelInit =3D 800df650<BR>0x81cb7024: Detecting VFP...0x81cb7024:  = VFP Not Found!<BR>0x81cb7024: Updated eptr->e32_vsize to =3D 00006000<BR= >0x81cb7024: first =3D 01f30000, last =3D 02000000, SharedDllBase =3D = 03190000<BR>0x81ca1288: CertMod.dll not found, using old OEM Trust = Model<BR>0x81ca1288: FileSystem Starting - starting with clean file = system<BR>0x81ca1288: FS: initializing ROM/RAM file system<BR>0x81ca1288: = SC_CreateAPIHandle: pvData =3D=3D NULL<BR>0x81ca1288: FS: Registering file = system ROM, index 2, flags 0x00000031<BR>0x81ca1288: FS: Mount complete = (ROM, index 2, flags 0x00000031)<BR>0x81ca1288: Succeeded on CheckFile<BR>0= x81ca1288: RestoreFile(0xe1c8cf02) called fDelete =3D TRUE<BR>0x81ca1288: = FS: Registering file system StoreMgr, index 3, flags 0x00000001<BR>0x81ca12= 88: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\in= it\BootVars<BR>0x81ca1288: FSREG: Logging in default user.<BR>0x81ca1288: = FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\Boo= tVars<BR>0x81ca1288: SetCurrentUser: Logging out (nobody), logging in = default<BR>0x81ca1288: FS: Using default path "\profiles\"<BR>0x81ca1288: = BuildPath: profiles<BR>0x81ca1288: BuildPath: profiles\default<BR>0x81ca128= 8: SetCurrentUser: User hives not supported -- using same registry for all = users<BR>0x81ca1288: FS: Using default path "Windows\"<BR>0x81ca1288: FS: = Using default path "Windows\"<BR>0x81ca1288: FSREG: Unable to read value = "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars<BR>0x81ca1288: <BR>Initial= izing Database<BR>0x81ca1288: DB:Validation: Name already exists DB_notify_= events<BR>0x81ca1288: DB:CeCreateDatabase failed<BR>0x81ca1288: DB:Validati= on: Name already exists DB_notify_events<BR>0x81ca1288: DB:CeCreateDatabase= failed<BR>0x81ca1288: ERROR: c:\macallan\private\winceos\coreos\filesys\db= ase\initdb.c line 535: 0x81ca1288: Conflict with existing database = DB_notify_events on line 385<BR>0x81ca1288: Filesystem initialized!<BR>0x81= ca1288: FILESYS: Waiting for kernel to be ready to launch apps<BR>0x81ca4b6= 8: InitMUI: DISABLED (-1039860968)<BR>0x81ca1288: FS: Creating signal = event SYSTEM/DevMgrApiSetReady<BR>0x81ca1288: FS: Creating signal event = SYSTEM/PowerManagerReady<BR>0x81ca1288: FS: Creating signal event = SYSTEM/GweApiSetReady<BR>0x81ca1288: FS: Creating signal event ReleaseFSD<B= R>0x81ca1288: FS: Creating signal event system/events/notify/APIReady<BR>0x= 81ca1288: FS: Creating signal event SYSTEM/ShellAPIReady<BR>0x81ca1288: = FILESYS: Launching apps<BR>0x81ca1288: FILESYS: Launching shell.exe<BR>0x81= c7da70: Prefetch Abort: Thread=3D81c7da70 Proc=3D80fbc5e0 'shell.exe'<BR>0x= 81c7da70: AKY=3D00000005 PC=3D0002b000(shell.exe+0x0001b000) RA=3D03e21db4(= toolhelp.dll+0x00001db4) BVA=3D0002b000 FSR=3D000004f0<BR>0x81c7da70: = Prefetch Abort: Thread=3D81c7da70 Proc=3D80fbc5e0 'shell.exe'<BR>0x81c7da70= : AKY=3D00000005 PC=3D0007f7c4(shell.exe+0x0006f7c4) RA=3D03e21fb0(toolhelp= .dll+0x00001fb0) BVA=3D0007f7c4 FSR=3D000004f0</DIV> <DIV> </DIV> <DIV>Any help is appreciated.</DIV> <DIV> </DIV> <DIV>Thanks</DIV> <DIV>Anand</DIV></BODY></HTML> --____FQSXIGXTRURSEYLMRUNN____-- --____OSGGVNVQDWWTHZGAXUFB____-- Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84815
  - 21
    - How to refer to Secure Digital Card Function Hi all, I want to refer to Secure Digital Card Driver Functions in my driver in the IDE of wince 50 with platform builder. But when I build the whole platform, system report : " sdcardlib.lib(sdmisc.obj) : error LNK2001: unresolved external symbol dpCurSettings BUILD: [01:0000003281:ERRORE] sdcardlib.lib(sddebug.obj) : error LNK2001: unresolved external symbol dpCurSettings BUILD: [01:0000003282:ERRORE] sdcardlib.lib(sdmemapi.obj) : error LNK2001: unresolved external symbol dpCurSettings BUILD: [01:0000003283:ERRORE] sdcardlib.lib(sdcardapistubs.obj) : error LNK2001: unresolved external symbol dpCurSettings BUILD: [01:0000003284:ERRORE] sdcardlib.lib(sdcardapistubs.obj) : error LNK2019: unresolved external symbol SDGetClientFunctions referenced in function SDRegisterClient " Please help me to find the error in the following things I have done. Firstly, I added this at begin of my xxxx.cpp file, such as #include <sdcardddk.h>, because I use the function of SDGetDeviceHandle(para1,para2) in my code; Secondly, I made a folder named sds in the directory of WINCE500\PUBLIC\COMMON\OAK\DRIVERS, and added a line " sds \" in the upper dir files ; Thirdly, I wrote reference paths in the sources file in sds directory like this: _ISVINCPATH=$(_WINCEROOT)\public\common\sdk\inc; _OEMINCPATH=$(_WINCEROOT)\public\common\oak\inc;$(_WINCEROOT)\public\common\sdk\inc;$(_WINCEROOT)\public\common\ddk\inc; TARGETLIBS=\ $(_PROJECTROOT)\cesysgen\sdk\lib\$(_CPUINDPATH)\coredll.lib \ $(_PROJECTROOT)\cesysgen\oak\lib\$(_CPUINDPATH)\sdcardlib.lib \ Where is the mistake ? Thanks for you help. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84814
  - 22
    - Error while building USBHID driver on WinCE 5.0 Hello. I'm trying to build USBHID driver on Windows CE 5.0. when calling "sysgen" I'm getting this error: "The system cannot find the path specified." see full log below. I suspect that my mistake was creating the OS in the wrong path, or placing the HID drivers in the wrong path. I created the OS in "C:\WINCE500\PBWorkspaces\test1\WINCE500". I put the HID driver in "C:\WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x86\Drivers\USB\CLASS\HID". That's where I call "sysgen" and "build -c" from. Is that the case? if not - any idea what is the problem? Thanks, Eddie. ------------------------------------------------------------- cmd log: ----------- SYSGEN_WATSON_XFER=1 Checking for uncleared variables Done checking for uncleared variables Report: SYSGEN_ATL=1 SYSGEN_AUDIO=1 SYSGEN_AUTH=1 SYSGEN_AUTH_NTLM=1 SYSGEN_AUTH_SCHANNEL=1 SYSGEN_AUTORAS=1 SYSGEN_AYGSHELL=1 SYSGEN_BATTERY=1 SYSGEN_BTH=1 SYSGEN_BTH_AG=1 SYSGEN_CERTS=1 SYSGEN_COMMCTRL=1 SYSGEN_COMMDLG=1 SYSGEN_CONNMC=1 SYSGEN_CORELOC=1 SYSGEN_CORESTRA=1 SYSGEN_CPP_EH_AND_RTTI=1 SYSGEN_CREDMAN=1 SYSGEN_CRYPTO=1 SYSGEN_CTLPNL=1 SYSGEN_CURSOR=1 SYSGEN_DEVICE=1 SYSGEN_DISPLAY=1 SYSGEN_DOTNET=1 SYSGEN_DOTNET_SUPPORT=1 SYSGEN_EAP=1 SYSGEN_ETHERNET=1 SYSGEN_ETH_80211=1 SYSGEN_FMTMSG=1 SYSGEN_FONTS_TAHOMA_1_07=1 SYSGEN_FSADVERTISE=1 SYSGEN_FSDBASE=1 SYSGEN_FSPASSWORD=1 SYSGEN_FSREPLBIT=1 SYSGEN_FULL_CRT=1 SYSGEN_GRADFILL=1 SYSGEN_HELP=1 SYSGEN_IABASE=1 SYSGEN_IE_JSCRIPT=1 SYSGEN_IMAGING=1 SYSGEN_IMAGING_BMP_DECODE=1 SYSGEN_IMAGING_GIF_DECODE=1 SYSGEN_IMAGING_JPG_DECODE=1 SYSGEN_IMAGING_PNG_DECODE=1 SYSGEN_IMM=1 SYSGEN_IPHLPAPI=1 SYSGEN_IRDA=1 SYSGEN_LDAP=1 SYSGEN_MENU_OVERLAP=1 SYSGEN_MINGDI=1 SYSGEN_MINGWES=1 SYSGEN_MININPUT=1 SYSGEN_MINWMGR=1 SYSGEN_MLANG=1 SYSGEN_MSGQUEUE=1 SYSGEN_MSIM=1 SYSGEN_MSMQ=1 SYSGEN_MSXML_DOM=1 SYSGEN_MSXML_SAX=1 SYSGEN_MSXML_XQL=1 SYSGEN_NDIS=1 SYSGEN_NDISUIO=1 SYSGEN_NKCOMPR=1 SYSGEN_NKMAPFILE=1 SYSGEN_NLED=1 SYSGEN_NOTIFY=1 SYSGEN_OBEX_CLIENT=1 SYSGEN_OBEX_SERVER=1 SYSGEN_OLE=1 SYSGEN_PM=1 SYSGEN_PPP=1 SYSGEN_PRINTING=1 SYSGEN_QVGAP=1 SYSGEN_REDIR=1 SYSGEN_SERDEV=1 SYSGEN_SERVICES=1 SYSGEN_SHELL=1 SYSGEN_SOAPTK_CLIENT=1 SYSGEN_SOFTKB=1 SYSGEN_STANDARDSHELL=1 SYSGEN_STDIO=1 SYSGEN_STDIOA=1 SYSGEN_STOREMGR=1 SYSGEN_STRSAFE=1 SYSGEN_TAPI=1 SYSGEN_TCPIP=1 SYSGEN_TCPIP6=1 SYSGEN_TIMESVC_API=1 SYSGEN_TIMESVC_DST=1 SYSGEN_TOOLHELP=1 SYSGEN_TOUCH=1 SYSGEN_URLMON=1 SYSGEN_USDK=1 SYSGEN_WATSON_CLIENT=1 SYSGEN_WATSON_CTLPNL=1 SYSGEN_WATSON_DMPGEN=1 SYSGEN_WATSON_XFER=1 SYSGEN_WEBVIEW=1 SYSGEN_WININET=1 SYSGEN_WINSOCK=1 The system cannot find the path specified. CE_MODULES=coredll nk stansdk msim commctrl commdlg shell relfsd loaddbg shellce log osaxst0 secur32 ntlmssp spnego schannel rsaenh crypt32 msasn1 credman prnpor t prnerr notify rnaapp connmc ndispwr netui wldap32 tcpstk tcpip6 ipv6hlp dhcpv6 l irdastk winsock afd ws2 ws2instl wspm nspm ssllsp rtl8139 e100bex smsc100fd dp 83815 ne2000 dhcp ethman wzcsvc wzcsapi pcx500 islp2nds wlclient wzctool eapol e ap eapchap eaptls netmui ndisuio ndis autoras ppp ircomm tapi redir netbios btsv c btd btdrt btagsvc bthuart bthamb bthsc bthcsr bthuniv wendyser wcestreambt sio 950 iphlpapi softkb gwes keybd pointer display fonts waveapi audiodrv wavesample s cxport battdrvr nleddrvr device regenum busenum pm ceddk giisr mmtimer pci pcm conv serial pccard 8042keyboard nopkeyboard csp csp_mininput fsdmgr zlib filesys toolhelp vmini rt_tests COREDLL_COMPONENTS=coremain lmem showerr thunks corecrt corestrw cryptapi tnoti fy tapilib coresip rectapi wmgr_c mgdi_c accel_c messagedialogboxthunk shcore sh ortcut shexec shmisc fileopen fileinfo shellapis dsa timezones mmwave mmsnd mmmi x battery nled devload coreimm fmtmsg corestra coresiow coresioa serdev coreloc multiui crt_cpp_eh_and_rtti full_crt crypthash rsa32 NK_COMPONENTS= nkcompr nkmapfile FILESYS_COMPONENTS=fsheap fsmain fsreg fsysram fsreplbit fsdbase fspass fsadvert ise msgqueue DEVICE_COMPONENTS= devcore iorm pmif PM_COMPONENTS= pm_default_pdd pm_mdd pm_pdd_common GWE1_COMPONENTS=wmbase gweshare gwesmain immthunk msgque GSetWinLong CePtr foreg nd idle kbdui uibase msgbeep audio GWE2_COMPONENTS=mgbase mgbitmap mgblt mgblt2 mgdc mgdibsec mgdraw mgrgn mgwinmgr tchui calibrui mggradfill mgalphablendstub mgtt mgdrwtxt mgprint mgpal mgpalnat GWE3_COMPONENTS=accel btnctl caret cascade imectl clipbd cmbctl defwndproc dlgmg r dlgmnem edctl gcache gwectrl icon iconcmn imgctl lbctl loadbmp loadimg menu me nuscrl mOverlap MouseCursorOnly iconcurs mcursor mcursor8 mNoTapUI GWE4_COMPONENTS=nclient oom sbcmn scbctl startup stcctl winmgr startui oomui sbc mnview nclientview gcacheview btnctlview stcctlview cmbctlview lbctlview msgbox msgbox_hpc dlgmgr_hpc menu_hpc EditControlOs timer column atom drawmbar hotkey s yscolor mgdx mgalias journal mgtci DCOM_MODULES= atl ole32 oleaut32 uuid OLE32_COMPONENTS=mcombase mcommem mcomstr mcommon mcomlib ole232 docfile msf exp mcomguid mcomstm GDIEX_MODULES= imaging IMAGING_COMPONENTS= img_png img_libpng img_pngdecoder img_gif img_liblzw img_g ifdecoder img_jpeg img_jpegfull img_jpegmem img_jpegdecoder img_bmp img_bmpdec oder IE_MODULES= shdocvw msxml3 urlmon wininet shlwapi uuid ieceext mlang SCRIPT_MODULES= jscript SERVERS_MODULES= obexapi obexsrvr mssoap1 wisc10 mssoapr msmqd msmqrt msmqadm ti mesvc services SHELLSDK_MODULES= aygshell SHELL_MODULES= explorer shcore ceshell qvgap CESHELL_COMPONENTS= ceshapi ceshui taskbarlist SHCORE_COMPONENTS= shcore path WCESHELLFE_MODULES= htmlview peghelp webview control ctlpnl cplmain AdvBacklight connpnl intlp Dw DwCtlPnl DwXfer bthpnl NETCF_MODULES= dotnet C:\WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x86\Drivers\USB\CLASS\HID>build -c Build for Windows CE (Release) (Built on Apr 22 2004 10:38:01) File names: Build.log Build.wrn Build.err Build.dat BUILD: [Thrd:Sequence:Type ] Message BUILD: [00:0000000000:PROGC ] Checking for \WINCE500\sdk\bin\i386\srccheck.exe. BUILD: [00:0000000001:PROGC ] SrcCheck exit code: 0 (dec). BUILD: [00:0000000002:PROGC ] Compile and Link for x86. BUILD: [00:0000000003:PROGC ] Computing include file dependencies: BUILD: [00:0000000004:PROGC ] Checking for SDK include directory: C:\WINCE500\sd k\ce\inc. BUILD: [00:0000000005:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\HIDCLASS\MDD\ BUILD: [00:0000000006:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000007:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000008:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000009:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\sdk\lib\$(_CPUINDPATH)\coredll.lib. BUILD: [00:0000000014:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\HIDCLASS\USBPDD\ BUILD: [00:0000000015:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000016:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\oak\lib\$(_CPUINDPATH)\$(TARGETDEFNAME).def. BUILD: [00:0000000017:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000018:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000019:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\oak\lib\$(_CPUINDPATH)\hidmdd.lib. BUILD: [00:0000000020:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\sdk\lib\$(_CPUINDPATH)\coredll.lib $(_SYSGENOAKROOT)\lib\$(_CPUINDPATH)\hidpa rse.lib $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\usbclient.lib $(_SYSGENOAKROOT)\lib \$(_CPUINDPATH)\usbd.lib $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\hidmdd.lib. BUILD: [00:0000000021:WARNS ] Macro: _COMMONPUBROOT not found in \sdk\lib\x86\re tail\coredll.lib C:\WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x86\cesysgen\oak\l ib\x86\retail\hidparse.lib $(_COMMONPUBROOT)\oak\lib\$(_CPUINDPATH)\usbclient.li b $(_SYSGENOAKROOT)\lib\$(_CPUINDPATH)\usbd.lib $(_COMMONOAKROOT)\lib\$(_CPUINDP ATH)\hidmdd.lib. BUILD: [00:0000000022:WARNS ] Macro: _COMMONPUBROOT not found in \sdk\lib\x86\re tail\coredll.lib C:\WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x86\cesysgen\oak\l ib\x86\retail\hidparse.lib \oak\lib\x86\retail\usbclient.lib C:\WINCE500\PBWorks paces\test1\WINCE500\CEPC_x86\cesysgen\oak\lib\x86\retail\usbd.lib $(_COMMONPUBR OOT)\oak\lib\$(_CPUINDPATH)\hidmdd.lib. BUILD: [00:0000000026:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\CLIENTS\KBDHID\ BUILD: [00:0000000027:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000028:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\oak\lib\$(_CPUINDPATH)\$(TARGETDEFNAME).def. BUILD: [00:0000000029:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000030:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000031:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\sdk\lib\$(_CPUINDPATH)\coredll.lib. BUILD: [00:0000000034:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\CLIENTS\MOUHID\BASE\ BUILD: [00:0000000035:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000036:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\oak\lib\$(_CPUINDPATH)\$(TARGETDEFNAME).def. BUILD: [00:0000000037:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000038:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000040:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\CLIENTS\MOUHID\LIB\STANDARD\ BUILD: [00:0000000041:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000042:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000043:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000045:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\CLIENTS\MOUHID\LIB\TRANSCRIBER\ BUILD: [00:0000000046:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000047:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\oak\lib\$(_CPUINDPATH)\$(TARGETDEFNAME).def. BUILD: [00:0000000048:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000049:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000050:WARNS ] Directory: \WINCE500\PBWorkspaces\test1\WINCE500\C EPC_x86\Drivers\touch\trnscrbr\ does not exist. BUILD: [00:0000000053:PROGC ] Scan \WINCE500\PBWorkspaces\test1\WINCE500\CEPC_x8 6\Drivers\USB\CLASS\HID\CLIENTS\CONSHID\ BUILD: [00:0000000054:WARNS ] RELEASETYPE is not set. Using default settings. BUILD: [00:0000000055:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\oak\lib\$(_CPUINDPATH)\$(TARGETDEFNAME).def. BUILD: [00:0000000056:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\t arget\$(__CPUDIR). BUILD: [00:0000000057:WARNS ] Macro: __PROJROOT not found in $(__PROJROOT)\oak\l ib\$(__CPUDIR). BUILD: [00:0000000058:WARNS ] Macro: _COMMONPUBROOT not found in $(_COMMONPUBROO T)\sdk\lib\$(_CPUINDPATH)\coredll.lib. BUILD: [00:0000000060:PROGC ] Saving C:\WINCE500\PBWorkspaces\test1\WINCE500\CEP C_x86\Drivers\USB\Build.dat. BUILD: [00:0000000062:PROGC ] Total of 0 pass zero files to compile in 5 directo ries. BUILD: [00:0000000063:PROGC ] Building generated files in \WINCE500\PBWorkspaces \test1\WINCE500\CEPC_x86\Drivers\USB\CLASS\HID\HIDCLASS\USBPDD\. BUILD: [01:0000000071:ERRORE] NMAKE : U1073: don't know how to make 'C:\WINCE50 0\PBWorkspaces\test1\WINCE500\CEPC_x86\cesysgen\oak\lib\x86\retail\USBHID.def' BUILD: [01:0000000073:ERRORE] NMAKE.EXE -i -c BUILDMSG=Stop. NOLINK=1 PASS0ON LY=1 CLEANBUILD=1 failed - rc = 2 BUILD: [00:0000000074:PROGC ] Files Warnings Erro rs BUILD: [00:0000000075:PROGC ] Midl 0 0 0 BUILD: [00:0000000076:PROGC ] Resource 0 0 0 BUILD: [00:0000000077:PROGC ] Message 0 0 0 BUILD: [00:0000000078:PROGC ] Precomp Header 0 0 0 BUILD: [00:0000000079:PROGC ] C/Cpp/Cxx 0 0 0 BUILD: [00:0000000080:PROGC ] Assembler 0 0 0 BUILD: [00:0000000081:PROGC ] Static Libraries 0 0 0 BUILD: [00:0000000082:PROGC ] Dll's 0 0 0 BUILD: [00:0000000083:PROGC ] Exe's 0 0 0 BUILD: [00:0000000084:PROGC ] Resx 0 0 0 BUILD: [00:0000000085:PROGC ] Csharp Targets 0 0 0 BUILD: [00:0000000086:PROGC ] Other 0 34 2 BUILD: [00:0000000087:PROGC ] BUILD: [00:0000000088:PROGC ] Total 0 34 2 BUILD: [00:0000000089:PROGC ] BUILD: [00:0000000090:PROGC ] 34 Warnings, 2 Errors Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84813
  - 23
    - What does this error mean? In platform builder, when i try to print i get the following error: Unknown: DEBUGCHK failed in file E:\macallan\private\winceos\osshell\commdlg\.\print.cpp at line 139 I use PRINTDLG structure and PrintDlg(&pd) function in my program. This error occurs in Platform builder when i try to use PrintDlg(&pd) function. What may be the problem? How can i resolve it? Thanks...Any help is highly appreciated :) Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84812
  - 24
    - Updateoverlay() is not called on WinCE5.0!! Hi all, Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84811
  - 25
    - CF 2.0 on headless configuration Hello, Does the CF 2.0 works on a headless configuration? Do I have to use the NULL display driver? Are there any plans to create a CF2.0 headless variant in order to minimize the memory footprint? Thanks Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84807
- Next
  - 1
    - USB function driver in WinCE 5.0 Dear all, I am developing a device using WinCE 5.0. Its hardware design is based on Samsung SMDK2410. I added two features to my image: "USB Function - USB Function Bus Drivers - Samsung 2410 CSP" and "USB Function - USB Function Clients - Serial". My PC machine has already installedActiveSyne. How receives me to need to do? Extremely thank! Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84803
  - 2
    - RequiredCEModules and DefaultDrivers in 5.0? I'm sorry if the solution is too obvious, but I can't find it. RequiredCEModules and DefaultDrivers are ignored in CEC files in PB5.0. And as I understand I should but these information in the "associated" BAT files. But how? And what BAT file is it exactly? How can I tell the PB5.0 IDE that my component A depends on component B? How can I tell the PB5.0 IDE that my default driver for display is driver C? TIA -- Michael Reim reim AT helmut-fischer DOT de Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84799
  - 3
    - Wake up from suspend Hi, I have a WinCE5.0 image where I can go to suspend mode with a call to SetPowerSystemState () function. I searched the Platform Builder help for information about how I can enable the power button as a wakeup source by using IOCTL_HAL_ENABLE_WAKE. I do not find much informativ information. Can anybody give me some hints or example codes how to do this? I know that my BSP and kernel supports this. D Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84798
  - 4
    - (608) communication error Every now and then I get the (608) error message when my device comes out of suspend and tries to initialize the PC connection through the USB port (ActiveSync). When that happens, all the entries in the connection type dialog displayed while defining a new connection are grayed out. 1. Is there any solution to this 608 error problem? 2. Is there anyway to disable the auto reconnection that is prompted even if no USB cable is connected to the Slave port? Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84797
  - 5
    - Where is "wzcshell.h" I'd like to use "SHWZCGetWiFiStatusString" API. In WM5.0's doc, it says the API is defined in "Wzcshell.h" header file. However, I cannot find this header file in my platform builder. Does anyone know where can I find it? Also, what library should I link for this API? Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84792
  - 6
    - USB Client Driver Loading Problem Hi, My WinCE 5.0 device has a Netchip2272 controller on it. I have the net2272 controller driver loading and initializing just fine. Add a Microsoft USB function client(Serial). Launching WinCE If you see below attached information, "WinCE booting Debug error message" raised an error as Data Abort: However, in my case, i change "idVendor"=dword:045E" as ;(the semi colon) in the registry of [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class] , Afterall, Don't use the "idVendor"=dword:045E" in my program. And then, after launching(Compiling), Don't happen an error like Data Abort. But, it could not connect with ActiveSync. It do well with USB1.1 in PXA270. if i want to choose NET2272 USB2.0, i should change "idVendor"= , "idProduct"= with [HKEY_LOCAL_MACHINEDriversUSBFunctionDriversSerial_Class]? also, if i change the idVendor, idProduct in www.usb.org, this problem is solved? please!! tell me the exact solution for this problem. ----------------------------------------------------------------------------------- [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class] "Dll"="serialusbfn.dll" "InterfaceSubClass"=dword:ff "InterfaceProtocol"=dword:ff "DeviceName"="USBFNS1:" "Tsp"="Unimodem.dll" "Prefix"="COM" "DeviceArrayIndex"=dword:0 "DeviceType"=dword:0 "IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}" ; idVendor must be changed. 045E belongs to Microsoft and is only to be used for ; prototype devices in your labs. Visit http://www.usb.org to obtain a vendor id. "idVendor"=dword:045E "Manufacturer"="" "idProduct"=dword:00ce "Product"="" "bcdDevice"=dword:0 "DevConfig"=hex: 10,00,00,00,05,00,00,00,00,01,00,00,00,4B,00,00,00,00,08,00,00,00,00,00,00 "FriendlyName"="USB Cable:" -------------------------------------------------------------------------------------------------------- WinCE booting Debug error message : Launching flash image ... System ready! Preparing for download... OEMPreDownload(): Direct launching from Flash address 0xBC900000 Start Read OS...!! OS upload Completed!!! rom_offset=0x0. ROMHDR at Address 80500044h OEMLaunch----------------------- g_EbootCFG.dwPhysStart: 0x80500000 g_EbootCFG.dwPhysLen: 0xD4E774 g_EbootCFG.dwLaunchAddr: 0x80501000 Download successful! Jumping to image at 0x80501000 (physical 0xA050Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00 ProcessorType=0411 Revision=7 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 80505fb4 Sp=ffffc7cc OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 NET2272: Binding to Base Address 4000000, IRQ 32 NET2272: Mapped to virtual address f0000 -BSPIntrEnableIrq(irq = -1) NET2272: Interrupt thread created System_InterruptController(1) -BSPIntrEnableIrq(irq = -1) NET2272: Driver successfully loaded Data Abort: Thread=83d9d10c Proc=81276300 'device.exe' AKY=00000005 PC=034d4b0c(net2272.dll+0x00004b0c) RA=034d4afc(net2272.dll+0x00004afc) BVA=0600003c FSR=00000007 RaiseException: Thread=83d9d10c Proc=81276300 'device.exe' AKY=00000005 PC=03f8de1c(coredll.dll+0x0001de1c) RA=805065d4(NK.EXE+0x000065d4) BVA=00000001 FSR=00000001 --------------------------------------------------------------------------------------------------------------- Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84789
  - 7
    - how to identify different appliction call in the stream driver which can open more one time. hi all. I want to write the stream driver which can been open more than once by different appliction. When different application call the ReadFile and call the driver's XXX_read() , how to identify its caller, since I want different caller must have its own data quence in the driver's XXX_read() mothod. It is right that the appliction call the driver as this: OS call XXX_init(), and the return result is the HANDLE pass to XXX_OPEN(), XXX_READ(), so it cannot mark the different caller(application). since there is no other paramter passed by App. thanks in advance. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84787
  - 8
    - debugging on CE 5.0 with 4.1 SDK Is it possible to debug on a CE 5.0 unit with a project that is built on a CE 4.1 SDK ? We're getting errors involving CEMON pkg from EVC when trying to start the debug session. Just trying to determine if this is a true limitation, or whether we're messing something up. We have a lot of product out on CE 4.1 and would like to upgrade new boxes with CE 5.0, but continue to distribute CE 4.1 applications which will run on both. If we debug on new hardware and build with a CE 5.0 SDK, there is a risk we might end up using something that is CE 5.0-only and not catch it. So, trying to keep the application development group on one SDK for now. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84782
  - 9
    - PB Generated DLL Hi, IS there a trick to exposing the entry points from a PB generated DLL ? I have tried extern "C" __declspec(dllexport) __declspec(dllexport) And the dotnet app thats trying to latch onto these always throws a EntryPointNotFound exception ? Any idea of the correct linkage to use ? Thanks nick Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84777
  - 10
    - Active sync "Connecting to host" message Hello, I am trying to eliminate the "Connecting to host" message at resume from suspend mode. I was told that i can change some things in the function controller's driver that would eliminate this mesasge. I have been given a sample code for pxa270 function controller driver, which disabled the controller(udccr.ude = 0) before suspend and re-enabled it later after the resume procedure. This was suppose to be enough. I tried to eliminate the UDC controller at the pxa255 pdd driver i am using, and give a detach message to the MDD driver. But still the active sync is trying to conect to host at resume Can someone shed some light on this matter? can it be done in an alternate way? Thanks, Oren. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84776
  - 11
    - Newbie DLL location question Hi, Am I correct in thinking that executable code (dll/exe) are put into the rom section of the build. Whilst other files are put into RAM. So that in the dat file for a project any statements of cpoying exe/dll say to \program files\projectname wont be effective. I seem to be getting the built dll in the \rel directory but it never appears in \program files\projectname where as non executable code does. Thanks nick Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84775
  - 12
    - Print Advanced Button Hello all, I'm writing a Printer Driver for WinCE 5.0. I need access to the Advanced button on the print dialog. I'd like to be able to use the "Advanced" button to bring up advanced settings for the printer. How can I access this? If you dont know what button I'm talking about, then open Wordpad->File->Print. On that print dialog there is a grayed-out button called "Advanced". I've searched the web with no luck. Any ideas anyone? Best Wishes, Farek Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84773
  - 13
    - LCD Driver porting Hi I am very new to Windows CE. Presently we are trying to port some custom lcd driver written for nucleus rtos based system to win CE based system. The problem we are facing is: 1) there is a third party graphics library which provides UI in case of nucleus based system. We want exactly the same UI in wince. 2)we want to port the whole software to wince OS based as we require to add many new features to it for which no support is provided in basic nucleus rtos. Now the question which I want to ask is as follows:- 1)Is there any way or API for accessing the lcd device directly from Win CE so that we can just perform little modification to present UI library and use it in wince based system? 2)Are there any alternate way of accessing control register of LCD using win CE API? 3)Is there standard support for 1/4VGA LCD driver on WinCE? Can we include the driver for this device using Platform Builder? Thanks , Sagar Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84771
  - 14
    - LCD Driver porting Hi I am very new to Windows CE. Presently we are trying to port some custom lcd driver written for nucleus rtos based system to win CE based system. The problem we are facing is: 1) there is a third party graphics library which provides UI in case of nucleus based system. We want exactly the same UI in wince. 2)we want to port the whole software to wince OS based as we require to add many new features to it for which no support is provided in basic nucleus rtos. Now the question which I want to ask is as follows:- 1)Is there any way or API for accessing the lcd device directly from Win CE so that we can just perform little modification to present UI library and use it in wince based system? 2)Are there any alternate way of accessing control register of LCD using win CE API? 3)Is there standard support for 1/4VGA LCD on WinCE? Can we include the driver for this device using Platform Builder? Thanks , Sagar Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84770
  - 15
    - NIC Problem while load image I have build a image for CEPC and try to load it to my X86 based PC through ethernet using eboot.bin,while it always indicates "Jumping to 0x0013A348".Through the serial port it reports that the type of my NIC card is 4 which is not matched the type 0 so it reports an error.The NIC card I used is RTL8139,which is supported by BSP,I think,so what is the problem with my process to load it? Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84768
  - 16
    - NIC detection order for eboot? As discussed in previous posts, I'm trying to bring up a platform based on a NICE3100 industrial PC from Nexcom. It has two integrated Ethernet interfaces that use the Intel 82551ER chip. This is not supported by eboot, not even in the latest QFE which includes some support fort that chip. However, the NICE3100 also has a PCI expansion slot, where I can install a RTL8139-based NIC. If I disable the built-in Ethernet interfaces, this NIC is used by eboot. But if they are enabled, eboot finds one of the built-in interfaces first and tries to do a NE2000 initialization, which of course fails. Is there any way I can force the order in which the NICs are detected, so that eboot will find the RTL8139 NIC first and use it even if the onboard NICs are enabled? Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84764
  - 17
    - CETK serial communication test Hi, I am working on WinCe 5.0 for ARM4 architecture. I tried to compile the pSerial.dll from the source code found under: \WINCE500\PRIVATE\TEST\DRIVERS\SERIAL\BVT_API\PSERIAL This results in compilation error for missing files: comm.cpp and comm.h; if I skip these files and try to compile the existing files, it doesn't recognize the api's for and pops with errors like: \pSerial\pserial.cpp(81) : error C2227: left of '->ReadFile' must point to class/struct/union Is there a way to compile this dll so I will be able to run serial tests? Is there any compiled file that I can add to my winCe tree and use it? Thank you in advance, Amit Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84759
  - 18
    - Strange thing of using 128M RAM in CEPC I use Wince5.0 CEPC. According to MSDN and previous messages of newsgroup. If I want to use 128M RAM in CEPC I must do the followings: 1. Modify _OEMAddressTable in startup.asm. dd 80000000h, 0, 04000000h ~~~~~~~~ this size should be larger 2. set IMGRAM128=1 set IMGRAM64= Now, I don't modify any of startup.asm and just set IMGRAM128=1 set IMGRAM64= , and everything is ok. Can anyone tell me why? Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84758
  - 19
    - Debug output for NDIS & TCPSTK Running Windows CE 5.0 on CEPC .... I enable Debug zones from PB menu Target | CE Debug Zones. Verify these in CE Shell (Target Control) using 'zo' command. I am running Debug configuration. What would be a reason I see no output as expected from modules Ndis.dll or Tcpstk.dll? This is very frustrating. Thanks, Mark Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84753
  - 20
    - USBD or USBFN Hi All, Just a general question: What's the difference between the USBD and USBFN? I'm trying to write a device driver for a platform (no host functionality) and it seems like there are examples in the 5.0 source tree for both the USBD and USBFN drivers. Some of the documentation seems to indicate that USBFN is new to 5.0. Does that mean we don't have to implement a USBD driver? Thanks in advance! Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84752
  - 21
    - Cloning an OAL Hi, Upon cloning OAL, I get "unresolved external symbols error" for global varibales such as _dwIntrTimeIsr1, _dwIntrTimeIsr2, fIntrTime. I have put the files in sources in correct order. Has anyone seen similar problem. Ansuya Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84751
  - 22
    - using Visual Studio 2005 with CEPB Hi MS guy: I converted a simple look-like "hello world" eMVC project to the Visual Studio 2005. The project using the platform SDK to build ok. In the eMVC IDE environment very easy to connect to the Target devive (Mobile device). How to connect Visual Studio 2005 IDE to the Target device, so the program could download to the device and start debug? I Could you point a direction or some kind of documentation using Visual Studio 2005 to development a mobile device application. Thanks Lu Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84748
  - 23
    - How to add a new locale into a existing PPC device with WM 5.0? I am trying to find the development document to add a new language support such as Simplified Chinese to an existing PPC with Windows mobile 5.0 (or CE 4.2). Can I use the Platform Builder to generate some .reg and other resource to an existing OS? Which parts are involved to add additional locales that can be selected in the Regional Setting of the control panel? Please provide any document hint from MSDN or somewhere else. Thanks. Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84739
  - 24
    - Read/Write port I/O from debugger Is there a way to read/write from/to an I/O address while debugging a target? I'm looking for commands similar to WinDbg's ib/ob commands. I've had no luck finding such functionality. Any help would be greatly appreciated. Thanks, Chris Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84737
  - 25
    - Automatic update for PB5.0 ? (Product Update rollup, etc) Hi, I want to have the PB 5.0 Up to date. When I install the WinCEPB50-051231-Product-Update-Rollup-Armv4I.msi does it mean I don=C2=B4t need to install all the Updates for 2004 and 2= 005? i.e. WinCEPB50-04XXXX-KB908958-Armv4I.msi WinCEPB50-05XXXX-XXXXXX-Armv4I.msi Is there a way to have an automatic update for PB 5.0 ? Regards -- = Javier Grijalba www.positivesystems.com Touch Panel - PC Systems Tag: how can the build-tool build a dll when source file says "TARGETTY Tag: 84729

I am developping a driver for SDCard using WM5.0,
I find the OS will load sdmemory.dll to drive the SDCard
but in the source-file it defines like this

TARGETDEFNAME=SDMemory
DEFFILE=$(TARGETDEFNAME).def

TARGETNAME=$(TARGETDEFNAME)_LIB
TARGETTYPE=LIBRARY
WINCETARGETFILE0=$(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\$(DEFFILE)

SOURCES = SDMemMain.cpp \
SDMemDiskIO.cpp \
SDMemCardIO.cpp \

it only make a LIB file but not a dll,
so why does build-tools finnally make a sdmemory.dll?

Top

Re: how can the build-tool build a dll when source file says "TARGETTY by Zhongwei

Zhongwei
Mon May 15 11:32:40 CDT 2006

As the SOURCES shows, building the files will create sdmemory.lib, not
sdmemory.dll. The end target file sdmemory.dll is created during the
sysgen process. Among other libs, coredll is linked implictly to the end
target sdmemory.dll. One of the reasons for this approach is COREDLL is
componentized, you know what COREDLL APIs are available on the system only
after the sysgen is done.

If you want to build dll from the source files, you can change the SOURCES
TARGETTYPE to DYNLINK, then you will need to find out what libs it
implicitly links besides coredll and add them explicitly, which is
troublesome sometimes. You can look up sysgen_capture, a very useful tool
to rebuild public drivers.

--
Zhongwei Wang
Applied Data Systems
www.applieddata.net

"simon" <simon@discussions.microsoft.com> wrote in message
news:2AA0353A-45EF-46A8-92A1-D0321B2A3C7C@microsoft.com...

Top