PXA255 vs. WinCE.NET 4.2

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - ANN: Windows CE .NET Chat coming up on 9/4 Title: Windows CE .NET Live Chat Description: Do you have tough technical questions regarding Windows CE .NET for which you're seeking answers? Do you want to tap into the deep knowledge of the talented Microsoft Embedded Devices Group members? If so, please join us for a live Windows CE .NET chat and bring on the questions! Windows CE .NET is the operating system that is powering the next generation of 32-bit, small-footprint and mobile devices. This chat will cover the tools and technologies used to develop devices using the Windows CE .NET operating system. September 4, 2003 10:00 - 11:00 A.M. Pacific time 1:00 - 2:00 P.M. Eastern time 18:00 - 19:00 GMT/BST To join this chat go to http://msdn.microsoft.com/chats Thanks, Michael Fosmire Community Program Manager, Windows Embedded This posting is provided AS IS with no warranties, and confers no rights. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40692
  - 2
    - MSVC 1.52 Hi all, I absolutely need the MSVC 1.52 compiler. I don't find where to buy it and I think that even with a MSDN subscription you won't any more get it because it is obsolete. Please help !!! thanks, Jean-Claude Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40690
  - 3
    - What does TLSKERN_NOFAULT debug message mean? I got the following message while debugging a problem on my system (4.1 on a PXA255). What does it mean? 4294798479 PID:408a2512 TID:20680332 0x80671000: Data Abort: Thread=80671000 Proc=818f1ab0 'gwes.exe' 4294798481 PID:408a2512 TID:20680332 0x80671000: AKY=00000111 PC=0003f4b0 RA=0003f4ac BVA=0a000014 FSR=00000007 4294798482 PID:408a2512 TID:20680332 0x80671000: TLSKERN_NOFAULT set... bypassing kernel debugger. 4294798484 PID:408a2512 TID:20680332 0x80671000: Calling exception handler @0015cd58(0015d944) Frame=1204f170 4294798486 PID:408a2512 TID:20680332 0x80671000: exception dispostion = 4 Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40689
  - 4
    - problems with a cf compact framework managed code application Hi, I have a WinCE4.2 PXA25x Platform with Compact FrameWork 1.0 included. When i start a Managed Code Programm, PB shows a Unhandled exception in COREDLL.DLL (0xC0000005 Access Violation). has anyone a idea ? A Registry entry from my Device: HKEY_LOCAL_MACHINE/SOFTWARE/Apps/Microsoft .NET Compact Framework/CabFile = netcf.all.wce4.armv4t.cab Is armv4t right, i have a armv4i BSP. VS.NET 2003 also trys to install netcf.all.wce4.armv4t.cab I have no Active Sync Connection, i connect with the SDAuthenthication Utility. How can i select the right CPU Type ? VS.NET | Tools | Select Windows CE Device CPU needs Active Sync Best Regards alfred Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40687
  - 5
    - temporary Files of PB4.2 Dear MS programmers Today I looked into my temporary files folder, it was shocking!!! I saw over 400000 Files using more than 1.6GB of my disk space. After some investigation I noticed that PB4.2 (and surely 4.1 too) produces two folders named libxxxx.tmp for every clean rebuild. And this is something I do very frequently. These two folders consist of 1700 files using over 6MB. Didn't you know that it's good programming practice to delete temporary files after usage? My wish for the next release: ************************************** Please delete your temporary files after usage. ************************************** ;-) TIA -- Michael Reim reim AT helmut-fischer DOT de Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40685
  - 6
    - BSP support for Intel Strong arm SA1110 hi all , A help needed is that our company is looking for going for development on WINCE.net 4.2 ,but i would like to know that in the BSP of the wince.net4.2 does support Intel strong arm SA1110 or not??? cause accornig to the data which i have gone thru the microsoft site there it has been said that it does not support Intel strong arm SA1110. So i would like to know does wince.net 4.2 support BSP for Intel strong SA1110. Thanks Shital Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40682
  - 7
    - Wireless problem. Hi All, I use the PB4.2 to configure the wireless lan. The cisco 350 can receive the excellent signal. Once click the "connect button" the connection disconnected. The same pcmcia.dll and pcx500.dll works fine in PB4.1. Is there a bug on PB4.2? Thanks. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40677
  - 8
    - Min. size of a WinCE Rom-image(nk.bin) supported display ??? Hi, all. I know that the size of a Tiny-kenel is about 0.8MB. But, I'm wandering a MIN. size of a wince rom-image supported display. ( only tiny-kernel + graphic ) I'm using a Platform builder 4.1 and a x86 emulator BSP. ASAP. Regards - Nam-Ho, Ahn Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40674
  - 9
    - where can i find more technical materials for windows automotive in english? Hi all, except the msdn,where can i find more technical materials for windows automotive in english?can anyone tell me ? thanks in advance. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40673
  - 10
    - Where does this Debugbreak() int imagelist.cpp come from? Hi everyone, My MFC program stops at the following debugbreak when I start it: 4294813649 PID:a1ef5b5a TID:e1e68756 0x81e4b000: Unknown: DEBUGCHK failed in file d:\jameson\private\winceos\coreos\gwe\controls\imgctl\.\imagelist.cpp at line 905 and the code jumps to kfuncs.h, line 102 where it calls "debugbreak();" #elif defined(x86) _inline void DebugBreak() { __asm int 3 } I checked my pc and I don't have any imagelist file, but I have a imgctl lib file. If I press F5, the application starts as is nothing has happened. But I can't do the same with a release build, the application doesn't start. This Debugbreak comes after the CChildView::OnCreate() returns 0 and before CMyApp::InitInstance { ................ pFrame->ShowWindow(m_nCmdShow); pFrame->UpdateWindow(); } lines are executed. I can't go with F11 until I find the debugbreak cal because at some stage the CEPC restarts itself and the PB loses connection. The same restart occurs when I want to debug my code using eVC and the emulator. I have 2 threads How can I solve this? Please help me. Selin Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40672
  - 11
    - migrating display driver from WinCE 2.12 to CE.NET 4.1 Hello, I want to migrate the display driver for standard VGA provided in WinCE 2.12 to WinCE .NET 4.1 I have compiled the dource code for Drivers under CE.NET and built the driver DLL. then I wrote the following entries in the platform.reg [HKEY_LOCAL_MACHINE\System\GDI\Driver] "Display"="ddi_vga8.dll" and also included the ddi_vga8.dll in the image. When I boot this image, the display remains blank. The image is working properly. It also writes the hive-based registry on the disk, but the display remains blank. How to solve this problem? Please help me. Thnaks BNP Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40671
  - 12
    - RNDIS Question - USBConnect4.TXT [0/1] Hi everyone, I'm in the process of porting across the netchip 2890 usb RNDIS driver to my Hitachi 64404 hardware. I'm at the point where the endpoint 0 setup appears to be working. I've installed the rndis driver and a SEND_ENCAPSULATED_COMMAND message is sent to the device, at which point nothing else happens. No further packets are received and nothing else seems to happen. I've got no other hardware to test this on, so I'm not sure what else is supposed to happen. Does anyone know what I should be sending in response or what ishould be waiting for at this point? I've attached some debug output from my serial port to indicate what's going on. Any suggestions on where to go from here are appreciated. Thanks, Glenn. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40666
  - 13
    - Where to find ethernet NDIS driver sample code Hi, Where to find NE2000 ethernet NDIS driver sample code and registry. Regards -Weijie Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40663
  - 14
    - problems creating the keyboard device layout I am following the MSDN's instructions for "Creating the Keyboard Device Layout", and am having problems as follows: 1. After running the Kbdgen.exe tool, two and only two files were created: WINCE420\PUBLIC\TestPlat\TestPlat.log, and WINCE420\PUBLIC\TestPlat\TESTPLAT_SetEnv.bat Step 5 of the instructions state "From the files that the kbdgen.exe tool generated, add the file ending in DL to the DeviceLayout directory." Neither of the two files created by Kbdgen.exe have DL anywhere in the file names or in the contents of the files. When i ran the Kbdgen.exe tool, i gave the arguments of the 8042 dll and input local 00000409. What and how many files (and where) SHOULD have been created by Kbdgen.exe, and what do i need to change to make that happen? 2. Step 3 refers to the makefile.def file in the directory WINCE420 \Public\common\oak\drivers\keybd\devicelayouts\ps2_at\00000 409. Since the file in that directory is named makefile (without a .def extension), can i correctly assume that what the documentation is refering to is makefile without the .def extension? Thanks in advance! MJ Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40661
  - 15
    - EnterCriticalSection DEBUGCHK in 4.2 I have been porting some proprietary code from Windows CE 3.0 to CE .Net 4.2 and occasionally hit a DEBUGCHK in EnterCriticalSection. Call stack is:- COREDLL!DebugBreak() line 102 cscode.c COREDLL!EnterCriticalSection() MYCODE!MyClass::MyMethod() DEBUGCHK call appears to be:- DEBUGCHK(!(DWORD)hTh & 1)) Where hTh appears to be a thread handle. What is the significance of the LSBit here and how( if at all ) could my code be effecting this Thanks in advance Rimmer Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40658
  - 16
    - FMD NOR Flash driver error message Hi , I am implementing FMD layer for a NOR Flash , I am doing the following : - I am using 2 MB of the flash only for the File System ( 0xBF500000-0xBF6FFFFF ) - Block size in this area of the flash is 64K , ( 32 Blocks in the 2 MB area ) -Every block contains 120 sectors , -Total number of sectors = 120*32= 3840 ,, and it is multiple of 256 ( 3840=256*15 ) . I get the following message in the debug window after the driver loads : //-------------------------------------------------------------------------------- FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 --------------------------------------------------------------------------------// What is the explination of this message ? Full log is : //-------------------------------------------------------------------------------- Loaded symbols for 'D:\WINCE420\PUBLIC\RG\RELDIR\88E6318_MIPSIV_FPDEBUG\FLASHDRV.DLL' 4294767733 PID:41fe6372 TID:41feaf42 0x81fe6000: INFO: FMD_Init: Flash Address=0xbf500000 Length=0x200000. Loaded symbols for 'D:\WINCE420\PUBLIC\RG\RELDIR\88E6318_MIPSIV_FPDEBUG\MSPART.DLL' Loaded symbols for 'D:\WINCE420\PUBLIC\RG\RELDIR\88E6318_MIPSIV_FPDEBUG\RELFSD.DLL' 4294767742 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:BuildupMappingInfo() - Enter. 4294767803 PID:41fe6372 TID:41feaf42 0x81fe6000: >>> Loading module mspart.dll at address 0x03E70000-0x03E7B000 (RW data at 0x01FEF000-0x01FEF494) 4294767804 PID:41fe6372 TID:41feaf42 0x81fe6000: Loading partition driver mspart.dll hModule=81FAB398 4294767804 PID:41fe6372 TID:41feaf42 0x81fe6000: Driver mspart.dll loaded 4294767804 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294767805 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 4294767805 PID:41fe6372 TID:41feaf42 0x81fe6000: Opened the store hStore=000B3F00 4294767805 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294767806 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 4294767806 PID:41fe6372 TID:41feaf42 0x81fe6000: NumSec=3600 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 .... .... .... .... .... --------------------------------------------------------------------------------// Thanks in advance -- Maen Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40654
  - 17
    - GWES DEBUG MESSAGES My system: PXA250, 32 MB FLASH, 32 MB RAM, PB4.2. I want to see the debug/retail messages from the modules GWES and NK. My kitl implementation doesn't work, so I use other way to activate the debug messages. 1. In my desktop PC, I launch regedit program. 2. I add a new key called [HKEY_CURRENT_USER\Pegasus\Zones]. 3. I add two dword values: - NK Kernel: REG_DWORD: 0x0000ffff. - GWE Server: REG_DWORD: 0x0000ffff. 4. I launch PB4.2. 5. I make a rebuild of a debug image. 6. I load the OS image in my board. 7. I reset the board. But I only see the messages of RETAILMSG and DEBUGMSG ( 1,..... For instance, If in the kernel there are a message like this: DEBUGMSG(ZONE_MEMORY, (TEXT("AllocHandle: pci=%8.8lx pvObj=%8.8lx pprc=%8.8lx\r\n"),pci, pvObj, pprc)); I never can't see it. But if the message is like this: DEBUGMSG (1, (L"SC_CloseAllHandles: CloseHandle(0x%8.8lx) Failed on Process exit, zapping the handle\r\n", phd->hValue)); I can see it. So the process of adding a key to the desktop registry to see debug messages is not working. Any ideas? What is the file where is stored the information about the debug zones of GWES? In GWES.EXE or in other file? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40652
  - 18
    - How to enable ethernet When the KITL is disabled Hi, when enabling KITL my ethernet can work normally. But when disabling KITL my ethernet can not work. My ethernet driver is NE2000-compatible which is provided by Microsoft. How to enable ethernet when KITL is disabled? Regards -Weijie Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40650
  - 19
    - Driver - Application communication hi , How can I register a callback in application which is to be called from a driver (for eg: serial driver) ? Please help me... regards Ajith Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40644
  - 20
    - multiXIP..Binfs hi, i m trying for MultiXip for .net4.2 and xcale 250 platform.. i have included : the following in config.bib DRIVERS 81E41000 001BF000 RAMIMAGE and included the following in paltform.bib: battdrvr.dll $(_FLATRELEASEDIR)\battdrvr.dll DRIVERS SH but i get the following error: Error: Unknown memory type found 'DRIVERS' Error: failed setting line makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec). makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec). could anyone tell me the solution for the same thnx atul Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40642
  - 21
    - How to Control the Volume of Sound Files in WinCE .? Hi , How to Control the Volume of Sound Files in WinCE .? I have written an audio driver for WinCE to use instead of wavedev.dll. I am getting the GetVolume and Setvolume indication when changing the volume control of Media player. I want to know who is increasing the volume, waveapi.dll or wavedev.dll ?. When increasing the volume , does the data getting at the wavedev.dll is volume increased one ? Thanx in advance Ajith Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40640
  - 22
    - HOw to enable ethernet without KITO Hi When I new a platform with KITO, I can use PIE to access Internet, but when I new a platform without Kito, I can not use PIE to access Internet. I use NE2000-compatible driver, which is provided by Microsoft. How to resolve the problem. Regards -Weijie zhu Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40638
  - 23
    - DiskOnChip driver does not work in WinCE 4.2 I run to a problem. I use new Platform Builder for WinCE 4.2 and I use driver for DiskOnChip (M-Systems) supplyed with Platform Builder 4.2. And nothing work! But when I use Platform Builder for WinCE 4.1 with driver from M-Systems- all OK. What is may be wrong in new Platform Builder 4.2? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40637
  - 24
    - PMDDI.dll Hi all. I migrate 4.1 to 4.2 using assabet board. I have problem that is about pmddi.dll. In 4.1, lcd driver is made up with linking library. But in 4.2, I cannot find pmddi.dll. What should I do in this situation. Please help me, if anybody that have same experience is here Best Regards. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40636
  - 25
    - How to fixed & add interrupt value in Biosloader ? I've to fixe some device interrupt value before loading nk.bin. My platform is X86 architecture. should I modify Biosloader's source code to get what I want ? Could someguys tell me some hints to fixe that above that. Thanks a lot. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40635
- Next
  - 1
    - test test Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40633
  - 2
    - problems manually setting DNS servers in windows CE .NET Hi there, I am using platform builder 4.2, building debug images and transferring them over ethernet to a CEPC. My platform is based on the Enterprise Web Pad. When I attempt to manually set DNS servers on my CE machine, the network connections window locks up, and the following debug error message is displayed on the development workstation in a continuous loop every second or so: AUTORAS:: Reg does not contain RasEntry value!!! Any ideas? Am I missing some registry settings or something? Thanks, David Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40628
  - 3
    - G.729 codec how can I find a plugable G.729 codec for CE.Net 4.2 ? can any body help me? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40619
  - 4
    - [HKEY_LOCAL_MACHINE\Init\BootVars] I want to use RAM based registry and registry backup. However, when calling the RegFlushKey, it creates a file on the persistent storage. Is it partially enabled the hive based registry? Is the Platform Builder treat it as hive based registry when it saw the [HKEY_LOCAL_MACHINE\Init\BootVars] registry entry? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40613
  - 5
    - Help! I have a very simple question about generation of unicodes in CE .NET 4.2 According to the MSDN documentation for CE .NET 4.2, the KeybdDriverVKeyToUnicode function is responsible for generating the correct Unicode characters. I located this function in WINCE420\PUBLIC\COMMON\OAK\DRIVERS\KEYBD\LAYMGR\laymgr.cpp. This function is the same one that is located in a different file in the PLATFORM tree of CE 3.0. My problem is that whatever changes I make to laymgr.cpp to change the unicode character has no effect on the target, even if I clean and rebuild. This is the case even if i hard code the character as a "Q" so that ALL keystrokes will register that character: *pcCharacters = 0x0051; I have done a text search on the entire WINCE420 directory tree, and laymgr.cpp is the only source file with the KeybdDriverVKeyToUnicode function. What must i do to allow my changes to have an effect on the target machine? Thank you very much Martin Johnson Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40607
  - 6
    - Platform Builder does not start! Things got really messy now... I was working on cloning BSP in my PB4.1 and I just went to File/Manage Catalog Features to remove my new BSP from Catalog. When I clocked "remove" button on this window PB crashed. Now I am not able to start PB at all. It fails with a message "Unable to initialize Catalog" followed by the "Runtime error" window and cepb.exe crashes. What can I do to avoid reinstallation? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40600
  - 7
    - Bug in BINFS+FAT+NANDFLASH I think we have identified a big fatal problem with the BINFS+FAT+NandFlash. According to my observation now, it is an aparent bug in MS's code, but due to lack of relate source code, I can not figure out where goes wrong. To simply put the problem: when writing data files on FAT partition, the BINFS partion will sometimes (actually, with very high frequency) get corrupted. Here is the full version of the story: 1). 2 partitions are created on NandFlash in bootloader, BINFS + FAT. 2). block 0x00 - block 0x0B are reserved for bootloader therefore out of file system, file system(MBR) starts on NandFlash block 0x0C. Followed by BINFS and FAT partition. 3). MBR, BINFS are marked with READ_ONLY. While FAT partition starts on a block boundary, not marked with READ_ONLY. 4). Windows CE works very well when the boot up, with BINFS+MultiXIP. 5). FAT on NandFlash works fine too at first sight. A "ResidentFlash" folder appears in file explorer. Download a Mp3 songs to this folder, play it without problem. 6). No problem appears if you don't do anything else, power on/off the board, everything works just fine. 7). Problem happens when we run a test application. 8). What the test app does is very simple, to create a file on under the "ResidentFlash" folder and write some random data to the file. Then repeatedly create with the same file name and overwrite it. 9). The symptom is after a few minutes, the test app will erase NandFlash from right start the file system, block 0x0C. If running enough long time, the whole file system (MBR, BINFS) on NandFlash will be erased. To dig out what happened exactly, I tried to print out a message in the FMD_EraseBlock function to see which block is gonna be erased. Here are what I found: 1). We are testing on a 32M NandFlash, so totall have 2000 (0x7D0) blocks. 2). FAT partition takes control of 0x550 - 0x7CF. 3). When the test app first time writes a file, file system will try to erase some blocks according to the file size, for example, from 0x551 - 0x650. 4). Second time to overwrite the same file, will cause the following blocks to be erased, for example, from 0x651 - 0x751. 5). Problems may possible happen when the searching for a block to erase wrap back to the boundary 0x7CF. 6). The problem is not happening every time when wraping back from 0x7CF. In some times, 0x7CF is followed with 0x551, which is the correct case. But in some times, 0x7CF is followed by 0x0C, which is the MBR block, then 0x0C is followed by 0x551, or sometimes, 0x0D, ... Following is some patterns: 0x7CF, 0x551, 0x552 ... (correct case) 0x7CF, 0x0C, 0x551, ... 0x7CF, 0x0C, 0x0C, 0x551, ... 0x7CF, 0x0C, 0x0C, 0x0D, 0x551, ... 0x7CF, 0x0C, 0x0C, 0x0D, 0x0E, 0x551, ... If the application runs enough long time, it will erase the whole file system. I also tested with the Monolithic NK image condition. In this case, the bootloader only creates a FAT partion, the NK image is stored on reserved blocks, out side of the file system's control. In this case, it seems there is no problem when test application erasing wraps back from 0x7CF block. I hope I have illurstrate this problem very clearly. I have tried to break the OS when trying to erase block 0x0C, but due to lock of related source file, I have no idea, when the file system tries to erase the MBR block. Best regards. Rui Tang Centrality Communications Inc Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40584
  - 8
    - USB on wince.net 4.1 Hi Below is an extract from my platform.reg, this allows auto connection of our device to a host pc when the usb lead is plugged in. This works on wince 3.0, I try the same code in wince 4.1 and it doesn't work, the [HKEY_CURRENT_USER\Comm\RasBook\USBCradle] seems to be ignored. The key is available on the system and I can view it and its content using a registry editor. Any help would be appreciated Regards Tariq [HKEY_CURRENT_USER\ControlPanel\Comm] "AutoCnct"=dword:1 "Cnct"="USBCradle" ;;;; "Cnct"="InfraRedLink" ;; DEV USE ONLY - shipped builds should default to USB [HKEY_CURRENT_USER\Comm\RasBook\USBCradle] "Entry"=hex:\ 08,02,00,00,00,00,00,00,00,00,00,00,00,00,E6,AC,\ 02,00,00,00,10,2A,15,8C,F2,DF,01,10,00,00,00,00,\ F2,DF,00,00,00,00,00,00,00,00,00,00,4C,56,10,00,\ 78,F9,19,00,0A,00,00,00,BC,E6,06,10,C4,0F,0D,00,\ 18,AE,19,00,00,00,00,00,02,00,00,00,F2,DF,01,10,\ AE,01,00,00,F2,DF,01,10,18,AE,19,00,D4,E6,06,10,\ 14,D8,05,00,CA,8C,E6,AC,88,08,1A,00,60,08,1A,00,\ EC,E6,06,10,F8,58,F9,01,80,B9,FD,01,01,00,00,00,\ 00,00,00,00,07,00,00,00,60,08,1A,00,03,00,00,00,\ 8E,01,00,00,01,00,00,00,88,08,1A,00,03,00,00,00,\ 8E,01,00,00,01,00,00,00,01,00,00,00,24,E7,06,10,\ 14,D8,05,00,24,E7,06,10,00,00,00,00,30,DA,08,00,\ 01,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,\ 50,E7,06,10,05,00,00,00,B0,06,1A,00,B0,06,1A,00,\ 5C,E7,06,10,50,59,F9,01,28,E5,12,00,7E,8F,E6,AC,\ 01,00,00,00,6C,E7,06,10,A4,E4,07,00,28,E5,12,00,\ BC,69,F9,01,80,B9,FD,01,00,05,1A,00,90,04,0D,00,\ 3E,18,EE,0C,80,AB,19,00,00,00,00,00,F2,DF,01,10,\ 0A,00,00,00,64,37,A8,C0,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,\ 64,00,69,00,72,00,65,00,63,00,74,00,00,00,0D,00,\ 01,00,00,00,01,00,00,00,01,00,00,00,80,D7,0C,00,\ 01,00,55,00,53,00,42,00,20,00,43,00,61,00,62,00,\ 6C,00,65,00,3A,00,00,00,02,00,00,00,F2,DF,01,10,\ 00,00,00,00,00,00,00,00,10,A1,14,8C,00,00,00,00,\ 90,68,19,0A,90,68,19,0A,00,00,00,00,0A,00,00,00,\ 00,00,00,00,00,00,F6,01,00,00,00,00,81,00,00,00,\ 10,2A,15,8C,00,00,00,00,30,E8,06,10,70,03,07,80,\ 30,E8,06,10,1F,00,00,00,00,00,00,00,01,00,00,00,\ 01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,A8,05,1A,00,00,00,00,00,00,00,00,00,\ 01,00,00,00,28,E5,12,00,7E,8F,E6,AC,01,00,00,00,\ 78,E8,06,10,7C,8E,03,00,28,E5,12,00,00,00,00,00,\ 0A,00,00,00,04,15,03,80,F2,DF,01,10,91,00,00,00,\ 10,2A,15,8C,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,01,00,00,00,01,00,00,00,00,00,00,00,\ C4,E8,06,10,5C,03,0D,00,80,AB,19,00,89,01,00,00,\ 02,00,00,00,F2,DF,01,10,00,AB,19,00,02,00,00,00,\ 0A,00,00,00,80,AB,19,00,E4,E8,06,10,F0,E8,06,10,\ A8,DB,0C,00,00,AB,19,00,21,00,00,00,F2,DF,01,10,\ 00,00,00,00,03,00,00,00,05,00,00,00,84,0C,1A,00,\ 00,00,00,00,00,AB,19,00,B0,05,00,00,40,00,00,00,\ 00,00,00,00,00,10,00,00,24,E9,06,10,D0,7A,21,01,\ 18,08,18,00,02,00,00,00,08,00,00,00,06,00,00,00,\ FF,FF,FF,FF,89,00,0C,00,00,00,00,00,06,00,00,00,\ FF,FF,FF,FF,02,00,00,00,68,E0,18,00,07,00,00,00,\ 00,00,00,00,F2,DF,01,00,80,00,00,00,FF,FF,FF,FF,\ 00,00,00,00,6C,E9,06,10,8C,7D,F6,01,B4,7D,F6,01,\ CA,8C,E6,AC,B8,12,03,80,0C,00,00,00,10,A1,14,8C,\ 74,7A,DF,8C,01,00,00,00,00,00,00,00,94,E9,06,10,\ 98,2D,04,80,02,00,00,00,00,00,00,00,28,E5,12,00,\ 00,00,00,00,01,00,00,00,B4,32,F6,8C,A4,E4,07,00,\ 74,7A,DF,8C,38,26,E2,8C,81,00,00,00,00,E9,06,10,\ 00,00,00,10,00,00,00,00,30,A8,19,00,00,00,00,00,\ 50,27,15,8C,0A,00,00,00,00,00,00,00,00,00,00,00,\ 00,28,15,8C,01,00,00,00,04,12,03,80,00,00,00,00,\ 01,00,00,00,03,00,00,00,F2,DF,01,10,01,00,00,00,\ 80,D7,0C,00,01,00,00,00,01,00,00,00,01,00,00,00,\ 98,77,01,00,00,00,00,00,2C,EA,06,10 Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40579
  - 9
    - Ethernet driver for CS8900? Hello, I am interestiond, when will be available Ethernet driver for CS8900A for Windows CE .NET referenced in following document "http://www.microsoft.com/windows/embedded/docs/ce.net/driv ers.xls"? Best regards Ales. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40559
  - 10
    - DEBUGCHK error at the beginning of application initialization Hi all, I'm developing an MFC application. I create a new window in my main window with the following code: /*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* int CChildView::OnCreate(LPCREATESTRUCT lpCreateStruct) { m_pTerm = new CTermWnd(); m_pTerm->Create(NULL, NULL, WS_CHILD | WS_VISIBLE | WS_BORDER, CRect(CPoint(0, 0), CSize(200, 200)), this, ID_TERMSCREEN); return 0; } /*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* class CTermWnd : public CWnd { public: CTermWnd(); virtual ~CTermWnd(); protected: //{{AFX_MSG(CTermWnd) afx_msg void OnPaint(); afx_msg int OnCreate(LPCREATESTRUCT lpCreateStruct); afx_msg BOOL OnEraseBkgnd(CDC* pDC); //}}AFX_MSG DECLARE_MESSAGE_MAP() private: CWnd* m_pTerm; static CBrush ms_bkgndBrush; public: HWND m_hTermWnd; }; /*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* CBrush CTermWnd::ms_bkgndBrush; CTermWnd::CTermWnd() { strTermClass = AfxRegisterWndClass(NULL, NULL, (HBRUSH) ::GetStockObject(LTGRAY_BRUSH), NULL); } CTermWnd::~CTermWnd() { } BEGIN_MESSAGE_MAP(CTermWnd,CWnd ) //{{AFX_MSG_MAP(CTermWnd) ON_WM_PAINT() ON_WM_CREATE() ON_WM_ERASEBKGND() //}}AFX_MSG_MAP END_MESSAGE_MAP() //////////////////////////////////////////////////////////////////////////// / // CTermWnd message handlers void CTermWnd::OnPaint() { CPaintDC dc(this); // device context for painting // TODO: Add your message handler code here // Do not call CWnd::OnPaint() for painting messages } BOOL CTermWnd::OnEraseBkgnd(CDC* pDC) { CRect rc; GetClientRect(&rc); pDC->FillSolidRect(&rc, RGB(192,192,192)); return TRUE; // Erased } int CTermWnd::OnCreate(LPCREATESTRUCT lpCreateStruct) { /* Most of OnCreate code is useless since I can't pass the GCL_HBRBACKGROUND parameter to SetClassLong*/ CDC *pDC = this->GetWindowDC(); //ms_bkgndBrush.CreateSolidBrush(LTGRAY_BRUSH); ms_bkgndBrush.CreateSolidBrush(RGB(192, 192, 192)); DWORD style = ::GetClassLong(m_hWnd, GCL_STYLE); //::SetClassLong(m_hWnd, pDC->SetBkColor(RGB(192, 192, 192)), (LONG) (HBRUSH) ms_bkgndBrush); ::SetClassLong(m_hWnd, GCL_STYLE, (LONG) (HBRUSH) ms_bkgndBrush); DWORD errno = GetLastError(); UpdateWindow(); return 0; } /*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* I also used AfxRegisterWndClass to create the child window with the following code, but that , too, stopped at the debugbreak() function: int CChildView::OnCreate(LPCREATESTRUCT lpCreateStruct) { CString strTermClass; strTermClass = AfxRegisterWndClass(NULL, NULL, (HBRUSH) ::GetStockObject(LTGRAY_BRUSH), NULL); m_pTerm = new CWnd(); m_pTerm->Create(strTermClass, NULL, WS_CHILD | WS_VISIBLE | WS_BORDER, CRect(CPoint(0, 0), CSize(200, 200)), this, ID_TERMSCREEN); return 0; } /*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/*/* Whenever I start my application I get the following debug message: 4294813649 PID:a1ef5b5a TID:e1e68756 0x81e4b000: Unknown: DEBUGCHK failed in file d:\jameson\private\winceos\coreos\gwe\controls\imgctl\.\imagelist.cpp at line 905 and the code jumps to kfuncs.h, line 102 where it calls "debugbreak();" #elif defined(x86) _inline void DebugBreak() { __asm int 3 } I checked my pc and I don't have any imagelist file, but I have a imgctl lib file and checking that (as much as it's possible to check!) I somehow figured out that these lines are in the lib file, which might be related with my problem: "application passed invalid ILC_color flags to imagelist_create imagelist out of near memory imagelist can't create bitmap imagelist unable to initialize APPLICATION ERROR exited with Imagelist not destroyed" If I press F5 I can continue to debug and the application initializes as if nothing has happened. I don't get these messages when I open / close dialog windows in my application. I get it only at the initialization stage. Also I don't get any error messages while working with eVC on the standard SDK Emulator. Since I don't know why this error comes, I can't handle it with any kind of exception handling procedure. My aim is to create a window in the view area and to display the characters I receive from the serial com port in this window. Could you tell me what is wrong with my code? Thank you very much already. Selin Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40558
  - 11
    - my hard disk open very slow hello all friends. i use ce4.1,when my ce startup ,i open my hard disk,i find open it very slow.why? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40557
  - 12
    - Allocating fixed shared memory for ISR On WINCE 4.2 ARMV4I: I want to allocate a buffer in cached memory that can be shared by the ISR and the IST. I've looked at several options but they all seem to indicate they will only allocate memory that is uncached (and uncachabe?) AllocPhysMem, CreateStaticMapping, KLibAllocShareMem. Question: 1) Is it safe to simply remove the uncached mask from this address and use it so that it is in the cached region? 2) Is it safe to virtualalloc/virtcopy this uncached address but set the page with cached parameters? I've been doing this sort of thing on Windows Automotive (which has supported installable interrupts all along using this mechanism) for 6 years but would just allocate a piece of virtual memory and do a LockPages on it to get the physical address. This works fine but much more messing around that using a simple API like the ones mentioned above. Regards, Mark Moeller Qualnetics Corporation Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40555
  - 13
    - [HELP} USB mouse cursor OFFSET? Dear guru: I am developing WinCE.NET 4.1 for a CEPC (VT8606+VT82C686B+RTL8139) using VIA BSP. For the USB function I encounter a strange condition. The USB mouse and Keyboard work ok except the mouse cursor DO NOT match the focus point. When you surf the IE, the link with the cursor on didn't change color but the next 2 rows' link changed (take MSN.COM as an example). If you clicked, the changed link is retrieved not the link with the cursor on. But the PS/2 mouse works perfectly. What is the possible cause? How should I debug this discrepency? Any hint is great thankful. Best Regards Henry Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40553
  - 14
    - Running CE directly from RAM Hi, I am trying to download CE image through Serial Port to x86(80486 DX) board.I am not making use of "CEPC Method" provided by Microsoft.I have customized my BIOS to receive the CE OS image through serial port and load it at desired location. I could download the image onto Target platform(In real mode), but systems hangs up,when i am trying to run this image.Before making FAR JMP i am switching processor mode to Protected mode.What could be the problem? I have created the image using PB 2.12.How can i customize CE in PB so that it can be run directly from RAM? Is there any special care i need to take before compiling the OS image? Thanking you all in advance, Hemant Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40548
  - 15
    - Testing a serial driver using CEPC Hi , How can I test a serial port driver by using CEPC. When I tried the tux utility. I have entered tux -o -d pserial , in the Target->Advanced commands(CESH) of platform builder. Then the output window displayed as follows tux -o -d pserial Unknown command. pserial.dll ,tux.exe, kato.dll and tooltalk.dll are present in the RelDir\X86_Debug directory. how can I solve this problem ? thanx in advance ajith Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40546
  - 16
    - SPI_GETPLATFORMTYPE in 4.2 What is the most recommended naming convention for SPI_GETPLATFORMTYPE in OEMIoControl -> IOCTL_HAL_GET_DEVICE_INFO. For CE300 we went with "Jupiter" but for this release we are thinking of something more specific to our product. However, we do not want to make it difficult for the installation of third party apps. I have looked for guidelines for this without success. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40542
  - 17
    - binfs and eboot hi, could anyone tell me , if i need to incorporate BinFs file system, do i need to have eboot modified. if yes, how can i download, different(kernel,application etc images) images... i m using xscale 250 plus .net4.2 thanks atul Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40540
  - 18
    - Does x86 Emulator support Stylus? Hi, Could anyone advise me if the x86 emulator supports Stylus (touch panel calibration)? If yes, what should I do in order to enbale the "Stylus". Thank you. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40539
  - 19
    - Custom Device SDK Hi, Has anyone made any progress on getting .NET CF applications to cleanly deploy to custom Windows CE.NET-based devices? We have a nice 4.2-based device on which a given .NET CF application runs fine, but when you deploy this application to the device the first time, with the Windows CE platform selected, you get a pop up on the device saying that the application is not compatible with the device and do you want to continue with installation. If you say no, it's not deployed. If you say yes, everything continues from there and works fine. I *have* built and installed the SDK generated by Platform Builder for the device (and the eVC part of the SDK works just fine). Referencing the previous thread primarily between Chris and I, http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=%23f8A3MFBDHA.208%40TK2MSFTNGP10.phx.gbl&rnum=3&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DISO-8859-1%26q%3D.net%2Bcf%26meta%3Dgroup%253Dmicrosoft.public.windowsce.platbuilder.* has anyone from MS come up with an update to the SDK generator which will generate a dialog that will work? I guess I could fool around with the internals of the SDK, but I'd much rather just generate it and have it work. Paul T. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40526
  - 20
    - (NDIS) Network not reconnecting on a suspend/resume with protocol driver. Hi All, I am adding a third party 802.1x supplicant to my device (CE 4.1) and have little experience with NDIS. The supplicant is a NDIS protocol driver that will bind to a 802.11b radio NDIS miniport driver. Currently, when I resume from suspend I cannot re-establish communications. The first problem I noticed is that my radio driver does not get unloaded and reloaded like it does when I don't have the supplicant running. Enabling debug has shown that on resume NDIS tries to unbind all protocols from the miniport however it stops after doing the supplicant. It seems that an error occurs "ObjectCall: Failed (2); h=0" after the protocol driver calls NdisCompleteUnbindAdapter(). Would this type of error cause NDIS to fail unloading the radio driver? Is the problem likely to be in the protocol driver or somewhere else? I have attached debug code with and without the protocol driver. (search for $$$ to find relevent parts of the code. With the supplicant protocol driver. 4294921697 PID:208d3cbe TID:a0739ce2 Back from OEMPowerOff 4294921697 PID:208d3cbe TID:a0739ce2 Calling device manager power proc. 4294921697 PID:208d3cbe TID:a0739ce2 Calling GWES power proc. 4294921697 PID:752fa6 TID:a0739ce2 Returning to normally scheduled programming. 4294921697 PID:752fa6 TID:a0739ce2 Setting Event 008d0176, phd = 808d0174 4294921697 PID:752fa6 TID:a0739ce2 Setting Event 208d019a, phd = 808d0198 4294921697 PID:752fa6 TID:a0739ce2 Setting Event e0739e26, phd = 80739e24 4294921697 PID:752fa6 TID:a0739ce2 Returning from PowerOnSetEvents. 4294921703 PID:208d3cbe TID:a084b952 0x80852a90: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294921736 PID:208d3cbe TID:a084b952 0x80852a90: PCMCIA:PcmciaPowerOn: socket 1 powered up 4294921738 PID:208d3cbe TID:405ccf0e 0x80783664: NDIS:: PcmciaCallBack Event=CE_PM_SUSPEND hSock=0 4294921739 PID:208d3cbe TID:405ccf0e S24NIC: CallBackFn: 0000000C 4294921739 PID:208d3cbe TID:405ccf0e 0x80783664: NDIS:: PcmciaCallBack Event=CE_CARD_REMOVAL hSock=0 4294921740 PID:208d3cbe TID:405ccf0e S24NIC: CallBackFn: 00000005 4294921741 PID:208d3cbe TID:405ccf0e S24NIC: CE_CARD_REMOVAL 4294921741 PID:208d3cbe TID:405ccf0e S24NIC: @POWER DOWN = TRUE 4294921744 PID:208d3cbe TID:a0851662 0x80851400: PDCardSetSocket 1 bvd 4294921745 PID:208d3cbe TID:a0851662 0x80851400: PDCardSetSocket 1 cd rising 4294921746 PID:208d3cbe TID:a0851662 0x80851400: PDCardSetSocket 1 irq off 4294921752 PID:808f923e TID:a0739ce2 0x807888a8: FS: Got Power notif 0x00000001 4294921756 PID:208d3cbe TID:a063f002 0x80597a8c: +CHub(Root tier 0)::HandleDetach 4294921758 PID:208d3cbe TID:a063f002 0x80597a8c: CHub(Root tier 0)::HandleDetach - status change thread closed in 1 ms 4294921759 PID:208d3cbe TID:a063f002 0x80597a8c: +CHub(External tier 1)::HandleDetach 4294921769 PID:208d3cbe TID:a084b952 0x80852a90: PCMCIA:Leaving PcmciaPowerOn 4294921771 PID:208d3cbe TID:a084b952 0x80852a90: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294921772 PID:208d3cbe TID:a084b952 0x80852a90: PCMCIA:Leaving PcmciaPowerOn 4294921774 PID:208d3cbe TID:c075f242 0x807a40a8: NDIS:: PcmciaCallBack Event=CE_PM_SUSPEND hSock=1 4294921775 PID:208d3cbe TID:c075f242 S24NIC: CallBackFn: 0000000C 4294921775 PID:208d3cbe TID:c075f242 0x807a40a8: NDIS:: PcmciaCallBack Event=CE_CARD_REMOVAL hSock=1 4294921776 PID:208d3cbe TID:c075f242 S24NIC: CallBackFn: 00000005 4294921778 PID:208d3cbe TID:a063f002 0x80597a8c: CHub(External tier 1)::HandleDetach - status change thread closed in 18 ms 4294921777 PID:208d3cbe TID:c075f242 S24NIC: CE_CARD_REMOVAL 4294921782 PID:208d3cbe TID:c075f242 S24NIC: @POWER DOWN = TRUE 4294921789 PID:208d3cbe TID:c075f242 0x807a40a8: NDIS: +ndisRemovePCCardDevice $$$ tries to unbind 4294921790 PID:208d3cbe TID:c075f242 ==>ndisPnPRemoveDevice: Miniport 0004B838 4294921792 PID:208d3cbe TID:c075f242 ==>ndisCloseMiniportBindings, Miniport 0004B838 4294921795 PID:208d3cbe TID:c075f242 ==>ndisUnbindProtocol: Open 007C8590, Notify 0 4294921797 PID:208d3cbe TID:c075f242 ==>ndisReferenceProtocol 4294921798 PID:208d3cbe TID:c075f242 Protocol: 4294921799 PID:208d3cbe TID:c075f242 MDC8021X 4294921801 PID:208d3cbe TID:c075f242 , RefCount: 3 4294921802 PID:208d3cbe TID:c075f242 <==ndisReferenceProtocol 4294921804 PID:208d3cbe TID:c075f242 ==>NdisCloseAdapter 4294921805 PID:208d3cbe TID:a063f002 0x80597a8c: +CFunction(tier 2)::HandleDetach 4294921806 PID:208d3cbe TID:c075f242 Protocol: 4294921808 PID:208d3cbe TID:c075f242 MDC8021X 4294921810 PID:208d3cbe TID:c075f242 is closing Adapter: 4294921811 PID:208d3cbe TID:c075f242 NETWLAN1 4294921812 PID:208d3cbe TID:c075f242 4294921814 PID:208d3cbe TID:c075f242 ==>ndisMKillOpen: Open 007C8590 4294921815 PID:208d3cbe TID:c075f242 !=0 Open 0x7c8590 References 0x1 4294921817 PID:208d3cbe TID:c075f242 - Open 0x7c8590 Reference 0x1 4294921819 PID:208d3cbe TID:c075f242 ==>ndisMFinishClose: MOpen 007C8590 4294921822 PID:208d3cbe TID:c075f242 ==>ndisDeQueueOpenOnProtocol 4294921823 PID:208d3cbe TID:c075f242 Protocol: 4294921824 PID:208d3cbe TID:c075f242 MDC8021X 4294921825 PID:208d3cbe TID:c075f242 4294921827 PID:208d3cbe TID:c075f242 <==ndisDeQueueOpenOnProtocol 4294921828 PID:208d3cbe TID:c075f242 ==>ndisDeQueueOpenOnMiniport: MOpen 007C8590, Miniport 0004B838 4294921830 PID:208d3cbe TID:c075f242 <==ndisDeQueueOpenOnMiniport: MOpen 007C8590, Miniport 0004B838 4294921832 PID:208d3cbe TID:c075f242 <==ndisMFinishClose: Mopen 007C8590 4294921833 PID:208d3cbe TID:c075f242 <==ndisMKillOpen: Open 007C8590, rc 0 4294921835 PID:208d3cbe TID:c075f242 <==NdisCloseAdapter 4294921832 PID:208d3cbe TID:876cc6 ndisWorkerThread: WorkItem 007C8654 4294921839 PID:208d3cbe TID:e0678f8e ==>ndisMQueuedFinishClose: Open 007C8590, Miniport 0004B838 $$$ failure occurs and we don't see it unbind from any other protocols 4294921841 PID:208d3cbe TID:e0678f8e ==>NdisCompleteUnbindAdapter 4294921843 PID:208d3cbe TID:e0678f8e 0x8079b8cc: ObjectCall: Failed (2): h=0 4294921858 PID:208d3cbe TID:e0678f8e 0x8079b8cc: Invalid handle: Set=4 Method=2 4294921860 PID:208d3cbe TID:e0678f8e <==NdisCompleteUnbindAdapter 4294921862 PID:208d3cbe TID:e0678f8e ==>ndisDereferenceProtocol 4294921863 PID:208d3cbe TID:e0678f8e Protocol: 4294921864 PID:208d3cbe TID:e0678f8e MDC8021X 4294921866 PID:208d3cbe TID:e0678f8e , RefCount: 2 4294921867 PID:208d3cbe TID:e0678f8e <==ndisDereferenceProtocol 4294921869 PID:208d3cbe TID:e0678f8e <==ndisMQueuedFinishClose: Open 007C8590, Miniport 0004B838 4294922384 PID:208d3cbe TID:8087c33e S24NIC: +NIC_COMMAND1: [00000011] [0000F103] [00000000] [00000000] 4294923012 PID:208d3cbe TID:8087c33e S24NIC: @POWER DOWN 4294923014 PID:208d3cbe TID:8087c33e S24NIC: @FAILED Setting CR_INQUIRE in Resd Group Info 4294923015 PID:208d3cbe TID:8087c33e ==>ndisMProcessDeferred 4294923017 PID:208d3cbe TID:8087c33e <==ndisMProcessDeferred 4294923006 PID:208d3cbe TID:e0597fde ==>ndisMSwapOpenHandlers: Miniport 0004149C, FakeStatus c001000d, Flags 1 4294923020 PID:208d3cbe TID:e0597fde <==ndisMSwapOpenHandlers: Miniport 0004149C 4294923021 PID:208d3cbe TID:e0597fde ***NDIS*** (a, 830) 4294923023 PID:208d3cbe TID:e0597fde Calling miniport reset 4294923024 PID:208d3cbe TID:e0597fde ==>ndisMAbortPackets 4294923025 PID:208d3cbe TID:e0597fde <==ndisMAbortPackets 4294923027 PID:208d3cbe TID:e0597fde ==>ndisMAbortRequests 4294923028 PID:208d3cbe TID:e0597fde <==ndisMAbortRequests 4294923030 PID:208d3cbe TID:e0597fde ==>ndisMRestoreOpenHandlers: Miniport 0004149C, Current fake status c001000d, Flags 1 4294923031 PID:208d3cbe TID:e0597fde <==ndisMRestoreOpenHandlers: Miniport 0004149C 4294923033 PID:208d3cbe TID:e0597fde 0x80783664: ndisMResetCompleteStage2: Internal reset 4294923034 PID:208d3cbe TID:e0597fde 0x80783664: NDIS: ndisMResetCompleteStage2: RebindOnResume ASYNCMAC1 = 0 4294921977 PID:208d3cbe TID:808d0bb6 0x808bcdb4: PlatformLoadTimeouts: ACUserIdle 10000, ACSystemIdle 10000, ACSuspend -20001, BattUserIdle 10000, BattSystemIdle 10000, BattSuspend 280000 4294922137 PID:752fa6 TID:a0739ce2 0x807888a8: Back from PowerOffSystem. 4294922012 PID:40719f16 TID:8071ab26 0x8070c400: TekDTSvc: Port 0 connect, DeviceID 8 4294923062 PID:40719f16 TID:8071ab26 0x8070c400: TekDTSvc: Port 1 disconnect 4294923383 PID:208d3cbe TID:8087c33e S24NIC: +NIC_COMMAND1: [00000011] [0000F103] [00000000] [00000000] 4294923384 PID:208d3cbe TID:8087c33e S24NIC: @POWER DOWN 4294923385 PID:208d3cbe TID:8087c33e S24NIC: @FAILED Setting CR_INQUIRE in Resd Group Info 4294923385 PID:208d3cbe TID:8087c33e ==>ndisMProcessDeferred 4294923386 PID:208d3cbe TID:8087c33e <==ndisMProcessDeferred 4294923522 PID:208d3cbe TID:8087c33e S24NIC: +TrilogyCheckForHang 4294923523 PID:208d3cbe TID:8087c33e S24NIC: @FAIL CHECKFORHANG: 0000DEAD 4294923523 PID:208d3cbe TID:8087c33e ***NDIS*** (b, 2769) 4294923524 PID:208d3cbe TID:8087c33e ==>ndisMQueueWorkItem 4294923525 PID:208d3cbe TID:8087c33e ***NDIS*** (b, 2802) 4294923525 PID:208d3cbe TID:8087c33e <==ndisMQueueWorkItem 4294923526 PID:208d3cbe TID:8087c33e ==>ndisMProcessDeferred 4294923526 PID:208d3cbe TID:8087c33e Reset requested 4294923527 PID:208d3cbe TID:8087c33e ==>ndisMSwapOpenHandlers: Miniport 0004B838, FakeStatus c001000d, Flags 1 4294923529 PID:208d3cbe TID:8087c33e <==ndisMSwapOpenHandlers: Miniport 0004B838 4294923531 PID:208d3cbe TID:8087c33e Calling miniport reset 4294923532 PID:208d3cbe TID:8087c33e S24NIC: +RESET 4294923534 PID:208d3cbe TID:8087c33e S24NIC: @POWER DOWN 4294923546 PID:208d3cbe TID:8087c33e ==>ndisMAbortPackets 4294923546 PID:208d3cbe TID:8087c33e <==ndisMAbortPackets 4294923547 PID:208d3cbe TID:8087c33e ==>ndisMAbortRequests 4294923548 PID:208d3cbe TID:8087c33e <==ndisMAbortRequests 4294923548 PID:208d3cbe TID:8087c33e ==>ndisMRestoreOpenHandlers: Miniport 0004B838, Current fake status c001000d, Flags 1 4294923549 PID:208d3cbe TID:8087c33e <==ndisMRestoreOpenHandlers: Miniport 0004B838 4294923551 PID:208d3cbe TID:8087c33e 0x808fea60: ndisMResetCompleteStage2: Internal reset 4294923551 PID:208d3cbe TID:8087c33e 0x808fea60: NDIS: ndisMResetCompleteStage2: RebindOnResume NETWLAN1 = 0 4294923552 PID:208d3cbe TID:8087c33e <==ndisMProcessDeferred 4294923553 PID:208d3cbe TID:80845662 ***NDIS*** (c, 318) 4294923561 PID:208d3cbe TID:80845662 ==>ndisMRequest 4294924250 PID:208d3cbe TID:60a482 0x80845400: DEVICE!ActivateDeviceEx(Drivers\USB\LoadClients\Default\Default\3\PSION_Tekl ogix_Hid_Class_Driver) entered 4294924254 PID:208d3cbe TID:60a482 0x80845400: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (HID1:) ATTACH 4294924258 PID:208d3cbe TID:60a482 0x80845400: HidNewDevice, hDevice = 0x34D730, MaxPacketSize0: 8 4294924259 PID:208d3cbe TID:60a482 0x80845400: Interface: IFNum: 0, NumEP: 1, Class: 0x3, SubClass: 0x1, Protocol: 0x2 4294924259 PID:208d3cbe TID:60a482 0x80845400: HID Descriptor: bLength: 9, bcdHID: 0x110, bCountryCode: 0x0 4294924260 PID:208d3cbe TID:60a482 0x80845400: bNumDescriptors: 1, bClassDescriptorType: 0x22, wDescriptorLength: 72 4294924262 PID:208d3cbe TID:60a482 0x80845400: +USBD:OpenPipe, EP: 129, MaxPkt: 4, Type: Interrupt 4294924263 PID:208d3cbe TID:60a482 0x80845400: CInterruptPipe::OpenPipe - setting the poll interval to 8 ms instead of 10 ms 4294924265 PID:208d3cbe TID:60a482 0x80845400: -USBD:OpenPipe success, hPipe = 34DA80 4294924269 PID:208d3cbe TID:60a482 0x80845400: -CHub(External tier 1)::AttachDevice - port = 3, fIsLowSpeed = 1, address = 2 4294924276 PID:208d3cbe TID:87c28a 0x8086fb84: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2 4294924297 PID:208d3cbe TID:a05a9866 0x805eb940: Hid: Entered worker thread 4294924299 PID:208d3cbe TID:a05a9866 0x805eb940: HID: Parse error, FF is an unsupported usage page 4294924301 PID:208d3cbe TID:a05a9866 0x805eb940: Parse error. Main before Usage 4294924303 PID:208d3cbe TID:a05a9866 0x805eb940: Parse error. Main before Usage 4294924382 PID:208d3cbe TID:8087c33e S24NIC: +NIC_COMMAND1: [00000011] [0000F103] [00000000] [00000000] 4294924383 PID:208d3cbe TID:8087c33e S24NIC: @POWER DOWN 4294924384 PID:208d3cbe TID:8087c33e S24NIC: @FAILED Setting CR_INQUIRE in Resd Group Info 4294924384 PID:208d3cbe TID:8087c33e ==>ndisMProcessDeferred 4294924385 PID:208d3cbe TID:8087c33e <==ndisMProcessDeferred 4294925385 PID:208d3cbe TID:8087c33e S24NIC: +NIC_COMMAND1: [00000011] [0000F103] [00000000] [00000000] 4294925386 PID:208d3cbe TID:8087c33e S24NIC: @POWER DOWN 4294925387 PID:208d3cbe TID:8087c33e S24NIC: @FAILED Setting CR_INQUIRE in Resd Group Info 4294925387 PID:208d3cbe TID:8087c33e ==>ndisMProcessDeferred 4294925388 PID:208d3cbe TID:8087c33e <==ndisMProcessDeferred 4294925517 PID:208d3cbe TID:8087c33e S24NIC: +TrilogyCheckForHang 4294925518 PID:208d3cbe TID:8087c33e S24NIC: @FAIL CHECKFORHANG: 0000DEAD 4294925518 PID:208d3cbe TID:8087c33e ***NDIS*** (b, 2769) 4294925519 PID:208d3cbe TID:8087c33e ==>ndisMQueueWorkItem 4294925520 PID:208d3cbe TID:8087c33e ***NDIS*** (b, 2802) 4294925520 PID:208d3cbe TID:8087c33e <==ndisMQueueWorkItem 4294925521 PID:208d3cbe TID:8087c33e ==>ndisMProcessDeferred 4294925521 PID:208d3cbe TID:8087c33e Reset requested 4294925522 PID:208d3cbe TID:8087c33e ==>ndisMSwapOpenHandlers: Miniport 0004B838, FakeStatus c001000d, Flags 1 4294925524 PID:208d3cbe TID:8087c33e <==ndisMSwapOpenHandlers: Miniport 0004B838 4294925526 PID:208d3cbe TID:8087c33e Calling miniport reset 4294925527 PID:208d3cbe TID:8087c33e S24NIC: +RESET 4294925529 PID:208d3cbe TID:8087c33e S24NIC: @POWER DOWN 4294925541 PID:208d3cbe TID:8087c33e ==>ndisMAbortPackets 4294925542 PID:208d3cbe TID:8087c33e <==ndisMAbortPackets 4294925542 PID:208d3cbe TID:8087c33e ==>ndisMAbortRequests 4294925543 PID:208d3cbe TID:8087c33e <==ndisMAbortRequests 4294925543 PID:208d3cbe TID:8087c33e ==>ndisMRestoreOpenHandlers: Miniport 0004B838, Current fake status c001000d, Flags 1 4294925544 PID:208d3cbe TID:8087c33e <==ndisMRestoreOpenHandlers: Miniport 0004B838 4294925546 PID:208d3cbe TID:8087c33e 0x808fea60: ndisMResetCompleteStage2: Internal reset 4294925546 PID:208d3cbe TID:8087c33e 0x808fea60: NDIS: ndisMResetCompleteStage2: RebindOnResume NETWLAN1 = 0 4294925547 PID:208d3cbe TID:8087c33e <==ndisMProcessDeferred 4294925550 PID:208d3cbe TID:80845662 ***NDIS*** (c, 318) This the debug for a resume with no supplicant 4294872948 PID:208d3cbe TID:607353e2 Back from OEMPowerOff 4294872948 PID:208d3cbe TID:607353e2 Calling device manager power proc. 4294872948 PID:208d3cbe TID:607353e2 Calling GWES power proc. 4294872948 PID:2075d63e TID:607353e2 Returning to normally scheduled programming. 4294872948 PID:2075d63e TID:607353e2 Setting Event a08d021e, phd = 808d021c 4294872948 PID:2075d63e TID:607353e2 Setting Event 208d0242, phd = 808d0240 4294872948 PID:2075d63e TID:607353e2 Setting Event a0735702, phd = 80735700 4294872948 PID:2075d63e TID:607353e2 Returning from PowerOnSetEvents. 4294872954 PID:208d3cbe TID:808525ee 0x808519e8: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294872987 PID:208d3cbe TID:808525ee 0x808519e8: PCMCIA:PcmciaPowerOn: socket 1 powered up 4294872989 PID:208d3cbe TID:208f9686 0x8062bab4: NDIS:: PcmciaCallBack Event=CE_PM_SUSPEND hSock=0 4294872990 PID:208d3cbe TID:208f9686 S24NIC: CallBackFn: 0000000C 4294872990 PID:208d3cbe TID:208f9686 0x8062bab4: NDIS:: PcmciaCallBack Event=CE_CARD_REMOVAL hSock=0 4294872991 PID:208d3cbe TID:208f9686 S24NIC: CallBackFn: 00000005 4294872992 PID:208d3cbe TID:208f9686 S24NIC: CE_CARD_REMOVAL 4294872992 PID:208d3cbe TID:208f9686 S24NIC: @POWER DOWN = TRUE 4294872995 PID:208d3cbe TID:8085efc2 0x808b9da4: PDCardSetSocket 1 bvd 4294872996 PID:208d3cbe TID:8085efc2 0x808b9da4: PDCardSetSocket 1 cd rising 4294872997 PID:208d3cbe TID:8085efc2 0x808b9da4: PDCardSetSocket 1 irq off 4294873002 PID:808f923e TID:607353e2 0x80757000: FS: Got Power notif 0x00000001 4294873008 PID:208d3cbe TID:2084a756 0x80838950: +CHub(Root tier 0)::HandleDetach 4294873010 PID:208d3cbe TID:2084a756 0x80838950: CHub(Root tier 0)::HandleDetach - status change thread closed in 1 ms 4294873011 PID:208d3cbe TID:2084a756 0x80838950: +CHub(External tier 1)::HandleDetach 4294873020 PID:208d3cbe TID:808525ee 0x808519e8: PCMCIA:Leaving PcmciaPowerOn 4294873022 PID:208d3cbe TID:808525ee 0x808519e8: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294873023 PID:208d3cbe TID:808525ee 0x808519e8: PCMCIA:Leaving PcmciaPowerOn 4294873024 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS:: PcmciaCallBack Event=CE_PM_SUSPEND hSock=1 4294873025 PID:208d3cbe TID:2067ef96 S24NIC: CallBackFn: 0000000C 4294873026 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS:: PcmciaCallBack Event=CE_CARD_REMOVAL hSock=1 4294873027 PID:208d3cbe TID:2067ef96 S24NIC: CallBackFn: 00000005 4294873027 PID:208d3cbe TID:2067ef96 S24NIC: CE_CARD_REMOVAL 4294873029 PID:208d3cbe TID:2084a756 0x80838950: CHub(External tier 1)::HandleDetach - status change thread closed in 17 ms 4294873028 PID:208d3cbe TID:2067ef96 S24NIC: @POWER DOWN = TRUE 4294873038 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS: +ndisRemovePCCardDevice 4294873040 PID:208d3cbe TID:2067ef96 ==>ndisPnPRemoveDevice: Miniport 0004B738 4294873041 PID:208d3cbe TID:2067ef96 ==>ndisCloseMiniportBindings, Miniport 0004B738 4294873044 PID:208d3cbe TID:2067ef96 ==>ndisUnbindProtocol: Open 0035C1D0, Notify 0 $$$ Starts unbinding from TCPIP 4294873047 PID:208d3cbe TID:2067ef96 ==>ndisReferenceProtocol 4294873048 PID:208d3cbe TID:2067ef96 Protocol: 4294873049 PID:208d3cbe TID:2067ef96 TCPIP 4294873051 PID:208d3cbe TID:2067ef96 , RefCount: 3 4294873052 PID:208d3cbe TID:2067ef96 <==ndisReferenceProtocol 4294873054 PID:208d3cbe TID:2067ef96 ***NDIS*** (c, 318) 4294873055 PID:208d3cbe TID:2067ef96 ==>ndisMRequest 4294873057 PID:208d3cbe TID:2067ef96 0x807a9924: *TakeNetDown: pDhcp 0x35ce40 IP FB70FEA9! 4294873060 PID:208d3cbe TID:2067ef96 0x807a9924: *FreeDhcpInfo: 35CE40 4294873062 PID:208d3cbe TID:2067ef96 0x807a9924: +OpenIFConfig(Comm\NETWLAN1\Parms\TCPIP Handle 0x654F7A8) 4294873064 PID:208d3cbe TID:2067ef96 0x807a9924: Opened registry info for Comm\NETWLAN1\Parms\TCPIP 4294873066 PID:208d3cbe TID:2067ef96 0x807a9924: -OpenIFConfig(Comm\NETWLAN1\Parms\TCPIP *Handle 0x654F7A8, BOOL Ret: 1) 4294873067 PID:208d3cbe TID:2067ef96 0x807a9924: *CloseIFConfig(Handle 0xA9C80) 4294873069 PID:208d3cbe TID:2067ef96 0x807a9924: +IPNotifyClientsIPEvent 4294873070 PID:208d3cbe TID:2067ef96 0x807a9924: IPNotifyClientsIPEvent: PendingIPGetIPEventRequest 6da10 4294873073 PID:208d3cbe TID:2067ef96 0x807a9924: IPNotifyClientsIPEvent: PendingIrp 6da10 4294873074 PID:208d3cbe TID:2067ef96 0x807a9924: IPNotifyClientsIPEvent: SetEvent 4294873076 PID:208d3cbe TID:2067ef96 Search Route #3: Route not found 4294873078 PID:208d3cbe TID:2067ef96 ==>NdisCloseAdapter 4294873079 PID:208d3cbe TID:2067ef96 Protocol: 4294873081 PID:208d3cbe TID:2067ef96 TCPIP 4294873082 PID:208d3cbe TID:2067ef96 is closing Adapter: 4294873084 PID:208d3cbe TID:2067ef96 NETWLAN1 4294873085 PID:208d3cbe TID:2067ef96 4294873086 PID:208d3cbe TID:2067ef96 ==>ndisMKillOpen: Open 0035C1D0 4294873088 PID:208d3cbe TID:2067ef96 !=0 Open 0x35c1d0 References 0x1 4294873089 PID:208d3cbe TID:2067ef96 - Open 0x35c1d0 Reference 0x1 4294873091 PID:208d3cbe TID:2067ef96 ==>ndisMFinishClose: MOpen 0035C1D0 4294873092 PID:208d3cbe TID:2067ef96 ==>ndisDeQueueOpenOnProtocol 4294873095 PID:208d3cbe TID:2067ef96 Protocol: 4294873110 PID:208d3cbe TID:2067ef96 TCPIP 4294873111 PID:208d3cbe TID:2067ef96 4294873112 PID:208d3cbe TID:2067ef96 <==ndisDeQueueOpenOnProtocol 4294873114 PID:208d3cbe TID:2067ef96 ==>ndisDeQueueOpenOnMiniport: MOpen 0035C1D0, Miniport 0004B738 4294873115 PID:208d3cbe TID:2067ef96 <==ndisDeQueueOpenOnMiniport: MOpen 0035C1D0, Miniport 0004B738 4294873117 PID:208d3cbe TID:2067ef96 <==ndisMFinishClose: Mopen 0035C1D0 4294873119 PID:208d3cbe TID:2067ef96 <==ndisMKillOpen: Open 0035C1D0, rc 0 4294873120 PID:208d3cbe TID:2067ef96 <==NdisCloseAdapter 4294873117 PID:208d3cbe TID:40875c36 ndisWorkerThread: WorkItem 0035C294 4294873124 PID:208d3cbe TID:20852182 ==>ndisMQueuedFinishClose: Open 0035C1D0, Miniport 0004B738 4294873127 PID:208d3cbe TID:20852182 ==>ndisDereferenceProtocol 4294873128 PID:208d3cbe TID:20852182 Protocol: 4294873130 PID:208d3cbe TID:20852182 TCPIP 4294873131 PID:208d3cbe TID:20852182 , RefCount: 2 4294873132 PID:208d3cbe TID:20852182 <==ndisDereferenceProtocol 4294873134 PID:208d3cbe TID:2067ef96 ==>ndisDereferenceProtocol 4294873136 PID:208d3cbe TID:2067ef96 Protocol: 4294873137 PID:208d3cbe TID:2067ef96 TCPIP 4294873138 PID:208d3cbe TID:2067ef96 , RefCount: 1 4294873140 PID:208d3cbe TID:2067ef96 <==ndisDereferenceProtocol 4294873141 PID:208d3cbe TID:2067ef96 <==ndisUnbindProtocol: Open 0035C1D0, Notify 0, Status 0 $$$ Done unbinding from TCPIP and continues with unbinding NDISUIO 4294873143 PID:208d3cbe TID:2067ef96 ==>ndisUnbindProtocol: Open 00358BE0, Notify 0 4294873144 PID:208d3cbe TID:2067ef96 ==>ndisReferenceProtocol 4294873146 PID:208d3cbe TID:2067ef96 Protocol: 4294873147 PID:208d3cbe TID:2067ef96 NDISUIO 4294873148 PID:208d3cbe TID:2067ef96 , RefCount: 3 4294873150 PID:208d3cbe TID:2067ef96 <==ndisReferenceProtocol 4294873152 PID:208d3cbe TID:2067ef96 ==>NdisCloseAdapter 4294873156 PID:208d3cbe TID:2067ef96 Protocol: 4294873158 PID:208d3cbe TID:2067ef96 NDISUIO 4294873160 PID:208d3cbe TID:2067ef96 is closing Adapter: 4294873161 PID:208d3cbe TID:2067ef96 NETWLAN1 4294873162 PID:208d3cbe TID:2067ef96 4294873163 PID:208d3cbe TID:2067ef96 ==>ndisMKillOpen: Open 00358BE0 4294873164 PID:208d3cbe TID:2067ef96 !=0 Open 0x358be0 References 0x1 4294873166 PID:208d3cbe TID:2067ef96 - Open 0x358be0 Reference 0x1 4294873167 PID:208d3cbe TID:2067ef96 ==>ndisMFinishClose: MOpen 00358BE0 4294873169 PID:208d3cbe TID:2067ef96 ==>ndisDeQueueOpenOnProtocol 4294873170 PID:208d3cbe TID:2067ef96 Protocol: 4294873171 PID:208d3cbe TID:2067ef96 NDISUIO 4294873173 PID:208d3cbe TID:2067ef96 4294873174 PID:208d3cbe TID:2067ef96 <==ndisDeQueueOpenOnProtocol 4294873176 PID:208d3cbe TID:2067ef96 ==>ndisDeQueueOpenOnMiniport: MOpen 00358BE0, Miniport 0004B738 4294873177 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS:: Forced unblocking MEDIA_CONNECT by [NDISUIO] on [NETWLAN1] 4294873179 PID:208d3cbe TID:2067ef96 <==ndisDeQueueOpenOnMiniport: MOpen 00358BE0, Miniport 0004B738 4294873180 PID:208d3cbe TID:2067ef96 <==ndisMFinishClose: Mopen 00358BE0 4294873182 PID:208d3cbe TID:2067ef96 <==ndisMKillOpen: Open 00358BE0, rc 0 4294873184 PID:208d3cbe TID:2067ef96 <==NdisCloseAdapter 4294873134 PID:208d3cbe TID:20852182 <==ndisMQueuedFinishClose: Open 0035C1D0, Miniport 0004B738 4294873181 PID:208d3cbe TID:40875c36 ndisWorkerThread: WorkItem 00358CA4 4294873191 PID:208d3cbe TID:e07b11ba ==>ndisMQueuedFinishClose: Open 00358BE0, Miniport 0004B738 4294873193 PID:208d3cbe TID:e07b11ba ==>ndisDereferenceProtocol 4294873194 PID:208d3cbe TID:e07b11ba Protocol: 4294873196 PID:208d3cbe TID:e07b11ba NDISUIO 4294873197 PID:208d3cbe TID:e07b11ba , RefCount: 2 4294873199 PID:208d3cbe TID:e07b11ba <==ndisDereferenceProtocol 4294873200 PID:208d3cbe TID:2067ef96 ==>ndisDereferenceProtocol 4294873202 PID:208d3cbe TID:2067ef96 Protocol: 4294873203 PID:208d3cbe TID:2067ef96 NDISUIO 4294873205 PID:208d3cbe TID:2067ef96 , RefCount: 1 4294873206 PID:208d3cbe TID:2067ef96 <==ndisDereferenceProtocol 4294873208 PID:208d3cbe TID:2067ef96 <==ndisUnbindProtocol: Open 00358BE0, Notify 0, Status 0 4294873210 PID:208d3cbe TID:2067ef96 <==ndisCloseMiniportBindings, Miniport 0004B738 4294873211 PID:208d3cbe TID:2067ef96 ==>ndisMHaltMiniport: Miniport 0004B738 4294873213 PID:208d3cbe TID:2067ef96 ==>ndisMCommonHaltMiniport: Miniport 0004B738 4294873214 PID:208d3cbe TID:2067ef96 S24NIC: +HALT $$$ Miniport is halted correctly. (We don't see this when the supplicant is running) 4294873215 PID:208d3cbe TID:2067ef96 ***NDIS*** (a, 659) 4294873217 PID:208d3cbe TID:2067ef96 ==>NdisMDeregisterInterrupt: Miniport 0004B738 4294873219 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 bvd 4294873220 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 cd rising 4294873221 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 irq off 4294873223 PID:208d3cbe TID:2067ef96 ***NDIS*** (a, 728) 4294873225 PID:208d3cbe TID:2067ef96 <==NdisMDeregisterInterrupt: Miniport 0004B738 4294873201 PID:208d3cbe TID:e07b11ba <==ndisMQueuedFinishClose: Open 00358BE0, Miniport 0004B738 4294873231 PID:208d3cbe TID:a07b37fe 0x807b1b44: NotifyChange: Setting Event 8068B7A6 4294873233 PID:208d3cbe TID:a07b3822 0x807b3d94: ************DHCP MEDIA STATUS************ 4294873234 PID:208d3cbe TID:a07b3822 0x807b3d94: SeqNo: 31 4294873236 PID:208d3cbe TID:a07b3822 0x807b3d94: MediaStatus: 11027 4294873238 PID:208d3cbe TID:a07b3822 0x807b3d94: Context: 65535 - 65535 4294873239 PID:208d3cbe TID:a07b3822 0x807b3d94: AdapterName: NETWLAN1 4294873242 PID:208d3cbe TID:a07b3822 0x807b3d94: Media Status is: IP_UNBIND_ADAPTER 4294873244 PID:208d3cbe TID:a07b3822 0x807b3d94: IPDispatchDeviceControl returned Status 103 4294873247 PID:208d3cbe TID:a07a285e 0x807576e4: Hid: Leaving worker thread 4294873250 PID:208d3cbe TID:2084a756 0x80838950: -Hid DriverEntry 4294873252 PID:208d3cbe TID:2084a756 0x80838950: <<< Unloading module usbhid.dll at address 0x03170000-0x03181000 (RW data at 0x01F26000-0x01F265E4) Unloaded symbols for 'R:\753X\RELDIR\753X_HANDHELDDEBUG\USBHID.DLL' 4294873257 PID:208d3cbe TID:2084a756 0x80838950: -CFunction(tier 2)::HandleDetach 4294873258 PID:208d3cbe TID:2084a756 0x80838950: -CHub(External tier 1)::HandleDetach 4294873258 PID:208d3cbe TID:2084a756 0x80838950: -CHub(Root tier 0)::HandleDetach 4294873259 PID:208d3cbe TID:2084a756 0x80838950: +CDevice::DeInitialize 4294873261 PID:208d3cbe TID:2084a756 0x80838950: <<< Unloading module usbd.dll at address 0x03600000-0x03610000 (RW data at 0x01F69000-0x01F695BC) Unloaded symbols for 'R:\753X\RELDIR\753X_HANDHELDDEBUG\USBD.DLL' 4294873263 PID:208d3cbe TID:2084a756 0x80838950: -CDevice::DeInitialize 4294873266 PID:208d3cbe TID:2084a756 0x80838950: DMA buffer passed in from PDD 4294873266 PID:208d3cbe TID:2084a756 0x80838950: CPhysMem Total Alloc Region PhysAddr = 0x0806BC00, VirtAddr = 0x0052BC00, size = 32768 4294873268 PID:208d3cbe TID:2084a756 0x80838950: CPhysMem Special Alloc Region PhysAddr = 0x0806BC00, VirtAddr = 0x0052BC00, size = 4096 4294873270 PID:208d3cbe TID:2084a756 0x80838950: CPhysMem HighPri Alloc Region PhysAddr = 0x0806CC00, VirtAddr = 0x0052CC00, size = 16384 4294873272 PID:208d3cbe TID:2084a756 0x80838950: CPhysMem Normal Alloc Region PhysAddr = 0x08070C00, VirtAddr = 0x00530C00, size = 12288 4294873273 PID:208d3cbe TID:2084a756 0x80838950: +CUhcd::Initialize. Entry 4294873274 PID:208d3cbe TID:2084a756 0x80838950: +CDevice::Initialize 4294873477 PID:208d3cbe TID:2067ef96 0x807a9924: CardReleaseWindow failed 29 4294874525 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:CardModifyConfiguration succeeded 4294874527 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 bvd off 4294874528 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 cd rising 4294874529 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 irq off 4294874531 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOff (sock: 1, force: 0) 4294874532 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 bvd off 4294874533 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 cd rising 4294874535 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 irq off 4294874536 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:PcmciaPowerOff: socket 1 powered down 4294874537 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:CardReleaseIRQ failed 28 4294874539 PID:208d3cbe TID:2067ef96 0x807a9924: CardReleaseSocketMask failed 11 4294874540 PID:208d3cbe TID:2067ef96 0x807a9924: CardReleaseExclusive failed 30 4294874542 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOff (sock: 0, force: 0) 4294874543 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOff (sock: 1, force: 0) 4294874545 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 bvd off 4294874546 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 cd rising 4294874547 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 irq off 4294874549 PID:208d3cbe TID:2067ef96 ####################### 4294874551 PID:208d3cbe TID:2067ef96 DeAllocate - pPcmcia 34 4294874552 PID:208d3cbe TID:2067ef96 DeAllocate - pOddBoundaryBuffer 1 - 2000 4294874554 PID:208d3cbe TID:2067ef96 DeAllocate - BAP . Send SpinLock 4294874556 PID:208d3cbe TID:2067ef96 S24NIC: -HALT 4294874557 PID:208d3cbe TID:2067ef96 DeAllocate - pAdapter (halt) 4ab0 4294874558 PID:208d3cbe TID:2067ef96 ****************** 4294874560 PID:208d3cbe TID:2067ef96 ==>ndisMAbortPackets 4294874561 PID:208d3cbe TID:2067ef96 <==ndisMAbortPackets 4294874563 PID:208d3cbe TID:2067ef96 ==>ndisMAbortRequests 4294874564 PID:208d3cbe TID:2067ef96 <==ndisMAbortRequests 4294874566 PID:208d3cbe TID:2067ef96 <==ndisMCommonHaltMiniport: Miniport 0004B738 4294874567 PID:208d3cbe TID:2067ef96 ==>NdisMDeregisterAdapterShutdownHandler: Miniport 0004B738 4294874569 PID:208d3cbe TID:2067ef96 <==NdisMDeregisterAdapterShutdownHandler: Miniport 0004B738 4294874570 PID:208d3cbe TID:2067ef96 <==ndisMHaltMiniport: Miniport 0004B738 4294874572 PID:208d3cbe TID:2067ef96 <==ndisPnPRemoveDevice: Miniport 0004B738 4294874573 PID:208d3cbe TID:2067ef96 ndisDereferenceMiniport:Miniport 0004B738, Ref = 0 4294874575 PID:208d3cbe TID:2067ef96 ==>ndisIsMiniportStarted: Miniport 0004B738 4294874576 PID:208d3cbe TID:2067ef96 <==ndisIsMiniportStarted: Miniport 0004B738, Started 1 4294874578 PID:208d3cbe TID:2067ef96 ==>ndisDeQueueMiniportOnDriver, Miniport 0004B738, MiniBlock 0004B540 4294874580 PID:208d3cbe TID:2067ef96 <==ndisDeQueueMiniportOnDriver: Miniport 0004B738, MiniBlock 0004B540 4294874581 PID:208d3cbe TID:2067ef96 ==>NdisMDeregisterAdapterShutdownHandler: Miniport 0004B738 4294874583 PID:208d3cbe TID:2067ef96 <==NdisMDeregisterAdapterShutdownHandler: Miniport 0004B738 4294874584 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS: +PcmciaReleaseAdapterResources 4294874586 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:CardReleaseIRQ failed 28 4294874587 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS: -PcmciaReleaseAdapterResources 4294874519 PID:208d3cbe TID:60673f36 ==>ndisMSwapOpenHandlers: Miniport 0004149C, FakeStatus c001000d, Flags 1 4294874590 PID:208d3cbe TID:60673f36 <==ndisMSwapOpenHandlers: Miniport 0004149C 4294874592 PID:208d3cbe TID:60673f36 ***NDIS*** (a, 830) 4294874593 PID:208d3cbe TID:60673f36 Calling miniport reset 4294874594 PID:208d3cbe TID:60673f36 ==>ndisMAbortPackets 4294874596 PID:208d3cbe TID:60673f36 <==ndisMAbortPackets 4294874597 PID:208d3cbe TID:60673f36 ==>ndisMAbortRequests 4294874599 PID:208d3cbe TID:60673f36 <==ndisMAbortRequests 4294874600 PID:208d3cbe TID:60673f36 ==>ndisMRestoreOpenHandlers: Miniport 0004149C, Current fake status c001000d, Flags 1 4294874602 PID:208d3cbe TID:60673f36 <==ndisMRestoreOpenHandlers: Miniport 0004149C 4294874603 PID:208d3cbe TID:60673f36 0x8079ba60: ndisMResetCompleteStage2: Internal reset 4294874604 PID:208d3cbe TID:60673f36 0x8079ba60: NDIS: ndisMResetCompleteStage2: RebindOnResume ASYNCMAC1 = 0 4294874606 PID:208d3cbe TID:2067ef96 ==>ndisMUnload: DriverObject 0004B430 4294874609 PID:208d3cbe TID:2067ef96 ndisMUnload: MiniBlock 0004B540 4294874611 PID:208d3cbe TID:2067ef96 <==ndisMUnload: DriverObject 0004B430, MiniBlock 0004B540 4294874613 PID:208d3cbe TID:2067ef96 S24NIC: NETWLAN: DLL_PROCESS_DETACH 4294874618 PID:208d3cbe TID:2067ef96 0x807a9924: <<< Unloading module netwlan.dll at address 0x03070000-0x030BA000 (RW data at 0x01EFE000-0x01F18F7C) Unloaded symbols for 'R:\753X\RELDIR\753X_HANDHELDDEBUG\NETWLAN.DLL' 4294874621 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS: -ndisRemovePCCardDevice 4294875633 PID:208d3cbe TID:2067ef96 0x807a9924: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (NDS1:) DETACH 4294875637 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 bvd off 4294875638 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 cd rising 4294875639 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 irq off 4294874831 PID:208d3cbe TID:a0875f9a 0x8062bab4: CHub(Root tier 0)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0101 4294873336 PID:208d3cbe TID:8d0c5e 0x808bcd9c: PlatformLoadTimeouts: ACUserIdle 10000, ACSystemIdle 10000, ACSuspend -20001, BattUserIdle 10000, BattSystemIdle 10000, BattSuspend 280000 4294873435 PID:2075d63e TID:607353e2 0x80757000: Back from PowerOffSystem. 4294873341 PID:208d3cbe TID:c0779f5e 0x8078294c: ZCF:: Notification:: Event [UNBIND] Adapter [NETWLAN1] 4294875656 PID:208d3cbe TID:a084a152 0x80845400: ZCF:: Cancelling timer [NETWLAN1]: timeout: [60000] ms succssful. 4294875658 PID:208d3cbe TID:a084a152 Ndisuio: 4294875661 PID:208d3cbe TID:a084a152 SetOid: Open 00357240/210 is in invalid state 4294875663 PID:208d3cbe TID:a084a152 0x80845400: ZCF:: IntfContext [0x35d060] deleted.. 4294873343 PID:208d3cbe TID:a069852a 0x8069c660: ETHMAN: Error updating connection status 4294873347 PID:4071cb9a TID:e0700176 0x8070b000: TekDTSvc: Port 0 connect, DeviceID 8 4294875673 PID:4071cb9a TID:e0700176 0x8070b000: TekDTSvc: Port 1 disconnect 4294875827 PID:208d3cbe TID:e07726ba 0x807294e8: NETUIQC: Could not find the systray icon associated with the given window 4294875829 PID:208d3cbe TID:e07726ba 0x807294e8: NetUIQC - Could not get systray icon for the specified hwnd 4294875831 PID:208d3cbe TID:e07726ba 0x807294e8: ETHMAN: Failed to close property sheet if ready 4294875833 PID:208d3cbe TID:e07726ba 0x807294e8: NETUIQC: Could not find the systray icon associated with the given window 4294875834 PID:208d3cbe TID:e07726ba 0x807294e8: NetUIQC - Could not get systray icon for the specified hwnd 4294876391 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876424 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:PcmciaPowerOn: socket 1 powered up 4294876431 PID:208d3cbe TID:c069866e 0x80838950: CHub(External tier 1)::HubStatusChangeThread - port 3, change = 0x0001, status = 0x0301 4294876457 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876458 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:I_MapWindow MAKE SURE THIS PLATFORM'S PCMCIA MEMORY AREAS ARE SPECIFIED AS ACTUAL PHYSICAL ADDRESSES 4294876458 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876459 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876460 PID:208d3cbe TID:2067ef96 0x807a9924: CardGetNextTuple failed 31 4294876461 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876461 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876462 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876463 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876465 PID:208d3cbe TID:2067ef96 0x807a9924: CardGetNextTuple failed 31 4294876466 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:I_MapWindow MAKE SURE THIS PLATFORM'S PCMCIA MEMORY AREAS ARE SPECIFIED AS ACTUAL PHYSICAL ADDRESSES 4294876468 PID:208d3cbe TID:2067ef96 0x807a9924: CreateFunction: Re-using Tuple attribute window, Config registers @ 0x3003e0 for 1:0 4294876469 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876470 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876472 PID:208d3cbe TID:2067ef96 0x807a9924: CardGetFirstTuple failed 31 4294876473 PID:208d3cbe TID:2067ef96 0x807a9924: CreateFunctions: CardGetFirstTuple(CISTPL_LONGLINK_MFC) returned 31 for 1:0 4294876475 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876476 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876478 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOn (socket: 1) 4294876479 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Leaving PcmciaPowerOn 4294876482 PID:208d3cbe TID:2067ef96 0x807a9924: CardGetNextTuple failed 31 4294876483 PID:208d3cbe TID:2067ef96 0x807a9924: GetCardCRC: CardGetNextTuple returned 31 4294876485 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS:: PcmciaCallBack Event=CE_CARD_INSERTION hSock=1 4294876488 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 bvd 4294876490 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 cd rising 4294876491 PID:208d3cbe TID:2067ef96 0x807a9924: PDCardSetSocket 1 irq off 4294876493 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:Entering PcmciaPowerOff (sock: 1, force: 0) 4294876494 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:PcmciaPowerOff(1) -- socket is active, not powering down 4294876495 PID:208d3cbe TID:2067ef96 0x807a9924: PCMCIA:CallbackPmResume sending CE_PM_RESUME 4294876497 PID:208d3cbe TID:2067ef96 0x807a9924: NDIS:: PcmciaCallBack Event=CE_PM_RESUME hSock=0 4294876487 PID:208d3cbe TID:6a3c82 0x8079b400: DEVICE!ActivateDeviceEx(Drivers\PCMCIA\Intel-PRO/Wireless_LAN_PC_Card-82DA) entered 4294876505 PID:208d3cbe TID:6a3c82 0x8079b400: NDIS:+ndisAddPCCardDevice(Drivers\Active\25) 4294876513 PID:208d3cbe TID:6a3c82 0x8079b400: >>> Loading module netwlan.dll at address 0x03070000-0x030BA000 (RW data at 0x01EFE000-0x01F18F7C) Loaded symbols for 'R:\753X\RELDIR\753X_HANDHELDDEBUG\NETWLAN.DLL' 4294876517 PID:208d3cbe TID:6a3c82 S24NIC: NETWLAN: DLL_PROCESS_ATTACH 4294877642 PID:208d3cbe TID:6a3c82 S24NIC: +DRIVERENTRY 4294877642 PID:208d3cbe TID:6a3c82 ==>NdisInitializeWrapper 4294877643 PID:208d3cbe TID:6a3c82 <==NdisInitializeWrapper 4294877644 PID:208d3cbe TID:6a3c82 ==>NdisMRegisterMiniport: NdisWrapperHandle 0004C190 4294877645 PID:208d3cbe TID:6a3c82 ==>ndisRegisterMiniportDriver: NdisWrapperHandle 0004C190 4294877646 PID:208d3cbe TID:6a3c82 <==ndisRegisterMiniportDriver: MiniBlock 0004C200 4294877647 PID:208d3cbe TID:6a3c82 NdisMRegisterMiniport: MiniBlock 0004C200 4294877648 PID:208d3cbe TID:6a3c82 <==NdisMRegisterMiniport: MiniBlock 0004C200, Status 0 4294877649 PID:208d3cbe TID:6a3c82 S24NIC: -DRIVERENTRY $$$ Miniport is now starting to reload. Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40524
  - 21
    - Running windows media player This is a multi-part message in MIME format. --------------4A7E812CA6E1911E5531B4F7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Could somebody tell if there is a way to run the Window Media Player while debuggin under Platform Builder. I can see the Wavplay.exe and Wavrec.exe in available Programs but despite I have added the Windows Media Player I cannot see the player2.exe. Maybe this is not possible tu run it from command line in Windows CE. It is possible in Windows 2000 (at least this is what help says). Regards Hubert --------------4A7E812CA6E1911E5531B4F7 Content-Type: text/x-vcard; charset=us-ascii; name="hubertr.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Hubert Rzezniczak Content-Disposition: attachment; filename="hubertr.vcf" begin:vcard n:Rzezniczak;Hubert tel;fax:0048 71 33-48-101 tel;work:0048 71 33-48-186 x-mozilla-html:FALSE org:Silicon & Software Systems Polska sp. z o.o. version:2.1 email;internet:hubertr@s3group.com.pl title:System Design Engineer adr;quoted-printable:;;ul. Nyska 83/85=0D=0A=0D=0A;50-505 Wroclaw;;;Poland fn:Hubert Rzezniczak end:vcard --------------4A7E812CA6E1911E5531B4F7-- Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40518
  - 22
    - FMD Flash File System fails Hi , I am using Strata NOR FMD driver included with Platform Builder as reference for our Flash FMD driver , and using the same registry used for that driver ( I changed only MemBase and MemLen ) . According to the log in the debug window , my driver (FlashDrv.dll) is failing ,below is the log I get in my debug window , and I don't understand the reason why I get this log ! I ran the driver in debug mode and saw that the driver is passing correct information to the FAL library and saw also that the FAL library calls FMD_ReadSector twice for every first sector in a block , and it passes only pointer for the meta data and the data returned is what is in the flash, the flash still has 0xFF value in all of its bytes . What could be the reason for my driver to fail ? and how should I format for the first time the resulted partition if the driver succeed ? Thanks in advance //------------------------------------------------------------------------------------------------------------------------- Loaded symbols for 'D:\WINCE420\PUBLIC\RG\RELDIR\88E6318_MIPSIV_FPDEBUG\MSPART.DLL' Loaded symbols for 'D:\WINCE420\PUBLIC\RG\RELDIR\88E6318_MIPSIV_FPDEBUG\RELFSD.DLL' 4294768220 PID:41fe6372 TID:41feaf42 0x81fe6000: >>> Loading module mspart.dll at address 0x03E70000-0x03E7B000 (RW data at 0x01FEF000-0x01FEF494) 4294768222 PID:41fe6372 TID:41feaf42 0x81fe6000: Loading partition driver mspart.dll hModule=81FAB000 4294768222 PID:41fe6372 TID:41feaf42 0x81fe6000: Driver mspart.dll loaded 4294768222 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294768223 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 4294768223 PID:41fe6372 TID:41feaf42 0x81fe6000: Opened the store hStore=000B3F00 4294768223 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294768224 PID:41fe6372 TID:41feaf42 0x81fe6000: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 4294768224 PID:41fe6372 TID:41feaf42 0x81fe6000: NumSec=3780 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 -------------------------------------------------------------------------------------------------------------------------// -- Maen Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40504
  - 23
    - Intermittent USB failures Hi! We are using the Samsung S3C2410 BSP on our hardware, parallel with the SMDK 2410. On both platforms we are experiencing intermittent USB problems when attaching a USB keyboard. I've added the OHCD controller and the USBHID class driver, and I usually get the keyboard to function correctly (only english mode though). However, every once in a while, the keyboard stops workings when cold booting the system. Usually, a reset is the solution to have the USB keyboard operate again. I've read the USB Host registers and seen that there is a difference between when the keyboard works and when it doesn't. Does anyone have an idea about this problem? Is it possible to reset the USB driver so that it reloads after all other drivers have loaded? Any ideas on how to solve the problem are appreciated! /Marcus I was thinking it might be a mist Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40501
  - 24
    - How to run the calibrate program once the Wince is boot up? thx a lot!! Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40496
  - 25
    - RegFlushKey did nothing I am using the IPSM data storage and registry backup features. At boot up, the ReadRegistryFromOEM was called. When I backup the registry by calling RegFlushKey(HKEY_LOCAL_MACHINE), the function return with ERROR_SUCCESS. However, it does not call the WriteRegistryToOEM function. I have successfully called the REG_FlashInitialize function and assigned the function addresses to pReadRegistryFromOEM and pWriteRegistryToOEM respectively. What caused the RegFlushKey doesn't call the WriteRegistryToOEM function? Tag: PXA255 vs. WinCE.NET 4.2 Tag: 40495

Hello,

Building a image with PXA250_DEV_PLATFORMARMV4DEBUG.
After download image to PXA255 board, I got an " access violation" error on
explorer.exe.

Do you know why have such an error?

Error message:
4294785135 PID:8389e89e TID:83c7adee 0x8389e660: Console
NOT redirected for process 0x42
4294785162 PID:8389e89e TID:83c7adee 0x8389e660: Prefetch Abort:
Thread=8389e660 Proc=82fd9678 'explorer.exe'
4294785163 PID:8389e89e TID:83c7adee 0x8389e660: AKY=00000021 PC=018c0000
RA=03e03938 BVA=018c0000 FSR=000004f0

Any commend is welcome.
JLL

Top