Hi.
I used to compile my driver using ddkbuild, integrated with Visual Studio and IFSKit too. My driver was about 150k big. After a little problem I had I reinstalled the system, and then Visual Studio, IFSKit and ddkbuild. Now I compile the driver and it is only 50k big (checked version) and it doesn’t work on WNT.
Normally ddkbuild, if not specified, builds for NT. Does this have to do with the IFSKit version?
Thank you very much.
Look at this article http://htfv.vba.com.by/articles/nt4ddk.asp for information on building drivers for Windows NT 4.0.
-htfv
----- Original Message -----
From: Ratmil Torres
To: Windows File Systems Devs Interest List
Sent: Monday, September 22, 2003 8:37 PM
Subject: [ntfsd] compiling with ddkbuild for nt
Hi.
I used to compile my driver using ddkbuild, integrated with Visual Studio and IFSKit too. My driver was about 150k big. After a little problem I had I reinstalled the system, and then Visual Studio, IFSKit and ddkbuild. Now I compile the driver and it is only 50k big (checked version) and it doesn’t work on WNT.
Normally ddkbuild, if not specified, builds for NT. Does this have to do with the IFSKit version?
Thank you very much.
You are currently subscribed to ntfsd as: xxxxx@vba.com.by
To unsubscribe send a blank email to xxxxx@lists.osr.com
A similar situation has happened to me when I built a driver using
libraries from DDK for Windows 2000.
To make your driver working under Windows NT, you must use
libraries from DDK for Windows NT. This is because libraries for
Win2K DDK force linker to use some symbols which are not exposed
by NTOSKRNL.exe from Windows NT (e.g. “__except_handler3”).
To make sure this is the problem you have, you can use
depends.exe tool on your linked driver. You can then see what
symbols are imported from what module and also which ones are not
exported by NTOSKRNL.exe.
L.
–
Vyhraj Ford Fiesta s klimatizac? a dal?? ceny!
V?ce na http://soutez.volny.cz
I don’t understand. I installed DDK for WNT.
Anyway I tried to link exsup.obj and exsup3.obj and I got this error:
exsup.obj() : error LNK1103: debugging information corrupt; recompile module
----- Original Message -----
From: “Ladislav Zezula”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, September 23, 2003 1:03 AM
Subject: [ntfsd] Re: compiling with ddkbuild for nt
> A similar situation has happened to me when I built a driver using
> libraries from DDK for Windows 2000.
>
> To make your driver working under Windows NT, you must use
> libraries from DDK for Windows NT. This is because libraries for
> Win2K DDK force linker to use some symbols which are not exposed
> by NTOSKRNL.exe from Windows NT (e.g. “__except_handler3”).
>
> To make sure this is the problem you have, you can use
> depends.exe tool on your linked driver. You can then see what
> symbols are imported from what module and also which ones are not
> exported by NTOSKRNL.exe.
>
> L.
>
>
>
> –
> Vyhraj Ford Fiesta s klimatizac? a dal?? ceny!
> V?ce na http://soutez.volny.cz
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@seg.inf.cu
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
>
>
>
>
>
According to Microsoft knowledge base article 316315 I need to link to
exsup.lib, but I only have exsup.obj. What tool can I use to make a .lib
from a .obj?
----- Original Message -----
From: “Ladislav Zezula”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, September 23, 2003 1:03 AM
Subject: [ntfsd] Re: compiling with ddkbuild for nt
> A similar situation has happened to me when I built a driver using
> libraries from DDK for Windows 2000.
>
> To make your driver working under Windows NT, you must use
> libraries from DDK for Windows NT. This is because libraries for
> Win2K DDK force linker to use some symbols which are not exposed
> by NTOSKRNL.exe from Windows NT (e.g. “__except_handler3”).
>
> To make sure this is the problem you have, you can use
> depends.exe tool on your linked driver. You can then see what
> symbols are imported from what module and also which ones are not
> exported by NTOSKRNL.exe.
>
> L.
>
>
>
> –
> Vyhraj Ford Fiesta s klimatizac? a dal?? ceny!
> V?ce na http://soutez.volny.cz
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@seg.inf.cu
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
>
>
>
>
>
You can link with an .obj as well, the linker doesn’t care.
Ratmil Torres wrote:
According to Microsoft knowledge base article 316315 I need to link to
exsup.lib, but I only have exsup.obj. What tool can I use to make a .lib
from a .obj?
----- Original Message -----
From: “Ladislav Zezula”
> To: “Windows File Systems Devs Interest List”
> Sent: Tuesday, September 23, 2003 1:03 AM
> Subject: [ntfsd] Re: compiling with ddkbuild for nt
>
>
>
>>A similar situation has happened to me when I built a driver using
>>libraries from DDK for Windows 2000.
>>
>>To make your driver working under Windows NT, you must use
>>libraries from DDK for Windows NT. This is because libraries for
>>Win2K DDK force linker to use some symbols which are not exposed
>>by NTOSKRNL.exe from Windows NT (e.g. “__except_handler3”).
>>
>>To make sure this is the problem you have, you can use
>>depends.exe tool on your linked driver. You can then see what
>>symbols are imported from what module and also which ones are not
>>exported by NTOSKRNL.exe.
>>
>>L.
>>
>>
>>
>>–
>>Vyhraj Ford Fiesta s klimatizací a dal¹í ceny!
>>Více na http://soutez.volny.cz
>>
>>
>>—
>>You are currently subscribed to ntfsd as: xxxxx@seg.inf.cu
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
–
Nick Ryan (MVP for DDK)
In Windows NT 4.0 DDK ntoskrnl.lib is linked with exsup.obj, exsup3.obj and
all the rest from that family.
----- Original Message -----
From: “Ladislav Zezula”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, September 23, 2003 11:03 AM
Subject: [ntfsd] Re: compiling with ddkbuild for nt
A similar situation has happened to me when I built a driver using
libraries from DDK for Windows 2000.
To make your driver working under Windows NT, you must use
libraries from DDK for Windows NT. This is because libraries for
Win2K DDK force linker to use some symbols which are not exposed
by NTOSKRNL.exe from Windows NT (e.g. “__except_handler3”).
To make sure this is the problem you have, you can use
depends.exe tool on your linked driver. You can then see what
symbols are imported from what module and also which ones are not
exported by NTOSKRNL.exe.
L.
–
Vyhraj Ford Fiesta s klimatizací a dal¹í ceny!
Více na http://soutez.volny.cz
—
You are currently subscribed to ntfsd as: xxxxx@vba.com.by
To unsubscribe send a blank email to xxxxx@lists.osr.com
You have to link your module with at least exsup.obj and exsup3.obj.
-htfv
----- Original Message -----
From: “Ratmil Torres”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, September 23, 2003 5:56 PM
Subject: [ntfsd] Re: compiling with ddkbuild for nt
According to Microsoft knowledge base article 316315 I need to link to
exsup.lib, but I only have exsup.obj. What tool can I use to make a .lib
from a .obj?
----- Original Message -----
From: “Ladislav Zezula”
To: “Windows File Systems Devs Interest List”
Sent: Tuesday, September 23, 2003 1:03 AM
Subject: [ntfsd] Re: compiling with ddkbuild for nt
> A similar situation has happened to me when I built a driver using
> libraries from DDK for Windows 2000.
>
> To make your driver working under Windows NT, you must use
> libraries from DDK for Windows NT. This is because libraries for
> Win2K DDK force linker to use some symbols which are not exposed
> by NTOSKRNL.exe from Windows NT (e.g. “__except_handler3”).
>
> To make sure this is the problem you have, you can use
> depends.exe tool on your linked driver. You can then see what
> symbols are imported from what module and also which ones are not
> exported by NTOSKRNL.exe.
>
> L.
>
>
>
> –
> Vyhraj Ford Fiesta s klimatizací a dal¹í ceny!
> Více na http://soutez.volny.cz
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@seg.inf.cu
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
>
>
>
>
>
—
You are currently subscribed to ntfsd as: xxxxx@vba.com.by
To unsubscribe send a blank email to xxxxx@lists.osr.com