PARTINFO does not match documentation

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - ANN: New Chinese language Windows Embedded Community Site Hello, I know that this may not interest everyone, but I wanted to mention that a new Chinese language Windows Embedded Community Site has recently been launched. There you'll find links to Chinese language Windows CE .NET, Windows XP Embedded and Mobile Device newsgroups as well as other localized technical information. Please see the following site for more information: http://www.microsoft.com/taiwan/community/embedded/ -- Thanks! Michael Fosmire Community PM/MVP Lead, Windows Embedded This posting is provided AS IS with no warranties, and confers no rights. Tag: PARTINFO does not match documentation Tag: 45703
  - 2
    - Need help with CEPC & PC750 PCMCIA reader. I have a Dell Optiplex GX110 system that I have installed a ActionTec PC750 PCMCIA reader in. Under Windows 2000, the PC750 has no problems, but I can't get it to work if I run CE .NET on this system. I have built my CEPC using the Standard WebPad configuration and have selected the TI1250 driver for PCMCIA. The ActionTec device is actually using a TI1225 controller but I think they are compatible as other people have reported that they have gotten the PC750 to work in their CEPC. Below is the error log I get when the driver is started. 4294770801 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcibus.dll at address 0x01310000-0x01323000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCIBUS.DLL' 4294770838 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/0/0. 4294770838 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt:(Bus=0,Device=1,Pin=1) 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=31 SlotNumber=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=0,INTA_IrqBitMap=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=30 SlotNumber=0 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770839 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770840 PID:e3fc3642 TID:e3e75f6e 0x83e72800: OR: No protseqs configured 4294770840 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=1 SlotNumber=0 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770842 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770843 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: - OEMGetInterrupt:Find existing IRQ return IRQ=9 4294770845 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 1/7/0. 4294770845 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770848 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(0) 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc+(Bus 1, Device 10, Function 0) 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/0): Offset 0x10, Type Memory, Size 0x1000 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/0): Offset 0xffffffff, Type Memory, Size 0x10000 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/0): Offset 0xfffffffe, Type IO, Size 0x4000 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc- 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt:(Bus=1,Device=10,Pin=1) 4294770875 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=31 SlotNumber=0 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=0,INTA_IrqBitMap=0 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770876 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=30 SlotNumber=0 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=1 SlotNumber=0 4294770877 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=12 SlotNumber=0 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770879 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=7 SlotNumber=1 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=8 SlotNumber=2 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=61,INTA_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=62,INTB_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=63,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=60,INTC_IrqBitMap=def8 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=9 SlotNumber=3 4294770881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=63,INTB_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=60,INTC_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=61,INTC_IrqBitMap=def8 4294770882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=10 SlotNumber=4 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=63,INTA_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=60,INTB_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=61,INTC_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=62,INTC_IrqBitMap=def8 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(15) to this device 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=f01) 4294770883 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(14) to this device 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=e01) 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(12) to this device 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=c01) 4294770884 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(11) to this device 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=b01) 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(7) to this device 4294770885 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=701) 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(6) to this device 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=601) 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(4) to this device 4294770886 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=401) 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: Mapping New IRQ(3) to this device 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr (EAX=b10f,EBX=150,ECX=301) 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: BiosMapIqr return 0 and EAX=880f 4294770887 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCardBusBridge: Get IRQ call failed. 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(0) 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc+(Bus 1, Device 10, Function 1) 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! ConfigRsrc: BAR(1/10/1): Offset 0x10, Type Memory, Size 0x1000 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x8 fc3000: PCMCIA! ConfigRsrc- 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt:(Bus=1,Device=10,Pin=2) 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=31 SlotNumber=0 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=0,INTA_IrqBitMap=0 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770888 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=30 SlotNumber=0 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770889 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=0 ,Device=1 SlotNumber=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770890 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=12 SlotNumber=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=0,INTB_IrqBitMap=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=0,INTC_IrqBitMap=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=0,INTC_IrqBitMap=0 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=7 SlotNumber=1 4294770891 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=60,INTA_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=61,INTB_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=62,INTC_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=63,INTC_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=8 SlotNumber=2 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=61,INTA_IrqBitMap=def8 4294770892 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=62,INTB_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=63,INTC_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=60,INTC_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=9 SlotNumber=3 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=62,INTA_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=63,INTB_IrqBitMap=def8 4294770893 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=60,INTC_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=61,INTC_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: OEMGetInterrupt: for Bus=1 ,Device=10 SlotNumber=4 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTA_LinkValue=63,INTA_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTB_LinkValue=60,INTB_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTC_LinkValue=61,INTC_IrqBitMap=def8 4294770894 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: INTD_LinkValue=62,INTC_IrqBitMap=def8 4294770895 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: - OEMGetInterrupt:Find existing IRQ return IRQ=9 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/0. 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/1. 4294770897 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/2. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/31/3. 4294770898 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 30, Function 0 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCIBUS! PCICfgAllocIoSpace: Failed to place Device resource: Bus 1, Device 10, Function 0 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294770899 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294770914 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294770961 PID:e3fc3642 TID:e3f54f72 0x83f3b9a8: IPTimer: setting IPTimer of NTE 160150 to 0 4294772383 PID:e3fc3642 TID:e3f54f72 0x83f3b9a8: *IPTimeout: NOT restarting IPTimeout Timer for NTE 160150 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(2) 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772402 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772405 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(3) Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772432 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772437 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(2) Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772465 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294772467 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA! DeviceConfig+(3) 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772495 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294772820 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance) entered 4294772820 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance\PCMCIA2) entered Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772821 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772848 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772849 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA:InitCardSvc PDCardInitServices returned 25 4294772849 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772849 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 Loaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772850 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! StartOneDriver RegisterDevice(<nil>, 0, pcmcia.dll, 0x802d8d8) failed 4294772850 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! ActivateDeviceEx(Drivers\BuiltIn\PCI\Instance\PCMCIA1) entered 4294772852 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: >>> Loading module pcmcia.dll at address 0x01290000-0x012B3000 4294772880 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_ATTACH Unloaded symbols for 'C:\WINCE420 \PUBLIC\MYCEPCWEBPAD\RELDIR\CEPC_X86DEBUG\PCMCIA.DLL' 4294772881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA:InitCardSvc PDCardInitServices returned 1 4294772881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: PCMCIA.DLL DLL_PROCESS_DETACH 4294772881 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: <<< Unloading module pcmcia.dll at address 0x01290000- 0x012B3000 4294772882 PID:e3fc3642 TID:e3fd2fb2 0x83fc3000: DEVICE! StartOneDriver RegisterDevice(<nil>, 0, pcmcia.dll, 0x802d8d8) failed Does anyone know what might be going wrong here? Thanks in advance for any help, Brian Tag: PARTINFO does not match documentation Tag: 45702
  - 3
    - FMD_OEMIoControl - Passing parameters? I created an IOCTL for my FMD driver which works OK (DeviceIoControl called with my IOCTL successfully calls FMD_OEMIoControl). Now, the problem is, all parameters to FMD_OEMIoControl (pInBuf, nInBufSize etc.) are 0. The help says that all parameters are set to zero if the dwIoControlCode parameter does not specify to require these data. So how do I have to setup my dwIoControlCode? The CTL_CODE macro does not seem to be the right place to configure this, so where else do I have to look? Or am I missing something here? Thanks in advance. Marc Tag: PARTINFO does not match documentation Tag: 45698
  - 4
    - PCMCIA/CF - no activity on the bus I am in the process of target board hardware/software debugging. My system uses Au1100 chip and I use Windows CE .NET (4.2). A lot of peripherals work fine and this is good thing :-) The problem I have now is I do not see ANY activity on the PCMCIA bus - actually it is CF in my case... I drive CF_RESET pin on the card to be LOW and then try to read "tuples" from ATTRIB area of the CF card with the original BSP code but I got complete junk data... I have tapped logic analyzer to several signals: PCE0, PCE1, ROE, POE, CF_A0-A10 (address bus in CF connector) and several other signals on the connector side, behind drivers/buffers and I see nothing happens when I read the card. The only signals change is RESET, CF_DETECT (when I insert the card) and RDY/-BSY telling me the CF is ready... then: only silence... On the software side, I have assigned RESET, CF_DETECT and RDY/-BSY pins to be driven by GPIO200, GPIO22 and GPIO21 respectively and I set sys_pinfunc bit 18 to 0 to have PREG, PCE1, PCE2, PWE functions instead of GPIO207:204 (standard setting for PCMCIA) and also bit 17 to 1 to have access to GPIO200. I have also verified there is PCMInitialize function called to fill TLB with three 16M-byte large virtual memory pages to match PCM_IO, PCM_ATTR, PCM_MEM physical addresses - this code is from the original BSP... Bits set in EntryHi and EntryLo0, EntryLo1 looks good and match both virtual addresses hardcoded in bootloader header files and physical addresses of PCMCIA interface controller area... The problem is that when PCMTuplePtr (set to virtual 0x1E00 0000 mapped to 0xF 4000 0000 physical address of the Attribute Memory area) is read in PCMReadFirstTuple nothing happens on the bus... including no activity on chip-selects and junk content of memory is read like this: Tuple Code=0x00 00 0E 08 0E 08 0E 08 0E 08 0E 08 0E 08 0E 0A 83 0E 80 06 00 00 00 3E 83 0E 80 42 19 00 50 7C 8C 0E 80 00 00 00 00 0A 00 00 00 00 00 00 00 0A B3 00 C0 3E 00 00 00 EC 83 0E 80 0D 00 00 00 0A 00 00 00 04 00 00 00 04 00 00 00 04 00 00 00 0A 00 00 00 00 00 00 00 04 00 00 00 0D 00 00 00 FC 9F 01 80 00 00 00 00 FC 9F 01 80 21 09 81 99 8C 67 0E 80 31 04 86 18 21 00 00 00 61 08 22 6A 22 60 52 56 14 60 40 00 7C 8F 05 80 21 00 00 00 00 00 00 00 7C 8F 05 80 8C 8F 05 80 04 00 00 00 FF FF Tuple Code=0x00 Tuple Code=0x0A Tuple Code=0x0A [program is looping thinking it reads from CF memory] Is there anything I could miss in regards to PCMCIA/CF setup? Do you know any other ways to debug this problem? Tag: PARTINFO does not match documentation Tag: 45695
  - 5
    - Device driver should load before StorageManager Hi everyone I am using a hive based registry. The HIVE BOOT SECTION looks something like this (pseudo) ;HIVE BOOT SECTION start DevMgr = 1 ; allow for hive based registry StorageManager autoload Flash profile ourDeviceDriver order:0 flashDriver order:1 ;END HIVE BOOT SECTION The Boot order now is the following: -------------------------------------------------------- 0) Boot registry is loaded 1) Storage Manger starts -autoload flash profile loads 'flashDriver' 2) built in drivers are loaded ourDeviceDriver (flashDriver is already loaded and thus not loaded again) What I would need is: ---------------------------------- 0) Boot registry is loaded 1) ourDeviceDriver is loaded 2) <do everything else> It is extremely important that 'ourDeviceDriver' is loaded prior to any driver else, i.e. 'flashDriver' depends on 'ourDeviceDriver'. Does anyone know how it can be achieved to load a device driver as soon as the Boot Registry is available BEFORE any other driver or component is loaded? Any hints appreciated, thanks. -Michael Tag: PARTINFO does not match documentation Tag: 45691
  - 6
    - Look into NK.bin Hello is it possibly to look inside the NK.BIN?? I want too see the Files into the NK.BIN. Thanks Tag: PARTINFO does not match documentation Tag: 45690
  - 7
    - Platform Manager connection with Emulator was broken ! Hi Gurus, I have developed a desktop app which talks with its smartphone agent over two Platform Manager connection streams, but I found the connections sometimes will be broken automatically by CEMGR, and I am sure the device side agent is still alive, and I never saw such situation occurs with only one connection stream mode. While I checked WinCE log of Event Viewer, found the following information could be the cause for such termination: ----------------------------------------------------- Event Type: Information Event Source: cemgr Event Category: None Event ID: 1 Date: 2003-12-3 Time: 23:32:03 User: N/A Computer: CCCC Description: Process Id: 424 Thread Id: 1524 Source: Message: ConnectionManager: keepalive heartbeat exiting. All emulator sessions are shutdown. ----------------------------------------------------- Thanks if anybody can give me some explainations in depth. Best regards, Bill Tag: PARTINFO does not match documentation Tag: 45685
  - 8
    - Sleep or Wait in BIOSLOADER Hello, has anybody written a Sleep or Wait function for the BIOSLOADER? I need a function which waits some milliseconds. I would like to place this function in Main.c so I am already in proteced-mode. Any tips? Regards Peter Tag: PARTINFO does not match documentation Tag: 45684
  - 9
    - Bluetooth HCI stack (CE .NET 4.2) Hi, We are trying to embed a serial Bluetooth module with HCI stack onto our serial port 3 on a StrongARM - SA1110 processor board). As the BT module has the HCI stack installed, we rely on the Windows CE .NET BT HCI UART driver (bthuart.dll). All we in theory would have to do is to embed it using RX,TX, and RTS,CTS lines and install the bthuart.dll, which then allows the upper layers to comunicate with the BT module via the Serial port driver (SP3). We also have another module multiplexed with the BT module (rx,tx,cts,rts lines). My question is: Does a bluetooth connection get disconnected by the upper layers if I via the MUX disable the serial port lines to the BT module for e.g. 3 seconds but leave the power on to the module? Does microsoft have any documentation on how the upper stack's timeouts and how long time the module can be disconnected before the upper stack will asume a reset? Generally what this means is that we want to use the other module for 3 seconds or less during an established TCP/IP connection to a BT access point, without having to re-connect to the BT access point. Any comments? Best regards, Bo Henriksen Tag: PARTINFO does not match documentation Tag: 45680
  - 10
    - Newbie Windows CE.net Hi, I'm new to Windows CE.net. Does anyone know a good link on the www to learn CE.net? I've tried to build an image but where do i find the image and how can i use it on the target device? Thanks, An Tag: PARTINFO does not match documentation Tag: 45675
  - 11
    - seraching WAN-Driver Hello, Where can I get a WAN-Driver (WIN CE 3.0) that works with CAPI.dll?? Tanks Tag: PARTINFO does not match documentation Tag: 45672
  - 12
    - CEPC - unresolved external symbol I'm trying to build a CEPC platform, based on Industrial Controller But I receive "unresolved external symbol" Where can I find these functions ?? Error messages: c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKrdmsr referenced in function _CheckExistingMTRR c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKVirtualSetAttributes referenced in function _PATSetMemoryAttributes c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKwrmsr referenced in function _WriteMtrrRegPair c:\wince420\platform\cepc\kernel\buildexe\kern\i486oal.lib (cfwpc.obj) : error LNK2001: unresolved external symbol _pfnOEMSetMemoryAttributes c:\wince420\platform\cepc\target\x86\retail\kern.exe() : error LNK1120: 4 unresolved externals BUILD: Linking c:\wince420 \platform\cepc\kernel\buildexe\kernkitl directory Files: 0 c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKrdmsr referenced in function _CheckExistingMTRR c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKVirtualSetAttributes referenced in function _PATSetMemoryAttributes c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKwrmsr referenced in function _WriteMtrrRegPair c:\wince420 \platform\cepc\kernel\buildexe\kernkitl\i486oal.lib (cfwpc.obj) : error LNK2001: unresolved external symbol _pfnOEMSetMemoryAttributes c:\wince420\platform\cepc\target\x86\retail\kernkitl.exe () : error LNK1120: 4 unresolved externals BUILD: Linking c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof directory Files: 0 c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKrdmsr referenced in function _CheckExistingMTRR c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKVirtualSetAttributes referenced in function _PATSetMemoryAttributes c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2019: unresolved external symbol _NKwrmsr referenced in function _WriteMtrrRegPair c:\wince420 \platform\cepc\kernel\buildexe\kernkitlprof\i486oal.lib (cfwpc.obj) : error LNK2001: unresolved external symbol _pfnOEMSetMemoryAttributes c:\wince420\platform\cepc\target\x86 \retail\kernkitlprof.exe() : error LNK1120: 4 unresolved externals BUILD: Done 15 files compiled - 15 Errors Tag: PARTINFO does not match documentation Tag: 45668
  - 13
    - More ISAPI extension questions I used platform builder 4.1 to create an emulator target. The CE web server appears to be working. A virtual path was created using the HKEY_LOCAL_MACHINE\Comm\HTTPD\VROOTS key in projects.reg, but it is not working. Can a virtual path map to any physical path or just to subdirectories off of the localhost path and does this work on the emulator? I am trying to access my isapi extension dll which is located in the "release" directory. Thanks, Jim King Tag: PARTINFO does not match documentation Tag: 45663
  - 14
    - CE on an ASUS PC board On http://www.microsoft.com/windows/Embedded/ce.NET/evaluation /hardware/x86.asp Microsoft gives reference of the board Asus TUSL2-C Intel 815EP. the problem is that ASUS doesn't supply any more this board . The new boards don't use the Intel 815EP chip but a new one Intel 885. BSP of this chip is not included in PB 4.2. What is the best solution if we want to work on CE with a standard PC board ? Thanks. Tag: PARTINFO does not match documentation Tag: 45662
  - 15
    - AVStream for CE .net I want to write a video capture driver for a USB video capture device. However, the referene driver source codes are for AVStream in Win32 platform. Does any one know how to port the AVStream into CE .net? Tag: PARTINFO does not match documentation Tag: 45657
  - 16
    - How to compile vb6 programe to Ce.Net4.2 version? Dear all, I have a vb6 code with acess2k Database, I would like to put this application to CE.Net4.2 emulator, Anyone knows how to do it? thanks for any help Tag: PARTINFO does not match documentation Tag: 45654
  - 17
    - Which variable for multilanguage. Hi, all: Here I want to build a system which support English and Chinese. Yes, I can set Locals in Setting tab from IDE, but which variables in command line for this ? I browse Foo.wce file and find these statements: # PROP Locales "0409 0804" # PROP DefaultLang "0804" When I run cebuild in command line, is there any logic to access these statements ? I wonder how to make the command line build as same as IDE environment build. Best regards. Jack. Tag: PARTINFO does not match documentation Tag: 45651
  - 18
    - library allowing image download through ethernet Hi all, I'm looking for a command line tool or a library that I could use on a PC from an application to download an image through ethernet (or USB via RNDIS). The goal is to deliver to users a PC application which allows image update on our device. As the .BIN file transfer protocol is fully designed (and implemented in PB and eshell), I wonder if there is a lib or dll I could use that would implement the protocol. Thanks by advance Yannick -- ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com Tél : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- Tag: PARTINFO does not match documentation Tag: 45648
  - 19
    - Question about NK.bin Hi all, How to write my own information into the NK.bin? For example: I want to write "CE420b2" in the fixed offset of NK.bin. Can I finish that while making the nk image? Thanks Bryan Tag: PARTINFO does not match documentation Tag: 45642
  - 20
    - Does IE5.5 support hotmail email Attached file receiving or sending? Hi: as we know ,wince4.1 ' IE version is 5.5, when I receive hotmail attachfile or just want to send an attach,it showes out:download IE6,I 'd like to ask if we have some other method to solve this proBlem, Does MS afford the QFE concerned? Thank you in advance. Tag: PARTINFO does not match documentation Tag: 45640
  - 21
    - Does CE.net support ARM720T ? Hi all, Does CE.net support ARM720T ? If yes, why CEPB has not a BSP for ARM720t? If not, Where or how can I get a BSP for it? Thank you very much Regards Lee Tag: PARTINFO does not match documentation Tag: 45635
  - 22
    - How to use Ramdisk and MyFSD from CE 3.0 to CE.NET How to use Ramdisk and MyFSD from CE 3.0 to CE.NET Hi there I am porting Ramdisk driver and MyFSD driver CE3.0 to CE.Net. This module work fine CE 3.0. but CE.Net don't work. RAMDISK device is visible Explorer on CE3.0, but .Net is net seen. And MyFSD Load is failed(LoadFSDEx()). Then, How to load MyFSD and link Ramdisk. I looking for newsgroup this information. but I don't understand Registry setting and How to load MyFSD. Anybody send me some information. Please. I'm sorry. I don't speak english very well. ^__^ Tag: PARTINFO does not match documentation Tag: 45631
  - 23
    - Error during Build|Clean I get the following error during a Build|Clean operation: Deleted intermediate files and output files for project 'AU1100TEST2 - AMD DB1100: MIPSII Win32 (WCE MIPSII) Debug'. Warning PB2020: Unable to copy file(s). The path is invalid or the files do not exist: - C:\WINCE420\platform\DB1100\target\MIPSII\retail\ddi_au1100lcd.dll 1 File(s) copied 1 File(s) copied 1 File(s) copied 1 File(s) copied 1 File(s) copied If you'll notice, it is trying to copy the ddi_au1100lcd.dll from the *retail* folder. This seems odd to me for two reasons, 1) I have never built the retail version, why it would copy it from that folder? 2) I would assume that the LCD DLL would be cleaned and re-built, not copied as part of a clean. Can anybody shed some light on this? -- Frank D. Lombardo Turning Point Technology, Inc. Frank_AT_TurningPointOnline_DOT_com Tag: PARTINFO does not match documentation Tag: 45626
  - 24
    - How to get the different device category's feature Hi all At the FeatureView window, Can I use some feature of the Display based devices to the headless devices? How to export the some feature of the display based devices and How to get the exported features to headless devices? Thanks Jeff Lee Tag: PARTINFO does not match documentation Tag: 45625
  - 25
    - Use touch screen on a VIA board. All, I got a VIA EPIA M-Series Mini-ITX mainboard and tried to install touch screen driver on WinCE 4.2 .NET. According to touch screen manual, 1. I have to add the Catalog->Core OS->Shell and User Interface-> User Interface->Touch Display(Stylus) Component in my platform and the Catalog->Core OS->Shell and User Interface-> User Interface->Mouse Component in my platform. 2. I edited project.bib to include touchscreen driver and added registry setting on project.reg. But I couldn't find "Stylus" from Control panel after booting up. The manual said Stylus would calibrate Touch Screen. This board has one Serial port on rear side and the other on board. I only use com1 to connect touch screen. Though I disable debug output serial on "debug.c", I still don't see "Stylus" on control panel. Do you give me some tip? Thanks in advance. Hwansoo Tag: PARTINFO does not match documentation Tag: 45621
- Next
  - 1
    - system freeze I've written an application that runs just fine for about 4 hours. After that the system freezes. I've talked to some people that experienced a simliar behaviour when there was memory leak on the driver level. I have no clue about the driver vs. application level. Whether there are different memory pools or whatever. So I am not quite sure where to search the bug. Anyway a leak detecting software reports no memory nor GDI leaks for the application. The allocated memory is *not* instantly growing (besides this would make a dialog pop up) Reducing the memory in the control center at least seems to make the freeze happen earlier. Does this ring a bell for anyone? ...I am really lost here! I need to know if this is a problem of my application or of a driver/software that comes from the vendor. -- Torsten Tag: PARTINFO does not match documentation Tag: 45619
  - 2
    - OEM Application and unique hardware I need to understand how an OEM can support unique hardware modules with their tailored applications. I am aware of the stream interface that can be used by user mode applications via the file system interface, but I would prefer not to go this route. Is there information available that describes how to bridge between a device driver with a custom interface, trusted OEM application and ultimately to a untrusted user application? Nathan Tag: PARTINFO does not match documentation Tag: 45617
  - 3
    - Check out this internet update from the Microsoft Corporation --osonvhkcnkkyjj Content-Type: multipart/related; boundary="oneoehhugufmkbqz"; type="multipart/alternative" --oneoehhugufmkbqz Content-Type: multipart/alternative; boundary="qnwfjfcwotliwqb" --qnwfjfcwotliwqb Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Microsoft Consumer this is the latest version of security update, the "December 2003, Cumulative Patch" update which eliminates all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to help protect your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your computer. This update includes the functionality = of all previously released patches. System requirements: Windows 95/98/Me/2000/NT/XP This update applies to: - MS Internet Explorer, version 4.01 and later - MS Outlook, version 8.00 and later - MS Outlook Express, version 4.01 and later Recommendation: Customers should install the patch = at the earliest opportunity. How to install: Run attached file. Choose Yes on displayed dialog box. How to use: You don't need to do anything after installing this item. Microsoft Product Support Services and Knowledge Base articles = can be found on the Microsoft Technical Support web site. http://support.microsoft.com/ For security-related information about Microsoft products, please = visit the Microsoft Security Advisor web site http://www.microsoft.com/security/ Thank you for using Microsoft products. Please do not reply to this message. It was sent from an unmonitored e-mail address and we are unable = to respond to any replies. ---------------------------------------------- The names of the actual companies and products mentioned = herein are the trademarks of their respective owners. Copyright 2003 Microsoft Corporation. --qnwfjfcwotliwqb Content-Type: text/html Content-Transfer-Encoding: quoted-printable <HTML> <HEAD> <style type=3D'text/css'>.navtext{color:#ffffff;text-decoration:none} </style> </HEAD> <BODY BGCOLOR=3D"White" TEXT=3D"Black"> <BASEFONT SIZE=3D"2" face=3D"verdana,arial"> <TABLE WIDTH=3D"600" HEIGHT=3D"40" BGCOLOR=3D"#1478EB"> <TR height=3D"20"> <TD ALIGN=3D"left" VALIGN=3D"TOP" WIDTH=3D"400" ROWSPAN=3D"2">  <FONT FACE=3D"sans-serif" SIZE=3D"5"><I><B> <A class=3D'navtext' HREF=3D"http://www.microsoft.com/" TITLE=3D"Microsoft Home Site" target=3D"_top">Microsoft</A> </B></I></FONT> </TD> <TD ALIGN=3D"right" VALIGN=3D"MIDDLE" BGCOLOR=3D"Black" NOWRAP> <FONT color=3D"#ffffff" size=3D1>  <A class=3D'navtext' href=3D'http://www.microsoft.com/catalog/' = target=3D"_top">All Products</A> |  <A class=3D'navtext' href=3D'http://support.microsoft.com/' = target=3D"_top">Support</A> |  <A class=3D'navtext' href=3D'http://search.microsoft.com/' = target=3D"_top">Search</A> |  <A class=3D'navtext' href=3D'http://www.microsoft.com/' target=3D_top> Microsoft.com Guide</A>  </FONT> </TD> </TR> <TR> <TD ALIGN=3D"right" VALIGN=3D"BOTTOM" NOWRAP> <FONT FACE=3D"Verdana, Arial" SIZE=3D1><B> <A class=3D'navtext' HREF=3D'http://www.microsoft.com/' TARGET=3D" top"> Microsoft Home</A>  </B> </FONT> </TD> </TR> </TABLE>  <IMG SRC=3D"cid:vamwzqp" BORDER=3D"0"><BR><BR> <TABLE WIDTH=3D"600"><TR><TD><FONT SIZE=3D"2"> Microsoft Consumer<BR><BR> this is the latest version of security update, the "December 2003, Cumulative Patch" update which eliminates all known security vulnerabilities affecting MS Internet Explorer, MS Outlook and MS Outlook Express as well as three newly discovered vulnerabilities. Install now to help protect your computer from these vulnerabilities, the most serious of which could allow an malicious user to run executable on your computer. This update includes the functionality = of all previously released patches. </FONT></TD></TR> </TABLE> <BR><BR> <TABLE BORDER=3D"1" CELLSPACING=3D"1" CELLPADDING=3D"3" WIDTH=3D"600"> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> System requirements</B> </FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Windows 95/98/Me/2000/NT/XP</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> This update applies to</B> </FONT></TD><TD NOWRAP> <FONT SIZE=3D"1"> MS Internet Explorer, version 4.01 and later<BR> MS Outlook, version 8.00 and later<BR> MS Outlook Express, version 4.01 and later </FONT> </TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> Recommendation</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Customers should install the patch = at the earliest opportunity.</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to install</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">Run attached file. = Choose Yes on displayed dialog box.</FONT></TD> </TR> <TR VALIGN=3D"TOP"> <TD NOWRAP><FONT SIZE=3D"1"><B><IMG SRC=3D"cid:fwmbvhw" = ALIGN=3D"absmiddle" BORDER=3D"0"> How to use</B></FONT></TD> <TD NOWRAP><FONT SIZE=3D"1">You don't need to do = anything after installing this item.</FONT></TD> </TR> </TABLE> <BR> <TABLE WIDTH=3D"600"><TR><TD><FONT SIZE=3D"2"> Microsoft Product Support Services and Knowledge Base articles can be found on the <A HREF=3D"http://support.microsoft.com/" = TARGET=3D"_top">Microsoft Technical Support</A> web site. = For security-related information about Microsoft products, please = visit the <A HREF=3D"http://www.microsoft.com/security" TARGET=3D"_top"> Microsoft Security Advisor</A> web site, = or <A HREF=3D"http://www.microsoft.com/contactus/contactus.asp" = TARGET=3D"_top">Contact Us.</A> <BR><BR> Thank you for using Microsoft products.<BR><BR></FONT> <FONT SIZE=3D"1">Please do not reply to this message. = It was sent from an unmonitored e-mail address and we are unable = to respond to any replies.<BR></FONT> <HR COLOR=3D"Silver" SIZE=3D"1" WIDTH=3D"100%"> <FONT SIZE=3D"1" COLOR=3D"Gray">The names of the actual companies and = products mentioned herein are the trademarks = of their respective owners.</FONT> </TD></TR></TABLE> <BR> <TABLE WIDTH=3D"600" HEIGHT=3D"45" BGCOLOR=3D"#1478EB"> <TR VALIGN=3D"TOP"> <TD WIDTH=3D"5"></TD> <TD> <FONT COLOR=3D"#FFFFFF" SIZE=3D"1"><B> <A class=3D'navtext' HREF=3D"http://www.microsoft.com/= contactus/contactus.asp" TARGET=3D"_top">Contact Us</A>  |  <A class=3D'navtext' HREF=3D"http://www.microsoft.com/legal/" = TARGET=3D"_top">Legal</A>  |  <A class=3D'navtext' HREF=3D"https://www.truste.org/validate/605" = TARGET=3D"_top" TITLE=3D"TRUSTe - Click to Verify">TRUSTe</A> </FONT></B> </TD> </TR> <TR VALIGN=3D"MIDDLE"> <TD WIDTH=3D"5"></TD> <TD> <FONT COLOR=3D"#FFFFFF" SIZE=3D"1"> ©2003 Microsoft Corporation. All rights reserved. <A STYLE=3D"color:#FFFFFF;" HREF=3D"http://www.microsoft.com/= info/cpyright.htm" TARGET=3D"_top">Terms of Use</A>  |  <A STYLE=3D"color:#FFFFFF;" HREF=3D"http://www.microsoft.com/= info/privacy.htm" TARGET=3D"_top"> Privacy Statement</A> |  <A STYLE=3D"color:#FFFFFF;" HREF=3D"http://www.microsoft.com/= enable/" TARGET=3D"_top">Accessibility</A> </FONT> </TD> </TR> </TABLE> </BODY> </HTML> --qnwfjfcwotliwqb-- --oneoehhugufmkbqz Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <vamwzqp> R0lGODlhaAA7APcAAP///+rp6puSp6GZrDUjUUc6Zn53mFJMdbGvvVtXh2xre8bF1x8cU4yLprOy zIGArlZWu25ux319xWpqnnNzppaWy46OvKKizZqavLa2176+283N5sfH34uLmpKSoNvb7c7O3L29 yqOjrtTU4crK1Nvb5erq9O/v+O7u99PT2sbGzePj6vLy99jY3Pv7/vb2+fn5++/v8Kqr0oWHuNbX 55SVoszN28vM2pGUr7S1vqqtv52frOPl8CQvaquz2Ojp7pmn3Ozu83OPzmmT6F1/xo6Voh9p2C5z 3EWC31mS40Zxr4uw6LXN8iZkuXmn55q97PH2/Yir1rbL5iVTh3Oj2cvX5Pv9/+/w8QF8606h62Wk 3n+dubnY9abB2c7n/83h9Nji6weK+CGJ4Vim6WyKpKWssgFyyAaV/0Km8Gyx6HW57FJxicDP2+Tt 9Pj8/wOa/wmL5wqd/w6V8heb91e5+mS9+VmLr4vD6qvc/b/j/Mbn/sTi9rvX6szq/tPt/9ju/dzx /+n2/+74//P6/+3w8hOh/xOW6yCm/iuu/zWv/0m4/XTH/IXK95TP9qPV9bfi/tDn9tfp9OP0/93r 9L3Izy6Vzj22/lrC/mfG/JvJ5JGntAyd6IbX/3zD6GzP/3jV/2uoxHqbqujv8g6MvJTj/2HF5pXV 606zz6Hp/63v/7j1/8Ps88b8/rbj5RKOkE2wr3OGhoKGhv7///Dx8V2alqvm4Zni1YPRvx5uVwyO X0q2hLTvw8X10gx2H4PXkkuoV5zkoQeADZu7mmzIVEO7HIXbaGfLMPz8+97d2/Px7v///+bl5eHg 4P7+/v39/fT09PLy8u7u7gAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAAaAA7AAAI/gCVCRxI sKDBgwgTKlzIsKHDhxAjKgwiqs2kSJEgQfqyp2PHLxoxTmojSpTEkyglBrGYcU+el3n09PEDSFKg mzclAfLTRw/MPV4gjTSZsmhRURchuXwUs88fSYIGubEiqyqAq1gBNLPiRlCgPz197tE4MojRswuD JHX5UiagQILcNMtKl26zu3etuBgUaKcePXv0QIo0iSjaw8raROKYh6nbuFbmVpVlpbKby4Mya858 eWrlrV0l/fECWDBhw4hPimoJUw9NQVa0Yg6kk6dPmD9xt/Xi52kgKG4GCRLtpTjZNmZTQ5yktLXT QFNDA+qJe2wkkgkrrmWrx4tv0X6M/gvFrnzh6uaO+wCKOhzs7TzWyUesyDom7z9//EAKOh51eYKK sdWWH1D15cd78J12GFJKufRXcfwNNtR/ANYXE006UfdSfBQq1lxM3fFHWFlojRBCCA5goMMK5y3V 1B879VGdUMlRqIxaG7kUmHEikVTjQyuAcGIGDmSQwQUYzPBAA1UIKJMfUCI4Vhs2EjTJKrWYwogp mXSxY0iTTLhQAC2ocKIDHGywgAwYWPDAm3AeIIVztr3E1FiFVSnQJLXc4ksxuujyiy6npNGFYBKK WRAzKZipAgkp8ACCAyLg0MClDcD5ppIUVNCFFDL1oSF8Qvn3nyi8+KIqMH8aQwwx/66EMQcoVQxG mI/KBEBCCCSo0MIPLJSJwA6YFvsmBlFkYgopUTxwgQ8XXGBBBRUA0QUXeJp6qi2r2rKLLcAU42qs WIRhR623YpdDNM4wQ0IOInggrwfFNoCDDl20wooqqaSCCil3SHCBBgQXnAGbFmCAgQMkBKDnLsMU 4wswvPCySy3DuLpJGFiY4YodX6RrUhnOIFDDvPNeqkkXfKzCyssv8+svwM5uYPPNONusAZszEEEE GoooQsfQdRRdxyJII83I0ow04nQjjkTtCB5cVN3KMBEXA8wuFbMC6Cu5jIJFLsG4oonIQeQQQw4o a5KsI6moogrMMMvt77+kCPzB3v589+03BxdQ0IFyotyCdTFap7I1K7Z4YskmcIwSTC+9KMHGSD6S 0AIJHkRxByekkIJKv3LPXbfMeOddgQmst+466xoAIUEEEUzAQNBD02H00UkvwnTTT0s9ddV4ZPEK 1hH/qTUnlyDyRi659BJMMLiEgrkoQSwTAjMefPIJ6KKPHnfppfeLCt6cCDFDmjT8AMP7MJywwQW0 1187Aco5osUYyGNtjC+ccFwhzuCK6U0OF2uoQht8FAMEoMADnfge+M7Xrwpa8HyhI0X6JGCwDGhg fvYLoe1wRzSj9c53THsa1KRGNS6oYQxZ0AXyjKGLUlzCEoeIQxjIRjnKTYESC/7EnjJyYAIRRMF7 4Auf+Cp4vtRxghNOiEAHjxTC+k3gfsp5ghPSAIqMBeoUlkjEIeYgBzjwEBdonEIOgmgWSDlgC0h8 YgabSEcncuITUZQBwYxERftRYAIToEDtbie0EhbthL9TofBa6IT9jeEVgQpUJcZoCDEUcHqUw8UU ysBGZZQgBAvAgSfimMQMmjJ0T/SeGiKgRw3w8QKz+2Mgp/UALKamC1FYwha1AElJzkEMYiDb5HqB wE2SRIjR0MEIGoCJUUqwlKd84h0/4QlMRKACezQSLAM5A2pR6wF/JGTudofIFAaPhVW7AxWooIX9 ZSELv4hnJYA5CjQScw1rUP/jMQeCgA/gQA2ecOYzpUnQaVKzmtfM5pEkMIFpebMCtZwA/lJTBR88 YQlRcIITQBHPeNrhCEcwQhPQmM8EALEkAwnBDTBAhWYG1HukTCVMD4oJTBDBAgrNAEOnZYE/vomh 4jQk75KWyHNGrYWO0KUT1tlOWnRUCUdQQhOaoIQ12GEKsVCgEAVSAge88RIufelMxxrQal7iEkLg oCv5uFOffvOPE0XMMvjggy74IAoZ3UI8aYEEJUh1CkoggxIOUIbCbFUZyczADM4K1rI69rHVxARj kyDFtRppp9OawR8pAFQS6s6EvSuq0xZZNS444gkZ1SgVQkELWvjMr1QlQgT+pgALG+yTIDrgwAPo wFiwhtWxNZUsYxVBWYX6YAYT0CwgHwDRB0i0PNGoghTsCoQoaEIYQhCCz7ZLhCYoIAdD+ZEyQqAB C4xBEb09a3Brmt5LBE0RWYiAB/mo2EBSoJvfdG5QP3vI0JpztOgsLR8y8QTU4jUK2U2wEIagBAWU AQy3JcgIUqSF97b3wu9VhCXQwErLKpYCDvXmmygQV+UEQLpScKUPfACEFjuBCGuAhQ4gXBLxIjZa QrBEhtGL3rPyOMOWCHIiOkxfCzT0oc2lwH7J6d+lKTLAVfPIdAu8hCUAwQlCIIMBikAJCEeYIMm4 gAxmkIggB3nHOzazJcb+QIXZ6bHIIPZmT0FMYj2RyUw50EEZRIAASnzheoctSJEekIgyq/nQalaE E2QXAYHlFANx1iyILYDcJYOWqP9d4VFLi62PgEQkGAl1mI5p44HcYMxoQISqC21oIYcxDUuowOwk IAMOTDEDGAAnBR5gARyAE5Al1pMytIM5UiuEBxWwQBIOoepmO1sRd/BBBWgnMGo9a758xECmcOBr QE5Av55lMqadbNThldYjX/h0qEVyvVIDiFpEOIS85b3qOjBBBrODgL4foCZoWVsG2cZAt5fL7ToL WyAVWeAxA42QScjgAkQoRCHmrYhGgDAC+s54AjbAAQ4s4GDeFHOuvf3/ABwMQBgiUHK4L620TJP2 3J7WSEhG1MmJRKILsJzDxBfxhfLWL+MZn4AGOm5rgj2cWrJ8wAB2sAMRFEMYBtcTRUpCdXcbZDV8 sIAExoAHHuA7At2sYv3Q5PEOQmvXTE/7DlCu8kLyd6gtJzeANw3zPaRb5uwOIkoV0gY2SNsCgG+0 DFJwJFhWMbkDK7qHRcD4xjMeBxMoQAGEHYSpWz0hPlhANHxggWtyYBnMQAYIKvBwCZj+9GCHqAUc kFMdOF4EOzBAAXoA2JX3d9zAm7u5oxxzW4164doaiAM0rwwU0IAHz4hGAEDfAjH74PTQn4G0EpAA Z9HX9Y03wAEKcIAB/oDAYQc/CQkcEIBoPAMGzoDBM2KwfGa0QAMXOBLg5y8B6V/gAVNowhQogIEV 61kEDXAAPdADTVAJaKBjtgd3KCR3mrZ7nWZ36kZzx0QIV5AQGNAC5Xd+x6B+7Md8KYBN0oZkziIt E4AAKTAACtBQ8ZIA3NcBKrAMMRB+RfEAzLAM0aAMz/ACLwANyrcMyNACKXABCwA40VKEFPBwRtYE cjAHhmAEU5AAAzgFYjAHrHZmCVhODPhyvAeBtkJzNUYIs5AQNLgM5VeBV9CDoQeEIZABICADbviG FBAtRqYAzCAQAVACOSAACFACMngYFqACNRgAgiiIy+CDLQCEJCAD/yWgAV7ViHF4ATOQAFMABxI3 cWM0B6tWhQjoduIWd7nXgC20hXfHbkOBPRSYECFgAchQg4VYiMyQhikAAjdwAStgAydyIm1yARVA AQXQASvQhzYSAA2AAav4iq/4g0AYiyRwATRQAiqgAggwAxYgA7t4AAcQAjcIjBTSAgYwAySADOB4 iMkoi7uCAQuQJBYgZj3FfQOwDNpYJSnQAROAAZozjuS4AAsAfzLgAGzyACzYfXX4jlVSAmVAfQ+w MCRgAyRAAvhIMCmCXNtXAAYQAu4okHryAzaAARNgjQYJJxNAfRF5AAaQAy2QjRYpdWBQBV2QawrA gpLHfQpgAA1ggiMrYJInKWxIsRhfUAU82ZMj0Iwr8AM3qY3E9ntVV3lDWSUBAQA7 --oneoehhugufmkbqz Content-Type: image/gif Content-Transfer-Encoding: base64 Content-ID: <fwmbvhw> R0lGODlhDAAMANUAAP////f3//f39+/v9+/v797m987W787W5sXW5rXF76295qW975y175St75St 3pSlzoyl1oSl5oylzoycxXOU3nOMxWOM5mOM3mOE1lqE3mOEvVKE1lp7xVJ71lJ7zlJ7xVJ7vUp7 zkpzzkpzxVJzrUprvUJrxUJrvUJjtTpjtTpjrTparTpapQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAADAAMAAAIjAABAAhwwMGFCxAQ CACwkICDDBYSLGjQwQEBhg8zDBAIYIEIBwIQdLjAoOOFgSFMIICwIUMEAxQwCBxhAgKHDh5C6DQA IIGJEyA4fPAwYoQCAAVKoEgBQsKJEidQ8CyRYumDA1VTqNBQQYXXFQofsPB6AIAKFiweNBTLoiza BxcFCjgwgQSJCQcWCggIADs= --oneoehhugufmkbqz-- --osonvhkcnkkyjj Content-Type: application/x-compressed; name="patch31.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment --osonvhkcnkkyjj-- Tag: PARTINFO does not match documentation Tag: 45616
  - 4
    - Future versions of Platform Builder Below are some unbalanced comments and questions about platform builder. Basically you can do a lot with PB, but there are also lots that could be improved. I'd like to hear something about the planning of future versions of platform builder. Any comments from Microsoft folks are more than welcome. ****************************** Will it be integrated with VS.NET? Editor, plugins, better debugger, working intellisense etc.? Will it be possible to use with source control easier? You're now basically forced to have all your code under C:\WINCE420. This shouldn't be needed. I would like to build all my code with read-only access to the C:\wince420 directory. All code build should be somewhere else, so I easily can get a fresh copy of my own code from source control and put it somewhere else and build. Suppose I check something into the source control and want to get a fresh copy to some other directory and rebuild to see that my checkin was ok (I didn't forget to add files etc.). I believe you MS folks call this "buddy build". Will it be possible to use with command line builds without invoking platform builder? Today, wince.bat does NOT give the same options as "Open Build Release Diretory" does. See for instance: http://groups.google.com/groups?hl=sv&lr=&ie=UTF-8&oe=UTF- 8&threadm=OsQ2SN2SDHA.1556% 40TK2MSFTNGP10.phx.gbl&rnum=36&prev=/groups%3Fq%3Dcommand% 2Bline%2Bbuilds% 2Bgroup:microsoft.public.windowsce.platbuilder.*% 2Bgroup:microsoft.public.windowsce.platbuilder.*% 2Bgroup:microsoft.public.windowsce.platbuilder.*%26hl% 3Dsv%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group% 3Dmicrosoft.public.windowsce.platbuilder.*%26start%3D30% 26sa%3DN Automated builds for an OEM is a necessity. Other parts of Microsoft seem to use it consistently for all products. But doing daily builds with PB, maybe followed by smoke tests, is not trivial. Project? Platform? The terminology is a pain to get into compared to "normal" windows development. CEC files? Ever heard of XML? BIB files? A few hours of brain storming should give you better solutions to much of this. QFE Updates!!! It's a pain to apply updates today, I don't think I need to describe details about why. Dr. Watson support for CE applications? I'd like my OEM device to gather crash dumps. Will it be possible to get .dmp files on a CE device and load in some debugger (similar to the way you do in windbg, and load symbols from a path to a matching build) Guess I could go on forever... But I think the bullets above are some important things to fix. And certainly a competetive advantage compared to Embedded Linux or Symbian environments. Comments? Tag: PARTINFO does not match documentation Tag: 45611
  - 5
    - How to create my own file system? Hi all, I want to use the PSM included in Platform builder 4.2 (StrataFlash NOR DRIVER). I think I have to create my own FSD(file system driver) but I don't know how to do that. Do you know where can I find documentations about that. Or can someone give me the main steps to do that. Best regards. Thank you. Tag: PARTINFO does not match documentation Tag: 45607
  - 6
    - updating BinFile This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C3B90A.D350DF50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Is there a stand alone tool that would allow .BIN file updates (adding = or updating modules and files and updating registry) without using PB to = regenerate completely the BIN file The goal is to allow some certified apps developper to update their = applications in a specific .BIN file that could be downloaded to the = device. Thanks Yannick --=20 ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com T=E9l : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- ------=_NextPart_000_0025_01C3B90A.D350DF50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial = size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there a stand alone tool that would = allow .BIN=20 file updates (adding or updating modules and files and updating = registry)=20 without using PB to regenerate completely the BIN file</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>The goal is to allow some certified = apps developper=20 to update their applications in a specific .BIN file that could be = downloaded to=20 the device.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Yannick</FONT></DIV> <DIV><FONT face=3DArial size=3D2> </DIV> <DIV><BR>--=20 <BR>----------------------------------------------------------------<BR>Y= annick=20 Chamming's<BR>ADESET<BR>Windows Embedded=20 Manager<BR>ychammings_AT_adeset_DOT_com><BR><A=20 href=3D"http://www.adeset.com">http://www.adeset.com</A><BR>T=E9l  = : +33=20 (0)4.72.18.57.77<BR>Fax : +33=20 (0)4.72.18.57.78<BR>-----------------------------------------------------= -----------<BR></DIV></FONT></BODY></HTML> ------=_NextPart_000_0025_01C3B90A.D350DF50-- Tag: PARTINFO does not match documentation Tag: 45601
  - 7
    - BinFS usage This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C3B90A.55150BC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Is there a way to have punctual Read/Write access through BinFS : the = goal is to perform image updates in NAND Flash while executing in SDRAM --=20 ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com T=E9l : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- ------=_NextPart_000_0015_01C3B90A.55150BC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there a way to have punctual = Read/Write access=20 through BinFS : the goal is to perform image updates in NAND Flash while = executing in SDRAM</FONT></DIV> <DIV><FONT face=3DArial size=3D2><BR>--=20 <BR>----------------------------------------------------------------<BR>Y= annick=20 Chamming's<BR>ADESET<BR>Windows Embedded=20 Manager<BR>ychammings_AT_adeset_DOT_com><BR><A=20 href=3D"http://www.adeset.com">http://www.adeset.com</A><BR>T=E9l  = : +33=20 (0)4.72.18.57.77<BR>Fax : +33=20 (0)4.72.18.57.78<BR>-----------------------------------------------------= -----------<BR></FONT></DIV></BODY></HTML> ------=_NextPart_000_0015_01C3B90A.55150BC0-- Tag: PARTINFO does not match documentation Tag: 45600
  - 8
    - eshell equivalent under ce 4.2 This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C3B90A.29E30060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Is there an equivalent app to eshell under PB 4.2 that would allow us to = perform image downloading through ethernet from a workstation that do = not have PB installed ? --=20 ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com T=E9l : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- ------=_NextPart_000_000A_01C3B90A.29E30060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Is there an equivalent app to eshell = under PB 4.2=20 that would allow us to perform image downloading through ethernet from a = workstation that do not have PB installed ?</FONT></DIV> <DIV><FONT face=3DArial size=3D2><BR>--=20 <BR>----------------------------------------------------------------<BR>Y= annick=20 Chamming's<BR>ADESET<BR>Windows Embedded=20 Manager<BR>ychammings_AT_adeset_DOT_com><BR><A=20 href=3D"http://www.adeset.com">http://www.adeset.com</A><BR>T=E9l  = : +33=20 (0)4.72.18.57.77<BR>Fax : +33=20 (0)4.72.18.57.78<BR>-----------------------------------------------------= -----------<BR></FONT></DIV></BODY></HTML> ------=_NextPart_000_000A_01C3B90A.29E30060-- Tag: PARTINFO does not match documentation Tag: 45599
  - 9
    - Using an ISAPI extension I have written an ISAPI extension dll and have included in my build. It gets placed in the "Release" directory of the target and I can't cut and paste it to any other directory (an error 18 results). How can I specify what directory to write this dll to instead of it being placed in the "Release" directory automatically? Thanks, Jim Tag: PARTINFO does not match documentation Tag: 45595
  - 10
    - IOCTL_DISK_SCAN_VOLUME documentation Hi, I am looking for IOCTL_DISK_SCAN_VOLUME input structure documentation. MSDN says there aren't any parameters passed to DeviceIOControl but I know there are some, specifically the #define SCANVOL_QUICK 0x00000001 parameter. Do you know of any other parameters that can be passed to the device driver with this I/O? Thanks, Anton Tag: PARTINFO does not match documentation Tag: 45593
  - 11
    - LNK4099 in Wince.net 4.2 Hi I can build PSM and add it to my platform, but lots of LNK4099 warnings are generated, this did not happen in wince300, I have looked through earlier postings and realise that this was a bug wince 4.1. I thought it had been fixed in 4.2. Its only a warning, but its irritating, is there anyway of surpressing it. Regards d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fin dfunc.obj) : warning LNK4099: PDB 'psmfsd.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmfsd.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fil edir.obj) : warning LNK4099: PDB 'psmfsd.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmfsd.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(sys func.obj) : warning LNK4099: PDB 'psmfsd.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmfsd.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(dll main.obj) : warning LNK4099: PDB 'psmfsd.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmfsd.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(psm _cmn.obj) : warning LNK4099: PDB 'psmcmn.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmcmn.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(os_ api.obj) : warning LNK4099: PDB 'oslib.pdb' was not found with 'PSMFSD.LIB' or at 'D :\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\oslib.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(uid .obj) : warning LNK4099: PDB 'dataobj.pdb' was not found with 'PSMFSD.LIB' or at 'D: \WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\dataobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(seq table.obj) : warning LNK4099: PDB 'dataobj.pdb' was not found with 'PSMFSD.LIB' or a t 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\dataobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(mul ti.obj) : warning LNK4099: PDB 'dataobj.pdb' was not found with 'PSMFSD.LIB' or at ' D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\dataobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(do_ int.obj) : warning LNK4099: PDB 'dataobj.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\dataobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(do_ api.obj) : warning LNK4099: PDB 'dataobj.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\dataobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(has htbl.obj) : warning LNK4099: PDB 'fileobj.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\fileobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fo_ cache.obj) : warning LNK4099: PDB 'fileobj.pdb' was not found with 'PSMFSD.LIB' or a t 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\fileobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fo_ find.obj) : warning LNK4099: PDB 'fileobj.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\fileobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fo_ int.obj) : warning LNK4099: PDB 'fileobj.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\fileobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fo_ files.obj) : warning LNK4099: PDB 'fileobj.pdb' was not found with 'PSMFSD.LIB' or a t 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\fileobj.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(ba_ int.obj) : warning LNK4099: PDB 'basalloc.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\basalloc.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(ba_ binfo.obj) : warning LNK4099: PDB 'basalloc.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\basalloc.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(ba_ lbt.obj) : warning LNK4099: PDB 'basalloc.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\basalloc.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(ba_ api.obj) : warning LNK4099: PDB 'basalloc.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\basalloc.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(ba_ alloc.obj) : warning LNK4099: PDB 'basalloc.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\basalloc.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fg_ int.obj) : warning LNK4099: PDB 'foregnd.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\foregnd.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fg_ api.obj) : warning LNK4099: PDB 'foregnd.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\foregnd.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(rec _int.obj) : warning LNK4099: PDB 'reclaim.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\reclaim.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(rec _api.obj) : warning LNK4099: PDB 'reclaim.pdb' was not found with 'PSMFSD.LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\reclaim.pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fla shold.obj) : warning LNK4099: PDB 'psmflashinterface.pdb' was not found with 'PSMFSD .LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmflashinterface .pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fla shlib.obj) : warning LNK4099: PDB 'psmflashinterface.pdb' was not found with 'PSMFSD .LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmflashinterface .pdb'; linking object as if no debug info d:\wince420\platform\intel_sa1110_assabet\drivers\psm\src\fsd\psmfsd.lib(fla shapi.obj) : warning LNK4099: PDB 'psmflashinterface.pdb' was not found with 'PSMFSD .LIB' or at 'D:\WINCE420\PLATFORM\Intel_SA1110_Assabet\Drivers\PSM\BIN\psmflashinterface .pdb'; linking object as if no debug info BUILD: Done Tag: PARTINFO does not match documentation Tag: 45592
  - 12
    - WinCE 4.1 PB Hi all, We want to have a WinCE 4.1 Platform Builder. It is not currently available for download. Can you please tell me where can I get the 4.1 PB? Actully, I am having SA1110 based STB board (like Assabet kit). Currently it is runing on Linux and I want to port Windows CE. For this, WinCE 4.2 PB does not have BSP support, while PB4.1 has support for the same. Please help us in identifying the correct PB version for the same. Right now we thought of going ahead with PB4.1 Thanks in Advance, ashok. Tag: PARTINFO does not match documentation Tag: 45589
  - 13
    - Color Common dialog What are the basic colors the Color Common dialog displays when the display is in 4bpp ? I've got the PXA25x hardware running in 8bpp mono mode, but have the driver setup as 4bpp. I've stuffed a full 256 entry palette in the hardware and the basic colors that display in the color common dialog are not the first 16 entries in the palette. They also don't appear to be 16 individual colors. When I change the first and 16th entry in the hardware palette, more than one color changes on the Color Common Dialog. CE 4.1 ARMV4I Tag: PARTINFO does not match documentation Tag: 45588
  - 14
    - How to notify "LINE DISCONNECTION" to the upper layer of COM port driver? Hi? I wrote CDC modem driver (Host side USB Serial port driver - actually, modem device) and I'm tying to stablize it. I did connect (remote connection) and then forced my device to be entered sleep mode. And then I did push power button for wake-up. After power up (wakeup), the CDC device is actually in disconnected state. But, the upper layer of CDC port driver - maybe UNIMODEM or RAS - do retry to connect again. Ofcourse I don't want such a result. Simply, I hope to announce to the upper layer the line is disconnected. How can I get I want? ** I'm working under PocketPC 2003 OS. ** Thanks in advance. Tag: PARTINFO does not match documentation Tag: 45582
  - 15
    - =?iso-8859-1?Q?=22!AFD__Unable_to_get_proc_address_of_ReadyToGo_in_DHCP=22?= We find the following message in the trace : "!AFD Unable to get proc address of ReadyToGo in DHCP" What does it mean ? May it cause problems in execution of DHCP. We use for DHCP.dll the code done by Platform BUILDER 4.2. Thanks. Tag: PARTINFO does not match documentation Tag: 45580
  - 16
    - Image/Apps upgrade through USBD Hi all, We are working on the processus of deployment and image upgrade for our product. We have various types of components : - The OS which we are developping - The certified apps which are developped either by us or certified partners - The non certified apps which are developped by whoever All these components are stored in NAND Flash. The OS is currently a bin file expanded in RAM by the bootloader. The apps are currently stored "as is" in a FAT partition. We want that the user of our product could not remove neither the OS nor the certified apps Neither our apps developer nor our users will have platform builder. The only communication link available is an USB Device port We are wondering what would be the best strategy for OS and certified apps deployment and upgrade. For the OS (which is a bin file in NAND), we can see two possible paths : - either an upgrade at boot level, using an RNDIS driver for the USB Device port, and a dedicated application on PC side that would answer to eboot to perform the download. Concerning this last point, it seems that eshell is no more available in CE.NET : is there a little PC tool that could be used for this without having the whole PB installed ? - either an upgrade at OS level, using ActiveSync to download the NK.BIN file from PC to target, and using BinFS to update the BIN file in NAND. This solution implies that we could use BinFS with a write access, and that we could secure this write access so that we could activate it only when performing update. Do you know if it's possible ? For the certified apps, we are thinknig of two types of implementation : - either storing them as an independent BIN file. In this case, the upgrade could be done the same way as the OS. The question is, how we could allow the generation of BIN file to our apps developer without distributing them PB - either storing them as is in a FAT partition. As we don't want the user to be able to remove the apps, it implies that this partition is read only, and is temporarily put in write access when performing the update From this various solutions and implementations requirements, what are your advises and comments ? Thanks a lot for your answers, Yannick -- ---------------------------------------------------------------- Yannick Chamming's ADESET Windows Embedded Manager ychammings_AT_adeset_DOT_com> http://www.adeset.com Tél : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- Tag: PARTINFO does not match documentation Tag: 45578
  - 17
    - Synchronisation between Kernel and Device Driver Hi everyone I am having a dilemma here... We have an external RTC Chip which has buffered SRAM as well. The Kernel accesses the RTC HW for time related matters through OEMSetRealTime() and such. There is also a stream device driver for the SRAM section which accesses the RTC HW. I originally intended to use a named mutex to protect access to the RTC HW - but since the Kernel cannot use mutexes I do not know how to handle this. I thought about moving all RTC HW Access functions into Kernel and use a CriticalSection to protect them. This way the device driver would have to use Kernel functions to access RTC HW instead of direct access. Does anyone know if this is how it should be done or if there is a better way? What is the way to access Kernel functions from a device driver? Any comments welcome -Michael Tag: PARTINFO does not match documentation Tag: 45575
  - 18
    - Problem with "for" instructions When I use "for" instructions in my Stream Drivers, all is OK in debug mode but it happens really strange thinks in release mode. I have verified I do not have timing problems. Did anybody have an analogous problem. How did you solve it? Thank you. Tag: PARTINFO does not match documentation Tag: 45571
  - 19
    - How to compile driver source To begin with i create a platform, build it, then I go to command line from Build-->Open release Directory where I build my sources, but encounter the problem below Compiling .\mydriver. cl : Command line error D2004: '/I' requireds an argument. Tag: PARTINFO does not match documentation Tag: 45565
  - 20
    - CE 4.2 Biosloader - Why Reloctated to 0000:1000? Hello, what is the reason why the BIOSLOADER of Windows CE 4.2 was relocated to the Loadaddress 0000:1000? As far as I know the Windows CE 4.1 BIOSLOADER was located at 0000:0700. Regards Peter Tag: PARTINFO does not match documentation Tag: 45562
  - 21
    - CE 4.2 Biosloader - Why Reloctated to 0000:1000? Hello, what is the reason why the BIOSLOADER of Windows CE 4.2 was relocated to the Loadaddress 0000:1000? As far as I know the Windows CE 4.1 BIOSLOADER was located at 0000:0700. Regards Peter Tag: PARTINFO does not match documentation Tag: 45561
  - 22
    - Find "ntcompat.h" Hi all can anyone tell me where can i find this file "ntcompat.h"? It is not in SDK eVC++ 3.0. Regards Ken Tag: PARTINFO does not match documentation Tag: 45555
  - 23
    - ECP mode Hi all, I use wince410. I know that parallel.dll initialize Parallel port as ECP mode. I want to use parallel port as SPP mode. Is it possible? Thanks. Tag: PARTINFO does not match documentation Tag: 45551
  - 24
    - CE 4.2 NDIS DEBUGCHK Hi guys, I'm working on an NDIS miniport driver and am seeing a debugcheck in NDIS miniport.c line 2921. The callstack does not show my driver, but does show NDIS DPC functions. Can anyone tell me what the check at 2921 is? Thanks! Mike Tag: PARTINFO does not match documentation Tag: 45549
  - 25
    - Printing problems with CE 4.2? Hello All, Is anyone else having problems printing to parallel port printers in CE 4.2? We have several printers that print just fine under CE 4.0 but time out under CE 4.2. The printers that fail include dot matrix printers and PCL printers such as an HP 2300n, Deskjet 870Cse. Other printers print just fine in both versions, HP 5p, HP 4000, etc... Thanks, Bill Boyles Tag: PARTINFO does not match documentation Tag: 45527

Hi,

From the PB 4.2 help, there is a member of the tagPARTINFO structure,
snFirstSector, that defines the first sector of a partition. However in
storemgr.h in the SDK folder, the tagPARTINFO structure has no such member.

Anyone have info on this?

Thanks,
Nick.

Top