Re: Unidrv Minidriver for Win 9x??
From: vipin aravind (vipin_at_nospam.com)
Date: 04/02/04
- Next message: vipin aravind: "Re: Can JOB_INFO_1 be accessed from Win98 UNIDRV-based driver?"
- Previous message: vipin aravind: "Re: Printer Driver: Save to PCL and EMF file."
- In reply to: Bobby Mattappally [MS]: "Re: Unidrv Minidriver for Win 9x??"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 2 Apr 2004 23:59:16 +0530
Use softice. Nice debugger.
vipin
"Bobby Mattappally [MS]" <bobbym@online.microsoft.com> wrote in message
news:SnBffxCGEHA.612@cpmsftngxa06.phx.gbl...
> Hi Sam,
> Is this an NT 4.0 driver?
> In NT, the rendering dll is run in kernel mode.
> So won't be able to debug it in usemode.
>
> --------------------
> From: "Sam" <anishsam@gnostice.com>
> Hi,
>
> Well, I am trying to create a virtual printer driver which will give me
the
> EMF file. I need to obtain the Metafile which is spooled. According to the
> reading that I've done, I have concluded that I'll need to write a Unidrv
> Minidriver for this, or a print processor (which will be more work). I was
> wondering if this will work for all platforms of Windows -
> 9X/ME/XP/NT/2K/etc. I guess I'll have to write different drivers for each
> platform, but based on the same technology - Unidrv Minidriver!!!!
>
> Are my assumptions right?
>
> Also, I'm having some trouble trying to debug and trace through the OEMDLL
> sample that comes with NTDDK. I created the checked build DLLs and
installed
> them. Then I opened WinDbg and attached to spoolsv.exe process.
>
> I've set the symbol path to windows 200 symbols and the OEMDLL's i386
> directory. These are my symbol paths I've set in WinDbg:
> C:\WinSymbols;C:\NTDDK\src\print\oemdll\i386;
>
> I've set the source path to:
> C:\NTDDK\src\print\oemdll\oemuni
>
> Then, I opened the "enable.cpp" and "dllentry.cpp" files using "Open
Source"
> menu option, and tried to set breakpoints. But it does not get set.
>
> When I invoke printing using WordPad, control comes to WinDbg, and I press
> F10 (Step Over) to go step by step. But the control never comes to any of
> the source files I've opened, and the "Command" window shows a number of
> "DLL ENTRY DLL ENTRY DLL ENTRY..." Nothing else.
>
> How can I trace through the source code? What am I doing wrong in the
above
> steps?
>
> Thanks in advance,
>
> --
> Sam.
>
>
>
> Hope this helps.
>
> Thank you,
> Bobby Mattappally
> Microsoft DDK Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
- Next message: vipin aravind: "Re: Can JOB_INFO_1 be accessed from Win98 UNIDRV-based driver?"
- Previous message: vipin aravind: "Re: Printer Driver: Save to PCL and EMF file."
- In reply to: Bobby Mattappally [MS]: "Re: Unidrv Minidriver for Win 9x??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
