HELP, 2k EngModifySurface Links with WIN32K.sys

Hi All,

In 2K usermode printer driver, I am trying to use
EngModifySurface. Only this call uses win32k.lib,
this finally gets linked with WIN32K.sys, which is kernel mode GDI component.

Even GDI32.DLL supports lot of ENG functions, why this is moved to WIN32K.sys?

for me any 2k driver built with this call causes
not load the UI. Also fails to print from the winword.

Any one noticed similar problem ?
Please help on this.

Waiting for your reply.
--
With Thanks & Regards,
Shrinidhi.Kulkarni
5732293x5215

Maxim
Wed Jul 21 08:52:45 CDT 2004

> Even GDI32.DLL supports lot of ENG functions, why this is moved to
WIN32K.sys?

Engxxx functions exported by GDI32 (with the sole purpose of user mode printer
drivers support) are nothing more then syscall stubs which lead to the real
kernel-mode Engxxx functions inside win32k.

The implementation of the graphics engine is in win32k only.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

vipin
Wed Jul 21 12:27:50 CDT 2004

Coming to the part which Maxim hasn't answered. I am wondering why you are
using EngModifySurface(...) in a printer driver.Are you trying to change the
hooks which the driver supports at runtime after the user had previously set
using EngAssociateSurface(...)

thanks
vipin


"Shrinidhi.Kulkarni" <ShrinidhiKulkarni@discussions.microsoft.com> wrote in
message news:3499C8B3-A57B-4EB8-AA82-D397B96AB494@microsoft.com...
> Hi All,
>
> In 2K usermode printer driver, I am trying to use
> EngModifySurface. Only this call uses win32k.lib,
> this finally gets linked with WIN32K.sys, which is kernel mode GDI
component.
>
> Even GDI32.DLL supports lot of ENG functions, why this is moved to
WIN32K.sys?
>
> for me any 2k driver built with this call causes
> not load the UI. Also fails to print from the winword.
>
> Any one noticed similar problem ?
> Please help on this.
>
> Waiting for your reply.
> --
> With Thanks & Regards,
> Shrinidhi.Kulkarni
> 5732293x5215
>

ShrinidhiKulkarni
Fri Jul 23 03:21:01 CDT 2004

Hi Vipin,
Please see my answer in inline...

"vipin" wrote:
> Coming to the part which Maxim hasn't answered. I am wondering why you are using EngModifySurface(...)

I wanted to use Device-Managed Surfaces (Standard-Format Bitmaps) A non-opaque device-managed surface as per DDK.

Ok... I will not use the EngModifySurface,
Please can you tell me as why EngModifySurface has been moved from gdi32.dll ?


If you can explain me as how to use this,.. it will be good, as there is very little documentation in DDK help.

Thanks in advance,
With Best regards,
Shrinidhi.Kulkarni
5732293x5215


>in a printer driver.Are you trying to change the
> hooks which the driver supports at runtime after the user had previously set
> using EngAssociateSurface(...)
>
> thanks
> vipin
>
>
> "Shrinidhi.Kulkarni" <ShrinidhiKulkarni@discussions.microsoft.com> wrote in
> message news:3499C8B3-A57B-4EB8-AA82-D397B96AB494@microsoft.com...
> > Hi All,
> >
> > In 2K usermode printer driver, I am trying to use
> > EngModifySurface. Only this call uses win32k.lib,
> > this finally gets linked with WIN32K.sys, which is kernel mode GDI
> component.
> >
> > Even GDI32.DLL supports lot of ENG functions, why this is moved to
> WIN32K.sys?
> >
> > for me any 2k driver built with this call causes
> > not load the UI. Also fails to print from the winword.
> >
> > Any one noticed similar problem ?
> > Please help on this.
> >
> > Waiting for your reply.
> > --
> > With Thanks & Regards,
> > Shrinidhi.Kulkarni
> > 5732293x5215
> >
>
>
>

vipin
Fri Jul 23 09:32:13 CDT 2004

As Maxim said ,gdi32.dll is stub and enables a kernel mode switch into
win32k.sys.The thing is in windows 2000, the drivers are usermode so they
need to use some of the GDI functions and the Eng* functions in gdi32*
enables seamless porting from NT4 written drivers which used to link with
win32k.sys via win32k.lib. EngModifySurface(...) appears useful probably for
display drivers.

thanks
vipin


"Shrinidhi.Kulkarni" <ShrinidhiKulkarni@discussions.microsoft.com> wrote in
message news:32BB0F73-1A94-4D0F-8BDE-7F75B6C747FF@microsoft.com...
> Hi Vipin,
> Please see my answer in inline...
>
> "vipin" wrote:
> > Coming to the part which Maxim hasn't answered. I am wondering why you
are using EngModifySurface(...)
>
> I wanted to use Device-Managed Surfaces (Standard-Format Bitmaps) A
non-opaque device-managed surface as per DDK.
>
> Ok... I will not use the EngModifySurface,
> Please can you tell me as why EngModifySurface has been moved from
gdi32.dll ?
>
>
> If you can explain me as how to use this,.. it will be good, as there is
very little documentation in DDK help.
>
> Thanks in advance,
> With Best regards,
> Shrinidhi.Kulkarni
> 5732293x5215
>
>
> >in a printer driver.Are you trying to change the
> > hooks which the driver supports at runtime after the user had previously
set
> > using EngAssociateSurface(...)
> >
> > thanks
> > vipin
> >
> >
> > "Shrinidhi.Kulkarni" <ShrinidhiKulkarni@discussions.microsoft.com> wrote
in
> > message news:3499C8B3-A57B-4EB8-AA82-D397B96AB494@microsoft.com...
> > > Hi All,
> > >
> > > In 2K usermode printer driver, I am trying to use
> > > EngModifySurface. Only this call uses win32k.lib,
> > > this finally gets linked with WIN32K.sys, which is kernel mode GDI
> > component.
> > >
> > > Even GDI32.DLL supports lot of ENG functions, why this is moved to
> > WIN32K.sys?
> > >
> > > for me any 2k driver built with this call causes
> > > not load the UI. Also fails to print from the winword.
> > >
> > > Any one noticed similar problem ?
> > > Please help on this.
> > >
> > > Waiting for your reply.
> > > --
> > > With Thanks & Regards,
> > > Shrinidhi.Kulkarni
> > > 5732293x5215
> > >
> >
> >
> >