how to add Common drivers to platform

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - cold boot update registry touch calibration values wince 5.0 Where in the os is the registry values of calibrationData read for the touch screen? I am unable to find this. I currently save the values from the registry to a file and upon a cold boot I want to restore the values to the registry - but when or were do I need to do this at? I've tried in DdsiTouchPanelEnable but it appears this is too late (my touchscreen was not calibrated - the values were copied into the registry -I looked with remote registry editor Tag: how to add Common drivers to platform Tag: 103780
  - 2
    - Flash driver for wince 5.0 Hi, I am going to design flash driver of 128MB size for a handset. So I need to persist my data in the flash every time it's updated. My doubt is, Whether I have to use HIVE BASED REGISTRY or RAM based registry? The hive-based registry is most efficient on target devices that cold boot often but rarely or never warm boot.(this info is from platform builder). I think as a handset, it will need considerable number of warm boot also. So can you suggest a suitable registry type? My second doubt is selecting the internal file system. The available file systems are ROM only file system and RAM and ROM file system. It is mentioned in Platform builder that, the RAM and ROM file system is most useful in target devices that continuously power RAM because the object store is lost when RAM is not refreshed, and in the case of ROM only file system, it does not allow applications to place files in the object store. So can anybody suggest a suitable internal file system among this? Thanks in advance. Tag: how to add Common drivers to platform Tag: 103779
  - 3
    - USB Serial KITL (WinCE 6) - can it be done? I posted this in the microsoft.public.windowsce.embedded group, but have had no response. I thought I'd give it a try here: I've got USB Serial downloads on my platform (350 KB/sec -- much better than the 11 KB/sec of a UART). Now I'd like to get KITL working over that transport. I can select that option (USB) for Transport in Target/Connectivity Options, but I'm having a bit of difficulty getting it to work. Before I continue down this road, can anyone tell me: 1) Is KITL supported over USB Serial (not USB RNDIS, which I know will work)? 2) Is there a sample implementation of KITL over USB Serial I could look at? More detail: EBOOT can use the USB transport to download its image (selecting USB for Download in Target/Connectivity Options works just fine). When I try to use USB for KITL, I get no traffic on the USB ports after enumeration has completed. So, a few more questions: 3) What is VS2005 expect when you select USB for KITL Transport? 4) What does VS2005 need to see in order to "speak KITL" over this USB pipe? 5) Is there ANY documentation on USB (NOT RNDIS) KITL? Can anyone help? Has anyone from Microsoft tried this? Thanks! -- Steve G. Tag: how to add Common drivers to platform Tag: 103777
  - 4
    - Platform 5.0 Bug with Building SDK We are experiencing the following Microsoft Bug in Platform Builder 5.0: "BUG: You may receive an error message when you try to build the SDK after you successfully build a Windows CE 5.0 run-time image in Platform Builder 5.0" http://support.microsoft.com/kb/906459 Note: I installed all of the QFE's to date prior to any of our build attempts. I followed the bug workaround procedure and found that there aren't any Sysgen variables that are found in Anchored.txt file that are not found in the SysgenSettings.out file. The only difference is that some of the Sysgen variables are in lowercase even though they are the same variables. Does case matter, if so, what do we edit to have uniform case? We have successfully built all configurations of the operating system multiple times, however, when we attempt to build the SDK we always get the errors reported as a known Microsoft bug. Are there any other methods or procedures to bypass or solve the Microsoft Bug with regards to building an SDK in Platform 5.0? Is there another fix for this bug? Thanks. Tag: how to add Common drivers to platform Tag: 103776
  - 5
    - Incorporating a 3rd party driver into a BSP/Image I have a .CAB file which installs a WiFi card driver onto the CE device I'm developing. I've been able to extract out all the binary files, and the registry changes necessary to get the driver up and running, but I've run into a problem. I don't know how to incorporate a binary-only driver into a BSP (especially not one with several components which installs itself across subdirectories in the \Windows folder) Even worse, the word from higher-ups says I have to get rid of the CAB support since it is taking up too much space, so I have to incorporate this driver into my image at least, even if it is impossible to make it part of the BSP. Tag: how to add Common drivers to platform Tag: 103766
  - 6
    - data file compression I'm developing a project which needs to store compressed files for uploading to a central server. Some of these files can get pretty large (video), so I will need compression on my CE device. Additionally, the device must be configured to receive compressed files for updating (also very large). What types of file or folder compression/decompression will run on a CE environment? I will most likely need a dll, since this project will be essentially headless. Tag: how to add Common drivers to platform Tag: 103765
  - 7
    - Serial communication on USB 2.0 losing characters when using WaitCommEvent Hello! I'm adapting a USB 2.0 driver to work with a PXA270. When using this driver as a serial driver (usbfndrv.cpp and mdd.c) together with WaitCommEvent, I'm losing 1 character for each 2048 charter. It's working fine when WaitCommEvent is not used. It's also working OK with the internal USB device on PXA27. The reason is that the page size is 64 byte on the internal USB device, but 512 on USB 2.0 device. And the FIFO in mdd is 2048 byte. The character is tossed in the SerialEventHandler in mdd.c. Is there someone who has worked out this problem earlier? Regards Amund Tag: how to add Common drivers to platform Tag: 103750
  - 8
    - FILESYS: Waiting for bootable file system to be mounted. Hi All, I am playing with wince60 device simulator, i select "Binary Rom Image File System" as my filesystem and ROM-only File System, however, when reboot, I got "FILESYS: Waiting for bootable file system to be mounted." many many times. How can i do? Thanks Tag: how to add Common drivers to platform Tag: 103746
  - 9
    - how can I play hive-registry on WINCE6.0 device simulator? Hi ALL, Can you tell me whether or not I can play hive registry on WINCE60 divice simulator? If can, can you tell me how? Thanks a lot max Tag: how to add Common drivers to platform Tag: 103745
  - 10
    - kill build task Hi ALL, i am calling my application through makefile during build command(build -c) in WINCE . So is there any way to stop the build through my perl application? Build ->makefile->perlapps .So i want to come out from the build process after my application finished the work . Any input is welcome Thanks Chinmoy Tag: how to add Common drivers to platform Tag: 103741
  - 11
    - WINCE Hangs PXA270, PB5.0 Our product will reside in a truck. For longer duration testing, I left the system running and at some point of time it hangs. I'm not able to findout where it hangs. The same system in the test bench works fine for days. How do I findout why the WINCE hangs and where ? I wont be able to capture debug output continuosly as I cannot keep a laptop connected always. Is there any log I can take ? Any advice would be really helpful to me Thanks, Venkatesh Tag: how to add Common drivers to platform Tag: 103739
  - 12
    - EAP-TLS with windows CE Hi, I was wondering how EAP-TLS authentication is performed with windows ce 5.0. I have loaded the necessary private key and certificates (they work with other devices such as laptops) onto my device and they appear to be going to the correct stores. When I go to connect to an EAP-TLS enabled network, I get a prompt for a User Name and Domain Name. What exactly is it looking for here? The Active Directory user name that the certificate was issued to? Or the subject name as on the certificate? After entering the user name and the domain, the username dialog goes away but then authentication fails and it reappears. What are possible causes of this authentication failure? Also, is there a good description somewhere out there about how EAP-TLS works with Windows CE5.0? I'd really like to be able to troubleshoot these types of problems... Thanks, Jon Tag: how to add Common drivers to platform Tag: 103734
  - 13
    - OEMIoControl: Unsupported Code Hi, Can anyone give me some clues on how understand and trace these errors... X86Init done, OEMAddressTable = 80229be8. OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 OEMIoControl: Unsupported Code 0x10100cc - device 0x0101 func 51 OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 Thanks, Joe W. Tag: how to add Common drivers to platform Tag: 103728
  - 14
    - pm.dll / RequestPowerNotifications Hi, I have a WINCE5.0 image with full power mngmnt. An application needs to be notified of a user pressing the power button. I call RequestPowerNotifications() for this, with correct parameters. I get Error 1060 : The specified service does not exist as an installed service. After this I noticed that pm.dll does not seem to be loaded. Can this be the cause ? I cannot find ANY regfile in the entire CE source-tree that references PM.dll How is this dll supposed to be loaded ? there is a lot of docu on powermanagement, but the docu assumes it works :-( and doesn't mention any settings. Any tips are welcome... Greetings, Rob. Tag: how to add Common drivers to platform Tag: 103721
  - 15
    - how to call CPP functions from a C files? I see some ms code do it, but i don't see any special calling conversion define in source or in make files? Tag: how to add Common drivers to platform Tag: 103716
  - 16
    - Help about COM Thread Models! In my opion the STA COM server only run in one thread and the data is thread-safety , To verify my opions, I did one test. But from my test result, the two opions are not verified.I can't know what problem in this. Any help would be really appreciated! The follow is to my step to do test, include key code-section and result content: The COM Server is only to print the caller's parameter and its threadid, the code is posted follow: -------------------------------------------------- STDMETHODIMP CHello::LogTrace(SHORT Caller, SHORT Inc, DWORD Client) { FILE* fp; //szPrint is one member of CHello, it used to check whether the COM server data is thread-safety. sprintf(szPrint, "C = %d, Inc = %d, Serv = %x, Client = %x", Caller, Inc, GetCurrentThreadId(), Client); Sleep(1); fp = fopen("Test.txt", "a+"); fprintf(fp, "%s\n", szPrint); fclose(fp); return S_OK; } -------------------------------------------------- The COM Client have three steps: 1.The main thread create a server thread which build STA thread, the code is : -------------------------------------------------- DWORD WINAPI ServPorc(LPVOID lpv) { pDlgParam pParam; DWORD dwInterface; bool bContinue = true; IHello* pHello = NULL; pParam = (pDlgParam )lpv; CoInitializeEx(NULL, COINIT_APARTMENTTHREADED); CoCreateInstance(CLSID_StdGlobalInterfaceTable, NULL, CLSCTX_INPROC_SERVER, IID_IGlobalInterfaceTable, (void **)&gpGIT); CoCreateInstance(CLSID_Hello, NULL, CLSCTX_INPROC_SERVER, IID_IHello, (void **)(&pHello)); pHello->LogTrace( -1, -1, GetCurrentThreadId()); gpGIT->RegisterInterfaceInGlobal(pHello, IID_IHello, &dwInterface); PostMessage(pParam->hDlg, WM_USER + 2, 0, (LPARAM)dwInterface); MSG msg; while(GetMessage(&msg, NULL, 0, 0)) { DispatchMessage(&msg); } if (pHello) pHello->Release(); CoUninitialize(); return 0; } -------------------------------------------------- 2.After setup COM server thread, the main thread create some COM client threads. -------------------------------------------------- for (int i= 0; i< PARAL_THREAD; i++) { LogParam[i].ICookie = dwCookie; LogParam[i].Child = i; hTestServer[i] = CreateThread(NULL, 0, LogPorc, &LogParam[i], NULL, &dwTestHandle[i]); } -------------------------------------------------- 3.The child thread call the pHello->LogTrace. DWORD WINAPI LogPorc(LPVOID lpv) { pLogChild pParam; IHello* pHello = NULL; HRESULT hr; pParam = (pLogChild) lpv; gpGIT->GetInterfaceFromGlobal(pParam->ICookie, IID_IHello, reinterpret_cast< void** >( &pHello )); for (int i = 0; i < 20; i++) { pHello->LogTrace(pParam->Child, i, GetCurrentThreadId()); Sleep(1); } pHello->Release(); return 0; } The section of test.txt file is : .... C = 0, Inc = 0, Serv = 61b000e, Client = 61b000e C = 0, Inc = 1, Serv = 61b000e, Client = 61b000e C = 2, Inc = 0, Serv = 620000e, Client = 620000e C = 1, Inc = 1, Serv = 61e000e, Client = 61e000e C = 0, Inc = 2, Serv = 61b000e, Client = 61b000e C = 2, Inc = 1, Serv = 620000e, Client = 620000e C = 1, Inc = 2, Serv = 61e000e, Client = 61e000e C = 1, Inc = 2, Serv = 61e000e, Client = 61e000e C = 0, Inc = 3, Serv = 61b000e, Client = 61b000e C = 2, Inc = 2, Serv = 620000e, Client = 620000e C = 1, Inc = 3, Serv = 61e000e, Client = 61e000e C = 1, Inc = 3, Serv = 61e000e, Client = 61e000e C = 1, Inc = 3, Serv = 61e000e, Client = 61e000e .... The serv fields have three threadids, and these have some repeated lines. Tag: how to add Common drivers to platform Tag: 103715
  - 17
    - Wave Driver registry settings Hi, I am trying to build a wave driver based on the Unified Audio model. For this I created a normal stream interface driver with all WAV_xxx functions required. The registry entry for the driver was done under HKEY_LOCAL_MACHINE\Drivers\Builtin\FILTER When I try to call the wave api "waveOutGetNumDevs" the 0 is returned. Also the waveOutOpen return "NO DRIVER" found. What i fail to understand is that how do the wave api know which are the audio drivers available. Under what registry settings should the audio driver be put? Thanks in advance Mohammed Anwar Tag: how to add Common drivers to platform Tag: 103714
  - 18
    - FATFS CacheSize - is it "overridden" by profiles, or ... ? Hello all, How does the CacheSize setting for FATFS interract between the base setting and the profiles? You can set the cache size for FATFS by setting the registry value [HKEY_LOCAL_MACHINE\System\StorageManager\FATFS] "CacheSize"=dword:1000 like the other FATFS parameters, you can supposedly override this with a value under the profile, e.g. [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\ramd\FATFS] "CacheSize"=dword:1000 But what does override mean here? Does it mean that FATFS allocates a separate cache of that size for the profile (ramd here), in addition to it's base cache? Does it use the larger or smaller of all the profiles for a single cache? Or is the base setting really just a default, and every mounted FAT filesystem gets a separate cache that big? Thanks Aaron Tag: how to add Common drivers to platform Tag: 103712
  - 19
    - Problem building debug version of a driver (LNK4204) Hi! Trying to build a debug version of a driver under eVC gives the warning "LNK4204: 'ccrthelp.pdb' is missing debugging information for referencing module; linking object as if no debug info". The driver DLL is build, but during a debug session the debugger jumps raher randomly through the source code. The PDB in question is from a Platform Builder directory (\PUBLIC\COMMON\OAK\LIB\ARMV4I\DEBUG). Any suggestions? Regards Max Tag: how to add Common drivers to platform Tag: 103709
  - 20
    - CE5 ASP - strange error message on Response.Flush Hello all, Is John Spaith out there ? :) In one of my ASP pages, I'm trying to use Response.Flush. Elsewhere, it has seemed to work OK, but here my script just stops with this message: ------------------------------ Buffering must be turned on to complete that action ASP scripting compilation error: '80020009' Description: In file: /Journal.asp On line: 54 ------------------------------ Even this simple test case now fails: <%@ language="VBScript" %> <% Response.Write "cake<br>" Response.Flush %> Any ideas? Regards Aaron Tag: how to add Common drivers to platform Tag: 103708
  - 21
    - NAND flash fmd dirver performance Dear all, I'm developing nand flash fmd driver using FAL library. I printf the 'dwNumSectors' parameter in function FMD_ReadSector(...) and find it is still 1 . So, FAL only read 1 sector one time? and if so, the performace is not good, any one can give me some idea? thanks. Tag: how to add Common drivers to platform Tag: 103707
  - 22
    - Unidentifed USB Device I have a HID-compliant USB device and I have written a custom driver for it. (And removed usbhid (SYSGEN_USB_HID) from the catalog for testing purposes). The driver is loaded correctly if I plug the device in AFTER startup. But ... if the device is already plugged in at startup, I get the Unidentifed USB Device dialog. If I cancel the dialog, unplug the device and plug it back in, the driver loads OK. Or if I just enter the driver name in the dialog, it loads OK. (With SYSGEN_USB_HID included, it is recognized at startup by the default HID settings). I have tried adding all sorts of registry entries under USB\LoadClients and other keys, using Vendor ID, VendorID_ProductID, Default or whatever, without success. What is different about the bootup procedure from that when I plug the device in? Tag: how to add Common drivers to platform Tag: 103700
  - 23
    - DLL test tool Hi ALL , I am trying to make a tool which will test the all DLL and EXEs are present are not in the platfrom target tree. So i am caling my perl application tool through makefile from my own created directory in platfrom tree with modify the dirs file and this test tools is checking all DLLS and EXEs.I am comparing with my platfrom.bib file and if i not found any DLL or my required EXE which will be used in my makeimg ,so soon i want come out from build .SO i dont know how to stop the microsoft build program through perl script and program should terminate gracefully also? Any ideas are welcome to open my locked door. Thanks Chinmoy Tag: how to add Common drivers to platform Tag: 103699
  - 24
    - Subtle bug in MIPS assembler - missing definition ignored Here is a potentially nasty behavior in at least the Windows CE MIPS assembler. It may be present on other as architectures as well. The following code is compilable: #include <kxmips.h> #define PATRICK_STARFISH 0x12340000 LEAF_ENTRY(this_is_bogus) lw t0, SPONGEBOB_SQUAREPANTS(PATRICK_STARFISH) ... even though there is _no_ definition for SPONGEBOB_SQUAREPANTS! The assembled code generated reads: Proc: this_is_bogus lw t0, SPONGEBOB_SQUAREPANTS(PATRICK_STARFISH) 0000000000 0x3c011234 lui at,0x1234 0x00000004 0x24210000 addiu at,at,0 0x00000008 0x8c280000 lw t0,0(at) ... in other words, SOMETHING(defined_symbol) is evaluated as if SOMETHING had an empty definition (as opposed to being undefined). The assembler correctly handles the case where the macro includes a literal instead of a symbol. Building the code: lw t0, SPONGEBOB_SQUAREPANTS(0x12340000) fails, with an error: unresolved external symbol SPONGEBOB_SQUAREPANTS referenced in function this_is_bogus -- --Richard R Lee, eMVP Tag: how to add Common drivers to platform Tag: 103698
  - 25
    - paired/unpaired Flash components and FMD Hi, I am facing a problem with the FMD located in: WINCE500\PUBLIC\COMMON\OAK\DRIVERS\BLOCK\MSFLASHFMD\FASL After creating my local copy of it, I got it working in one of our devices using NOR Flash (Spansion) with 2 paired chips. Also my Booloader is using the PQOAL flash library. I used it to flash the NK.bin and it works fine. Now I am using a non-paired architecture (only one 16-bit Flash chip). I thought that setting the bPairedFlash variable to FALSE should be enough, but it is not working, while the bootloader still works without problems. After some debugging, I found that the driver fails in the following line: pStorageDesc->pFlashDevDesc->stDeviceID.u32MfgID = RD_FLASH_REG (lpvBaseVirtualAddr, CYCLE_4_ADDR_MFG_ID) ; That is, it cannnot get a correct manufacturer ID. As the Flash manufacturer is the same for both devices and the bootloader is working, I am thinking that some is wrong with the WR_FLASH_REG/ RD_FLASH_REG macros in the driver for unpaired chips (or that I'm getting some alignment problems with the virtual address mapping [MmMapIoSpace]). Has anybody find the same situation? Thanks for your feedback, Alex Tag: how to add Common drivers to platform Tag: 103690
- Next
  - 1
    - How to disable ActiveSync from monitoring serial lines? I have a strange situation. I have a PXA255 dev board and I use the processors USB client for ActiveSync. I also have a serial modem port that I use for remote communication. When I click the Modem off, I get a brief "USB status" connect system status screen that pops up. At first I thought the USB +D line must be glitching and briefly triggering a USB "attach". I eliminated this as a posibility by disabling the "USB Client" subsystem on the Xscale chip. and via hardware. I narrowed it down to the "CD" (carrier detct) signal glitching which must result in CE poping up the status screen as it must not discern a USB vs a serial port ActiveSync attach. This screen is very annoying and I can not ship product with this. I could totally remove the ActiveSync component but I don't want to give up the functionality. Is there a way to prevent ActiveSync from monitoring the serial ports (and just monitor the USB client connection)? I believe you can do this on the desktop side of ActiveSync, is this available in CE somehow?. Tag: how to add Common drivers to platform Tag: 103687
  - 2
    - cloning driver Dear all, I wanted to clone USB driver, i am getting the following error BUILD: [01:0000000467:ERRORE] LINK : fatal error LNK1104: cannot open file 'E:\WINCE500\PBWorkspaces\XXXXX\WINCE500\XXXXX\oak\lib\x86\retail\hcdlib.lib' What settings as to be changed to rectify this error? Below is the sources file TARGETTYPE=LIBRARY TARGETNAME=hcdlib CONDITIONAL_INCLUDES=macwin32.h SOURCELIBS= \ $(_TARGETPLATROOT)\lib\hcdlib.lib \ TARGETLIBS= \ $(_TARGETPLATROOT)\lib\hcdlib.lib \ SOURCES= \ cphysmem.cpp \ sync.cpp \ cdevice.cpp \ hcd.cpp \ hcddrv.cpp \ Regards, Sankarraj Tag: how to add Common drivers to platform Tag: 103685
  - 3
    - keyword __interface in PB30 Hello, I need to compile a project in Platform Builder (3.0). The PB30 online help says, that the keyword __interface is supported but the keyword interface needs a 'pragma keyword("interface", on)'. But compiling this code in a .CPP file gets an error: #include <windows.h> __interface foo { void bar() = 0; }; error C2146: syntax error : missing ';' before identifier 'foo' The same occures when I use 'interface' instead of '__interface'. Is there any command line argument that enables the support of __interface, or do I really need the ugly for with the virtual keyword at each methdod? class foo { virtual void bar() = 0; }; /Helge -- Time is an ocean but it ends at the shore Tag: how to add Common drivers to platform Tag: 103680
  - 4
    - IR Hi, I am working on FIR driver for Windows mobile. When I run the IRPort tests I am getting a debug message "SKIPPED: Unable to establish connection to IRTestServer" AND ALL THE TEST CASES WHICH REQUIRE CONNECTION TO IRServer are getting skipped. This is happening eventhough I am using another board to run irapisrvxx. One more thing is when I try to stop obexsrv it is not happening and I get a message that unable to stop obexsrv. If anybody has faced this issue and know why this is happening, Please help me. Regards, Raman Tag: how to add Common drivers to platform Tag: 103676
  - 5
    - Filesystem filter ENCFILT fail load Hi all, I'm testing the ENCFILT sample on Windows Mobile 6 Emulator. I change the name to myfilter.dll. I build it in PB and deploy on WM6 Emulator added filesystem filter registry for Storage Card. When I try to attac the storage card (by setting storage location in emulator), followin message shown in debug console: CertVerify: myfilter.dll trust = 2 I can't see other functions of the filter being called when I try t access the storage card, even DllMain (I added debug msg in DllMain). I tried the same things with fsdspy.dll and everything works find (ca see the DllMain function called) so I think it's shouldn't be registr problem. Do I missed something with the ENCFILT sample? Thanks a lot!!! Just Tag: how to add Common drivers to platform Tag: 103674
  - 6
    - How to load bluetooth driver manually ? Dear all: I want to active my bluetooth driver manually when I need it, other time I will shutdown it. how to do it? Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\AFD.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\PPP.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\TCPSTK.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\DHCP.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\NETBIOS.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\WS2.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\IPHLPAPI.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\WINSOCK.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\AUTORAS.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\IRDASTK.DLL' Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\BTHUNIV.DLL' ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\BTD.DLL' ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Loaded symbols for 'D:\WINCE500\PBWORKSPACES\S1\RELDIR\STORM_ARMV4I_RELEASE\BTHBCSP.DLL' ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` Tag: how to add Common drivers to platform Tag: 103670
  - 7
    - wehre is performance monitor in VS.NET 2005 Hi, I have isntalled VS.NET 2005 and Microsfot Remote Tools Framework 1.0. I am looking for a tool I used in WinCE 5.0 and it is called "Performance Monitor" but it seems does not shipped with VS.NET. I only have: registry editor, file viewer, process viwer, and so on... and all of them work perfect using Remote tools framework 1.0, Activesync connection works OK and remote tol is launched OK in my WinCE 6.0 device... but... I want to use remote tool... does anybody how can I get that tool and use it with "Remote Tools Framework 1.0" Thanks advanced. Tag: how to add Common drivers to platform Tag: 103662
  - 8
    - Re: whether license dialog box show while using Windows CE 5.0. I have done some test by changing the date , Nothing happened! "tony" wrote :... > We use evaluation PB5 ,and we have deployed the runtime OS image on my > device. Of course we have bought the runtime license for every device. > My question is whether any license dialog box will show while customers > using the device. > Thanks for any answer! > Tag: how to add Common drivers to platform Tag: 103661
  - 9
    - WinCE6.0 - MSFlash for Strata P30 Hi, everyone. I have a problem need to solve. So i did search already in this newsgroup about similar topics. But there is no answer i need. Now i try to post again expect good answer. Please give your concern about my question. I'm now working to use MSFlash driver in Windows Embedded CE 6.0 on my PXA270 processor based platform. my platform has Intel Stata Flash P30B product. (64MB) So that i modified the driver to add a code to unlock at initializing step. because P30 have a volatile lock machanism. I think that there is no needs to modify the driver except applying the code to unlock. First of all, do you think that my think is right? if my think is wrong then what shall i do more? Next question is about applying the 'RAM & ROM file system' with 'RAM-based Registry' in Windows Embedded CE 6.0. I want to set RAM file system(Object Store) as Root file system and to set External file system as sub directory in root. external file system is FAT or exFAT file system with FMD(MSFlash). Actually i had used same way in early version of CE. (4.2 and 5.0) but i think that there is something change about registry setting or anything maybe i don't know in 6.0. I think that i did everything already as posible as i can. but still not work. do you know how to set the registry for my expect? Currently, i can't see the folder defined in registry for MSFlash in root directory. but i can see the storage manager in control panerl with MSFlash attached. so i can do format and scan but i can't mount. There is message 'Unable to mount partition' when is press the mount button. Please help to solve it. Regards FreeJack Tag: how to add Common drivers to platform Tag: 103660
  - 10
    - Storage Folder not coming in WinCE 6.0 fro RAMDISK I have complied the RAMDISK driver in PB 6.0 and trying to run it in PB 6.0 in ARM Emulator. The driver is loading but Storage Folder is not coming in the root or Storage Manager. Registery settings that I am using are: [HKEY_LOCAL_MACHINE\Drivers\Builtin\RamDisk] "Profile"="RamDisk" "IClass"="{A4E7EDDA-E575-4252-9D68-4195D48BB865}" "Ioctl"=dword:4 "Order"=dword:40 "FriendlyName"="Windows CE Ramdisk Driver" "Dll"="RAMDISK.dll" "Prefix"="DSK" "FSD"="exfat.dll" [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\RamDisk] "MountFlags"=dword:0 "AutoFormat"=dword:1 "AutoPart"=dword:1 "AutoMount"=dword:1 "Folder"="StorageCardTemp" "Name"="RAM Disk Block Device" "PartitionDriver"="mspart.dll" "DefaultFileSystem"="EXFAT" As the FAT has been changed to EXFAT in WinCE 6.0. Is there any additional registry settings required above. What are correct registries in WinE 6.0 fro a block driver? I have taken these registries from my working block driver in wince 5.0. How can I know what WinCE 6.0 expects from my block driver/my driver profile registry to make my diver properly running and showing Storage Folder. It is not clear from WinCE docs. Tag: how to add Common drivers to platform Tag: 103659
  - 11
    - Configuring Object Store Memory Hi all, I am trying to modify division between program memory and storage memory when my WinCE 6.0 image is running. In this link explain this can be done using "SetSystemMemoryDivision()". http://msdn2.microsoft.com/en-US/library/aa917785.aspx I click on SetSystemMemoryDivision ( http://msdn2.microsoft.com/en-US/library/aa908756.aspx ) and I found this function is deprecated and not should be used. Could anyone give me some info about what is the correct way to do this (using command line application when OS is running) without using this deprecated function, because I suppouse that this function will disappear? Thanks advanced. Tag: how to add Common drivers to platform Tag: 103657
  - 12
    - What OSDesign files need to be archived (CE 6)?? I am trying to archive just my source OSDesign files. Not the generated output. There are several files under \WINCE600\OSDesign\<myosdesign>\<myosdesign>\wince600\<myosdesign>_ARM4I namely: __CEBASE_FEATURES.txt PBInitEnv.bat SysgenSettings.out I know the SysgenSettings.out does not have to be archived as it is generated upon a sysgen build. I do not know about the others ??? How and what are they used for?? Do they need to be archived? Tag: how to add Common drivers to platform Tag: 103652
  - 13
    - Why Write perf of FAT32 is very poor then FAT16 on SD cards for Wi Hi MSFT folks, This has been observed on WinCE OS. I have different brands of SD cards like Sandisk, Transcend and Kingston. I have run the SPB benhmark tool to measure the Read and Write performance figures on differnt devices. The Write speed on FAT32 was very very poor compared to FAT16 formatted cards. Can anybody help me to know this? And is there any way to improve the write performance on FAT32? like any registry settings... Thanks and Regards, Sachin Nikam. Pune. Tag: how to add Common drivers to platform Tag: 103651
  - 14
    - whether license dialog box show while using Windows CE 5.0. We use evaluation PB5 ,and we have deployed the runtime OS image on my device. Of course we have bought the runtime license for every device. My question is whether any license dialog box will show while customers using the device. Thanks for any answer! Tag: how to add Common drivers to platform Tag: 103650
  - 15
    - June QFE broke my USB mass storage devices I am using a PXA255 and a Oxford USB host controler and their CE 5.0 driver. All worked fine mounting SanDisk USB drives (mass storage device). After installing June's QFE, drives no longer mount or work at all. Has anyone else had problems with June's QFE? Tag: how to add Common drivers to platform Tag: 103649
  - 16
    - WinCE 5.0 and Vista Is Platform Builder 5.0 supported on Vista? Tag: how to add Common drivers to platform Tag: 103644
  - 17
    - KITL Ethernet driver doesn't support interrupt sharing I haven't been able to get the Platform Builder Download to work and the lack of interrupt sharing seems to be the issue. Does anyone have experience/comments about this? I seem to be stuck since my BIOS assigns all the devices to just two interrupts. Tag: how to add Common drivers to platform Tag: 103639
  - 18
    - PXA255 WinCE 5.0 FMD_EraseBlock Why is my StrataFlash always locked when trying to do FMD_EraseBlock? I thought FAL handled IOCTL_FMD_UNLOCK_BLOCKS before an erase. /trond Tag: how to add Common drivers to platform Tag: 103634
  - 19
    - cd rw driver for ce? hi, everyone? I'm finding whether there is a cd rw driver for windows ce 5.0 or 6.0. Is there any driver for it? Anybody know? Tag: how to add Common drivers to platform Tag: 103626
  - 20
    - Atapi mounting problem... Hi, AMD turion 64, RS690T NB, SB600 SB. OS : Windows CE 5.0 I added atapi to mount the HDD, but its not mounting in storage manager itself it showwing IDE Hard Drive. Here are the debug messages. I added atapi driver and all the supports. Debug msgs for atapi : ---------------------- Warning: No Match template is found for following PCI Device 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Bus/Device/Function = 0/24/3, Host / PCI Bridge 0x83fd1b30: VendorID = 0x1022, DeviceID = 0x1103, Command = 0x0000, Status = 0x0010 0x83fd1b30: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06 0x83fd1b30: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fd1b30: BaseAddresses: 0x83fd1b30: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fd1b30: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fd1b30: ROMBaseAddress = 0x00000000 0x83fd1b30: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 6, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 1, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 7, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 20, Function 2 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 1 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 2 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 3 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 4 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 5 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: IoBase = 0xD000, IoLimit = 0xDFFF 0x83fd1b30: IoBase reg = 0x0, offset 0x30 0x83fd1b30: IoBase = 0xE000, IoLimit = 0xEFFF 0x83fd1b30: IoBase reg = 0x0, offset 0x30 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 20, Function 0 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(1) 0x83fd1b30: ATAPI DLL_PROCESS_DETACH 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1) returned open exist.continue search 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1) returned open exist.continue search 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE2) returned open exist.continue search 0x83fd1b30: ATAPI DLL_PROCESS_ATTACH 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(2) 0x83fd1b30: ATAPI:PCIConfig!ConfigSize+(Bus 0, Device 18, Function 0) 0x83fd1b30: ATAPI:PCIConfig!ConfigSize- 0x83fd1b30: ATAPI DLL_PROCESS_DETACH 0x83fd1b30: ATAPI DLL_PROCESS_ATTACH 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(3) 0x83fd1b30: ATAPI DLL_PROCESS_DETACH 0x83fd1b30: ATAPI DLL_PROCESS_ATTACH 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(2) 0x83fd1b30: ATAPI:PCIConfig!ConfigSize+(Bus 0, Device 20, Function 1) 0x83fd1b30: ATAPI:PCIConfig!ConfigSize- 0x83fd1b30: ATAPI DLL_PROCESS_DETACH 0x83fd1b30: ATAPI DLL_PROCESS_ATTACH 0x83fd1b30: ATAPI:PCIConfig!DeviceConfig+(3) 0x83fd1b30: ATAPI DLL_PROCESS_DETACH 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\ALI14531) returned open exist.continue search 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1) returned open exist.continue search 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE2) returned open exist.continue search 0x83fd1b30: PCIBUS::OpenNonExistInstanceKey(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE3) returned open exist.continue search 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14532\BusPrefix) returned 2 0x83fd1b30: ATAPI DLL_PROCESS_ATTACH 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\4294967292 0x83fd1b30: Hnd = 000310A0 0x83fd1b30: Name = IDE1: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14532 0x83fd1b30: BusParent = 0003F610 0x83fd1b30: InterfaceType = 00000005 0x83fd1b30: BusName = PCI_0_20_1 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14532 0x83fd1b30: IoLen : 0x83fd1b30: 8 0x83fd1b30: 4 0x83fd1b30: 8 0x83fd1b30: 4 0x83fd1b30: 10 0x83fd1b30: IoBase : 0x83fd1b30: a030 0x83fd1b30: a048 0x83fd1b30: a038 0x83fd1b30: a04c 0x83fd1b30: a010 0x83fd1b30: FunctionNumber = 00000001 0x83fd1b30: DeviceNumber = 00000014 0x83fd1b30: BusNumber = 00000000 0x83fd1b30: InterfaceType = 00000005 0x83fd1b30: SubSystemID = 0000438C 0x83fd1b30: SubVendorID = 00001002 0x83fd1b30: RevisionID = 00000000 0x83fd1b30: DeviceID = 0000438C 0x83fd1b30: VendorID = 00001002 0x83fd1b30: ProgIF = 0000008A 0x83fd1b30: RegisterStride = 00000001 0x83fd1b30: StatusPollCyclePause = 00000005 0x83fd1b30: StatusPollsPerCycle = 00000020 0x83fd1b30: StatusPollCycles = 00000100 0x83fd1b30: SoftResetTimeout = 00000003 0x83fd1b30: DMAAlignment = 00000004 0x83fd1b30: SysIntr = 00000000 0x83fd1b30: Irq = 0000000E 0x83fd1b30: Legacy = 00000001 0x83fd1b30: ConfigEntry = GenericConfig 0x83fd1b30: SubClass = 00000001 0x83fd1b30: Class = 00000001 0x83fd1b30: Order = 00000002 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = IDE 0x83fd1b30: IClass : 0x83fd1b30: {CDDC3621-3512-4b3f-BB6F-B4DD5E061795} 0x83fd1b30: SpawnFunction = CreatePCIHDCD 0x83fd1b30: InstanceIndex = 00000002 0x83fd1b30: Atapi!IDE_Init> Start of IDE/ATA device enumeration 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device3 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device2 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device1 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device0 0x83fd1b30: Atapi!IDE_Init> End of IDE/ATA device enumeration 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device0 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14532\Device0\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\4294967293 0x83fd1b30: Hnd = 0003EF60 0x83fd1b30: Name = DSK1: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14532\Device0 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14532\Device0 0x83fd1b30: Port = 00034730 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: DeviceId = 00000000 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(1) 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 3 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 2 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 1 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Timeout 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(0) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x0003ef60 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0x602d030 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device1 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14532\Device1\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\4294967294 0x83fd1b30: Hnd = 000431C0 0x83fd1b30: Name = DSK1: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14532\Device1 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14532\Device1 0x83fd1b30: Port = 00034730 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: DeviceId = 00000001 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(1) 0x83fd1b30: Atapi!CDisk::IsDevicePresent> Device 1 is not present; Error register(0xff) 0x83fd1b30: Atapi!CDisk::InitController> Device did not respond to identify 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(0) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x000431c0 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0x602d030 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device2 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14532\Device2\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\00 0x83fd1b30: Hnd = 00043430 0x83fd1b30: Name = DSK1: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14532\Device2 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14532\Device2 0x83fd1b30: Port = 000347A0 0x83fd1b30: DeviceId = 00000000 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(1) 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 3 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 2 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 1 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Timeout 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(0) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x00043430 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0x602d030 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14532\Device3 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14532\Device3\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\01 0x83fd1b30: Hnd = 000436A0 0x83fd1b30: Name = DSK1: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14532\Device3 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14532\Device3 0x83fd1b30: Port = 000347A0 0x83fd1b30: DeviceId = 00000001 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(1) 0x83fd1b30: Atapi!CDisk::IsDevicePresent> Device 1 is not present; Error register(0xff) 0x83fd1b30: Atapi!CDisk::InitController> Device did not respond to identify 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(0) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x000436a0 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0x602d030 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\02 0x83fd1b30: Hnd = 00042FD0 0x83fd1b30: Name = IDE2: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14531 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD IDE1: 0x83fd1b30: BusParent = 0003F610 0x83fd1b30: InterfaceType = 00000005 0x83fd1b30: BusName = PCI_0_18_0 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14531 0x83fd1b30: SysIntr = 00000010 0x83fd1b30: Irq = 0000000B 0x83fd1b30: IoLen : 0x83fd1b30: 8 0x83fd1b30: 4 0x83fd1b30: 8 0x83fd1b30: 4 0x83fd1b30: 10 0x83fd1b30: IoBase : 0x83fd1b30: a020 0x83fd1b30: a040 0x83fd1b30: a028 0x83fd1b30: a044 0x83fd1b30: a000 0x83fd1b30: MemLen = 00000400 0x83fd1b30: MemBase = 80000000 0x83fd1b30: FunctionNumber = 00000000 0x83fd1b30: DeviceNumber = 00000012 0x83fd1b30: BusNumber = 00000000 0x83fd1b30: InterfaceType = 00000005 0x83fd1b30: SubSystemID = 00004380 0x83fd1b30: SubVendorID = 00001002 0x83fd1b30: RevisionID = 00000000 0x83fd1b30: DeviceID = 00004380 0x83fd1b30: VendorID = 00001002 0x83fd1b30: ProgIF = 0000008F 0x83fd1b30: RegisterStride = 00000001 0x83fd1b30: StatusPollCyclePause = 00000005 0x83fd1b30: StatusPollsPerCycle = 00000020 0x83fd1b30: StatusPollCycles = 00000100 0x83fd1b30: SoftResetTimeout = 00000003 0x83fd1b30: DMAAlignment = 00000004 0x83fd1b30: Legacy = 00000001 0x83fd1b30: ConfigEntry = GenericConfig 0x83fd1b30: SubClass = 00000001 0x83fd1b30: Class = 00000001 0x83fd1b30: Order = 00000002 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = IDE 0x83fd1b30: IClass : 0x83fd1b30: {CDDC3621-3512-4b3f-BB6F-B4DD5E061795} 0x83fd1b30: SpawnFunction = CreatePCIHDCD 0x83fd1b30: InstanceIndex = 00000001 0x83fd1b30: Atapi!IDE_Init> Start of IDE/ATA device enumeration 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device3 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device2 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device1 0x83fd1b30: Atapi!IDE_Init> Enumerated IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device0 0x83fd1b30: Atapi!IDE_Init> End of IDE/ATA device enumeration 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device0 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device0\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\03 0x83fd1b30: Hnd = 000438C0 0x83fd1b30: Name = DSK1: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14531\Device0 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14531\Device0 0x83fd1b30: Port = 000431F0 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: DeviceId = 00000000 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(1) 0x83fd1b30: Atapi!CDisk::ResetController> Device is busy; 3 seconds remaining 0x83fd1b30: Atapi!CDisk::ResetController> Device is ready 0x83fd1b30: Atapi!CDisk::IsDevicePresent> Device 0 is present 0x83fd1b30: Atapi!CDisk::SendExecuteDeviceDiagnostic> Device 0 passed, Device 1 passed or not present 0x83fd1b30: Atapi!CDisk::SendExecuteDeviceDiagnostic> ATA device 0x83fd1b30: Atapi!DumpIdentify> ... 0x83fd1b30: 5a c ff 3f 37 c8 10 0 0 0 0 0 3f 0 0 0 Z..?7.......?... 0x83fd1b30: 0 0 0 0 20 20 20 20 20 20 20 20 20 20 20 20 .... 0x83fd1b30: 4c 35 35 52 32 33 58 37 0 0 0 10 4 0 2e 33 L55R23X7.......3 0x83fd1b30: 41 41 20 48 20 20 54 53 38 33 32 30 31 31 41 30 AA H TS832011A0 0x83fd1b30: 20 53 20 20 20 20 20 20 20 20 20 20 20 20 20 20 S 0x83fd1b30: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 10 80 .. 0x83fd1b30: 0 0 0 2f 0 40 0 2 0 2 7 0 ff 3f 10 0 .../.@.......?.. 0x83fd1b30: 3f 0 10 fc fb 0 10 1 b0 f8 50 9 0 0 7 0 ?.........P..... 0x83fd1b30: 3 0 78 0 78 0 f0 0 78 0 0 0 0 0 0 0 ..x.x...x....... 0x83fd1b30: 0 0 0 0 0 0 1f 0 6 5 0 0 40 0 40 0 ............@.@. 0x83fd1b30: fe 0 0 0 6b 34 1 7d 23 40 69 34 1 3c 23 40 ....k4.}#@i4.<#@ 0x83fd1b30: 7f 40 0 0 0 0 fe fe fe ff 0 0 0 fe 0 0 .@.............. 0x83fd1b30: 0 0 0 0 0 0 0 0 b0 f8 50 9 0 0 0 0 ..........P..... 0x83fd1b30: 0 0 0 0 0 40 0 0 0 0 0 0 0 0 0 0 .....@.......... 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 9 0 b0 f8 50 9 b0 f8 50 9 20 20 2 0 b6 2 ....P...P. .... 0x83fd1b30: 2 80 8a 0 6 3c a 3c 0 0 c6 7 0 1 0 8 .....<.<........ 0x83fd1b30: 12 13 0 5 2 0 80 0 0 0 0 0 a0 0 2 2 ................ 0x83fd1b30: 0 0 4 4 0 0 0 0 0 0 0 0 0 c b 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ................ 0x83fd1b30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 a5 c7 ................ 0x83fd1b30: rotational speed tolerance is > 0,5 0x83fd1b30: disk transfer rate > 10Mbs 0x83fd1b30: fixed drive 0x83fd1b30: head switch time > 15us 0x83fd1b30: not MFM encoded 0x83fd1b30: hard sectored 0x83fd1b30: number of cylinders : 16383 0x83fd1b30: number of heads : 16 0x83fd1b30: unformatted bytes per track : 0 0x83fd1b30: unformatted bytes per sector : 0 0x83fd1b30: sectors per track : 63 0x83fd1b30: buffer type : unspecified 0x83fd1b30: buffer size : 4096 sectors 0x83fd1b30: read/write multiple : supported, 16 sectors/interrupt 0x83fd1b30: double word IO : not supported 0x83fd1b30: LBA mode : supported 0x83fd1b30: DMA : supported 0x83fd1b30: PIO cycle timing mode : 2 0x83fd1b30: DMA cycle timing mode : 2 0x83fd1b30: current size fields valid : yes 0x83fd1b30: current number of cylinders : 16383 0x83fd1b30: current number of heads : 16 0x83fd1b30: current number of sectors/track : 63 0x83fd1b30: current sector capacity : 16514064 0x83fd1b30: sectors/interrupt with read/write multiple : 16 0x83fd1b30: multi sector setting : valid 0x83fd1b30: total user addressable sectors : 156301488 0x83fd1b30: single word DMA modes supported : 0 0x83fd1b30: single word transfer mode active : 0 0x83fd1b30: multi word DMA modes supported : 7 0x83fd1b30: multi word transfer mode active : 0 0x83fd1b30: Atapi!DumpSupportedTransferModes> Supported transfer mode summary: 0x83fd1b30: IORDY supported 0x83fd1b30: minimum multiword DMA transfer cycle time per word (ns) = 120 0x83fd1b30: manufacturer's recommended multi word DMA transfer cycle time (ns) = 120 0x83fd1b30: minimum PIO transfer cycle time w/o flow control (ns) = 240 0x83fd1b30: minimum PIO transfer cycle time w/ IORDY flow control (ns) = 120 0x83fd1b30: PIO mode 0 supported 0x83fd1b30: PIO mode 1 supported 0x83fd1b30: multi word DMA mode 2 and below is supported 0x83fd1b30: ultra DMA mode 5 and below is supported 0x83fd1b30: look-ahead supported 0x83fd1b30: write cache supported 0x83fd1b30: S.M.A.R.T. feature set supported 0x83fd1b30: Atapi!CDisk::Identify> Assuming direct-access device (hard disk drive) 0x83fd1b30: Atapi!CDisk::Identify::ConfigLBA48> Device supports 48-bit LBA 0x83fd1b30: Atapi!CDisk::Identify::ConfigLBA48> Max LBA Address = 0x000000000950f8b00x83fd1b30: Atapi!CDisk::InitController> Device responded to identify 0x83fd1b30: Atapi!CDisk::Init> Enabled write cache 0x83fd1b30: Atapi!CDisk::Init> Enabled read look-ahead 0x83fd1b30: Atapi!DSK_Init> Initialized PRIMARY MASTER on Drivers\BuiltIn\PCI\Instance\ALI14531\Device0 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device1 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD DSK1: 0x83fce9ac: Loading partition driver mspart.dll hModule=83EB40A8 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device1\BusPrefix) returned 2 0x83fce9ac: Driver mspart.dll loaded 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\04 0x83fd1b30: Hnd = 00044430 0x83fd1b30: Name = DSK2: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14531\Device1 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14531\Device1 0x83fd1b30: Port = 000431F0 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: DeviceId = 00000001 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(2) 0x83fd1b30: Atapi!CDisk::IsDevicePresent> Device 1 is not present; Error register(0x0) 0x83fd1b30: Atapi!CDisk::InitController> Device did not respond to identify 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(1) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x00044430 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 2, dll atapi.dll, context 0x602d030 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device2 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device2\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\05 0x83fd1b30: Hnd = 000446A0 0x83fd1b30: Name = DSK2: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14531\Device2 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14531\Device2 0x83fd1b30: Port = 00043260 0x83fd1b30: DeviceId = 00000000 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(2) 0x83fd1b30: Atapi!CDisk::ResetController> Device is ready 0x83fd1b30: Atapi!CDisk::ResetController> SRST failed 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(1) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x000446a0 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 2, dll atapi.dll, context 0x602d030 0x83fd1b30: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\ALI14531\Device3 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device3\BusPrefix) returned 2 0x83fd1b30: Atapi!DumpRegKey> Drivers\Active\06 0x83fd1b30: Hnd = 00044910 0x83fd1b30: Name = DSK2: 0x83fd1b30: Key = Drivers\BuiltIn\PCI\Instance\ALI14531\Device3 0x83fd1b30: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\ALI14531\Device3 0x83fd1b30: Port = 00043260 0x83fd1b30: DeviceId = 00000001 0x83fd1b30: TransferMode = 000000FF 0x83fd1b30: LookAhead = 00000001 0x83fd1b30: WriteCache = 00000001 0x83fd1b30: DrqDataBlockSize = 00000200 0x83fd1b30: DoubleBufferSize = 00010000 0x83fd1b30: DMA = 00000002 0x83fd1b30: InterruptDriven = 00000001 0x83fd1b30: Dll = atapi.dll 0x83fd1b30: Prefix = DSK 0x83fd1b30: IClass : 0x83fd1b30: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83fd1b30: Atapi!CPCIDisk::CPCIDisk> device count(2) 0x83fd1b30: Atapi!CDisk::IsDevicePresent> Device 1 is not present; Error register(0x7f) 0x83fd1b30: Atapi!CDisk::InitController> Device did not respond to identify 0x83fd1b30: Atapi!CDisk::Init> Failed to initialize device 0x83fd1b30: Atapi!CPCIDisk::~CPCIDisk> device count(1) 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x00044910 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 2, dll atapi.dll, context 0x602d030 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE4\DllName) returned 2 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD IDE2: 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE4' 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE3\DllName) returned 2 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE3' 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE2\DllName) returned 2 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE2' 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1\DllName) returned 2 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1' 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\TIMESVC\BusPrefix) returned 2 0x83eb4da0: [TIMESVC DST] System Started... ..... Can u people help me in rectifying this.. Regards, Mekas. Tag: how to add Common drivers to platform Tag: 103625
  - 21
    - USB mounting probem!!!!! Hi all, O.S-Win CE 5.0. Processor - AMD turion 64 bit, Chipset RS 690T. I've created a image and it is booting well. But the thing is that both the USB and Hard Disk is not mounting. Firstlt i added USB, the system hangs, Debug msgs for USB : ---------------------- 0x83fd1b30: PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for placed device 0/20/3. 0x83fd1b30: PCIBUS!PCICfgCheckBARs: Problems can result if the device is being used while configuring PCIbus. 0x83fd1b30: Warning: No Match template is found for following PCI Device 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Bus/Device/Function = 0/24/0, Host / PCI Bridge 0x83fd1b30: VendorID = 0x1022, DeviceID = 0x1100, Command = 0x0000, Status = 0x0010 0x83fd1b30: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06 0x83fd1b30: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fd1b30: BaseAddresses: 0x83fd1b30: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fd1b30: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fd1b30: ROMBaseAddress = 0x00000000 0x83fd1b30: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Warning: No Match template is found for following PCI Device 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Bus/Device/Function = 0/24/1, Host / PCI Bridge 0x83fd1b30: VendorID = 0x1022, DeviceID = 0x1101, Command = 0x0000, Status = 0x0000 0x83fd1b30: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06 0x83fd1b30: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fd1b30: BaseAddresses: 0x83fd1b30: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fd1b30: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fd1b30: ROMBaseAddress = 0x00000000 0x83fd1b30: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Warning: No Match template is found for following PCI Device 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Bus/Device/Function = 0/24/2, Host / PCI Bridge 0x83fd1b30: VendorID = 0x1022, DeviceID = 0x1102, Command = 0x0000, Status = 0x0000 0x83fd1b30: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06 0x83fd1b30: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fd1b30: BaseAddresses: 0x83fd1b30: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fd1b30: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fd1b30: ROMBaseAddress = 0x00000000 0x83fd1b30: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Warning: No Match template is found for following PCI Device 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: Bus/Device/Function = 0/24/3, Host / PCI Bridge 0x83fd1b30: VendorID = 0x1022, DeviceID = 0x1103, Command = 0x0000, Status = 0x0010 0x83fd1b30: RevisionID = 0x00, ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06 0x83fd1b30: CacheLineSize = 0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00 0x83fd1b30: BaseAddresses: 0x83fd1b30: 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x83fd1b30: CIS = 0x00000000, SubVendorID = 0x0000, SubSystemID = 0x0000 0x83fd1b30: ROMBaseAddress = 0x00000000 0x83fd1b30: InterruptLine = 0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00 0x83fd1b30: ------------------------------------------------------------------------------- 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 6, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 1, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Bridge resource: Bus 0, Device 7, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 20, Function 2 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 1 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 2 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 3 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 4 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 18, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 19, Function 5 0x83fd1b30: IoBase = 0xD000, IoLimit = 0xDFFF 0x83fd1b30: IoBase reg = 0x0, offset 0x30 0x83fd1b30: IoBase = 0xE000, IoLimit = 0xEFFF 0x83fd1b30: IoBase reg = 0x0, offset 0x30 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 18, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 20, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 20, Function 1 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 20, Function 1 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 18, Function 0 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 20, Function 1 0x83fd1b30: PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 20, Function 1 0x83fd1b30: PCIBUS!PCIRequestResources: I/O Resource Manager request for I/O range 0x0-0x3 failed 0x83fd1b30: PCIbus!PCIEnum: WARNING: Resource request for device 0:20:1 failed 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ehci1\BusPrefix) returned 2 0x83fd1b30: HCD driver DLL attach 0x83fd1b30: EHCD!HCD_Init 0x83fd1b30: EHCD: Read config from registry: Base Address: 0xFDDFF000, Length: 0x100, I/O Port: NO, SysIntr: 0x21, Interface Type: 5, Bus Number: 0 0x83fd1b30: EHCD: ioPhysicalBase 0xFDDFF000, IoSpace 0x0 0x83fd1b30: EHCD: ioPortBase 0x230000, portBase 0xFDDFF000 0x83fd1b30: Updated eptr->e32_vsize to = 00002000 0x83fd1b30: EHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 10 0x83fd1b30: DMA buffer passed in from PDD 0x83fd1b30: CPhysMem Total Alloc Region PhysAddr = 0x02A2E000, VirtAddr = 0x00240000, size = 131072 0x83fd1b30: CPhysMem Special Alloc Region PhysAddr = 0x02A2E000, VirtAddr = 0x00240000, size = 4096 0x83fd1b30: CPhysMem HighPri Alloc Region PhysAddr = 0x02A2F000, VirtAddr = 0x00241000, size = 32768 0x83fd1b30: CPhysMem Normal Alloc Region PhysAddr = 0x02A37000, VirtAddr = 0x00249000, size = 94208 0x83fd1b30: +CHW::CHW base=0x230000, intr=0x21 0x83fd1b30: +CEhcd::Initialize. Entry 0x83fd1b30: +CDeviceGlobal::Initialize 0x83fd1b30: USBD: DLL attach 0x83fd1b30: +USBD:HcdAttach, hcd: 0x45D00 0x83fd1b30: -CDevice::Initialize, success! 0x83fd1b30: +CHW::Initialize 0x83fd1b30: -CEhcd::Initialize. Error - could not initialize device/pipe/hw classes 0x83fd1b30: Unknown: DEBUGCHK failed in file E:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\USB\HCD\USB20\EHCI\.\cehcd.cpp at line 144 0x83fd1b30: DEBUG_BREAK @02d7299c Ignored. 0x83fd1b30: +CDevice::DeInitialize 0x83fd1b30: -CDevice::DeInitialize 0x83fd1b30: DEVICE!LaunchDevice: Init() failed for device 0x0003ffd0 0x83fd1b30: DEVICE!I_ActivateDeviceEx: couldn't activate: prefix HCD, index 1, dll ehci.dll, context 0x602da0c 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\OHCI5\BusPrefix) returned 2 0x83fd1b30: HCD driver DLL attach 0x83fd1b30: HCD!HCD_Init 0x83fd1b30: OHCD: Read config from registry: Base Address: 0xFDDFA000, Length: 0x1000, I/O Port: NO, SysIntr: 0x20, Interface Type: 5, Bus Number: 0 0x83fd1b30: OHCD: ioPhysicalBase 0xFDDFA000, IoSpace 0x0 0x83fd1b30: OHCD: ioPortBase 0x240000, portBase 0xFDDFA000 0x83fd1b30: OHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 10 0x83fd1b30: DMA buffer passed in from PDD 0x83fd1b30: CPhysMem Total Alloc Region PhysAddr = 0x02A2E000, VirtAddr = 0x00250000, size = 65536 0x83fd1b30: CPhysMem Special Alloc Region PhysAddr = 0x02A2E000, VirtAddr = 0x00250000, size = 4096 0x83fd1b30: CPhysMem HighPri Alloc Region PhysAddr = 0x02A2F000, VirtAddr = 0x00251000, size = 16384 0x83fd1b30: CPhysMem Normal Alloc Region PhysAddr = 0x02A33000, VirtAddr = 0x00255000, size = 45056 0x83fd1b30: +COhcd::Initialize. Entry 0x83fd1b30: +CDeviceGlobal::Initialize 0x83fd1b30: USBD: DLL attach 0x83fd1b30: +USBD:HcdAttach, hcd: 0x45980 0x83fd1b30: -CDevice::Initialize, success! 0x83fd1b30: +CHW::Initialize base=0x240000, intr=0x20 0x83fd1b30: -CHW::Initialize, success! 0x83fd1b30: +CPipe::Initialize 0x83fd1b30: -CPipe::Initialize. Success! 0x83fd1b30: +CHW::EnterOperationalState 0x83fd1b30: -CHW::EnterOperationalState 0x83fd1b30: -COhcd::Initialize. Success!! 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\OHCI4\BusPrefix) returned 2 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD HCD1: 0x83fd1b30: HCD!HCD_Init 0x83fd1b30: OHCD: Read config from registry: Base Address: 0xFDDFB000, Length: 0x1000, I/O Port: NO, SysIntr: 0x1D, Interface Type: 5, Bus Number: 0 0x83fd1b30: OHCD: ioPhysicalBase 0xFDDFB000, IoSpace 0x0 0x83fd1b30: OHCD: ioPortBase 0x290000, portBase 0xFDDFB000 0x83fd1b30: OHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 15 0x83fd1b30: DMA buffer passed in from PDD 0x83fd1b30: CPhysMem Total Alloc Region PhysAddr = 0x02A44000, VirtAddr = 0x002A0000, size = 65536 0x83fd1b30: CPhysMem Special Alloc Region PhysAddr = 0x02A44000, VirtAddr = 0x002A0000, size = 4096 0x83fd1b30: CPhysMem HighPri Alloc Region PhysAddr = 0x02A45000, VirtAddr = 0x002A1000, size = 16384 0x83fd1b30: CPhysMem Normal Alloc Region PhysAddr = 0x02A49000, VirtAddr = 0x002A5000, size = 45056 0x83fd1b30: +COhcd::Initialize. Entry 0x83fd1b30: +CDeviceGlobal::Initialize 0x83fd1b30: +USBD:HcdAttach, hcd: 0x470F0 0x83fd1b30: -CDevice::Initialize, success! 0x83fd1b30: +CHW::Initialize base=0x290000, intr=0x1d 0x83fd1b30: -CHW::Initialize, success! 0x83fd1b30: +CPipe::Initialize 0x83fd1b30: -CPipe::Initialize. Success! 0x83fd1b30: +CHW::EnterOperationalState 0x83fd1b30: -CHW::EnterOperationalState 0x83fd1b30: -COhcd::Initialize. Success!! 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\OHCI3\BusPrefix) returned 2 0x83fd1b30: HCD!HCD_Init 0x83fd1b30: OHCD: Read config from registry: Base Address: 0xFDDFC000, Length: 0x1000, I/O Port: NO, SysIntr: 0x18, Interface Type: 5, Bus Number: 0 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD HCD2: 0x83fd1b30: OHCD: ioPhysicalBase 0xFDDFC000, IoSpace 0x0 0x83fd1b30: OHCD: ioPortBase 0x2E0000, portBase 0xFDDFC000 0x83fd1b30: OHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 10 0x83fd1b30: DMA buffer passed in from PDD 0x83fd1b30: CPhysMem Total Alloc Region PhysAddr = 0x02A54000, VirtAddr = 0x002F0000, size = 65536 0x83fd1b30: CPhysMem Special Alloc Region PhysAddr = 0x02A54000, VirtAddr = 0x002F0000, size = 4096 0x83fd1b30: CPhysMem HighPri Alloc Region PhysAddr = 0x02A55000, VirtAddr = 0x002F1000, size = 16384 0x83fd1b30: CPhysMem Normal Alloc Region PhysAddr = 0x02A59000, VirtAddr = 0x002F5000, size = 45056 0x83fd1b30: +COhcd::Initialize. Entry 0x83fd1b30: +CDeviceGlobal::Initialize 0x83fd1b30: +USBD:HcdAttach, hcd: 0x48700 0x83fd1b30: -CDevice::Initialize, success! 0x83fd1b30: +CHW::Initialize base=0x2e0000, intr=0x18 0x83fd1b30: -CHW::Initialize, success! 0x83fd1b30: +CPipe::Initialize 0x83fd1b30: -CPipe::Initialize. Success! 0x83fd1b30: +CHW::EnterOperationalState 0x83fd1b30: -CHW::EnterOperationalState 0x83fd1b30: -COhcd::Initialize. Success!! 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\OHCI2\BusPrefix) returned 2 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD HCD3: 0x83fd1b30: HCD!HCD_Init 0x83fd1b30: OHCD: Read config from registry: Base Address: 0xFDDFD000, Length: 0x1000, I/O Port: NO, SysIntr: 0x12, Interface Type: 5, Bus Number: 0 0x83fd1b30: OHCD: ioPhysicalBase 0xFDDFD000, IoSpace 0x0 0x83fd1b30: OHCD: ioPortBase 0x330000, portBase 0xFDDFD000 0x83fd1b30: OHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 15 0x83fd1b30: DMA buffer passed in from PDD 0x83fd1b30: CPhysMem Total Alloc Region PhysAddr = 0x02A64000, VirtAddr = 0x00340000, size = 65536 0x83fd1b30: CPhysMem Special Alloc Region PhysAddr = 0x02A64000, VirtAddr = 0x00340000, size = 4096 0x83fd1b30: CPhysMem HighPri Alloc Region PhysAddr = 0x02A65000, VirtAddr = 0x00341000, size = 16384 0x83fd1b30: CPhysMem Normal Alloc Region PhysAddr = 0x02A69000, VirtAddr = 0x00345000, size = 45056 0x83fd1b30: +COhcd::Initialize. Entry 0x83fd1b30: +CDeviceGlobal::Initialize 0x83fd1b30: +USBD:HcdAttach, hcd: 0x49E70 0x83fd1b30: -CDevice::Initialize, success! 0x83fd1b30: +CHW::Initialize base=0x330000, intr=0x12 0x83fd1b30: -CHW::Initialize, success! 0x83fd1b30: +CPipe::Initialize 0x83fd1b30: -CPipe::Initialize. Success! 0x83fd1b30: +CHW::EnterOperationalState 0x83fd1b30: -CHW::EnterOperationalState 0x83fd1b30: -COhcd::Initialize. Success!! 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\OHCI1\BusPrefix) returned 2 0x83fd1b30: HCD!HCD_Init 0x83fd1b30: OHCD: Read config from registry: Base Address: 0xFDDFE000, Length: 0x1000, I/O Port: NO, SysIntr: 0x10, Interface Type: 5, Bus Number: 0 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD HCD4: 0x83fd1b30: OHCD: ioPhysicalBase 0xFDDFE000, IoSpace 0x0 0x83fd1b30: OHCD: ioPortBase 0x380000, portBase 0xFDDFE000 0x83fd1b30: OHCD: Installed ISR handler, Dll = 'giisr.dll', Handler = 'ISRHandler', Irq = 5 0x83fd1b30: DMA buffer passed in from PDD 0x83fd1b30: CPhysMem Total Alloc Region PhysAddr = 0x02A74000, VirtAddr = 0x00390000, size = 65536 0x83fd1b30: CPhysMem Special Alloc Region PhysAddr = 0x02A74000, VirtAddr = 0x00390000, size = 4096 0x83fd1b30: CPhysMem HighPri Alloc Region PhysAddr = 0x02A75000, VirtAddr = 0x00391000, size = 16384 0x83fd1b30: CPhysMem Normal Alloc Region PhysAddr = 0x02A79000, VirtAddr = 0x00395000, size = 45056 0x83fd1b30: +COhcd::Initialize. Entry 0x83fd1b30: +CDeviceGlobal::Initialize 0x83fd1b30: +USBD:HcdAttach, hcd: 0x3F000 0x83fd1b30: -CDevice::Initialize, success! 0x83fd1b30: +CHW::Initialize base=0x380000, intr=0x10 0x83fd1b30: -CHW::Initialize, success! 0x83fd1b30: +CPipe::Initialize 0x83fd1b30: -CPipe::Initialize. Success! 0x83fd1b30: +CHW::EnterOperationalState 0x83fd1b30: -CHW::EnterOperationalState 0x83fd1b30: -COhcd::Initialize. Success!! 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE4\DllName) returned 2 0x83fce800: [NOTIFY] HandleSystemEvent 7 /ADD HCD5: 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE4' 0x83e96800: CHub(Root tier 0)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0101 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE3\DllName) returned 2 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE3' 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE2\DllName) returned 2 0x83e96800: CHub(Root tier 0)::HubStatusChangeThread - device attached on port 1 0x83e96800: +CHub(Root tier 0)::AttachDevice - port = 1, fIsLowSpeed = 0 0x83e96800: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0 0x83e96800: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0 0x83e96800: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0 0x83fd1b30: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE2' 0x83fd1b30: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\PCI-PCI-BRIDGE1\DllName) returned 2 0x83e96800: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 0 Help me in rectifying this error. Regards, Mekas :) Tag: how to add Common drivers to platform Tag: 103624
  - 22
    - app download error between vs2005 and ce5.0 device hi, I built a ce 5.0 image with pb5.0. and I also built a sample c# app by vs2005. At the ce os image, I added dotnet cf 2.0, activesync related component. I think there is no problem with my ce os image. But when I try to download c# app from vs2005 to ce device, I have wait about 5 minutes until the sample app is downloaded and run at the target device. What is problem??? Following my procedure. 1. ce device boot and configure tcp/ip network to 192.168.1.125. 2. run conmanclient2 and cmaccept at cmd windows. 3. configure the vs2005 settings to connect the ce device and the 'connect device' is successful. 4. At the vs2005 menu, run the 'debug->start without debugging' and then click the deply popup window by selecting windows ce 5.0 device. 5. The sample application is downloaded to target device right away. But there need about 5 minutes to be automatically run at the target side. I hardly to know what is problem... Tag: how to add Common drivers to platform Tag: 103622
  - 23
    - what is the major difference between 0340 SMS and IS637 SMS? what is the major difference between these two SMS format? many thanks. Tag: how to add Common drivers to platform Tag: 103621
  - 24
    - USB HOST CONTROLLER SUPPORT FOR RNDIS DEVICE (USR5421) Hi All, I am planning to have RNDIS support for the WLAN device (USR5421) on my newly developed host controller. My doubt is that whether any extra support is needed from the HOST CONTROLLER point of view to support RNDIS devices. I am raising this question becouse the host controller what we have on our davinci board is not complaint to any of the specifications(EHCI, OHCI or UHCI). since this is the case, We have developed a host controller device driver of ours own and now it is supporting all the HID devices such as Mouse, keyboard etc and the mass storage devices such as pen drives. The doubt came in to my mind becouse, i can see some registers kept in the specification of the HOST CONTROLLER specific to RNDIS. So should i program these registers to support USR5421 up on my Host Controller driver. So Experts Please Open Your Eyes.... Thanks & Regards, Noor Tag: how to add Common drivers to platform Tag: 103613
  - 25
    - permenent storage Hi all, I am going to develop a mobile handset.My platform is intel pxa270 and os is wince 5.0.In normal case, if we switch off the handset ,the downloded files and contacts are kept intact..ie in a mobile, if we switch off and switch on everything will bw there.But if we press the 'Reset to factory setting 'only the datas are lost..Can you tell me how it is implemented in the handset or mobile.I think the contats are stored uging the database..Is the data bse is stored in the flash..Can you tell me.if there is any code in wince 5.0 which handles all these.Is it anything to do with FMD(flash media driver) or rtc driver..or what else.please help me Tag: how to add Common drivers to platform Tag: 103605

hi all,
how can i build the driver in PUBLIC\COMMON\Drivers folder..for
example.. the one in PUBLIC\COMMON\OAK
\DRIVERS\BLOCK\MSFLASHFMD\STRATA folder...

i am using maistone ii and how can i add stratad.dll to my platform
image..
Can u tell me procedures..

What are the normal procedure for adding the drivers in to platform..I
follwed the steps in the platform builder help and "Add driver to
existing bsp".But it is not building properly.

Top

Re: how to add Common drivers to platform by Jack

Jack
Thu Aug 16 01:00:01 CDT 2007

what exactly is the error?

Top

Re: how to add Common drivers to platform by princyf

princyf
Thu Aug 16 02:05:01 CDT 2007

On Aug 16, 11:00 am, Jack <unseen_co...@hotmail.com> wrote:
> what exactly is the error?

i am not getting error...but i cannot build the directory and there
is no dll in release folder..

Top

Re: how to add Common drivers to platform by Janez

Janez
Thu Aug 16 04:00:29 CDT 2007

1) Open a Command Line Window
2) set WINCEREL=1
3) sysgen -p common stratad
The stratad.dll will be in your %_flatreleasedir%

http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_frm/thread/e3ab096328c380d4/9ca85a9c9df4dc4f?lnk=st&q=stratad_lib.lib&rnum=1&hl=sl#9ca85a9c9df4dc4f

On 16 avg., 09:05, prin...@gmail.com wrote:
> On Aug 16, 11:00 am, Jack <unseen_co...@hotmail.com> wrote:
>
> > what exactly is the error?
>
> i am not getting error...but i cannot build the directory and there
> is no dll in release folder..

Top

Re: how to add Common drivers to platform by princyf

princyf
Thu Aug 16 04:55:50 CDT 2007

hi,
I have tried that..and it worked also..but is it he correct way to do
that...what we have done is we manualy build the stratad.dll..and fro
adding it to the nk.bin,we edited the platform.bib .Can we move this
files to platform directory and build the same.?

Top

Re: how to add Common drivers to platform by alexquisi

alexquisi
Thu Aug 16 07:12:00 CDT 2007

Hi,

probably you need to do what is explained here:

http://msdn2.microsoft.com/en-us/library/aa459163.aspx

Best regards,

Alex

On Aug 16, 11:55 am, prin...@gmail.com wrote:
> hi,
> I have tried that..and it worked also..but is it he correct way to do
> that...what we have done is we manualy build the stratad.dll..and fro
> adding it to the nk.bin,we edited the platform.bib .Can we move this
> files to platform directory and build the same.?

Top