Which type of driver should I develop to turn a file to a pesudo-d

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
    - Keyboard filter driver - obtaining keyboard indicator status Hi all, I am new to device driver development and am currently writing an upper filter driver for a USB keyboard. My first step I am trying is to obtain the LED information from the keyboard from a user-mode application. I have followed the Windows example (toaster filter) regarding creating a control device object in the upper filter driver and am able to obtain a handle to this control device object in the user-mode application. However, I then attempt to obtain the LED information as follows in the application: USBHandle = CreateFile("\\\\.\\KeyboardUSB", GENERIC_READ | GENERIC_WRITE, NULL, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL); if (USBHandle != INVALID_HANDLE_VALUE) { status = DeviceIoControl(USBHandle, IOCTL_KEYBOARD_QUERY_INDICATORS, NULL, 0, &kbdParam, sizeof(kbdParam), &outLength, NULL); } In the filter driver, I receive the correct IRP (as below in my DispatchIO routine), but am unsure how to obtain and return the correct data. Below shows what I am currently attempting to do. irpStack = IoGetCurrentIrpStackLocation(Irp); switch (irpStack->MajorFunction) { case IRP_MJ_DEVICE_CONTROL: #ifdef DEBUG WriteLogFile("DispatchIo: IRP_MJ_DEVICE_CONTROL\r\n", 35); #endif switch (irpStack->Parameters.DeviceIoControl.IoControlCode) { case IOCTL_KEYBOARD_QUERY_INDICATORS: #ifdef DEBUG WriteLogFile("DispatchIo: IOCTL_KEYBOARD_QUERY_INDICATORS\r\n", 45); #endif return FilterPass(MainDeviceObject, Irp); break; default: break; } default: break; } Therefore, my main question is how to execute the IRPs correctly that are created from my application using DeviceIoControl. Do I need to use completion routines and if so, how should these be used? Thanks in advance, Kyzer Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72294
  - 2
    - How to post message to application Hi, I am writing application which shows some status of kernel driver on real time basis. I tried to achieve this by posting messages from kernel driver, but I could not find such API in DDK. Is there any way to post or send messages from kernel driver? Thanks Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72292
  - 3
    - USB client driver between Usbhub.sys and other client drivers. Greetings Experts! I hope some of you were written USB Client drivers for XP and 2000. I have to do the same - an USB client driver on top of Usbhub.sys. The only purpose of this driver is to implement vendor-specific request IOCTRL_ and talk to the Enpoint 0 of an USB device. The problem here is that in our system there are some other USB Client drivers like usbser.sys, blan.sys, some composite client drivers, etc. The driver I am to write should expose an additional interface in the Device Manager and co-exist with these client drivers. In my opinion I should place my 'vendor-specific' driver on top of Usbhub.sys and below another USB client drivers that we have. Please correct me if I am wrong. It seams that the problem here is how to place this driver properly in the driver stack... I will be very grateful if you can give me information, an advice or direct me to some DDK samples implementing a similar driver. Thanks in advance! Dim Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72291
  - 4
    - How to load NDIS driver for SDIO bus in Windows CE? I hope some one can help. I am trying to write a NDIS driver in windows CE. The driver interface is an SDIO bus. My first step was to write an SDIO stream driver to test that card. It's worked like magic. Second step was to try loading an NDIS driver for this card. According to Microsoft documentation I have to do the fallowing: 1. Write a dll that export "DriverEntry". 2. Add a key in the registry [HKEY_LOCAL_MACHINE \Comm \MYDRV] DisplayName="MYDRV NDIS Driver" Group ="NDIS" ImagePath="MYDRV.DLL" [Linkage] Route="MYDRV1" [HKEY_LOCAL_MACHINE \Comm \MYDRV1] DisplayName="MYDRV NDIS Driver" Group ="NDIS" ImagePath="MYDRV.DLL" [Parms] BusNumber=0 BusType=0 [HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Custom\MANF-02DF-CARDID-9103-FUNC-1] DLL="NDIS.DLL" Prefix= "NDS" Miniport=" MYDRV " As a resulted my DllMain was call twice one for load and one for unload. Can some one tell me what I am doing wrong? Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72286
  - 5
    - WinCE crash - HeapAlloc function Hi, I am working on a passthru driver for WinCE platform and recently (after updating the wlan.dll as there was some problem with the adhoc mode), it started crashing randomly. Some of the crashes are outside the modified passthru driver. I have attached few crash dumps below. I am not having any clue for the crash as it is happening randomly, sometimes after running the system for few minutes and sometimes after few hours. Any insight in this problem will be greatly appreciated or how can I go about debugging this problem. Thanks, -Niranjan Wireless Terminals Lab, Samsung Telecommunication America. CRASH 1: COREDLL!FindFreeItemInRegion(void * 0x00000000, region * 0x20302030, int 0x08d5ddf8) line 841 + 8 bytes COREDLL!FindFreeItem(void * 0x00000000, heap * 0x20302030, unsigned long 0x08d5ddf8, region * * 0x00000020) line 921 + 16 bytes COREDLL!Int_HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d5ddf8) line 1256 + 20 bytes LMEMDEBUG!HeapAllocTrace(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d5ddf8, unsigned long 0x00000020, char * 0x00000000) line 721 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d5ddf8) line 742 COREDLL!LocalAlloc(unsigned int 0x00000000, unsigned int 0x20302030) line 197 WZCSVC!MIDL_user_allocate(unsigned int 0x00000000) line 33 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d5ddf8) line 742 5a1fddc6() LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d5ddf8) line 742 WZCSVC!CE_QueryInterface(unsigned char * 0x00000000, unsigned long 0x20302030, unsigned long * 0x08d5ddf8) line 1751 + 12 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d5ddf8) line 742 NK! first chance exception in ndis.dll (0xC0000005: illegal instruction) **************************************************************************** *************************************************** CRASH 2: COREDLL!FindFreeItemInRegion(void * 0x00000000, region * 0x20302030, int 0x08d54e48) line 841 + 8 bytes COREDLL!FindFreeItem(void * 0x00000000, heap * 0x20302030, unsigned long 0x08d54e48, region * * 0x00000030) line 921 + 16 bytes COREDLL!Int_HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d54e48) line 1256 + 20 bytes LMEMDEBUG!HeapAllocTrace(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d54e48, unsigned long 0x00000030, char * 0x00000000) line 721 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d54e48) line 742 COREDLL!LocalAlloc(unsigned int 0x00000000, unsigned int 0x20302030) line 197 NDIS!NdisAllocateMemory(void * * 0x00000000, unsigned int 0x20302030, unsigned int 0x08d54e48, _LARGE_INTEGER {...}) line 165 LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d54e48) line 742 PASSTHRU!KNEWZ(int 0x0000005c) line 45 PASSTHRU!fast_timer_new(unsigned long * 0x00d54bfc, int 0x00000320, unsigned int 0x00000002, void (unsigned long, void *)* 0x010e958c marp_timer_callback(unsigned long, void *), void * 0x00d54bfc) line 108 + 8 bytes PASSTHRU!marp_timer_new(marp_timer * 0x00d54bfc, int 0x00000320, unsigned int 0x00000002, void (marp_timer *, void *)* 0x010e6a8c marp_rreq_record_cb(marp_timer *, void *), void * 0x00d54bf0) line 49 + 28 bytes PASSTHRU!marp_rreq_record_insert(unsigned char * 0x00d5331c, unsigned int 0x00000006) line 716 PASSTHRU!marp_rreq_process_start(marp_os_buf * 0x00d53e30, marp_rreq * 0x00d532d0) line 1218 PASSTHRU!marp_rreq_process(marp_os_buf * 0x00d53e30) line 331 + 12 bytes PASSTHRU!marp_process_packet(marp_os_buf * 0x00d53e30) line 347 PASSTHRU!marp_process_event() line 346 PASSTHRU!marp_thread() line 398 first chance exception in ndis.dll (0xC0000005: Access Violation) **************************************************************************** *********************************************************** CRASH 3: COREDLL!FindFreeItemInRegion(void * 0x00000000, region * 0x20302030, int 0x08beb3a8) line 841 + 8 bytes COREDLL!FindFreeItem(void * 0x00000000, heap * 0x20302030, unsigned long 0x08beb3a8, region * * 0x00000060) line 921 + 16 bytes COREDLL!Int_HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08beb3a8) line 1256 + 20 bytes LMEMDEBUG!HeapAllocTrace(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08beb3a8, unsigned long 0x00000060, char * 0x00000000) line 721 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08beb3a8) line 742 COREDLL!LocalAlloc(unsigned int 0x00000000, unsigned int 0x20302030) line 197 WZCSVC!MIDL_user_allocate(unsigned int 0x00000000) line 33 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08beb3a8) line 742 first chance exception in ndis.dll (0xC0000005: Access Violation) **************************************************************************** ************************************************** CRASH 4: COREDLL!FindFreeItemInRegion(void * 0x00000000, region * 0x20302030, int 0x08d4df58) line 841 + 8 bytes COREDLL!FindFreeItem(void * 0x00000000, heap * 0x20302030, unsigned long 0x08d4df58, region * * 0x00000020) line 921 + 16 bytes COREDLL!Int_HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d4df58) line 1256 + 20 bytes LMEMDEBUG!HeapAllocTrace(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d4df58, unsigned long 0x00000020, char * 0x00000000) line 721 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d4df58) line 742 COREDLL!LocalAlloc(unsigned int 0x00000000, unsigned int 0x20302030) line 197 NDIS!NdisAllocateMemory(void * * 0x00000000, unsigned int 0x20302030, unsigned int 0x08d4df58, _LARGE_INTEGER {...}) line 165 LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08d4df58) line 742 PASSTHRU!marp_copy_ndis_packet_add_marp_hdr(_NDIS_PACKET * 0x00bb01a4, _NDIS_PACKET * 0x00051afc, _BINDING * 0x00a9e3b0) line 277 + 20 bytes PASSTHRU!MiniportSendPackets(void * 0x00a9e3b0, _NDIS_PACKET * * 0x0862f7e8, unsigned int 0x00000001) line 335 NDIS!ndisMSendX(void * 0x00000000, _NDIS_PACKET * 0x20302030) first chance exception in ndis.dll (0xC0000005: Access Violation) **************************************************************************** ************************************************************ CRASH 5: COREDLL!FindFreeItemInRegion(void * 0x00000000, region * 0x20302030, int 0x08bc4ed8) line 841 + 8 bytes COREDLL!FindFreeItem(void * 0x00000000, heap * 0x20302030, unsigned long 0x08bc4ed8, region * * 0x00000020) line 921 + 16 bytes COREDLL!Int_HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08bc4ed8) line 1256 + 20 bytes LMEMDEBUG!HeapAllocTrace(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08bc4ed8, unsigned long 0x00000020, char * 0x00000000) line 721 + 4 bytes LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08bc4ed8) line 742 COREDLL!LocalAlloc(unsigned int 0x00000000, unsigned int 0x20302030) line 197 NDIS!NdisAllocateMemory(void * * 0x00000000, unsigned int 0x20302030, unsigned int 0x08bc4ed8, _LARGE_INTEGER {...}) line 165 LMEMDEBUG!HeapAlloc(void * 0x00000000, unsigned long 0x20302030, unsigned long 0x08bc4ed8) line 742 PASSTHRU!KNEWZ(int 0x0000000c) line 45 PASSTHRU!fast_timer_set(unsigned long 0x00bc8d00, int 0x00000802) line 233 + 8 bytes PASSTHRU!marp_timer_set(marp_timer * 0x00bbfff0, int 0x00000802) line 141 PASSTHRU!marp_neighbor_add(marp_os_buf * 0x00bcabb0, unsigned char * 0x00bcaae4, unsigned int 0x00000007) line 211 PASSTHRU!marp_hello_process(marp_os_buf * 0x00bcabb0) line 263 PASSTHRU!marp_rrep_process(marp_os_buf * 0x00bcabb0) line 279 PASSTHRU!marp_process_packet(marp_os_buf * 0x00bcabb0) line 353 PASSTHRU!marp_process_event() line 346 PASSTHRU!marp_thread() line 398 COREDLL!ThreadBaseFunc(void * 0x00000000, unsigned long 0x20302030) line 419 first chance exception in ndis.dll (0xC0000005: Access Violation) Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72277
  - 6
    - How to check a driver is digitally signed through code? Hello, How does the driverquery.exe obtain info on a driver if it is digitally signed? Any help would be appreciated. Thanks, ~ jiac Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72271
  - 7
    - How to check a driver is digitally signed through code? Hello, How does the driverquery.exe obtain info on a driver if it is digitally signed? Any help would be appreciated. Thanks, ~ jiac Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72270
  - 8
    - UniDrv Printer Driver with plugins, Need 'hPrinter' (handle) in function hrOEMDevicePropertySheets(-) UniDrv Printer Driver with plugins, Need 'hPrinter' (handle) in function hrOEMDevicePropertySheets(-) Modified WDK example printer "graphics and UI plugins". Cannot seem to find a way to get a valid "printer handle" function hrOEMDevicePropertySheets(-). Any ideas? -Rudy Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72265
  - 9
    - Bug check calling nt!RtlQueryEnvironmentVariable_U Hello, I am writing a minifilter driver that reads some configuration data from the registry in its DriverEntry procedure using RtlQueryRegistryValues. If I use REG_SZ values in the registry then everything works as expected. However if I use REG_EXPAND_SZ values the system bug checks when calling nt!RtlQueryEnvironmentVariable_U. The bug check is PAGE_FAULT_IN_NONPAGED_AREA (50) and it occurs right at the beginning of RtlQueryEnvironmentVariable_U. When I examine RtlQueryEnvironmentVariable_U in the debugger it looks like the procedure is paged out (the debugger just shows ?? for the diassembly). Details are at the end of the message. Can anyone tell me what's going on and how to fix the problem? I'm using the Windows XP SP2 checked build with the driver verifier enabled for my driver (same problem occurs with the free build without the driver verifier IIRC). Cheers, Chris My code: 696 UNICODE_STRING uTop, uBottom; 697 UNICODE_STRING uTopPath = { 0 }; 698 UNICODE_STRING uBottomPath = { 0 }; 699 PKEY_VALUE_PARTIAL_INFORMATION pkvpi; 700 RTL_QUERY_REGISTRY_TABLE QueryTable[3]; 701 PVOID TopBuffer = NULL; 702 PVOID BottomBuffer = NULL; 703 704 RtlZeroMemory( QueryTable, sizeof( QueryTable ) ); 705 706 QueryTable[0].Flags = RTL_QUERY_REGISTRY_REQUIRED | RTL_QUERY_REGISTRY_DIRECT; 707 QueryTable[0].Name = L"Top"; 708 QueryTable[0].EntryContext = &uTopPath; 709 QueryTable[1].Flags = RTL_QUERY_REGISTRY_REQUIRED | RTL_QUERY_REGISTRY_DIRECT; 710 QueryTable[1].Name = L"Bottom"; 711 QueryTable[1].EntryContext = &uBottomPath; 712 713 ASSERT( KeGetCurrentIrql( ) == PASSIVE_LEVEL ); 714 715 status = RtlQueryRegistryValues( RTL_REGISTRY_HANDLE, ( PCWSTR ) SubKeyHandle, QueryTable, NULL, NULL ); 716 if ( !NT_SUCCESS( status ) ) { 717 OVL_DBG_PRINT( OVLDBG_TRACE_ERRORS, 718 ( "Overlay!OverlayInitFromRegistry: RtlQueryRegistryValues failed %08x\n", status ) ); 719 } else { 720 OVL_DBG_PRINT( OVLDBG_TRACE_VERBOSE, 721 ( "Overlay!OverlayInitFromRegistry: uTopPath = \"%wZ\" uBottomPath = \"%wZ\"\n", &uTopPath, 722 &uBottomPath ) ); 723 status = OverlayAdd( &uBottomPath, &uTopPath ); 724 if ( !NT_SUCCESS( status ) ) 725 OVL_DBG_PRINT( OVLDBG_TRACE_ERRORS, ( "Overlay!OverlayInitFromRegistry: OverlayAdd failed %08x\n", status ) ); 726 727 RtlFreeUnicodeString( &uBottomPath ); 728 RtlFreeUnicodeString( &uTopPath ); 729 } (Some of the declared variables are unused.) Debugger output: ******************************************************************************* * * This is the string you add to your checkin description * Driver Verifier: Enabled for Overlay.sys on Build 2600 bvs3DuzH2lcqtHJHBbXCJD * ******************************************************************************* Overlay!DriverEntry: Entered Overlay!DriverEntry: Build Nov 18 2005 11:42:25 Overlay!OverlayInitFromRegistry: Entered Overlay!OverlayInitFromRegistry: RegistryPath = "\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Overlay" Overlay!OverlayInitFromRegistry: SubKeys = 1 *** Fatal System Error: 0x00000050 (0x80D463E6,0x00000000,0x80D463E6,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE Loading Kernel Symbols .................................................................................................. Loading unloaded module list ............ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {80d463e6, 0, 80d463e6, 0} Probably caused by : Overlay.sys ( Overlay!OverlayInitFromRegistry+314 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80aba26c cc int 3 kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 80d463e6, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 80d463e6, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ OVERLAPPED_MODULE: rdbss READ_ADDRESS: 80d463e6 FAULTING_IP: nt!RtlQueryEnvironmentVariable_U+0 80d463e6 ?? ??? MM_INTERNAL_CODE: 0 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 LAST_CONTROL_TRANSFER: from 80bf3c51 to 80d463e6 TRAP_FRAME: f9744a10 -- (.trap fffffffff9744a10) ErrCode = 00000000 eax=f9744aa8 ebx=00000026 ecx=00000016 edx=00000000 esi=e12dd8b4 edi=e12dd8cc eip=80d463e6 esp=f9744a84 ebp=f9744ac0 iopl=0 nv up ei pl zr na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000246 nt!RtlQueryEnvironmentVariable_U: 80d463e6 ?? ??? Resetting default scope STACK_TEXT: f9744a80 80bf3c51 00000000 f9744aa8 f9744aa0 nt!RtlQueryEnvironmentVariable_U f9744ac0 80bf44c4 00000000 00000082 f9744aec nt!RtlExpandEnvironmentStrings_U+0xed f9744b04 80bf4957 f9744b90 e12dd8b4 f9744b64 nt!RtlpCallQueryRegistryRoutine+0x2f4 f9744b68 f56b588e 00000000 00000084 00000001 nt!RtlQueryRegistryValues+0x2dd f9744c6c f56b64e3 ff984000 81d46610 f9744d58 Overlay!OverlayInitFromRegistry+0x314 [c:\winddk\5112\src\filesys\minifilter\overlay\overlay.c @ 715] f9744c7c 80b3368a 81d46610 ff984000 f597fce8 Overlay!DriverEntry+0x5d [c:\winddk\5112\src\filesys\minifilter\overlay\overlay.c @ 954] f9744d58 80b338ba 000004c0 00000001 00000000 nt!IopLoadDriver+0x6b6 f9744d80 80acbd9f 00000000 00000000 81dbc848 nt!IopLoadUnloadDriver+0x78 f9744dac 80bcb95a f597fce8 00000000 00000000 nt!ExpWorkerThread+0x10f f9744ddc 80adae82 80acbc90 80000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FAILED_INSTRUCTION_ADDRESS: nt!RtlQueryEnvironmentVariable_U+0 80d463e6 ?? ??? FOLLOWUP_IP: Overlay!OverlayInitFromRegistry+314 [c:\winddk\5112\src\filesys\minifilter\overlay\overlay.c @ 715] f56b588e 8bf0 mov esi,eax SYMBOL_STACK_INDEX: 4 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: Overlay!OverlayInitFromRegistry+314 MODULE_NAME: Overlay IMAGE_NAME: Overlay.sys DEBUG_FLR_IMAGE_TIMESTAMP: 437dbe21 STACK_COMMAND: .trap fffffffff9744a10 ; kb FAILURE_BUCKET_ID: 0x50_CODE_AV_BAD_IP_Overlay!OverlayInitFromRegistry+314 BUCKET_ID: 0x50_CODE_AV_BAD_IP_Overlay!OverlayInitFromRegistry+314 Followup: MachineOwner --------- Disassembly of nt!RtlQueryEnvironmentVariable_U: No prior disassembly possible nt!RtlQueryEnvironmentVariable_U: 80d463e6 ?? ??? 80d463e7 ?? ??? 80d463e8 ?? ??? 80d463e9 ?? ??? 80d463ea ?? ??? 80d463eb ?? ??? 80d463ec ?? ??? 80d463ed ?? ??? 80d463ee ?? ??? 80d463ef ?? ??? 80d463f0 ?? ??? 80d463f1 ?? ??? 80d463f2 ?? ??? 80d463f3 ?? ??? 80d463f4 ?? ??? 80d463f5 ?? ??? 80d463f6 ?? ??? 80d463f7 ?? ??? 80d463f8 ?? ??? 80d463f9 ?? ??? 80d463fa ?? ??? 80d463fb ?? ??? 80d463fc ?? ??? 80d463fd ?? ??? 80d463fe ?? ??? 80d463ff ?? ??? 80d46400 ?? ??? Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72258
  - 10
    - A question about gdi functions for a print processor. Hi I'm working on a printer driver. ours is Unidriver-based driver. I'm programming with the sample sources of a print processor that are in the Windows DDK. (\WINDDK\3790\src\print\genprint) The sample sources already implemented a few printing features such as n-up, reverse printing, etc... i want to make a feature of manual duplex with the sample sources, but i got a problem. As you know, the manual duplex feature is that the front data of pages for duplex is printed at first, and then the driver show a message box that inform of the user to put the printed matters on the multi-purpose tray. Finally, the back data of pages for duplex is printed. So, i refered to the sample code amd made a linked list that store a page information. i used Gdi functions for a print processor such as GdiStartDocEMF() and GdiEndDocEMF().... but.. I got a problem.. the problme is that after the front data of pages for duplex is sent to spooler, i called GdiEndDocEMF() function to eject all the front data of page from printer. At that time, unforunately.. the emf data is deleted from spooler. T_T although i called GdiStartDocEMF() to tranlate the back data of pages, the return of the function is failed,(the GetLastErr() is 62).. what function do the GdiEndDocEMF() replace to eject all data from printer? how can i implement the maunal duplex feature in a print processor?? if you know, plz... let me know how to do or what to do.... thanks. wany. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72255
  - 11
    - How to open this transport address Hi, I have tried to open raw ip in kernel mode "\device\rawip\255" or "\device\rawip\17" (UDP) or "\device\rawip\1" (ICMP), all is OK, I can to use it for sending packets. Problem is that I need to open raw ip for TCP. When I am trying to open transport address with device name for TCP: "\device\rawip\6" ZwCreateFile() returns 0xC000000D. I am trying it with the same way like for above successful attempts, I pass only different device name. What is different in opening address for TCP ? Must be set some different object attributes or something other ? Peter Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72253
  - 12
    - getting serial.sys to work for an ISA based 4xserial port card to work I have an ISA based card with 4 serial standard serial ports(16550 type) that share an IRQ (using a cpld) that I would like to use with windows 2K. As far as I can understand it, i can use the driver included with windows (serial.sys) and I need to write a wrapper of some kind and an INF file. Is this a correct assumption ? Are there any links to information that more or less outline the steps to do something like this ? (as i have no prior experience with developing kernel mode drivers on microsoft platforms.) I would just like to estimate the difficulty of this job first, it seems to me that it should be fairly simple. Thanks very much, Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72250
  - 13
    - multicast ping My network driver supports multicast. I have tested with multicast applications and it works fine. But when I issue ping 224.0.0.1 from command prompt, it doesnt reply to that though it has joined the group already through ndis oids. I have tried setting IGMPLevel to 2 in registry. Will this work at all? I am testing on Windows2003 server. Should I tune in additional parameters? thanks sophia Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72246
  - 14
    - Capturing USB port data How can we capture USB interface data in WindowsXP? I want to verify the data transfered across the device and machine. If anyone of you have any utility, pls let me know. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72242
  - 15
    - Page limit when using GDI to print Although this is a client side issue, I believe the real issue is a buffering limit in the printer driver. Since our Unidrv-based printer driver is the first driver Iâ??ve ever worked on, I am curious if I am diagnosing this problem correctly and if I understand all possible solutions. We are experiencing a page limit when using GDI printing. After printing 85 pages from our application, we get a failure. We raised our Unidrv-based printer memory limit to 2 GByte maximum and printing fails consistently on the 86th page. This happens whether we print to an external printer or to our Unidrv-based software PDF printer, i.e. a printer that creates a PDF document. When we print from our application using GDI printing, the return value for the EndPage function for the 86th page is 0cFFFFFFFF, i.e. -1, and GetLastError returns 0 (zero). We then call AbortDoc. If I modify the code to allow printing to continue, only the first 85 pages are printed. The same thing happens on an external printer. Note, we do not believe that any pages approach the 350 MByte limitation mentioned in the documentation. Also, if we delete pages at the beginning of the document, then the document will still print only 85 pages, i.e. some pages that previously didnâ??t print suddenly print. Is the only solution to reduce the color-depth the 24 bit color images ouor application produces, and of course, greatly reduce the size of the images for gray scale or black and white printing? Then Ican modify the device context to reduce the memory requirements for each page. Is there anything else I can do? If that is the solution, do printers typically use 16 bit color, 8 bit color, or something else? We do need to be able to print photographs to high quality printers, but the buik what our application deals with is black and white documents. If those documents contain a color photograph we do want to support printing that without such a small page limit. We've heard of customer documents that exceeded 4000 pages! (Granted, these are quite rare, but 1000 pages is no unheard of). Thanks in advance. P.S. Our printer driver is a Unidrv-based PDF printer driver, i.e. it produces PDF files. It was built using DDK 3790. We support Windows 2000 and Windows XP. It was developed using the Unidrv sample code provided in the DDK. The printer-generated PDF file is sent to an application we also have developed, i.e. there is no hardware printer. ------------------------------------------------------------------------- I posted the message above in the win32.programmer.gdi newsgroup in a post titled "Page limit when using GDI printing.", and I received the reply below from Rhett Gong [MSFT]: Note however, despite his reply, that this is NOT just a Unidrv issue. It happens when using GDI to print to other printers. I responded in that forum, and included the calculation that shows that 2 GBytes will handle 85 8.5 inch by 11 inch 300 DPI 24 bit color images. (2 to the power 31) / ( (300 DPI * 8.5 I) * ( 300 DPI * 11.0 I) * 24 bits/pixel) ) = 85.0 This is what makes me believe the page limit is related to buffering in the driver (or at least buffering somewhere). The issue is that printing doesn't start until EndDoc() is called. Is it reasonable to raise the driver buffering way above the virtual memory limit? Is this data all mapped to a file? I do not want to segement a 1000 page print job into multiple jobs as these arrive back asynchronously from the Unidrv printer and are loaded into our application. Having to append these over and over again would annoy most users. Note also, there are two separate issues. 1. GDI to other printers. 2. GDI to our Unidrv-based printer. A solution to either of these would be useful. Is this a fundamental limitation of GDI printing? (An answer to that would help me to stop pursuing something with no solution). ------------------------------------------------------------------------- Hello From your description, you write a Unidrv by yourself, but you can only print 86 pages and then EndPage return -1 and not further error code returned . Based on my understanding, this is a Printer Driver issue and require debugging into the printer driver to find out the problem, so I would suggest you post this question to following newsgroup: microsoft.public.development.device.drivers It is a managed newsgroup. and all DDK issues and driver dev questions are posted in the newsgroup above. The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who the newsgroups regularly can either share their knowledge or learn from your interaction with us. Also, this is to make sure that the responders can better track the problem. Thank you, Rhett Gong [MSFT] Microsoft Online Partner Support Get Secure! - www.microsoft.com/security http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn This posting is provided "AS IS" with no warranties and confers no rights. -- You''''re unique, just like everyone else. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72236
  - 16
    - Synchronizing Timers and ISR I am attempting to synchronize Timer procedures with the ISR. When my timer expires it should perform operation A. If the ISR runs prior to that it will perform operation B and cancel the timer. What I am concerned about is the possiblity that the timer will expire, start executing, and get interrupted prior to reaching the Critical Section. In this scenario, Operation B will be performed by the ISR followed by Operation A by the timer. Is there a method to prevent this from happening? Thank you. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72229
  - 17
    - sqrt() cos() sin() in kernel mode Hello All, I need to perform some calculations in my driver, and I need to call some advanced math functions like sqrt(), cos() and sin()... I'd like to know if this is possible ? How to do that ? if these functions aren't available, can I call them from the user-mode ? Thanks for your help ! Eric. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72222
  - 18
    - Windows DDK Suite 3.0 hi,, all... i'm new here... i'm trying to make an application such as magictune of portrait displays... i plant a micro controller in the display.. that is configured i2c slave device.. connect pin 12, 15 of vga cable to the mcu.. i'm trying to send some simple data to the mcu... i'm using vc++ 6.0 i found that i need video.h from msdn.. so,, i got windows ddk suite 3.0 and installed it.. the header file, video.h is in C:\WINDDK\3790\inc\ddk\wxp and in vc++ 6.0,, tools -> options..., directories tab.. i put above directory in the list of "include files" section.. then i put // some header files #include <video.h> // some header files and tried to compile.. then i got 102 errors that all of them came from video.h and videoagp.h that are newly included headers.. did i do something wrong to configure building environment? is there some special thing to do in order to compile ddk headers? thank you very much... best regards, /u --------------- --------------------Configuration: VWCtrl - Win32 Debug-------------------- Compiling... VWCtrlDlg.cpp c:\winddk\3790\inc\ddk\wxp\videoagp.h(35) : error C2065: 'PAGP_RESERVE_PHYSICAL' : undeclared identifier c:\winddk\3790\inc\ddk\wxp\videoagp.h(35) : error C2100: illegal indirection c:\winddk\3790\inc\ddk\wxp\videoagp.h(35) : error C2501: 'PHYSICAL_ADDRESS' : missing storage-class or type specifiers c:\winddk\3790\inc\ddk\wxp\videoagp.h(35) : error C2143: syntax error : missing ';' before '(' c:\winddk\3790\inc\ddk\wxp\videoagp.h(36) : error C2226: syntax error : unexpected type 'PVOID' c:\winddk\3790\inc\ddk\wxp\videoagp.h(40) : error C2059: syntax error : ')' . . . c:\winddk\3790\inc\ddk\wxp\video.h(1500) : error C2146: syntax error : missing ';' before identifier 'InterfaceReference' c:\winddk\3790\inc\ddk\wxp\video.h(1500) : error C2501: 'PINTERFACE_REFERENCE' : missing storage-class or type specifiers c:\winddk\3790\inc\ddk\wxp\video.h(1500) : fatal error C1003: error count exceeds 100; stopping compilation Error executing cl.exe. VWCtrl.exe - 102 error(s), 0 warning(s) --------------- Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72220
  - 19
    - Correct DDK Windows 2000 SP4 I have Visual Studio 6, my O.S. is Windows 2000 SP4. According to the MSDN order site the correct DDK for my system is the Windows Server 2003 SP1 DDK, which I ordered. My main interest in the DDK was to obtain the Usbview,c source code, however Usbview.c will not compile on my system, it generates errors. I have been told by a systems developer that I need the 'Windows 2000 DDK' in order to compile Usbview.c on my system. The 'Windows 2000 DDK' is now only available to MSDN subscribers and I am not yet an MSDN subscriber. If the above infromation is correct, can anyone here on the forum who has the Windows 2000 DDK post back with the year(s) and month(s) of the MSDN subscription CD that included the DDK. Thank you for your help. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72217
  - 20
    - Migrating from KS1.0 (stream.sys) to AVStream Hi, When I have the sources of a driver that currently uses KS1.0 (stream.sys) is it difficult to rewrite the driver so that it uses AVStream instead? What would be a good starting point of rewriting the driver? Does it also effect the application that I'm currently using or do I need to rewrite the application as well? Avi Cohen Stuart. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72214
  - 21
    - Problems performing USB Isochronous/Bulk Read/Writes and unplugging device Hello all, hello Mr. Roberts! After clearing some general misunderstandings, maybe you could help me once more with the second part of my former post. I would be very grateful for your assistance. I described it as follows: >Depending on the pipe type I leave the dispatch routine forwarding the >current Irp and device object to a validation routine for isochronous >transfers (because they are more complicated) or bulk transfer >completion routine. Isochronous completion is done as it can be seen >the original sample. Microsoft did in their samples the validation for >isochronous and both validation and transaction in the case of bulk >transfers in the dispatch routine. Although I copied and pasted the >whole algorithm from their (fine-working [standalone]) drivers, the system >crashes when I try to perform a bulk/isochronous read or write. What >rule did I violate? Moreover I recognized the same crash behaviour when I unplug one or both devices. I tried to get some debugging messages via DbgView from Sysinternals, but the system crashes, without storing the information into the given log file. I checked the in- and decrements on the stack without result. They seem okay to me. Since I solely introduced the validation routine for isochronous transfer and sourced the transfer algorithm of the bulk transmission out, I assume it must have something to do with the parameters I forward to these functions. I appreciate your help in advance, special thanks to Mr. Roberts who helped me this far. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72211
  - 22
    - NDIS driver sample code for SDIO interface Hi, I am developing a SDIO driver for our chipset. The output from our chipset is IP datagram carry realtime video. I need to give the IP datagram to the NDIS protocol stack then pass to Windows CE media player does anybody have any NDIS example for WinCE I can follow? I understand how to transfer data via SDIO interface the experience I am lacking is after I get the data how do I pass to upper layer protocol stack (NDIS) so when user want to watch live TV using windows media player they can do it. It should be similar to 802.11 just the out put from our chipset is IP packets not Ethernet packet Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72209
  - 23
    - how do i: import from another loaded driver I am writing a miniport driver for the SMBus class driver. I need to call a function defined in SMBClass.sys. The function is defined in SMB.h, I get link errors, so I thought I could load it dymanically, bu LoadLibrary dosen't seem to be useable in kernal mode. How do I call functions in the class driver from my miniport driver? TIA Ryan Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72202
  - 24
    - SMART_GET_VERSION returns ERROR_INVALID_FUNCTION On Windows XP the SMART_GET_VERSION code for PhysicalDrive0 (a SATA drive) works. On Windows 2003 Server SP1, the same code fails with ERROR_INVALID_FUNCTION. I've searched the DDK and knowledgebase without any luck of finding the necessary information. Why does the code fail? I've found a workaround using SCSI_MINIPORT and \\.\scsi0 device name. Please see below. sprintf(devcName, "\\\\.\\PhysicalDrive%u", deviceId); devcHndl = CreateFile (devcName, GENERIC_READ|GENERIC_WRITE, FILE_SHARE_READ|FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL); if (devcHndl == INVALID_HANDLE_VALUE) { printf("cannot open device %s error %d\n", devcName, GetLastError()); } retVal = DeviceIoControl(devcHndl, SMART_GET_VERSION, NULL, 0, &versionInfo, sizeof(GETVERSIONINPARAMS), &retSize, 0); if (retVal) printf ( "Device........... %s\n" "Driver version... %1d\n" "Revision......... %1d\n" "Device map....... 0x%02x\n" "Capabilities......0x%02x\n", devcName, versionInfo.bVersion, versionInfo.bRevision, versionInfo.bIDEDeviceMap, versionInfo.fCapabilities); else printf("DeviceIoControl (SMART_GET_VERSION) for %s error %d\n", devcName, GetLastError ()); CloseHandle(devcHndl); Workaround: sprintf(devcName, "\\\\.\\scsi%u:", controllerId); devcHndl = CreateFileA (devcName, GENERIC_READ|GENERIC_WRITE, FILE_SHARE_READ|FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL ); if (devcHndl == INVALID_HANDLE_VALUE) { printf("cannot open device %s error %d\n", devcName, GetLastError()); } PSENDCMDINPARAMS cmdIn = (PSENDCMDINPARAMS )&iobuff.cmdBuff; memset(&iobuff, 0, sizeof(iobuff)); cmdIn->cBufferSize = 0; cmdIn->bBuffer[0] = 0; cmdIn->bDriveNumber = (BYTE) deviceId; //For IDE: 0=master; 1=slave; actual ID for SCSI iobuff.srbCtrl.ControlCode = IOCTL_SCSI_MINIPORT_SMART_VERSION; iobuff.srbCtrl.Length = sizeof(iobuff.cmdBuff); iobuff.srbCtrl.HeaderLength = sizeof(SRB_IO_CONTROL); iobuff.srbCtrl.Timeout = 1000; memcpy(iobuff.srbCtrl.Signature, "SCSIDISK", sizeof(iobuff.srbCtrl.Signature)); retVal = DeviceIoControl(devcHndl, IOCTL_SCSI_MINIPORT, &iobuff, sizeof(iobuff), &iobuff, sizeof(iobuff), &retSize, 0); if (retVal) { versionInfo = (GETVERSIONINPARAMS *) iobuff.cmdBuff; printf ( "Controller........... %s\n" "Device........... %1d\n" "Driver version... %1d\n" "Revision......... %1d\n" "Device map....... 0x%02x\n" "Capabilities......0x%02x\n", devcName, deviceId, versionInfo->bVersion, versionInfo->bRevision, versionInfo->bIDEDeviceMap, versionInfo->fCapabilities); } else printf("DeviceIoControl (IOCTL_SCSI_MINIPORT) for %d error %d\n", controllerId, GetLastError ()); Thank you in advance. Regards, Mik Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72200
  - 25
    - NDISProtocol Driver for PPP (WinCE 4.2/5.0) has anybody developed a NDISProtocol Driver for WinCE 4.2/5.0??? I've done all the proper step to bind to the PPP but yet when I send the packet to PPP I never receive the call back... I'm thinking there is issue with the way I bind or do OpenAdapter... is there specific steps I should take? could somebody point out a guideline?? would appreciate it... Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72193
- Next
  - 1
    - Should UsbIntel driver go to D3 or D0 inIdleNotificationRequestComplete We are making USB image capture device with a driver like UsbIntel. I added IdleNotification routine to the driver. A PC pluged in our device wasn't able to suspend sometimes. My attention is in PoRequestPowerIrp call of IdleNotificationRequestComplete. Now our driver code is as below. powerState.DeviceState = PowerDeviceD0; PoRequestPowerIrp( ... IRP_MN_SET_POWER, powerState, ... ); When I delete this function call PoRequestPowerIrp, A PC pluged in our device was able to suspend always. But My device power is still off. In IdleNotificationRequestComplete I must know whether our driver should go to D3 or D0. Please help me. Thanks in Advance, shinji Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72188
  - 2
    - BSOD in stream.sys bugcheck with Margi DVD-to-GO Hi, I'm running into a bugheck in stream.sys when using the Margi DVD-to-Go. windbg gave me the following analysis: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 00000010, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: fa48b018, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 00000010 CURRENT_IRQL: 2 FAULTING_IP: STREAM!SCProcessCompletedDataRequest+e6 fa48b018 8b4010 mov eax,[eax+0x10] DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from fa48acf3 to fa48b018 TRAP_FRAME: f9023d24 -- (.trap fffffffff9023d24) ErrCode = 00000000 eax=00000000 ebx=ff96cd98 ecx=02440000 edx=00000000 esi=ff9d77e8 edi=00000000 eip=fa48b018 esp=f9023d98 ebp=f9023dac iopl=0 nv up ei pl zr na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 STREAM!SCProcessCompletedDataRequest+0xe6: fa48b018 8b4010 mov eax,[eax+0x10] ds:0023:00000010=???????? Resetting default scope STACK_TEXT: f9023dac fa48acf3 00000004 ff9d4ac8 ff96b0e8 STREAM!SCProcessCompletedDataRequest+0xe6 f9023dc0 fa48b2de ff9d77e8 ff96b0e8 ff96b1c0 STREAM!SCCallBackSrb+0x43 f9023e94 fa48b5d0 00000000 ff96b030 00000000 STREAM!StreamClassDpc+0xc2 f9023eb4 8043185f ff96b154 ff96b0e8 74a5e210 STREAM!SCMinidriverDeviceTimerDpc+0x48 f9023fb4 80431770 dd4cae90 00000010 ffdff000 nt!KiTimerListExpire+0xe7 f9023fe0 80464437 80480f60 00000000 000b0951 nt!KiTimerExpiration+0xb4 f9023ff4 80468e1a fa69db6c 00000000 00000000 nt!KiRetireDpcList+0x30 f9023ff8 fa69db6c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a WARNING: Frame IP not in any known module. Following frames may be wrong. 80468e1a 00000000 00000008 bb835275 00000128 0xfa69db6c FOLLOWUP_IP: STREAM!SCProcessCompletedDataRequest+e6 fa48b018 8b4010 mov eax,[eax+0x10] SYMBOL_STACK_INDEX: 0 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: STREAM!SCProcessCompletedDataRequest+e6 MODULE_NAME: STREAM IMAGE_NAME: STREAM.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 41107d3e STACK_COMMAND: .trap fffffffff9023d24 ; kb FAILURE_BUCKET_ID: 0xD1_VRF_STREAM!SCProcessCompletedDataRequest+e6 BUCKET_ID: 0xD1_VRF_STREAM!SCProcessCompletedDataRequest+e6 Followup: MachineOwner --------- After some more analysis using IDA Pro on the stream.sys I came to the following: The function STREAM!SCProcessCompletedDataRequest() takes a PHW_STREAM_REQUEST_BLOCK as its parameter. For this particular pSRB the following values were found: ff9d77e8 00 0000004c SIzeOf ThisPacket ff9d77ec 04 00000001 Command: SRB_WRITE_DATA ff9d77f0 08 00000000 Status ff9d77f4 0c ff9d4b70 HW_STREAM_OBJECT ff9d77f8 10 ff96b32c HWDeviceExtension ff9d77fc 14 ff9d7890 SRBExtention ff9d7800 18 ff96cd68 CommandData ff9d7804 1C 00000001 NumberOfBuffers ff9d7808 20 0000000e TimeoutCounter ff9d780c 24 0000000f TimeoutOriginal ff9d7810 28 00000000 nextSRB ff9d7814 2c fc570f48 IRP ff9d7818 30 00000003 Flags ff9d781c 34 ffa29e74 HwInstanceExtension ff9d7820 38 0000000f NumberBytesToTransfer ff9d7824 3C ff9d78f0 ScatterGatterBuffer ff9d7828 40 00000000 NumberOfPhysicalPages ff9d782c 44 00000000 NumberOfScatterGatterElements Particulary the IRP is interesting when using !ipr the following is displayed: kd> !irp fc570f48 1 Irp is active with 2 stacks 4 is current (= 00000000) Mdl = ffa7e4c8 System buffer = ff96cd68 Thread ff9982f4: Irp is completed. Pending has been returned Flags = 40000030 ThreadListEntry.Flink = ff9984cc ThreadListEntry.Blink = fdd3af58 IoStatus.Status = 00000000 IoStatus.Information = 00000000 RequestorMode = 00000001 Cancel = 00 CancelIrql = 0 ApcEnvironment = 00 UserIosb = 0170f3d4 UserEvent = ff9284a0 Overlay.AsynchronousParameters.UserApcRoutine = 00000000 Overlay.AsynchronousParameters.UserApcContext = 0170f3d4 Overlay.AllocationSize = 0170f3d4 - 00000000 CancelRoutine = 00000000 UserBuffer = 0170bcc0 &Tail.Overlay.DeviceQueueEntry = 00eecf6c Tail.Overlay.Thread = ff9982f4 Tail.Overlay.AuxiliaryBuffer = 8042398a Tail.Overlay.ListEntry.Flink = 804ac282 Tail.Overlay.ListEntry.Blink = 00000000 Tail.Overlay.CurrentStackLocation = 00000000 Tail.Overlay.OriginalFileObject = ff9bbe68 Tail.Apc = 00300012 Tail.CompletionKey = 00300012 cmd flg cl Device File Completion-Context [ 0, 0] 0 0 00000000 00000000 00000000-00000000 Args: 00000000 00000000 00000000 00000000 [ e, 0] 0 10 ff96b030 00000000 00000000-00000000 \Driver\mdvdwdm Args: 00000000 00000000 00000000 00000000 When the trap occurs eax is NULL and [eax+0x10] is being accessed. When disassembling the function using IDA Pro, eax should point to the Tail.Overlay.CurrentStackLocation which happens to be NULL. The actual trap occurs because [eax0x10] points to Tail.Overlay.CurrentStackLocation that appears to be NULL. The strange thing is that I don't see a '>' pointed before any of the cmd. I don't know if this is a bug in stream.sys or in the mdvdwdm (the Margi driver) I have the sources for the Margi driver but I've no idea where to look from here. Any clues are welcome. (Crashes happen during DVD play...) (Part of the !process dump of DVDPlay.exe) THREAD ff9982c0 Cid 2fc.16c Teb: 7ffd4000 Win32Thread: 00000000 RUNNING IRP List: fe0d2f48: (0006,00b8) Flags: 40000030 Mdl: ff926268 fdfa4f48: (0006,00b8) Flags: 40000030 Mdl: ff98b0c8 fe0a4f48: (0006,00b8) Flags: 40000030 Mdl: ff97d508 fc55ef48: (0006,00b8) Flags: 40000030 Mdl: ff979208 fe056f48: (0006,00b8) Flags: 40000030 Mdl: ff9dbbc8 fdc76f48: (0006,00b8) Flags: 40000030 Mdl: ff971688 fe096f48: (0006,00b8) Flags: 40000030 Mdl: ff925f88 fdd60f48: (0006,00b8) Flags: 40000030 Mdl: ff9a22c8 fd30ef48: (0006,00b8) Flags: 40000030 Mdl: ff928108 fde54f48: (0006,00b8) Flags: 40000030 Mdl: ffa192a8 fdfaaf48: (0006,00b8) Flags: 40000030 Mdl: ff9a2968 fe018f48: (0006,00b8) Flags: 40000030 Mdl: ff921f88 fc818f48: (0006,00b8) Flags: 40000030 Mdl: ffaa6508 fdf9cf48: (0006,00b8) Flags: 40000030 Mdl: ff9998c8 fdcf0f48: (0006,00b8) Flags: 40000030 Mdl: ffa386e8 fdc00f48: (0006,00b8) Flags: 40000030 Mdl: ff9a8a68 fdca2f48: (0006,00b8) Flags: 40000030 Mdl: ff9a82a8 Not impersonating Owning Process ffa363c0 Wait Start TickCount 723281 Elapsed Ticks: 0 Context Switch Count 460027 UserTime 0:00:03.0846 KernelTime 0:00:15.0454 Start Address KERNEL32!BaseThreadStartThunk (0x7c57b700) Win32 Start Address qdvd!COutputQueue::InitialThreadProc (0x1c25060d) Stack Init fa69e000 Current fa69dca0 Base fa69e000 Limit fa69b000 Call 0 Priority 11 BasePriority 8 PriorityDecrement 0 DecrementCount 0 ChildEBP RetAddr Args to Child f9023d24 fa48b018 ff9bbe68 00000000 00000000 nt!KiTrap0E+0x20b f9023dac fa48acf3 00000004 ff9d4ac8 ff96b0e8 STREAM!SCProcessCompletedDataRequest+0xe6 f9023dc0 fa48b2de ff9d77e8 ff96b0e8 ff96b1c0 STREAM!SCCallBackSrb+0x43 f9023e94 fa48b5d0 00000000 ff96b030 00000000 STREAM!StreamClassDpc+0xc2 f9023eb4 8043185f ff96b154 ff96b0e8 74a5e210 STREAM!SCMinidriverDeviceTimerDpc+0x48 f9023fb4 80431770 dd4cae90 00000010 ffdff000 nt!KiTimerListExpire+0xe7 f9023fe0 80464437 80480f60 00000000 000b0951 nt!KiTimerExpiration+0xb4 f9023ff4 80468e1a fa69db6c 00000000 00000000 nt!KiRetireDpcList+0x30 f9023ff8 fa69db6c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a 80468e1a 00000000 00000008 bb835275 00000128 +0xfa69db6c Avi Cohen Stuart Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72187
  - 3
    - Supporting IAMStreamConfig with AVStream I'm just getting started on an AVStream driver and would like to support the IAMStreamConfig interface for the purpose of getting and setting the data format (framerate, size, etc.). Which property set must be supported for this? Also, will supporting this interface result in the Video Format tab of the pin properties being activated? (Don't worry, I'm not going to leave the default property pages in my final version, but I'd like to get them working for now.) Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72186
  - 4
    - Install IFS kit on XP x64 Hi all I'm trying to install the Windows Server 2003 IFS Dev Kit onto my XP x64 machine, but I keep getting an error when running setup : "Kitsetup.exe - Entry Point Not Found" "The procedure entry point ??3@YAXPAX@Z could not be located in the dynamic link library msvcrt.dll" I've managed to install the IFS kit on an XP X86 machine without any issues. Has anyone else come across this problem before ? Anyone know hot to get around it ? Cheers Ged Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72185
  - 5
    - oryginal name of the device Hi. Can you tell me, please, how to get device's oryginal name. The name that is assigned during PnP enumeration. E.g.: After I plug FM801 PCI joystick, I see such in the Device Manager and in the registers. When I install some driver to it, I see only new name. I tried a lot with SetupDi functions but I could not get the oryginal value. I thought that getting devices SPDRP_FRIENDLYNAME property will solve the problem but in most cases this call fails. When I was testing WInDriver, I saw that this tool can see oryginal name of the device. Thanks in advance, Grzegorz Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72181
  - 6
    - ICD DDK Hi all, I am looking for the ICD DDK. Does someone know where to order or download it? best regards Christian Hartig Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72180
  - 7
    - Multiple virtual COM ports. Hi All, We use a CDC device implementation( modem), and is making use of usbser.sys as the communication driver. As per our requirement we need to emulate multiple virtual COM ports over the usb. (usbser emulates only 1 com port). Is there a way,by which I could emulate multiple COM ports,using USBSER.ie can I add an upper filter to usbser,wherein I create multiple com ports.Does usbser supports this. Plz help .................. Thanks in Advance, Teena. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72177
  - 8
    - Where can I get SMBClass.sys? I am writing a SMBus miniport driver for the MS SMBus class driver. I discovered that I don't have the SMBClass.sys file anywhere on my laptop. Any idea where I can find it and install it? TIA, -- Ryan Abrahamson, MCSD.NET Sr Consultant Magenic Technologies MS Gold Certified Partner Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72164
  - 9
    - Print a text string that uses True type font I need to convert True Type Font (TTF) to bitmap and then download it to the printer. Our printer drivers are a plug-in to minidrivers (PScript, UniDrv). Is there any documentation available that will help me accomplish the task? EngTextOut(...) is one API that I have in my mind but it requires surface, string, font object, How should I create or get these objects? Best Regards, Athar Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72161
  - 10
    - One shot capture gives wrong DX GetStatus When I start capturing in DX with just DSCBSTATUS_CAPTURING (no |DSCBSTATUS_LOOPING) the GetStatus function is still coming back with the DSCBSTART_LOOPING state. I based the driver initially from the MSVAD sample and I am not clear where this distinction in startup lies. If you have an pointers as to were I could look to fix this I would greatly appreciate it. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72159
  - 11
    - Help me for driver in Vista Windows Hello, thanks for answering to my question : I installed Windows Vista, but I have two problems, with my sound card, and with my modem. Both doesn't work by default and I had no problem with them before in Win XP.. Maybe someone knows, how to install XP drivers, or where to find drivers for Windows Vista? My sound card : Creative AudioPCI My modem: Rockwell HCF V92 56K Speakerphone PCI Modem Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72158
  - 12
    - HPET support 1) Does Windows XP provide any support for accessing/using the High Performace Event Timers (HPET) in the chipset? 2) Will Windoes Vista use the HPET for QueryPerformanceCounter (both uni and multi-processor HALs)? 3) Does the Windows DDK offer any guidance on writing a driver for the HPET? I ask these questions because I'm looking for a high resolution timing solution to monitor performance of a multimedia app. I need a consistant, reliable timing base to compare against. 1ms resolution is not enough for my particular application. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72157
  - 13
    - Using NDL/NDIS in winCE driver Does any one know a documentation describing "NDL" in windows CE? I am trying to write an NDIS driver for SDIO device. I have looked at a dll from "Ambicom" and it had the fallowing exporter functions: DriverEntry NDL_Init NDL_Deinit NDL_Open NDL_Close NDL_Read NDL_Write NDL_Seek NDL_IOControl NDL_PowerDown NDL_PowerUp Does any one know how it is associated to NDIS? Thanks. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72153
  - 14
    - Slipstreaming Device Drivers into a WIN2K3 installation I hope this topic is not to far from the purpose of this newsgroup. I am trying to install WIN2K3 on a new Dell 850 Server. I opted to buy an Adaptec SATA controller for $100 instead of Dell's for $400, but it may now be coming back to haunt me. The Dell Server Manager CD does not recognize the controller and I have been unable to get the drivers for this controller installed as the 850 does not support a Floppy drive. Can anyone point me in the direction of a good resource for slipstreaming drivers into a Win2k3 installation? Thanks Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72152
  - 15
    - Bulk and Iso-Transfers in one USB-Driver Hi all, I'm searching a reliable way to detect the pipe type of an IRP. I tried to read this information like Microsoft did in their Bulk Driver Sample from the DDK. In the dispatch routine I check for upcoming idle requests. Then I get the current Irp, the current file object, the pipe information and that's where I get the current pipe type from. I understood that every IRP stores information about what transfer type is at hand. Is that right? Depending on the pipe type I leave the dispatch routine forwarding the current Irp and device object to a validation routine for isochronous transfers (because they are more complicated) or bulk transfer completion routine. Isochronous completion is done as it can be seen the original sample. Microsoft did in their samples the validation for isochronous and both validation and transaction in the case of bulk transfers in the dispatch routine. Although I copied and pasted the whole algorithm from their (fine-working single) drivers, the system crashes when I try to perform a bulk/isochronous read or write. What rule did I violate? I'm through with W. Oneys book and the USB specification and the firmware and the application. Although this work is part of my internship and I'm (quite) new to this field I'm seriously trying to get the best out of my work. I appreciate your ideas very, very much! Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72150
  - 16
    - DeviceIoControl() in WinCE Hi, I am writing a driver which takes in the call to DeviceIoControl() some structure like below: stuct someStruct { char *in_ptr; int in_ptr_len; int num; char *out_ptr; int out_ptr_len; } where ptr points to some memory. Problem is that DeviceIoControl() just seems to take a pointer to a buffer (in_ptr and out_ptr), so if now I passed address of an object of someStruct type, the how can I access data pointed to by ptr member from inside my driver? Also is it possible that i allocate memory pointed to by out_ptr in my driver and still I can access the memory from my application that opens that driver? I am using Pocker PC 2003. Thanks, Arsalan Thanks, Arsalan Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72149
  - 17
    - Adding USB to BDA Driver Linking ERROR! Hi All, I adding USB interface to BDA Driver but Linking ERROR! Below is my sources from DDK BDA samples IF 0 Copyright (C) Microsoft Corporation, 1999 - 1999 Module Name: sources. !ENDIF MAJORCOMP=ntos MINORCOMP=dd TARGETNAME=BDACap TARGETPATH=obj TARGETTYPE=DRIVER TARGETLIBS=$(DDK_LIB_PATH)\ks.lib \ $(DDK_LIB_PATH)\usbd.lib INCLUDES=$(DDK_INC_PATH);$(SDK_PATH)\AMovie\Inc DRIVERTYPE=WDM MSC_WARNING_LEVEL=/W3 /WX C_DEFINES=$(C_DEFINES) -DUNICODE -D_UNICODE -DDEBUG_LEVEL=DEBUGLVL_BLAB -DDRIVER BROWSER_INFO=1 USE_MAPSYM=1 LINKER_FLAGS =$(LINKER_FLAGS) -map -merge:PAGECONST=PAGE SOURCES=\ $(TARGETNAME).rc \ device.cpp \ filter.cpp \ TStream.cpp \ capture.cpp \ hwsim.cpp MISCFILES=\ bdacap.inf \ BdaSWRcv.inf I Adding this line <<$(DDK_LIB_PATH)\usbd.lib>> for link USBD_XXX founction but still appear the unresolved external symbol USBD_CreateConfigurationRequestEx Why! Anybody can help me! Thanks! Eric Lu Averlogic Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72145
  - 18
    - DriverDateData and others.... Hi, Where do "DriverDateData" and "DriverDate" come from in my device's registry key? I see it in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\xxxx" Thanks, Sushrut. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72141
  - 19
    - Possible to write data to SMBIOS from ACPI operation region?? I have been reading the docs on ACPI operation regions and it seems that these regions are only useful for getting data from the BIOS, is this true? I have a need to access an SMBIOS interface which requires punching a physical address into a CPU register directly and then writing an I/O port. I was wondering if this interface could be converted to an ACPI op region and avoid all of the non-standard, non-WHQL approved kernel calls that are necessary to make this work? I notice that their are two access types listed for these regions "cooked" and "raw". The latest docs say "raw" access isn't implemented yet. I am guessing this is what would be needed for this type of interface yes? Originally, I was hoping that ACPI op region buffers were shared between BIOS and ACPI op region registrars, but it appears that the data flow is only one way, yes? Any pointers on how these op regions work and even better how an SMBIOS interface such as this could be accessed in a cleaner fashion would be much appreciated. BTW, for the sake of discussion assume I can modify the BIOS at will. Bill M. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72140
  - 20
    - How to use COM in Filter Driver. Hi, I want to use COM say IStorage in one of my filter driver, is there any way of implementing existing COM interfaces in drivers. Thanks & Regards, YASH Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72137
  - 21
    - CDC interface for Composite (USB) device Hello Everyone, We have a composite USB device which contains a Line device (PSTN line) and Telephone device. Each of these two device have two audio interfaces. I want to expose to Windows my composite device as Two communication class devices - a) Line device (like a Modem) and b) Phone Device (CDC spec - Telephone control model). a) I would like to know if Usbser.sys will support this or do I have to write my own driver? b) Also what are minimum interfaces required by usbser.sys? Thank you, Harish Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72130
  - 22
    - Hibernation problem for USB device without ROM firmware We make use of a USB device that gets its identity changed dynamically after the firmware is downloaded by our driver. The device has a unique VID and PID that is used for the two sets of drivers. The first VID & PID are burned into the ROM and it is not the USB chip manufacturer's VID/PID. I have searched through the archives and found a similar issue discussed along with a workaround suggested by Microsoft. (Attached below) Our device is not quite as schizophrenic since it has our own VID/PID before the downloading of firmware. Anyway, I preferred to test the second design for hibernation so I created a compound device with a hub. I installed a lower filter driver to our hub and tried to download the firmware during power up, but I found that the request (IOCTL_INTERNAL_USB_SUBMIT_URB with URB_FUNCTION_VENDOR_DEVICE) fails with STATUS_DEVICE_POWERED_OFF when I download the firmware before calling PoCallDriver (this is an experiment and what I expected). Also I get STATUS_DEVICE_NOT_CONNECTED when I download the firmware after PoCallDriver and this is not what I expected. It seems to me from my experimentation that this is not a realizable solution. I realize this suggestion was made "AS IS", but I was wondering if the concepts have ever been tested or what I might be missing? --- the following is the workaround --- Newsgroups: microsoft.public.development.device.drivers From: "Eliyas Yakub" <eliy...@microsoft.com> - Find messages by this author Date: Wed, 22 May 2002 12:16:04 -0700 Local: Wed, May 22 2002 3:16 pm Subject: Issues with schizophrenic devices (fyi) Reply to Author | Forward | Print | Individual Message | Show original | Report Abuse I brought to our PNP developer's attention nasty driver design issues people are running into with reprogrammable PCI (FPGA/DSP) and USB devices. We saw couple of those in recent days (Triggering a PCI bus re-scan) in this forum. Here is his response: ********************** Our customer needs to be warned that this type of hardware may not be productizable. The design (a reprogammable PCI FPGA chip that disappears and reappears as another device) is similar to some of the USB programmable DSP designs we've also seen problems with. Both of these designs run into major problems with PnP and Power Management. Problems -------- Identification - In its default state, the device usually exposes generic "DSP/FGPA" IDs. An INF targets those IDs and specifies a driver that'll transform the hardware into something else. If two different hardware vendors each use the same reprogrammable chip, their INFs will both match against the same DSP/FGPA IDs. The OS doesn't know which driver to pick. Even better, insert a card from each vendor - mayhem ensues as one of the cards will get the wrong payload. Power Management - During power management operations (hibernation, suspend, etc), all power is often removed from the chip. When this happens, the chip typically loses its new identity and reverts back to its DSP/FPGA form. To the OS, this appears to be a surprise removal (the card disappeared). All the handles opened by applications against the device will go dead. The application might reestablish contact when the original device appears to be "reinserted", ie the load sequence has repeated, but there is no gaurantee of this. Plug and Play - Some Plug and Play operations may result in power loss (rebalance), leading to the problem above. Updating the driver also temporarily places the hardware in D3. Depending on the bus, this may result in a state loss, causing the device to "disappear" just as the OS is planning to reload the new drivers. A reboot popup may result from this. How To Make FGPA/Reprogrammable-DSP Designs Work ------------------------------------------------ The best designs simulate a bridge/hub with devices behind it. For instance, the following design of a PCI FGPA works properly with Windows: 1. The PCI FGPA simulates a PCI-to-PCI bridge. 2. The PCI FGPA logic retrieves the IDs for the bridge from an EEPROM, ensuring no possible overlap with other customers using the same chip (the IHV is expected to contact the PCI SIG and retrieve such IDs.) 3. The INF for the FGPA specifies PCI.SYS as the FDO (using NEEDS and INCLUDE directives to reference machine.inf as needed), and specifies a lower filter driver that will deliver the payload. 4. During IRP_MN_START_DEVICE, the filter driver downloads the payload to the FPGA. The FPGA now appears as a bridge (same IDs) with a *child* behind it. The child represents the IHV's device. 5. After start, the OS enumerates the bridge. Since the child is present, the OS loads the next set of drivers. 6. During powerup from suspend or hibernation, the OS first powers up the bridge. The filter driver takes this opportunity to reapply the payload if necessary. Here is a similar design for a reprogrammable USB chip: 1. The USB chip simulates a hub. 2. The USB chip retrieves the Vid/Pid IDs for the hub from an EEPROM 3. The INF specifies USBHUB.SYS using NEEDS and INCLUDE directives targeting USB.INF. The INF also specifies a special lower filter driver to download the payload. 4. During IRP_MN_START_DEVICE, the filter programs the USB chip to appear as a hub with a device behind it. 5. After start, the OS enumerates the hub and discovers the child. 6. During powerup, the OS always powers up the hub before the child. The filter reapplies the payload during hub powerup. And another USB design: 1. The USB chip simulates a *composite* USB device. 2. The USB chip retrieves the Vid/Pid IDs for the hub from an EEPROM 3. The INF specifies USBGCCP.SYS via NEEDS and INCLUDE directives (similar to above). 4. During IRP_MN_START_DEVICE, USBGCCP will read descriptors from the hardware to determine which functions are exposed by the composite device. The driver (a lower filter) would reprogram the hardware to specify child during Start, before the IRP reached USBGCCP. 5. During powerup, the driver would reapply the payload as needed. -- -Eliyas This posting is provided "AS IS" with no warranties, and confers no rights. Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72127
  - 23
    - Supporting IAMStreamConfig with AVStream driver I'm just getting started on an AVStream driver and would like to support the IAMStreamConfig interface for the purpose of getting and setting the data format (framerate, size, etc.). Which property set must be supported for this? Also, will supporting this interface result in the Video Format tab of the pin properties being activated? (Don't worry, I'm not going to leave the default property pages in my final version, but I'd like to get them working for now.) Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72126
  - 24
    - printer port monitor question re: drag-n-drop install I've got a question about port monitors and drag-n-drop printer installation. When you drag a printer from a server to a workstation, what happens to the port monitor that the printer driver(on the server) is using? Fron the printers folder, clicking on the printer's Properties/Ports tab shows the printer on the workstation is using the same port as the printer on the server is using. However, if you do File/Server Properties from the printers folder and look at the ports tab, the port is nowhere to be seen. If it's a non-standard port monitor (ie, not included with windows), the port TYPE isn't even there. (and you can't configure the port) So what port is the workstation printer actually using? Is this documented anywhere? I am especially interested in any information regarding user-written port monitors in this situation. Thanks, ScottR -- Scott Robins Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72120
  - 25
    - Q: USB SCSI, announce media change? Ok, I couldn't find a better place to post this question, so here goes! I'm writing code for a device that exposes a removeable media drive. So far, no problems getting Windows to see the drive, notice that there's no media, etc. - however, when I change media Windows will redisplay the contents of the old media! I'm returning a CHECK_CONDITION with a sense code of 0x28 and a qualifier of 0x00 to TEST_UNIT_READY, which based on my reading of the SCSI spec should tell Windows that the media might have changed.. but Windows won't reread the device directory. Is there something else I should be returning here? TIA for any assistance, this is driving me nuts! Tag: Which type of driver should I develop to turn a file to a pesudo-d Tag: 72113

Hello, I am a beginner of driver development.

I want to create a pesudo-disk from a normal file.

Which type or types of driver should I develop?

I think I am getting lost in the driver stack for a disk.

Anyway, thank you for your idea in advance!

Top

Re: Which type of driver should I develop to turn a file to a pesudo-d by Don

Don
Mon Nov 21 07:14:49 CST 2005

Start with the disk class driver example in the DDK. There is a driver
source called filedisk out there that does this, unfortunately this is
stolen software so you not use it for anything real.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

"Ryan Yan" <Ryan Yan@discussions.microsoft.com> wrote in message
news:F5B0B3DB-DA77-4D11-8D5B-2710892681E1@microsoft.com...
> Hello, I am a beginner of driver development.
>
> I want to create a pesudo-disk from a normal file.
>
> Which type or types of driver should I develop?
>
> I think I am getting lost in the driver stack for a disk.
>
> Anyway, thank you for your idea in advance!

Top

Re: Which type of driver should I develop to turn a file to a pesu by RyanYan

RyanYan
Tue Nov 22 09:27:07 CST 2005

Thank you very much for giving me such a good guide!
I am deeply appreciated for your kindness!

"Don Burn" wrote:

> Start with the disk class driver example in the DDK. There is a driver
> source called filedisk out there that does this, unfortunately this is
> stolen software so you not use it for anything real.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
>
>
> "Ryan Yan" <Ryan Yan@discussions.microsoft.com> wrote in message
> news:F5B0B3DB-DA77-4D11-8D5B-2710892681E1@microsoft.com...
> > Hello, I am a beginner of driver development.
> >
> > I want to create a pesudo-disk from a normal file.
> >
> > Which type or types of driver should I develop?
> >
> > I think I am getting lost in the driver stack for a disk.
> >
> > Anyway, thank you for your idea in advance!
>
>
>

Top