Hello all,
Can I Load
Thanks in advance,
Regards
-Akhil
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
No, you cannot.
EXEs and DLLs work in user mode and cannot be called from a driver.
Max
----- Original Message -----
From: “akhil”
To: “NT Developers Interest List”
Sent: Monday, December 24, 2001 12:00 AM
Subject: [ntdev] Dll or Exe in Kernel mode
> Hello all,
>
> Can I Load
> 1) EXE
> 2) DLL
> in a kernel mode driver.
> How can I do it ?any sample code or idea will be a great help for me .
>
> Thanks in advance,
> Regards
> -Akhil
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Ok Max,it is not possible to call user-mode code from
kernel mode.
my second question is >
Can i activate a process which is in user-mode by some
event from kernel mode?
Regards,
Akhil
— “Maxim S. Shatskih”
wrote: > No, you cannot.
> EXEs and DLLs work in user mode and cannot be called
> from a driver.
>
> Max
>
> ----- Original Message -----
> From: “akhil”
> To: “NT Developers Interest List”
>
> Sent: Monday, December 24, 2001 12:00 AM
> Subject: [ntdev] Dll or Exe in Kernel mode
>
>
> > Hello all,
> >
> > Can I Load
> > 1) EXE
> > 2) DLL
> > in a kernel mode driver.
> > How can I do it ?any sample code or idea will be a
> great help for me .
> >
> > Thanks in advance,
> > Regards
> > -Akhil
> >
> > —
> > You are currently subscribed to ntdev as:
> xxxxx@storagecraft.com
> > To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.co.uk
> To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
__________________________________________________
Do You Yahoo!?
Everything you’ll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hi, akhil sunder!
my second question is >
Can i activate a process which is in user-mode by some
event from kernel mode?
No problem. Look at IoCreateSynchronizationEvent() function in ddk. Create
event in \BaseNamedObjects dir. In your DLL or EXE open it with OpenEvent.
Eugene.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Max,
Whereas you are right on the EXE, you are wrong on the DLL. Remember, a
driver in NT/2000 is nothing more than a DLL. Case in point - SCSIPORT. You
link your mini-port driver with the import lib. When the mini-port loads, it
goes through the DLL loading procedures when you the call
ScsiPortIninitialize.
Gary
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
Sent: Monday, December 24, 2001 2:53 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel mode
No, you cannot.
EXEs and DLLs work in user mode and cannot be called from a driver.
Max
----- Original Message -----
From: “akhil”
To: “NT Developers Interest List”
Sent: Monday, December 24, 2001 12:00 AM
Subject: [ntdev] Dll or Exe in Kernel mode
> Hello all,
>
> Can I Load
> 1) EXE
> 2) DLL
> in a kernel mode driver.
> How can I do it ?any sample code or idea will be a great help for me .
>
> Thanks in advance,
> Regards
> -Akhil
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: xxxxx@inland.net
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
There is some truth that SCSIPORT & SMCLIB are nothing more than DLLs, but
you can’t create them with the same tools and methods used to create DLLs
that run in user mode. They are both .SYS drivers that have a DriverEntry()
exported function. They are both created using the DDK & BUILD.EXE. The
.LIBs that permit linking to them are similar but not identical to a LIB
used with a user mode DLL.
CLASSPNP is another ‘kernel-mode DLL’. The source and build files are
available in the DDK.
----- Original Message -----
From: “Gary G. Little”
To: “NT Developers Interest List”
Sent: Monday, December 24, 2001 12:21 PM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> Max,
>
> Whereas you are right on the EXE, you are wrong on the DLL. Remember, a
> driver in NT/2000 is nothing more than a DLL. Case in point - SCSIPORT.
You
> link your mini-port driver with the import lib. When the mini-port loads,
it
> goes through the DLL loading procedures when you the call
> ScsiPortIninitialize.
>
> Gary
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> Sent: Monday, December 24, 2001 2:53 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
> No, you cannot.
> EXEs and DLLs work in user mode and cannot be called from a driver.
>
> Max
>
> ----- Original Message -----
> From: “akhil”
> To: “NT Developers Interest List”
> Sent: Monday, December 24, 2001 12:00 AM
> Subject: [ntdev] Dll or Exe in Kernel mode
>
>
> > Hello all,
> >
> > Can I Load
> > 1) EXE
> > 2) DLL
> > in a kernel mode driver.
> > How can I do it ?any sample code or idea will be a great help for me .
> >
> > Thanks in advance,
> > Regards
> > -Akhil
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Yes, this is a terminology issue.
Surely kernel-mode DLLs can be called, but not usual user-mode DLLs.
Max
----- Original Message -----
From: “Gary G. Little”
To: “NT Developers Interest List”
Sent: Monday, December 24, 2001 8:21 PM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> Max,
>
> Whereas you are right on the EXE, you are wrong on the DLL. Remember, a
> driver in NT/2000 is nothing more than a DLL. Case in point - SCSIPORT. You
> link your mini-port driver with the import lib. When the mini-port loads, it
> goes through the DLL loading procedures when you the call
> ScsiPortIninitialize.
>
> Gary
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> Sent: Monday, December 24, 2001 2:53 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
> No, you cannot.
> EXEs and DLLs work in user mode and cannot be called from a driver.
>
> Max
>
> ----- Original Message -----
> From: “akhil”
> To: “NT Developers Interest List”
> Sent: Monday, December 24, 2001 12:00 AM
> Subject: [ntdev] Dll or Exe in Kernel mode
>
>
> > Hello all,
> >
> > Can I Load
> > 1) EXE
> > 2) DLL
> > in a kernel mode driver.
> > How can I do it ?any sample code or idea will be a great help for me .
> >
> > Thanks in advance,
> > Regards
> > -Akhil
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Creating a process is a very complex thing. Surely NtCreateProcess is not enough.
So, it is much better to have a user app which will do this if your driver wants this.
Max
----- Original Message -----
From: “akhil sunder”
To: “NT Developers Interest List”
Sent: Monday, December 24, 2001 2:58 PM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> Ok Max,it is not possible to call user-mode code from
> kernel mode.
> my second question is >
> Can i activate a process which is in user-mode by some
> event from kernel mode?
> Regards,
> Akhil
>
> — “Maxim S. Shatskih”
> wrote: > No, you cannot.
> > EXEs and DLLs work in user mode and cannot be called
> > from a driver.
> >
> > Max
> >
> > ----- Original Message -----
> > From: “akhil”
> > To: “NT Developers Interest List”
> >
> > Sent: Monday, December 24, 2001 12:00 AM
> > Subject: [ntdev] Dll or Exe in Kernel mode
> >
> >
> > > Hello all,
> > >
> > > Can I Load
> > > 1) EXE
> > > 2) DLL
> > > in a kernel mode driver.
> > > How can I do it ?any sample code or idea will be a
> > great help for me .
> > >
> > > Thanks in advance,
> > > Regards
> > > -Akhil
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> > xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to
> > leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@yahoo.co.uk
> > To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
> __________________________________________________
> Do You Yahoo!?
> Everything you’ll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> that run in user mode. They are both .SYS drivers that have a DriverEntry()
exported function.
…which is never called for them since they have no SC database entry.
DriverEntry also is not exported, it is the image entry point, not in exports table.
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Again, not necessarily true. You can use any symbol other than Driver entry
that you want, but you do need to export it and specify it as the entry
point. There is no magic in drivers. They are only DLLs with SYS as an
extension and of course are linked with the kernel libraries that are not
available to user mode. You must use the DDK but you do not HAVE to use
BUILD. That tends to be a religious issue between using the Visual Studio
IDE and the command line window folks.
Gary
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
Sent: Monday, December 24, 2001 12:24 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel mode
There is some truth that SCSIPORT & SMCLIB are nothing more than DLLs, but
you can’t create them with the same tools and methods used to create DLLs
that run in user mode. They are both .SYS drivers that have a DriverEntry()
exported function. They are both created using the DDK & BUILD.EXE. The
.LIBs that permit linking to them are similar but not identical to a LIB
used with a user mode DLL.
CLASSPNP is another ‘kernel-mode DLL’. The source and build files are
available in the DDK.
----- Original Message -----
From: “Gary G. Little”
To: “NT Developers Interest List”
Sent: Monday, December 24, 2001 12:21 PM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> Max,
>
> Whereas you are right on the EXE, you are wrong on the DLL. Remember, a
> driver in NT/2000 is nothing more than a DLL. Case in point - SCSIPORT.
You
> link your mini-port driver with the import lib. When the mini-port loads,
it
> goes through the DLL loading procedures when you the call
> ScsiPortIninitialize.
>
> Gary
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> Sent: Monday, December 24, 2001 2:53 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
> No, you cannot.
> EXEs and DLLs work in user mode and cannot be called from a driver.
>
> Max
>
> ----- Original Message -----
> From: “akhil”
> To: “NT Developers Interest List”
> Sent: Monday, December 24, 2001 12:00 AM
> Subject: [ntdev] Dll or Exe in Kernel mode
>
>
> > Hello all,
> >
> > Can I Load
> > 1) EXE
> > 2) DLL
> > in a kernel mode driver.
> > How can I do it ?any sample code or idea will be a great help for me .
> >
> > Thanks in advance,
> > Regards
> > -Akhil
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: xxxxx@inland.net
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Microsoft has declared from upon high that the IDE is to be ignored. The
command line compiler is shipped with the XP DDK and is the only supported
compiler. I haven’t started using the XP DDK other than as a reference, but
I guess the DDK group at Microsoft finally got fed up with the compiler
group releasing compilers that broke one or more of the DDKs.
I think that if want to have a driver that is included in the box of the
latest OS, you must use BUILD. M$ requires you to give them the source and
you must have WHQL approval.
----- Original Message -----
From: “Gary G. Little”
To: “NT Developers Interest List”
Sent: Wednesday, December 26, 2001 12:14 AM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> Again, not necessarily true. You can use any symbol other than Driver
entry
> that you want, but you do need to export it and specify it as the entry
> point. There is no magic in drivers. They are only DLLs with SYS as an
> extension and of course are linked with the kernel libraries that are not
> available to user mode. You must use the DDK but you do not HAVE to use
> BUILD. That tends to be a religious issue between using the Visual Studio
> IDE and the command line window folks.
>
> Gary
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
> Sent: Monday, December 24, 2001 12:24 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
> There is some truth that SCSIPORT & SMCLIB are nothing more than DLLs, but
> you can’t create them with the same tools and methods used to create DLLs
> that run in user mode. They are both .SYS drivers that have a
DriverEntry()
> exported function. They are both created using the DDK & BUILD.EXE. The
> .LIBs that permit linking to them are similar but not identical to a LIB
> used with a user mode DLL.
>
> CLASSPNP is another ‘kernel-mode DLL’. The source and build files are
> available in the DDK.
>
> ----- Original Message -----
> From: “Gary G. Little”
> To: “NT Developers Interest List”
> Sent: Monday, December 24, 2001 12:21 PM
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
>
> > Max,
> >
> > Whereas you are right on the EXE, you are wrong on the DLL. Remember, a
> > driver in NT/2000 is nothing more than a DLL. Case in point - SCSIPORT.
> You
> > link your mini-port driver with the import lib. When the mini-port
loads,
> it
> > goes through the DLL loading procedures when you the call
> > ScsiPortIninitialize.
> >
> > Gary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> > Sent: Monday, December 24, 2001 2:53 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> > No, you cannot.
> > EXEs and DLLs work in user mode and cannot be called from a driver.
> >
> > Max
> >
> > ----- Original Message -----
> > From: “akhil”
> > To: “NT Developers Interest List”
> > Sent: Monday, December 24, 2001 12:00 AM
> > Subject: [ntdev] Dll or Exe in Kernel mode
> >
> >
> > > Hello all,
> > >
> > > Can I Load
> > > 1) EXE
> > > 2) DLL
> > > in a kernel mode driver.
> > > How can I do it ?any sample code or idea will be a great help for me .
> > >
> > > Thanks in advance,
> > > Regards
> > > -Akhil
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@inland.net
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
That is if you want WHQL approval. There are TONS of drivers out there that
will NEVER see the inside of CompUsa or any other store and there do NOT
require Microsoft’s blessing. In my case, our driver simply updates the
Qlogic driver that delivers with the OS, but our driver does things that the
Qlogic folks didn’t want to support for customers that that need that kind
of support. And as to the XP MUST BE BUILT WITH build …
Why? If you take the time to set the IDE to the proper paths, and then use
the proper compiler and linker, how can the OS tell if you used IDE or
BUILD?
Gary
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
Sent: Wednesday, December 26, 2001 6:47 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel mode
Microsoft has declared from upon high that the IDE is to be ignored. The
command line compiler is shipped with the XP DDK and is the only supported
compiler. I haven’t started using the XP DDK other than as a reference, but
I guess the DDK group at Microsoft finally got fed up with the compiler
group releasing compilers that broke one or more of the DDKs.
I think that if want to have a driver that is included in the box of the
latest OS, you must use BUILD. M$ requires you to give them the source and
you must have WHQL approval.
----- Original Message -----
From: “Gary G. Little”
To: “NT Developers Interest List”
Sent: Wednesday, December 26, 2001 12:14 AM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> Again, not necessarily true. You can use any symbol other than Driver
entry
> that you want, but you do need to export it and specify it as the entry
> point. There is no magic in drivers. They are only DLLs with SYS as an
> extension and of course are linked with the kernel libraries that are not
> available to user mode. You must use the DDK but you do not HAVE to use
> BUILD. That tends to be a religious issue between using the Visual Studio
> IDE and the command line window folks.
>
> Gary
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
> Sent: Monday, December 24, 2001 12:24 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
> There is some truth that SCSIPORT & SMCLIB are nothing more than DLLs, but
> you can’t create them with the same tools and methods used to create DLLs
> that run in user mode. They are both .SYS drivers that have a
DriverEntry()
> exported function. They are both created using the DDK & BUILD.EXE. The
> .LIBs that permit linking to them are similar but not identical to a LIB
> used with a user mode DLL.
>
> CLASSPNP is another ‘kernel-mode DLL’. The source and build files are
> available in the DDK.
>
> ----- Original Message -----
> From: “Gary G. Little”
> To: “NT Developers Interest List”
> Sent: Monday, December 24, 2001 12:21 PM
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
>
> > Max,
> >
> > Whereas you are right on the EXE, you are wrong on the DLL. Remember, a
> > driver in NT/2000 is nothing more than a DLL. Case in point - SCSIPORT.
> You
> > link your mini-port driver with the import lib. When the mini-port
loads,
> it
> > goes through the DLL loading procedures when you the call
> > ScsiPortIninitialize.
> >
> > Gary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> > Sent: Monday, December 24, 2001 2:53 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> > No, you cannot.
> > EXEs and DLLs work in user mode and cannot be called from a driver.
> >
> > Max
> >
> > ----- Original Message -----
> > From: “akhil”
> > To: “NT Developers Interest List”
> > Sent: Monday, December 24, 2001 12:00 AM
> > Subject: [ntdev] Dll or Exe in Kernel mode
> >
> >
> > > Hello all,
> > >
> > > Can I Load
> > > 1) EXE
> > > 2) DLL
> > > in a kernel mode driver.
> > > How can I do it ?any sample code or idea will be a great help for me .
> > >
> > > Thanks in advance,
> > > Regards
> > > -Akhil
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@inland.net
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
—
You are currently subscribed to ntdev as: xxxxx@inland.net
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
If the Qlogic drivers are shipped with the OS and your drivers are not, it
is difficult, but not impossible, for a non-signed driver to replace a
signed driver. If someone runs the system file check utility your driver
will go away and it will revert to the signed drivers. There are many
categories of drivers that are not signed, but I was thinking that any M$
shipped driver is always signed.
I try to avoid using the IDE unless I have to, but how do you force the IDE
to use the compiler & linker in the DDK and not the one shipped with the
IDE? I am asking about the .NET compiler - VC++ 7? M$ is doing all they
can to stop the use of the IDE for drivers. The later build logic, Windows
2000 DDK onward, even allows applications to be built using BUILD. I think
the OS guys just got tired of getting screwed by the compiler group. I know
I sure was unhappy when VxDs would not work or working code only continued
to work with the new compiler when optimizations are disabled. Is there any
truth to the rumor that the XP DDK’s compiler contains special features &
keywords that are not present in the full .NET IDE? I know M$ has special
versions of their compilers that are used to build the OS and other
products, but are not released.
----- Original Message -----
From: “Gary G. Little”
To: “NT Developers Interest List”
Sent: Wednesday, December 26, 2001 1:28 PM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> That is if you want WHQL approval. There are TONS of drivers out there
that
> will NEVER see the inside of CompUsa or any other store and there do NOT
> require Microsoft’s blessing. In my case, our driver simply updates the
> Qlogic driver that delivers with the OS, but our driver does things that
the
> Qlogic folks didn’t want to support for customers that that need that kind
> of support. And as to the XP MUST BE BUILT WITH build …
>
> Why? If you take the time to set the IDE to the proper paths, and then use
> the proper compiler and linker, how can the OS tell if you used IDE or
> BUILD?
>
> Gary
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
> Sent: Wednesday, December 26, 2001 6:47 AM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
> Microsoft has declared from upon high that the IDE is to be ignored. The
> command line compiler is shipped with the XP DDK and is the only supported
> compiler. I haven’t started using the XP DDK other than as a reference,
but
> I guess the DDK group at Microsoft finally got fed up with the compiler
> group releasing compilers that broke one or more of the DDKs.
>
> I think that if want to have a driver that is included in the box of the
> latest OS, you must use BUILD. M$ requires you to give them the source
and
> you must have WHQL approval.
>
> ----- Original Message -----
> From: “Gary G. Little”
> To: “NT Developers Interest List”
> Sent: Wednesday, December 26, 2001 12:14 AM
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
>
> > Again, not necessarily true. You can use any symbol other than Driver
> entry
> > that you want, but you do need to export it and specify it as the entry
> > point. There is no magic in drivers. They are only DLLs with SYS as an
> > extension and of course are linked with the kernel libraries that are
not
> > available to user mode. You must use the DDK but you do not HAVE to use
> > BUILD. That tends to be a religious issue between using the Visual
Studio
> > IDE and the command line window folks.
> >
> > Gary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
> > Sent: Monday, December 24, 2001 12:24 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> > There is some truth that SCSIPORT & SMCLIB are nothing more than DLLs,
but
> > you can’t create them with the same tools and methods used to create
DLLs
> > that run in user mode. They are both .SYS drivers that have a
> DriverEntry()
> > exported function. They are both created using the DDK & BUILD.EXE.
The
> > .LIBs that permit linking to them are similar but not identical to a LIB
> > used with a user mode DLL.
> >
> > CLASSPNP is another ‘kernel-mode DLL’. The source and build files are
> > available in the DDK.
> >
> > ----- Original Message -----
> > From: “Gary G. Little”
> > To: “NT Developers Interest List”
> > Sent: Monday, December 24, 2001 12:21 PM
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> >
> > > Max,
> > >
> > > Whereas you are right on the EXE, you are wrong on the DLL. Remember,
a
> > > driver in NT/2000 is nothing more than a DLL. Case in point -
SCSIPORT.
> > You
> > > link your mini-port driver with the import lib. When the mini-port
> loads,
> > it
> > > goes through the DLL loading procedures when you the call
> > > ScsiPortIninitialize.
> > >
> > > Gary
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
> > > Sent: Monday, December 24, 2001 2:53 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> > >
> > > No, you cannot.
> > > EXEs and DLLs work in user mode and cannot be called from a driver.
> > >
> > > Max
> > >
> > > ----- Original Message -----
> > > From: “akhil”
> > > To: “NT Developers Interest List”
> > > Sent: Monday, December 24, 2001 12:00 AM
> > > Subject: [ntdev] Dll or Exe in Kernel mode
> > >
> > >
> > > > Hello all,
> > > >
> > > > Can I Load
> > > > 1) EXE
> > > > 2) DLL
> > > > in a kernel mode driver.
> > > > How can I do it ?any sample code or idea will be a great help for me
.
> > > >
> > > > Thanks in advance,
> > > > Regards
> > > > -Akhil
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@inland.net
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@inland.net
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> Why? If you take the time to set the IDE to the proper paths, and then use
the proper compiler and linker, how can the OS tell if you used IDE or
BUILD?
BUILD uses the guaranteed correct command-line options for compiler and linker.
You must abuse the IDE a lot to maintain the same options. This is the bad side.
The good side? Being able to find the compiler error by a double click? This is the only one.
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> can to stop the use of the IDE for drivers. The later build logic, Windows
2000 DDK onward, even allows applications to be built using BUILD.
It was always so, in NT4 DDK too.
Having BUILD and DIRS file is sometimes better then having lots of .MAKs generated from .DSPs (why on Earth MS invented this .DSP
idiocy in MSVC5? Earlier MSVC used the same .MAK for an IDE project as for command-line NMAKE, thus no buggy “Export Makefile”
option which generates absolute pathname dependency for any complex project tree) and a .BAT file which calls them all.
And - having BUILD and DIRS is MUCH better than a complex project with subprojects in the IDE.
truth to the rumor that the XP DDK’s compiler contains special features &
keywords that are not present in the full .NET IDE?
:-)))
Looks like MS will stop real C/C++ in the IDE and replace it with C# due to marketing reasons, and the only C/C++ compiler which
will survive will be the one in the DDK.
Just kidding :-)))
I know M$ has special
versions of their compilers that are used to build the OS and other
products, but are not released.
Are you sure MS will have the pain of maintaining 2 compilers - one for themselves, other for mere mortals?
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I have a solution to your problem, Max. I use CodeWright and create a batch
file in each project that calls other batch files to create the correct DDK,
SDK & compiler environment. Since this is done in a disposable DOS
(CMD.EXE) box, the changes to the environment disappear when the compile
finishes. The output is redirected to a file that the editor can use to
locate errors and warnings. I can compile with the NT4 DDK, Win 2000 DDK,
98DDK, MSVC 1.52c, etc. without changing my machine. I just switch projects
in CodeWright and it just works.
CodeWright also provides an interface with the IDE so you can edit files
with it and compile in the IDE when you have to do applications. I
generally try to avoid doing that, but sometimes I can’t.
----- Original Message -----
From: “Maxim S. Shatskih”
To: “NT Developers Interest List”
Sent: Wednesday, December 26, 2001 3:21 PM
Subject: [ntdev] Re: Dll or Exe in Kernel mode
> > Why? If you take the time to set the IDE to the proper paths, and then
use
> > the proper compiler and linker, how can the OS tell if you used IDE or
> > BUILD?
>
> BUILD uses the guaranteed correct command-line options for compiler and
linker.
> You must abuse the IDE a lot to maintain the same options. This is the bad
side.
>
> The good side? Being able to find the compiler error by a double click?
This is the only one.
>
> Max
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@yoshimuni.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Not only that but, as I keep discovering, unsigned drivers are
ubiquitous, even for commercial products available retail at compusa. A
lot of manufacturers went throught eh process to get their release 1.0
w2k drivers signed, but I think perhaps they decided that maintenance
release signing was a TPA and simply skipped it. My experience is that
about half of the drivers one actually installs are unsigned.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Wednesday, December 26, 2001 1:29 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel modeThat is if you want WHQL approval. There are TONS of drivers
out there that will NEVER see the inside of CompUsa or any
other store and there do NOT require Microsoft’s blessing. In
my case, our driver simply updates the Qlogic driver that
delivers with the OS, but our driver does things that the
Qlogic folks didn’t want to support for customers that that
need that kind of support. And as to the XP MUST BE BUILT
WITH build …Why? If you take the time to set the IDE to the proper paths,
and then use the proper compiler and linker, how can the OS
tell if you used IDE or BUILD?Gary
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
Sent: Wednesday, December 26, 2001 6:47 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel modeMicrosoft has declared from upon high that the IDE is to be
ignored. The command line compiler is shipped with the XP
DDK and is the only supported compiler. I haven’t started
using the XP DDK other than as a reference, but I guess the
DDK group at Microsoft finally got fed up with the compiler
group releasing compilers that broke one or more of the DDKs.I think that if want to have a driver that is included in the
box of the latest OS, you must use BUILD. M$ requires you to
give them the source and you must have WHQL approval.----- Original Message -----
From: “Gary G. Little”
> To: “NT Developers Interest List”
> Sent: Wednesday, December 26, 2001 12:14 AM
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
>
> > Again, not necessarily true. You can use any symbol other
> than Driver
> entry
> > that you want, but you do need to export it and specify it as the
> > entry point. There is no magic in drivers. They are only
> DLLs with SYS
> > as an extension and of course are linked with the kernel libraries
> > that are not available to user mode. You must use the DDK
> but you do
> > not HAVE to use BUILD. That tends to be a religious issue between
> > using the Visual Studio IDE and the command line window folks.
> >
> > Gary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
> > Sent: Monday, December 24, 2001 12:24 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> > There is some truth that SCSIPORT & SMCLIB are nothing more
> than DLLs,
> > but you can’t create them with the same tools and methods used to
> > create DLLs that run in user mode. They are both .SYS drivers that
> > have a
> DriverEntry()
> > exported function. They are both created using the DDK &
> BUILD.EXE.
> > The .LIBs that permit linking to them are similar but not
> identical to
> > a LIB used with a user mode DLL.
> >
> > CLASSPNP is another ‘kernel-mode DLL’. The source and
> build files are
> > available in the DDK.
> >
> > ----- Original Message -----
> > From: “Gary G. Little”
> > To: “NT Developers Interest List”
> > Sent: Monday, December 24, 2001 12:21 PM
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> >
> > > Max,
> > >
> > > Whereas you are right on the EXE, you are wrong on the DLL.
> > > Remember, a driver in NT/2000 is nothing more than a DLL.
> Case in
> > > point - SCSIPORT.
> > You
> > > link your mini-port driver with the import lib. When the mini-port
> loads,
> > it
> > > goes through the DLL loading procedures when you the call
> > > ScsiPortIninitialize.
> > >
> > > Gary
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S.
> > > Shatskih
> > > Sent: Monday, December 24, 2001 2:53 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> > >
> > > No, you cannot.
> > > EXEs and DLLs work in user mode and cannot be called from
> a driver.
> > >
> > > Max
> > >
> > > ----- Original Message -----
> > > From: “akhil”
> > > To: “NT Developers Interest List”
> > > Sent: Monday, December 24, 2001 12:00 AM
> > > Subject: [ntdev] Dll or Exe in Kernel mode
> > >
> > >
> > > > Hello all,
> > > >
> > > > Can I Load
> > > > 1) EXE
> > > > 2) DLL
> > > > in a kernel mode driver.
> > > > How can I do it ?any sample code or idea will be a
> great help for
> > > > me .
> > > >
> > > > Thanks in advance,
> > > > Regards
> > > > -Akhil
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> xxxxx@storagecraft.com
> > > > To unsubscribe send a blank email to
> > > > leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@inland.net To
> > > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> xxxxx@yoshimuni.com To
> > > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@inland.net To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@inland.net
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@hollistech.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I think that is a little on the harsh side. The IDE is fine, you just
really have to use the proper compiler and linker and include files.
This is not an onerous or irrational requirement. If you really want to
have a visual studio wizard thing, you can create one that works with
XP, you just have to understand what the rules are and follow them.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David J. Craig
Sent: Wednesday, December 26, 2001 9:47 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel modeMicrosoft has declared from upon high that the IDE is to be
ignored. The command line compiler is shipped with the XP
DDK and is the only supported compiler. I haven’t started
using the XP DDK other than as a reference, but I guess the
DDK group at Microsoft finally got fed up with the compiler
group releasing compilers that broke one or more of the DDKs.I think that if want to have a driver that is included in the
box of the latest OS, you must use BUILD. M$ requires you to
give them the source and you must have WHQL approval.----- Original Message -----
From: “Gary G. Little”
> To: “NT Developers Interest List”
> Sent: Wednesday, December 26, 2001 12:14 AM
> Subject: [ntdev] Re: Dll or Exe in Kernel mode
>
>
> > Again, not necessarily true. You can use any symbol other
> than Driver
> entry
> > that you want, but you do need to export it and specify it as the
> > entry point. There is no magic in drivers. They are only
> DLLs with SYS
> > as an extension and of course are linked with the kernel libraries
> > that are not available to user mode. You must use the DDK
> but you do
> > not HAVE to use BUILD. That tends to be a religious issue between
> > using the Visual Studio IDE and the command line window folks.
> >
> > Gary
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of David J. Craig
> > Sent: Monday, December 24, 2001 12:24 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> > There is some truth that SCSIPORT & SMCLIB are nothing more
> than DLLs,
> > but you can’t create them with the same tools and methods used to
> > create DLLs that run in user mode. They are both .SYS drivers that
> > have a
> DriverEntry()
> > exported function. They are both created using the DDK &
> BUILD.EXE.
> > The .LIBs that permit linking to them are similar but not
> identical to
> > a LIB used with a user mode DLL.
> >
> > CLASSPNP is another ‘kernel-mode DLL’. The source and
> build files are
> > available in the DDK.
> >
> > ----- Original Message -----
> > From: “Gary G. Little”
> > To: “NT Developers Interest List”
> > Sent: Monday, December 24, 2001 12:21 PM
> > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> >
> >
> > > Max,
> > >
> > > Whereas you are right on the EXE, you are wrong on the DLL.
> > > Remember, a driver in NT/2000 is nothing more than a DLL.
> Case in
> > > point - SCSIPORT.
> > You
> > > link your mini-port driver with the import lib. When the mini-port
> loads,
> > it
> > > goes through the DLL loading procedures when you the call
> > > ScsiPortIninitialize.
> > >
> > > Gary
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S.
> > > Shatskih
> > > Sent: Monday, December 24, 2001 2:53 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: Dll or Exe in Kernel mode
> > >
> > > No, you cannot.
> > > EXEs and DLLs work in user mode and cannot be called from
> a driver.
> > >
> > > Max
> > >
> > > ----- Original Message -----
> > > From: “akhil”
> > > To: “NT Developers Interest List”
> > > Sent: Monday, December 24, 2001 12:00 AM
> > > Subject: [ntdev] Dll or Exe in Kernel mode
> > >
> > >
> > > > Hello all,
> > > >
> > > > Can I Load
> > > > 1) EXE
> > > > 2) DLL
> > > > in a kernel mode driver.
> > > > How can I do it ?any sample code or idea will be a
> great help for
> > > > me .
> > > >
> > > > Thanks in advance,
> > > > Regards
> > > > -Akhil
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> xxxxx@storagecraft.com
> > > > To unsubscribe send a blank email to
> > > > leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@inland.net To
> > > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> xxxxx@yoshimuni.com To
> > > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@inland.net To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@yoshimuni.com To
> > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@hollistech.com To unsubscribe send a blank email to
> leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> -----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim
S. Shatskih
Sent: Wednesday, December 26, 2001 3:21 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel mode> Why? If you take the time to set the IDE to the proper
paths, and then
> use the proper compiler and linker, how can the OS tell if you used
> IDE or BUILD?BUILD uses the guaranteed correct command-line options for
compiler and linker. You must abuse the IDE a lot to maintain
the same options. This is the bad side.The good side? Being able to find the compiler error by a
double click? This is the only one.
Source code browsing using bsc files. This is actually the only reason I
continue to use the IDE.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Well, that depends on how one defines abuse. I believe Oney talked about
changing his wizard to accommodate XP and the new compilers.
Gary
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Maxim S. Shatskih
Sent: Wednesday, December 26, 2001 12:21 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Dll or Exe in Kernel mode
Why? If you take the time to set the IDE to the proper paths, and then use
the proper compiler and linker, how can the OS tell if you used IDE or
BUILD?
BUILD uses the guaranteed correct command-line options for compiler and
linker.
You must abuse the IDE a lot to maintain the same options. This is the bad
side.
The good side? Being able to find the compiler error by a double click? This
is the only one.
Max
You are currently subscribed to ntdev as: xxxxx@inland.net
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com