I’m trying to build a co-installer with WDK6000. I’ve been able to
build it successfully, but when I install the associated driver
package on an Windows XP SP 2 system I get the following error:
The procedure entry point _except_handler4_common could not be
located in the dynamic library msvcrt.dll.
From what I can tell this is a new symbol that was introduced with
Vista. What I’m not sure about, however, is what the best way to work
around this issue is. Presumably I could build the coinstaller with
an earlier version of the DDK, but I’d prefer not to complicate our
build environment. I’m pretty sure that this problem occurs
regardless of the selected build environment (I’ve tried both the
Windows XP and the Windows Vista x86 environments).
Has anyone else encountered this before?
Thanks.
-John
Try w2k build env.
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
“John Kraft” wrote in message news:xxxxx@ntdev…
> I’m trying to build a co-installer with WDK6000. I’ve been able to
> build it successfully, but when I install the associated driver
> package on an Windows XP SP 2 system I get the following error:
>
> The procedure entry point _except_handler4_common could not be
> located in the dynamic library msvcrt.dll.
>
> From what I can tell this is a new symbol that was introduced with
> Vista. What I’m not sure about, however, is what the best way to work
> around this issue is. Presumably I could build the coinstaller with
> an earlier version of the DDK, but I’d prefer not to complicate our
> build environment. I’m pretty sure that this problem occurs
> regardless of the selected build environment (I’ve tried both the
> Windows XP and the Windows Vista x86 environments).
>
> Has anyone else encountered this before?
>
> Thanks.
>
> -John
>
>
>
>
I don’t know why you are getting this, as I thought that
_except_handler4_common was only part of MSVCRT8.DLL, and you’re using
BUILD, but I would try adding USE_LIBCMT to your SOURCES file. If
you’ve added USE_MSVCRT, comment it out or remove it. This will
statically link libc, which should fix the problem, whatever is causing it.
Good luck,
mm
John Kraft wrote:
I’m trying to build a co-installer with WDK6000. I’ve been able to
build it successfully, but when I install the associated driver package
on an Windows XP SP 2 system I get the following error:
The procedure entry point _except_handler4_common could not be
located in the dynamic library msvcrt.dll.
From what I can tell this is a new symbol that was introduced with
Vista. What I’m not sure about, however, is what the best way to work
around this issue is. Presumably I could build the coinstaller with an
earlier version of the DDK, but I’d prefer not to complicate our build
environment. I’m pretty sure that this problem occurs regardless of
the selected build environment (I’ve tried both the Windows XP and the
Windows Vista x86 environments).
Has anyone else encountered this before?
Thanks.
-John
USE_MSVCRT will link good old MSVCRT in, not MSVCRT8.DLL
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
“Martin O’Brien” wrote in message
news:xxxxx@ntdev…
> I don’t know why you are getting this, as I thought that
> _except_handler4_common was only part of MSVCRT8.DLL, and you’re using
> BUILD, but I would try adding USE_LIBCMT to your SOURCES file. If
> you’ve added USE_MSVCRT, comment it out or remove it. This will
> statically link libc, which should fix the problem, whatever is causing it.
>
> Good luck,
>
> mm
>
>
> John Kraft wrote:
> > I’m trying to build a co-installer with WDK6000. I’ve been able to
> > build it successfully, but when I install the associated driver package
> > on an Windows XP SP 2 system I get the following error:
> >
> > The procedure entry point _except_handler4_common could not be
> > located in the dynamic library msvcrt.dll.
> >
> > From what I can tell this is a new symbol that was introduced with
> > Vista. What I’m not sure about, however, is what the best way to work
> > around this issue is. Presumably I could build the coinstaller with an
> > earlier version of the DDK, but I’d prefer not to complicate our build
> > environment. I’m pretty sure that this problem occurs regardless of
> > the selected build environment (I’ve tried both the Windows XP and the
> > Windows Vista x86 environments).
> >
> > Has anyone else encountered this before?
> >
> > Thanks.
> >
> > -John
> >
> >
> >
> >
>