Re: How can drivers be called BEFORE call InitInstance

From:

"Alexander Grigoriev" <alegr@earthlink.net>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 20 Apr 2009 21:36:08 -0700

Message-ID:

<OXJwyqjwJHA.5900@TK2MSFTNGP03.phx.gbl>

Make sure you don't link to the driver vendor's DLL. It looks like the DLL
is installing the driver in its DllMain (VERY BAD, INVALID APPROACH).

I used to work with a video capture board that tried to find the board in
its DLL's DllMain, and if failed it SHOWED A MESSAGE BOX AND FAILED DLL
LOADING! That meant, if an application was linked to the DLL it WOULD NOT
START AT ALL.

"Chris H" <humme.chris@royalmaster.com> wrote in message
news:49ece1e9$0$22547$607ed4bc@cv.net...

I am trying to get my latest version program of a program started a LONG
time ago to run on Vista. Over the years we have changed motion
controllers. Until now I could just install the drivers for the old and new
motion controllers and based on a flag, I set the registry, call the
drivers for either motion controller. The drivers for the old motion
controller will not install on Vista. The company that made the old motion
controller used a utility by Bsqare called WinRT to develop the driver for
the old motion controller. I am not finding any info on how the driver
works.

Back in 2005 I used #define NO_MACHINE and then #ifdef and #ifndef to
create a demo version of the program that would run without any motion
controller driver installed, worked fine as expected.

It seems that I should be able to use the registry flag to avoid calls to
the old motion controller driver and the program would run fine just not
talk with the old motion controller.

NOT SO FAST THERE!!

I went so far as to go through the code and made sure that every call I
could find to the old motion controller and its .h file were commented
out. Still as soon as I start the program before any code I can find is
run I get an error "NT6400 - WinRT" " Please reboot to start the driver."
I have seen this error many times over the years on new PCs, just install
the driver, reboot problem solved. The error message must be from WinRT
since the error message is not in my code and the same error comes up with
the terminal utility supplied by the motion controller vender. By the way
this is on a PC with a fresh copy of XP, Vista is just another layer of
trouble I don't want to get into yet.

So now I am baffled as to where the driver is getting called from. Just to
finish rattling my brain even after commenting out everything that I had
been doing by defining NO_MACHINE. When I define NO_MACHINE I don't get
the error message and I am able to run the parts of the program that don't
involve the motion controller just like the demo version from 2005.

Since there are a lot of systems out there with the old motion controller
I would very much like to have one version of the program run with either
motion controller. Besides which this is developing into an instance of
morbid curiosity.

Sorry for such a long message.

Thanks in advance

ChrisH