direct3d mobile driver

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - RAS on Virtual Serial Port (ethernet) Hi we have WinCE4.2 device . I want to add web browsing ( internet) in my device .I am planing to use RAS . This will use a virtual serial port ,that will actually be mappped to ethernet controller for sending and receiving data. and this etehrnet cabel will be connected to CDMA MODEM. 1. Is it feseable ..? 2. Just sending and receiving data through ethernet controller(No need to impelement NDIS or miniport) ..am i correct ot not..? Please answer ..so that i can procede Regards Manish Tag: direct3d mobile driver Tag: 82184
  - 2
    - Ceplayer not work Dear All, I meet a problem when I change the display driver. Anyone can help me ? I use the via display dirver to instead of the ddi_flat. The system is ok. But the ceplayer can not display any pictures, but sound is not. Thanks Gpeica Tag: direct3d mobile driver Tag: 82179
  - 3
    - Problem in Jumbing to image Hello, I am working in Pxa270 with Wince5.0. After download the Nk.bin in Sdram,it cant jumb to image. i am getting the given below in my hyperterminal. ROMHDR at Address 80100044h Download successful! Jumping to image at 0x80101000 (physical 0xA0101000)... !OEMEthGetFrame Got EDBG_CMD_JUMPIMG Got EDBG_CMD_CONFIG, flags:0x0000000F >>here stoped(nothing happend after this)<<< is it kernel initialization problem? if it is, please let me know the possibilities to solve this problem. Do i need any modification in config.bib? please help me . here i have given config.bib and oemaddress table. config.bib ----------- MEMORY IF IMGFLASH! ; Name Start Size Type ; ------- -------- -------- ---- RSVD 80000000 000FF000 RESERVED ARGS 800FF000 00001000 RESERVED NK 80100000 03000000 RAMIMAGE RAM 83100000 00F00000 RAM ENDIF IF IMGFLASH RSVD 80000000 000FF000 RESERVED ARGS 800FF000 00001000 RESERVED NK 86600000 03000000 RAMIMAGE RAM 80100000 03F00000 RAM ENDIF ; Reserve ZBANK virtual block (No physical memory ; is required to back this virtual range). ; ZBANK 96500000 00100000 RESERVED CONFIG IF IMGFLASH ! AUTOSIZE=ON ENDIF KERNELFIXUPS=ON ; @CESYSGEN IF !NK_NKNOCOMP COMPRESSION=ON ; @CESYSGEN ENDIF !NK_NKNOCOMP ; @CESYSGEN IF NK_NKNOCOMP COMPRESSION=OFF ; @CESYSGEN ENDIF NK_NKNOCOMP IF IMGPROFILER PROFILE=ON ELSE PROFILE=OFF ENDIF ; ; ROMFLAGS is a bitmask of options for the kernel ; ROMFLAGS 0x0001 Disallow Paging ; ROMFLAGS 0x0002 Not all KMode ; ROMFLAGS 0x0010 Trust Module only ; IF IMGTRUSTROMONLY IF IMGNOTALLKMODE ROMFLAGS=12 ELSE ROMFLAGS=10 ENDIF ELSE IF IMGNOTALLKMODE ROMFLAGS=02 ELSE ROMFLAGS=00 ENDIF ENDIF g_oalAddressTable ------------------------- DCD 0x80000000, 0xA0000000, 64 ; SANDGATEII: SDRAM (64MB). DCD 0x84000000, 0x5C000000, 1 ; InternalSRAM DCD 0x84100000, 0x58000000, 1 ; Internal memory PM registers. DCD 0x84200000, 0x4C000000, 1 ; USB host controller. DCD 0x84300000, 0x48000000, 1 ; Memory controller. DCD 0x84400000, 0x44000000, 1 ; LCD controller. DCD 0x84500000, 0x40000000, 32 ; Memory-mapped registers DCD 0x88500000, 0x0C000000, 1 ; SANDGATEII: Ethernet controller. DCD 0x88600000, 0x04000000, 32 ; Secondary flash (32MB). DCD 0x8A600000, 0x00000000, 1 ; nCS0: Boot Flash (64MB). DCD 0x00000000, 0x00000000, 0 ; end of table thanks, sakthi Tag: direct3d mobile driver Tag: 82177
  - 4
    - WARNING: Marvell 88W8385 Based Wi-Fi Solutions on Windows CE Hey guys. I've been hesitating to post something like this, but I think I'm frustrated enough at this point to go ahead and do it. If anyone out there is considering using any Wi-Fi modules based on the Marvell 88W8385 chipset under Windows CE 5.0, I strongly recommend you reconsider. Or, at least put whatever you are considering through a very rigorous evaluation before making any design commitments. The company I'm doing work for had committed to a design that used this chipset on a CF interface Wi-Fi module. The assumption was that they would be able to use the NDIS mini-port driver provided by Marvell in their software platform just as they had done with many CF Wi-Fi solutions in the past. Unfortunately, this was not the case. Marvell has provided them with no direct support whatsoever. The module manufacturer they were working with has provided them with no support whatsoever. The sales organization that they were purchasing these modules through managed to provide them with two different drops of driver source code. Neither worked on their platform as-is. After approximately 6 weeks of software effort, they managed to achieve minimal Wi-Fi functionality under very controlled setups. This was not sufficient for their requirements. They are currently in quite a bit of a pickle. Is anyone out there successfully using this chipset? If so, who's drivers are you using? Are there any contacts for people willing to provide high-quality, production-grade software support for this chipset under Windows CE? For everyone else... If you're anything other than a Tier 1 customer to Marvell, be very careful. If any module providers are promising you drivers, make sure you can evaluate them before making any design decisions. (I feel like I just went to confession.) "Frustrated" Tag: direct3d mobile driver Tag: 82166
  - 5
    - Howto eject USB mass storage disk? I expose an USB mass storage partition from my custom Windows CE device. For instance, I can connect a USB cable between my device and a Windows XP computer, and it will appear as a hard drive in Windows XP. From Windows XP I can right click the drive "D:" from "My computer" and select "Eject", which will cause the filesystem to flush correctly on my device and have it unmounted from Windows XP. So eject works fine if initiated from Windows XP. But is there a way from my device to force this "Eject" to happen? I haven't found a way to initiate this, maybe I'm asking for a feature that doesn't exist in USB? Has anyone experience from this? Tag: direct3d mobile driver Tag: 82165
  - 6
    - Problem with suspend/resume on LAN91C111 Hello, I am trying to implement suspend / resume functionality for my LAN91C111 miniport driver on CE 5.0. I'm running into a problem that keeps it from functioning on power up. I've followed the directions in the SMSC documentation for this device for powering down and then powering up the device. I power up and down in response to OID_PNP_SET_POWER requests from NDIS. I believe I am powering down and powering up properly, but my network connection doesn't work after resume. Using netmon, I have verified that my NIC is sending packets out over the network after resume. For example, when I ping my desktop from my CE device, I can see the packets in netmon. Also, when I ping the device from my desktop, I receive the packets on my device (verified by using netstat.exe). I can also see my driver responding to RX interrupts. It seems to me then that my hardware is set up properly on resume, but somehow the protocol driver is messed up. Does anyone have any suggestions for me? Is there a way to re-init the protocol drivers from my miniport driver? Thanks a lot, Jason Tag: direct3d mobile driver Tag: 82164
  - 7
    - Virtual target that's not the emulator I run my WinCE development system on a virtual machine, which makes it impossible to use the emulator platform for testing. So I created another virtual machine, meant to replace the emulator - it brings up eboot and away we go - almost. The virtual machine presents the NIC as an AMD PCNet. How can I modify and/or configure eboot to work with that adapter? -- #include <standard.disclaimer> _ Kevin D Quitt USA 91387-4454 96.37% of all statistics are made up Tag: direct3d mobile driver Tag: 82158
  - 8
    - USB data Transfer question I wrote a USB to Serial driver on CE ARM device. and the write function which write data from USB host to client works fine, but when tried to read data from client, just occasionally get the serial data, most likely, host only read partial data. USB analizer tells that Writing from USB host to Client works fine, but always error when I tried to read data from Client, no matter I got data complete or not. eg. if I write "Hello" in Client, I can read "Hello" in the beginning some times, then I'll get "HHH......" or "lllll....." or "oooo..." randomly. The USB analizer always tells "no data". Any ideas? Tag: direct3d mobile driver Tag: 82148
  - 9
    - 5.0 CEPC Image Problem Hi, I've got a problem I haven't been able to figure out. The problem occurs when trying to boot the image from CF. The CF is connected to an IDE port. Here are the steps I used: 1. Built a debug image 2. Downloaded to CEPC via ethernet - Runs fine. CF fully functional via ATAPI driver. 3. Built a release image 4. Download to CEPC via ethernet - Runs fine. CF fully functional via ATAPI driver. 5. Boot system from CF using LoadCEPC.exe. System loads but doesn't start. I've tried this with and without the hive-based registry and the result is the same. PB is current with all QFEs. I'd welcome any suggestions for things to try. Thanks, Jim Frazer Tag: direct3d mobile driver Tag: 82146
  - 10
    - Implementing Networking in WincE4.2 device we are having a WinCE4.2 based device.I have following questions . Q1 .If we have RAS service(using USB or serial) in our device for internet Access in that case do we need to have ethernet controller..? Q2. If we want to implement networking facility ,then CS8900 ethernet controller will be ok..? Can anybody suggest wht chip set be good to use. Please reply Manish budhia Tag: direct3d mobile driver Tag: 82142
  - 11
    - Can't install SDK Ok, I first installed Platform Builder. Turns out you can only compile trivial applications with Platform Builder. So I installed eMbedded Visual C++ 4.0. Then I made a SDK from platform builder. When I try to install the .msi file it tells me that "Software development tools required to use this SDK... are not installed...", and won't let the SDK install. So what am I supposed to do now??? I'm coming to this from a linux background and finding it absurdly difficult. Has anyone else made this transition - can you offer some help in trying to grasp Microsoft's philosophy? My first impression is that I haven't seen anything this sloppy since OS/2, but I'm trying to keep an open mind. Tag: direct3d mobile driver Tag: 82141
  - 12
    - How to let ActiveSync NOT change the deivce time ? Hi, When I connect device with PC by ActiveSync, I found system time in device will be changed according to Time Zone Setting. It seems time sync is done when ActiveSync is finished. How to prevent ActiveSync from changing the system time in device ? I do not want the solution in PC side because it is not convenient to ask users to change something in their PC when they use our devices. Is it possible to disable the "Time Change by ActiveSync" in device side ? Thanks. Yu. Tag: direct3d mobile driver Tag: 82134
  - 13
    - ExTapi not working hi, I tried to run the ExTAPI application which came with the ssamples of smartphone 2002 sdk. I built it and loaded that in the Motorola MXP200 smartphone. It gave me an error message "unable to get ExTAPI information" The application is not at all getting launched. Has anyone tried that sample? The Tapi sample is working fine. Tag: direct3d mobile driver Tag: 82132
  - 14
    - Can't debug output from Visual Studio 2005 with Platform Builder WM50 Hi, I'm developing WM50 PPC with Platform Builder for Windows Mobile 5.0. As you know, PB has KITL Debugging Functionality. Problem is this. When I made application(test.exe) with EVC++ 4.0, I can download & make BreakPoint at test.exe with PB.(and stop at that point) But, if I make test.exe with Visual Studio 2005, I can download but can't make BreakPoint. It acts like that symbol info is not loaded. I found MS's doc. explaining symbol info file(pdb) from VS2005 is not compatible with PB 5.0. But, their workaround is availble for only Platform Builder for Windows CE 5.0, not Platform Builder for Windows Mobile 5.0. Can you help me to solve this problem? Thanks. Tag: direct3d mobile driver Tag: 82131
  - 15
    - How to show the Software Input Panel when CE 5.0 boot-up ? Dear All, When CE boot-up, I must hit the SIP icon on task bar to show the visual keyboard. I need a function that SIP shown automatically when CE boot-up. Is there any way to do this? Thanks. Tag: direct3d mobile driver Tag: 82129
  - 16
    - Registry Settings For an Ethernet Device Hi, We are developing a driver for an ethernet device which works on PCI Bus. We are having problems with the registry setting of the device. Here are the settings: [HKEY_LOCAL_MACHINE\Comm\MyDevice] "DisplayName"="My Ethernet Driver" "Group"="NDIS" "ImagePath"="MyDevice.dll" [HKEY_LOCAL_MACHINE\Comm\MyDevice\Linkage] "Route"=multi_sz:"PCI\\MyDevice1" [HKEY_LOCAL_MACHINE\Comm\PCI\MyDevice1] "DisplayName"="My Ethernet Driver" [HKEY_LOCAL_MACHINE\Comm\PCI\MyDevice1\Parms\TcpIp] "EnableDHCP"=dword:1 "DefaultGateway"="" "LLInterface"="" "UseZeroBroadcast"=dword:0 "IpAddress"="192.168.56.199" "Subnetmask"="255.255.255.0" "AutoIP"="192.168.56.199" "AutoMask"="255.255.255.0" "AutoSubnet"="192.168.56.0" [$(PCI_BUS_ROOT)\Template\MyDevice] "Class"=dword:02 "SubClass"=dword:00 "ProgIF"=dword:00 "VendorID"=multi_sz:"110A" "DeviceID"=multi_sz:"4036" "Dll"="NDIS.dll" "Entry"="NdisPCIBusDeviceInit" "Prefix"="EDD" "MiniPort"="MyDevice" "IsrDll"="eddisr.dll" "IsrHandler"="ISRHandler" At the begining of the load phase of the driver, a debug message appears: "DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions at (Drivers\BuiltIn\PCI\Instance\MyDevice1). Driver cannot be unloaded." But the driver is loaded succesfully. The device appears under "Network and Dial-Up Connections" with the name "PCI-MYDEVICE1" and when the settings menu is opened, DisplayName can be seen as "'My Ethernet Driver' Settings". Nevertheless, when an "Ipconfig /all" command is executed, the device appears with Adapter Name : "PCI\MYDEVICE1" and Description:"PCI\MYDEVICE1". The questions are: 1 - Why are deprecated load instructions found? 2 - How can we change AdapterName and Description? 3 - Most important, is it right to set "Route"=multi_sz:"PCI\\MyDevice1" under "Comm\MyDevice\Linkage"? When we set "Route"=multi_sz:"MyDevice1", an additional registry entry appears: "comm\MyDevice1" and we can not see a friendly DisplayName under "Network and Dial-Up Connections", just see "PCI\MyDevice1" again. Thanks, Osman Tag: direct3d mobile driver Tag: 82128
  - 17
    - Emulator for ARMV4 Hi, There's only an X86 Emulator in Platform Builder 5.0, Is there an ARMV4I Emulator? I want to debug my ARM version code on PC directly(without connecting to my B.B), how to? Best regards, Jack Zhao Tag: direct3d mobile driver Tag: 82120
  - 18
    - Cirrus EP931x CPU FPU (MaverickCrunch) support? Does anyone know if the WinCE 5.0 ARM compiler supports the hardware floating point coprocessor (MaverickCrunch) used in the Cirrus EP931x range of CPUs? We are interested in using one of these processors, but need hardware floating point support in the compiler. I understand the "standard" ARM FPUs are supported, but it looks like MaverickCrunch is a different animal... Andrew Tag: direct3d mobile driver Tag: 82116
  - 19
    - RAS service for Internet Access Hi ! we want to access Internet from our device (winCE4.2 RAS) using CDMA MODEM(Using PPP) . I let you know that communication media between MODEM and our device will be ethernet cabel. We don't have in build eithernet controller ..we are planing to use CS8900 ethernet controller. What steps i need to do in MY BSP...? Will it require to implement NDIS..?or RAS can be configured to use this ethenet connection. How it will be possible ..? Please answer Regards Manish Tag: direct3d mobile driver Tag: 82115
  - 20
    - Platform Builder error building Mobile Handheld(windows ce device) What is the meaning of below error while building and sysgen Mobile Handheld ( windows ce device) Thanks Error - cannot open input file C:\WINCE500\PBWorkspaces\Mobile2\RelDir\CEPC_x86_Release\postproc\nlscfg.inf makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec). makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec). Tag: direct3d mobile driver Tag: 82114
  - 21
    - Establishing RNDIS over USB I am trying to figure out what are the necessary registry settings, platform builder 5.0 settings, autostart exes on the device, and client side .inf and driver files I need to be able to perform PPP over USB. I have a PXA270 processor that I added RNDIS support to. I am trying to setup the OS such that when the device is plugged via USB to a PC it shows up as a network device. I would like to be able to verify communications via WinSock over this connection. Does anyone know what I need to do to set this all up. Currently, I have added a RAS entry on the device side to try to establish a connection. If I have ActiveSync running the device gets and IP address assigned but the PC side has ActiveSync connecting forever and I never see an IP address. Plus I would like to not use ActiveSync. Thanks Tag: direct3d mobile driver Tag: 82111
  - 22
    - command line tools Does anyone know how to build command line tool to run on windows ce 5.1 build 1702? can we use Platforma builder to build the cmd.exe ? thanks Tag: direct3d mobile driver Tag: 82100
  - 23
    - CE 5.0 TASKMAN Shell -- How???? Hi all. We just moved from CE 4.20 to 5.0, and we're trying to build a desktop-less image. With 4.20 we simply, according to the MSDN docs, included the Standard Shell, and defined __SYSGEN_TASKMAN (2 leading underscores) as 1 in the environment variables, and it always worked fine. The difference between the 5.0 documentation and 4.20, is very subtle. in 4.20 the documentation says to define _SYSGEN_TASKMAN as 1, but the 5.0 docs say SYSGEN_TASKMAN as 1 (no leading underscore). Now, i've tried one, two and three underscores leading the string, but i always get the taskbar, trash, my computer and the CE desktop. Anything i'm missing here? -- P Tag: direct3d mobile driver Tag: 82087
  - 24
    - SYMBOL_LA4137 Hi I am trying get the Symbol La-4137-1020 card to work in our wince.net 4.2 based hardware, but all I get is a dialog box title 'Unidentifed PCCard Adapter and an option the enter the name of the driver. I have added the following files to platform.bib nictt.exe mudll.dll evmon.exe kerb5.dll cewdm.dll trans.dll netwlan.dll nictt.htm splash.wav ssping.wav ssroam.wav arrowr.2bp I added the following to platform.reg [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TRANS] "Prefix"="PRT" "Dll"="TRANS.dll" "Index"=dword:1 "Order"=dword:3 ; TYPE 2 TRILOGY [HKEY_LOCAL_MACHINE\Drivers\PCMCIA\Symbol_Technologies-LA4111_Spectrum24_Wireless_LAN_PC_Card-077d] "Dll"="NDIS.dll" "Prefix"="NDS" "Miniport"="NETWLAN" "Index"=dword:1 ; TYPE 3 TRILOGY [HKEY_LOCAL_MACHINE\Drivers\PCMCIA\Symbol-Spectrum24_LA4100_Series_WLAN_PC_Card-e063] "Dll"="NDIS.dll" "Prefix"="NDS" "Miniport"="NETWLAN" "Index"=dword:1 [HKEY_LOCAL_MACHINE\Comm\NETWLAN] "DisplayName"="Spectrum 24 802.11b" "ImagePath"="NETWLAN.dll" "Group"="NDIS" [HKEY_LOCAL_MACHINE\Comm\NETWLAN\Linkage] "Route"=multi_sz:"NETWLAN1" [HKEY_LOCAL_MACHINE\Comm\NETWLAN1] "DisplayName"="Spectrum 24 802.11b" "ImagePath"="NETWLAN.dll" "Group"="NDIS" [HKEY_LOCAL_MACHINE\Comm\NETWLAN1\Parms\TcpIp] "EnableDHCP"=dword:1 "IpAddress"="0.0.0.0" "Subnetmask"="0.0.0.0" "DefaultGateway"="0.0.0.0" "DNS"="0.0.0.0" "WINS"="0.0.0.0" "UseZeroBroadcast"=dword:0 [HKEY_LOCAL_MACHINE\Comm\NETWLAN1\Parms] "AdapterModel"="Spectrum 24 802.11b" "Version"="3.0.0.0" "Password"="3745A4CA1FD2D1CFC10041C7576C0E6423A815E6D4D094C8D87441C26A6C0211153DDE9C851085" "PowerIndex"=dword:1 ; PSP "RogueAPDetection"=dword:1; "InterruptNumber"=dword:03 ;; "IoMapping"=dword:0 ; 0=NDIS, 1=PCMCIA (1 for WCE211,PPC2000) (0 forWCE300, PPC2002); "IoBaseAddress"=dword:300 ;; "IoLength"=dword:46 ;; "MemoryMappedBaseAddress"=dword:D0000 ;; "MemoryMappedSize"=dword:1000 ;; "PowerIndex"=dword:1 ;; "CardType"=dword:0 ; PCMCIA; "Environment"=dword:2 ; WINCE; "BusType"=dword:8 ; PROVIDED BY NDIS; "BusNumber"=dword:0 ; PROVIDED BY NDIS; "NetworkAddress"=dword ; PROVIDED BY NDIS; "InterruptNumber"=dword:03 ; 3; "IoBaseAddress"=dword:300 ; 768; "IoLength"=dword:46 ; 70; "MemoryMappedBaseAddress"=dword:D4000 ;; "MemoryMappedSize"=dword:1000 ;; "PowerIndex"=dword:1 ; PSP; "Channel"=dword:0 ; 0; "Ess_TxPower"=dword:0 ; AUTO; "Adhoc_TxPower"=dword:0 ; FULL; "LongPreamble"=dword:0 ; ENABLED; "Diversity"=dword:0 ; BOTH ANTENEA; "PCCARDPacketFilter"=dword:0B ; BROADCAST, DIRECTED, AND MULTICAST; "DTIM_Delay"=dword:1 ; 1; "RTS_Threshold"=dword:640 ; 1600; "FragmentationThreshold"=dword:0 ; 0; "MBIT_11"=dword:1 ; ENABLED; "MBIT_5_5"=dword:1 ; ENABLED; "MBIT_2"=dword:1 ; ENABLED; "MBIT_1"=dword:1 ; ENABLED; "IntlRoaming"=dword:0 ; DISABLED; "PortType"=dword:1 ; BSS; "Mandatory_BSS_ID"="" ; BLANK; "ESS_ID"="ANY" ; ANY; "EncryptionKeyId"=dword:0 ; KEY 0; "MUEncryptionAlgorithm"=dword:1 ; OPEN SYSTEM; "StationName"="" ;; "Provider"="Symbol" ;;[HKEY_LOCAL_MACHINE\Comm\Cxport]; Enable the device to suspend while communicating;"NoIdleTimerReset"=dword:1But it still refuses to recognise the card and propts me to enter the nameof the driver.Regards Tag: direct3d mobile driver Tag: 82082
  - 25
    - "Empty file name" I'm trying to port a rather large appliction to WinCE 5.0 using Platform Builder. I'm just evaluating WinCE at this point, and so far it doesn't look like Platform Builder is designed for large, multi-directory applications. So I moved all the source files to one directory. If I build with clean most of the sources compile, with a few errors. If I fix those errors and then re-build, I get: BUILD: [00:0000000009:ERRORI] Empty file name. I can find no clue as to what this means. And btw, the doc on running BUILD.EXE from a command line - the -x options in the doc do not match what BUILD.EXE recognizes. Close, but not the same. Tag: direct3d mobile driver Tag: 82080
- Next
  - 1
    - Windows CE 5.0 boot failure when USB thumb drive left attached I have a Windows CE 5.0 image on a system that works fine until power is cycled with a USB thumb drive left attached. The system enters a state of constant reboot with the USB drive attached. Removing the USB drive results in an eventual successful CE load (it may take several load / reboot attemtps). Any help, thoughts, or suggestions would be appreciated... Here is the debug output from a load failure: Debug Serial Init SysInit: GDTBase=80fa40e8 IDTBase=80ff6340 KData=81015800 Windows CE Kernel for i486 Built on Jun 24 2004 at 18:28:19 g_pPageDir = 8102e000 PCIBIOS:: BIOS Address static map to addr=a00e0000 GetPicRoutingIrqTable: Start search_pci_bios start CE Ethernet Bootloader found 32Bit BIOS Entry master_bios32=a00f79b0 bios32_call_offset=1d850 for CE/PC Return from First BIOS EAX=49435000 EBX=fd850,ECX=7b0 EDX=12c 32 PCI BIOS offset located.addr=1d97c 32 PCI BIOS Present EDX=20494350,EAX=1 EBX=f0210,ECX=700 +GetRoutingOption search_pci_routing search_pci_routing found entry =a00fdf50 CE/PC GetRoutingOption, found ROM version for Routing table. GetRoutingOption return SUCCESS .AH=0 canConfiguredIrq with PCI Exclusive Irq Bit (wExClusive) =0 ScanConfigureIrq: BufferSize = 112 @ address 80ff9daa ScanConfigureIrq: for Bus=0 ,Device=19 SlotNumber=0 INTA_LinkValue=1,INTA_IrqBitMap=def8 INTB_LinkValue=0,INTB_IrqBitMap=def8 INTC_LinkValue=0,INTC_IrqBitMap=def8 INTD_LinkValue=0,INTC_IrqBitMap=def8 ScanConfigureIrq: LinkNumber=1 associated with irq=11 ScanConfigureIrq: for Bus=0 ,Device=15 SlotNumber=0 INTA_LinkValue=1,INTA_IrqBitMap=def8 INTB_LinkValue=0,INTB_IrqBitMap=def8 INTC_LinkValue=0,INTC_IrqBitMap=def8 INTD_LinkValue=0,INTC_IrqBitMap=def8 ScanConfigureIrq: LinkNumber=1 associated with irq=11 ScanConfigureIrq: for Bus=0 ,Device=16 SlotNumber=0 INTA_LinkValue=2,INTA_IrqBitMap=def8 INTB_LinkValue=0,INTB_IrqBitMap=def8 INTC_LinkValue=0,INTC_IrqBitMap=def8 INTD_LinkValue=0,INTC_IrqBitMap=def8 ScanConfigureIrq: LinkNumber=2 associated with irq=10 ScanConfigureIrq: for Bus=0 ,Device=10 SlotNumber=1 INTA_LinkValue=1,INTA_IrqBitMap=def8 INTB_LinkValue=2,INTB_IrqBitMap=def8 INTC_LinkValue=3,INTC_IrqBitMap=def8 INTD_LinkValue=4,INTC_IrqBitMap=def8 ScanConfigureIrq: for Bus=0 ,Device=11 SlotNumber=2 INTA_LinkValue=2,INTA_IrqBitMap=def8 INTB_LinkValue=3,INTB_IrqBitMap=def8 INTC_LinkValue=4,INTC_IrqBitMap=def8 INTD_LinkValue=1,INTC_IrqBitMap=def8 ScanConfigureIrq: for Bus=0 ,Device=12 SlotNumber=3 INTA_LinkValue=3,INTA_IrqBitMap=def8 INTB_LinkValue=4,INTB_IrqBitMap=def8 INTC_LinkValue=1,INTC_IrqBitMap=def8 INTD_LinkValue=2,INTC_IrqBitMap=def8 ScanConfigureIrq: for Bus=0 ,Device=13 SlotNumber=4 INTA_LinkValue=4,INTA_IrqBitMap=def8 INTB_LinkValue=1,INTB_IrqBitMap=def8 INTC_LinkValue=2,INTC_IrqBitMap=def8 INTD_LinkValue=3,INTC_IrqBitMap=def8 InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0, dwDfltType = 0) ... CEPC Firmware Init RTC - Status Reg B - 0x02 g_dwCPUFeatures = 00808131 OEM Extra DRAM Detected @ base = xA1C00000, size=36 MB Looking for rom chain Rom chain NOT found Firmware Init Done. Error Reporting Memory Reserved, dump size = 00020000 Booting Windows CE version 5.00 for (x86) &pTOC = 802279d8, pTOC = 80fa1ce8, pTOC->ulRamFree = 8102e000, MemForPT = 00024000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 12170, Secondary pages: 0, Filesystem pages = 6085 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 81053000, extension: 00003000, length: 02f8a000 X86Init done, OEMAddressTable = 8023dc98. Windows CE KernelInit Updated eptr->e32_vsize to = 00090000 Scheduling the first thread. 0x83fdf030: KernelInit2: pCurThread=83fdf030 hCurThread=03fdf1de hCurProc=03fdf002, KernelInit = 80260db0 0x83fdf030: Updated eptr->e32_vsize to = 00005000 0x83fdf030: Updated eptr->e32_vsize to = 00022000 0x83fdf030: Updated eptr->e32_vsize to = 00007000 0x83fdf030: Updated eptr->e32_vsize to = 00018000 0x83fdf030: ERROR: E:\macallan\private\winceos\COREOS\nk\kernel\nknormal\..\kwin32.c line 777: 0x83fdf030: ConnectDebugger failed 0x83fdf030: first = 01f10000, last = 02000000, SharedDllBase = 03190000 0x83fdf030: Did not find emulation code for x86... using floating point hardware. 0x83fcd9dc: CertMod.dll not found, using old OEM Trust Model 0x83fcd9dc: FileSystem Starting - starting with clean file system 0x83fcd9dc: FS: initializing ROM/RAM file system 0x83fcd9dc: SC_CreateAPIHandle: pvData == NULL 0x83fcd9dc: FS: Registering file system ROM, index 2, flags 0x00000031 0x83fcd9dc: FS: Mount complete (ROM, index 2, flags 0x00000031) 0x83fcd9dc: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 0x83fcd9dc: Succeeded on CheckFile 0x83fcd9dc: RestoreFile(0xe3fb2e22) called fDelete = TRUE 0x83fcd9dc: PCIReg(key: , device: 0/0/0) 0x83fcd9dc: FS: Registering file system StoreMgr, index 3, flags 0x00000001 0x83fcd9dc: OEMIoControl: Unsupported Code 0x10100cc - device 0x0101 func 51 0x83fcd9dc: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 0x83fcd9dc: FSREG: Logging in default user. 0x83fcd9dc: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 0x83fcf800: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 0x83fcd9dc: SetCurrentUser: Logging out (nobody), logging in default 0x83fcd9dc: FS: Using default path "\profiles\" 0x83fcd9dc: BuildPath: profiles 0x83fcd9dc: BuildPath: profiles\default 0x83fcd9dc: SetCurrentUser: User hives not supported -- using same registry for all users 0x83fcd9dc: FS: Using default path "Windows\" 0x83fcd9dc: OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 0x83fcd9dc: OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 0x83fcd9dc: FS: Using default path "Windows\" 0x83fcd9dc: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars 0x83fcd9dc: Initializing Database 0x83fcd9dc: DB:Validation: Name already exists DB_notify_events 0x83fcd9dc: DB:CeCreateDatabase failed 0x83fcd9dc: Filesystem initialized! 0x83fcd9dc: FILESYS: Waiting for kernel to be ready to launch apps 0x83fcfcb0: InitMUI: DISABLED (-2145016752) 0x83fcd9dc: FS: Creating signal event SYSTEM/DevMgrApiSetReady 0x83fcd9dc: FS: Creating signal event SYSTEM/PowerManagerReady 0x83fcd9dc: FS: Creating signal event SYSTEM/GweApiSetReady 0x83fcd9dc: FS: Creating signal event ReleaseFSD 0x83fcd9dc: FS: Creating signal event system/events/notify/APIReady 0x83fcd9dc: FS: Creating signal event SYSTEM/ShellAPIReady 0x83fcd9dc: FS: Creating signal event SYSTEM/NLedAPIsReady 0x83fcd9dc: FILESYS: Launching apps 0x83fcd9dc: FILESYS: Launching shell.exe 0x83fcd9dc: FILESYS: Launching device.exe 0x83fcfcb0: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x3fce2f2 *** 0x83fcfcb0: +InitDeviceFileSystems 0x83fcfcb0: FS: Registering file system $device, index 4, flags 0x00000001 0x83fcfcb0: FS: Registering file system $bus, index 5, flags 0x00000001 0x83fcfcb0: -InitDeviceFileSystems: status is 1 0x83fcfcb0: Ceddk!CalibrateStallCounter: Enter 0x83fcd9dc: FILESYS: SignalStarted loop = 2 0x83fcfcb0: Ceddk!CalibrateStallCounter: Could not find stall counter 0x83fcfcb0: Ceddk!BeginCalibration: min(1194) max(1326) 0x83fcfcb0: Ceddk!BeginCalibration: Elapsed is 1315 0x83fcfcb0: Ceddk!BeginCalibration: Delay is 18 0x83fcfcb0: DEVICE!DevloadInit 0x83fcfcb0: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCCARD\Prefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCCARD\BusPrefix) returned 2 0x83fcfcb0: CardBus.DLL DLL_PROCESS_ATTACH 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Serial2\BusPrefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Serial3\BusPrefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NLed\BusPrefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NDIS\BusPrefix) returned 2 0x83fcfcb0: CXPORT:dllentry ProcessAttach 0x83fcfcb0: CXPORT:+GetRegSettings 0x83fcfcb0: CXPORT:-GetRegSettings 0x83fcfcb0: CXPORT:InitBlockPool - Pool(16), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(32), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(48), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(64), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(96), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(128), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(256), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(356), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(476), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(512), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(1024), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(1600), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(2048), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(4096), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(8192), limit 20000 bytes 0x83fcfcb0: CXPORT:InitBlockPool - Pool(-1), limit 20000 bytes 0x83fcfcb0: NDIS: RebindAdaptersOnResume = 0 0x83fcfcb0: NDIS: PcmciaNeedsMapToScrap = 0 0x83fcfcb0: NDIS:: CE_DeleteBusFriendlyNames() failed deleting [HKLM\Comm\BusFriendlyNames] 0x83fcfcb0: DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions at (Drivers\BuiltIn\AFD). Driver cannot be unloaded. 0x83fcfcb0: Can't load library ppp.dll 0x83fcfcb0: !AFD:AfdInitialize: Can't open Registry key Comm\AFD -- creating 'Stacks' entry 0x83fcfcb0: TCPIP: dllentry() 0x83fcfcb0: TCPIP.Register() 0x83fcfcb0: *** New TcpStack *** 0x83fcfcb0: +IPInit() 0x83fcfcb0: +IPGetConfig 0x83fcfcb0: -IPGetConfig: Ret: 0x1006B0 0x83fcfcb0: Dhcp: dllentry() -2081363536 0x83fcfcb0: +DhcpRegister: 0x83fcfcb0: -DhcpRegister: Ret = 36780 0x83fcfcb0: IPInit: registered w/ DHCP 0x83fcfcb0: IPInit: Unable to Load IPSEC 0x83fcfcb0: IGMPDelInclList: AddrPtr=1010e0 NumDelSources=0 DelSourceList=0 0x83fcfcb0: -IPInit [SUCCESS] 0x83fcfcb0: +TCPGetConfigInfo 0x83fcfcb0: -TCPGetConfigInfo 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(TCPIP\IPDevice\BusPrefix) returned 2 0x83fcfcb0: +IPD_Init(802de18) 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(TCPIP\TCPDevice\BusPrefix) returned 2 0x83fcfcb0: +TCP_Init(802de18) 0x83fcfcb0: TCPIP.About to register 0x83fcfcb0: !AFD: Unable to load library 'tcpip6.dll' 0x83fcfcb0: !AFD: Unable to load library 'irdastk.dll' 0x83fcfcb0: !AFD: Unable to load library 'btd.dll' 0x83fcfcb0: RdrMain: DLL_PROCESS_ATTACH, hInst:0x83F0EDD0 0x83fcfcb0: +RDR:Redir helper func: Ctxt:0x0, OpCode:1 0x83fcfcb0: +RDR:InitRedir 0x83fcfcb0: InitRedirConfig: 0x83fcfcb0: ClearTxtPwd: FALSE 0x83fcfcb0: ServerTimeoutMs: 10000 0x83fcfcb0: FindCacheMaxSize: 8192 0x83fcfcb0: ResourceExpiryInt: 600 0x83fcfcb0: RecvBufSize: 9000 0x83fcfcb0: RecvThreadPrio256: 251 0x83fcfcb0: RegisterFSRoot: TRUE 0x83fcfcb0: SECUR32: Loading package DLL: 'schannel.dll'. 0x83fcfcb0: SECUR32: Loading package DLL: 'ntlmssp.dll'. 0x83fcfcb0: SECUR32: Loading package DLL: 'kerberos.dll'. 0x83fcfcb0: SECUR32: Loading package DLL: 'spnego.dll'. 0x83fcfcb0: SECUR32: Package [1] loaded -- 'Microsoft Unified Security Protocol Provider' 0x83fcfcb0: SECUR32: Package [2] loaded -- 'Microsoft TLS 1.0' 0x83fcfcb0: SECUR32: Package [3] loaded -- 'Microsoft SSL 3.0' 0x83fcfcb0: SECUR32: Package [4] loaded -- 'Microsoft SSL 2.0' 0x83fcfcb0: SECUR32: Package [5] loaded -- 'NTLM' 0x83fcfcb0: SECUR32: Package [6] loaded -- 'Negotiate' 0x83fcfcb0: SECUR32: Locating package 'Negotiate' ...0x83fcfcb0: found (0x00040B20). 0x83fcfcb0: Found Kerberos package 0x83fcfcb0: +RDR:InitNetBIOS 0x83fcfcb0: NETBIOS: NB_NET_NOTIFY for callback at address 0x3994a500x83fcfcb0: Browser initialized 0x83fcfcb0: +RDR:FSAPIInit 0x83fcfcb0: FS: Registering file system Network, index 1, flags 0x00000000 0x83fcfcb0: -RDR:FSAPIInit 0x83fcfcb0: +RDR_Init 0x83fcfcb0: -RDR:InitRedir, initialization successful 0x83fcfcb0: !AFD: Unable to load library 'IPNat.dll' 0x83fcfcb0: Ws2Instl dllentry() -2081552924 0x83fcfcb0: Ws2Instl:IsStackInstalled - LoadLibrary(irdastk) failed 126 0x83fcfcb0: Ws2Instl:IsStackInstalled - LoadLibrary(btd) failed 126 0x83ede000: IPDispatchDeviceControl returned Status 103 0x83fcfcb0: Ws2Instl:IsStackInstalled - LoadLibrary(tcpip6) failed 126 0x83fcfcb0: !AFD: Unable to load library 'DhcpV6L.dll' 0x83fcfcb0: *TCPIP:ReadyToGo 0x83fcfcb0: +ARPInit() 0x83fcfcb0: -ARPInit [0] 0x83fcfcb0: !AFD: Unable to load library 'tcpip6.dll' 0x83fcfcb0: !AFD: Unable to load library 'irdastk.dll' 0x83fcfcb0: !AFD: Unable to load library 'btd.dll' 0x83fcfcb0: !AFD: Unable to GetProcAddress of ReadyToGo in 'Netbios' 0x83fcfcb0: !AFD: Unable to GetProcAddress of ReadyToGo in 'Redir' 0x83fcfcb0: !AFD: Unable to GetProcAddress of ReadyToGo in 'Dhcp' 0x83fcfcb0: !AFD: Unable to load library 'IPNat.dll' 0x83fcfcb0: !AFD: Unable to GetProcAddress of ReadyToGo in 'Ws2Instl' 0x83fcfcb0: !AFD: Unable to load library 'DhcpV6L.dll' 0x83fcfcb0: AFD: Initialization Complete 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix) returned 2 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix) returned 2 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/0/0, Host / PCI Bridge 0x83fcfcb0: VendorID = 0x1078, DeviceID = 0x0001, Command = 0x0007, Status = 0x0280 0x83fcfcb0: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/0/0. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/15/0, Ethernet Network Controller 0x83fcfcb0: VendorID = 0x8086, DeviceID = 0x1209, Command = 0x0117, Status = 0x0290 0x83fcfcb0: RevisionID = 0x10, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x02 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x42, HeaderType = 0x00, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0xFEDA0000 0x00001081 0xFEDC0000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x8086, SubSystemID = 0x000C 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x0B, InterruptPin = 0x01, MinGrant = 0x08, MaxLatency = 0x38 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/15/0. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/16/0, Ethernet Network Controller 0x83fcfcb0: VendorID = 0x8086, DeviceID = 0x1209, Command = 0x0117, Status = 0x0290 0x83fcfcb0: RevisionID = 0x10, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x02 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x42, HeaderType = 0x00, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0xFEDA1000 0x000010C1 0xFEDE0000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x8086, SubSystemID = 0x000C 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x0A, InterruptPin = 0x01, MinGrant = 0x08, MaxLatency = 0x38 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/16/0. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/18/0, PCI / ISA Bridge 0x83fcfcb0: VendorID = 0x1078, DeviceID = 0x0100, Command = 0x000F, Status = 0x0280 0x83fcfcb0: RevisionID = 0x30, ProgIf = 0x00, SubClass = 0x01, BaseClass = 0x06 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/18/0. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/18/1, Other Bridge 0x83fcfcb0: VendorID = 0x1078, DeviceID = 0x0101, Command = 0x0002, Status = 0x0280 0x83fcfcb0: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x80, BaseClass = 0x06 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0x40012000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/18/1. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: ATAPI DLL_PROCESS_ATTACH 0x83fcfcb0: ATAPI:PCIConfig!DeviceConfig+(0) 0x83fcfcb0: ATAPI:PCIConfig!ConfigRsrc+(Bus 0, Device 18, Function 2) 0x83fcfcb0: ATAPI:PCIConfig!ConfigRsrc: BAR(0/18/2): Offset 0x20, Type I/O, Size 0x10 0x83fcfcb0: ATAPI:PCIConfig!ConfigRsrc- 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/18/3, Audio Multimedia Device 0x83fcfcb0: VendorID = 0x1078, DeviceID = 0x0103, Command = 0x0006, Status = 0x0280 0x83fcfcb0: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x01, BaseClass = 0x04 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0x40011000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x1078, SubSystemID = 0x0103 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/18/3. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: Warning: No Match template is found for following PCI Device 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: Bus/Device/Function = 0/18/4, VGA Compatible Display Adapter 0x83fcfcb0: VendorID = 0x1078, DeviceID = 0x0104, Command = 0x0003, Status = 0x0280 0x83fcfcb0: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x03 0x83fcfcb0: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fcfcb0: BaseAddresses: 0x83fcfcb0: 0x40800000 0x40010000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fcfcb0: CIS = 0x00000000, SubVendorID = 0x1078, SubSystemID = 0x584D 0x83fcfcb0: ROMBaseAddress = 0x00000000 0x83fcfcb0: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fcfcb0: ------------------------------------------------------------------------------- 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/18/4. 0x83fcfcb0: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fcfcb0: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fcfcb0: ATAPI DLL_PROCESS_DETACH 0x83fcf800: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 0x83fcfcb0: ATAPI DLL_PROCESS_ATTACH 0x83fcfcb0: ATAPI:PCIConfig!DeviceConfig+(2) 0x83fcfcb0: ATAPI:PCIConfig!ConfigSize+(Bus 0, Device 18, Function 2) 0x83fcfcb0: ATAPI:PCIConfig!ConfigSize- 0x83fcfcb0: ATAPI DLL_PROCESS_DETACH 0x83fcfcb0: ATAPI DLL_PROCESS_ATTACH 0x83fcfcb0: ATAPI:PCIConfig!DeviceConfig+(3) 0x83fcfcb0: ATAPI DLL_PROCESS_DETACH 0x83fcfcb0: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\OHCI1\BusPrefix) returned 2 0x83fcfcb0: HCD driver DLL attach 0x83fcfcb0: HCD!HCD_Init 0x83fcfcb0: OHCD: Read config from registry: Base Address: 0xFEDA2000, Length: 0x1000, I/O Port: NO, SysIntr: 0x10, Interface Type: 5, Bus Number: 0 0x83fcfcb0: OHCD: ioPhysicalBase 0xFEDA2000, IoSpace 0x0 0x83fcfcb0: OHCD: ioPortBase 0x1C0000, portBase 0xFEDA2000 0x83fcfcb0: OHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 11 0x83fcfcb0: DMA buffer passed in from PDD 0x83fcfcb0: CPhysMem Total Alloc Region PhysAddr = 0x0281F000, VirtAddr = 0x001D0000, size = 65536 0x83fcfcb0: CPhysMem Special Alloc Region PhysAddr = 0x0281F000, VirtAddr = 0x001D0000, size = 4096 0x83fcfcb0: CPhysMem HighPri Alloc Region PhysAddr = 0x02820000, VirtAddr = 0x001D1000, size = 16384 0x83fcfcb0: CPhysMem Normal Alloc Region PhysAddr = 0x02824000, VirtAddr = 0x001D5000, size = 45056 0x83fcfcb0: +COhcd::Initialize. Entry 0x83fcfcb0: +CDeviceGlobal::Initialize 0x83fcfcb0: USBD: DLL attach 0x83fcfcb0: +USBD:HcdAttach, hcd: 0x46100 0x83fcfcb0: -CDevice::Initialize, success! 0x83fcfcb0: +CHW::Initialize base=0x1c Tag: direct3d mobile driver Tag: 82073
  - 2
    - kitl debug hi all, I am debugging kitl with SMSC9115 Lan chip. I re-wrote the low level functions. And the chip runs very well . But when I built the kernel with kitl support, the kernel stopped and the PB could not connect with my target board . Please help me to solve this problem. Thanks a lot! zhiqiang 3 7 2006 **************Output message from serial port ******************** OEMInitDebugSerial using UART1 Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 13 2003 at 22:44:13 ProcessorType=0411 Revision=7 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 96cb982c +OEMKitlInit Checking for LAN9115 Ethernet controller...++LAN9115 HardWare Setup! ChipID = 1150001!LAN9115 Ethernet controller initialized.VBridgeInit()...TX = [16384] bytes -- Rx = [16384] byteser [0xB8F09360] to [0xB8F0D360].uffer [0xB8F05340] to [0xB8F09340].Bridge:: NK add MAC: [78-2B-DE-9-4D-9A]ther IP Addr: 192.168.1.6 OEMether IP netmask: 255.255.0.0Device XSC1BD19866, IP 192.168.1.6, Port 981 Calling EdbgInitDHCP-OEMKitlInit Host connectedHost IP: 192.168.1.8, port 3962 KeyIndex 0 = -1 KeyIndex 1 = -1 KeyIndex 2 = -1 KeyIndex 3 = -1 KeyIndex 4 = -1 KeyIndex 5 = -4194305 KeyIndex 6 = -4194305 KeyIndex 7 = -1 +KITLRegisterDfltClient, service:0 +KITLRegisterDfltClient, service:1 KITLGlobalState == 0x61 KITL Initialized Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0 ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service PPSH ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service PPSH ProcessAdminMsg: Receive Config message for service DBGMSG *******************Output message form "PB Debug window"****** 0 PID:0 TID:0 XSCDBG:Trace initialized: CFG:98ef1f24 Buffer: 98ef04a8, 14f0 0 PID:0 TID:0 Booting Windows CE version 4.20 for (ARM) Tag: direct3d mobile driver Tag: 82071
  - 3
    - SMSC9115 Kitl debug hi all, I am debugging kitl with SMSC9115 Lan chip. I re-wrote the low level functions. And the chip runs very well . But when I built the kernel with kitl support, the kernel stopped and the PB could not connect with my target board with kitl. Please help me to solve this problem. Thanks a lot! zhiqiang 3 7 ,2006 **************Output message from serial port ******************** OEMInitDebugSerial using UART1 Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 13 2003 at 22:44:13 ProcessorType=0411 Revision=7 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 96cb982c +OEMKitlInit Checking for LAN9115 Ethernet controller...++LAN9115 HardWare Setup! ChipID = 1150001!LAN9115 Ethernet controller initialized.VBridgeInit()...TX = [16384] bytes -- Rx = [16384] byteser [0xB8F09360] to [0xB8F0D360].uffer [0xB8F05340] to [0xB8F09340].Bridge:: NK add MAC: [78-2B-DE-9-4D-9A]ther IP Addr: 192.168.1.6 OEMether IP netmask: 255.255.0.0Device XSC1BD19866, IP 192.168.1.6, Port 981 Calling EdbgInitDHCP-OEMKitlInit Host connectedHost IP: 192.168.1.8, port 3962 KeyIndex 0 = -1 KeyIndex 1 = -1 KeyIndex 2 = -1 KeyIndex 3 = -1 KeyIndex 4 = -1 KeyIndex 5 = -4194305 KeyIndex 6 = -4194305 KeyIndex 7 = -1 +KITLRegisterDfltClient, service:0 +KITLRegisterDfltClient, service:1 KITLGlobalState == 0x61 KITL Initialized Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0 ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service PPSH ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service PPSH ProcessAdminMsg: Receive Config message for service DBGMSG *******************Output message form "PB Debug window"****** 0 PID:0 TID:0 XSCDBG:Trace initialized: CFG:98ef1f24 Buffer: 98ef04a8, 14f0 0 PID:0 TID:0 Booting Windows CE version 4.20 for (ARM) Tag: direct3d mobile driver Tag: 82070
  - 4
    - Can't download WinCE Update Is anyone else having problems when trying to download CE updates? I've been trying to get the Oct to Dec 2005 update for WinCE 4.2 for the past 2 days, but I keep receiving the message "The download you requested is unavailable". Here's the link... "http://www.microsoft.com/downloads/details.aspx?familyid=5e793909-5219-419b-9e67-9a959c2afc07&displaylang=en". Any info would be appreciated. Tag: direct3d mobile driver Tag: 82069
  - 5
    - Bulk-only USB Mass storage Function driver Hi everybody. Iam trying to add support for USB Mass Storage function to existing Windows Mobile 5 Smartphones/PDAs. I've successfully made a fuction driver based on BOT.CPP, registered it, and it works right, but - for reads only. When I try to issue a write, it looks like protocol sequence got messed up ("invalid CBW signature). Maybe someone encontered similar issues and know how to fix it? Here is relevant log part: UsbMsFn!ProcessScsiRead10: starting LBA/sector = 275904, transfer length = 8 (sectors) UsbMsFn!ProcessScsiRead10: IOCTL_DISK_READ( 8fb7c76a, 482312, 275904, 8 => (8d3e390, 4096) ) passed; 4096 bytes read UsbMsFn!STORE_ExecuteCommand: -- UsbMsFn!BOT_ExecuteCB: Command : passed UsbMsFn!BOT_ExecuteCB: -- UsbMsFn!BOT_HandleCBW: request length = 4096 UsbMsFn!BOT_SetupTx: ++ UsbMsFn!BOT_SetupTx: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBOPipeTransfer: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 1 UsbMsFn!BOT_TransferThread: 4096 bytes transferred UsbMsFn!ProcessBIPipeTransfer: ++ UsbMsFn!BOT_HandleCBW: ++ UsbMsFn!ChangeMscState: State change: data in transport -> status transport UsbMsFn!BOT_BuildCSW: ++ UsbMsFn!BOT_BuildCSW: -- UsbMsFn!BOT_SetupTx: ++ UsbMsFn!BOT_SetupTx: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBIPipeTransfer: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 1 UsbMsFn!BOT_TransferThread: 13 bytes transferred UsbMsFn!ProcessBIPipeTransfer: ++ UsbMsFn!BOT_HandleCBW: ++ UsbMsFn!ChangeMscState: State change: status transport -> idle UsbMsFn!ReceiveCBW: ++ UsbMsFn!BOT_SetupRx: ++ UsbMsFn!BOT_SetupRx: -- UsbMsFn!ChangeMscState: State change: idle -> command transport UsbMsFn!ReceiveCBW: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBIPipeTransfer: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 2 UsbMsFn!BOT_TransferThread: 31 bytes transferred UsbMsFn!ProcessBOPipeTransfer: ++ UsbMsFn!ProcessBOPipeTransfer: Received CBW UsbMsFn!BOT_HandleCBW: ++ UsbMsFn!BOT_HandleCBW: Length: 0x0200 Flags: 0x0 CBWLen: 0xa UsbMsFn!STORE_IsCommandSupported: ++ UsbMsFn!STORE_IsCommandSupported: command 0x2a UsbMsFn!STORE_IsCommandSupported: WRITE (10) UsbMsFn!STORE_IsCommandSupported: -- UsbMsFn!ChangeMscState: State change: command transport -> data out transport UsbMsFn!BOT_HandleCBW: request length = 512 UsbMsFn!BOT_SetupRx: ++ UsbMsFn!BOT_SetupRx: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBOPipeTransfer: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 2 UsbMsFn!BOT_TransferThread: 512 bytes transferred UsbMsFn!ProcessBOPipeTransfer: ++ UsbMsFn!ProcessBOPipeTransfer: Received data block UsbMsFn!BOT_HandleCBW: ++ UsbMsFn!BOT_ExecuteCB: ++ UsbMsFn!STORE_ExecuteCommand: ++ UsbMsFn!STORE_IsCommandSupported: ++ UsbMsFn!STORE_IsCommandSupported: command 0x2a UsbMsFn!STORE_IsCommandSupported: WRITE (10) UsbMsFn!STORE_IsCommandSupported: -- UsbMsFn!STORE_ExecuteCommand: command 0x2a UsbMsFn!STORE_ExecuteCommand: WRITE (10) UsbMsFn!ProcessScsiWrite10: starting LBA/sector = 247, transfer length = 1 (sectors) UsbMsFn!ProcessScsiWrite10: IOCTL_DISK_WRITE passed; 512 bytes written UsbMsFn!STORE_ExecuteCommand: -- UsbMsFn!BOT_ExecuteCB: Command : passed UsbMsFn!BOT_ExecuteCB: -- UsbMsFn!ChangeMscState: State change: data out transport -> status transport UsbMsFn!BOT_BuildCSW: ++ UsbMsFn!BOT_BuildCSW: -- UsbMsFn!BOT_SetupTx: ++ UsbMsFn!BOT_SetupTx: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBOPipeTransfer: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 1 UsbMsFn!BOT_TransferThread: 13 bytes transferred UsbMsFn!ProcessBIPipeTransfer: ++ UsbMsFn!BOT_HandleCBW: ++ UsbMsFn!ChangeMscState: State change: status transport -> idle UsbMsFn!ReceiveCBW: ++ UsbMsFn!BOT_SetupRx: ++ UsbMsFn!BOT_SetupRx: -- UsbMsFn!ChangeMscState: State change: idle -> command transport UsbMsFn!ReceiveCBW: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBIPipeTransfer: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 2 UsbMsFn!BOT_TransferThread: 31 bytes transferred UsbMsFn!ProcessBOPipeTransfer: ++ UsbMsFn!ProcessBOPipeTransfer: Received CBW UsbMsFn!BOT_HandleCBW: ++ ERROR: .\bot.cpp line 595: UsbMsFn!BOT_HandleCBW: Invalid CBW signature UsbMsFn!ChangeMscState: State change: command transport -> wait for reset UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBOPipeTransfer: -- UsbMsFn!BOT_DeviceNotify: ++ UsbMsFn!BOT_DeviceNotify: Process device msg 5 (5) UsbMsFn!BOT_HandleRequest: ++ UsbMsFn!BOT_HandleClearFeature: ++ UsbMsFn!ChangeMscState: State change: wait for reset -> status transport UsbMsFn!BOT_BuildCSW: ++ UsbMsFn!BOT_BuildCSW: -- UsbMsFn!BOT_SetupTx: ++ UsbMsFn!BOT_SetupTx: -- UsbMsFn!BOT_HandleRequest: -- UsbMsFn!BOT_DeviceNotify: -- BOT DefaultTransferComplete setting event UsbMsFn!BOT_TransferThread: Transfer 1 UsbMsFn!BOT_TransferThread: 13 bytes transferred UsbMsFn!ProcessBIPipeTransfer: ++ UsbMsFn!BOT_HandleCBW: ++ UsbMsFn!ChangeMscState: State change: status transport -> idle UsbMsFn!ReceiveCBW: ++ UsbMsFn!BOT_SetupRx: ++ BOT DefaultTransferComplete setting event UsbMsFn!BOT_SetupRx: -- UsbMsFn!ChangeMscState: State change: idle -> command transport UsbMsFn!ReceiveCBW: -- UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBIPipeTransfer: -- UsbMsFn!BOT_TransferThread: Transfer 2 UsbMsFn!BOT_TransferThread: 31 bytes transferred UsbMsFn!ProcessBOPipeTransfer: ++ UsbMsFn!ProcessBOPipeTransfer: Received CBW UsbMsFn!BOT_HandleCBW: ++ ERROR: .\bot.cpp line 595: UsbMsFn!BOT_HandleCBW: Invalid CBW signature UsbMsFn!ChangeMscState: State change: command transport -> wait for reset UsbMsFn!BOT_HandleCBW: -- UsbMsFn!ProcessBOPipeTransfer: -- UsbMsFn!BOT_DeviceNotify: ++ UsbMsFn!BOT_DeviceNotify: Process device msg 1 (1) UsbMsFn!BOT_DeviceNotify: Process UFN bus event 0 (0) UsbMsFn!STORE_Close: closing store Tag: direct3d mobile driver Tag: 82068
  - 6
    - Detecting ActiveSync (on the device) I have a simple "C" application running on my device that needs to detect if ActiveSync is connected and active. I know the info is in the docs somewhere but all I can find is info on detection of connections from the desktop side. I need the device side info. Any help?? Tag: direct3d mobile driver Tag: 82064
  - 7
    - Power Management & Alarm Hi, I am working on Power Management on WM5. It works by the most part OK but when I set up an alarm, the device wakes up just fine, but the alarm does not go off nor does any notification message about the scheduled alarm come up. Any idea how I can force it to go off? Thanks in advance, -PK Tag: direct3d mobile driver Tag: 82060
  - 8
    - LAN91C111 NDIS Windows CE 4.2 HELP!!! Hi, I am trying to make LAN91C111 NDIS driver from SMSC to work with a custom board. My Physical Address is 0x0c0000000 (ChipSelect 3) and i have a bootloader with KITL already working. The instructions from the SMSC driver tells to configure these registry keys: "InterruptNumber"=dword:E ;<= interrupt number, in hex "IoBaseAddress"=dword: ABA00300 ;<= IOBase address, in hex (SEE NOTE) "Transceiver"=dword:1E;<= Enter the correct sysintr value here Investigating the driver, there is a strange #if 0 that jumps the NdisMRegisterIoPortRange and gives a VirtualAlloc/VirtualCopy instead and uses PXA250_LAN91C111_ADDR value. When i try to use PXA250_LAN91C111_ADDR as 0x0c0000000 it goes until AdapterVerify and then gives me the following message: "LAN91C111: ERROR : Invalid LAN Chip and Driver Combination \r\n" i suspected that is a problem on the function NdisRawReadPortUshort that gets the Chip ID and the Revision. Reading the information from help, it is said that NdisRawReadPortUshort depends on NdisMRegisterIoPortRange, so i changed the #if 0 to #if 1 in LAN91C111_MiniportInitialize, but the driver always give me "LAN91C9111 : ERROR - Can't Register I/O Port Range!" when I try any of these values 0x0c0000000 and 0x0c0000300 I need this driver working till thursday so i really really need some advice. I'm using a platform without KITL to avoid conflits, and getting these messages over the serial port. My platform is a PXA255, modified from XSC1BD. With KITL, my ethernet goes OK, i can use VMINI as a normal device. Also, my register settings are: "InterruptNumber"=dword:8 "IoBaseAddress"=dword: 0x0c0000300 ;<= IOBase address, in hex (SEE NOTE) "Transceiver"=dword:20;<= Enter the correct sysintr value here Thanks in Advance, Marcelo Tag: direct3d mobile driver Tag: 82051
  - 9
    - Link .obj files Hi how can i link .o files to my driver? i know that i can specify the sources files for my driver by using SOURCES= \ can i use OBJECTS= \ in the sources file to specify the .o files to be linked to my driver? regards Mo Tag: direct3d mobile driver Tag: 82047
  - 10
    - icon scaling in windows ce 5.0 Has anyone noticed a change in icon operation in windows CE 5.0 ? I realized that my icons in the taskbar were not the small icon versions (16x16), so I created a dialog based application with different icons for large (32x32) and small. It looks like in CE 4.1, icon scaling wasn't supported, but since LoadIcon didn't support loading anything other than 32x32 bit icons, in general, there was no small icon in the class and I ended up with no icon for the taskbar. In CE 5.0, it looks like icons get scaled and you can endup with a system scaled version of the 32x32 bit icon in taskbar if the 16x16 version isn't loaded by the application class. Tag: direct3d mobile driver Tag: 82046
  - 11
    - Alternatives to TFAT? Hello, I wonder what alternatives exist to TFAT that is possible to use on external storage cards. I have found a system called "reliance". Are there other alternatives? Tag: direct3d mobile driver Tag: 82044
  - 12
    - No IST in an NDIS Miniport? Hello All, I have just inherited a CE NDIS driver and am trying to debug a problem where, after several quick power-cycles, the driver comes up in a state where it receives no interrupts. As such I am trying to learn about the WinCE interrupt model. Everything I've read so far refers to an ISR/IST model where an event is created at initialization time and linked to a system interrupt such that all interrupts result in activation of a waiting thread. I've also read that InterruptInitialize and IniterruptDone are essential calls in this process. I see none of that in this driver. The interrupt handler seems to be a function that was registered with NDIS via the NdisMRegisterMiniport call. So my question is, does the ISR/IST model not apply to NDIS miniports, i.e., is it handled invisibly by NDIS? For example, should there be a call to InterruptDone anywhere in an NDIS miniport? Also, I have been dumping portions of the interrupt object during startup (there's a lot to dump!) but so far have been unable to detect any difference between normal start-ups where interrupts work fine, and those where the ISR is never called. Does anyone have any suggestions on how to debug this sort of thing. Thanks. (I have not tried putting a scope on the interrupt line to verify that it is being generated. This device is not m company's; it's all self-contained and might be difficult to get at. For the moment I am assuming that the h/w is not the problem.) Tag: direct3d mobile driver Tag: 82035
  - 13
    - Credentials do not survive reboot Hi All, We use CE0 for our industrial controller, and we are currently migrating from CE4.2 to CE5.0. We have the problem that we can't save the username/password/domain settings. We use NTLM and it is configured to store the credentials in the registry. When I enter username/domain/password I see that a new credential is added to the registry and everything works just fine, but after a reboot the credential it is not recognised anymore. I checked if the credential keys in the registry are the same before and after the reboot, and they were. The only difference in the registry before and after reboot was the key 'HKEY_LOCAL_MACHINE\Comm\Security\Crypto\Seed'. I changed this key to the value of before the reboot, but it did not make any difference. Unfortunately I don't have access to the full source code, so I am not able to look at the source code of the credential manager. Does anyboby have an idea of why the credentials do not survive a reboot? Thanks in advance, Tim Brugman. Tag: direct3d mobile driver Tag: 82019
  - 14
    - Display driver--why is the word fat? Hi, When I powerd on my device, the word showd on LCD screen is fatter than normal. What is the possible mistake I took in display driver or other setting?? Thanks in advance! Tag: direct3d mobile driver Tag: 82016
  - 15
    - BSP_ARGS I would like to pass MAC address from bootloader to kernel. It is working OK with KITL and vmini driver. But with ndis driver MAC address is not passed. regards Tag: direct3d mobile driver Tag: 82013
  - 16
    - USB Mass storage driver problem Hello, I want to ask if a problem with USB mass storage driver in Win CE 5.0 had been solved. I red all messages posted in this newsgroup but I did not find any complex solution. We still have problem with some USB keys on PXA270 platform. Thanks. Tucniak Tag: direct3d mobile driver Tag: 82012
  - 17
    - Installation Error in PB 5.0 I am currently getting an error when installing PB 5.0. The install brings up the dialog: "Unable to initialize the catalog." when installing and after the install is complete the same dialog pops up when PB is run. I have tried full reinstallation and the same dialog pops up again. have tried the suggestions listed on: http://www.tech-archive.net/Archive/WindowsCE/microsoft.public.windowsce.platbuilder/2004-08/0255.html but cleandb.bat returns this: ************************************************** Using PBCEC and PBCommon to find the default catalog location. PBCEC = "C:\Program Files\Windows CE Platform Builder\5.00\CEPB\BIN\pbcec.exe" DESTDB = "C:\WINCE500\public\COMMON\oak\Catalog\Database\pbdb.mdb" SOURCEDB = "C:\WINCE500\PUBLIC\COMMON\OAK\CATALOG\DATABASE\base_pbdb.mdb" CECDIR = "C:\WINCE500\PUBLIC\COMMON\OAK\CATALOG\DATABASE\..\cec" Copying template "C:\WINCE500\PUBLIC\COMMON\OAK\CATALOG\DATABASE\base_pbdb.mdb" to new database location "C:\WINCE500\public\COMMON\oak\Catalog\Database\pbdb.mdb"... 1 file(s) copied. Importing CEC files from "C:\WINCE500\PUBLIC\COMMON\OAK\CATALOG\DATABASE\..\cec" into "C:\WINCE500\public\COMMON\oak\Catalog\Database\pbdb.mdb": Using database 'C:\WINCE500\public\COMMON\oak\Catalog\Database\pbdb.mdb' Could not load catalog database 'C:\WINCE500\public\COMMON\oak\Catalog\Database\pbdb.mdb'. ******* Import failed! Check the CEC file syntax and parameters. *************************************************************** Would anyone know why i cant seem to get the catalog to install? Thank You Peter Tag: direct3d mobile driver Tag: 82008
  - 18
    - Hour glass Hello All, I'm facing a strange problem with the hour glass in my application written in EVC 4.2. I used LoadCursor to load the wait cursor in my application and used SetCursor to show the hour glass. What is happening now is when i use the mouse, the cursor is changing into hour glass as the behaviour expected on the wait but when i use the touchscreen then the two hour galsses are coming, one is in the middle and one is for cursor(arrow is changing to hour glass cursor). The application is a dialog based application. I didnt get why the two hour glasses are coming when i tap the stylus on the touch screen but this is not the case when i use the mouse instead of stylus. Sometimes even when i'm browsing the folders using touch pad also i saw this behavior coming two cursors. My device is a windows CE based MIPSII processor, it contains mouse, keyboard and strylus facility. Where is going wrong? Any help on this is appreciated.... -- Software Engineer Tag: direct3d mobile driver Tag: 82006
  - 19
    - build fails when workspace directory is on another drive than your BSP Hi, My workspace is on drive D. My BSP (%_TARGETPLATROOT%) is on drive C. Result: ** failure ** Looks like the build system cannot deal with this sitation and fails when moving files. I guess it assumes %_flatreleasedir% and %_targetplatroot% reside on the same drive. Look at this beautiful snippet from the build.log : BUILD: [01:0000000099:INFO ] failed moving temp file 'D:\PBWorkSpaces\EDP\RelDir\MobulaCE50_ARMV4I_Release\bin953.tmp' to 'C:\WINCE 500\platform\MobulaCE50\target\ARMV4I\retail\EBOOT.bin': 17 BUILD: [01:0000000100:INFO ] Fatal error hit, exiting... I guess I move everything back on one drive again. Sigh. Do any of you guys have troubles with this ? (NOTE: 5.0 build environment) -- Ronald Tag: direct3d mobile driver Tag: 82004
  - 20
    - ChangeDisplaySettingsEx Hello all, I call ChangeDisplaySettingsEx(NULL,NULL,NULL,CDS_RESET,NULL) in my APP, and it return DISP_CHANGE_BADMODE. How can I modify my BSP that it can return DISP_CHANGE_SUCCESSFUL? Tag: direct3d mobile driver Tag: 82002
  - 21
    - Built-in or not built-in, that is the question CE 4.2 on ARM PXA 255 based device. I have a platform that has the IDE drive feature (and all the others required for a file system on the hard drive) included. This happens to be in the "built-in" category (looking at the registry shows the driver under built-in). When I boot the OS on a clean device for the first time with the hard drive installed, it creates the registry etc. (not on the HD, on a NAND flash), and the unit works fine. If I then remove the hard drive, the unit will fail to boot. If I put the drive back in, it works again. Why would removing the HD cause the device to fail? Has this something to do with what the device expects to find on the PCI bus? I'm thinking that on the first boot a bus enumeration happens but subsequent boots don't enumerate the actual devices. Subsequent boots assume the first enumeration worked and all the drivers are loaded regardless of whether or not the hardware is really there. Is this what happens? And, is this why the device is in the "built-in" section of the registry? Thanks. Ten. Tag: direct3d mobile driver Tag: 82000
  - 22
    - Ref: "Building Powerful Platforms with Windows CE" Book Hi, I am in urgent need of the book. Does anybody have an ebook? Or from where can I buy the ebook version of the same? Amazon will take at least 3-4 days to ship... I'm in India. And I need it urgently. Any help / pointers would be appreciated. -- Cheers, Gaurav ------------------ Spoken Words Fly Away, Written Words Last Forever ------------------ Tag: direct3d mobile driver Tag: 81993
  - 23
    - USB DiskOnKey need help Hi, I use Geode cpu with 32 MB ram and 32 MB flash on bard. I have application that need to read data from USB diskonkey device, this application is the first to run automaticaly after image loaded ended. The problem is: the application can't find the USB device - shuld be Hard Disk. It is also not exists when I use explorer to browse. There is no problem if I take the USB device out then put it in back. The problem in iamge made on Platformbuilder 4.2 and 5.0. David. Tag: direct3d mobile driver Tag: 81992
  - 24
    - Power management: what is allowed in callbacks? I am developing a driver for a measurement device which has multiple power states. The channel which changes power state is shared with the measurement channel. >From the PB documentation I gathered that the XXX_Power*** functions execute in a thread context. I think this means that measurement operations (running in a user thread) can be pre-empted by PowerDown. Since this function changes the power state, it will invalidate the current scheduled measurement. My question: how can I prevent this from happening? The obvious solution would be to block the XXX_PowerDown() call until the current measurement finishes. But this is not allowed since the PowerDown() function is not allowed to block or even call WaitForSingleObject! Another solution would be to set a global flag on PowerUp(), so user threads can check if there's been a suspend. Somehow that doesn't sound like a very elegant solution. Is there any way to wait or block in the PowerDown() call? Is it a good idea to want to do so? TIA Frans Tag: direct3d mobile driver Tag: 81985
  - 25
    - USB Error on boot with hive registry (OK without it) CE5, Via EPIA M1000 (x86) Board Using VIA BSP Have implemented hive registery (Harddisk). Prior to adding this to the system, boot worked OK and USB mouse worked. Now boot stops because of asserted USB error. Can continue boot but USB mouse not available. Asserted error occurs in cehcd.cpp, which had been called from hcddrv.cpp cehcd.cpp had just called chw.cpp which returned false, hence error. Have tried to tag output with code: (Any ideas? Thx) ==================================================================================================== Calling code: in C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\USB\HCD\USB20\USB2COM\hcddrv.cpp ============== extern "C" LPVOID HcdMdd_CreateHcdObject(LPVOID lpvUhcdPddObject, LPVOID lpvMemoryObject, LPCWSTR szRegKey, PUCHAR ioPortBase, DWORD dwSysIntr) { CHcd * pobUhcd = CreateHCDObject(lpvUhcdPddObject,(CPhysMem *)lpvMemoryObject,szRegKey,ioPortBase,dwSysIntr); if ( pobUhcd != NULL ) { if ( !pobUhcd->DeviceInitialize( )) { <<-- This calls The function CEhcd::DeviceInitialize() as below delete pobUhcd; pobUhcd = NULL; } } return pobUhcd; } ===================================================================================================== Function in which asserted error occurs: =============================== in C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\USB\HCD\USB20\EHCI\cehcd.cpp BOOL CEhcd::DeviceInitialize() // // Purpose: Set up the Host Controller hardware, associated data structures, // and threads so that schedule processing can begin. // // Parameters: pvUhcdPddObject - pointer to the PDD object for this driver // // pCPhysMem - pointer to class for managing physical memory // // szDriverRegistryKey - unused ? // // portBase - base address for USB registers // // dwSysIntr - interrupt identifier for USB interrupts // // Returns: TRUE - if initializes successfully and is ready to process // the schedule // FALSE - if setup fails // // Notes: This function is called by right after the constructor. // It is the starting point for all initialization. // // This needs to be implemented for HCDI // ****************************************************************** { DEBUGMSG(ZONE_INIT,(TEXT("+CEhcd::Initialize. Entry\r\n"))); <<<--Displayed as [[1]] below in Output // All Initialize routines must be called, so we can't write // if ( !CDevice::Initialize() || !CPipe::Initialize() etc ) // due to short circuit eval. { m_pMem ->ReInit(); BOOL fCDeviceInitOK = CDeviceGlobal::Initialize(this); <<-- Called function displays output [[2]] which is OK BOOL fCHWInitOK = CHW::Initialize( ); << This fails See code chw.cpp below, in particular [[3]] if ( !fCDeviceInitOK || !fCHWInitOK ) { DEBUGMSG(ZONE_ERROR, (TEXT("-CEhcd::Initialize. Error - could not initialize device/pipe/hw classes\n"))); <<<--- See Ouput [[5]] below ASSERT(FALSE); <<------------------------------ [[6]See Output below. This is line 144 Causes break in boot up return FALSE; } } ==================================================================================================== Output: ======= 4294772963 PID:af750662 TID:af750632 0x8f7a4d10: +USBD:HcdAttach, hcd: 0x57570 4294772963 PID:af750662 TID:af750632 0x8f7a4d10: -CDevice::Initialize, success!<<<-- 4294773008 PID:af750662 TID:af750632 0x8f7a4d10: +CHW::Initialize <<<---[[1]] 4294773013 PID:af750662 TID:af750632 0x8f7a4d10: !!!Warning!!! Setting resume/suspend/reset bits of USBCMD 4294774153 PID:af750662 TID:af750632 0x8f7a4d10: -CEhcd::Initialize. Error - could not initialize device/pipe/hw classes <<<---[[2]] 4294774202 PID:af750662 TID:af750632 0x8f7a4d10: Unknown: DEBUGCHK failed in file E:\macallan\public\COMMON\oak\drivers\usb\hcd\usb20\ehci\.\CEhcd.cpp at line 144 <<<---[[3]] 4294773278 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ehci1\BusPrefix) returned 2 4294773281 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: >>> Loading module ehci.dll at address 0x013C0000-0x013F3000 Loaded symbols for 'C:\VIA1\VIA1\RELDIR\VIACN_X86_DEBUG\EHCI.DLL' 4294773319 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: HCD driver DLL attach 4294773320 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: EHCD!HCD_Init 4294773321 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: EHCD: Read config from registry: Base Address: 0xDE001000, Length: 0x100, I/O Port: NO, SysIntr: 0x20, Interface Type: 5, Bus Number: 0 4294773321 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: EHCD: ioPhysicalBase 0xDE001000, IoSpace 0x0 4294773321 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: EHCD: ioPortBase 0x450000, portBase 0xDE001000 4294773322 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: EHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 5 4294773323 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: DMA buffer passed in from PDD 4294773323 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: CPhysMem Total Alloc Region PhysAddr = 0x09268000, VirtAddr = 0x00460000, size = 131072 4294773323 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: CPhysMem Special Alloc Region PhysAddr = 0x09268000, VirtAddr = 0x00460000, size = 4096 4294773324 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: CPhysMem HighPri Alloc Region PhysAddr = 0x09269000, VirtAddr = 0x00461000, size = 32768 4294773326 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: CPhysMem Normal Alloc Region PhysAddr = 0x09271000, VirtAddr = 0x00469000, size = 94208 4294773326 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: +CHW::CHW base=0x450000, intr=0x20 4294773369 PID:6f74e65a TID:f4d8ed6 0x8f4d8c44: !!!Warning!!! Setting resume/suspend/reset bits of USBCMD 4294773416 PID:6f74e65a TID:8f4e0fc2 0x8f4e3800: !!!Warning!!! Setting resume/suspend/reset bits of USBCMD 4294773479 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: +CEhcd::Initialize. Entry <-------------------------------------------------[[1]] Below < Call [[2]] Above> 4294773523 PID:6f74e65a TID:2f4e8fb6 0x8f4e8ce4: !!!Warning!!! Setting resume/suspend/reset bits of USBCMD 4294773568 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: +CDeviceGlobal::Initialize 4294773568 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: +USBD:HcdAttach, hcd: 0x57870 4294773568 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: -CDevice::Initialize, success! </Call [[2]] Above> 4294773691 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: +CHW::Initialize <<<---------------------------------------------------------[[3]] Below < Code [[4]] Below> 4294773975 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: !!!Warning!!! Setting resume/suspend/reset bits of USBCMD 4294774995 PID:6f74e65a TID:ef566da6 0x8f50a800: +OpenIFConfig(Comm\VMINI1\Parms\TCPIP Handle 0x629FAFC) 4294774995 PID:6f74e65a TID:ef566da6 0x8f50a800: Opened registry info for Comm\VMINI1\Parms\TCPIP 4294774995 PID:6f74e65a TID:ef566da6 0x8f50a800: -OpenIFConfig(Comm\VMINI1\Parms\TCPIP *Handle 0x629FAFC, BOOL Ret: 1) 4294774995 PID:6f74e65a TID:ef566da6 0x8f50a800: *CloseIFConfig(Handle 0xB30F0) 4294774995 PID:6f74e65a TID:ef566da6 0x8f50a800: IPAddAddrComplete: IF 168290 ntecount 1, SAC 0 </Code [[4]] Below> 4294775316 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: -CEhcd::Initialize. Error - could not initialize device/pipe/hw classes <<<--------[[5]] Above 4294775362 PID:6f74e65a TID:6f74e62a 0x8f7a4d10: Unknown: DEBUGCHK failed in file E:\macallan\public\COMMON\oak\drivers\usb\hcd\usb20\ehci\.\CEhcd.cpp at line 144 <<<----[[6]] Above ============================================================================================================== Called Code (Lowest level) ================ In C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\USB\HCD\USB20\EHCI\chw.cpp // ****************************************************************** BOOL CHW::Initialize( ) // Purpose: Reset and Configure the Host Controller with the schedule. // // Parameters: portBase - base address for host controller registers // // dwSysIntr - system interrupt number to use for USB // interrupts from host controller // // frameListPhysAddr - physical address of frame list index // maintained by CPipe class // // pvUhcdPddObject - PDD specific structure used during suspend/resume // // Returns: TRUE if initialization succeeded, else FALSE // // Notes: This function is only called from the CUhcd::Initialize routine. // // This function is static // ****************************************************************** { DEBUGMSG( ZONE_INIT, (TEXT("+CHW::Initialize\n")));<<<---[[2]]Output DEBUGCHK( m_frameCounterLowPart == 0 && m_frameCounterHighPart == 0 ); // set up the frame list area. if ( m_portBase == 0 || <<<---------This whole statement generates output [[4]] (Code) m_cPeriodicMgr.Init()==FALSE || m_cAsyncMgr.Init() == FALSE || m_cBusyPipeList.Init()==FALSE) { DEBUGMSG( ZONE_ERROR, (TEXT("-CHW::Initialize - zero Register Base or CeriodicMgr or CAsyncMgr fails\n"))); ASSERT(FALSE); return FALSE; } DEBUGMSG(ZONE_INIT && ZONE_REGISTERS, (TEXT("CHW::Initialize - signalling global reset\n"))); { USBCMD usbcmd=Read_USBCMD(); usbcmd.bit.HCReset=1; Write_USBCMD(usbcmd); for (DWORD dwCount=0;dwCount<50 && (Read_USBCMD().bit.HCReset!=0);dwCount++) Sleep( 20 ); usbcmd=Read_USBCMD(); if (usbcmd.bit.HCReset!=0) // If can not reset within 1 second, we assume this is bad device. <<<--- This fails return FALSE; -- David Jones Senior Lecturer School of Electrical & Computer Engineering RMIT University +61 3 99255318 Tag: direct3d mobile driver Tag: 81978

Hi,

I'm going to develop an application using direct3d mobile interface based on
windows ce 5.0.

I wonder PDAs based on WindowsCE 5.0 support applications using direct3d
mobile interface as default.

If there are PDAs based on WindowsCE 5.0 do not support direct3d mobile,
Can I distribute an application and direct3d mobile driver?

and, is direct3d mobile driver independent of CPUS such as x86 or
arm(xscale) ?

white

Top

Re: direct3d mobile driver by Steve

Steve
Thu Mar 09 08:47:33 CST 2006

Windows Mobile devices have D3DM, whether other devices have that or not is
up to the OEM. You cannot just ship a D3DM driver as the system needs the
D3DM core to utilize the driver. The driver is usually hardware specific and
not likely to work as-is on any other platform than the one it was designed
for.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Top