Re: Unidrv Minidriver for Win 9x??
From: question (question_at_nospam.com)
Date: 03/29/04
- Next message: Raj: "Re: Device driver questions."
- Previous message: mozart: "WRITE_REGISTER_BUFFER_UCHAR..."
- In reply to: Sam: "Re: Unidrv Minidriver for Win 9x??"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Mar 2004 22:32:45 +0530
Put a statement like "_asm int 3" in DrvEnableDriver and subsequently
breakpoints in other entry points, to debug.
I assume you are writting some commercial piece of software.
vipin
"Sam" <anishsam@gnostice.com> wrote in message
news:uPY4D8UFEHA.2732@tk2msftngp13.phx.gbl...
> 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.
>
>
> "vipin aravind" <vipin.aravind@wpro.com> wrote in message
> news:up0D8WAFEHA.3856@TK2MSFTNGP12.phx.gbl...
> > BTW what are you trying do. what is your virtual printer driver supposed
> to
> > do?
> > vipin
> >
> > "Sam" <anishsam@gnostice.com> wrote in message
> > news:#mVoAI7EEHA.3804@TK2MSFTNGP09.phx.gbl...
> > > Hi Vipin,
> > >
> > > I am certainly Anish Sam! But not Anish Sam Jacob from IIT! ;-)
> > >
> > > --
> > > Sam.
> > >
> > > "vipin aravind" <vipin.aravind@wpro.com> wrote in message
> > > news:uss2mJyEEHA.3788@TK2MSFTNGP10.phx.gbl...
> > > > Are you anish sam jacob from IIT?
> > > >
> > > > vipin
> > > > "Sam" <anishsam@gnostice.com> wrote in message
> > > > news:e56kAMmEEHA.2308@tk2msftngp13.phx.gbl...
> > > > > Hi,
> > > > >
> > > > > If I create a Unidrv Minidriver like the OEMUNI sample, will it
work
> > on
> > > > all
> > > > > the versions of windows (Win 95/98/NT/2K/ME/XP...)? How can I
write
> a
> > > > > virtual printer driver that will work on all versions of windows?
> > > > >
> > > > > Thanks,
> > > > > --
> > > > > Sam
> > > > >
> > > >
> > > >
> > >
> >
> >
>
- Next message: Raj: "Re: Device driver questions."
- Previous message: mozart: "WRITE_REGISTER_BUFFER_UCHAR..."
- In reply to: Sam: "Re: Unidrv Minidriver for Win 9x??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
