GDI_DRIVER Driver compilation with VS7.1 IDE

Hi,

Introduction:
**********
I am writing a display mirror driver, I am trying to use the VS7.1 (.NET)
IDE to compile the driver, conversion to an .vsproj solution is done by the
'Source to DSP converter' app provided with 'SoftIce driver suit'.

The Problem:
**********
The mirror is build of to files: the miniport driver and the display driver,
no problems has occurred converting compiling and using the miniport driver,
in contrast, conversion of the display driver failed: the 'Source to DSP
converter' doesn't support GDI_DRIVER conversions, SO..., I tried to do some
tricks: I have changed the TARGETTYPE of the GDI_DRIVER to DRIVER and then
used the 'Source to DSP converter' with the new source file, the result was
a new .vsproj compiling a .sys driver I have changed the name of the driver
to be .dll and removed the 'DriverEntry' DLL entry point from the project
configuration, still, using the new driver causes an 'Unhandled kernel mode
exception', using the display driver compiled by the 'source' makefile works
fine and doesn't reproduce this problem, what may cause the problem? what
went wrong during the 'Source to DSP converter' conversion? what special
configurations are required for a GDI driver?
Should there be any specific entry point to a GDI_DRIVER?

Thanks in advance,
Nadav,

Maxim
Sat Jan 10 18:46:07 CST 2004

> IDE to compile the driver, conversion to an .vsproj solution is done by the
> 'Source to DSP converter' app provided with 'SoftIce driver suit'.

Forget the converter and build using the native kernel build environment,
without all these VC++'s toys.

If the rest of your project uses VC++ build (and I would really and seriously
recommend to move it to SOURCES instead, unless you use some wizards heavily) -
then use DDKBUILD.BAT by Mark Roddy.

It runs the real DDK BUILD as a "custom build step" in VC++ project. By far
more sane solution then converting SOURCES to plain idiotic .DSP.

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

Nadav
Sat Jan 10 16:50:40 CST 2004

Well... It was because the Driver entry wasn't set to 'DrvEnableDriver'.

"Nadav" <not@today> wrote in message
news:%23%23Yu4j51DHA.3116@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> Introduction:
> **********
> I am writing a display mirror driver, I am trying to use the VS7.1 (.NET)
> IDE to compile the driver, conversion to an .vsproj solution is done by
the
> 'Source to DSP converter' app provided with 'SoftIce driver suit'.
>
> The Problem:
> **********
> The mirror is build of to files: the miniport driver and the display
driver,
> no problems has occurred converting compiling and using the miniport
driver,
> in contrast, conversion of the display driver failed: the 'Source to DSP
> converter' doesn't support GDI_DRIVER conversions, SO..., I tried to do
some
> tricks: I have changed the TARGETTYPE of the GDI_DRIVER to DRIVER and then
> used the 'Source to DSP converter' with the new source file, the result
was
> a new .vsproj compiling a .sys driver I have changed the name of the
driver
> to be .dll and removed the 'DriverEntry' DLL entry point from the project
> configuration, still, using the new driver causes an 'Unhandled kernel
mode
> exception', using the display driver compiled by the 'source' makefile
works
> fine and doesn't reproduce this problem, what may cause the problem? what
> went wrong during the 'Source to DSP converter' conversion? what special
> configurations are required for a GDI driver?
> Should there be any specific entry point to a GDI_DRIVER?
>
> Thanks in advance,
> Nadav,
>
>