Windows Server 2003 - Removing Reliance On USB/HID

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
 - Issue while attempting to retrieve the file object's path name associated with process section Hi All, We encountered a issue while attempting to retrieve the file object's path name associated with process section object after renaming the folder that contains the executable image. File System: NTFS OS: seems like all x32 NT based (2000, XP, 2003 & their SP) Steps to reproduce: 1. Create a new folder named "1" on disk (for example, C:) 2. Copy any executable file (e.g., "test.exe") to the created folder. 3. Execute this application. 4. Exit from this application (e.g., "test.exe"). 5. Rename folder "1" to another name (for example, "2"). 6. Execute the application located in this folder ("2\test.exe") that was executed at step 3. What did we get? The new process is successfully running, however we can't get the correct path name for the section object associated with this process, and also we got the incorrect path name in the PsSetLoadImageNotifyRoutine callback routine (see below example #4). As a result of querying the path name of process section we got: \Device\HardDiskXXX\1\test.exe Instead of expected: \Device\HardDiskXXX\2\test.exe We tried the different methods of getting the path name for the section object associated with the process. All methods, except the reading PEB give the incorrect path name:( Example #1. PSECTION pSection; .... get section for process executable image .... PFILE_OBJECT pSectionFile = pSection->Segment->ControlArea->FilePointer; ObQueryNameString(pSectionFile, ......); Example #2. Use IoQueryFileInformation for file object associated with process section object or use ObOpenObjectByName AND ZwQueryInformationFile for this file object Example #3. Direct scan file object fields and get file path name. Example #4. VOID NTAPI _PsSetLoadImageNotifyRoutine( IN PUNICODE_STRING FullImageName, IN HANDLE ProcessId, IN PIMAGE_INFO ImageInfo) { KdPrint(("Load image: %ws\n", FullImageName->Buffer)); } EXTERN_C NTSTATUS DriverEntry( IN PDRIVER_OBJECT pDriverObject, IN PUNICODE_STRING pRegistryPath) { return PsSetLoadImageNotifyRoutine(&_PsSetLoadImageNotifyRoutine); } Basing on PDB information (ntoskrnl.exe) the unexported function MmGetFileNameForSection that is called before executing load-image callback routine got the invalid path name also. What can Microsoft developers say on this matter? Best regards, Andrey Alekseev Development Team ISV System Safety Ltd. http://www.syssafety.com Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76745
 - 2
 - Read Data from USB Hi all, I have a problem in reading the data packets from USB. I have got the USB from the Vendor(IXXAT) , and implemented the code to return handle for USB using CreateFile(). it is returning the Handle and Device path correctly but the BytesRead variable in ReadFile function is always zero. Can any one help me? I think i have almost reached the endpoint in reading the data. Thanks in advance samaya Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76744
 - 3
 - a dumb HID question Why is the HID API still not part of the Platform SDK? The hid*.h files are only contained in the DDK. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76742
 - 4
 - Unable to delete .sys file Hi All. I had posted this issue some times back. Can any one help me on this? This is the story: My driver is working fine as expected. But I am not able to delete the driver (.sys file) from drivers folder or overwrite it with another version , even after unloading the driver successfully !!!. Each time our custemers have to reboot the machine to do it !! Windows says,someuser mapped section is left, so I don't have the permission to delete it. I can delete the driver if I haven't run any user application on top of it. My driver code always runs and uses NonPaged memory pools. Driver is running on Windows XP machine with all driver verifier options enabled (of course without low memory simulation). It doesn't report any errors while I unload the driver. I could not see any resources left after unloading the driver (used Winobj, winmsd, process explorer etc.). And I haven't run Event Viewer. Can anyone suggest, how the application program can prevent deleting a driver file? Application interacts with the driver only through IOCTLs. It does not know .sys's name. Thanking You, Mohamed Biju Koothrat Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76741
 - 5
 - Cursor size Dear All I do not know how to support 64x64 size cursor for display driver in wince5.0, and need add some code or variable to BSP? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76739
 - 6
 - USB 2.0 High Bandwidth Iso I am having an issue with a USB 2.0 high-bandwidth iso endpoint. It isn't behaving the way I expect. The descriptor for the endpoint has the maximum bandwidth -- wMaxPacketsize of 0x1400, meaning 1024 bytes with 3 transfers per microframe. I had assumed that I would use this like any other isochronous endpoint, by sending it a series of 1024-byte packets, so that each microframe would consume 3 such packets. However, that does not seem to be what the host controller driver expects. I was VERY surprised to find that USBD_PIPE_INFORMATION.MaximumPacketSize was 3072, not 1024. Further, if I send it a series of 1024-byte packets, I get USBD_STATUS_INVALID_PARAMETER. It looks as though USBD will only schedule one URB per microframe. So why is this a problem? Well, let's say our data is coming in chunks of 2600 bytes, which means 1024 plus 1024 plus 552. We are using an FX2. Our data rate is lower than the maximum bandwidth. When the FX2 gets an IN token but its FIFO is empty, it does not reply. When that happens, I will get a packet with 1024+1024 bytes plus an error, followed by a packet with 552+1024+1024, but those bytes are all packed together. I can't identify the packet boundaries. So, is it a fact that USBD will only schedule one URB per microframe? Or have I missed something? -- - Tim Roberts, timr@probo.com Providenza & Boekelheide, Inc. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76734
 - 7
 - DIFxApp and unsigned driver I'm trying to use DIFxpp.msi to install an unsigned driver of non-WHQL (custom) class. I set the flag in MsiDriverTable to 8, and included the driver files to the corresponding component. But when the installer runs, only INF file is copied to DRIVERSTORE folder, not the SYS file, causing the setup to issue a prompt for SYS file. What could cause that? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76733
 - 8
 - lib file for AudioEngineBaseAPO.h Hi, I'm trying to link a APO DLL using the February CTP SDK, and is having linking errors to link functions defined in AudioEngineBase.h. Does anyone know which lib file I need to link to? Thanks KS Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76731
 - 9
 - Any white paper or samples on KSPROPSETID_Jack implementation? I'm trying to add Jack description to my audio device so that Vista will be able to display it on the speaker endpoint. Unfortunately, only manage to find the macros and definitions(portcls.h) in the WDK 5308, but not a single sample or doc on it. Thanks! Kenny. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76730
 - 10
 - IOCTL_INTERNAL_MOUSE_CONNECT Hello I already got a working IOCTL that gives me the info i need from my user application. And now i want that every time i send my own IOCTL with an x and y values for the mouse to execute the mouse_callbackfunctie and insert a self made package with the x and y from my IOCTL.. Does it take much time to replace the IOCTL_INTERNAL_MOUSE_CONNECT (located under IRP_MJ_INTERNAL_DEVICE_CONTROL) that triggers the Mouse_Callbackfunction with a own made IOCTL? I get my IOCTL with help of an control device and in that control device i get my data with help of the Home made IOCTL. I hope it's possible to answer. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76727
 - 11
 - IR communication using non standard protocol Hi, I have an electronic device that communicates with my PC (running Windows XP) using infrared communication. The protocol it uses is like this: For instance to get a buffer status the PC can send B\r to the device, and the device will respond with something like B\r00\rOK\r if the buffer is empty. In other words you send the command to the device and it responds with the command, the answer to the request, and "OK". Currently I use an infrared transmitter connected to one of the COM ports in the PC to communicate with the device. In C sharp I have written a program that communicates directly with the COM port the device is connected to: I open the COM port, sends a command to the device, and waits for a response. It works okay but now I also want to use an IR transmitter connected to an USB port! Virtual com ports and IR is not a possible solution in Windows 2000/XP! Is there an IR communication class that makes it possible to write a program that uses the IR interface there is in Windows 2000/XP to communicate with any IR device - regardless of how it is connected to the PC (as long as it just has a driver)? I know there is something like this for (win)socket programming but will that be possible to use in this case/ with the protocol I described? Best regards, Kim Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76722
 - 12
 - STATUS_INVALID_DEVICE_REQUEST from IoGetDeviceObjectPointer Hi, I'm trying to get a pdo pointer to send IRP_MN_READ_CONFIG requests to. For most devices this works fine but for some devices I get STATUS_INVALID_DEVICE_REQUEST. Any idea why? Thanks Hua-Ying Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76717
 - 13
 - How to modify volume/partition/drive name in code When a partition is created from disk management untility, a volume name can be created for it. How can the volume/partition/drive name for a removable storage device like RAMDISK be modified in the code ? Where the information is stored (I could not find it in registry, is it stored in the disk device ? Thanks -Gary Li Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76716
 - 14
 - hid minidriver w2k freeze when setup Hi List, I have an issue, when I setup my HID minidriver under windows 2k, installation process freeze, while everything are OK under windows XP. During setup, after standard IRPs (i.e. start, hid_get_*, etc) minidriver receive a couple of IRP_MN_QUERY_ID ('BusRelations' and 'BusQueryHardwareIDs'), the number of collection it expose (in my case 4). Then it receive 2 IOCTL_HID_READ_REPORT for ping pong IRPs. At this time "new hardware" wizard ask me to click on "finish" button... So do I With Win2k, minidriver get 2 new IRP_MN_QUERY_ID and freeze. In device manager first collection appear this an exclamation mark. At this point I must reboot to unlock. Does something could be wrong in IRP_MN_QUERY_ID handling ? minidriver reply a string like "Vid_1234&Pid_5678" to those IRPs, is that correct ? Or there is something else to do ? note: in IOCTL_HID_READ_REPORT handler, I call IoMarkIrpPending() to the received IRPs and return STATUS_PENDING... Is that correct ? Regards -- Benoit Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76710
 - 15
 - AddPrinterDriverEx with APD_COPY_ALL_FILES to upgrade a driver ? Hello all, I need to be able to update a printer driver when files may be in use. Can someone confirm that when calling AddPRinterDriverEx with the Option APD_COPY_ALL_FILES, Windows take care of drivers files in use and mark them to be moved on reboot ? TIA. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76709
 - 16
 - BluetoothFindFirstDevice help ! 911 Hi guys, I'm stucked with a bluetooth application. Shortly , my visual c++ 2003 bluetooth code is intended to query for devices nearby (example : my cellphone with bluetooh) I'm using the below code; (my code compiles fine, but when I hit the line, BtHandle = BluetoothFindFirstDevice(&search_param, &btDevInfo); I debug and assume that it will wait for querying devices nearby but it immediately switches to dissambler code; I then toogle another breakpoint to another line below this line and resume from debug , it comes to this line and i see that "BtHandle" returns "unknown value" , as if it doesnot query any devices, something wrong occurs here as much as i understand here. Where am i doing wrong here ? Someone please shed a light upon me due i'm stucked at this point. I'm using built-in Widcomm stack in my Win2003 server. Does it matter for this code to work on different stacks? (Microsoft,Widcomm,Toshiba,etc..) Actually, the application i'm working on is intended to work on any machine with bluetooth whatever bluetooth stack it has ? Where do i have to start from ? This is an urgent call, please some experienced guy, direct me in the right order. Thanks much and Regards Tiger Developer HBLUETOOTH_DEVICE_FIND BtHandle; BLUETOOTH_DEVICE_INFO btDevInfo; BLUETOOTH_DEVICE_SEARCH_PARAMS search_param; memset(&search_param, 0, sizeof(search_param)); search_param.dwSize = sizeof(search_param); search_param.fReturnAuthenticated = FALSE; search_param.fReturnRemembered = FALSE; search_param.fReturnUnknown = TRUE; search_param.fReturnConnected = FALSE; search_param.fIssueInquiry = TRUE; search_param.cTimeoutMultiplier = 20; search_param.hRadio = NULL; memset(&btDevInfo, 0, sizeof(btDevInfo)); btDevInfo.dwSize = sizeof(btDevInfo); device_count = 0; BtHandle = BluetoothFindFirstDevice(&search_param, &btDevInfo); if (BtHandle == 0) { last_error = GetLastError(); printf("\nNo devices found: %d", last_error); BluetoothFindDeviceClose(BtHandle); exit (0); } else { szAccept = 'y'; bContinue = TRUE; while (bContinue) { device_count++; wcstombs(szDeviceName, btDevInfo.szName, sizeof(szDeviceName)); printf("\nFound Device %d : %s", device_count, szDeviceName); printf("\nDevice address %x", btDevInfo.Address.ullLong); if (btDevInfo.fConnected) printf("\n It is connected"); else printf("\n Device is not connected"); if (btDevInfo.fRemembered) printf("\n It is remembered"); else printf("\n Device is not remembered"); printf("\nPress 'y' to accept or 'n' to not accept this device "); szAccept = _getch(); if (szAccept == 'n') { memset(&btDevInfo, 0, sizeof(btDevInfo)); btDevInfo.dwSize = sizeof(btDevInfo); bResult = BluetoothFindNextDevice(BtHandle, &btDevInfo); if (bResult == FALSE) { last_error = GetLastError(); printf("\nBluetoothFindNextDevice returned error: %d", last_error); BluetoothFindDeviceClose(BtHandle); exit (0); } } else bContinue = FALSE; } } Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76707
 - 17
 - how to block access to floppy ? Need help! I want to block access to my floppy, and let administrator can access it only. At first, I have an idea that is to do a filter driver which could be attached to floppy driver. But I found it's so difficult to do that because I 'm a novice to ddk. Let alone what kinds of datas (ie. Irps) should I blocked. Recently, I found something about how to block access to floppy in the group. The link is http://groups.google.com/group/microsoft.public.win32.programmer.kernel/browse_thread/thread/06dc46a69fca7c9e?hl=zh-CN I try do program as what Karan Mehra have said. But I found it did not work! Is there maybe some wrong with my code below? p= _T("D:P"); hDevInfo=SetupDiGetClassDevs(&guid,NULL,NULL,DIGCF_PRESENT); if(hDevInfo==INVALID_HANDLE_VALUE) { printf("wrong!"); return 1 ; } DWORD i, err; SP_DEVINFO_DATA DeviceInfoData; ZeroMemory(&DeviceInfoData, sizeof(SP_DEVINFO_DATA)); DeviceInfoData.cbSize = sizeof(SP_DEVINFO_DATA); for (i = 0; SetupDiEnumDeviceInfo(hDevInfo, i, &DeviceInfoData); ++i) { if (!SetupDiSetDeviceRegistryProperty(hDevInfo, &DeviceInfoData, SPDRP_SECURITY_SDS, (LPBYTE)p, strlen(p)+1)) and set SPDRP_CHARACTERISTICS by using SetupDiSetDeviceRegistryProperty as follow: CharacterFlags = GetDeviceCharacterFlags(hDevInfo, &DeviceInfoData); CharacterFlags |= FILE_DEVICE_SECURE_OPEN; SetDeviceCharacterFlags(hDevInfo, &DeviceInfoData, CharacterFlags); VOID SetDeviceCharacterFlags( IN HDEVINFO DeviceInfoSet, IN PSP_DEVINFO_DATA DeviceInfoData, IN DWORD CharacterFlags ) { if(!SetupDiSetDeviceRegistryProperty(DeviceInfoSet, DeviceInfoData, SPDRP_CHARACTERISTICS, (PBYTE)&CharacterFlags, sizeof(CharacterFlags) )) { printf("unavailble"); } printf("it is ok!"); } DWORD GetDeviceCharacterFlags( IN HDEVINFO DeviceInfoSet, IN PSP_DEVINFO_DATA DeviceInfoData ) { DWORD CharacterFlags; if(!SetupDiGetDeviceRegistryProperty(DeviceInfoSet, DeviceInfoData, SPDRP_CHARACTERISTICS, NULL, (PBYTE)&CharacterFlags, NULL, (unsigned long *) sizeof(CharacterFlags) )) { printf("unsucess to get device property spdrp_characteristicse"); CharacterFlags = 0; } return CharacterFlags; } I could complie my program, and build exe file. but I found it did not work! Could you point out to me whether there are something I have not noticed. Or the idea is absolutely wrong to do that in winxp? I' m very appreciated if you can reply to me soon, and thank you in advance. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76704
 - 18
 - How to do defragment and analysis on disk? Hi, all: I need do defragment and anlysis on some disks, but I can not find WINDOWS API to do this task in MSDN Library, how can I do it? By the way, I found that the windows has provided WMI interfaces(Win32_Volume) to do this task, but tihis is limited to Windows2003 system, I need do this task on any system, including: windows2000 and XP. Thanks a lot! Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76703
 - 19
 - Walter Oney WDM: CacheControlRequest() resets computer while calling IoMarkPending(Irp) Hi I'm using Walter Oney's book and routines to implement a driver for a PCI card. The code for CacheControlRequest() is exactly the same as on Walters Oney book on page 503 The computer resets completely while calling IoMarkPending(Irp) inside CacheControlRequest() While calling DispatchControl and IOCTL_WAIT_NOTIFY implemented without calling CacheControlRequest() the driver returns a Status value without problems. It is also possible without problems to call IOCTL_GET_VERSION_BUFFERED. Calling DispatchControl and IOCTL_WAIT_NOTIFY implemented with the CacheControlRequest() function resets the computer completely and later on starts without problems. What can be done to solve the problem? Any help or hints would be kindly apreciated Best Regards Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76699
 - 20
 - USB device as Serialport I am having one usb card, as soon as I connect this card to my pc, I want to create one com port in my windows 98/ME system, and the application running on windows can open this com port can communicate. How can I proceed doing this. Jyothi Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76698
 - 21
 - Enabling debug options in NDIS Debug options in checked ndis.sys can be set with ndiskd windbg extension (dbgsystems, dbglevel). How to set these manually, without ndiskd extensions or registry? Are there exported variables like for other subsystems (KB314743) ? --PA Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76688
 - 22
 - Configuration Manager on 2K3 asks 10 minutes for enabling 1394 device...?!? This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C63D53.13D601D0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable It's seen as Microsoft's bug inside Configuration Manager (CM) for = Windows 2003 Server version... Problem reproducing in 2 steps: 1. Device Manager tries enabling 1394 device (disk) and sleeps down such = as all (!?!) CM operations are blocked.=20 2. CM can't recognize new PnP device or support enabling/disabling for = existing. Even Devcone.exe enable/disable is opened in other session for = any not 1394(!) devices are waiting for... After ~10 minutes (?!?) CM wakes up and continues well! The problem only in 10 minutes interval of CM inactivity... :( CM is seen as single thread and waiting for internal event or critical = section... Additional Information: 1. The same device on the same computer, but under Windows XP (dual = boot) works perfectly. 2. I set up the latest Microsoft Windows Server 2003 R2 Enterprise = Edition Service Pack 1. 3. Disk may be attached or "disabled from Device Manager before Step 1" = with same result. 4. Appropriate Devcon command line may be used instead of Device Manager = for 1394 enabling with same result. Thanks for help & Regards, Michael.=20 ------=_NextPart_000_000A_01C63D53.13D601D0 Content-Type: text/html; charset="windows-1255" 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=3Dwindows-1255"> <META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV>It's seen as Microsoft's bug inside = Configuration=20 Manager (CM) for Windows 2003 Server version... Problem = reproducing in 2=20 steps: 1. Device Manager tries enabling 1394 device = (disk)=20 and sleeps down such as all (!?!) CM operations are = blocked.=20 2. CM can't recognize new PnP device or support enabling/disabling = for=20 existing. Even Devcone.exe enable/disable is opened in other session for = any not=20 1394(!) devices are waiting for... After ~10 minutes = (?!?) CM=20 wakes up and continues well! The problem only in 10 = minutes=20 interval of CM inactivity... :( CM is seen as single thread and = waiting for=20 internal event or critical section... Additional = Information: 1.=20 The same device on the same computer, but under Windows XP (dual = boot)=20 works perfectly. 2. I set up the latest Microsoft = Windows=20 Server 2003 R2 Enterprise Edition Service Pack=20 1. 3. Disk may be attached or "disabled from Device Manager = before=20 Step 1" with same result. 4. Appropriate Devcon command line may be = used=20 instead of Device Manager for 1394 enabling with same = result. Thanks=20 for help & Regards, Michael. </DIV></BODY></HTML> ------=_NextPart_000_000A_01C63D53.13D601D0-- Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76673
 - 23
 - setting MTU size for NDISWAN I am trying to get a dialup connection to use 576 bytes MTU. I have tried setting the registry value that is supposed to do it ... HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\NdisWanIp\MTU but this does nothing at all! I have also tried setting this value ... HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MTU this also does nothing!!! Both times I restarted after making the change. My MTU size is always 1500!!! So now I'm trying to do it in my imdriver using OIDs ... OID_GEN_MAXIMUM_FRAME_SIZE and OID_WAN_SET_LINK_INFO ... guess what? These also do nothing!!! I am going to cry!!! Please can someone help? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76672
 - 24
 - Cancel a printer job Hi, I want to know if the following is possible. When an user tries to print a file, a dialog should pop up asking the user for his / her credentials. If the credentials are not correct then the print job for that file should be cancelled. I tried subscribing to the printer event e.g. JOB_CHANGED and then cancelled the print job. However, in many cases the file was already printed before my application could cancel the job. What is the right place to hook (e.g. Print monitor, Print provider, Print processor, Printer driver etc) into the printer to achieve the same. Thanks, Vishal Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76663
 - 25
 - Obtaining interrupt vector in IRP_MN_START_DEVICE Hello! I written a driver. It is a upper-filter driver for serial devices. The driver handles 4-byte timeout. Earlier, when I tested it in Intel under Windows XP SP1 it worked correctly, vector got by code if(PartialDescriptors[i].Type == CmResourceTypeInterrupt){ vector = stack->Parameters.StartDevice.AllocatedResourcesTranslated[0].List[0].PartialResourceList.PartialDescriptors[i].u.Interrupt.Vector; } has a correct value 0x34. Now I test driver in AMD under Windows XP SP2. Vector value is 0x191 - it is wrong, it is out of IDT bounds... What happens, explain me please. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76660
- Next
 - 1
 - CSpinButtonCtrl could not be used in a coinstaller program? hello everyone: I encountered a strange problem here, that is there is an error while the device manager load a property page i wrote, and the page contains a CSpinButtonCtrl (MFC class), the error shows that ACCESS violation. while i remove the CSpinButtonCtrl , every thing is ok,what's wrong ? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76658
 - 2
 - NDIS + Windows Mobile 5.0 = Fun? I've been thinking of getting a new PDA Phone. And then I got to thinking, hey if it uses the NDIS model I can probably hack it and do all sorts of funky stuff. Like make it a router (maybe) that my bluetooth enabled laptop could use, wirelessly, while I'm driving, and shaving, and drinking latte. So I started looking it up but I don't see any definitive answer on the driver model that Windows Mobile 5 uses. Can anyone help? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76652
 - 3
 - Reading/Writing To A Device on SMBus in Windows XP Embedded I've seen several posting with answers related to this, but none with an answer so I want to try asking it a different way. I have a system running Windows XP Embedded. On it's SMBus there is a chip which controls the brightness and contrast of the LCD panel hooked into the LVDS. The problem is that the manufacturer of my board does not supply an API for my board to read and write to the SMBus. So, does anyone know what I have to do to be able to read and write (single bytes only) to this device on the SMBus? I have the SMBus Device Driver external architecture specification from Intel, but can't seem to get any of the examples in it to compile, despite hours of trying. I've also searched and searched for example or other information that would help but to no avail. My board has an Intel 82801DB/DBM SMBus Controller driver installed (hence why I was trying to use the specification from Intel, et al). Can anyone help me figure out what I'm doing wrong or where I can find information on reading from/writing to the SMBus? Thanks, Mike Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76641
 - 4
 - Serial Mouse driver Hi, I want to use some legacy mice for windows XP. They are from Mouse systems and can't find any compatible driver. I am trying to write a generic serial mouse driver. Any suggestions? I installed XP DDK SP1 and tried sample driver and it doesn't detect any input. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76639
 - 5
 - DMA mapping question Hello all, I am working on a driver for which I would like to DMA buffers to a device where the buffers have not been specifically allocated for a given device. These buffers are created common kernel memory and we don't know to which device they will be transmitted before hand. I would like to use MmAllocateContiguousMemory to get the buffers and MmGet PhysicalAddress to map them, but this MSDN is replete with warnings about using MmAllocateContiguousMemory for DMA. If we use AllocateCommonBuffer then we incur the cost of copying each buffer before transmission. Any suggestions on how we can effeciently DMA these buffers? Thanks, Tom Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76635
 - 6
 - ERROR_DRIVER_BLOCKED x64 Server 2003, build 3790, SP1 Get ERROR_DRIVER_BLOCKED (STATUS_DRIVER_BLOCKED_CRITICAL, decimal 1275) from StartService(). What causes that particular error? Enio. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76633
 - 7
 - filter on usbprint.sys, WORK?? Now I am trying to add a filter on a USB printer. I add a lowerfilters on the usbprint.sys, and I find out the majorfunction is IRP_MJ_DEVICE_CONTROL, but I didn't how to find the real operation code and where to find ? My final aim is to control the printer. Make it LOCK or UNLOCK. I intend to stop the operation code. Does it work? Please give me some hints, thanks ! bob Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76631
 - 8
 - CreateInitiatorLu and windows 2k3 Hi All, I've seen that the CreateInitiatorLU registry entry is supported by windows 2003 server and above. Does it also imply that there need not be any device on Lun 0 for a target to be scanned further or still the Lun 0 should always have some device? Regards, Killme. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76629
 - 9
 - Newbie: How to create or allocate a copy of symbolic link (UNICODE_STRING)? : Hi all, I´m trying to get an inter-driver communication. I´d read that it´s better to make use of WorkItems instead of calling "IoGetDeviceObjectPointer" directly from the "IoRegisterPlugPlayNotification" callback function. (I´m using "IoRegisterInterface"). Ok. My problem is that I don´t know how to create or allocate a copy of the 'SymbolicLinkName' got from the 'IoRegisterPlugPlayNotification' notification structure. SymbolicLinkName is necessary because I need to call the "IoGetDeviceObjectPointer" function inside the "IoQueueWorkItem" callback routine. Here is my code: ------------------------------------------------------------ typedef struct _MY_WORK_CONTEXT { PIO_WORKITEM Item; PUNICODE_STRING SymbolicLinkName; } MY_WORK_CONTEXT, *PMY_WORK_CONTEXT; NTSTATUS PNPCallbackFunction( IN PDEVICE_INTERFACE_CHANGE_NOTIFICATION NotificationStructure, IN PVOID Context ) { NTSTATUS status = STATUS_SUCCESS; PDEVICE_INTERFACE_CHANGE_NOTIFICATION notify = NotificationStructure; PDEVICE_OBJECT deviceObject = (PDEVICE_OBJECT)Context; PIO_WORKITEM workItem; PMY_WORK_CONTEXT myWorkContext; if(IsEqualGUID(notify->Event, GUID_DEVICE_INTERFACE_ARRIVAL)) { workItem = IoAllocateWorkItem(deviceObject); myWorkContext = (PMY_WORK_CONTEXT) ExAllocatePoolWithTag(NonPagedPool, sizeof(MY_WORK_CONTEXT), 'cWbD'); if(!myWorkContext) { IoFreeWorkItem(workItem); return(STATUS_XXX); } // WorkItem to the CONTEXT struct myWorkContext->Item = workItem; // Symbolic Lynk to the CONTEXT struct myWorkContext->SymbolicLinkName = notify->SymbolicLinkName; // OF COURSE I CAN´T DO THAT... WHAT CAN I DO??? // Queue WorkItem IoQueueWorkItem(workItem, (PIO_WORKITEM_ROUTINE)CallbackWorker, DelayedWorkQueue, (PVOID)myWorkContext); } return status; } ---------------------------------------------------------------------- Can anybody help me? Thanks a lot!!! Paulo. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76627
 - 10
 - How can I put dependency while installing a PNP driver? Hi All, I have two pci devices. Functional drivers for both these PNP devices need services from another driver(bus driver for a dummy device) which should be loaded first. If I try to install any PNP driver manually (from DeviceManager), how can the inf automatically install the non-PNP driver first ? I cannot load nonPNP driver as an export driver for some reason. StartType for nonPNP driver is SERVICE_BOOT_START and that for PNP drivers is SERVICE_DEMAND_START. I tried with Include and Needs on inf for PNP device to read inf for nonPNP device, but it installs only non-PNP driver and doesnot come back. So can any one suggest a solution for this? Thanks & Regards Biju Mohamed K Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76626
 - 11
 - When the spooler will go to RAW mode? Heya, since there is no way you can force some format over another, can the expected format to be "detected" in advance in order to warn the users or not list the printer or whatever... After some reading around I found out a nice list from Ashwin [MS] and completed by Carey Gregory: We'll go RAW in the following cases: - Printing to FILE: - this can be detected with ease - Printing directly to port (no spooling) - this can be detected with ease - Client disables "advanced printing features" in printer properties - How to detect this? Haven't seen a reference in all PRINTER_INFO structures or attribs? Additionally, for networking printing: - Client is anything other than NT/Win200/XP - Checking for a network port and then? - Client doesn't use a "true" connection - Don't even have an idea what that means, how to detect? - Printing to a "masq" printer (win9x, netware, etc.) - this one too... - Server has "printer attribute RAW only" bit set - this can be detected with ease - Server doesn't accept client's EMF version - how to detect? - Client and server OS versions don't match exactly - again, how to detect... Additionally, I have some network HP around - nice printer with a full cd drivers which take half an hour to install. Printing to it using its own drivers *always* result in RAW mode, while if I simply install HP LaserJet 6L and redirect it to the same IP, on the same PC, it goes to EMF. Something missing from the list? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76624
 - 12
 - Problems with PPPoE At this moment our biggest problem is point 4 from the ones I listed here. We are currently working on PPP over Ethernet protocol driver. Our driver has been built as NDIS IM protocol driver using NDIS 4.0 and TAPI 1.4. The driver are consists of protocol and miniport layers: - Protocol is bind to: ethernet (lower) and our miniport (upper). - Miniport is bind to: our protocol (lower) and NDISWAN (upper). The driver is building with DDK 3790.1830 2K build environment and following C_DEFINES: C_DEFINES=-DNDIS_MINIPORT_DRIVER=1 -DNDIS_WDM=1 -DDEBUG=1 \ -DNDIS40_MINIPORT=1 -DNDIS40=1 -DUSE_KLOCKS=1 -DBINARY_COMPATIBLE=1 \ -DWIN9X_COMPAT_SPINLOCK=1 -D_WIN2K_COMPAT_SLIST_USAGE=1 \ -DNDIS_TAPI_CURRENT_VERSION=0x10004 -DTAPI_CURRENT_VERSION=0x10004 The driver works fine on 2K/XP/2K3, but on 98/ME we have following problems: 1) OID_TAPI_PROVIDER_INITIALIZE gives us ulDeviceIDBase=0 and occures two times. Is this correct ? (START) 00004173 13:31:02.720 ==> alpppoe->DriverEntry 00004174 13:31:02.720 alpppoe->DriverEntry: Driver: 0xf818c6d8 00004175 13:31:02.720 alpppoe->DriverEntry: Wrapper has initialized 00004176 13:31:02.720 alpppoe->DriverEntry: Handle: 0xf816a430 00004177 13:31:02.720 alpppoe->DriverEntry: Miniport has registered 00004178 13:31:02.720 alpppoe->DriverEntry: Protocol has registered 00004179 13:31:02.720 <== alpppoe->DriverEntry: 0x00000000 (...) 00000007 18:09:30.749 ==> miniport->MPQuery 00000008 18:09:30.749 miniport->MPQuery: OID: 0x07030118 00000009 18:09:30.749 ==> QRQ_OID_TAPI_PROVIDER_INITIALIZE 00000010 18:09:30.749 QRQ_OID_TAPI_PROVIDER_INITIALIZE: ulDeviceIDBase: 0x00000000 00000011 18:09:30.749 <== QRQ_OID_TAPI_PROVIDER_INITIALIZE 00000012 18:09:30.749 <== miniport->MPQuery: 0x00000000 00000013 18:09:30.749 ==> miniport->MPSet 00000014 18:09:30.749 miniport->MPSet: OID: 0x07030119 00000015 18:09:30.749 ==> SRQ_OID_TAPI_PROVIDER_SHUTDOWN 00000017 18:09:30.749 <== SRQ_OID_TAPI_PROVIDER_SHUTDOWN 00000018 18:09:30.754 <== miniport->MPSet: 0x00000000 00000019 18:09:30.754 ==> miniport->MPQuery 00000020 18:09:30.754 miniport->MPQuery: OID: 0x07030118 00000021 18:09:30.754 ==> QRQ_OID_TAPI_PROVIDER_INITIALIZE 00000022 18:09:30.754 QRQ_OID_TAPI_PROVIDER_INITIALIZE: ulDeviceIDBase: 0x00000000 00000023 18:09:30.754 <== QRQ_OID_TAPI_PROVIDER_INITIALIZE 00000024 18:09:30.784 <== miniport->MPQuery: 0x00000000 00000025 18:09:30.784 ==> miniport->MPQuery 00000026 18:09:30.784 miniport->MPQuery: OID: 0x07030112 00000027 18:09:30.784 ==> QRQ_OID_TAPI_GET_EXTENSION_ID 00000029 18:09:30.784 <== QRQ_OID_TAPI_GET_EXTENSION_ID 00000030 18:09:30.799 <== miniport->MPQuery: 0x00000000 00000031 18:09:30.799 ==> miniport->MPQuery 00000032 18:09:30.799 miniport->MPQuery: OID: 0x07030110 00000033 18:09:30.799 ==> QRQ_OID_TAPI_GET_DEV_CAPS 00000034 18:09:30.799 QRQ_OID_TAPI_GET_DEV_CAPS: ulDeviceId: 0x00000000, ulExtVersion: 0x00000000 00000035 18:09:30.799 QRQ_OID_TAPI_GET_DEV_CAPS: ulMediaModes: 0x00000000 00000036 18:09:30.799 QRQ_OID_TAPI_GET_DEV_CAPS: Buf->Len: 248, ulTotalSize: 236, ulNeededSize: 284 00000037 18:09:30.799 <== QRQ_OID_TAPI_GET_DEV_CAPS 00000038 18:09:30.799 <== miniport->MPQuery: 0x00000000 00000039 18:09:30.799 ==> miniport->MPQuery 00000040 18:09:30.799 miniport->MPQuery: OID: 0x07030110 00000041 18:09:30.799 ==> QRQ_OID_TAPI_GET_DEV_CAPS 00000042 18:09:30.799 QRQ_OID_TAPI_GET_DEV_CAPS: ulDeviceId: 0x00000000, ulExtVersion: 0x00000000 00000043 18:09:30.799 QRQ_OID_TAPI_GET_DEV_CAPS: ulMediaModes: 0x00000000 00000044 18:09:30.799 QRQ_OID_TAPI_GET_DEV_CAPS: Buf->Len: 584, ulTotalSize: 572, ulNeededSize: 284 00000046 18:09:30.799 <== QRQ_OID_TAPI_GET_DEV_CAPS 00000047 18:09:30.799 <== miniport->MPQuery: 0x00000000 00000048 18:09:30.799 ==> miniport->MPQuery 00000049 18:09:30.799 miniport->MPQuery: OID: 0x07030117 00000050 18:09:30.799 ==> QRQ_OID_TAPI_OPEN 00000051 18:09:30.799 QRQ_OID_TAPI_OPEN: HtLine: 0x00000234 00000052 18:09:30.799 ==> miniport->Line 00000054 18:09:30.799 miniport->Line: OPEN (0x00000200) 00000055 18:09:30.799 miniport->Line: NdisMIndicateStatus(LINE_LINEDEVSTATE): 0x00000200 00000056 18:09:30.799 <== miniport->Line 00000056 18:09:30.799 ==> miniport->Call 00000058 18:09:30.799 miniport->Call: IDLE (0x00000001) 00000059 18:09:30.799 miniport->Call: NdisMIndicateStatus(LINE_CALLSTATE): 0x00000001 00000060 18:09:30.799 <== miniport->Call 00000062 18:09:30.799 <== QRQ_OID_TAPI_OPEN 00000063 18:09:30.804 <== miniport->MPQuery: 0x00000000 00000064 18:09:30.804 ==> miniport->MPQuery 00000065 18:09:30.804 miniport->MPQuery: OID: 0x07030110 00000066 18:09:30.804 ==> QRQ_OID_TAPI_GET_DEV_CAPS 00000067 18:09:30.804 QRQ_OID_TAPI_GET_DEV_CAPS: ulDeviceId: 0x00000000, ulExtVersion: 0x00000000 00000068 18:09:30.804 QRQ_OID_TAPI_GET_DEV_CAPS: ulMediaModes: 0x00000000 00000069 18:09:30.804 QRQ_OID_TAPI_GET_DEV_CAPS: Buf->Len: 252, ulTotalSize: 240, ulNeededSize: 284 00000070 18:09:30.804 <== QRQ_OID_TAPI_GET_DEV_CAPS 00000071 18:09:30.804 <== miniport->MPQuery: 0x00000000 (...) 2) OID_TAPI_GET_ID gives us ulDeviceClassOffset="ndis" and ulSelect=LINECALLSELECT_LINE or further LINECALLSELECT_ADDRESS. What should we return as DeviceID in that cases ? We are returning ulDeviceIDBase value (it's zero) in both cases because we have only one channel. Is it correct ? (...) 00000072 18:09:30.804 ==> miniport->MPQuery 00000073 18:09:30.804 miniport->MPQuery: OID: 0x07030113 00000074 18:09:30.804 ==> QRQ_OID_TAPI_GET_ID 00000075 18:09:30.804 QRQ_OID_TAPI_GET_ID: Device class: ndis, ulSelect: 0x00000001 00000076 18:09:30.804 QRQ_OID_TAPI_GET_ID: hdCall: 0x00000000, hdLine: 0xc1bb1440 00000077 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulAddressID: 0x00000000 00000079 18:09:30.804 QRQ_OID_TAPI_GET_ID: DeviceId=0x00000000 (UlDeviceID) 00000081 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulTotalSize : 24 00000082 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulNeededSize: 33 00000084 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulUsedSize : 33 00000085 18:09:30.804 <== QRQ_OID_TAPI_GET_ID 00000086 18:09:30.804 <== miniport->MPQuery: 0x00000000 00000087 18:09:30.804 ==> miniport->MPQuery 00000088 18:09:30.804 miniport->MPQuery: OID: 0x07030113 00000089 18:09:30.804 ==> QRQ_OID_TAPI_GET_ID 00000090 18:09:30.804 QRQ_OID_TAPI_GET_ID: Device class: ndis, ulSelect: 0x00000001 00000091 18:09:30.804 QRQ_OID_TAPI_GET_ID: hdCall: 0x00000000, hdLine: 0xc1bb1440 00000092 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulAddressID: 0x00000000 00000094 18:09:30.804 QRQ_OID_TAPI_GET_ID: DeviceId=0x00000000 (UlDeviceID) 00000096 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulTotalSize : 33 00000097 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulNeededSize: 33 00000099 18:09:30.804 QRQ_OID_TAPI_GET_ID: ulUsedSize : 33 00000100 18:09:30.804 <== QRQ_OID_TAPI_GET_ID 00000101 18:09:30.804 <== miniport->MPQuery: 0x00000000 00000102 18:09:30.804 ==> miniport->MPQuery 00000103 18:09:30.804 miniport->MPQuery: OID: 0x07030114 00000104 18:09:30.804 ==> QRQ_OID_TAPI_GET_LINE_DEV_STATUS 00000105 18:09:30.804 QRQ_OID_TAPI_GET_LINE_DEV_STATUS: ulTotalSize : 76 00000106 18:09:30.804 QRQ_OID_TAPI_GET_LINE_DEV_STATUS: ulNeededSize: 76 00000108 18:09:30.804 <== QRQ_OID_TAPI_GET_LINE_DEV_STATUS 00000109 18:09:30.804 <== miniport->MPQuery: 0x00000000 00000110 18:09:30.804 ==> miniport->MPQuery 00000111 18:09:30.804 miniport->MPQuery: OID: 0x07030114 00000112 18:09:30.804 ==> QRQ_OID_TAPI_GET_LINE_DEV_STATUS 00000113 18:09:30.804 QRQ_OID_TAPI_GET_LINE_DEV_STATUS: ulTotalSize : 76 00000114 18:09:30.804 QRQ_OID_TAPI_GET_LINE_DEV_STATUS: ulNeededSize: 76 00000116 18:09:30.804 <== QRQ_OID_TAPI_GET_LINE_DEV_STATUS 00000117 18:09:30.809 <== miniport->MPQuery: 0x00000000 00000118 18:09:30.809 ==> miniport->MPSet 00000119 18:09:30.809 miniport->MPSet: OID: 0x07030122 00000120 18:09:30.809 ==> SRQ_OID_TAPI_SET_STATUS_MESSAGES 00000123 18:09:30.809 <== SRQ_OID_TAPI_SET_STATUS_MESSAGES 00000124 18:09:30.809 <== miniport->MPSet: 0x00000000 00000125 18:09:30.809 ==> miniport->MPQuery 00000126 18:09:30.809 miniport->MPQuery: OID: 0x0703010a 00000127 18:09:30.809 ==> QRQ_OID_TAPI_GET_ADDRESS_CAPS 00000128 18:09:30.809 QRQ_OID_TAPI_GET_ADDRESS_CAPS: ulDeviceID: 0x00000000, ulAddressID: 0x00000000, ulExtVersion: 0 00000129 18:09:30.809 <== QRQ_OID_TAPI_GET_ADDRESS_CAPS 00000130 18:09:30.809 <== miniport->MPQuery: 0x00000000 00000131 18:09:30.809 ==> miniport->MPQuery 00000132 18:09:30.809 miniport->MPQuery: OID: 0x0703010a 00000133 18:09:30.809 ==> QRQ_OID_TAPI_GET_ADDRESS_CAPS 00000134 18:09:30.809 QRQ_OID_TAPI_GET_ADDRESS_CAPS: ulDeviceID: 0x00000000, ulAddressID: 0x00000000, ulExtVersion: 0 00000135 18:09:30.809 <== QRQ_OID_TAPI_GET_ADDRESS_CAPS 00000136 18:09:30.844 <== miniport->MPQuery: 0x00000000 00000137 18:09:30.844 ==> miniport->MPQuery 00000138 18:09:30.844 miniport->MPQuery: OID: 0x07030111 00000139 18:09:30.844 ==> QRQ_OID_TAPI_GET_DEV_CONFIG 00000141 18:09:30.844 <== QRQ_OID_TAPI_GET_DEV_CONFIG: 0x00000000 00000142 18:09:30.844 <== miniport->MPQuery: 0x00000000 00000143 18:09:30.844 ==> miniport->MPQuery 00000144 18:09:30.844 miniport->MPQuery: OID: 0x07030111 00000145 18:09:30.844 ==> QRQ_OID_TAPI_GET_DEV_CONFIG 00000147 18:09:30.844 <== QRQ_OID_TAPI_GET_DEV_CONFIG: 0x00000000 00000148 18:09:30.844 <== miniport->MPQuery: 0x00000000 00000149 18:09:30.844 ==> miniport->MPQuery 00000150 18:09:30.844 miniport->MPQuery: OID: 0x07030111 00000151 18:09:30.844 ==> QRQ_OID_TAPI_GET_DEV_CONFIG 00000153 18:09:30.844 <== QRQ_OID_TAPI_GET_DEV_CONFIG: 0x00000000 00000154 18:09:37.108 <== miniport->MPQuery: 0x00000000 00000155 18:09:37.108 ==> miniport->MPCheckForHang 00000156 18:09:37.108 miniport->MPCheckForHang: 0xc1bb1440 00000157 18:09:47.107 <== miniport->MPCheckForHang: 0 00000158 18:09:47.107 ==> miniport->MPCheckForHang 00000159 18:09:47.107 miniport->MPCheckForHang: 0xc1bb1440 00000160 18:09:57.105 <== miniport->MPCheckForHang: 0 (...) 3) OID_TAPI_GET_DEV_CONFIG wants from us DeviceConfig binary string. What should we return into this string ? How this configuration is defined ? What structure should we use (if any) ? (...) 00000173 18:10:15.543 ==> miniport->MPQuery 00000174 18:10:15.543 miniport->MPQuery: OID: 0x07030111 00000175 18:10:15.543 ==> QRQ_OID_TAPI_GET_DEV_CONFIG 00000177 18:10:15.543 <== QRQ_OID_TAPI_GET_DEV_CONFIG: 0x00000000 00000178 18:10:15.543 <== miniport->MPQuery: 0x00000000 00000179 18:10:15.543 ==> miniport->MPQuery 00000180 18:10:15.543 miniport->MPQuery: OID: 0x07030111 00000181 18:10:15.543 ==> QRQ_OID_TAPI_GET_DEV_CONFIG 00000183 18:10:15.543 <== QRQ_OID_TAPI_GET_DEV_CONFIG: 0x00000000 00000184 18:10:15.553 <== miniport->MPQuery: 0x00000000 00000185 18:10:15.553 ==> miniport->MPQuery 00000186 18:10:15.553 miniport->MPQuery: OID: 0x0703010c 00000187 18:10:15.553 ==> QRQ_OID_TAPI_GET_ADDRESS_STATUS 00000188 18:10:15.553 QRQ_OID_TAPI_GET_ADDRESS_STATUS: hdLine: 0xc1bb1440, ulAddressID: 0x00000000 00000189 18:10:15.553 QRQ_OID_TAPI_GET_ADDRESS_STATUS: ulTotalSize : 64 00000190 18:10:15.553 QRQ_OID_TAPI_GET_ADDRESS_STATUS: ulNeededSize: 64 00000192 18:10:15.553 <== QRQ_OID_TAPI_GET_ADDRESS_STATUS 00000193 18:10:15.553 <== miniport->MPQuery: 0x00000000 00000194 18:10:15.553 ==> miniport->MPQuery 00000195 18:10:15.553 miniport->MPQuery: OID: 0x0703010c 00000196 18:10:15.553 ==> QRQ_OID_TAPI_GET_ADDRESS_STATUS 00000197 18:10:15.553 QRQ_OID_TAPI_GET_ADDRESS_STATUS: hdLine: 0xc1bb1440, ulAddressID: 0x00000000 00000198 18:10:15.553 QRQ_OID_TAPI_GET_ADDRESS_STATUS: ulTotalSize : 64 00000199 18:10:15.553 QRQ_OID_TAPI_GET_ADDRESS_STATUS: ulNeededSize: 64 00000201 18:10:15.553 <== QRQ_OID_TAPI_GET_ADDRESS_STATUS 00000202 18:10:15.553 <== miniport->MPQuery: 0x00000000 00000203 18:10:15.553 ==> miniport->MPQuery 00000204 18:10:15.553 miniport->MPQuery: OID: 0x07030115 00000205 18:10:15.553 ==> QRQ_OID_TAPI_MAKE_CALL 00000206 18:10:15.553 QRQ_OID_TAPI_MAKE_CALL: htCall: 0x000002a0, hdCall: 0xc1bb1440 00000209 18:10:15.553 ==> miniport->Call 00000211 18:10:15.553 miniport->Call: DIALING (0x00000010) 00000212 18:10:15.553 miniport->Call: NdisMIndicateStatus(LINE_CALLSTATE): 0x00000010 00000213 18:10:15.553 <== miniport->Call 00000214 18:10:15.553 ==> pppoe->ConnectPPPoE (...) 4) When I try to connect from API, then OID_TAPI_MAKE_CALL is delivered to our driver. With this request we doing all necessary negotiations with PPPoE server and after receiving PPPoE session id we are calling: NdisMIndicateStatus(Adpt->AdapterHandle,NDIS_STATUS_WAN_LINE_UP,&mac,sizeof(mac)) and further NdisMIndicateStatus(Adpt->AdapterHandle,NDIS_STATUS_TAPI_INDICATION,&Event,sizeof(Event)) with LINE_CALLSTATE.Then API returns Error 645 and OID_TAPI_DROP is delivered to our driver. What is wrong ? Note that if we have called NdisMIndicateStatus(Adpt->AdapterHandle,NDIS_STATUS_TAPI_INDICATION,&Event,sizeof(Event)) with LINE_CALLSTATE two times, then connection is established, but WanSendHandler from miniport is never called. This is strange behaviour. Besides there are not connection counter in connection status API. (...) 00000249 18:10:15.553 <== pppoe->ConnectPPPoE:0 00000250 18:10:15.553 <== QRQ_OID_TAPI_MAKE_CALL 00000251 18:10:15.553 <== miniport->MPQuery: 0x00000000 00000252 18:10:15.553 ==> protocol->PTSendComplete 00000259 18:10:15.553 <== protocol->PTSendComplete 00000260 18:10:15.553 ==> protocol->PTReceive 00000269 18:10:15.553 <== protocol->PTReceive: 0x00000000 00000270 18:10:15.553 ==> protocol->PTReceiveComplete 00000322 18:10:15.553 <== protocol->PTReceiveComplete 00000323 18:10:15.553 ==> protocol->PTSendComplete 00000330 18:10:15.553 <== protocol->PTSendComplete 00000331 18:10:15.553 ==> miniport->MPQuery 00000332 18:10:15.553 miniport->MPQuery: OID: 0x0703010d 00000333 18:10:15.553 ==> QRQ_OID_TAPI_GET_CALL_ADDRESS_ID 00000334 18:10:15.553 QRQ_OID_TAPI_GET_CALL_ADDRESS_ID: ulRequestID: 0x00000000, hdCall: 0xc1bb1440 00000334 18:10:15.553 QRQ_OID_TAPI_GET_CALL_ADDRESS_ID: ulAddressID=0x00000000 00000335 18:10:15.553 <== QRQ_OID_TAPI_GET_CALL_ADDRESS_ID 00000336 18:10:15.553 <== miniport->MPQuery: 0x00000000 00000337 18:10:15.553 ==> protocol->PTReceive 00000346 18:10:15.553 <== protocol->PTReceive: 0x00000000 00000347 18:10:15.553 ==> protocol->PTReceiveComplete 00000369 18:10:15.553 ==> miniport->Line 00000371 18:10:15.553 miniport->Line: CONNECTED (0x00000004) 00000372 18:10:15.553 ==> miniport->Call 00000374 18:10:15.553 miniport->Call: CONNECTED 00000375 18:10:15.553 ==> miniport->WanUp 00000376 18:10:15.553 miniport->WanUp: HtCall: 0x000002a0, NdisLinkContext: 0x00000000 00000377 18:10:15.553 miniport->WanUp: NdisLinkContext: 0xc1bb3cf0 00000378 18:10:15.553 <== miniport->WanUp 00000379 18:10:15.553 miniport->Call: NdisMIndicateStatus(LINE_CALLSTATE): 0x00000100 00000380 18:10:15.553 <== miniport->Call 00000381 18:10:15.553 <== miniport->Line 00000387 18:10:15.553 <== protocol->PTReceiveComplete 00000388 18:10:15.553 ==> miniport->MPQuery 00000389 18:10:15.553 miniport->MPQuery: OID: 0x0703010e 00000390 18:10:15.553 ==> QRQ_OID_TAPI_GET_CALL_INFO 00000392 18:10:15.553 <== QRQ_OID_TAPI_GET_CALL_INFO 00000393 18:10:15.553 <== miniport->MPQuery: 0x00000000 00000394 18:10:15.553 ==> miniport->MPQuery 00000395 18:10:15.553 miniport->MPQuery: OID: 0x07030113 00000396 18:10:15.553 ==> QRQ_OID_TAPI_GET_ID 00000397 18:10:15.553 QRQ_OID_TAPI_GET_ID: Device class: ndis, ulSelect: 0x00000002 00000398 18:10:15.553 QRQ_OID_TAPI_GET_ID: hdCall: 0x00000000, hdLine: 0xc1bb1440 00000399 18:10:15.553 QRQ_OID_TAPI_GET_ID: ulAddressID: 0x00000000 00000401 18:10:15.553 QRQ_OID_TAPI_GET_ID: DeviceId=0x00000000 (UlDeviceID) 00000403 18:10:15.553 QRQ_OID_TAPI_GET_ID: Total size : 33 00000404 18:10:15.553 QRQ_OID_TAPI_GET_ID: Needed size: 33 00000406 18:10:15.553 QRQ_OID_TAPI_GET_ID: ulUsedSize : 33 00000407 18:10:15.553 <== QRQ_OID_TAPI_GET_ID 00000408 18:10:15.593 <== miniport->MPQuery: 0x00000000 00000409 18:10:15.593 ==> miniport->MPSet 00000410 18:10:15.593 miniport->MPSet: OID: 0x07030109 00000411 18:10:15.593 ==> SRQ_OID_TAPI_DROP 00000412 18:10:15.593 ==> miniport->Call 00000414 18:10:15.593 miniport->Call: DISCONNECTED 00000415 18:10:15.593 ==> miniport->WanDown 00000416 18:10:15.593 miniport->WanDown: NdisLinkContext: 0xc1bb3cf0 00000417 18:10:15.593 <== miniport->WanDown 00000418 18:10:15.593 miniport->Call: NdisMIndicateStatus(LINE_CALLSTATE): 0x00004000 00000419 18:10:15.593 <== miniport->Call 00000452 18:10:15.593 <== SRQ_OID_TAPI_DROP 00000453 18:10:15.593 <== miniport->MPSet: 0x00000000 (...) Several important routines: ====================== Miniport query and set routines: NDIS_STATUS QRQ_OID_TAPI_PROVIDER_INITIALIZE(MYBUF Buf) { NDIS_TAPI_PROVIDER_INITIALIZE *p; p=(NDIS_TAPI_PROVIDER_INITIALIZE*)Buf->Buffer; Adpt->UlDeviceIDBase=p->ulDeviceIDBase; Adpt->UlDeviceID=p->ulDeviceIDBase; p->ulNumLineDevs=1; p->ulProviderID=(ULONG)Adpt; return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_WAN_GET_INFO(MYBUF Buf) { NDIS_WAN_INFO *p; p=(NDIS_WAN_INFO*)Buf->Buffer; p->MaxFrameSize=1492-32; // I use MTU=1492 p->MaxTransmit=5; p->HeaderPadding=20; p->TailPadding=0; p->Endpoints=1; p->MemoryFlags=0; p->HighestAcceptableAddress=NDIS_PHYSICAL_ADDRESS_CONST(-1,-1); p->FramingBits=PPP_FRAMING|TAPI_PROVIDER; p->DesiredACCM=0; return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_TAPI_GET_DEV_CAPS(MYBUF Buf) { PLINE_DEV_CAPS c; PNDIS_TAPI_GET_DEV_CAPS p; CHAR ProviderInfo[]="PPPoE Device\0"; CHAR LineName[]="PPPoE Device\0"; p=(PNDIS_TAPI_GET_DEV_CAPS)Buf->Buffer; c=&(p->LineDevCaps); if(p->ulDeviceID!=Adpt->UlDeviceID) return NDIS_STATUS_TAPI_NODRIVER; c->ulPermanentLineID=1; c->ulUsedSize=sizeof(*c); c->ulNeededSize=sizeof(*c)+28; *Buf->BytesNeeded=sizeof(NDIS_TAPI_GET_DEV_CAPS)+28; if(c->ulNeededSize<=c->ulTotalSize) { c->ulUsedSize+=28; c->ulProviderInfoSize=14; c->ulProviderInfoOffset=sizeof(*c); c->ulLineNameSize=14; c->ulLineNameOffset=sizeof(*c)+14; NdisMoveMemory((PUCHAR)c+c->ulProviderInfoOffset,ProviderInfo,14); NdisMoveMemory((PUCHAR)c+c->ulLineNameOffset,LineName,14); } c->ulStringFormat=STRINGFORMAT_ASCII; c->ulAddressModes=LINEADDRESSMODE_ADDRESSID; c->ulNumAddresses=1; c->ulBearerModes=LINEBEARERMODE_DATA; c->ulMaxRate=Adpt->PtLinkSpeed; c->ulMediaModes=LINEMEDIAMODE_DIGITALDATA; c->ulDevCapFlags=LINEDEVCAPFLAGS_CLOSEDROP; c->ulMaxNumActiveCalls=1; c->ulAnswerMode=LINEANSWERMODE_DROP; c->ulRingModes=1; c->ulLineFeatures=LINEFEATURE_MAKECALL; // Adpt->LS: LINEDEVSTATE_OPEN|LINEDEVSTATE_CLOSE|LINEDEVSTATE_REINIT| // LINEDEVSTATE_CONNECTED|LINEDEVSTATE_DISCONNECTED|LINEDEVSTATE_INSERVICE; c->ulLineStates=Adpt->LS; return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_TAPI_OPEN(MYBUF Buf) { NDIS_TAPI_OPEN *p; p=(NDIS_TAPI_OPEN*)Buf->Buffer; if(p->ulDeviceID!=Adpt->UlDeviceID) return NDIS_STATUS_FAILURE; p->hdLine=(ULONG)Adpt; Adpt->HtLine=p->htLine; Line(LINEDEVSTATE_OPEN); Call(LINECALLSTATE_IDLE); return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_TAPI_GET_ID(MYBUF Buf) { NDIS_STATUS Status=NDIS_STATUS_SUCCESS; ULONG DeviceId; CHAR DeviceType[]="ISDN\0"; NDIS_TAPI_GET_ID *p; p=(NDIS_TAPI_GET_ID*)Buf->Buffer; if(_strnicmp((PCHAR)p+p->ulDeviceClassOffset,"ndis",p->ulDeviceClassSize)!=0 && _strnicmp((PCHAR)p+p->ulDeviceClassOffset,"tapi/line",p->ulDeviceClassSize)!=0) Status=NDIS_STATUS_TAPI_INVALDEVICECLASS; if(Status==NDIS_STATUS_SUCCESS) { if(p->ulSelect==LINECALLSELECT_CALL) { DeviceId=(ULONG)Adpt->NdisLinkContext; Status=NDIS_STATUS_SUCCESS; } else if(p->ulSelect==LINECALLSELECT_LINE || p->ulSelect==LINECALLSELECT_ADDRESS) { DeviceId=(ULONG)Adpt->UlDeviceID; Status=NDIS_STATUS_SUCCESS; } else Status=NDIS_STATUS_FAILURE; if(Status==NDIS_STATUS_SUCCESS) p->DeviceID.ulNeededSize=sizeof(VAR_STRING)+sizeof(DeviceId)+5; p->DeviceID.ulUsedSize=sizeof(VAR_STRING); if(p->DeviceID.ulTotalSize>=p->DeviceID.ulNeededSize || p->DeviceID.ulNeededSize-p->DeviceID.ulTotalSize>=sizeof(DeviceId)) { p->DeviceID.ulUsedSize=p->DeviceID.ulNeededSize; p->DeviceID.ulStringFormat=STRINGFORMAT_BINARY; p->DeviceID.ulStringSize=sizeof(DeviceId)+5; p->DeviceID.ulStringOffset=sizeof(VAR_STRING); NdisMoveMemory((PCHAR)&p->DeviceID+sizeof(VAR_STRING), (PCHAR)&DeviceId,sizeof(DeviceId)); NdisMoveMemory((PCHAR)&p->DeviceID+sizeof(VAR_STRING)+ sizeof(DeviceId),(PCHAR)DeviceType,5); } } return Status; } NDIS_STATUS QRQ_OID_TAPI_GET_LINE_DEV_STATUS(MYBUF Buf) { NDIS_TAPI_GET_LINE_DEV_STATUS *p; p=(NDIS_TAPI_GET_LINE_DEV_STATUS*)Buf->Buffer; p->LineDevStatus.ulNeededSize=sizeof(p->LineDevStatus); p->LineDevStatus.ulUsedSize=sizeof(p->LineDevStatus); if(p->LineDevStatus.ulTotalSize>=p->LineDevStatus.ulNeededSize) { p->LineDevStatus.ulNumOpens=1; p->LineDevStatus.ulDevStatusFlags=LINEDEVSTATUSFLAGS_CONNECTED|LINEDEVSTATUSFLAGS_INSERVICE; p->LineDevStatus.ulOpenMediaModes=LINEMEDIAMODE_DIGITALDATA; p->LineDevStatus.ulNumActiveCalls=Adpt->CurCS<=LINECALLSTATE_IDLE ? 0 : 1; p->LineDevStatus.ulLineFeatures=Adpt->CurCS<=LINECALLSTATE_IDLE ? LINEFEATURE_MAKECALL : 0; p->LineDevStatus.ulRingMode=1; } return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_TAPI_GET_ADDRESS_CAPS(MYBUF Buf) { NDIS_TAPI_GET_ADDRESS_CAPS *p; p=(NDIS_TAPI_GET_ADDRESS_CAPS*)Buf->Buffer; if(p->ulDeviceID!=Adpt->UlDeviceID) return NDIS_STATUS_TAPI_NODRIVER; if(p->ulAddressID!=0) return NDIS_STATUS_TAPI_INVALADDRESSID; p->LineAddressCaps.ulNeededSize=sizeof(NDIS_TAPI_GET_ADDRESS_CAPS); p->LineAddressCaps.ulUsedSize=sizeof(NDIS_TAPI_GET_ADDRESS_CAPS); *Buf->BytesNeeded=sizeof(NDIS_TAPI_GET_ADDRESS_CAPS); if(p->LineAddressCaps.ulNeededSize<=p->LineAddressCaps.ulTotalSize) { p->LineAddressCaps.ulAddressSharing=LINEADDRESSSHARING_PRIVATE; p->LineAddressCaps.ulCallInfoStates=LINECALLINFOSTATE_NUMOWNERINCR| LINECALLINFOSTATE_NUMOWNERDECR|LINECALLINFOSTATE_NUMMONITORS; // Adpt->CS: LINECALLSTATE_IDLE|LINECALLSTATE_CONNECTED|LINECALLSTATE_DISCONNECTED| // LINECALLSTATE_UNKNOWN|LINECALLSTATE_DIALING|LINECALLSTATE_BUSY; p->LineAddressCaps.ulCallStates=Adpt->CS; p->LineAddressCaps.ulDisconnectModes=LINEDISCONNECTMODE_NORMAL| LINEDISCONNECTMODE_REJECT|LINEDISCONNECTMODE_NOANSWER| LINEDISCONNECTMODE_INCOMPATIBLE|LINEDISCONNECTMODE_UNAVAIL; p->LineAddressCaps.ulMaxNumActiveCalls=1; p->LineAddressCaps.ulCallFeatures=LINECALLFEATURE_ANSWER|LINECALLFEATURE_DROP; } return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_TAPI_GET_ADDRESS_STATUS(MYBUF Buf) { NDIS_TAPI_GET_ADDRESS_STATUS *p; p=(NDIS_TAPI_GET_ADDRESS_STATUS*)Buf->Buffer; p->LineAddressStatus.ulNeededSize=sizeof(p->LineAddressStatus); p->LineAddressStatus.ulUsedSize=sizeof(p->LineAddressStatus); if(p->LineAddressStatus.ulNeededSize>=p->LineAddressStatus.ulTotalSize) { p->LineAddressStatus.ulNumInUse=Adpt->CurCS<=LINECALLSTATE_IDLE ? 0 : 1; p->LineAddressStatus.ulNumActiveCalls=Adpt->CurCS<=LINECALLSTATE_IDLE ? 0 : 1; p->LineAddressStatus.ulAddressFeatures=Adpt->CurCS<=LINECALLSTATE_IDLE ? LINEADDRFEATURE_MAKECALL : 0; } return NDIS_STATUS_SUCCESS; } NDIS_STATUS QRQ_OID_TAPI_MAKE_CALL(MYBUF Buf) { NDIS_TAPI_MAKE_CALL *p; NDIS_STATUS Status; p=(NDIS_TAPI_MAKE_CALL*)Buf->Buffer; p->hdCall=(ULONG)Adpt; Adpt->HtCall=p->htCall; Call(LINECALLSTATE_DIALING); // ... // Starting with PPPoE negotiations // .... return Status; } NDIS_STATUS QRQ_OID_TAPI_GET_CALL_INFO(MYBUF Buf) { NDIS_TAPI_GET_CALL_INFO *p; p=(NDIS_TAPI_GET_CALL_INFO*)Buf->Buffer; if(p->hdCall!=(ULONG)Adpt) return NDIS_STATUS_TAPI_INVALCALLHANDLE; p->LineCallInfo.ulNeededSize=sizeof(p->LineCallInfo); p->LineCallInfo.ulUsedSize=sizeof(p->LineCallInfo); p->LineCallInfo.ulBearerMode=LINEBEARERMODE_DATA; p->LineCallInfo.ulRate=Adpt->Speed/100; p->LineCallInfo.ulMediaMode=LINEMEDIAMODE_DIGITALDATA; p->LineCallInfo.ulCallStates=Adpt->CS; p->LineCallInfo.ulNumOwners=1; return NDIS_STATUS_SUCCESS; } Line indications: VOID Line(ULONG S) { NDIS_TAPI_EVENT Event; if(Adpt->CurLS==S) return; else Adpt->CurLS=S; NdisZeroMemory(&Event,sizeof(NDIS_TAPI_EVENT)); Event.ulMsg=LINE_LINEDEVSTATE; Event.ulParam1=S; Event.htCall=Adpt->HtCall; Event.htLine=Adpt->HtLine; NdisMIndicateStatus(Adpt->AdpterHandle,NDIS_STATUS_TAPI_INDICATION,&Event,sizeof(Event)); } Call indications: VOID Call(ULONG S,ULONG Param) { NDIS_TAPI_EVENT Event; NdisZeroMemory(&Event,sizeof(Event)); Event.ulMsg=LINE_CALLSTATE; Event.ulParam1=S; Event.htLine=Adpt->HtLine; Event.htCall=Adpt->HtCall; if(Adpt->CurCS==State) return; else Adpt->CurCS=S; if(S==LINECALLSTATE_CONNECTED) WanUp(); else if(S==LINECALLSTATE_DISCONNECTED) Event.ulParam2=LINEDISCONNECTMODE_NORMAL; else if(S==LINECALLSTATE_DIALING) Event.ulParam2=LINEDIALTONEMODE_NORMAL; NdisMIndicateStatus(Adpt->AdpterHandle,NDIS_STATUS_TAPI_INDICATION,&Event,sizeof(Event)); } WAN indications: VOID WanUp() { NDIS_MAC_LINE_UP mac; mac.NdisLinkHandle=Adpt; mac.NdisLinkContext=Adpt->NdisLinkContext; mac.ConnectionWrapperID=(NDIS_HANDLE)Adpt->HtCall; mac.Quality=NdisWanRaw; mac.SendWindow=5; mac.LinkSpeed=Adpt->Speed/100; NdisMIndicateStatus(Adpt->AdpterHandle,NDIS_STATUS_WAN_LINE_UP,&mac,sizeof(mac)); Adpt->NdisLinkContext=mac.NdisLinkContext; } VOID WanDown() { NDIS_MAC_LINE_DOWN mac; if(Adpt->NdisLinkContext) { mac.NdisLinkContext=Adpt->NdisLinkContext; NdisMIndicateStatus(Adpt->AdpterHandle,NDIS_STATUS_WAN_LINE_DOWN, &mac,sizeof(mac)); Adpt->NdisLinkContext=NULL; } } Thanks in advance Frank van Huet Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76623
 - 13
 - Cannot succeed with the Event sample Dear all, I am sorry to bother you again. I have installed the DDK on my E driver. And I have download the event source code from MS website. but the build got some problem. the buildchk_w2K_x86 is as following. Actually I don't have the event.rc file inside the sys directory. Could anyone tell me what error I have made? Do I need to add the "inc" directory of the WINDDK to my environment variable setting? p.s. BUILD: Examining e:\0227w\event\sys directory for files to compile. Compiling (NoSync) e:\0227w\event\sys directory ******************** 'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 386=1' cl -nologo -Ii386\ -I. -IE:\WINDDK\3790~1.183\inc\mfc42 -I.. -Iobjchk_w2K_x86\i386 -IE:\WINDDK\3790~1.183\inc\w2K -IE:\WINDDK\3790~1.183\inc\w2K -IE:\WINDDK\3790~1.183\inc\ddk\w2K -IE:\WINDDK\3790~1.183\inc\ddk\wdm\w2K -IE:\WINDDK\3790~1.183\inc\crt -D_X86_=1 -Di386=1 -DSTD_CALL -DCONDITION_HANDLING=1 -DNT_INST=0 -DWIN32=100 -D_NT1X_=100 -DWINNT=1 -D_WIN32_WINNT=0x0500 /DWINVER=0x0500 -D_WIN32_IE=0x0501 -DWIN32_LEAN_AND_MEAN=1 -DDEVL=1 -DDBG=1 -D__BUILDMACHINE__=WinDDK -DFPO=0 -DNDEBUG -D_DLL=1 /c /Zl /Zp8 /Gy /Gm- -cbstring /W3 /WX /Gz /GX- /GR- /GF /GS /G6 /Ze /Gi- /QIfdiv- /hotpatch -Z7 /Od /Oi /Oy- -FIE:\WINDDK\3790~1.183\inc\w2K\warning.h .\event.c .\pnp.c event.c pnp.c Generating Code... Stop. Linking e:\0227w\event\sys directory ******************** 'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST= 386=1' link -out:objchk_w2K_x86\i386\Event.sys -machine:ix86 @C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\nm2571.tmp Microsoft (R) Incremental Linker Version 7.10.4035 Copyright (C) Microsoft Corporation. All rights reserved. -MERGE:_PAGE=PAGE -MERGE:_TEXT=.text -SECTION:INIT,d -OPT:REF -OPT:ICF -IGNORE:4198,4010,4037,4039,4065,4070,4078,4087,4089,4221 -INCREMENTAL:NO -FULLBUILD /release -NODEFAULTLIB /WX -debug -debugtype:cv -version:5.0 -osversion:5.0 /functionpadmin:5 /pdbcompress -STACK:0x40000,0x1000 -driver -base:0x10000 -align:0x80 /stub:E:\WINDDK\3790~1.183\lib\w2K\stub512.com -subsystem:native,5.00 -entry:GsDriverEntry@8 -out:objchk_w2K_x86\i386\Event.sys objchk_w2K_x86\i386\event.obj objchk_w2K_x86\i386\pnp.obj E:\WINDDK\3790~1.183\lib\w2K\i386\BufferOverflowK.lib E:\WINDDK\3790~1.183\lib\w2K\i386\ntoskrnl.lib E:\WINDDK\3790~1.183\lib\w2K\i386\hal.lib E:\WINDDK\3790~1.183\lib\w2K\i386\wmilib.lib E:\WINDDK\3790~1.183\lib\w2K\i386\sehupd.lib echo Skip Binplace: Skip Binplace: Stop. Thanks! Jeff Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76621
 - 14
 - IoGetDeviceObjectPointer and zombie drive Hi, It seems that by calling this IoGetDeviceObjectPointer with different params causes zombie drives to appear. Zombie drives are drives that still appears when you call GetLogicalDrives() in user mode although it's been plugged out (usb for e.g.). The difference of params is DesiredAccess, which with value 0, zombie drives appear, but with FILE_READ_DATA, it seems to be working fine. The problem with feeding FILE_READ_DATA is that at times it will fail, with STATUS_SHARING_VIOLATION. I hope someone could shed some light on this. Could it be a bug of that call? thanks in advance. -- EWK Liew Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76620
 - 15
 - Bug in Windows Server 2003 SP1 classpnp!NewTransferPacket in Windows 2003 SP1 has the following new code added, which tries to preallocate a buffer of the maximum transfer size : // // Allocate a MDL. Add one page to the length to insure an extra page // entry is allocated if the buffer does not start on page boundaries. // newPkt->PartialMdl = IoAllocateMdl(NULL, fdoData->HwMaxXferLen + PAGE_SIZE, FALSE, FALSE, NULL); Now if we set STORAGE_ADAPTER_DESCRIPTOR.MaximumPhysicalPages/MaximumTransferLength to anything exceeding 64MB, indicating that we support unlimited transfers, in a response to IOCTL_STORAGE_QUERY_PROPERTY/StorageAdapterProperty, then fdoData->HwMaxXferLen becomes too big for IoAllocateMdl and the driver won't load. If I was asked to write similar code, I'd allocate say 64K and then reallocate the buffer increasing its size as needed. I remember posting the above already to this newsgroup, though can't recall any acknowledgement from Microsoft. Thanks! Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76617
 - 16
 - SetThreadAffinityMask and DispatchDeviceControl routine As per requirements, I need to read/write CPU MSRs for specified logical processor. Hence designed this way: - user mode thread would set affinity (using SetThreadAffinityMask) to run in specified logical processor - now user mode thread would issue an IOCTL to read/write CPU MSRs for this logical processor - my driver is Root enumerated and receives this IOCTL and processes and returns data synchronously. Environment: Win2k3 SP1 DDK, target OS: Win2k3 x86 & x64. Now my question is: Is it safe to assume that ALWAYS my driver's dispatch device control will run in SAME context as my user thread (since it is root enumerated driver and no drivers above/below it)???? If not, how else shall I handle this issue? -- ++Sathya Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76615
 - 17
 - Vista64 driver signing Apart from Class 3 CSP Certificate from Verisign what all has to be submitted to Microsoft for getting the PIC. where can i get the exact procedure for Vista 64 driver signing? Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76613
 - 18
 - Memory Leak Filter Drivers? Hi All, How can I effectively check memory leaks in Filter drivers? Any tools or methods to find out. Thanks Amazon Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76612
 - 19
 - Enumerating WAN Devices Bound to NDISWAN Hi! I've written an IM driver that enables ethernet and wan as its filter media types. Sure enough, the driver gets a single binding to \device\NdisWanIp and is able to get the NDIS_STATUS_WAN_LINE_UP and NDIS_STATUS_WAN_LINE_DOWN indications. However, on my test machine, I have two modems (1 PCI and 1 USB) along with a 1xEVDO NIC, so that means NDISWAN has three adapter bindings. So, can someone answer these questions: 1. Is there a way for the IM driver to get the friendly name of the underlying WAN adapters? 2. Is there a way for a service or application to get the friendly names without looking at the modem devices in the registry? In other words, is there an OID interface to NdisWan that allows for the query of the underlying WAN adapter? 3. When the IM driver gets the NDIS_STATUS_WAN_LINE_UP indication, is there a way for it to determine which WAN adapter is connected? If the driver can't determine this, is there a way for a service or application to determine this? Thanks! Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76604
 - 20
 - Mirror Driver not loading Hi - I built the mirror driver sample included in the Windows Server 2003 SP1 DDK using the Windows 2000 Checked Build Environment and installed it on my target machine, which has a Server 2000 OS (latest service packs installed). My debugger is a Server 2003 (SP1) machine, and the two machines are linked via null-modem cable. When the target machine starts up, I am able to see the debug messages printed from the miniport (mirror.sys), but none of the messages from mirror.dll. I confirmed (using the lm command in WinDbg) that mirror.dll was not one of the loaded modules. Does anybody know what could be causing this behavior on sample code taken straight from the Microsoft DDK cd? Thanks in advance for your help. Ronny Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76602
 - 21
 - Capturing fax # I am trying to figure out how to capture the fax #, etc at the beginning of a print-to-fax job like the Microsoft fax driver does. I have read the available docs and I think I have found a way to capture the information by implementing the DrvDocumentEvent method in a printer interface DLL but I have been completely unable to find a way to communicate this to the port monitor. Any suggestions would be appreciated. Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76592
 - 22
 - Mirror Driver Architecture I am building a mirror driver that needs to compress, encrypt and transmit bytes over a network. I believe it would be more efficient to do this from within the driver rather than requesting the user-mode application to perform these tasks every time there is a modification to the UI. My understanding is that these kernel to user-mode context switches are costly (as are the synchronizations on shared memory, etc.) - not to mention the additional headache of managing the shared memory in the driver - so I opted for doing everything in the driver. Before implementation, however, I would like to get advice/recommendations on the better approach to take. Thanks in advance for your replies Ronny Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76591
 - 23
 - Mouse driver GUI modification Hi all, I would like to create a custome version of a driver interface like mouse driver. It usually has few tabs with customization options. What would be needed to create a custom interface like this: 1. the whole driver would have to be created from scratch? or 2. driver core stays the same and then just the interface is recreated and recompiled? and 3. is there a mouse (like MS intellimouse driver) driver sample or code (that can be utilized) available or does it have to be reacreated from scratch? Ideally I would need some kind of overlay for the mouse driver that would use exactly the same functions as Intellimouse but with a updated interface (few graphical changes or touchups for easy access to orientation, mouse speed etc). Haw can this be accomplished in a simplest way? I'm not a programmer but would gladly use (hopefully ) some programmers assistance. What skills such programmer should have (and knowledge of): VB, VC++, DDK (just guessing). What to look for? I can create graphical side of it, need someone with expertise to put this together. Any advice highly appreciated. Paul Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76581
 - 24
 - D3D display driver and AMD64 Where can I get the headers/libraries to build a 64-bit AMD64 display driver that supports Direct3D? Using the latest and greatest DDK gives lots of errors and warnings. -Brian Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76580
 - 25
 - Filter Manager Redistributable Hi, I've developed a minifilter driver for a commercial product and would like to redistribute the Filter Manager for Windows 2000 clients that do not have URP1 installed. Is this possible to get? Also, what are the OS versions and SP levels that include the Filter Manger? -- Thanks, Brian Tag: Windows Server 2003 - Removing Reliance On USB/HID Tag: 76579

I have just recovered a Win2K3 install from an IBM XSeries onto an HP
Proliant ML370 G3.

Although the XSeries uses PS/2 keyboard/mouse I cannot log into the Proliant
unless I use USB devices.

This is not usually a problem, but I have 6 of these servers and only 1 USB
keyboard/mouse.

I could go out and purchase extra kit but I would like to try removing the
reliance on USD/HID.

Any ideas?

D.

Top