Webcam "Hazy" effect on USB1.1 mode

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
    - Suppress command window wile using IExpress wizard Hi all, I'm using IExpress wizard to create a self extracting driver package. I use a command-line script to create some directories in the extraction path and copy some files into them. I'm using DPInst to install the driver files onto Vista systems. My questions are; 1. How I can suppress or at least minimize the ugly command window that pops up when the command-line script runs? 2. Some of the buttons on the DPInst screens seem to be redundant... such as the Finish and Cancel buttons on the finish page seem to do the same thing. How can I get rid of the redundant buttons on the DPInst screens? Thanks in advance, Shaji. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83196
  - 2
    - Interfacing to Com port driver I am attempting to interface to a piece of equipment which provides serial port emulation via its driver for USB. When it is plugged into different USB ports, it appears at different com port addresses - i.e. COM8: or COM12: (on my machine). I have two specific quistions: 1) How do I open a COM port greater than COM9:? When I try to use the recommended procedure (open as a file), it fails if the COM port number is greater than 9. 2) How do I find which COM port number the device is connected to? It manifests as a modem, and has a specific device name which I can see in Hardware Manager. If I examine the advanced port properties, I can see which COM port number it has assigned. I need to find the device by name (or see if it's not there). How do I do this? I am using Visual Studio 2005 and writing in ANSI C. Thanks, -- Al Jewer Alcomp, Inc Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83187
  - 3
    - Windows Vista Printer Driver and Printer Name Hello all, I've developed a user mode printer driver. Until Windows Vista it never had any problem. In Vista, when installing from remote server, the printer name that gets into DrvPrinterEvent, with PRINTER_EVENT_INITIALIZE, it's something like this "\\CSR|ServerName\{94718C2F-E998-90E2-2CA0E49A1C12}. What does this printer name means? I've also noticed that there are additional registry keys under "HKLM\Software\Microsoft\Windows NT\Print\Providers\Client Side Rendering Print Provider\Servers\ServerName\Printers\{94718C2F-E998-90E2-2CA0E49A1C12}" What Keys are these ones?? The driver uses my own Language Monitor, which will write specific data under PrinterDriverData, normally it was written under HKLM\System\CurrentControlSet\Print...." but now where should it be written? Strange it's the name that get's into DrvPrinterEvent! it should be something like \\ServerName\\Printer Name" !! And PRINTER_EVENT_INITIALIZE gets called like 6 times in a row, and when I try to print nothing happens. No StartDoc, no closeport, nothing!!! It worked ok two times, and at this time I've noticed that local registry settings were the same as in Server registry. Help me please!! Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83181
  - 4
    - IRP_MJ_SCSI Hi All, I need to write a bus driver for a customer storage controller chip. I cannot use the SCSIPORT model as the enumeration of the devices is very specific and I feel writing a bus driver will provide me the most flexibility to do this. I am trying to decide between using the WDM and KMDF framework for writing this driver. From KMDF documentation I could not figure out what the framework entry point will be for IRP_MJ_SCSI. Is it possible to do this storage bus driver using KMDF? vs Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83180
  - 5
    - Windows Server 2003 x64 SCSI fibre channel driver We have noticed a different behaviour between the Windows Server 2003 x64 and x86 SCSI fibre channel drivers. Is this the appropriate discussion group for this type of question? Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83173
  - 6
    - NDIS-TDI Example Question Hey There, Thanks for the info. I was wondering if anyone out there knows of any good TDI-NDIS examples. I'm not sure how to implement TDI to be used above NDIS. -Jay (patelj27b at gmail dot com) Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83168
  - 7
    - How to inhibit Enabling of I/O Resource Hi everybody, I have a PCI device which is able to export its Control/Status Register space (4 KB in size) to both Memory and I/O Address Space. However, due to the fact that I/O resources requirements are reported in a single PCI BAR (which in fact is a PCI spec violation), I get a Code 12 error in Device Manager ("The device cannot find enough free resources that it can use"). In this case the last function code the PNP Manager sends is IRP_MN_FILTER_RESOURCE_REQUIREMENTS. The resource requirements list reads as follows: Resource Requirements: Number of Lists: 1 List 0: Descriptors: 7 Desc 0: - Option: preferred - Type: CmResourceTypeMemory Length : 1000 Alignmt : 00000001 Min.Addr: 00000000.c0000000 Max.Addr: 00000000.c0000000 Desc 1: - Option: alternative - Type: CmResourceTypeMemory Length : 1000 Alignmt : 00001000 Min.Addr: 00000000.00000000 Max.Addr: 00000000.00000000 Desc 2: - Option: required - Type: 0x81 - NAK Desc 3: - Option: preferred - Type: CmResourceTypePort Length : 1000 Alignmt : 00000001 Min.Addr: 00000000.0000c000 Max.Addr: 00000000.0000cfff Desc 4: - Option: alternative - Type: CmResourceTypePort Length : 1000 Alignmt : 00001000 Min.Addr: 00000000.00000000 Max.Addr: 00000000.ffffffff Desc 5: - Option: required - Type: 0x81 - NAK Desc 6: - Option: required - Type: CmResourceTypeInterrupt Min.Vector: 24 Max.Vector: 24 Filtering the above list in removing descriptors 3 through 5 from the list helps: I get an IRP_MN_START_DEVICE and resources look okay in Device Manager (no I/O address range is assigned). However, if I inspect the PCI config space of the device I see the I/O Space bit in the Command Register of PCI Configuration Space enabled. This happens even if the the I/O Space comes up disabled by BIOS. To be very clear at this point: - if there is no driver registered for the device, the I/O Space bit is left unchanged - if there is a driver registered but disabled the bit also is left unchanged - if the driver is enabled, then I/O decode is enabled (even if I tell the system I do not want/need I/O ports) How can I instruct Windows XP to leave the I/O resource disabled? Thanks for any response! Gernot Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83166
  - 8
    - IoCreateDevice before or after IoInvalidateDeviceRelations I'm back-porting an XP WDM/PNP bus driver to W98SE (don't ask why!) and it seems that under 98 I must create a PDO for a newly-arrived device before I call IoInvalidateDeviceRelations, otherwise the driver does not get a following IRP_MN_QUERY_DEVICE_RELATIONS. Under XP the original driver was Invalidating the relations, then creating the PDO during the consequent IRP_MN_QUERY_DEVICE_RELATIONS handling. Is either ordering mandatory? TIA Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83163
  - 9
    - Serial Port Driver Hi! I want to write driver for serial port (COM), but I don't want support standard functions. For me that port has 2 outputs, 4 inputs and 1 interrupt source. Unfortunatelly I cannot "reserve" I/O ports and interrupt vector (IoReportResourceUsage fails) because standard driver has that resources for its own. When I turn off that serial port in BIOS, IoReportResourceUsage succeed, but writing/reading to/from output/input lines has no effect. Please for help, how to "disconnect" standard driver from one of serial ports (COM1 or COM2 - maybe another if exist) and "connect" to that port with my driver. Of cource my driver cannot figure as serial port on Windows' hardware list. Thanks for any suggestions. Best Regards. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83159
  - 10
    - IRP_MJ_READ asynchronous completion Hi, I am writing a driver for a device, which offers several interfaces - one of it is a virtual serial port. Within DispatchRead (for IRP_MJ_READ) I did as I read and thought that's correct, i.e. mark the irp pending, set a cancel routine, que it, and returned pending. I wrote a simple Win32 test program, which opened the port for overlapped IO and got the data back (if any available) with GetOverlappedResult. But the status returned by a call to GetLastError was still ERROR_IO_PENDING. When used with Microsoft Hyperterminal it seems that Hyperterminal did not get the information, that the IRP was completed at all. Thus I disabled all other interfaces and minimized my DispatchRead to the code below. It doesn't make much sense to mark the irp pending in that way but according the docs and info found on the web it should be allowed and working. IoMarkIrpPending(Irp); *((BYTE *)Irp->AssociatedIrp.SystemBuffer) = 'a'; Irp->IoStatus.Information = 1; Irp->IoStatus.Status = STATUS_SUCCESS; IoCompleteRequest(Irp, IO_SERIAL_INCREMENT); return (STATUS_PENDING); Still the same result. My Win32 program gets the data but does not get correct status information via GetLasterror and Hyperterminal does not recognize that the irp has been completed. Any idea what I do wrong or where I could have messed up my driver? Many thanks Werner Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83155
  - 11
    - _resetstkoflw() error I am get an error "The procedure entry point _resetstkoflw could not be locatedin the dynamic lik library msvcrt.dll". while executing my application. How to resolve this error? Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83149
  - 12
    - Serial Port Confusion I'm new to Serial communication, what I'm confused about is since data is being transmitted serially, should there be a clock signal as well for synchroisation. The output is a voltage for 0 or 1, how will the receiving device interpret this information without a clock? Can anyone guide me to some simple introductory material that can get me started with serial ports, I searched around but most of the articles was too much for me. I know C#/VB.NET and found articles that show me how to communicate serially but I need to know the exact working of a serial port. Thanks & Regards, Joel Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83147
  - 13
    - (mike han)(Usb MassStorage½L¡A¦b¶Ç¿é¤¤´£¥Ü"µLªk´_¨îXXXX, ¸ô®|¤Óªø"¤Î"µLªk´_¨îXXXX¡A°Ñ¼Æ¿ù»~") Dear Friends: §Ú¦Û¤v¶}µoªºUsb MassStorage½L¡A¦b¶Ç¿é¤¤´£¥Ü"µLªk´_¨îXXXX, ¸ô®|¤Óªø "¤Î"µLªk´_¨îXXXX¡A°Ñ¼Æ¿ù»~"¬O«ü¤°»ò·N«ä, §Æ±æ°ª¤H«üÂI°g¬z¡AÁÂÁÂ¡C Best Regards Mike Han Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83143
  - 14
    - NdisMEthIndicateReceive - no reaction Hi, I am developing application to encypt / decrypt TCP/IP packets data. I am using the PassThru driver extended by Thomas F. Divine (part 2 of his article). I change packet data outside the driver (in the application) so after decryption I want to indicate packet up. As a MiniportReceiveContext I use NULL, becouse I don't know where I could take it from (I thought that it is not necessary). My problem is very simple - after invoking appropriate ioctl code nothing happens. I used Ethereal to monitor packets and I can't see any of my packets (I hope I am right, that Ethereal looks above NDIS IM drivers). Please look at this little piece of code and tell me what the problem could be. Is it that MiniportReceiveContext or maybe something else. I use DbgView so I know that everything was invoked as I wanted. FltDevIoControl(){ (...) ioBuffer = pIrp->AssociatedIrp.SystemBuffer; inputBufferLength = pIrpSp->Parameters.DeviceIoControl.InputBufferLength; (...) case IOCTL_PTUSERIO_SET_INCOMING_PACKET_DATA: PUCHAR packetBuffer = NULL; UINT headerLen = 14; UINT payloadLen = inputBufferLength - headerLen; NdisAllocateMemoryWithTag(&packetBuffer, inputBufferLength, TAG ); NdisMoveMemory(packetBuffer, ioBuffer, inputBufferLength ); NdisMEthIndicateReceive( pAdapt->MiniportHandle, NULL, packetBuffer, headerLen, &packetBuffer[14], payloadLen, inputBufferLength ); break; } Thanks a lot in advance. Arek Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83136
  - 15
    - USB driver does not start after computer restart Hi everyone I am having some problems with an USB device supplied by our vendor. It comes with a standard .inf & .sys file. The first problem: even the driver can be installed properly in the first time, it always will not work after I restart the computer (it becomes Unknown Device inside Device Manager's Device List), I always have to unplug and replug the device again for it to work properly. The second problem: if I use MS devcon or Walter Oney's FastInst to install the .inf file automatically, I will always have BSOD right away. However, if I install manually by running the Windows Install Driver Wizard and select the .inf file, it can be installed without any problem. So my question is: is there a common mistake (e.g. forget to handling certain IRPs) that could cause the above two problems? I already ask our vendor and they seem quite clueless, so I would like to ask if anyone here have experienced it before and could shed some lights for me to speed up our vendor. Thanks in advance Hai Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83134
  - 16
    - Converting kernel-mode print drivers to user mode Hello all, I've recently needed to convert a Win32 print driver from kernel mode to user mode, and I ran into what I imagine are the same problems that everybody else does while doing this. Frustrated by burning time on stupid little stuff, I started keeping notes, and ended up with a pretty decent Tech Tip on the subject. Converting Win32 Kernel-mode Print Drivers to User Mode http://www.unixwiz.net/techtips/win32-pdriver-ktou.html I hope this is helpful to others in the same boat. Steve -- Steve Friedl / UNIX Wizard / Microsoft Security MVP / www.unixwiz.net Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83128
  - 17
    - PsSetCreateProcessNotifyRoutine I am trying to make something similar to task manager but when I call PsSetCreateProcessNotifyRoutine it returns this error: The specified procedure could not be found. It means that it's first parameter, the one which should have been the pointer to a procedure for callback is not recognised. I have my callback defined like this: VOID ProcMgrGabi(IN HANDLE ParentId, IN HANDLE ProcessId,BOOL Create) { etc etc etc; } and I call the function like this: rc=PsSetCreateProcessNotifyRoutine(ProcMgrGabi,FALSE); and rc returns that error what can it be Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83126
  - 18
    - data exchange betwen driver and gui aplication I want to know how can it be done corectly. I can't seem to find any documentation on this. For example how can I tell if the buffer was sent to the driver in the Type3InputBuffer variable or Irp->UserBuffer. I know it depends on how you define your control codes. I mean: METHOD bufered => the buffer will come in Irp->UserBuffer for example. Can someone clear this out for me a little or tell me where I can find documentation. I am trying to send a handle of an event in kernel mode and it always tells me that the memory is not valid but if I am sending a string it works. Please help me. Thanks in advance Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83122
  - 19
    - Ethernet bridge on WXP and IM driver I have one problem with my ndis IM driver running on WinXP with network bridge. First - on W2K3 bridge all i OK, I am seeing that IM driver is bound to "MAC bridge miniport" but also on both ethernet interfaces which is bridge composed of. But on WXP there is a bit amazing result: I am seeing that installed IM driver is bound only to "Mac bridge miniport" and I am not seeing bindings to both ethernet adapters which is bridge composed of. Second relating to this is that on WXP with bridge in my IM driver there does not go packets in outgoing direction. All packets going through IM driver on WXP with created bridge are incoming. I am seeing that this is true for packets entering through one bridged interface and leaving through second but also vice versa, so all pakcets in both directions in IM driver I am seeing like incoming packets through my PtReceiveHandler. question: Is possible also on WXP to set something and to have IM driver bound to both ethernet interfaces in bridge like on W2K3, and not only to MAC bridge miniport ? Peter Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83120
  - 20
    - How do I get a devices "Device Instance ID" programmatically Hi all, I've been working with the SetupAPI (SetupDiXxx) library in C#. It's been a challenge due to my lack of C++/WinAPI skills/experience, but I've made some great progress. I'm having problems getting a device's instance ID. Like the ID seen in the Device Manager (in case this term is ambiguous). eg. USB\VID_03F3&PID_0093\024290079102 Thus far, -- I'm able to get the ClassGuid as defined in http://msdn.microsoft.com/library/default.asp?url=/library/en-us/devinst_d/hh/DevInst_d/setup-cls_f7544122-69a3-4b34-85f5-db3714408026.xml.asp by calling the SetupDiClassGuidsFromName(...) function. -- I'm able to to create a Device Information Set (HDEVINFO) using this ClassGuid by calling SetupDiGetClassDevA(....) -- I then loop through the elements in this Device Information Set by calling SetupDiEnumDeviceInfo (...) where I'm also fortunate enough to have my SP_DEVINFO_DATA struct populated. This is where I'm having troubles. I'm not sure whether I'm calling the correct function to retreive the Device Instance ID. I was lead to believe that I could use SetupDiGetDeviceInstanceID(...) function and attain the Device Instance ID via its out parameter "OUT PTSTR DeviceInstanceId", but I'm just getting strange text at best. I don't know whether I'm barking up the wrong tree by calling this specific function or rather I'm PInvoking incorrectly this specific function. I've tried numerous variations within my PInvoke/DllImport and have struck out so far each time, some worse than others. Any advice or clarification would be greatly appreciated. Thanks, -MH Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83112
  - 21
    - USB Audio Device and USB Audio Device (2), how can VC++ mapping out physical PID? USB Audio Device and USB Audio Device (2), how can VC++ mapping out physical PID? No problem to read PID/VID. I need to send stream to a specific PID through audio channel Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83108
  - 22
    - local buffer size I am developing a dll library used by XP embedded, XP and Windows 2000 applications. How big of a local buffer is ok? None of these functions are recursive but some of my functions will internally call some other function meaning stack required in the system can be two or three times more than required for one function. I am thinking of stack problems if I define a big local buffer (buffer of 50K ) in functions. I am sure I wont need more than 50 K for the function because of other constraints. Should I allocate memory dynamically and free it before leaving the function. My arguement is defining local buffer is kind of dynamic memory because stack is released after the function call. Is it a good practice to define big buffers on stack. At what buffer size should I stop allocating local buffer and allocate a dynamic buffer. Thanks, Raj Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83107
  - 23
    - InterlockedExchange use I have a simple but important question. Problem is I cannot test and verify in a sure way. I want to compare a LONG variable with MY_VALUE. I want to do something like ' if (target == MY_VALUE) or if (target > MY_VALUE) ' thread safe way. I dont want to exchange any value. But I want the comparison to be thread safe. So I am using InterlockedExchange () even though I dont really have any value to exchange. Is this correct way to do this? if ( InterlockedExchange(&target, target) == MY_VALUE) if ( InterlockedExchange(&target, target) > MY_VALUE) Thanks, Raj Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83102
  - 24
    - Setupapi Hi all. Is it possible to call a SetupAPI function from within the SERVICE_TABLE_ENTRY::lpServiceProc routine of a service? In particular if the service is an autostart one (SERVICE_AUTO_START). I suspect that the answer is "no", as the SetupAPI (when installing an INF) calls the SCM to register the driver, and the SC database is maybe locked when the SERVICE_TABLE_ENTRY::lpServiceProc routine is invoked (maybe I'm completely wrong). Have a nice day GV PS: I don't know if this is the right NG for this query... Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83097
  - 25
    - Export Driver Hello, I need to embed a security parameter in the export driver binary (Win2K/XP) after compilation. I have defined an array in data segment which is initailized with a unique string. An external application then parses the driver sys file and modifies it to the value I want. When I use the export driver sys file, it does not load. Why does the export driver not load? Can I modify the driver file and still execute? I have done this for application exe and it works. Is there any other way I can perform the same task? Thanks, ..Ram Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83096
- Next
  - 1
    - NetCfg.dll Mystery Exports Hello All: There are a bunch of exports other than the 4 COM entry points in netcfgx.dll. These include NetCfgDiagFromCommandArgs, etc. Does anyone know where the function prototypes for these mystery functions are defined? Robert Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83094
  - 2
    - SMBus and I2C in USER mode Hi all, I need to access I2C bus (a portion of SBBus) from my USER (ring 3) app, I noticed pci.sys implemented the functionality 'Intel 82801FB/FBM SBBus Controller' but I do not know its device interface and its IOCTL. Can you help me? In the I2C some diagnostic chips are present in order to read CPU temperature, fan speed and so on... Thanks in advance. Regards, Andrea Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83091
  - 3
    - WorkItem causes a blue screen ? Hello, I coded a simple work item callback, but it crashes my computer, I can't guess why. here's the code : void WorkItemCallback( WorkItemStruct *work ) { KdPrint(( "Hello !" )); IoFreeWorkItem( work->item ); ExFreePool( work ); } work = (WorkItemStruct *) ExAllocatePool( PagedPool, sizeof(WorkItemStruct) ); if( work != NULL ) { work->item = IoAllocateWorkItem( DeviceObject ); IoQueueWorkItem( work->item, (PIO_WORKITEM_ROUTINE) WorkItemCallback, DelayedWorkQueue, work ); } And here's the bugcheck : *** Fatal System Error: 0x0000007e (0xC0000005,0x80550211,0xF7A5BC50,0xF7A5B94C) What could cause this bug ? Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83089
  - 4
    - New to BDA driver I am new to writing BDA driver. But there is something I am confused. From DDK docs, As I know, at driverentry point, Calling KsInitializeDriver function will initialize the the driver object of an AVStream minidriver. Then AVStream will call AVStrMiniDeviceAdd(AddDevice routine). At this point, WDM device object is created and KSDEVICE structure is initialed. There is a sensence showed in DDK Doc: Minidrivers can use this routine to associate context information with the AVStream device object, or to initialize a device extension. Question 1: What is context information? Does this mean device extension? If it does, what does device extension belong to? Minidriver? or User-created device extension? Question 2: Can I store User-created device extension in context information? or store into KSDEVICE.FunctionalDeviceObject.DeviceExtension? I try to look up the KSDevice structure. I am confused something,too. Question 3: Does FunctionalDeviceObject of KSDevice belong to this minidriver? If I want to add USB support into BDA, Should I aquire FunctionalDeviceObject for USB? or leave it alone, put USB support in the PDO? or there is another method? Really need experts' help for my confusing. Thanks Roache Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83081
  - 5
    - WinXP SDIO Interrupt Handling Dear all, We have now completed our winxp driver upto CMD 53 Byte mode successfully Block mode is failing .(WINXP Bus Driver fault it seems)but the problem now is on Interrupt handling actually on an Interrupt we were able to proceed into Interrupt Handler but when we try to issue CMD 52 there we are getting a status STATUS_DELETE_PENDING we also need some help for Interrupt aknowledge routine regards Nake Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83080
  - 6
    - How to know the BandWidth of a USB 2.0 device? Hi all, I connected my webcam to USB 2.0 port, when live preview, I checked the device manager, it says the USB bandwidth used is 398%! when connect to USB1.1 port, the value is 60%, I think 60% is reasonable. How do I know the actual used BandWidth when connect my webcam to USB2.0 port? Thanks in advance, Barry Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83078
  - 7
    - Bimap character size Hi, I am working on Text rendering in printer driver. I have to download the given text as bitmap, so after downloading the font header information, i am trying to download the character header information, the character header contains 'Left offset', 'Top offset', 'Bitmap width' and 'Bitmap height'. I have obtained the width and height from sizlBitmap member of GLYPHBITS structure, but these vealues are not matching with the required result, like For character 'b' of Arial-12, the Required width=45 i am getting 896 and Requred height=73 i m getting 96 And i am not getting how to find out the left and top offsets. Can anybody help me in obtainig correct values for all these parameters. Thanks. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83076
  - 8
    - Virtual COM Driver Occurs Surprise Removal Event When CPU Loading is High Dear all, I write a Virtual COM Driver, it can transfers data from COM port to USB port. It's lower driver is USB driver (USBHID.sys) developed by Microsoft. But when CPU Load increase to 100%, a "Surprise Removal" event happens. Though it is not removed from Device Manager, it doesn't work normally. Anyone knows the reason? Any help will be appreciate! Best Regards, David Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83072
  - 9
    - Tutorial for understanding / using the Setup API available for non-C++ wizards? Hi all, Does anybody know if there is a tutorial or documentation that explains the usage of the Setup API for those w/o much unmanaged code experience. I've been working on test automation where we check whether a device can be disabled and then re-enabled. This is a manual test currently which we're striving to move to our automation. I thought that I had this figured out but each perceived step forward in the right direction presents yet another logic error. Currently, we're trying to implement this in C# using PInvoke. I don't have a world of experience/skill w/ C++ nor using PInvoke so this has been quite a challenge. I've been looking at the devcon example included in the Windows 2003 SP1 DDK along w/ various usage examples/soure code online but am still tripping in various places :(. Any guidance/direction would be greatly appreciated! Thanks a trillion, MH Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83066
  - 10
    - Can't Get "SRB_INDICATE_MASTER_CLOCK" Ctrl Packet from SRB Dear all : I write a stream mini Audio driver . i am invoke StreamClassQueryMasterClockSync function to get stream time . But i can't get the "TimeContext.Time" cause i can't got the hMasterClock handle from "SRB_INDICATE_MASTER_CLOCK" control packet . So , what can i do some setting for let get the "SRB_INDICATE_MASTER_CLOCK" control packet to get Srb->CommandData.MasterClockHandle value ?? Small Chang Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83059
  - 11
    - Query on USB bus driver Hi all, Currently iam working in faking a usb bus driver. I am catching all the query asked from the class driver which is on the top layer of my bus driver. The problem what i am facing now is in setting the configuration for the class driver? The class driver inorder to set a configuration creating a URB by passing the corresponding configuration descriptor to the bus driver which it wants to set. In response to this query my bus driver has to send a configration handle back to the class driver. How a bus driver will get a handle to a configration? What is the need of this configration handle? Similarly for the interface and endpoints? Please help me Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83056
  - 12
    - question for the pro's I install my NDIS IM driver on a laptop that has an intel wireless adapter and pretty soon it starts blue screening. When I check the crash dump there is nothing in it about my driver ... the crash is happening inside the NIC driver (s24trans.sys) How on earth do I debug this? Even though it is not my driver that crashes, my driver must be partially responsible, because the other driver only begins to crash when mine is installed. I've thought about the idea of installing a checked build of xp on the crashing system and then hopefully the crash dumps might contain more information ... but ultimately I'll still be staring at a bunch of assembler written by MS or Intel! Any ideas? Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83055
  - 13
    - About using Intrinsics in Driver Hello, I am trying to use MMX Intrinsics to speedup driver performace. It includes <mmintrin.h>. Driver codes are compiled fine but it get errors whtn linking. -- 1>defect.obj : error LNK2001: unresolved external symbol _m_empty -- _m_empty is an MMX Intrinsic. What's wrong with it? I am using DDK 3790.1830 for x64 version driver. Is there anyone can help me? Thanks a lot. Saxen Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83054
  - 14
    - interfacing to a flash device I have been tasked to write a driver for a device that uses a flash interface for I/O. The device in question does not support Plug and Play so I am trying to figure out how Windows will be able to get config info from it. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83047
  - 15
    - ACPI intercepting power button (and lid switch) questions (XP) Hi, I want to intercept ACPI power button (and perhaps also the lid switch on a notebook) in order to gain more control on what to do depending on application status. Unfortunately the WM_QUERYENDSESSION method is not sufficient to me because a couple of applications (e.g visual studio) terminate themselves even if my app returns that it does not want windows to shutdown/whatever. How is the button press communicated from kernel to user space? (same for lid switch) What windows process is the first consumer of these events? Which windows process is displaying the dialog for standby, power down, restart if the power button is configured for "Ask what to do" ? (winlogon, crss, ... ) While poking around I installed a custom gina dll (using the original msgina.dll but created a GinaDLL registry entry). As soon as this GinaDLL entry was present, the system displayed the old fashioned dialog instead of the new colorful XP shutdown dialog. With help of a small program I discovered that the dialog window which has focus (after a power button press) seems to belong to the windows explorer process . Interestingly when I kill the explorer the same dialog is being displayed nevertheless, so there seems to be more than one process which can display the power down dialog. Please help me to understand better whats exactly going on after power button press. Regards, Konrad Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83029
  - 16
    - MiniportHalt is not being called Hi Expert, My NIC driver sometimes doesn't call MiniportHalt after surprise remove and I realize that some packets may not be compete. But I check my TX queue all pending packets have been completed. So I try do dump the miniport open block queue as below. My question is what does STATUS_RECEIVED mean? Thanks! kd> !mopen 8214f3e0 Miniport Open Block 8214f3e0 Protocol 82327bf0 = PSCHED, ProtocolContext 815c1008, v5.0 Miniport 815a4130 = My NIC LAN Card #2, v0.0 MiniportAdapterContext: ffb01000 Flags : 00000100 STATUS_RECEIVED, References : 1 Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83025
  - 17
    - USB Hub driver Hi, I have encountered a strange problem. And I have a few doubts regarding this. Here it goes... I have a 4 port Belkin hub connected to my system . To one of the port, I have my Smartcard Reader connected and to another port I have connected a Serial to USB converter. Now I open the serial port from the hyper Terminal. Now if I unplug the USB Hub, USB Hub sends IRP_MN_SURPRISE_REMOVE to my Smartcard Reader, which my reader completes and returns STATUS_SUCCESS. However my reader doesn't recieve the IRP_MN_REMOVE notification and hence my device doesnt gets unloaded. However the entries are removed from the Device Manager. Now if I diconnect the COM port, my reader driver gets the IRP_MN_REMOVE and gets unloaded. In short, my reader driver does not get unloaded as long as the COM port is open. Now my assumption is that when the PNP manager sends IRP_MN_SURPRISE REMOVAL to both my reader driver and the Serial port driver , both should complete it with Status Success, and subsequently both should receive an IRP_MN_REMOVE , thus unloading the drivers. Then why is it behaving this way.? Is it a known issue, or is it something to do with my reader driver? Thanks in Advance for the help. Sareena. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83019
  - 18
    - install root-enumerated device driver via .MSI file? I'm using MAKEMSI to build a .MSI file that intalls my various device drivers. So far I have been able to create a .MM file that appends a location to the DevicePath registry key when the .MSI runs so that Windows knows where to search for the .INF/.SYS files for my PnP drivers. However, I would also like to install a root-enumerated bus driver (basically a modified toaster bus) at the time when the .MSI runs. How do I do this? Can I do this via some VBSCRIPT inside the .MM file? It seems that DIFxAPP does not support root-enumerated drivers and that DEVCON is not redistributable, so I guess these will not help me. Thanks in advance for your suggestions. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83017
  - 19
    - Windows CE USB development First let me explain about the project a bit. There is a Hardware that contains a Real Time OS that suports USB (host). My job is to develop a program do get the data from (via USB) the hardware and plot a math graph of it in the PDA Pocket PC . For now, I decided to use C# . The visual Studial has a nice GUI for mobile programing. My problems: 1) Is there a USB conector to the pocket pc ? a kind compact flash that conects to the palm and suport USB ? The cradle always start the MS activeSync. 2) The pocket needs to find the USB host (hardware). Is there any programs out there for windows CE for USB develpment? any C# codes o? Or I should not be worried about the pocket USB since the Hardware is the Host USB? thanks. Best regards, Alberto. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83016
  - 20
    - USB Issue i had two USB connected to my computer... and i m tracking URB going to USBBus, can anybody tell me how handles which URB should be send to which devices.. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83012
  - 21
    - Send data to Spooler Hello All, I am writing a component which gets the data through USB interface. I want to send this data to print spooler component. I m using Windows API functions like OpenPrinter(...), WritePrinter(...) etc to communicate with spooler. I have just began implementing this API. So, I would like to know if this approach is a feasible one to communicate with spooler directly. Do i need to develop any other component or plug-in to talk to spooler. Any help would be of use. Thank You, Regards, Sushma. Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83010
  - 22
    - How to set pattern for wake-up frame ? I am trying to set my PC to wake up by frames which contains patterns defined by me, in properties of my network card I am seeing that such capability (wake-up frame) is supported and enabled. But I cannot find some software on web pages of vendor of this network card for setting pattern. In DDK doc I am seeing, that there exist OID... for this which can be sent by protocol drivers, so I think that there exists some applications with protocol drivers able to set it. Where can I find such application ? Thx ! Peter Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 83008
  - 23
    - ZwCreateFile fails for harddisk device Hi, I am trying to open a physical disk object to extract some hard disk properties, but the ZwCreateFile keeps failing. I had tried \??\PhysicalDrive0, \Device\Harddisk0 etc but everyone of this fails. Following is the code snippet.... NTSTATUS OpenPhysicalDisk(char* pszDevice, PHANDLE pHandle) { IO_STATUS_BLOCK IoStatusBlock ; OBJECT_ATTRIBUTES ObjectAttributes ; LARGE_INTEGER AllocSize ; NTSTATUS status ; WCHAR wszDevice[BYTES_256] ; UNICODE_STRING ObjectName ; //mbstowcs(wszDevice, pszDevice, strlen(pszDevice)+1) ; wcscpy(wszDevice, L"\\??\\PhysicalDrive0") ; RtlInitUnicodeString(&ObjectName, wszDevice) ; InitializeObjectAttributes(&ObjectAttributes, &ObjectName, OBJ_CASE_INSENSITIVE | OBJ_KERNEL_HANDLE, NULL, NULL); RtlZeroMemory(&IoStatusBlock, sizeof(IO_STATUS_BLOCK)) ; AllocSize.QuadPart = 0; status = ZwCreateFile(pHandle, GENERIC_READ|GENERIC_WRITE, &ObjectAttributes, &IoStatusBlock, &AllocSize, FILE_ATTRIBUTE_NORMAL, FILE_SHARE_READ|FILE_SHARE_WRITE, FILE_OPEN, FILE_DIRECTORY_FILE, NULL, 0) ; DbgPrint("ZwCreateFile status = 0x%x\n", status) ; } I get one of the following error codes when i use different names: STATUS_OBJECT_NAME_INVALID STATUS_OBJECT_NAME_NOT_FOUND STATUS_INVALID_PARAMETER Can someone please direct me what is wrong here or what i should be doing? Thanks in advance Brijesh Mishra Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 82990
  - 24
    - Windows DDK build with Visual Studio 2005? Error 1 error PRJ0019: A tool returned an error code from "Performing Makefile project actions" What does this mean. Do I miss something? Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 82968
  - 25
    - _EPROCESS::ProcessExiting and PsGetProcessExitProcessCalled(). As posted before, Iâ??ve been having some problems with preparing to go into another process just as it is shutting down. I finally managed to avoid this simply by using: if ( pParms->peProc->ProcessExiting ) { return NtStatus; } So if the process is closing, I just return. However, the _EPROCESS structure changes unpredictably with service packs and versions of Windows, so I changed this code to: if ( PsGetProcessExitProcessCalled( pParms->peProc ) ) { return NtStatus; } According to every site I can find, the actual code for PsGetProcessExitProcessCalled() is: NTSTATUS NTAPI PsGetProcessExitProcessCalled(PEPROCESS Process) { return Process->ProcessExiting; } So it should be doing the same thing, but will work correctly on each version of Windows that supports this function. However it does not! My function ended up always returning at that line, even though the process was not closing. I put a debug print and printed both pParms->peProc->ProcessExiting and PsGetProcessExitProcessCalled( pParms->peProc ) and I got this: pParms->peProc->ProcessExiting: 0x0 PsGetProcessExitProcessCalled( pParms->peProc ): 0x34200 Why are these different values? PsGetProcessExitProcessCalled() doesnâ??t know the correct offsets in its own structures? When I use pParms->peProc->ProcessExiting directly it works fine, and my function does not try to go into the target process while it is closing, avoiding the crashes I have been getting. So my header files are correctly defining _EPROCESS. But why are these 3rd-party hack-up header files more accurate than the real thing? is PsGetProcessExitProcessCalled() returning the whole DWORD where ProcessExiting is or what? How can I get this to work without using ProcessExiting directly? Tag: Webcam "Hazy" effect on USB1.1 mode Tag: 82960

My webcam driver is based on "usbintel" sample in DDK src\wdm\videocap
folder. We changed it to support 64-bit system but encountered a problem when
connect the device to USB1.1 port (via a USB1.1 hub which connect to a USB2.0
port on motherboard) on 64-bit XP. The issue is : preview effect is hazy,
it's like cover the preview window by using a gray semitransparent cloth. I
have no idea how come that happened? Is it related to the sensor settings or
USB chip control?

Any suggestion would be greatly appreciated~

Barry

Top