WinCE <-> WinXP (serial over USB)

TheMSsForum.com: The Microsoft Software Forum

The MSS Forum ‹ Drivers
- Archive
  - Biz
  - MCSE
  - CRM
  - Drivers
  - Framework
  - ADO
  - ASP
  - Compact
  - Forms
  - Dotnet
  - C#
  - VB
  - FontpageGen
  - Excel
  - WorkSheet
  - Exchange
  - Setup
  - Fox
  - Fontpage
  - ASP
  - IIS
  - Entourage
  - Money
  - Messanger
  - PocketPC
  - Powerpoint
  - Project
  - Publisher
  - Excel
  - VB
  - Security
  - Portal
  - Services
  - SQLServerDev
  - SVCS
  - SQLServer
  - VB
  - VC
  - MFC
  - ExcelGen

- Previous
  - 1
    - DeviceIoControl Usage User mode code uses an overlapped call of DeviceIoControl to send an IOCTL to my driver. This operation normally takes quite a long time to process. I notice that DeviceIoControl is not returning immediately. Do I need to mark the Irp as STATUS_PENDING in order for DeviceIoControl to return? Also, if I re-use the original Irp, and data is being passed back to the User code, do I have to lock the buffer somehow? Thanks in advance, Dennis Tag: WinCE <-> WinXP (serial over USB) Tag: 52103
  - 2
    - Cannot get an array from a WMI method I have a WDM driver that is a WMI provider. Everything works fine if its methods report output parameters such as uint8. But I need a method to report a binary array. If I simply change a uint8 output parameter to a fixed length array of uint8's, then when my Win32 C++ app calls IWbemClassObject->Get to get the output data from ExecMethod, it succeeds but the varaint is type VT_NULL (note the CIMTYPE reported by this call on the other hand seems accurate--VT_ARRAY|VT_UI1). I can't figure out how to access the array returned because all I get is VT_NULL. Below is the Win32 Get call and the MOF. Is there something special that needs done to pass arrays? Any suggestions? _variant_t v; CIMTYPE CimType; HRESULT hRes = OutParms->Get(_bstr_t(L"Info"), 0, &v, &CimType, 0); --------------- [Description("Test API"), WMI, Dynamic, Provider("WMIProv"), guid("{692BFCA9-9EEB-45d7-8621-4E59D993DB90}"), locale("MS\\0x409")] class TestApi { [key, read] string InstanceName; [read] boolean Active; [WmiMethodId(1), Implemented, Description("Get Info")] void GetInfo([out, Description("Information")] uint8 Info[4]); }; Tag: WinCE <-> WinXP (serial over USB) Tag: 52100
  - 3
    - How to disable/block USB ports Hi, I have a server that I wish to disable / block the USB ports for security without physically damaging the USB ports. Has anyone any ideas on how to do this in software or has someone got sample code I can leech? Thanx in advance. Tag: WinCE <-> WinXP (serial over USB) Tag: 52096
  - 4
    - OT: The New Forger's Dictionary A friend of mine has posted a takeoff on "The New Hacker's Dictionary" (TNHD), defining new means for words as used in specialized contexts. See http://www.eclectic-eng.com/forged.htm. Example: Authentic [adj] (1) worthy of acceptance or belief. Trustworthy (2) not imaginary, false, or imitation (3) [CBS] A document which can be held in the hand. Common usage: "the document we have is an authentic document". Fans of TNHD might enjoy this site, so I'm sharing it with you. (It seems, by the way, that I, and the hundreds of other experts in a variety of domains, that weighed in on the "authentic" CBS documents seem to have won. However, I think I may the only MVP that participated in this discussion) joe Joseph M. Newcomer [MVP] email: newcomer@flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm Tag: WinCE <-> WinXP (serial over USB) Tag: 52080
  - 5
    - WPA2 supplicant beta Hi, I was told there is WPA2 supplicant beta avaliable. Can someone tell me where to signup for that. We need it to implement the support for WPA2. Thanks. -Paul Tag: WinCE <-> WinXP (serial over USB) Tag: 52079
  - 6
    - PCI enumeration Hi, Is there a PCI functions library/sample code in DDK which will allow me to enumerates PCI devices and does reads in PCI config space. or DOS tool for which source is available which does something similar Thanks, Hemant Tag: WinCE <-> WinXP (serial over USB) Tag: 52078
  - 7
    - dvd layer descriptor information dear friends, I am querying the dvd with the api DeviceIOControl with the control code IOCTL_DVD_READ_STRUCTURE and acquiring the dvd layer descriptor. sometimes I am getthe layer descriptor BCAFlag value as 1 though dvd is not a BCA enabled disc. any suggestion is greatful -- thnaks iyappan Tag: WinCE <-> WinXP (serial over USB) Tag: 52077
  - 8
    - faile in co0mpiling EPassThru example on one of the computers hello All I'm trying to compile the EPassThru example with the Windows DDK Server 2003 on a Windows 2000 environmnet... in Microsoft Visual Studio 6.0 I have also using the ddkbuild (free ware).... now I'm compiling successfully on one of the computers but failing on the other one... The envrionment is quite the same on both: running windows 2000 env variable is set to W2KBASE c:\WINNT Visual Studio 6.0 IDE the directory path for both are c:\d\CProjects\TDI-NDIS\EPassThru I'm using ddkbuild from Hollis Technology solution on both and run the bat file the same way and have the same project setting on both... and here is the error I'm getting on the pc... its basically error on one of the .h files which is exact copy of the same in on the other laptop.. I assume there should be some settings that I'm not aware of... could you please help me???? Deleting intermediate files and output files for project 'EPassThru - Win32 Debug'. --------------------Configuration: EPassThru - Win32 Debug-------------------- DDKBUILD VERSION 3.9.27 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS Comments? Suggestions? info@hollistech.com New or updated MSVC detected. Updating DDK environment.... Setting environment for using Microsoft Visual C++ tools. Starting dirs creation...Completed. DDKBUILD using W2K DDK in directory . for checked version (basedir c:\NTDDK extension chk) commandline: "build -cfe " BUILD: Object root set to: ==> objchk BUILD: /i switch ignored BUILD: Compile and Link for i386 BUILD: Loading c:\NTDDK\build.dat... BUILD: Computing Include file dependencies: BUILD: c:\program files\microsoft visual studio\vc98\include\exdisp.odl(31): c:\program files\microsoft visual studio\vc98\include\exdisp.odl - invalid include statement: importlib(STDOLE_TLB); BUILD: c:\program files\microsoft visual studio\vc98\include\vidsvr.odl(16): c:\program files\microsoft visual studio\vc98\include\vidsvr.odl - invalid include statement: importlib(STDOLE_TLB); BUILD: c:\progra~1\micros~3\vc98\include\exdisp.odl(31): c:\progra~1\micros~3\vc98\include\exdisp.odl - invalid include statement: importlib(STDOLE_TLB); BUILD: c:\progra~1\micros~3\vc98\include\vidsvr.odl(16): c:\progra~1\micros~3\vc98\include\vidsvr.odl - invalid include statement: importlib(STDOLE_TLB); BUILD: Examining c:\epassthru directory for files to compile. c:\epassthru c:\epassthru - 6 source files (4,481 lines) BUILD: Saving c:\NTDDK\build.dat... BUILD: Compiling c:\epassthru directory Compiling Precompiled Header - precomp.h for i386 ptextend.h(130) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(130) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(130) : error C2061: syntax error : identifier 'pIrp' ptextend.h(130) : error C2059: syntax error : ';' ptextend.h(131) : error C2059: syntax error : ')' ptextend.h(141) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(141) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(141) : error C2061: syntax error : identifier 'pIrp' ptextend.h(141) : error C2059: syntax error : ';' ptextend.h(142) : error C2059: syntax error : ')' ptextend.h(147) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(147) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(147) : error C2061: syntax error : identifier 'pIrp' ptextend.h(147) : error C2059: syntax error : ';' ptextend.h(148) : error C2059: syntax error : ')' ptextend.h(153) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(153) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(153) : error C2061: syntax error : identifier 'pIrp' ptextend.h(153) : error C2059: syntax error : ';' ptextend.h(154) : error C2059: syntax error : ')' Compiling Precompiled Header - precomp.h for i386 ptextend.h(130) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(130) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(130) : error C2061: syntax error : identifier 'pIrp' ptextend.h(130) : error C2059: syntax error : ';' ptextend.h(131) : error C2059: syntax error : ')' ptextend.h(141) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(141) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(141) : error C2061: syntax error : identifier 'pIrp' ptextend.h(141) : error C2059: syntax error : ';' ptextend.h(142) : error C2059: syntax error : ')' ptextend.h(147) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(147) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(147) : error C2061: syntax error : identifier 'pIrp' ptextend.h(147) : error C2059: syntax error : ';' ptextend.h(148) : error C2059: syntax error : ')' ptextend.h(153) : error C2146: syntax error : missing ')' before identifier 'pIrp' ptextend.h(153) : error C2081: 'PIRP' : name in formal parameter list illegal ptextend.h(153) : error C2061: syntax error : identifier 'pIrp' ptextend.h(153) : error C2059: syntax error : ';' ptextend.h(154) : error C2059: syntax error : ')' Compiling - passthru.rc for i386 Compiling - miniport.c for i386 miniport.c(30) : error C1083: Cannot open precompiled header file: 'objchk\i386\precomp.pch': No such file or directory Compiling - passthru.c for i386 passthru.c(31) : error C1083: Cannot open precompiled header file: 'objchk\i386\precomp.pch': No such file or directory Compiling - protocol.c for i386 protocol.c(31) : error C1083: Cannot open precompiled header file: 'objchk\i386\precomp.pch': No such file or directory Compiling - ptextend.c for i386 ptextend.c(4) : error C1083: Cannot open precompiled header file: 'objchk\i386\precomp.pch': No such file or directory BUILD: Compile errors: not linking c:\epassthru directory BUILD: Done 7 files compiled - 44 Errors =============== build warnings ====================== cl -nologo /Tc -Ii386\ -I. -Ic:\NTDDK\inc -Ic:\NTDDK\inc -Ic:\NTDDK\inc -Ic:\NTDDK\inc\ ddk -Ic:\NTDDK\inc\ddk\wdm -Ic:\NTDDK\private\inc -Ic:\NTDDK\inc -D_X86_=1 - Di386=1 -DSTD_CALL -DCONDITION_HANDLING=1 -DNT_UP=1 -DNT_INST=0 -DWIN32=100 -D_NT1 X_=100 -DWINNT=1 -D_WIN32_WINNT=0x0500 -DWINVER=0x0500 -D_WIN32_IE=0x0501 -D WIN32_LEAN_AND_MEAN=1 -DDBG=1 -DDEVL=1 -DFPO=0 -DNDEBUG -D_DLL=1 -DNDIS40 -D NDIS_MINIPORT_DRIVER -DNDIS40_MINIPORT -DNDIS40_MINIPORT=1 -DNDIS40=1 /c /Zel /Zp8 /Gy -cbstring /W3 /WX /Gz /QIfdiv- /QIf /QI0f /GB /Gi- /Gm- /GX- /GR- /GF -Z7 /Oxs /Oy- /FRC:\EPassThru\objchk\i386\ -FIc:\NTDDK\inc\warning.h /Yuprecomp.h /Fpobjchk\i386\precomp.pch /YlPASSTHRU /Ycprecomp.h /Fpobjchk\i386\precomp.pch /Fo"C:\EPassT hru\objchk\i386\precomp.obj" cl -nologo /Tc -Ii386\ -I. -Ic:\NTDDK\inc -Ic:\NTDDK\inc -Ic:\NTDDK\inc -Ic:\NTDDK\inc\ ddk -Ic:\NTDDK\inc\ddk\wdm -Ic:\NTDDK\private\inc -Ic:\NTDDK\inc -D_X86_=1 - Di386=1 -DSTD_CALL -DCONDITION_HANDLING=1 -DNT_UP=1 -DNT_INST=0 -DWIN32=100 -D_NT1 X_=100 -DWINNT=1 -D_WIN32_WINNT=0x0500 -DWINVER=0x0500 -D_WIN32_IE=0x0501 -D WIN32_LEAN_AND_MEAN=1 -DDBG=1 -DDEVL=1 -DFPO=0 -DNDEBUG -D_DLL=1 -DNDIS40 -D NDIS_MINIPORT_DRIVER -DNDIS40_MINIPORT -DNDIS40_MINIPORT=1 -DNDIS40=1 /c /Zel /Zp8 /Gy -cbstring /W3 /WX /Gz /QIfdiv- /QIf /QI0f /GB /Gi- /Gm- /GX- /GR- /GF -Z7 /Oxs /Oy- /FRC:\EPassThru\objchk\i386\ -FIc:\NTDDK\inc\warning.h /Yuprecomp.h /Fpobjchk\i386\precomp.pch /YlPASSTHRU /Ycprecomp.h /Fpobjchk\i386\precomp.pch /Fo"C:\EPassT hru\objchk\i386\precomp.obj" build complete building browse information files EPassThru.exe - 44 error(s), 0 warning(s) Thank you for your help..... Tag: WinCE <-> WinXP (serial over USB) Tag: 52076
  - 9
    - DVD BCA querying..... hi friends, I want to query the BCA information from the DVD that is BCA enabled. This is the following code i did, please tell me whether this is correct or not. DWORD dwReturned = 0; HANDLE hfile = NULL; SetDlgItemText( IDC_EDIT_BCA_VALUE, NULL); hfile = CreateFile("\\\\.\\E:",GENERIC_READ, FILE_SHARE_READ,NULL, OPEN_EXISTING, FILE_ATTRIBUTE_READONLY,NULL); TRACE("Load disk File handle Value %d\n", hfile); if( hfile == INVALID_HANDLE_VALUE ) return; DeviceIoControl(hfile, IOCTL_DISK_LOAD_MEDIA, NULL, 0, NULL, 0, &dwReturned, 0); ///*DVD_ Sleep(3000); DVD_READ_STRUCTURE read_struct; DVD_BCA_DESCRIPTOR bcaDesc; //DVD_COPYRIGHT_DESCRIPTOR copyright; DVD_LAYER_DESCRIPTOR layer; //DVD_MANUFACTURER_DESCRIPTOR manufacturer; DWORD bytes_read, err; HRESULT hr = S_OK; ((long*) &read_struct.BlockByteOffset)[0] = 0; ((long*) &read_struct.BlockByteOffset)[1] = 0; long session = 0; hr = DeviceIoControl (hfile, IOCTL_DVD_START_SESSION, 0, 0, &session, sizeof (session), &bytes_read, 0); if( FAILED( hr )) return; read_struct.SessionId = session; read_struct.LayerNumber = 0; //layer.BCAFlag =0; //layer.BookVersion = 0; read_struct.Format = DvdPhysicalDescriptor; hr = DeviceIoControl (hfile, IOCTL_DVD_READ_STRUCTURE, &read_struct, sizeof (read_struct), &layer, sizeof (layer), &bytes_read, 0); if( FAILED( hr )) { err = GetLastError(); //exit (1); } TRACE("Disk Layer BCAFlag %d\n", layer.BCAFlag ); if( layer.BCAFlag != 0 ) { read_struct.Format = DvdBCADescriptor; hr = DeviceIoControl (hfile, IOCTL_DVD_READ_STRUCTURE, &read_struct, sizeof (read_struct), &bcaDesc, sizeof (bcaDesc), &bytes_read, 0); if( FAILED( hr )) { err = GetLastError(); //exit (1); } TRACE("BCA Data %s\n", bcaDesc.BCAInformation); if( size_t(bcaDesc.BCAInformation) > 0 ) SetDlgItemText( IDC_EDIT_BCA_VALUE, (LPCTSTR)bcaDesc.BCAInformation ); } hr = DeviceIoControl (hfile, IOCTL_DVD_END_SESSION, &session, sizeof (session), 0, 0, &bytes_read, 0); if( FAILED( hr )) { //exit (1); } ////DeviceIoControl(hfile, IOCTL_DISK_EJECT_MEDIA, NULL, 0, //// NULL, 0, &dwReturned, 0); CloseHandle( hfile ); -- thnaks iyappan Tag: WinCE <-> WinXP (serial over USB) Tag: 52074
  - 10
    - Capture driver supporting transport stream All, I am running into a problem while exposing a tranpsort stream from the output pin of a capture driver. I have started from the DDK sample and have modified it to accomodate my needs and basically I have configured the capture and preview output pins of the capture driver to support MPEG-2 transport streams. The pins being confgured as STATIC_KSDATAFORMAT_TYPE_STREAM, STATIC_KSDATAFORMAT_TYPE_MPEG2_TRANSPORT, STATIC_KSDATAFORMAT_SPECIFIER_NONE being the majortype, subtype and the datformat resp. For some reason when using some PVR general purpose DirectShow compliant apps, I do get a call to open the input streams(pins) via SRB_OPEN_STREAM but never get a call to open the output stream. This I understand could be because the downstream filter( which would be the Demux in this vase) doesnt accept the connections and hence the problem. Would anyone know why this would happen ? On a side note, when I try to manually connect the filters through graphedit, I can connect the capture to ademux and so on and the MPEG stream is rendered correctly, provided I have to manually set the DEmux filter to the correct P-ID and then it configures its output ipin and then connects to any downstream decoder filter and so on. So, within graphedit, I can connnect and things are fine. However, with PVR apps and I have tried a variety of them(which all have support for transport streams and I have verified them with other capture drivers that do support transport streams possibly), things dont work. Any help appreciated. Thanks. Tag: WinCE <-> WinXP (serial over USB) Tag: 52072
  - 11
    - Debugging NDIS protocol driver I am new to writing drivers. I have just begun on the work of writing a NDIS protocol driver. As a starting point I am using the sample protocol driver NDISUIO provided with WINDDK 2600.1106. I have modified NDISUIO and put some DbgPrint() statements to understand its behaviour. I build the driver using the build environment provided with WINDDK on a windows XP sp1 box. I install the driver using snetcfg utility and load it using net start <driver> command. All this is successful. I have written a user level program (DriverTest.exe) that opens the driver using "CreateFile" call and then communicates with the driver through "DeviceIoControl" calls. All calls are running perfectly without any problem. The problem is when I try to debug I cannot see the messages that I am passing through DbgPrint() statements in my driver. Here is how I am trying to Debug the driver locally (target and host machine are the same): 1. type kd -kl at the command prompt (symbols are loaded properly, no error messages) 2. open windbg.exe from Start > Programs > Debugging Tools for Windows 3. open my user level program DriverTest.exe from File > Open Executable in WindDbg GUI 4. I don't get any error messages, I can press F5 (Go) and get the program to complete and do intended task but cannot see any messages in the debugger neither in WinDbg nor in kd Is there a fundamental mistake in my debugging approach? Where are the debugging messages sent by DbgPrint() supposed to appear, in kd or WinDbg? Any help would be appreciated. Thanks in advance, James Tag: WinCE <-> WinXP (serial over USB) Tag: 52071
  - 12
    - re: Problem accessing Intel chipset configuration registers Update: After changing my direct accesses of the virtual address to the HAL READ_REGISTER_*/WRITE_REGISTER_* functions everything works like a charm. I had done this before, but that was previous to where I had correctly mapped the physical address to a virtual. Randy > *(ULONG*)virtAddr = oneBit; > > // test read > if ( *(ULONG*)virtAddr != oneBit ) { > RtlInitUnicodeString(&uniErrorString, L"0x0000000000000005"); // error > condition > goto testDONE; > } > > // test write, this should fail silently because of write-once bit > *(ULONGLONG*)virtAddr = zeroBit; > memVal = *(ULONGLONG*)virtAddr; > > uniErrorString.Length = 0; > uniErrorString.MaximumLength = 70; > uniErrorString.Buffer = &addrBuffer[0]; > // convert value to string > if ( STATUS_SUCCESS != > RtlIntegerToUnicodeString(memVal,10,&uniErrorString) ) { > RtlInitUnicodeString(&uniErrorString, L"0x0000000000000003"); // error > condition > } > > testDONE: > // do error things... > > Tag: WinCE <-> WinXP (serial over USB) Tag: 52062
  - 13
    - Re-using Irp for Usb I have an IOCTL defined for performing a read of an Interrupt IN endpoint on my USB device. User mode code makes an overlapped call of DeviceIoControl with this IOCTL, and waits (perhaps for a long time) for the result. When the associated Irp shows up in my DispatchDeviceControl function, can I continue to use it without creating a new Irp? Could I just change its major function to IOCTL_INTERNAL_USB_SUBMIT_URB, attach an appropriate URB to it, and pass it down, and forget about it? Will the USBD take care of completion and / or cancellation, or do I have to worry about this, even though I did not create the Irp in the driver. Thanks in advance for the help, Dennis Tag: WinCE <-> WinXP (serial over USB) Tag: 52061
  - 14
    - XP SP2 prevents checked kernel execution Since installing SP2 for XP Pro, I can no longer execute a checked build using the /kernel= and /hal= options in the boot.ini file. All attempts to do so results in an error complaining about the system32\drivers\ntfs.sys file being either corrupted or missing. Obviously SP2 must have replaced this driver, and who knows how many others. Bottom line is there a work around? If not, when can we expect to return to running checked kernels for our development or do we simply chuck SP2? Tag: WinCE <-> WinXP (serial over USB) Tag: 52056
  - 15
    - SANDISK Geometry via IOCTL_DISK_GET_DRIVE_GEOMETRY_EX I am having difficulty with gathering correct disk geometry values for my PC Card using IOCTL_DISK_GET_DRIVE_GEOMETRY_EX. The card I am using is a 40MB Flash, but it has 64,225,280 bytes capacity. The manufacturer (who I've spoken with) gave me the following values: Cylinders: 490 Heads : 8 Sectors : 32 Doing the C*H*S*512 math gives me the correct # of bytes, as expected. However, the call to IOCTL_DISK_GET_DRIVE_GEOMETRY_EX is returning: Cylinders: 7 Heads : 255 <-- I'm calling tracks/cyl the "heads"..is this wrong? Sectors : 63 This gives me only 57,576,960 bytes! The manufacturer said that that is "just the way Windows is." Hopefully not, because if it is so, I'll have to go "way-low" and attempt direct ATA access via ports. And since I can't readily find a way to get the IDE port the PC Card is using, I will be quite out of luck. Can anyone verify that Windows does in fact report erroneous drive geometry with these cards? Is there a better way to gather this data? Thanks in advance, Eric Rudisill Tag: WinCE <-> WinXP (serial over USB) Tag: 52054
  - 16
    - High frequency output on parallel port, how? Hi, I want to control stepper motors from XP, this requires me to toggle the parallel port datalines with a frequency ofseveral KHz. I have the givio driver which gives me IO privilege so that I can write and read to the port in usermode. Now I have the problem that the fastest timers in user mode is the multimedia timer which works with 1 millisecond at most. These guys http://www.artofcnc.ca claim that they can get 35 KHz output on the parallel port of a 1 GHz machine running XP, I know that they use a device driver, that's why I ask this question here. How do I accomplish a timer that works with much higher frequencies, does anybody of you kernel programmers know? Bert Tag: WinCE <-> WinXP (serial over USB) Tag: 52053
  - 17
    - Problem accessing Intel chipset configuration registers I am writing a driver to access a specific read/write-once register in the Intel ICH chipset configuration space. My test is to set some write-once bits in the register, and then write a clear to those same bits. This clear should silently fail and remain at the first value written. (Verified in linux.) The Intel spec states that the chipset configuration space mapped location is set in the RCBA register. I can verify this also using linux. So my physical memory location should be the address in the RCBA plus any offset to the specific register I want. I looked in the RCBA register to find the physical address of the chipset configuration mapped memory block. Finding this, I then mapped it from a physical into a virtual address using MmMapIoSpace() in the DDK. Below is a snippet of my code, trying to run my tests and then convert the location of that register into a unicode string to print to a system log entry. Am I doing something wrong here? Thanks a bunch for the help, Randy -- begin code snippet -- UNICODE_STRING uniErrorString ; // return string VOID* virtAddr = NULL; // virtual address from MmMapIoSpace ULONG memVal = 0; // value derived from memory mapped register WCHAR addrBuffer[70]; // used to store the converted integer, or error codes PHYSICAL_ADDRESS memAddr2; //ULONG addrSpace = 0x0; //memory, not IO space ULONG oneBit = 0x010001; // for test write 1 ULONG zeroBit = 0x010000; // for test write 2 memAddr2.HighPart = 0x0; // where xxx is replaced by the configuration register I am testing memAddr2.LowPart = 0xFED1Cxxx; // address combined with offset as indicated by RCBA virtAddr = MmMapIoSpace(memAddr2,4,FALSE); if ( virtAddr == NULL ) { memVal = 0x00000002; // error condition goto testDONE; } // should be able to set, and then the one should stay...clear bit should not replace it // first test write *(ULONG*)virtAddr = oneBit; // test read if ( *(ULONG*)virtAddr != oneBit ) { RtlInitUnicodeString(&uniErrorString, L"0x0000000000000005"); // error condition goto testDONE; } // test write, this should fail silently because of write-once bit *(ULONGLONG*)virtAddr = zeroBit; memVal = *(ULONGLONG*)virtAddr; uniErrorString.Length = 0; uniErrorString.MaximumLength = 70; uniErrorString.Buffer = &addrBuffer[0]; // convert value to string if ( STATUS_SUCCESS != RtlIntegerToUnicodeString(memVal,10,&uniErrorString) ) { RtlInitUnicodeString(&uniErrorString, L"0x0000000000000003"); // error condition } testDONE: // do error things... Tag: WinCE <-> WinXP (serial over USB) Tag: 52049
  - 18
    - VIDEO_MEMORY_INFORMATION I found the following definition in DDK: VideoRamLength = VideoMemoryBitmapHeight * ScreenStride FrameBufferLength = VisScreenWidth * ScreenStride I think the document for FrameBufferLength is not correct. It should be: FrameBufferLength = VisScreenHeight * ScreenStride Correct me if I'm wrong. Regards, Min Tag: WinCE <-> WinXP (serial over USB) Tag: 52044
  - 19
    - SharedUserData Is there some documented way to access SharedUserData structure from user mode? Thanks for assistance. Tag: WinCE <-> WinXP (serial over USB) Tag: 52041
  - 20
    - HOWTO make usbser.sys run on Win 9x/ME Hi Is there anybody who can tell me how to make usbser.sys run on older Windows versions that support USB? Many thanks Holi Tag: WinCE <-> WinXP (serial over USB) Tag: 52038
  - 21
    - How to read data in IRP_MJ_READ and IRP_MJ_WRITE Hi, I have an upper filter driver for a serial port which can see the various IOCTls going down to the driver from the application (i.e. Hyperterminal) which has been loaded on top of it. I want to be able to read the data that is being sent and received by Hyperterminal but I can't see how to extract this. Should I be able to see this in the SystemBuffer or the MDL? The IRP Flag DO_DIRECT_IO is set which would suggest that the MDL is in use but the Irp->MdlAddress pointer is NULL. Thanks O.C. Tag: WinCE <-> WinXP (serial over USB) Tag: 52032
  - 22
    - Printer driver problem XP SP1 Hi, My old Epson stylus colour printer was recognised by new XP SP1 when first installed a few months ago. A few weeks ago simply stopped working. No problem with printer; no problem with port. Unable to download driver proposed by Epson nor driver proposed by MS. What other solution? Peter Tag: WinCE <-> WinXP (serial over USB) Tag: 52029
  - 23
    - Remote Debugging, User and Kernel Mode I'm setting up host and target machines for debugging both kernel mode code, built with the DDK, and user mode code, built with Visual Studio. NET. I'm planning to use the Visual Studio debugger for the User code. It appears to support remote debugging, but I've never used it this way. My host-target connection here will be via my ethernet LAN. I plan to use Windbg for the driver code. I have a dedicated 1394 connection for Windbg, which seem to work. To you experienced developers, does this setup make sense? Right now I'm concerned about making sure that the executables are always up-to-date on the target, and that the symbols are always current. Any tips for changing or using this setup would be appreciated. I don't suppose I can use one debugger for both kernel and user mode, can I? Thanks, Dennis Tag: WinCE <-> WinXP (serial over USB) Tag: 52021
  - 24
    - Keyboard filter to simulate keys Hello, I'm new to driver development, in fact I have never written a real mode sys file nor a driver. Now I have to accomplish the following task: A program generates virtual key events to control a directx game. Because directx directly reads out the keyboard I can't simply use the WinAPI keybd_event or a simple SendKeys function. So the best way seems to be to send the keystrokes from my application (can be delphi, c++ or vb) to the keyboard filter driver that creates the keystroke. Therefore I register a new keyboardchain filter KbdFilterInit Then I'd like to feed keys into the keyboard chain to simulate button press events. Therefore I create KeyData packets. To process the keyboard chain I implement proper dispatch function for reading NTSTATUS KbdDispatchRead( IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp ) So my questions are: Is there already something similar out there that I can use? Is it possible to create such a driver file without getting 1000s of blue screens? What's the easiest way to do this. How can I send some bytes from my app to the driver? (My app tells the driver to generate an 'F1' keystroke...) Is my theory correct? I hope to get some help from you. Thanks for any hints Mel NTSTATUS KbdFilterInit( IN PDRIVER_OBJECT DriverObject ) /*++ Routine Description: Create a device object and attaches it to the first keyboard device chain Arguments: DeviceObject - pointer to a device object. Return Value: NT Status code --*/ { UNICODE_STRING ntUnicodeString; NTSTATUS ntStatus; PDEVICE_OBJECT DeviceObject = NULL; // // Only hook onto the first keyboard's chain. // RtlInitUnicodeString( &ntUnicodeString, L"\\Device\\KeyboardClass0" ); // // Create device object for the keyboard. // ntStatus = IoCreateDevice( DriverObject, 0, NULL, FILE_DEVICE_KEYBOARD, 0, FALSE, &DeviceObject ); if( !NT_SUCCESS(ntStatus) ) { JKBD_DbgPrint(("JKBD: Keyboard hook failed to create device!\n")); return ntStatus; } // // Keyboard uses buffered I/O so we must as well. // DeviceObject->Flags |= DO_BUFFERED_IO; // // Attach to the keyboard chain. // ntStatus = IoAttachDevice( DeviceObject, &ntUnicodeString, &pGlobalDevExt->KbdDevice ); if( !NT_SUCCESS(ntStatus) ) { JKBD_DbgPrint(("JKBD: Connect with keyboard failed!\n")); IoDeleteDevice( DeviceObject ); return ntStatus; } pGlobalDevExt->KbdFilterDevice = DeviceObject; return STATUS_SUCCESS; } // // Create a keyboard packet // KeyData = pGlobalDevExt->RawKbdIrp->AssociatedIrp.SystemBuffer; RtlZeroMemory(KeyData, 2*sizeof(KEYBOARD_INPUT_DATA)); KeyData[numKeys].Flags = 0; //down KeyData[numKeys+1].Flags = 1; //up KeyData[numKeys].MakeCode = 0x1e; // character a KeyData[numKeys+1].MakeCode = 0x1e; // character a numKeys += 2; KeyData += numKeys*sizeof(KEYBOARD_INPUT_DATA); pGlobalDevExt->RawKbdIrp->IoStatus.Status = STATUS_SUCCESS; pGlobalDevExt->RawKbdIrp->IoStatus.Information = numKeys*sizeof(KEYBOARD_INPUT_DATA); pGlobalDevExt->RawKbdIrpPending = FALSE; IoCompleteRequest(pGlobalDevExt->RawKbdIrp, IO_KEYBOARD_INCREMENT); Tag: WinCE <-> WinXP (serial over USB) Tag: 52017
  - 25
    - DVD_BCA_DESCRIPTOR hi friends, I want to query the BCA information from the DVD that is BCA enabled. This is the following code i did, please tell me whether this is correct or not. DWORD dwReturned = 0; HANDLE hfile = NULL; SetDlgItemText( IDC_EDIT_BCA_VALUE, NULL); hfile = CreateFile("\\\\.\\E:",GENERIC_READ, FILE_SHARE_READ,NULL, OPEN_EXISTING, FILE_ATTRIBUTE_READONLY,NULL); TRACE("Load disk File handle Value %d\n", hfile); if( hfile == INVALID_HANDLE_VALUE ) return; DeviceIoControl(hfile, IOCTL_DISK_LOAD_MEDIA, NULL, 0, NULL, 0, &dwReturned, 0); ///*DVD_ Sleep(3000); DVD_READ_STRUCTURE read_struct; DVD_BCA_DESCRIPTOR bcaDesc; //DVD_COPYRIGHT_DESCRIPTOR copyright; DVD_LAYER_DESCRIPTOR layer; //DVD_MANUFACTURER_DESCRIPTOR manufacturer; DWORD bytes_read, err; HRESULT hr = S_OK; ((long*) &read_struct.BlockByteOffset)[0] = 0; ((long*) &read_struct.BlockByteOffset)[1] = 0; long session = 0; hr = DeviceIoControl (hfile, IOCTL_DVD_START_SESSION, 0, 0, &session, sizeof (session), &bytes_read, 0); if( FAILED( hr )) return; read_struct.SessionId = session; read_struct.LayerNumber = 0; //layer.BCAFlag =0; //layer.BookVersion = 0; read_struct.Format = DvdPhysicalDescriptor; hr = DeviceIoControl (hfile, IOCTL_DVD_READ_STRUCTURE, &read_struct, sizeof (read_struct), &layer, sizeof (layer), &bytes_read, 0); if( FAILED( hr )) { err = GetLastError(); //exit (1); } TRACE("Disk Layer BCAFlag %d\n", layer.BCAFlag ); if( layer.BCAFlag != 0 ) { read_struct.Format = DvdBCADescriptor; hr = DeviceIoControl (hfile, IOCTL_DVD_READ_STRUCTURE, &read_struct, sizeof (read_struct), &bcaDesc, sizeof (bcaDesc), &bytes_read, 0); if( FAILED( hr )) { err = GetLastError(); //exit (1); } TRACE("BCA Data %s\n", bcaDesc.BCAInformation); if( size_t(bcaDesc.BCAInformation) > 0 ) SetDlgItemText( IDC_EDIT_BCA_VALUE, (LPCTSTR)bcaDesc.BCAInformation ); } hr = DeviceIoControl (hfile, IOCTL_DVD_END_SESSION, &session, sizeof (session), 0, 0, &bytes_read, 0); if( FAILED( hr )) { //exit (1); } ////DeviceIoControl(hfile, IOCTL_DISK_EJECT_MEDIA, NULL, 0, //// NULL, 0, &dwReturned, 0); CloseHandle( hfile ); -- thnaks iyappan Tag: WinCE <-> WinXP (serial over USB) Tag: 52014
- Next
  - 1
    - Floating Point Operations This is a multi-part message in MIME format. ------=_NextPart_000_0022_01C49FDF.B83C9D00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, DDK says that "Floating point arithmetic is not otherwise supported = in the Windows NT kernel code." but i was able to execute a small piece of code which does float = operations. VOID Floatops() { int decimal, sign; char *buffer; double a =3D 22.00,b =3D 7.0,c=3D0; c =3D a/b; buffer =3D _fcvt( c, 7, &decimal, &sign ); // uses libc.lib = for linking KdPrint(( "Value: '%s' Decimal: %d sign: %d\n",buffer, = decimal, sign )); } which neatly calculcated the value.To fix the linking issues i said=20 extern int _fltused =3D 0; I just wanted to know 1.what are the implications of doing such a thing,do the float values = get corrupted over time=20 i.e due to some other operations 2.Do i have to use the KeSaveFloatXXX and Restore routines,to perform = float operations in a "safe" way. 3.When I say "extern int _fltused =3D0;" ,is it a valid thing to do.what = is _fltused ?? where does it come from, what is being linked that uses this Regards, Manohar ------=_NextPart_000_0022_01C49FDF.B83C9D00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#c8e0d8 background=3D""> <DIV><FONT face=3DArial size=3D2>Hi All,<BR><BR>    DDK = says that=20 "Floating point arithmetic is not otherwise supported in the Windows NT = kernel=20 code."<BR>    but i was able to execute a small = piece of=20 code which does float operations.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial = size=3D2></FONT><FONT=20 face=3DArial size=3D2></FONT><FONT face=3DArial size=3D2></FONT><FONT = face=3DArial=20 size=3D2></FONT><BR><FONT face=3DArial size=3D2>   VOID=20 Floatops()<BR>   {<BR>      =      int=20 decimal, sign;<BR>    =        char=20 *buffer;<BR>          &= nbsp;double=20 a =3D 22.00,b =3D 7.0,c=3D0;<BR>   =20        c =3D=20 a/b;<BR>           = buffer =3D=20 _fcvt( c, 7, &decimal, &sign ); // uses libc.lib for=20 linking<BR>          =20 KdPrint(( "Value: '%s' Decimal: %d sign: %d\n",buffer, decimal, sign=20 ));<BR>  }</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2> which neatly calculcated the = value.To fix the=20 linking issues i said </FONT></DIV> <P><FONT face=3DArial size=3D2> extern int _fltused =3D = 0;</FONT></P> <P><FONT face=3DArial size=3D2>I just wanted to know</FONT></P> <DIV><FONT face=3DArial size=3D2>1.what are the implications of doing = such a =20 thing,do the float values get corrupted over time </FONT></DIV> <DIV><FONT face=3DArial size=3D2>  i.e due to some other=20 operations</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial = size=3D2></FONT><BR><FONT=20 face=3DArial size=3D2>2.Do i have to use the KeSaveFloatXXX and Restore = routines,to=20 perform float operations in a "safe" way.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>3.When I say "extern int _fltused = =3D0;" ,is it a=20 valid thing to do.what is _fltused ?? where does it come = from,</FONT></DIV> <DIV><FONT face=3DArial size=3D2>   what is being linked = that uses=20 this</FONT><BR><BR><FONT face=3DArial=20 size=3D2>Regards,<BR>Manohar</FONT></DIV></BODY></HTML> ------=_NextPart_000_0022_01C49FDF.B83C9D00-- Tag: WinCE <-> WinXP (serial over USB) Tag: 52008
  - 2
    - WZC vs OID_802_11_SSID... hi, I'm building my wireless lan driver and encounter the following situation: After I've finished to connect to AccessPoint, and PING is working normally. After couple of minitus, I will receive OID_802_11_SSID again. I don't know why WZC send this OID to me again, but if I use my utility(just like WZC) it works well. That means I wouldn't receive this OID under my utility when PING is ok. Could somebody tell me when will WZC send OID_802_11_SSID(ssid field included the name in Perferred Networks) again? If my connection is established, it seems WZC shouldn't send this OID to me? Any help, thank you very much. -RedOctober Tag: WinCE <-> WinXP (serial over USB) Tag: 52000
  - 3
    - Oney's spinlock sample code. I tryed to compile the spinlock sample code of the Oney's book with .NET. 2002 and with Whidbey C++ Express The compiler complains though: DriverEntry.obj : error LNK2019: unresolved external symbol @__security_check_cookie@4 referenced in function "long __stdcall AddDevice(struct _DRIVER_OBJECT *,struct _DEVICE_OBJECT *)" (?AddDevice@@YGJPAU_DRIVER_OBJECT@@PAU_DEVICE_OBJECT@@@Z) objchk_wxp_x86\i386\spinlock.sys : fatal error LNK1120: 1 unresolved externals I'd be grateful if You could explain me. Regards. Tag: WinCE <-> WinXP (serial over USB) Tag: 51981
  - 4
    - Fucntional USB driver launching USBPRINT with error. All please help me to solve this to me tricky problem. I have an USB printer which don't report the correct class id. The printer reports USB\Class_ff and my driver replaces this string with USB\Class_07 when enumerated. This makes the USBPRINT system to launch exactly as I want, until USB print starts the PDO. In my PDO (I call it my Virtual PDO due to the fact it tunnels all trafik down to the real PDO which has the wrong class id) IRP_MN_START_DEVICE I complete the IRP and returns STATUS_SUCCESS. I then expect USBPRINT to be started, but no way. USBPRINT send an IRP_MN_REMOVE_DEVICE, why????? This makes every thing fail. What have I forgotten in my IRP_MN_START_DEVICE so that USBPRINT doesn't send a remove device IRP? Below is the dbg print from WindDbg. The PDO dispatch is in the file pdo.c which is called after device relations have been served by pnp.c (FDO dispatch). lkd> !dbgprint 'USBLarsa-2> DriverEntry 'USBLarsa-2> AddDevice: drvObj=82295D28h, pdo=8205D9B8h 'USBLarsa-2> CreateOurVirtual: drvObj=82295D28h, pdo=8205D9B8h virtualpdo=8229EE80h 'USBLarsa-2> pnp.c - IRP_MN_QUERY_LEGACY_BUS_INFORMATION 'USBLarsa-2> pnp.c - IRP_MN_QUERY_RESOURCE_REQUIREMENTS 'USBLarsa-2> pnp.c - IRP_MN_FILTER_RESOURCE_REQUIREMENTS 'USBLarsa-2> pnp.c - IRP_MN_START_DEVICE 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pnp.c - IRP_MN_QUERY_CAPABILITIES 'USBLarsa-2> pnp.c - IRP_MN_QUERY_PNP_DEVICE_STATE 'USBLarsa-2> pnp.c - IRP_MN_QUERY_DEVICE_RELATIONS 'USBLarsa-2> Relation string : BusRelations 'USBLarsa-2> pdo.c - IRP_MN_QUERY_ID 'USBLarsa-2> pdo.c - IRP_MN_QUERY_CAPABILITIES 'USBLarsa-2> pdo.c - IRP_MN_QUERY_DEVICE_TEXT 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pdo.c - IRP_MN_QUERY_DEVICE_TEXT 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pdo.c - IRP_MN_QUERY_ID 'USBLarsa-2> pdo.c - IRP_MN_QUERY_ID 'USBLarsa-2> pdo.c - IRP_MN_QUERY_ID 'USBLarsa-2> DoQueryID_PDO 'USBLarsa-2> BusQueryCompatibleIDs 'USBLarsa-2> pdo.c - IRP_MN_QUERY_RESOURCE_REQUIREMENTS 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pdo.c - IRP_MN_QUERY_BUS_INFORMATION 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pdo.c - IRP_MN_QUERY_RESOURCES 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pdo.c - IRP_MN_QUERY_CAPABILITIES 'USBLarsa-2> pdo.c - IRP_MN_QUERY_LEGACY_BUS_INFORMATION 'USBLarsa-2> pdo.c - IRP_MN_QUERY_RESOURCE_REQUIREMENTS 'USBLarsa-2> CallNextDriverSync 'USBLarsa-2> CallDriverSync 'USBLarsa-2> CallDriverSyncCompletion 'USBLarsa-2> pdo.c - IRP_MN_FILTER_RESOURCE_REQUIREMENTS 'USBLarsa-2> pdo.c - IRP_MN_START_DEVICE 'USBLarsa-2> pdo.c - IRP_MN_REMOVE_DEVICE Tag: WinCE <-> WinXP (serial over USB) Tag: 51978
  - 5
    - MULTIPLE_IRP_COMPLETE_REQUEST stop error Hello, I have written a usb client driver , and am using it on 2k/XP. when i open a handle to the driver from user mode and close the handle , and later form the task bar , i click on safely remove hardware , and then stop the device, then BSOD with MULTIPLE_IRP_COMPLETE_REQUEST comes up. The error does not come up if: 1) a handle to the driver was not opened 2) If i remove the device abruptly by pulling out the usb wire any clues on how to debug this ? are there any kd commands helpful for debugging this issue? thanks Taha Tag: WinCE <-> WinXP (serial over USB) Tag: 51969
  - 6
    - Enumerating USB Ports Hi, If SetupDiClassGuidsFromName is called to get GUID for class "USB", SetupDiEnumInterfaceDevice always return false though there are 4 USB ports available. and if SetupDiClassGuidsFromName is called to get GUID for class "Ports", its listing only 2 though there are 4 USB ports. (Devices are attached in both the cases.) Sample Code: ---------------------------------------------------------------------------- ------------------------------------------------------------------------ var RequiredSize: Cardinal; vDeviceList : OleVariant Guid: TGUID; DevInfoHandle: HDEVINFO; // Comments DeviceInfoData: TSPDevInfoData; MemberIndex: Cardinal; PropertyRegDataType: DWord; RegProperty: Cardinal; RegTyp: Cardinal; Key: Hkey; Info: TRegKeyInfo; S1,S2: string; hc: THandle; hLib : HINST; needed : DWORD; hINfo : HDEVINFO; Interface_Info : TSPDeviceInterfaceData; interface_detail : PSPDeviceInterfaceDetailData; sdname : pChar; strDeviceName : String; vattachedUSBList : OleVariant; slDynamicBuil : TStringList; begin try try if SetupDiClassGuidsFromName('Ports',@Guid,RequiredSize,RequiredSize) then // get 'Ports' class guid from name begin DevInfoHandle :=SetupDiGetClassDevs(@Guid,Nil,0,DIGCF_INTERFACEDEVICE);//());//get object handle of 'Ports' class to interate all devices if Cardinal(DevInfoHandle)<>Invalid_Handle_Value then begin try MemberIndex:=0; repeat //iterate device list Interface_Info.cbSize := SizeOf(_SP_DEVICE_INTERFACE_DATA); //28; //SizeOf(Interface_Info) 28; if (not SetupDiEnumInterfaceDevice(DevInfoHandle, nil,Guid,MemberIndex,Interface_Info)) then begin SetupDiDestroyDeviceInfoList(DevInfoHandle); break; end; SetupDiGetInterfaceDeviceDetail(DevInfoHandle, @Interface_Info, nil, 0, @needed, nil); interface_detail := AllocMem(needed); interface_detail.cbSize := SizeOf(_SP_DEVICE_INTERFACE_DETAIL_DATA_A); //5; //SizeOf(interface_detail) 5; SetupDiGetInterfaceDeviceDetail(DevInfoHandle,@Interface_Info,interface_deta il, needed,@needed, 0); sdName := StrAlloc(MAX_PATH); StrCopy(sdName,interface_detail.DevicePath); VarArrayRedim(vDeviceList,MemberIndex); vDeviceList[MemberIndex] := StrPas(sdName); FreeMemory(interface_detail); Inc(MemberIndex); until False; finally SetupDiDestroyDeviceInfoList(DevInfoHandle); end; end; end; finally // Result := vUSBList; end; except on E:Exception do ShowMessage(e.Message); end; Tag: WinCE <-> WinXP (serial over USB) Tag: 51964
  - 7
    - Enumerating USB ports I am trying to open cash drawer which is connected to Reciept printer (Printer is connected to USB port of CPU). We want to automatically detect the PORT for the selected printer. This works fine using "GetPrinter" WinAPI (populating _PRINTER_INFO_2A structure). And it displays USB002. To open cash drawer we use "CreateFile" and "WriteFile" WIN APIs. These functions work fine if PORT is of LPT/COM, but if its USB, it throws invalid handle. To interact with USB, we need to send DevicePath. Using SetupDiClassGuidsFromName, SetupDiGetClassDevs, SetupDiEnumInterfaceDevice, SetupDiGetInterfaceDeviceDetail of "SetupAPI.dll", we can enumerate available interface devices and can get DevicePath. But how do we map this strange DevicePath with Port name ? For example, For port USB002, how do I get respective DevicePath ? Thanks in advance, Tag: WinCE <-> WinXP (serial over USB) Tag: 51963
  - 8
    - calculate CPU cycles Is there an API that I can tap into from an NT Service that will allow me to get an estimated CPU clock cycles it takes to do X code? I have to do reports on performance and we normally do GetTickCount() but I need someone closer to the CPU Cycle level. Tag: WinCE <-> WinXP (serial over USB) Tag: 51961
  - 9
    - HELP! I enrolled in device driver class. My employer has purchased one week's training next week for device driver development. This is all to my suprise because I have been asking for the training for well over two years now. My only problem is that have been developing NT Services (with great success) but have never been able to get my head wrapped around device drivers and their architecture. I really need some help and I am out of time (almost). What book or on-line reference can I go to that will help me prepare for this class? I just have 6 days for prep and I feel very behind. I'm not even really sure what the different kinds of device drivers there are or what kinds of things that I can do with them. When complete with the course I am expected to work on a few projects that would either require several messy NT Services (polling and scanning) or just a few device drivers. Unfortunately, my understanding of device drivers is so limited that I'm not even sure if I'm right. I need some materials and I need them fast!!! thank you for all your help! Please do not respond via email directly because my current web connection (linux) does not like my email at this point but newgroups are awesome. All of my other machines are Windows flavors but my internet connection is linux and the only thing the stinking thing does not like is my email. Also, if someone is cross-platform savvy and wants to point me to a place that can outline a device driver in linux that might be interesting. THANKS!!!!!! Tag: WinCE <-> WinXP (serial over USB) Tag: 51960
  - 10
    - is it possible (fake file) I would like to attempt to create a "fake file" where when you do a 'dir' or subsuquent command it shows the file and all the normal information for a file. I can even open the file in notepad or such but the file must remain as read-only at all times. The reason is that when someone opens the file at that point they are reading a snapshot report of status items of their machine ... like maybe memory and hard drive space and current CPU status. A "copy" of this file to a new location is not necessary but would be nice. To get the contents of this file from fake status to real status I would just say "type fake.file > real.file" and it would be created. Another possible choice would be to have a notification I guess when the file is opened and at that point I generate a file in memory and give the opening application a handle to that file and not the actual file. I am new to device drivers but not to C++ and I create NT Services all the time. My current design uses an NT Service to generate this file but it would be much more effective if I could create this "fake file" for reasons not entirely outlined above. The only operating system that I plan on running this on is Windows 2000 Server/Professional or greater. thanks!! Tag: WinCE <-> WinXP (serial over USB) Tag: 51958
  - 11
    - Threads' blocking I'm new in Kernel Programming. I'm reading the Oney's book. I don't understand where he say that at a certain irql threads can't be blocked. I'd be grateful if you could give me only only an idea about that. Regards. Tag: WinCE <-> WinXP (serial over USB) Tag: 51957
  - 12
    - SetupDiEnumDeviceInterfaces Problem Calls to SetupDiEnumDeviceInterfaces fail to locate my device for which I've created a class GUID. Here's a sample call, with the index set to 0, just for test. SP_DEVICE_INTERFACE_DATA ifdata; ifdata.cbSize = sizeof( SP_DEVICE_INTERFACE_DATA ); BOOL Found = SetupDiEnumDeviceInterfaces(info, NULL, &m_InterfaceGUID, 0, &ifdata); Note that info is a handle that was sucessfully returned by a call to SetupDiGetClassDevs Found evaluates to zero and GetLastError returns 0x00000103 ("No more data is available"). I'm scratching my head, wondering why. Can someone suggest a cause of the problem? Thanks, Dennis Tag: WinCE <-> WinXP (serial over USB) Tag: 51955
  - 13
    - Serial Upper Filter Driver Help Required Hi, This is my first driver project. I need to write an upper filter driver for a serial port which is dynamically loaded from a test application when required. The driver will be loaded by means of the Service Control Manager and the driver will connect to the serial port by means of a special "start" IOCTL call from the test application using the DeviceIoControl() function, this will pass the name of the serial port device i.e. \??\COM4". The driver will attach to the named device leaving it in a state where it can still be opened by a 3rd party application. When loaded the driver will monitor incoming and outgoing data on the port and pass it back to the test application. I have used two of Walt Oney's sample projects as a starting point for my code. My driver loads and unloads OK but when I attempt to open the serial port from a 3rd party application (Hyperterminal in this case) I get a bugcheck as described below. I have included here the "bones" of the DriverEntry, AddDevice and DispatchAny functions. The bugcheck occurs at point XXX at the bottom of the DispatchControl function. I guess I have "broken" the IRP in some way but I don't know how. I can't see what the problem is but I am hoping that someone on this group will be able to see what I can't. Any help will be gratefully received. Sorry for such a long post. Many thanks O.C. **** DriverEntry Funtion extern "C" NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject,IN PUNICODE_STRING RegistryPath) { // Save the name of the service key servkey.Buffer = (PWSTR) ExAllocatePool(PagedPool, RegistryPath->Length + sizeof(WCHAR)); if(!servkey.Buffer) return STATUS_INSUFFICIENT_RESOURCES; servkey.MaximumLength = RegistryPath->Length + sizeof(WCHAR); RtlCopyUnicodeString(&servkey, RegistryPath); servkey.Buffer[RegistryPath->Length / 2] = 0; // Initialize function pointers DriverObject->DriverUnload = DriverUnload; for (int i = 0; i < arraysize(DriverObject->MajorFunction); ++i) DriverObject->MajorFunction[i] = DispatchControl; DriverObject->MajorFunction[IRP_MJ_CREATE] = DispatchCreate; DriverObject->MajorFunction[IRP_MJ_CLOSE] = DispatchClose; // Create a device object to allow an associated application to open a handle // in order to send us IOCTL requests status = AddDevice(DriverObject); if(!NT_SUCCESS(status)) DriverUnload(DriverObject); return status; } **** AddDevice Function NTSTATUS AddDevice(IN PDRIVER_OBJECT DriverObject) { PAGED_CODE(); KdPrint((DRIVERNAME " AddDevice(%8.8lX) - Start\n", DriverObject)); NTSTATUS status; // Create a function device object to represent the hardware we're managing. PDEVICE_OBJECT fdo; UNICODE_STRING devname; RtlInitUnicodeString(&devname, L"\\DosDevices\\NetMonSerW2kD"); status = IoCreateDevice(DriverObject, sizeof(DEVICE_EXTENSION), &devname, FILE_DEVICE_SERIAL_PORT, FILE_DEVICE_SECURE_OPEN, FALSE, &fdo); if (!NT_SUCCESS(status)) { KdPrint((DRIVERNAME " - IoCreateDevice failed - %X\n", status)); return status; } PDEVICE_EXTENSION pdx = (PDEVICE_EXTENSION) fdo->DeviceExtension; // From this point forward, any error will have side effects that need to // be cleaned up. do { pdx->DeviceObject = fdo; pdx->DriverObject = DriverObject; InitializeListHead(&pdx->registered); InitializeListHead(&pdx->events); KeInitializeSpinLock(&pdx->eventlock); // Make a copy of the device name pdx->devname.Buffer = (PWCHAR) ExAllocatePool(NonPagedPool, devname.MaximumLength); if (!pdx->devname.Buffer) { // can't allocate buffer status = STATUS_INSUFFICIENT_RESOURCES; KdPrint((DRIVERNAME " - Unable to allocate %d bytes for copy of name\n", devname.MaximumLength)); break;; } // can't allocate buffer pdx->devname.MaximumLength = devname.MaximumLength; RtlCopyUnicodeString(&pdx->devname, &devname); // Not sure about this bit. KeInitializeEvent(&pdx->RemoveLock.evRemove, NotificationEvent, FALSE); pdx->RemoveLock.usage = 1; pdx->RemoveLock.removing = FALSE; } while (FALSE); if(!NT_SUCCESS(status)) { if (pdx->devname.Buffer) RtlFreeUnicodeString(&pdx->devname); IoDeleteDevice(fdo); } return status; } **** DispatchControl Function NTSTATUS DispatchControl(PDEVICE_OBJECT fdo, PIRP Irp) { PAGED_CODE(); PDEVICE_EXTENSION pdx = (PDEVICE_EXTENSION) fdo->DeviceExtension; NTSTATUS status = STATUS_SUCCESS; ULONG info = 0; PIO_STACK_LOCATION stack = IoGetCurrentIrpStackLocation(Irp); ULONG cbin = stack->Parameters.DeviceIoControl.InputBufferLength; ULONG cbout = stack->Parameters.DeviceIoControl.OutputBufferLength; ULONG code = stack->Parameters.DeviceIoControl.IoControlCode; KdPrint(("\n"DRIVERNAME " DispatchControl() - Irp=%08X IOCTL = %08X\n",Irp,code)); switch(code) { case IOCTL_NETMON_STARTMON: { // Copy passed-in data to a unicode string. // (This will be something like "\??\COM4"). UNICODE_STRING PortName; WCHAR wPortName[32]; swprintf(wPortName,(WCHAR*)Irp->AssociatedIrp.SystemBuffer,cbin); RtlInitUnicodeString(&PortName,wPortName); PFILE_OBJECT FileObject = NULL; // Will be filled in with pointer to a file object. PDEVICE_OBJECT DeviceObject = NULL; // Will be filled in with pointer to a device object. status=IoGetDeviceObjectPointer(&PortName, FILE_READ_DATA, &FileObject, &DeviceObject); if(status!=STATUS_SUCCESS) { KdPrint((DRIVERNAME " DispatchControl() - Error=%08X\n",status)); break; } // "\??\COM4" if(!FileObject) break; if(!DeviceObject) break; pdx->Pdo = DeviceObject; // The current device. // Now attach our device to the device stack. // Attach our object (which we created with IoCreateDevice() in the // AddDevice() function and which has been passed to us as the "fdo" // parameter) to the object we just obtained a pointer to. // Save a pointer to the device beneath us so we can pass stuff on to it. // Attach OUR device object (fdo) to the curent device (ie for COM4). pdx->LowerDeviceObject = IoAttachDeviceToDeviceStack(fdo,DeviceObject); // Stuff from page 781 of Walt's book... fdo->Flags |= pdx->LowerDeviceObject->Flags & (DO_DIRECT_IO | DO_BUFFERED_IO | DO_POWER_PAGABLE); if(!pdx->LowerDeviceObject) { KdPrint((DRIVERNAME " DispatchControl() - Failed to attach\n")); ObDereferenceObject(FileObject); break; } ObDereferenceObject(FileObject); // Close port again. status = STATUS_SUCCESS; info = 0; KdPrint((DRIVERNAME " DispatchControl() - IOCTL_NETMON_STARTMON (End)\n")); break; } /***********/ /* Default */ /***********/ default: KdPrint((DRIVERNAME " DispatchControl() - Default Start\n")); static char* irpname[] = { "IRP_MJ_CREATE", "IRP_MJ_CREATE_NAMED_PIPE", "IRP_MJ_CLOSE", "IRP_MJ_READ", "IRP_MJ_WRITE", "IRP_MJ_QUERY_INFORMATION", "IRP_MJ_SET_INFORMATION", "IRP_MJ_QUERY_EA", "IRP_MJ_SET_EA", "IRP_MJ_FLUSH_BUFFERS", "IRP_MJ_QUERY_VOLUME_INFORMATION", "IRP_MJ_SET_VOLUME_INFORMATION", "IRP_MJ_DIRECTORY_CONTROL", "IRP_MJ_FILE_SYSTEM_CONTROL", "IRP_MJ_DEVICE_CONTROL", "IRP_MJ_INTERNAL_DEVICE_CONTROL", "IRP_MJ_SHUTDOWN", "IRP_MJ_LOCK_CONTROL", "IRP_MJ_CLEANUP", "IRP_MJ_CREATE_MAILSLOT", "IRP_MJ_QUERY_SECURITY", "IRP_MJ_SET_SECURITY", "IRP_MJ_POWER", "IRP_MJ_SYSTEM_CONTROL", "IRP_MJ_DEVICE_CHANGE", "IRP_MJ_QUERY_QUOTA", "IRP_MJ_SET_QUOTA", "IRP_MJ_PNP", }; UCHAR type = stack->MajorFunction; if (type >= arraysize(irpname)) KdPrint((DRIVERNAME " Unknown IRP, major type %X\n", type)); else KdPrint((DRIVERNAME " %s\n", irpname[type])); // Pass request down without additional processing NTSTATUS status; KdPrint((DRIVERNAME " DispatchControl() Def - Calling IoAcquireRemoveLock(%08X,%08X)\n",pdx->RemoveLock,Irp)); status = IoAcquireRemoveLock(&pdx->RemoveLock,Irp); KdPrint((DRIVERNAME " DispatchControl() Def - IoAcquireRemoveLock() acquired %08X and returns %08X\n",pdx->RemoveLock,status)); if (!NT_SUCCESS(status)) return CompleteRequest(Irp, status, 0); // If there is no lower device object supplied. if(pdx->LowerDeviceObject==NULL) { KdPrint((DRIVERNAME " DispatchControl() Def - No LDO so exit now\n")); status=STATUS_SUCCESS; break; } IoSkipCurrentIrpStackLocation(Irp); KdPrint((DRIVERNAME " DispatchControl() Def - Calling IoCallDriver(%08X,%08X)\n",pdx->LowerDeviceObject,Irp)); status = IoCallDriver(pdx->LowerDeviceObject,Irp); KdPrint((DRIVERNAME " DispatchControl() Def - IoCallDriver() returns %08X\n",status)); if(Irp) { IoReleaseRemoveLock(&pdx->RemoveLock,Irp); } KdPrint((DRIVERNAME " DispatchControl() Def - End\n")); break; } XXX Bugcheck DRIVER_PAGE_FAULT_IN_FREED_MEMORY_POOL when next instruction is executed. The Irp pointer is still the same so I guess the memory it points to has been released. Irp->IoStatus.Status = status; Irp->IoStatus.Information = info; IoCompleteRequest(Irp, IO_NO_INCREMENT); return status; } // DispatchControl Tag: WinCE <-> WinXP (serial over USB) Tag: 51949
  - 14
    - how to use a system DMA channel? hello, Everybody, I am writing a PCI driver. In this device ,there is no Pci interface chip, so I need to get a system DMA channel. But I don't konw how.In the pnp start IRP£¬there is no DMA resource for me to use. Another question is that how to use the system DMA channel? I know if the device has got its own dma channel,usually,I can set the start address,and counter,and trigger the DMA. But using system DMA channel, how to do these thing? Any advice or disscusion is welcome. sean Tag: WinCE <-> WinXP (serial over USB) Tag: 51948
  - 15
    - Show the "safe removal" dialog Is there an API to show the dialog programmatically? Tag: WinCE <-> WinXP (serial over USB) Tag: 51947
  - 16
    - Performance question Hi, is it better (regarding the performance) to copy one large buffer via RtlCopyMemory or to copy some small buffer several times? Is there a tool that can do performance monitoring for drivers? Thanks a lot Peter Tag: WinCE <-> WinXP (serial over USB) Tag: 51945
  - 17
    - USB to MIDI QUESTION BY NUBIE I am trying to use the FTDI232BM USB to serial chip in a MIDI application. The FT232BM chip comes with a WDM usb driver and API (FT_Write(lngHandle, strWriteBuffer, LENGTH_MESSAGE, lngBytesWritten))that I can use to send midi data to the chip and it will convert to MIDI serial output. I would like to use the windows MIDI API functions like IRET = midiOutShortMsg(MIDI_OUT_HANDLE, MIDIMSG). My question is what do I have to do to have the FT232BM chip recognized as a MIDI device? Why do I want it to be recognized as a MIDI device when I can already send midi data to it? So that CAKEWALK and other musical applications can use it. Thanks in advance for your input. Bob Tag: WinCE <-> WinXP (serial over USB) Tag: 51939
  - 18
    - ISA Device Driver We are porting Device Control software from MSDOS to Windows 98 and need to write a Device Driver for a legacy ISA Interface Card with Visual C++ 5.0 and the Windows 98 DDK (Driver Development Kit). The sample ISA Device Driver in Chapter 7 of Walter Oney's book "Programming the Microsoft Windows Driver Model" works fine after adding an Interrupt Handler. However, my Device Driver will not install properly (Device Manager error code 2 and does not even call AddDevice or DriverEntry) unless Walter Oney's sample is installed first. The sample does not install properly either but any ideas how to fix this problem to make my Device Driver install independently ? Tag: WinCE <-> WinXP (serial over USB) Tag: 51938
  - 19
    - [newbie] Linked list problem Hi again, just one question: How can I read a kernel double linked list in reverse order? Or, better to say, how can I access the 'last' (the item that linkes to the head again) item, if all I got is a pointer to the head? I've tried this one, but it doesn't seem to work: lastitem = CONTAINING_RECORD(DoubleHead.Blink,MYSTRUCT, linkfield); Any ideas? Thanks a lot Peter Tag: WinCE <-> WinXP (serial over USB) Tag: 51936
  - 20
    - [Q] Many problems installing DDK I'm having a great deal of difficulty getting the Windows Server 2003 DDK to install correctly. I'd like to know if I'm doing something wrong and be set straight. (1) Attempting to build the samples in the kit fails, i.e., several of the samples fail with [relatively minor] errors: bin\x86\prefast\examples\pft-example2.cpp(17) : error C4700: local variable 'a' used without having been initialized bin\x86\prefast\examples\pft-example1.cpp(14) : error C4700: local variable 'j' used without having been initialized Granted, these are trivial but the docs say that the kit should build with no warnings or errors. Hence, my uncertainty as to the quality of the distribution. (2) The setenv.bat file, on line #254, sets an environment variable as follows: set _LINK_=/Tmp This causes the linker to fail because the file "/Tmp" can not be found. What is the _LINK_ symbol used for? This symbol occurs nowhere else in any makefile. *.def, or sources file. As far as I can tell, it's only purpose is to make my life difficult [:-) (3) Finally, when trying to link a simple user-mode application, the linker fails with a LNK4099 message: warning LNK4099: PDB 'mfcs42d.pdb' was not found with 'C:\local\sde\lib\winddk\3790\lib\wxp\i386\mfcs42d.lib' However, mfcs42d.pdb is nowhere in the DDK tree and nowhere on my system. Can someone help my out here? My dev and target platform are XP-Pro. Cheers, Michael Tag: WinCE <-> WinXP (serial over USB) Tag: 51933
  - 21
    - Linked list in kernel mode Hi, I wrote the following code to walk a linked list: >LIST_ENTRY DoubleHead; //points to the head of the double-linked > list, initialized > > [...] > PLIST_ENTRY plistentry = NULL; > PMYSTRUCT pmystruct = NULL; > > if(!IsListEmpty(&DoubleHead)) > { > plistentry = DoubleHead.Flink; > while(plistentry != &DoubleHead) > { > pmystruct = CONTAINING_RECORD(plistentry, MYSTRUCT, > linkfield); > > [...]//Doing some checking with pmystruct here > plistentry = plistentry->Flink;//next one > } > } > Now, the problem is: although the list is filled with valid members (not shown), when I check the items that way, 'pmystruct' contains only invalid members. What am I doing wrong? Thanks a lot Peter Tag: WinCE <-> WinXP (serial over USB) Tag: 51926
  - 22
    - How can we retrieve a postscript file information? Hello. I'm developing postscript driver plug-ins. I know that PScript5.dll makes poscript file information with print data stream from GDI information. I want to know how can I retrieve the postscript file information in rendering plug-in. Thanks, Tag: WinCE <-> WinXP (serial over USB) Tag: 51925
  - 23
    - Creative WebCam NX Ultra & WIA Has anyone ever figured out how to access the Creative WebCam NX Ultra through the WIA scripting object model? The documentation on the WebCam NX Ultra says it is WIA compliant, but I am unable to access it. Here is the simple script that I have been using to test the camera which results in message boxing a zero. BTW-I called the Creative technical support, and they told me that as long as their application worked it was up to Microsoft to get the WIA api working. Another point, I hooked up a Canon 400S still camera (WIA compliant) to the same computer and it worked just fine. 'Testing Script Dim objWia Set objWia = CreateObject("Wia.Script") msgbox objWia.Devices.Count Tag: WinCE <-> WinXP (serial over USB) Tag: 51917
  - 24
    - Purging System of Driver Junk I've been experimenting with USB driver development for a few months now, including "from-scratch" and using existing off-the-shelf drivers and tools. I'd like to completely purge my system of all accumulated junk related to these experiments. I figure I could do it as follows: 1) Browse the registry and remove all folders and symbolic links that contain my vendor and product ID?. 2) Search for and delete all .sys and .inf files that are specific to my driver. Is this the proper approach? Other suggestions? Thanks in advance for the help, Dennis Tag: WinCE <-> WinXP (serial over USB) Tag: 51914
  - 25
    - RtlStringCbVPrintfExW linking error under Win2k Hi, I used RtlStringCbVPrintfExW routine, and it was built ok under Windows XP and Windows Server 2003. But I got the linking error under Windows 2000: my.obj : error LNK2019: unresolved external symbol __imp___vsnwprintf referenced in function _RtlStringVPrintfWorkerW@16 objchk_w2k_x86\i386\netvmini.sys : error LNK1120: 1 unresolved externals Does Windows 2000 not support that routine? PS. I have set the ntstrsafe.lib in my sources file: TARGETLIBS=$(DDK_LIB_PATH)\ndis.lib \ $(DDK_LIB_PATH)\ntstrsafe.lib Tag: WinCE <-> WinXP (serial over USB) Tag: 51911

Hi,

I have to ensure the communication between WinCE Device and Win (XP/2000/Me)
thru USB interface. The device has an ActiveSync dedicated driver (serial
over USB). On WinXP the wceusbsh.sys driver serves it.

The problem is that this WinCE platform is built without ActiveSync. So the
question arises: is it possible to ensure the raw communication based on
these drivers (using ReadFile/WriteFile)?

Maybe the better way would it be to communicate with the device thru the
usbser.sys (identified as 'virtual com')? But I am not sure if the device
driver will serve it without modifications.

Thanks in advance,
Kristian

Top