Happy new year everybody,
My driver does not explicitly link to any DLL and it is using structured
exception handling, I have windows 2000 DDK installed on a Windows NT
machine, SP5. The driver compiles and links successfully, when trying to
load the driver the system fails to resolve the link _except_handler3 in
NTOSKRNL.EXE.
NTOSKRNL does not export this routine on Windows NT 4.0 but it does so on
Windows 2000. When I removed all try/except/finally statements from the
driver, the driver loads successfully.
Also when building the driver using NT 4.0 DDK, this problem does not
exist. So my question is that is there anyway to instruct the
compiler/linker not to use this _except_hanldler3 routine or to produce
code that is Windows NT 4.0 Compatible.
Your help is highly appreciated.
Thanks
-Muath
Commvault Systems
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Build it with NT DDK for 4.0 , or be evil and code yourself by hand an
except_handler3().
Which isnt recomeded.
Regards
----- Original Message -----
From:
To: “File Systems Developers”
Sent: Sunday, December 30, 2001 2:00 PM
Subject: [ntfsd] Can I build a Windows NT 4.0 Driver using Windows 2000 DDK
> Happy new year everybody,
>
> My driver does not explicitly link to any DLL and it is using structured
> exception handling, I have windows 2000 DDK installed on a Windows NT
> machine, SP5. The driver compiles and links successfully, when trying to
> load the driver the system fails to resolve the link _except_handler3 in
> NTOSKRNL.EXE.
> NTOSKRNL does not export this routine on Windows NT 4.0 but it does so on
> Windows 2000. When I removed all try/except/finally statements from the
> driver, the driver loads successfully.
>
> Also when building the driver using NT 4.0 DDK, this problem does not
> exist. So my question is that is there anyway to instruct the
> compiler/linker not to use this _except_hanldler3 routine or to produce
> code that is Windows NT 4.0 Compatible.
>
> Your help is highly appreciated.
> Thanks
> -Muath
> Commvault Systems
>
> —
> You are currently subscribed to ntfsd as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
If you do not use exception you can surely use Win2k DDK without any
modifications. If you use exceptions you would have to redefine some
#define’s in your sources file or even setenv.bat. The “excpt.h” file is the
same in both DDK’s (I copied one from 2k DDK to NT4 DDK and have no
problems) so it probably works through some #defines.
----- Original Message -----
From:
To: “File Systems Developers”
Sent: Sunday, December 30, 2001 2:00 PM
Subject: [ntfsd] Can I build a Windows NT 4.0 Driver using Windows 2000 DDK
> Happy new year everybody,
>
> My driver does not explicitly link to any DLL and it is using structured
> exception handling, I have windows 2000 DDK installed on a Windows NT
> machine, SP5. The driver compiles and links successfully, when trying to
> load the driver the system fails to resolve the link _except_handler3 in
> NTOSKRNL.EXE.
> NTOSKRNL does not export this routine on Windows NT 4.0 but it does so on
> Windows 2000. When I removed all try/except/finally statements from the
> driver, the driver loads successfully.
>
> Also when building the driver using NT 4.0 DDK, this problem does not
> exist. So my question is that is there anyway to instruct the
> compiler/linker not to use this _except_hanldler3 routine or to produce
> code that is Windows NT 4.0 Compatible.
>
> Your help is highly appreciated.
> Thanks
> -Muath
> Commvault Systems
>
> —
> You are currently subscribed to ntfsd as: xxxxx@vba.com.by
> To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com