A problem about USB serial Driver??

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Cross Process Callbacks Hi all, I want to make a callback from a driver in the context of device.exe to an application in userland. Actually, that's a lie, I want to do it differently but I am getting pushback for other reasons. My scenario is like this: Application -> registers callback via stream driver IOCTL Driver -> allocates buffers and handles reading data from device .. .. Driver -> Data arrives at driver and is put in a buffer in created in device.exe context. Driver -> Driver makes callback to userland application with the data mapped to application user space. Application -> processes data and returns Driver -> handles buffer cleanup and continues in device.exe context The first problem is mapping the data buffer, MapPtrToProcess is deprecated and MapCallerPtr would not work as it is not a PSL call and I want to avoid a buffer copy. The best way I could come up with was ReadProcessMemory, this is a trusted API though so I may have problems there too. Next, how do I make a function call in the context of a different process space? I could use a thread in the application space that simply waits for an event and do it that way (like an IST) but I am racking my brains to figure out another way - does anybody have any ideas? BTW: This is under CE5.0, to be used on WM5. Geoff -- Tag: A problem about USB serial Driver?? Tag: 87743
  - 2
    - GPIO configuration in WinCE5.0 Hi, I am basically new to WinCE environment so I would really appreciate if any one of you could help me to sort out my problem. I am using Intel PXA270 and BSP is MainstoneII in WinCE5.0. I want to make my GPIO 14 as active output high. So I have changed GPIO's in xlli_mainstone_defs.inc and mainstone.inc GPIO's that I changed are GPDR0 as 0xC010C000 ( for output), GPSR0 as 0x00004000 ( for active high). My GAFR0_L is 0x84000000 as well. But these values are not configuring my GPIO 14 as high as I measured signal. Later on, I tried to print GPIO's values on hyper terminal but it showing GPSR0 still as 0x00000000. I donot know where else do I need to change for make it active high? Thanks in advance. Kind Regards, Sandeep Tag: A problem about USB serial Driver?? Tag: 87741
  - 3
    - Why should I update from OEM embedded vs. download QFEs? As an OEM embedded partner, Microsoft directs me to download PB updates from their OEM embedded site. I find that on this site, only .IMG files are available, usuallly 250MB+, and are not up-to-date with what is available to the general public on the MS download site. For example, the open MS download site has monthly updates, the latest of which is June 2006. The latest update on the OEM embedded partner site is May (284MB IMG file). The corresponding May QFE on the open MS download site is 34 MB. Of course, this is the x86 only download, but still why would I want the .IMG file? Tag: A problem about USB serial Driver?? Tag: 87738
  - 4
    - Using WNetConnection3 Hi Everyone, Here is my problem, I want to use WNetConnection3 to keep a connection to a net share. I would also like the connection to be persistent after a reboot. What I thought is to use the Credential Manager to save the credential and then call WNetConnection3 with 0 as a Pass and User parameters. It says in the MSDN help that WNetConnection3 when User is NULL that it's supposed to use the default username and password, can I set it using CredWrite and how does it works? I must also say that it's not possible for the user to enter it manually (headless device), I must add it programatically. Is this possible? Vincent Gauthier Tag: A problem about USB serial Driver?? Tag: 87736
  - 5
    - Terminal build errors in PB5! Until last week my kernel builds were working fine, but something's changed and I don't know what. The weird thing is my colleague's having the same problems, and he's working on a different project with a different PC. It's possible our ever-helpful IT department have rolled out something that's interfering with Platform Builder 5.0 but I'd like some idea of what might be causing the build errors first. There seem to be two main problem areas, but they occur all over the build so there's no single point of failure. I may have seen other errors as well but these are the two from the logs I've collected. Does anyone have any idea what these problems might be caused by? Res2Res: Adding resources from F:\WINCE500\public\common\oak\lib\ARMV4I\retail\0413\commctrlbase.res to C:\DOCUME~1\ISAACS~1\LOCALS~1\Temp\R2RBC4.tmp. ERROR: Res2Res: Res2Res: ERROR: Line: 267 File: f:\macallan2\private\winceos\tools\rescommon\checksum.cpp Res2Res: Error adding resources (-1) NMAKE : fatal error U1077: 'SysgenMake' : return code '0x2' Stop. Processing include files cefilter F:\WINCE500\public\common\sdk\inc\*.* F:\WINCE500\PBWorkspaces\lightningii\WINCE500\Thunder_ARMV4I\cesysgen\sdk\inc NMAKE : fatal error U1077: 'cefilter' : return code '0xc0000005' Stop. Tag: A problem about USB serial Driver?? Tag: 87735
  - 6
    - vulume problem of ringtone plug-in I have developmet a ringtone plug-in which impletment IEventSound interface. But it can't change vulume when ring profile change, and the vulume the ringtone is too small when incoming call occur. Whether the issues could be resolved if I try IEventSound2 interface? If is, how to impletment IEventSound2::SetVulume() ,and so on? Whether there are some API to set vulume? Any help appreciated! Tag: A problem about USB serial Driver?? Tag: 87731
  - 7
    - Developing D3DM Primary Hardware Device Driver Can anyone help me with these issues? We are trying to develop D3DM hardware-based device driver and we are somewhat lost as to where to start since this is the first time ever developing for D3DM device driver. OpenGL ES driver/SDK development is done and is up and running fine. We first tried to base our effort on the given D3DM null driver from Platform Builder for Windows CE 5.0 catalog. That null driver looked like a good place to start until we found that all the D3DM applications need to call; LoadLibrary(TEXT("d3dm_nulldrv.dll")) and register as a software device. Now this method would work fine if we stuff all our hardware-accelerated implementations to the d3dm_nulldrv.dll and have the application developer go through the above stages before creating a D3DM device (CreateDevice). The problem with this method however is that WinCE documentation states that this method is usually for software renderer drivers and it might cause confusion among D3DM developers. The proper way would be not going through those LoadLibrary/RegisterSoftwareDevice process and go directly call CreateDevice with default adapter and default device parameters, as stated in the WinCE documentation as a proper hardware D3DM device driver creation. So, in order for us to start developing the clean D3DM hardware-based device driver in place of the null driver, where would we have to start? Would this involve coming up with our own WinCE display driver implementation? Or can we implement D3DM only and still use the default display device driver? Any help on this issues would be greatly appreciated. Thanks..... Tag: A problem about USB serial Driver?? Tag: 87723
  - 8
    - FATSystem "BUG"? Hi, I have written some block device drivers, such as CF card, SD card, IDE disk...There is a common problem. For example, in CF card driver, I used the stream interface(XXX_init, XXX_IoControl...). And I called the AdvertiseInterface() function to declare it's a block device. So with the FAT system, we could see the mounted disk in "My device" under WinCE. Then I copied files in & out of the disk to test the W/R speed. I found that the write-in speed is 900KB/s, but the read-out speed is no more than 500KB/s. That's insufferable. I wrote an application to test R/W speed of CF card keep away from FAT: I called CreateFile() to get the handle of the driver, then used DeviceIocontrol() to write data in and read out. In this case, the Write speed is 1.1MB/s, and the Read speed is more than 2MB/s. And the same situation was appeared in SD card. With FAT: Write 1.2MB/s, Read 500KB/s. Without FAT: Write 1.4MB/s, Read 4.1MB/s. Even in the Ram Disk driver, the one used memory space as the virtual storage space, the test result was: With FAT: Write more than 1.5MB/s, Read 600KB/s. With out FAT: all very fast speed. So I thought the FAT system may cause the low efficiency of read operation under WinCE. Any suggestion is helpful and thankful. Tag: A problem about USB serial Driver?? Tag: 87716
  - 9
    - A problem about USB serial Driver I use USB serial driver to connect activesync. I connected PC, but the driver on PC is not correct. I use activesync 4.1. my board is mainstoneii, and the bsp is provided by Intel, which means the dirver on PC must be intel's? the following is my platform.reg: ; @CESYSGEN IF CE_MODULES_USBFN IF BSP_NOUSBFN ! [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Usbfn] "InterfaceType"=dword:0 ; Internal "Prefix"="UFN" "Dll"="ms2_usbfn.dll" "Order"=dword:1 "Priority256"=dword:64 "MemBase"=dword:40600000 ; UDC_BASE_U_VIRTUAL "MemLen"=dword:1000 ; Needs at least 0xE04. Round up to 1 page. "Sysintr"=dword:1a "BusIoctl"=dword:2a0048 "IClass"=multi_sz:"{E2BDC372-598F-4619-BC50-54B3F7848D35}=%b","{6F40791D-300E-44E4-BC38-E0E63CA8375C}=%b" [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class\Config] "EnableFlowHard"=dword:0 "EnableFlowSoft"=dword:0 [HKEY_LOCAL_MACHINE\Comm\DefaultConnections] "`USB Default"=multi_sz:"USB Cable:","115200" ;Default Connectoid [HKEY_CURRENT_USER\ControlPanel\Comm] "Cnct"="`USB Default" ;Default Connectoid ;[HKEY_CURRENT_USER\ControlPanel\Comm] ;"Cnct"="`Desktop @ 19000" [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class] "Dll"="serialusbfn.dll" "InterfaceSubClass"=dword:ff "InterfaceProtocol"=dword:ff "DeviceName"="USBFNS1:" ; "DeviceName"="UFN1:" "Tsp"="Unimodem.dll" "FriendlyName"="USB Cable:" "Prefix"="COM" ; "DeviceArrayIndex"=dword:0 "DeviceArrayIndex"=dword:2 "DeviceType"=dword:0 "IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}" ; "IClass"="{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}" ; idVendor must be changed. 045E belongs to Microsoft and is only to be used for ; prototype devices in your labs. Visit http://www.usb.org to obtain a vendor id. "idVendor"=dword:045E ; "idVendor"=dword:8086 "Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change idVendor)" ; "Manufacturer"="Intel" "idProduct"=dword:00ce ; "idProduct"=dword:A6CD "Product"="Generic Serial (PROTOTYPE--Remember to change idVendor)" ; "Product"="WindowsCE.NET 5.0" "bcdDevice"=dword:0 IF BSP_NOUSBRNDIS [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers] "DefaultClientDriver"=- "DefaultClientDriver"="Serial_Class" ELSE [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS] ; idVendor must be changed. 8086 belongs to Intel and is only to be used for ; prototype devices in your labs. Visit http://www.usb.org to obtain a vendor id. "idVendor"=dword:8086 ; "Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change idVendor)" "Manufacturer"="Intel Corporation (PROTOTYPE--Remember to change idVendor)" "idProduct"=dword:F003 "Product"="Generic RNDIS (PROTOTYPE--Remember to change idVendor)" "bcdDevice"=dword:0 [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers] "DefaultClientDriver"=- "DefaultClientDriver"="RNDIS" ENDIF BSP_NOUSBRNDIS ENDIF BSP_NOUSBFN ! Tag: A problem about USB serial Driver?? Tag: 87712
  - 10
    - Serial CMD I'm trying to get CMD to come out of one of the com ports on my device. I am able to get CMD running through a telnet session without trouble, as well as run the simple comport tester on the desired port. I edit the console registry to include the speed and the port to OutputTo. Additionally i tell the init registry section to start cmd. When the system boots, i get the message "Unrecognized option XX" where XX is the Launch number associated with the CMD call. This message appears on the com port where i expect the pocket cmd to start, and not the debug port. Any suggestions? Tag: A problem about USB serial Driver?? Tag: 87711
  - 11
    - Halt after OEMInit(). in s3c2440 I am using samsung s3c2440 Arm cpu, wince 5.0 After executing OEMInit(), just halted. how to debug this problem? i'm found similar this problem. i checked as follows. but they were not in my case. 1. Verify that your system tick timer function properly. Does your OEMInterruptHandler implement SYSINTR_RESCHED interrupt? 2. any uninitialized pointer has been used in your code. 3. Wrong Memory Settings. oemaddrtab_cfg.inc, config.bib 4. Interrupt. The debug message as follows. --------------------------------------------------- Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00 ProcessorType=0920 Revision=0 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8022c610 DCache: 8 sets, 64 ways, 32 line size, 16384 size ICache: 8 sets, 64 ways, 32 line size, 16384 size +OALInterruptInit +OALIntrMapInit -OALIntrMapInit +OALPAtoVA(0x4a000000, 0) -OALPAtoVA(va = 0xb0a00000) +OALPAtoVA(0x56000000, 0) -OALPAtoVA(va = 0xb1600000) +BSPIntrInit +OALPAtoVA(0x56000000, 0) -OALPAtoVA(va = 0xb1600000) +OALIntrStaticTranslate(17, 26) -OALIntrStaticTranslate -BSPIntrInit(rc = 1) -OALInterruptInit(rc = 1) +OALTimerInit( 1, 17, 0 ) +OALIntrRequestSysIntr(1, 0xffffc76c, 0x00000004) -OALIntrRequestSysIntr(sysIntr = 16) +OALPAtoVA(0x51000000, 0) -OALPAtoVA(va = 0xb1100000) +OEMInterruptEnable(16, 0x0, 0) +OALTranslateSysIntr(16) -OALTranslateSysIntr(rc = 1) +OALIntrEnableIrqs(1, 0x8201ef20) +BSPIntrEnableIrq(14) -BSPIntrEnableIrq(irq = 14) -OALIntrEnableIrqs(rc = 1) -OEMInterruptEnable(rc = 1) -OALTimerInit(rc = 1) +ConfigureGPIO +OALPAtoVA(0x56000000, 0) -OALPAtoVA(va = 0xb1600000) +OALPAtoVA(0x4c000000, 0) -OALPAtoVA(va = 0xb0c00000) -ConfigureGPIO +InitDisplay +OALPAtoVA(0x56000000, 0) -OALPAtoVA(va = 0xb1600000) +OALPAtoVA(0x4d000000, 0) -OALPAtoVA(va = 0xb0d00000) -InitDisplay +OALKitlStart OALKitlStart Null -OALKitlStart -OEMInit <END> -OR----------------------------------------------- +OEMCacheRangeFlush(0x00000000, 0, 0x00000004) -OEMCacheRangeFlush Sp=ffffc7cc +OEMCacheRangeFlush(0x00000000, 0, 0x00000001) -OEMCacheRangeFlush <END> --------------------------------------------------- Thanks. Regard. Tag: A problem about USB serial Driver?? Tag: 87710
  - 12
    - Debugging after installing the v2.0 SP1 QFE to platform builder Hi, I have just installed the newly released QFE for v2.0 SP1 in our Windows CE target device. Everying thing works fine on the device. However, when debugging using Visual Studio 2005, it tries to install: NETCFv2.wce5.armv4i.cab I assume this is the original v2.0 CF and Visual Studio is trying to install it because the one on the device reports a different (newer) version. Unfortunately, it can't install it on our device because it is too big and so debugging fails. Anyone know a resolution for this problem? TIA, - John Tag: A problem about USB serial Driver?? Tag: 87707
  - 13
    - RNDIS - USRobotics Wireless MAXg USB Adapter I'm using the following post by Mike Hall to set up this USB adapter for 802.11 in my platform builder 5 project. http://blogs.msdn.com/mikehall/archive/2006/02/28/540912.aspx I only need the device to function as a client to connect to an access point. Do I need all the sysgens he has listed or only a subset? Also, not sure how to add a sysgen with a value of "". I just added a space to enable the OK button. THX Quote: You don't need a driver, that's the cool thing, you only need to have the appropriate SYSGENS set. ============================================= For USB Host ============================================= SYSGEN_USB=1 ==> usbhost & usbd BSP_USB_UHCI=1 ==> includes uhci.dll BSP_USB_OHCI=1 ==> includes ohci2.dll BSP_USB_EHCI=1 ==> includes ehci.dll BSP_NOUSB="" IMG_NOUSB="" ============================================= For USB Function ============================================= SYSGEN_USBFN_NET2280=1 ==> to have net2280 SYSGEN_USBFN_SERIAL=1 ==> to have serialusbfn ============================================= For RNDIS Host ============================================= SYSGEN_ETH_USB_HOST ==> To have usb8023 & rndimp included ============================================= For RNDIS Function ============================================= SYSGEN_USBFN_ETHERNET=1 - Mike Tag: A problem about USB serial Driver?? Tag: 87704
  - 14
    - memory exception on array We're trying to test our application running under CE 5.0. It was previously working under CE 4.1, and we don't do anything fancy, so generally its been working fine in CE 5.0. I've hit a snag, and I don't understand why this one case would be odd in any way. In a windows message handler, we create an array of data with: TCHAR *lParam = new TCHAR[_tcslen(parList->p.strParam) + 1]; We pass that memory to another message handler with: PostMessage( ownerWin, cmd, wParam,(LPARAM) lParam ); and then leave. When we get to the other message handler, the value of lParam is the same, (it is in the same process), and the data in the array is all fine. But, when we go to release the memory with: delete [] lParam; On CE 5.0, it aborts. CE 4.1 works fine. Any ideas ? The assembly just takes the pointer and passes it to the library call for delete. Tag: A problem about USB serial Driver?? Tag: 87702
  - 15
    - Debugzones without KITL Hi, I am using WinCE 4.2 with a PXA255 platform. I wouldlike to turn on debugzones but from the PC HKLM\Pegasus\Zones reg key. This is because i don't have a KITL connection but have serial port output. Only problem is in the registry key i don't know which bits to set for my NDIS driver. How does one find out which bits correspond to whihc driver and then the zone within the driver? Tag: A problem about USB serial Driver?? Tag: 87700
  - 16
    - revision control Having imported the entire %WINCEROOT% tree and our BSP into clearcase (which makes everything read-only), I can successfully build an image only after I've made the following files writable: PUBLIC\COMMON\OAK\CATALOG\DATABASE\pbdb.mdb pbdb.mdb is written when importing our BSP (.cec) into the catalog. I'm wondering if there is any reason that I would not want to check in this updated file. Maybe there are hard-coded paths that will break on other workstations? I'm sure someone else has run into this same issue? PUBLIC\SHELL\OAK\LIB\ARMV4I\DEBUG\<lcid>\ceshapi_base.res PUBLIC\SHELL\OAK\LIB\ARMV4I\DEBUG\<lcid>\ceshui_base.res PUBLIC\WCESHELLFE\OAK\LIB\ARMV4I\DEBUG\*.res If these resource files are not writable, renumbericonids fails and kills the build. For now, I write-enable them using a pre-sysgen batch file. That's less than ideal however and again, I'm wondering what others have done? Thanks for any help. eamonn Tag: A problem about USB serial Driver?? Tag: 87690
  - 17
    - Activesync over Ethernet on XSCALE Hi All, I am trying to determine if it is even possible to run activesync over ethernet on the PXA270. I can't seem to get a clear answer. There are a lot of posts that talk about how to troubleshoot activesync over ENET, but I must be missing some major component from my build or some concept is completely alluding me as what I hear described in these FAQs and what I see have little in common. I have a custom CE 4.1 device, based off the Intel MAINSTONE design. I can do activesync over serial, and I can FTP over Ethernet, but I can't activesync over Ethernet. From what I've read, all agree Activesync over Ethernet is only possible if you set up a "Partnership" on the host side. I have the 3.5 build of Activesync running on my PC and see no possible way to setup the partnership. It seems I always connect as guest. I've tried reinstalling, and I've tried upgrading to later versions of Activesync, all with no luck. Perhaps it is just not possible because of something inherent with the XSCALE BSP or how Activesync recognizes this device? Or perhaps I have left some required component from my device build? I'm at a loss. I'd aprreciate hearing from anyone out there who has had similar experience, especially if someone out there has a similar configuration up and running. Thanks! Tag: A problem about USB serial Driver?? Tag: 87689
  - 18
    - Adding dependencies to Platform Builder components Hi, I'm trying to create some components to add to Platform Builder for Windows CE 5.0 but I've run into some problems. Synopsis: I create component 'B' with a dependency on component 'A' with dependencies on some O.S. components. When I add 'B' to my platform it pulls in 'A' automatically but then 'A' does not seem to have any dependencies. When I add 'A' directly it does pull in the O.S. components and I can see the dependencies. In more depth: I can create a component project, call it 'A', with associated .cec, .bib, .reg, .dat, .db files etc. This project results in a support DLL being copied to %_FLATRELEASEDIR% which I achieve through use of the postlink.bat file. This component has dependencies on a number of operating system components so I specify them in projsysgen.bat by setting the SYSGEN_xxx's as per the instructions here http://tinyurl.com/m753x. I can import my .cec file into platform builder and successfully add the component. The operating system components which we have dependencies on are pulled in correctly and I can see them in the catalog items for my platform workspace. If I sysgen I see the DLL is added to my kernel image correctly. So far so good... Next I create another project with associated files, call it 'B'. I want this project to be a component which has a dependency on the DLL I add in with component 'A'. If import the .cec for 'B' I can add 'B' and that pulls in 'A' successfully. However it does not pull in the dependencies that 'A' has on operating system components. If I step back and add in 'A' directly the operating system component dependencies do get added. So I'm wondering if either I am doing something wrong with my dependency setup in projsysgen.bat or if the build environment will only let me specify single level dependencies where 3rd party components are involved? I can't seem to find an enormous amount of information on this by Googling, but perhaps I'm looking in the wrong place. Can anybody help? Thanks, Alex Lennon Tag: A problem about USB serial Driver?? Tag: 87688
  - 19
    - =?iso-8859-15?Q?Cherche_comp=E9tence_sur_Windows_CE?= Bonjour, Ma soci=E9t=E9 aimerait agrandir ses =E9quipes de d=E9veloppement dans le= =20 domaine de la mobilit=E9 en particulier windows mobile 5. Toutefois nous=20 trouvons difficile de rencontrer des personnes comp=E9tentes dans ce=20 domaine. Auriez vous des id=E9es sur les canaux =E0 solliciter afin de trouver des= =20 personnes passionn=E9es et voulant travailler sur des projets tr=E9s pointu= s=20 sur ce syst=E8me ? Pour un contact direct, n'h=E9sitez pas a me joindre a : edessioux@everbee.com Tag: A problem about USB serial Driver?? Tag: 87686
  - 20
    - OEMIoControl: Unsupported Code I am using CE 5.0 with a VIA BSP on a proprietary x86 platform and get the debug output below at boot and at various other times. I know that these are the IOCTL_HAL_GET_RANDOM_SEED and IOCTL_HAL_GET_HWENTROPY codes respectively but wonder what is calling them, why they are being called and what happens when they are called but not supported. I have searched the shared code base and fiound nothing. OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 Tag: A problem about USB serial Driver?? Tag: 87684
  - 21
    - Connecting to a File Server Hi Everyone, I'm migrating a device from Windows CE4.2 to 5.0. With the device we use a command prompt program that allows a user to set a Network Share using WNetAddConnection3. The point of the program is to be able to set a username and password and then add any number of network share (on the same domain) and make them available after a reboot without having to enter the passwork each time. Using 4.2 we were able to save the credentials and then pass 0 to username and password parameters to WNetAddConnection3 and it worked. In the help files (MSDN) it says that using 0 tells to the function to use default username and passwork. By using this method it give the possibility to the user to save a network share and have it accessible after a reboot by using CONNECT_UPDATE_PROFILE with WNetAddConnection3(It was working perfectly under 4.2, maybe it's not possible anymore under 5.0). Under 5.0 it doesn't work anymore. I must add that our device is a headless device, that means that it's not possible for a dialog box to popup for asking the user to enter the password. I suspect that the problem is with the save credential function. Here is the code, we call this code before calling WNetAddConnection3: BOOL SaveDefaultCredentials(TCHAR *szUser, TCHAR *szPassword, TCHAR *szUserFull, TCHAR *szDomain) { BOOL RetValue = FALSE; CECREDENTIAL Credential; Credential.Flags = 0; Credential.Persist = CRED_PERSIST_LOCAL_MACHINE; Credential.Type = CRED_TYPE_DOMAIN_PASSWORD; Credential.UserName = szUserFull; Credential.CredentialBlobSize = 0; Credential.CredentialBlob = 0; RetValue = CeCredWrite( 0, &Credential ); if (!RetValue) { wprintf(L"CeCredWrite error writing %s\r\n",Credential.UserName); } else { //wprintf(L"CeCredWrite success writing %s\r\n", Credential.UserName); } // Set password if( RetValue ) { SEC_WINNT_AUTH_IDENTITY_W AuthIdentity; AuthIdentity.User = szUser; AuthIdentity.UserLength = wcslen(szUser); AuthIdentity.Domain = szDomain; AuthIdentity.DomainLength = wcslen(szDomain); AuthIdentity.Password = szPassword; AuthIdentity.PasswordLength = wcslen(szPassword); AuthIdentity.Flags = SEC_WINNT_AUTH_IDENTITY_UNICODE; RetValue = SaveSspCredentials(&AuthIdentity); } return RetValue; } BOOL SaveSspCredentials(SEC_WINNT_AUTH_IDENTITY_W *pAuthIdentity) { PWSTR Packages[] = {L"NTLM", L"KERBEROS"}; BOOL fRet = TRUE; int i; __try { for (i = 0; i < (sizeof(Packages) / sizeof(Packages[0])); i++) { CredHandle hCred; // Credential Handle TimeStamp Lifetime; if( AcquireCredentialsHandleW( NULL, // Principal Packages[i], // Names of the security packages SECPKG_CRED_OUTBOUND,// Flag that indicates how these credentials will be used NULL, // LOGON id pAuthIdentity, NULL, // Pointer to a SEC_GET_KEY_FN function NULL, // get key arg &hCred, // Pointer to CredHandle structure that receives the credential handle. &Lifetime // Pointer to a TimeStamp ) == NO_ERROR ) { FreeCredentialsHandle(&hCred); } } } __except(1) { fRet = FALSE; wprintf(TEXT("AcquireCredentialsHandle faulted")); } return fRet; } Is this the correct way to do it in CE 5.0? I know that we should now use CredWrite but CeCredWrite should be still supported. Can somebody help me solve my problem? Thanks Tag: A problem about USB serial Driver?? Tag: 87683
  - 22
    - Bluetooth, Headset, WinCE5 I am trying to use Bluetooth headset on WinCE5. I have included in build: Bluetooth Stack with Integrated CSR Chipset driver Bluetooth HS/HF and Audio Gateway Service and have set SYSGEN_BTH_AUDIO The bluetooth hardware is a Bluegiga module, connected via serial port using HCI mode. I can run bluetooth manager from Control Panel and discover the device just fine (a Jabra 200) [I can also discover various devices supporting SPP and can connect and use these fine] When it finds the Jabra it pops up a window asking for the PIN, I enter 0000 (the PIN for the Jabra) and it appears to be happy with this. I then double tap on the entry in bluetooth manager and set the device to be "Trusted" and "Active". I then run "btagconfig -audio on" from command line but it fails to connect. It returns "Operation failed: 21". Looking at the PB debug shows "tdisdp_connect_out: fails, err = 0x000004b1" which Error Lookup reports as meaning "The device is not currently connected but it is a remembered connection. " which is not very helpful. I know the headset works as I have used it OK on an XDA. If I press the button on the headset it appears to try to connect to the device since the PB debug shows: "hci_connection_complete_event : no connection, status = 5" seven times and then "hci_connection_complete_event : no connection, status = 23". This sequence appears to be triggered by pressing the button on the headset. Anyone any ideas here on what I am missing? Why I cannot connect to the headset? Thanks in advance Andrew Tag: A problem about USB serial Driver?? Tag: 87680
  - 23
    - Windows CE 5.0 Display Properties In windows ce 4.2 control panel -> display->Background the image selected is shown as a 1.5cm by 1.5cm picture, he same picture on windows ce 5.0 is 1.5cm by 5.5cm, anyone else seen this, don't understand why the image is stretched. Any help would be appreciated. Tag: A problem about USB serial Driver?? Tag: 87679
  - 24
    - using pxa270 GPIO_0 as external interrupt source Hi everybody, I have a question concerned about using GPIO_0 of pxa270 as interrupt source. My external miniPCI device is connected to target pxa270 though VLIO bus and the interrupt pin INTA# is connected to the GPIO_0 of pxa270. From mannual , I came to know that GPIO_0 & GPIO_1 (FIQ) are distinguished from other GPIO interrupt source and are used by pxa270 at startup like power management etc., My question is that, if I want to use GPIO_0 as interrupt source should I need to do setting up of bits corresponding to GPIO_0 interrupt in the interrupt controller register and mask register ? or the existing BSP will do the interrupt setup for GPIO_0 ? Thanks to clarify me about GPIO_0 . Sara Tag: A problem about USB serial Driver?? Tag: 87674
  - 25
    - ISR-IST data transfer... Hi, we are working on serial communication and the problem is that the processor usage is around 90% during data transfer. We need to lower this and searching msdn we come up with the idea of ISR notifying IST less frequently so that we can gain from this. Anyone please tell how we can modify ISR-IST so that coming data would first be buffered in ISR and then how to pass this data to ISR? Thanks for any help... Tag: A problem about USB serial Driver?? Tag: 87673
- Next
  - 1
    - Platform Manager was unable to queue the clientside package for .. I need to evaluate the graphics performance of a new PXA270, Windows CE 5.0 third party vendor device. I tried to use the WCETK test "Graphics Device Interface Performance Test". Unfortunately I get the error message "Platform Manager was unable to queue the clientside package for download to the device." What does this mean? Regards Peter Tag: A problem about USB serial Driver?? Tag: 87672
  - 2
    - Imagehash always fail. Hi, When I follow the Technical Articles "Implementing Enhanced Boot Loader" to do image hash/unhash, I can't finish all process. 1. I can't follow the step to produce the certificate on win2003 server. 2. I found a tool "makecert.exe" that mention in the mobile5 document. I can get a private certificate and import it to IE. But when I run "Imagehash flash.bin flash_sign.bin 1024" and select the certificate, it always return "An error ocurred during signing". 3. I use "signimage.exe" to hash my image, but when I use SBL_VerifyPacket() to unhash the code, it always return error code "0x80004005" Thanks. Tag: A problem about USB serial Driver?? Tag: 87671
  - 3
    - USB Bluetooth adapter not working Hi, I'm having a problem getting a Belkin Bluetooth USB adapter (Model: F8T012) working with my WinCE 5.0 device, a Kontron X-Board <PXA> development board. In the WinCE image I built, I made sure to include the following catalog items: OBEX File Browser (SYSGEN_OBEX_FILEBROWSER) Bluetooth PAN (SYSGEN_BTH_PAN) Bluetooth DUN Gateway (SYSGEN_BTH_MODEM) Bluetooth HID - Keyboard (SYSGEN_BTH_HID_KEYBOARD) Bluetooth HID - Mouse (SYSGEN_BTH_HID_MOUSE) Bluetooth Stack with Universal Loadable Driver (SYSGEN_BTH) The image boots up ok. Upon connecting the USB Bluetooth adapter an extra network interface (BTPAN1) appears down the bottom of the screen. I then go into control panel and double click the Bluetooth Device Properties to bring up the "Bluetooth Manager" and press the Scan Device button. After some searching, the bluetooth device I am trying to connect to (an iPAQ PDA with inbuilt bluetooth) appears in the Untrusted list with a question mark next to its name. I can authorise the PDA by clicking the --> button and entering a PIN code. The PDA then asks me to enter the same PIN code, and when I do the PDA now moves to the Trusted list. My problem is that while I can detect the PDA fine, I cannot transfer any data or use any of the services the PDA is set up to offer. I have tested the Bluetooth adapter on my PC and was able to transfer files to and from the PDA, but it seems to me that the X-Board is not able to detect what Bluetooth services the PDA is offering. The problem is not unique to the PDA, it also happens with two mobile phones with inbuilt bluetooth I have tried. I followed the instructions at http://support.microsoft.com/kb/328900/en-us and got the following result when running btdc.exe: > readbd BthReadLocalAddr returns 0x00000000 0, address = 00003a690354 > inquiry 0x0 0x1e 0x5 BthPerformInquiry returns 0x00000000 0 001237b44f1b cod = 0x00020110 clock = 0x5d31 page = 0 period = 0 repetition = 1 > l2cap load L2CAPLoad : 1062 > ping 001237b44f1b L2CAPPing returns 0x00000426 (1062) > l2cap seems to always return error 1062 (service has not been started, correct?) I tried building a debug WinCE image, but it didn't want to boot up, so I created a release image using some of the debug DLLs (btd.dll, bthusb.dll, bthuniv.dll) instead. The debugger output didn't seem particularly helpful though... a lot of normal looking messages would appear when running the inquiry, but nothing when "l2cap load" or "ping" was run. I can post a copy of the debug output if anyone thinks it would would help. Can anyone help me with this? Is it possible that the adapter isn't supported by WinCE (the box says it uses Bluetooth standard 2.0 + EDR, so its probably a CSR BlueCore4 chipset)? On that thought, is there a list of supported Bluetooth adapters for WinCE 5.0? Thanks in advance, Derrick. Tag: A problem about USB serial Driver?? Tag: 87669
  - 4
    - Calculating a function from which the last call has been made Hi, Could somebody tell if I am properly calculating a function from which the last call has been made and exception occurred? Exception: 8756624: RaiseException: Thread=8a051bac Proc=856f7680 'gwes.exe' 8756643: AKY=00000019 PC=00000000(???+0x00000000) RA=8415165c(NK.EXE+0x0003165c) BVA=00000003 FSR=00000003 8756674: Exception 'RaiseException' Thread=8a051bac AKY=ffffffff PC=84151ec4 BVA=00000003 8756700: R0=a5713000 R1=a4046000 R2=00967000 R3=fffff000 8756718: R4=84151604 R5=ffffc7a4 R6=8415165c R7=841275f4 8756736: R8=00000000 R9=856d62dc R10=ffffcbc0 R11=00000010 8756754: R12=00000000 SP=00202000 Lr=856f6fe0 Psr=a000001f 8756771: Halting system NK.MAP Excert: . . 0001:0003136c ScavengeStacks 8483236c f nk:physmem.obj 0001:00031584 HoldPages 84832584 f nk:physmem.obj 0001:00031814 GetContiguousPages 84832814 f nk:physmem.obj. . The function is HoldPages since 0x0003165c is greater then HoldPages' address but less than GetContiguousPages' address. Also what can cause this. I do not have source code for HoldPages to find this out on my own. Thanks, -PK Tag: A problem about USB serial Driver?? Tag: 87659
  - 5
    - Static and dynamic IP on the same adapter Has anyone assigned a static IP to an adapter that already had an IP from DHCP? If so, did you run into any issues with it? Are there any gotchas to be aware of? Tag: A problem about USB serial Driver?? Tag: 87654
  - 6
    - Installation of Networked Media Device Feature Pack (part deuce) This is continued from here (I could not post because it is more than 30 days old): http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_frm/thread/7f3f3519e53feb2d/75180168413bbd25?lnk=st&q=Networked+Media+Device&rnum=1&hl=en#75180168413bbd25 I had the same error: "Windows CE 5.0 Networked Media Device Feature Pack cannot install one of its required products. Contact your technical support group." Well I contacted my technical support group, they told me to install the x86 versions as well as the ARMV4I versions. This is because when I installed PB 5.0 I selected the ARMV4I and x86 architectures. So you have to install the updates for all architectures for which PB 5.0 was installed on your workstation. -J Tom Moon Qualnetics Tag: A problem about USB serial Driver?? Tag: 87651
  - 7
    - IPSM under Windows CE 4.2 on StrongArm 1100 CPU Hello, I have tried and tried to get the IPSM 3.7 and 3.8 to work on my old StrongArm SA1100 and Intel Strata flash based system with Windows CE 4.2. It never starts and the debug fails with an "illegal instruction" at an instruction right at the start of the IPSM initialisation code. The instruction is "bx lr" and I assume this is an Xscale instruction that then fails on my StrongArm... Does anyone know what was the last version of the IPSM 3.6 or 2.6? to support strongarm CPUs and that someone got working with Windows CE 4.2. I have asked Intel in the USA and the UK, neither have been able to answer me. Interestingly, by confusing me further is that this web page says that IPSm is included in Windows CE 4.2, but the Microsoft documentation on the Platform Builder installation says that it is not hthere and I can't find it. http://msdn.microsoft.com/embedded/usewinemb/ce/drivers/supdrivers/default.aspx Thanks Simon Tag: A problem about USB serial Driver?? Tag: 87649
  - 8
    - Edge triggered interrupts Hi, i have the common scneario in that i have a few level triggered ints wired in to one of the PXA270 GPIOXX_2 lines. I have seen in the archives a suggested solution is to treat this as a shared interrupt and call NKcallIntChian. I was wondering why this complexity Can it not jut be done by in the ISR checking the GPIOXX_2 bit in the ICMR then further checking which one of the io lines it is. Then disabling the interrupt at the peripheral device, this prevents rentrency in to the IST. Once the interrupt is processed reeenable the interrupt at the device say in the InterruptDone. Pending interrupts in the device will raise an edge again. This solves missing edges and reentrancy issues surely or have i missed something? I thought NKcallInt Chain was more for PCI devices where you have different cards plugged in at any give time. In my scenario i have fixed hardware. Tag: A problem about USB serial Driver?? Tag: 87634
  - 9
    - Building files in directory wince500\private\ Hi, I made some changes to the file wince500\private\winceos\coreos\nk\kernel\arm\mdarm.c. But could not build it thought PB. Is it possible to compile those files. Thanks, Shiju Tag: A problem about USB serial Driver?? Tag: 87632
  - 10
    - PB monthly update June 2006 Hi! After installing the PB monthly updates for May and June 2006, I get the following error when bulding a project that it used to work before: wmt_splitter.lib(nssplit.obj) : error LNK2019: unresolved external symbol "public: long __cdecl CASFMMStream::LoadHeader (unsigned char *, unsigned long, unsigned long*, unsigned long) " bla bla ... referenced in function "private: long __cdecl CNSSource::RebuildFromHeader (struct IWMediaStreamBuffer* ) etc... I had to put back the wmt_splitter.lib from 16.Nov.2005 in C:\WINCE500\PUBLIC\DIRECTX\OAK\LIB\ARMV4I\RETAIL in order to get rid of this error. However, I won't be able to use the new fixes like this. Could you tell me in wich module RebuildFromHeader has to be? Did it went something wrong during the updates? Any advice would be greatly appreciated. Best regards, Draghi Puterity Tag: A problem about USB serial Driver?? Tag: 87625
  - 11
    - HTTPD configuration hi all, in my platform I've just configurated HTTPD services; in project.reg in HKLM/Ident I've changed the field name but if I request http://localhost/remoteadmin/DeviceConfig.htm, the Device Name field is empy. Why ? Thanks in advance Stefano Tag: A problem about USB serial Driver?? Tag: 87624
  - 12
    - question about extern card dear all, I have a question about PPC extern card (SD card ,CF card,T card...).Could you tell me PPC support the card of capacity exceed 4GB? Tag: A problem about USB serial Driver?? Tag: 87623
  - 13
    - WIN CE KERNEL SPACE MY QUESTION WHETHER NK.EXE RUNS IN KERNEL SPACE OR USER SPACE.SINCE ONLY 32 PROCESS ARE POSSIBLE TO RUN AT A TIME ,THERE ARE ONLY 33 SLOTS OF WHICH SLOT 0 IS BEING USED BY ACTIVE PROCESS AND SLOT 1 FOR ROM BASED DLLS.BUT ONLY 31 SLOTS ARE REMAINING HOW COME 32 PROCESS RUN AT A TIME?? Tag: A problem about USB serial Driver?? Tag: 87622
  - 14
    - Hive bsed Registry using DiskOnChip Hi, I tried to use hive based registry on a device with storage medium an M-System's "DiskOnChip 2000". I added the Platform builder component "Hive bsed Registry" and the following lines in registry: [HKEY_LOCAL_MACHINE\init\BootVars] "SystemHive"="DiskOnChip\\System\\system.hv" "ProfileDir"="DiskOnChip\\System" "Flags"=dword:3 But the resulting image (NK.BIN) does not work (the system does not start). Can anyone help me? Thank you. Tag: A problem about USB serial Driver?? Tag: 87621
  - 15
    - Sychip SD WLAN card where to buy ? Hello, once more I want to ask if somebody knows where (which brand) it is possible to buy the Sychip WLAN6060 SDIO card ? I want this card because as far as I know the driver is included in the platbuilder 5.0 or not ? I know that there are several other cards on the market (Spectec, Socket, ...) and they have their own driver for WinCE5.0, but unfortunally I'am using a SH4 =B5C and all the drivers are for some ARM9 derivates. So please help me !! Thanks Tag: A problem about USB serial Driver?? Tag: 87618
  - 16
    - BUG in FSDMGR.dll CeGetVolumeInfo() will not work properly I'm using WinCE 5.0 with all the latest QFEs (until June 2006). CeGetVolumeInfo() seems not to return all the info as it should!! For example it cannot be used to find out of a volume is using TFAT or not, as the CE_VOLUME_TRANSACTION_SAFE flag will never be set, even if the volume is TFAT! First I thought that maybe i was not really formatting my volume with TFAT, so i spent hours trying to find out what i was doing wrong. Finally i decided to debug the problem in Platform Builder and I found out that i the volume was 100% TFAT (reported as debug message). So i set a breakpoint in the FSDMGR_GetVolumeInfo() and found out that there must be something wrong there... In fsdapis.cpp, line 1458: Shouldn't it be pVol->dwVolData instead of pVol->pDsk for the first paramenter of pVol->pDsk->pFSD->pGetVolumeInfo() ? I tried to verify this by resetting the pointer in the debugger and it seems to work. Corey, or some other MS guy, can you confirm this as a BUG and how soon will this be released as a QFE? Any chance to include it in the July QFE? I could change that myself, but since it's in the private code i will not be allowed to use this in a retail product. -- John Tag: A problem about USB serial Driver?? Tag: 87614
  - 17
    - Running a bat file at windows CE boot Hi All: I want to start a bat file at windows ce startup. I tried to modify "HKEY_LOCAL_MACHINE\init" in the registry but did not work out. I suspect it only accepts exe's. Then I have tried to make small exe application and launch a bat file, but have not succeeded there either. My sourcode looks like: PROCESS_INFORMATION pi; ZeroMemory(&pi, sizeof(pi)); if (CreateProcess(TEXT("\\windows\\cmd.exe"),TEXT("/C \\windows\\IBMjvm.bat"), NULL, NULL, FALSE,CREATE_NEW_CONSOLE, NULL, NULL, NULL, &pi)) { CloseHandle(pi.hThread); CloseHandle(pi.hProcess); } WaitForSingleObject(pi.hProcess, INFINITE); Sleep(1000); return 0; This small exe application can launch IBMjvm.bat if I run it under telnet console instead of runing at the boot time. Please help, Chuck dot Lin at Symbol dot Com Tag: A problem about USB serial Driver?? Tag: 87603
  - 18
    - eboot If I create a boot loader (eboot) using platform builder, can I download it using URT? Tag: A problem about USB serial Driver?? Tag: 87600
  - 19
    - Problem assigning a 2nd IP address to an adapter We have a CE device that is connected to a modem/router via USB using RNDIS. We have the ability to download either a VxWorks or Linux image to the modem and boot it into either mode. The modem can be soft booted independently of the CE side. This has worked fine so far under VxWorks. Because of some limitations in Linux, we've had to statically assign a 2nd IP address to the USB8023 ethernet adapter so it can talk to the modem (which in Linux mode has its own statically-assigned IP address). When we reboot under Linux, the USB bus resets and when Linux comes back up I believe the USB host driver should enumerate the devices, find device #1, and bind the ethernet adapter. The Linux boot takes about 30 seconds. However, after adding the 2nd IP address we've noticed a phenomenon that has stopped us cold. The adapter gets unbound but it then goes into an indeterminate state. The adapter icon isn't visible from the "Network Connections" window, but the adapter symbol is visible on the shell's start bar. Tapping the symbol to bring up the adapter dialog shows the standard dialog, but with no information. The CE side can't be pinged and it appears that the CE network stack is hosed at that point. Enumerating through the available adapters show that none is present. At the bus level using a protocol analyzer, we find that when this happens, CE enumerates the USB bus and finds the adapter as device #2 when it should be device #1. (Our CE side has a limitation of 1 USB device.) A reset of CE clears up the problem, but that's not an acceptable solution. We need to find out why 1) CE is finding device #2 on the USB bus 2) The USB8023 driver is dying Some notes: - I can also make this fail with a modified unit that brings out the USB connection out on two cables that can be physically unplugged. Unplugging and replugging this connection works fine until I add the 2nd IP address. After that, I get about 1 - 4 unplug/replugs before the adapter goes into the indeterminate state. - One hunch that we've had so far is that it's a timing issue, as our Linux image is slower than the VxWorks one. - Is there a way to reset the USB80231 driver (not DeactivateDevice) without unloading and reloading it? TIA, Dan. Tag: A problem about USB serial Driver?? Tag: 87599
  - 20
    - Rotating the touch (without rotating the display) Hi guys, I've got a device that uses a display with touch and has the display data fed through an FPGA before sending it to the display. A user is able to flip the screen (physically), and the FPGA notices this and rotates the screen. However, the FPGA does not know/can not rotate the touch input. Is there any way to tell GWES that the display is rotated and touch data should be interpreted in a rotated way? The help suggests that when a display is rotated (through display driver changedisplaysettingsex() ) it tells GWES to change the touch input as well. I don't see this happening (but maybe that's because my display driver does not support rotating?). Any thoughts on how to achieve this? Currently I'm thinking to implement this in the touch driver recalculating the coordinates right there, unless I can find the magic GWES call to fix it for me ;-) Thx, Niels Brouwers Chess Tag: A problem about USB serial Driver?? Tag: 87598
  - 21
    - Query about Pictbridge hi, We got a requirement to implement Pictbridge protocol for our board. I searched in net and got some basic idea about this protocol. If anyone has worked on this protocol, pls guide me about its implementation and pls let me know from where i can get pictbridge specification. any reference code is available in net? Thanks inadvance, Rajesh Tag: A problem about USB serial Driver?? Tag: 87597
  - 22
    - passive kitl on ce 4.2 Hi, I want a possibility to debug a device without the need to download the image and being connected to the device all the time. We have a x86 platform. I tried to start the ce image including loaddbg.exe and kd.dll on my target and starting loaddbg. After that I tried to connect to my target using the connect menu entry in the the IDE. But it doesn't work. I also initialized kitl using KitlInit(FALSE). Any ideas? thanks in advance regards Reinhold Tag: A problem about USB serial Driver?? Tag: 87595
  - 23
    - How to debug WinCE using E10A Hello , I am a newbie to WINCE and i dont have any knowledge of E10A... but i want to debug Wince using E10A.....can any one guide me or give me the link where i can find the help.......... please help me out its very urgent thanks in advance Meenal Tag: A problem about USB serial Driver?? Tag: 87594
  - 24
    - wince5.0 FAT system Hi all, I had developed CF memory card driver in wince5.0.I test CF write/read speed through copying file to/from sdram. the read speed:330KB/s the write speed:900KB/s Then I test CF write/read speed through IOControl funtions that operate read/write functions directly and not through FAT system the read speed:4.4MB/s the write speed:1.8MB/s Why is its speed different so big,especially reading speed? Why is the efficiency of wince fat system so low? I had test ramdisk driver read/write speed in fatsystem and IOControl funtions way,and the speed different is too so big! Tag: A problem about USB serial Driver?? Tag: 87593
  - 25
    - Wireless CETK tests wzctooltest.dll Hello, I'm testing my SDHC driver on WinCE5.0. I'm using Sandisk Connect Wi-Fi (SDWSDB-000) SDIO card. My Wi-Fi SDIO driver is pegasSDN.dll, shipped along with WinCE. I modified the sorce for wzctooltest as per the instructions given in http://groups.google.com.sg/group/microsoft.public.windowsce.platbuilder/browse_frm/thread/20c5c19dafa6c21d/c76d850952448317?hl=en&lr=&rnum=2&prev=/groups%3Fq%3DXWIFI11B1%26hl%3Den%26lr%3D%26group%3Dmicrosoft.public.windowsce.platbuilder.*%26selm%3D019e01c4b557%252400c1f570%25243a01280a%2540phx.gbl%26rnum%3D2#c76d850952448317 I have tests #411, #412, #413 and #451 fail. During these tests, my wireless card is not supposed to get a valid IP address over DHCP from the AP. But in my case, I see that I get the same IP I got during test #410. The log is given below. <TESTGROUP> *** ================================================================== *** SUITE INFORMATION *** *** Suite Name: N/A (built on the fly) *** Suite Description: N/A *** Number of Tests: 9 *** ================================================================== *** ================================================================== *** SYSTEM INFORMATION *** *** Date and Time: 01/01/2003 2:55 PM (Wednesday) *** *** Device Name: MX3130583 *** *** OS Version: 5.0 *** Build Number: 1400 *** Platform ID: 3 "Windows CE" *** Version String: "" *** *** Processor Type: 0x00000B36 (2,870) "Unknown" *** Processor Architecture: 0x0005 (5) "ARM" *** Page Size: 0x00001000 (4,096) *** Minimum App Address: 0x00010000 (65,536) *** Maximum App Address: 0x7FFFFFFF (2,147,483,647) *** Active Processor Mask: 0x00000001 *** Number Of Processors: 1 *** Allocation Granularity: 0x00010000 (65,536) *** Processor Level: 0x0004 (4) *** Processor Revision: 0x0004 (4) *** ================================================================== *** ================================================================== *** MEMORY INFO *** *** Memory Total: 57,139,200 bytes *** Memory Used: 10,305,536 bytes *** Memory Free: 46,833,664 bytes *** *** Kernel Used: 561,152 bytes *** Water Mark: 11,433 pages *** *** Store Total: 57,036,800 bytes *** Store Used: 293,036 bytes *** Store Free: 56,743,764 bytes *** ================================================================== <TESTCASE ID=410> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-WEP40 *** Test ID: 410 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 16918 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-WEP40 -auth open -encry wep key 1/0x1234567890 ECHO:command wzctool -c -ssid CE-WEP40 -auth open -encr wep -key 1/0x1234567890 ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 192.168.1.103 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO: Default Gateway ... : 192.168.1.1 ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 192.168.1.103 ECHO:expected 192.168., current IP =192.168.1.103 (pass) SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-WEP40 *** Test ID: 410 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Passed *** Random Seed: 16918 *** Thread Count: 1 *** Execution Time: 0:00:06.031 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="PASSED"> <TESTCASE ID=411> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-WEP40 (incorrect WEP key index) *** Test ID: 411 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 22517 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-WEP40 -auth open -encry wep key 2/0x1234567890 ECHO:command wzctool -c -ssid CE-WEP40 -auth open -encr wep -key 2/0x1234567890 ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 192.168.1.103 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO: Default Gateway ... : 192.168.1.1 ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:192.168.1.103 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 192.168.1.103 FAIL:expected 169.254., current IP =192.168.1.103 (FAIL) SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-WEP40 (incorrect WEP key index) *** Test ID: 411 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Failed *** Random Seed: 22517 *** Thread Count: 1 *** Execution Time: 0:00:11.087 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="FAILED"> <TESTCASE ID=412> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-WEP40 (incorrect WEP key value) *** Test ID: 412 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 8033 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-WEP40 -auth open -encry wep key 1/0x0987654321 ECHO:command wzctool -c -ssid CE-WEP40 -auth open -encr wep -key 1/0x0987654321 ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 192.168.1.103 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO: Default Gateway ... : 192.168.1.1 ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 192.168.1.103 FAIL:expected 169.254., current IP =192.168.1.103 (FAIL) SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-WEP40 (incorrect WEP key value) *** Test ID: 412 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Failed *** Random Seed: 8033 *** Thread Count: 1 *** Execution Time: 0:00:24.203 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="FAILED"> <TESTCASE ID=413> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-WEP40 (without WEP encryption) *** Test ID: 413 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 26271 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-WEP40 ECHO:command wzctool -c -ssid CE-WEP40 ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 192.168.1.103 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO: Default Gateway ... : 192.168.1.1 ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 192.168.1.103 FAIL:expected 169.254., current IP =192.168.1.103 (FAIL) SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-WEP40 (without WEP encryption) *** Test ID: 413 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Failed *** Random Seed: 26271 *** Thread Count: 1 *** Execution Time: 0:00:26.360 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="FAILED"> <TESTCASE ID=450> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-ADHOC1 *** Test ID: 450 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 20292 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-ADHOC1 -adhoc ECHO:command wzctool -c -ssid CE-ADHOC1 -adhoc ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 169.254.149.138 ECHO: Subnet Mask ....... : 255.255.0.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 169.254.149.138 ECHO:expected 169.254., current IP =169.254.149.138 (pass) SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-ADHOC1 *** Test ID: 450 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Passed *** Random Seed: 20292 *** Thread Count: 1 *** Execution Time: 0:00:23.518 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="PASSED"> <TESTCASE ID=451> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-ADHOC1 *** Test ID: 451 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 767 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-ADHOC1 -encry wep key 1/0x1234567890 -adhoc ECHO:command wzctool -c -ssid CE-ADHOC1 -encry wep key 1/0x1234567890 -adhoc ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 0.0.0.0 ECHO: Subnet Mask ....... : 0.0.0.0 ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 0.0.0.0 FAIL:WIFI1 has IP address 0.0.0.0 SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-ADHOC1 *** Test ID: 451 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Failed *** Random Seed: 767 *** Thread Count: 1 *** Execution Time: 0:02:36.137 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="FAILED"> <TESTCASE ID=452> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -c -ssid CE-ADHOC2 *** Test ID: 452 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 2543 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:WARNING this test needs XWIFI11B1 [has PEGASSDN1] ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:wzctool -c -ssid CE-ADHOC2 -adhoc ECHO:command wzctool -c -ssid CE-ADHOC2 -adhoc ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:waiting for PEGASSDN1 gets an address ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 169.254.149.138 ECHO: Subnet Mask ....... : 255.255.0.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 169.254.149.138 ECHO:expected 169.254., current IP =169.254.149.138 (pass) SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -c -ssid CE-ADHOC2 *** Test ID: 452 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Passed *** Random Seed: 2543 *** Thread Count: 1 *** Execution Time: 0:00:04.985 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="PASSED"> <TESTCASE ID=502> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool -registry *** Test ID: 502 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 8342 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:[HKEY_CURRENT_USER\Comm\WZCTOOL] deletion failed (this key might not exist) ECHO:wzctool -registry (for CE_WEP40) ECHO:command wzctool -registry ECHO:g_szCommandOutput[] = ECHO:wireless card found: PEGASSDN1 ECHO:invalid key value ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 169.254.149.138 ECHO: Subnet Mask ....... : 255.255.0.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 169.254.149.138 ECHO:[HKEY_CURRENT_USER\Comm\WZCTOOL] deleted SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool -registry *** Test ID: 502 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Passed *** Random Seed: 8342 *** Thread Count: 1 *** Execution Time: 0:00:58.760 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="PASSED"> <TESTCASE ID=503> *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: wzctool *** Test ID: 503 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Random Seed: 27280 *** Thread Count: 0 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv SPM_BEGIN_TEST ECHO:command wzctool -reset ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 169.254.149.138 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:WiFi card reset done. ([Preferred List] is cleared) ECHO:[HKEY_CURRENT_USER\Comm\WZCTOOL] deletion failed (this key might not exist) ECHO:wzctool (without any argument, with registry set for CE_WEP40) ECHO:command wzctool ECHO:g_szCommandOutput[] = ECHO:trying to read registry and configure wireless settings ECHO:security warning: storing encryption key in clear text is volunerable to attack. ECHO:wireless card found: PEGASSDN1 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 0.0.0.0 ECHO:[PEGASSDN1] IpAddress ----> 192.168.1.103 ECHO:command ipconfig ECHO:g_szCommandOutput[] = ECHO:Windows IP configuration ECHO:Ethernet adapter [VMINI1]: ECHO: IP Address ........ : 10.232.185.69 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::1013:17ff:fe28:7777 ECHO: Default Gateway ... : 10.232.185.254 ECHO:Ethernet adapter [PEGASSDN1]: ECHO: IP Address ........ : 192.168.1.103 ECHO: Subnet Mask ....... : 255.255.255.0 ECHO: IP Address ........ : fe80::20b:6cff:fe1f:c70b ECHO: Default Gateway ... : 192.168.1.1 ECHO:Tunnel adapter []: ECHO: Interface Number .. : 4 ECHO:Tunnel adapter [6to4 Pseudo-Interface]: ECHO: Interface Number .. : 3 ECHO:Tunnel adapter [Automatic Tunneling Pseudo-Interface]: ECHO: Interface Number .. : 2 ECHO: IP Address ........ : fe80::5efe:10.232.185.69 ECHO: DNS Servers........ : 10.211.0.3 ECHO: 10.211.0.131 ECHO: 192.168.1.1 ECHO:IP Address = 192.168.1.103 ECHO:[HKEY_CURRENT_USER\Comm\WZCTOOL] deleted SPM_END_TEST *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ *** TEST COMPLETED *** *** Test Name: wzctool *** Test ID: 503 *** Library Path: \release\wzctooltest.dll *** Command Line: *** Result: Passed *** Random Seed: 27280 *** Thread Count: 1 *** Execution Time: 0:00:13.465 *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ </TESTCASE RESULT="PASSED"> *** ================================================================== *** MEMORY INFO *** *** Memory Total: 57,139,200 bytes *** Memory Used: 10,407,936 bytes *** Memory Free: 46,731,264 bytes *** *** Kernel Used: 573,440 bytes *** Water Mark: 11,380 pages *** *** Store Total: 57,036,800 bytes *** Store Used: 308,812 bytes *** Store Free: 56,727,988 bytes *** ================================================================== *** ================================================================== *** SUITE SUMMARY *** *** Passed: 5 *** Failed: 4 *** Skipped: 0 *** Aborted: 0 *** -------- --------- *** Total: 9 *** *** Cumulative Test Execution Time: 0:05:24.546 *** Total Tux Suite Execution Time: 0:05:26.215 *** CPU Idle Time: 0:05:02.683 *** ================================================================== </TESTGROUP> @@@@@@4 NOTE: If I run any of these failing test cases alone, they all pass, meaning my card can't lease a valid IP address. And the AP does not allow me to connect to the internet and browse, if I give incorrect key or index. --Inder Tag: A problem about USB serial Driver?? Tag: 87591

I connect pxa27x to PC by usb serial, I have installed activesync
4.1. But the USB device on PC shows that the USB driver is corrected
and not usable.
my paltform.reg is:
HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class]
"Dll"="serialusbfn.dll"
"InterfaceSubClass"=dword:ff
"InterfaceProtocol"=dword:ff
"DeviceName"="USBFNS1:"
; "DeviceName"="UFN1:"
"Tsp"="Unimodem.dll"
"FriendlyName"="USB Cable:"
"Prefix"="COM"
; "DeviceArrayIndex"=dword:0
"DeviceArrayIndex"=dword:2
"DeviceType"=dword:0
"IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}"
; "IClass"="{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}"
; idVendor must be changed. 045E belongs to Microsoft and is only to be

used for
; prototype devices in your labs. Visit http://www.usb.org to obtain a
vendor id.
"idVendor"=dword:045E
; "idVendor"=dword:8086
"Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change
idVendor)"
; "Manufacturer"="Intel"
"idProduct"=dword:00ce
; "idProduct"=dword:A6CD
"Product"="Generic Serial (PROTOTYPE--Remember to change idVendor)"
; "Product"="WindowsCE.NET 5.0"
"bcdDevice"=dword:0

The "DeviceArrayIndex" is set to 2, so it could not load serial
driver, it must be 0 or 1. 0 would load USBSerialFN class, 1 would load

USBSerserialFN, which number could I choose?

Top