IOCTL level information on SMB.sys for Windows 2003...

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
    - SysHook and STATUS_ACCESS_VIOLATION Hi, Recently I've attempt to write a driver in order to hook any registry access using the KeServiceDescriptorTable and then subst the table entry with my function. If I use the this code only for logging (ie. RegMon) it's all ok, but if I try to modify the parameter all the Zwxx function give me a STATUS_ACCESS_VIOLATION: for example: - if the key that the application want to open is \Registry\Machine\Software\Test I create (ExAllocatePool) a new POBJECT_ATTRIBUTES and relative PUNICODE_STRING - then I call the RealZwOpenKey (the real KeServiceDescriptorTable's function) but If I do so the function give me the error. But, If I dehook the ZwOpenKey and the I call ZwOpenKey the Fn is Ok. But dehooking this Fn isn't good (some access could be lost). It seems that the real ZwOpenKey's code can't or don't want access the memory allocated by the driver... thank's Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65602
  - 2
    - Reading psoSrc data in DrvCopyBits provides not correct results Hi, I have a problem to read an image from the source "psoSrc" in function DrvCopyBits. The image has alwas a black line at the right and bottom. Please tell me how I should read it to receive the correct data. Thanks for help. AF Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65600
  - 3
    - Requirements for including Driver on Longhorn CD? Hi, What is the requirements or process of including our XP signed driver in Longhorn CD (including BETA)?. We got a MS signed and WHQL qualified driver for XP. We would like our driver to include in Longhorn CD. Is there anyone that we can contact to? Regards Maung Bandu Brainboxes Ltd. Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65597
  - 4
    - Extract custom PPD-features in print processor. Hi. I have to write a print processor that extracts custom features added to the PPD-file of a PS printer. To my understanding, the features are saved in the private area of DEVMODE, but I can't find them. When I use WinPrint and RAW, the features are included in the output, so I know it's possible. /Erik Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65595
  - 5
    - 64-bit driver compile error hello everyone: I tried to compile my driver codes in 64-bit computer with windows2003 SP1 DDK. Got error code: NMAKE " fatel error U1073: don't know how to make 'objchk_wnet_AMD64\unicode.obj What's the possible error? In fact there is no unicode.c file in my source file. thanx your attention ! Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65592
  - 6
    - How can I get the NDIS driver? I have to do the project about Indoor Wireless Positioning System. I implement with JAVA ...so how can i get NDIS pls help me.. .I just started for a few time Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65589
  - 7
    - Neophyte question on SMP & mutexes Hi, Do mutexes protect against concurrent access from another CPU? I have a worker thread which acquires a mutex before a critical section and then releases it. If, on an SMP machine, another instance of this thread executes, would it also be serialized by the same mutex? Also, generally speaking, when is it better to use spinlocks? My driver uses mutexes only. Regards, James Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65583
  - 8
    - WinDbg Variable checking Is there like a magic trick to see the content of my variables all I see is the parameters. I can't even see my locals ??? Denis Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65568
  - 9
    - Filter Driver Install How do I specify on my INF installation file that a particular filter driver needs to run as LowerFilters to the PCI Bus? Hendrix Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65562
  - 10
    - Scannig issue of new SCSI devices Hello, I am writing a user application program to scan hundreds of SCSI drives been connected and/or removed. I use IOCTL_SCSI_RESCAN_BUS to force scan (suppose to invalidate the device list in SCSIPort driver) and then IOCTL_SCSI_GET_INQUIRY_DATA to get the new list. However I get the stale data (i.e the device list prior to the drives been connected and/or removed). After I call IOCTL_SCSI_RESCAN_BUS and IOCTL_SCSI_GET_INQUIRY_DATA several loops (each time the number of loops changes), IOCTL_SCSI_GET_INQUIRY_DATA returns the correct list of drives. Using the SCSI Analyzer it has been confirmed that IOCTL_SCSI_RESCAN_BUS send REPORT_LUNS, then several INQUIRY command (the correct data is returned for all the new drives connected). Is there any way to prevent getting the stale device list? Is there a way to force clear the stale device list in the scsiport driver?. This is a major issue for the application program as it does not know the number of loops it has to issue the IOCTLs to get all the new device list. Regards Raj Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65561
  - 11
    - USBD_STATUS not in header Hello, A status code that is returned in the Isopacket[].Status field of the _URB_ISOCH_TRANSFER struct does not seem to be in the USBD status code enum. The value is 0xC000000E. What does this code means in the context of an isochronous USB OUT and IN transfer? Can someone relate this code to the TD status field that is called out in the OHCI specification? I am testing on an AMD system using WindowsXP SP2. Thanks for your time, John Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65560
  - 12
    - 1394 Host Controller Node Number Hi All, I need to inform my 1394 devices of the firewire node number of the host controller board. Can the node number of the host controller be determined programatically? Thanks, Scott Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65559
  - 13
    - USB enumeration time in a production test environment I seem to recall a discussion thread regarding speeding up recognition/enumeration of new devices. The problem that needs to be solved is that it's taking from 7 to 20 seconds for a new device to become available for communication after power on connection. The folks at our production facility want this to happen more quickly. The port that we will be using can be dedicated to this function. The device VID, PID, and Version will be constant but the USB serial number will probably be changing. My inital reaction is that the amount of time needed for enumeration is determined by how much work the PnP manager has to do to figure out the correct driver. As I mentioned, I seem to remember a similar issue that was on the list, but a search of current articles doesn't seem to turn anything up. Does anyone remember this one? Sam Robinson Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65556
  - 14
    - AVStream: DispatchShutdown handler Hi, all! I have to add IRP_MJ_SHUTDOWN handler for AVStream miniport driver. How should I prevent device from being removed? Does ks.sys support some kind of remove lock. If so, how can I acquire it? WBR Igor Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65554
  - 15
    - Checked build Assert in EngLoadImage Hi All, I get this when I load a dll from my display driver in Win2k3 Checked build: *** Assertion failed: Section->Segment->u1.ImageCommitment != 0 *** Source File: d:\srvrtm\base\ntos\mm\sessload.c, line 239 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? The warning seems inert, and it all works if I ignore it. But still it worries me. Any ideas what might be causing this? I guess it must be some sort of problem with the dll image. Thanks, Otto Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65553
  - 16
    - 1394 Raw Mode Addressing And Driver Verifier Hello All... I've been using 1394 raw mode addressing successfully but when I run the driver verfier I get a bug check when accessing the port driver to perform a raw mode io request. My guess this is because I'm using an address that wasn't obtained by using IoGetDeviceObjectPointer( ). I retrieve the port driver address by accessing the bus driver's PortDeviceObject element. As follows.... // Get the port driver object. This is the next to the lowest layer in the driver stack. // The port driver is used to send messages to a node other than the node // for which the lower driver object exists. pDeviceExtension->pPortDeviceObject = ((PNODE_DEVICE_EXTENSION)pDeviceExtension->pStackDeviceObject-> DeviceExtension)->PortDeviceObject; However, I don't know what the symbolic link is for the 1394 port driver. (driver file ohci1394.sys.) The symbolic link for the bus driver is known as \\device\1394BUS0. Does anyone know the symbolic link for the 1394 Port Driver? I need this since it's required as the first parameter in IoGetDeviceObjectPointer( ). Thanks, Scott Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65549
  - 17
    - lower the priority of a process when doing Kernel-mode debugging Hi, I need to lower the priority of a process when doing Kernel-mode debugging through a Null Modem cable. For example, I edited the base priority at offset 0x62 of the EPROCESS structure but it does not seem to work. -- Thanks, Daniel Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65544
  - 18
    - HOw to query different profiles supported by a bluetooth device Hi, Could anyone explain, how to query different profiles supported by a bluetooth device or all available devices found during scan. Thanks, Arsalan Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65539
  - 19
    - STL classes I've noticed that if I include <string> in my printer interface DLL, Windows 2000 won't let me install the driver. If I change it to use regular character pointers, it's fine. Has this happened to anyone else? -- Matt Kane m k b a t d i r t y d o t o r g Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65527
  - 20
    - Ways to anlayze crash dump files When I get a BSOD, I use Visual SOFTICE and a Kernel memory dump to try and trace the error. If one of my driver's function is in the stack trace, I can goto its source and try to find the error. My problem starts when I don't see my driver in the stack trace, and even when I disassemble "Parameter 4: Address of instruction executing" I can't see any of my driver's function. Any way I can get more informant from the dump? Does WinDbg can be more helpful in analyzing dump files ? Any way to know if the win32 user mode app caused the crash? (Then I need to use a complete memory dump?) Any other tips on debugging BSODs? Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65526
  - 21
    - PDB file path in driver binary By default if i build my driver, the path of the pdb file is seen in the driver binary even in the free build. i don't want the path to be seen in the driver binary. how to remove it. any comile time flags? Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65520
  - 22
    - Test Question 11 Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65511
  - 23
    - NdisAllocatePacketPoolEx & NULL pool handle NdisAllocateBufferPool can return a NULL pool handle which is valid. is same true with NdisAllocatePacketPoolEx ? Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65510
  - 24
    - Visual Studio 5.0 compatibility Hi, I need Visual Studio 5.0 to build my driver code. Am not able to get it I have 6.0 version. Can anyone tell me how to make 6.0 to be compatible for 5.0? What settings has to be changed? Thanks & Regards Gayathri Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65503
  - 25
    - Microsoft - Need urgent help - Product rollout stopped Hello, Sorry for posting this again but I'm in a crunch to resolve this issue ASAP. We are developing a 3.3 V only PC Card which work with my driver under Windows 2000 and Xp but Windows 98SE is showing an error code of 7. My driver entry routine is called but not my initialize routine. Does Windows 98SE support 3.3V only PC Card? I've noticed that Microsoft recommends that PC Card be implemented as dual voltage (3.3V/5V). Please reply ASAP since our product rollout is on hold until this issue is resolve. Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65495
- Next
  - 1
    - Newbie! Creating correct inf file Hi, before asking my question I should say that I'm absolutely new to driver programming and worse I don't even have the DDK documentation. However, I have some years experience with Windows development and now want to create a MIDI driver thats sole purpose is to route MIDI messages to my custom application. I have already found the documentation for Installable Drivers in the Win SDK and some code in newsgroups. The code is written for Win 3.11 but I was able to rewrite and compile it under Windows XP. I'm also able to load the driver with the OpenDriver() API. My question: I want other applications let select the driver for their MIDI output device. For this, I assume, I must install the driver. The old Win 3.11 code example comes with an inf file that looks something like this: [disks] 1=. ,"My MIDI driver",disk1 [Installable.Drivers] MyMidiDrv=1:d:\bcb5\music\installableDrivers\MidiDriver1\MyMidiDrv.dll,"MIDI","MIDI",,, However, trying to install this always gives me the error "Installation failed". What could be the cause? Is this inf file at all valid under Win32? I really appreciate any comment/idea!! thanks, Nick Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65493
  - 2
    - Does the WinDbg in source mode Does someone has successfully debug with source and break point and all with the WinDbg? I put a break point in my source code... (set the source path and all) When my driver loads it always tell me that it cannot locate the breakpoint??? Thanks Denis Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65486
  - 3
    - out of the device driver newsgroup Guys, I am pausing out of the driver newsgroup for a month or two. I am reachable for any printer driver,port monitor, language monitor, print processor,spooler or any printing related queries at my email vprnt at lycos dot com Thanks Vipin Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65478
  - 4
    - printer driver halftoning I have been given the task of adding enhanced halftoning capability to an existing printer driver. The driver sends its output to a thermal transfer barcode printer. This is monochrome device (hence the need for halftoning). I have tried changing the halftoning parameters, such as the GDIINFO HTPatternSize, but this does not seem to affect the output. Ultimately, I am look for a way to let the use choose from any of the HT_PATSIZE_* values and have the driver use these when rendering color images. I just can't seem to get all of the settings lined up just right between the GDIINFO, DEVINFO, DEVHTINFO. I have implemented DrvStretchBlt and I am calling EngStretchBlt with iMode set to HALFTONE. None of this seems to help. Any pointers or suggestions would be welcome. Neal Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65477
  - 5
    - Mirror Driver - Capturing GDI Call information Hi everyone, For a remote desktop type application, I am trying to see if it is feasible to actually grab GDI call information with a mirror driver and send that to the client where it would be drawn. This would result in much less data being transferred over the network over the usual approach of sending pre-drawn JPEG rectangles for changed parts of the screen, I would think. Can anyone point me to some information on how to do this? How would I use this data on the client to redraw the display since it will be coming from kernel-mode on the server? The DDK mirror sample doesn't have enough comments for me to figure this out. Thanks! Aruk Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65476
  - 6
    - is device interface path (DevicePath) persistent ? Is device interface path [ i.e. the DevicePath parameter of the SetupDiOpenDeviceInterface function or DevicePath member of the SP_DEVICE_INTERFACE_DETAIL_DATA structure ] persistent 1) between reboots? I.e. will sequential SetupDi*-style enumerations made in the same Windows session give the same DevicePath for the same device interface? 2) over reboots? i.e. will enumerations before and after reboot give the same DevicePath for the same device interface ? Many thanks! Igor. Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65474
  - 7
    - drive letter from DevicePath / Device handle Should be an easy question I guess ... Suppose, I used SetupDi* functions to get the DevicePath for the device, say CD-ROM drive, and then opened the handle for the device passing this DevicePath to CreateFile. So far, so good. Now, what is the best/recommended way to resolve the drive letter (if any) associated with this device [e.g. E:, F: etc] ? Many thanks! Igor. Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65472
  - 8
    - High Volume Queueing in NDIS MiniportSendPackets I have a deserialized intermediate driver that accepts packets in MiniportSendPackets, queues them, schedules a work item to do some processing on them that has to happen at PASSIVE_LEVEL, and sets their status to NDIS_STATUS_PENDING. The work item completes the packets once it is finished processing. This all works fine in low volume situations, but when I subject my driver to one of the NDIS Test stress tests, I notice the following: - MiniportSendPackets keeps getting called at DISPATCH_LEVEL and queueing the packets; - My work items never get a chance to run and complete the packets; and, - Eventually I run out of buffer descriptors and I have to start setting NDIS_STATUS_FAILURE on the packets in MiniportSendPackets. I don't think there's a way to pause the execution of MiniportSendPackets because it's getting called at DISPATCH_LEVEL. My question is: how can I follow all the rules for MiniportSendPackets in this situation and still give my work items a chance to complete the packets in a high volume situation? Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65471
  - 9
    - NDIS driver Hello: My application involves streaming audio, video, and control data from nodes with embedded ethernet capabilities. Each node will have a video camera and microphone as inputs, and speakers and a video screen as outputs. Each node can transmit audio/video/control data to any other node on the network. The windows PC will be able to stream data to any node, and will be able to receive data streamed from any node. The PC will also be able to monitor and save data being streamed directly from 1 node to another. The nodes will have ethernet PHY/MAC front ends connected to a microcontroller or FPGA to send and receive data, but no high-level capabilities (ie no TCP/IP stack). My question is what sort of network driver I need to write (Windows XP). Is an intermediate NDIS driver the correct choice? Is there a way to simplify the architecture by improving the capabilities of the remote nodes - ie package audio/video/control data as some "standard" format recognized by Windows resulting in simplification or elimination of need for custom device driver? If nodes have full TCP/IP stacks, does this simplify anything? If nodes are just "dumb" MAC addresses that source or sink data without knowledge of any windows high level protocols, does this force the creation of custom network driver? Any suggestions are welcome. Thanks, Doug Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65461
  - 10
    - About SMB client driver ... I am using Microsoft Windows 2003 on a Tyan motherboard which has the Intel ICH5R (7520 chipset). This chipset has an embedded I2C controller and my application needs to do some I2C based device communication, i.e. thermal, drive detection, etc. These are normal I2C communication that I can get done in Linux very well. With Windows I know that some SMB client driver is needed. I can't figure out if there are any SMB client drivers available from Microsoft for Windows 2003 (at some point it will be SAK solution). If there is a driver already available then how do I talk to the driver (i.e. are there documented IOCTL that I can use?). If such a driver is not available then how easy it is to write one? Even if I write one the SMB client driver of mine needs to talk to the SMB class driver but I do not know or did not find any document that explains this. Can somebody please provide me some information on how to get this working. Sincerely appreciate your feedback and help on this one. Regards SG -- SG, Device Driver writer Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65458
  - 11
    - Help in analyzing crash dump files When I get a BSOD, I use Visual SOFTICE and a Kernel memory dump to try and trace the error. If one of my driver's function is in the stack trace, I can goto its source and try to find the error. My problem starts when I don't see my driver in the stack trace, and even when I disassemble "Parameter 4: Address of instruction executing" I can't see any of my driver's function. Any way I can get more informant from the dump? Does WinDbg can be more helpful in analyzing dump files ? Any way to know if the win32 user mode app caused the crash? (Then I need to use a complete memory dump?) Any other tips on debugging BSODs? Thanks Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65456
  - 12
    - Override excel's printing dpi setting This question has been asked before, but not answered. So here goes again: I need to programmatically print excel documents based on the printer's settings (essentially the dpi). However, for excel documents, they have their own print settings in Page Setup. When printing programmatically, these settings override the printer's default settings. Any ways to change the document's settings, or to override these settings to use the printer's, or even to intercept the print job to change them? Thanks! Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65453
  - 13
    - DPC/ISR synchronization (windows ce) I haven't had a lot of response in the platform builder newsgroups, so I'll try here. In Windows CE 4.1, I had no problem with a NDIS ISR (miniportISR) interrupting the DPC(MiniportHandleInterrupt). In upgrading to Windows CE 5.0, I'm seeing that the ISR is getting held off by the DPC. I've tried serialized/deserialized. I've verified that the interrupt is not disabled in the kernel and can see with independent means that kernel is seeing the interrupt and setting the interrupt event in time with the hardware, but the ISR waits until the DPC finishes until it is run. Does anyone have visibility into what has changed between the CE 4.x and 5.x NDIS implementation ? The driver registers as an NDIS 5.0 miniport. Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65444
  - 14
    - HID mouse filter (aka firefly) question Greetings, I have a question about the DDK firefly example. It's supposed to show how to implement a filter driver for a MS optical mouse device. My question is, how are HID mouse events actually intercepted, identified, and filtered relative to the firefly example? I'm kinda new at device driver programming, but I already understand (to some extent) the other filter drivers (moufiltr and kbfiltr) in the DDK, to the point that I've successfully modified, rebuilt, and loaded those. Now I want to do the same with the firefly example (really for all HID mice and keyboards), but there don't seem to be enough clues in the example. Can somebody help me connect the missing dots? Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65443
  - 15
    - Kernal or application thread - Help Hi Guys I have a windows application and device driver using a piece of data acquisition hardware. When the data has been acquired I use the device driver to read back the data. Its read back byte by byte and there is a lot to read back. At the moment I don't have any threads operating so when the device driver is reading back the data the User interface is locked out. So what I'm going to do is create a thread that operates in the background always waiting for the data ready signal and then reading the data back when its available. It would have lower priority than the User Interface thread and so should not effect its operation. My question is this. Should I create a thread in the kernel i.e. created by the device driver, Or should I create a thread at the application level which owns the device driver(i.e. opens it communicates with it etc.)? Creating a thread in the device driver is easier for me given the current software architecture. If I change, to create a new application level thread then all existing communication between the User Interface thread and the device driver would have to be modified to go to, and then through the new thread. So Ideally I want to create a new thread in the Kernel. But will it operate at a lower priority than the User Interface thread and therefor allow it priority. All help appreciated. Denis ____________________ Centron System Solutions http://www.CentronSolutions.com Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65440
  - 16
    - Use GetPrinterData to GetPrinterDataFromPort to get printer status Trying to write a language monitor for a printer to retrieve printer status, but having some trouble connecting the dots. There does not seem to be much info on this subject. Through reading other threads and info on the MSDN site I understand that the API GetPrinterData retrieves printer config data from the registry, but if the data is not in the registry it will call GetPrinterDataFromPort in the language monitor, which will communicate with the printer with WriteCommand and read back the results in the UstatusThread with ReadCommand. I can retreive an existing registry key with GetPrinterData successfully, but a non-existing key will return 0 bytes needed and does not seem to call the language monitors PJLMonGetPrinterDataFromPort. I have a debug statement with OutputDebugString here that never gets called. What do I need to do in order for an application to retrieve printer status directly from the printer? Is this the preferred method? Do I have to make use of SetPrinterData to store the result or trigger the call to GetPrinterData to make the call the the language monitor? If there is a more appropriate thread for this question, please let me know. Assistance with this would be much appreciated. Thankyou Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65437
  - 17
    - Ke386CallBios() I've got a situation where I'm being told to make an Int15 bios call from a driver. I know it's no longer supported, highly discouraged etc, but I'm still being pushed into it. Based on some newsgroup posts, it looks like Ke386CallBios() is what I need. However, I don't have any idea on how to call it (obviously no documentation for an undocumented function). Any suggestions? -- Dean Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65433
  - 18
    - Creating Browser Info in Server 2003.SP1 DDK In my sources file, I have the following: BROWSER_INFO=1 BROWSERFILE=$(TARGETNAME).bsc -n This works great when I build using the Server 2003 DDK. However, it doesn't generate a browser file if I build using the Server 2003 SP1 DDK. What happened? Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65426
  - 19
    - Install a filter driver automatcally Hi everyone, DDK sample Firefly shows how to install a mouse filter driver on a USB mouse, but it requires manual installation. A user has to find out his/her mouse device object (sometimes appears as HID compliant mouse) in Device Manager and take the "Update Driver" route to install it. Is it possible to install such a filter driver between mouhid.sys and mouclass.sys (so it filters all USB mice but not other PS/2, serial, i.e., not a classwide filter) aautomatically with a SETUP.exe or the similar? Is there any example to create SETUP.exe for automatic installation? Thanks in advance, Liang Fu Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65425
  - 20
    - Win98 calls to lower driver from upper driver We have developed a Windows 98 upper and lower driver to perform read and write operations to the disk. How do we make these both drivers communicate with each other. Thanks in advance!! Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65422
  - 21
    - How to use a PTRDIFF to get the value it offsets to I am trying to get the family name of a font which is accessed by a PTRDIFF which holds the offset to its memory location. I have tried to add the offset to the memory location of the variable and it is pointing me to garbage. What is the procedure to get the family name of a font from the PIFIMETRICS? Thanks Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65421
  - 22
    - Bluetooth programming compilation problems Hi all, I am trying to develop an application which try to discover different devices present and the services exposed by them over bluetooth. I am using WSALookupServiceBegin(), WSALookupServiceEnd() and WSALookupServiceNext() functions. When I try to query services then i get some BLOB data in pwsaResults->lpBlob->pBlobData. I dont know how to get information from this. Although I try to use interfaces like ISdpRecord, ISdpStream but when I include bthapi.h nothing happens and I get the errors that the following interfaces are not defined. Then I included bthapi.idl but I am getting following errors: C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Include\bthapi.idl(13) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 1>C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Include\bthapi.idl(13) : error C2440: 'initializing' : cannot convert from 'const char [3]' to 'int' 1> There is no context in which this conversion is possible 1>C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Include\bthapi.idl(13) : error C2146: syntax error : missing ';' before identifier 'cpp_quote' 1>C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Include\bthapi.idl(14) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 1>C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Include\bthapi.idl(14) : error C2374: 'cpp_quote' : redefinition; multiple initialization 1> C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\PocketPC2003\Include\bthapi.idl(12) : see declaration of 'cpp_quote' Could anyone please help me out here. Thanks, Arsalan Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65416
  - 23
    - NDIS and broadcast Hi all, I would like to ask you for an answer on following question. If I send a broadcast frame from my NDIS IM, will it be delivered to all stations on segment including source station, or not? I have a reason to think that it is so ... when I send broadcast frame, it is a bit later indicated in my PtReceive. It seems little strange to me but ... Another questions are: Is it normal behaviour? Is it possible to somehow switch it off? thanks for patient Michal Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65410
  - 24
    - Network mechanism in windows Hi all, I have following problem. Using NDIS IM, I have discovered that after plugging cable into NIC card (e.g. associated with ip 192.168.10.1), windows send throught it ARP request (filled with Sender IP = 192.168.10.1 and Target IP = 192.168.10.1), which is then indicated as received (again in my NDIS IM). It occures even if translation for the IP is included in ARP table, so I suppose that this is done as some kind of testing accessibility of network. Questions are: 1) is that description correct ? 2) why does it happen? thanks for answers Michal Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65400
  - 25
    - PAE question about memory access Hello, I have some questions related to the use of PAE for access to memory beyond 4G in 32-bit Windows drivers. I'm trying to understand how a PCI device which supports dual address cycles works in conjunction with a device driver running on a system with PAE enabled. As I understand it any memory that the system provides can be either above or below the 4G mark. If a driver calls IoGetDmaAdapter with Dma32BitAddresses set to TRUE (and Dma64bitAddresses set to FALSE), does this mean that when AllocateCommonBuffer is called that it will only give memory which is physically below 4G? Or does it mean that the memory can be anywhere, but the "logical" address it returns will always be a 32-bit quantity? Or is there some other interpretation? In my case, the device only wants to receive 32-bit host memory addresses to access, but we do want the device to be able take advantage of the upper memory, if possible. Also, if for some reason we did want to restrict the memory for this device to the lower 4G of memory, is there a way to specify it? We might want to support some device types which can support DAC and some which do not in the same driver at the same time. Thanks, Nathan Tag: IOCTL level information on SMB.sys for Windows 2003... Tag: 65387

Hi,
I was wondering if anybody would have any information on the IOCTL data
to talk to the SMB.sys driver in Windows 2003. The SMB.sys driver comes from
Intel and I am having a big difficulty in getting any information from Intel
as nobody responds and all I get is redirection at Intel.
Any information would be deeply appreciated. All I am trying to do is
send some I2C commands that the SMB.sys can fulfill for my application via
the SMBclass.sys and SMBhc.sys drivers. Please send me a note at
ganguly2004@hotmail.com

Thanks
SG

--
SG, Device Driver writer

RE: IOCTL level information on SMB.sys for Windows 2003... by pavel_a

pavel_a
Sun Jul 03 13:12:01 CDT 2005

"SG" wrote:
> Hi,
> I was wondering if anybody would have any information on the IOCTL data
> to talk to the SMB.sys driver in Windows 2003. The SMB.sys driver comes from
> Intel and I am having a big difficulty in getting any information from Intel
> as nobody responds and all I get is redirection at Intel.
> Any information would be deeply appreciated. All I am trying to do is
> send some I2C commands that the SMB.sys can fulfill for my application via
> the SMBclass.sys and SMBhc.sys drivers. Please send me a note at
> ganguly2004@hotmail.com
>
> Thanks
> SG
>
> --
> SG, Device Driver writer

Do you need information about internals of the Intel smbus driver,
or general information how you can send data to smbus ?
For the latter case, the DDK documentation has enough details... or doesn't
it?

Regards,
--PA

RE: IOCTL level information on SMB.sys for Windows 2003... by pavel_a

pavel_a
Sun Jul 03 13:29:01 CDT 2005

"Pavel A." wrote:
> Do you need information about internals of the Intel smbus driver,
> or general information how you can send data to smbus ?
> For the latter case, the DDK documentation has enough details... or doesn't it?

Have you seen it n the DDK docum? -

DDK > Device technologies > System support for buses > SMB
> Design guide > Sending a SMB request

Regards,
--PA