Hi, I saw that this issue was addressed in the NTDEV archives, but
couldn’t access them. It seems that using the exception handling keywords
in a driver causes the VC++ compiler to generate a refernce to
“_except_handler3” from NTOSKRNL.DLL, which doesn’t exist in NT4, so the
driver won’t load. Some info I saw indicates the VC++ compiler versions
8.00 and above generates this when it sees “_try, _except, etc.” If this
is the case, are there any switches, or any other mechanism that will
generate an import compatible acress NT4/2K/XP?
Any suggestions would be very much appreciated (of course 
Best, Ken Claggett
You ever search microsoft.com? How about 316315?
“Kenneth Claggett” wrote in message
news:xxxxx@ntdev…
>
> Hi, I saw that this issue was addressed in the NTDEV archives, but
> couldn’t access them. It seems that using the exception handling keywords
> in a driver causes the VC++ compiler to generate a refernce to
> “_except_handler3” from NTOSKRNL.DLL, which doesn’t exist in NT4, so the
> driver won’t load. Some info I saw indicates the VC++ compiler versions
> 8.00 and above generates this when it sees “_try, _except, etc.” If this
> is the case, are there any switches, or any other mechanism that will
> generate an import compatible acress NT4/2K/XP?
>
> Any suggestions would be very much appreciated (of course 
>
> Best, Ken Claggett
>
>
This occurs if you build by w2k or later DDK and run on NT4.
Build by NT4 DDK.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
----- Original Message -----
From: “Kenneth Claggett”
To: “Windows System Software Devs Interest List”
Sent: Wednesday, November 26, 2003 10:52 PM
Subject: [ntdev] _except_handler3 and NT4
> Hi, I saw that this issue was addressed in the NTDEV archives, but
> couldn’t access them. It seems that using the exception handling keywords
> in a driver causes the VC++ compiler to generate a refernce to
> “_except_handler3” from NTOSKRNL.DLL, which doesn’t exist in NT4, so the
> driver won’t load. Some info I saw indicates the VC++ compiler versions
> 8.00 and above generates this when it sees “_try, _except, etc.” If this
> is the case, are there any switches, or any other mechanism that will
> generate an import compatible acress NT4/2K/XP?
>
> Any suggestions would be very much appreciated (of course 
>
> Best, Ken Claggett
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
Try this http://htfv.vba.com.by/articles/nt4ddk.asp
-htfv
“Kenneth Claggett” wrote in message
news:xxxxx@ntdev…
>
> Hi, I saw that this issue was addressed in the NTDEV archives, but
> couldn’t access them. It seems that using the exception handling keywords
> in a driver causes the VC++ compiler to generate a refernce to
> “_except_handler3” from NTOSKRNL.DLL, which doesn’t exist in NT4, so the
> driver won’t load. Some info I saw indicates the VC++ compiler versions
> 8.00 and above generates this when it sees “_try, _except, etc.” If this
> is the case, are there any switches, or any other mechanism that will
> generate an import compatible acress NT4/2K/XP?
>
> Any suggestions would be very much appreciated (of course 
>
> Best, Ken Claggett
>
>