Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver from Visual C++.
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
You can do any of the following:
- use the ddk command line tools, as in ‘build -cZ’;
- goto my website ( www.hollistech.com http:)and> )and fetch forth from there ddkbuild.bat after reading the article
on integrating with visual studio;
3) try one of those wizard tools or such and hope they work for your
driver.
1) is of course the recommended microsoft way. It is ugly antiquated
painful dull annoying ridiculous bad evil etc. It does however work, and
at least theoretically if there are problems those ddk folks will be all
over it like flies on poop, and have it fixed in no time.
2) ddkbuild.bat is of course my preferred method. It is simply a
frontend to the ddk toolset, and if your driver builds using (1) above,
then it should build with no problem inside the visual studio ide using
ddkbuild. It allows for most everything that visual studio does except
for things like dependency checking and some project management stuff.
It is of course not supported by microsoft, and if there are problems
you have to appeal to my good nature to get them resolved. As anyone who
knows me can tell you, that is a tough road to hoe
The again I am
not nearly as rich or good looking as billg or jeanval.
3) wizards, blech.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ratmil Torres
Sent: Friday, October 12, 2001 5:45 PM
To: File Systems Developers
Subject: [ntfsd] Build using Visual C++ 6.0
Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver
from Visual C++.
—
You are currently subscribed to ntfsd as: xxxxx@hollistech.com
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</http:>
I did it this way. First, I built a project using build utility. The project doesn't have to be big. One source file is enough. Then look through the build log and copy compiler/linker options and paste them in VC in projects settings. It really works 
----- Original Message -----
From: Ratmil Torres
To: File Systems Developers
Sent: Saturday, October 13, 2001 12:45 AM
Subject: [ntfsd] Build using Visual C++ 6.0
Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver from Visual C++.
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
That works fine, except it is very fragile. It will break, for example,
if you attempt to use the XP ddk header files. It is highly manual and
thus prone to human error. It would difficult, for example, to provide
this as a repeatable process for a team of software engineers.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alexey Logachyov
Sent: Saturday, October 13, 2001 4:11 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0
I did it this way. First, I built a project using build utility. The
project doesn’t have to be big. One source file is enough. Then look
through the build log and copy compiler/linker options and paste them in
VC in projects settings. It really works
----- Original Message -----
From: Ratmil Torres mailto:xxxxx
To: File Systems Developers mailto:xxxxx
Sent: Saturday, October 13, 2001 12:45 AM
Subject: [ntfsd] Build using Visual C++ 6.0
Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver
from Visual C++.
—
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
mailto:leave-ntfsd-
—
You are currently subscribed to ntfsd as: xxxxx@hollistech.com
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</mailto:leave-ntfsd-></mailto:xxxxx></mailto:xxxxx>
MessageLook! Microsoft does not suppose you to build drivers with VC and does not provide any native support. If something changes you would have do this operation once again. That would take like 5 or 10 minutes. You of course may write a special plug-in or something. But you would spare much more time then.
OK. You don't want this way I can suggest another one. As far as I understand the only reason for wanting to build drivers in VC is its convenient editor (if you need anything more, like specialized settings, you're gonna need special plug-ins, that's for sure). So, you create a usual project along with 'sources' file and all other stuff. Then you add this to you VC project and put 'exclude from build' for all sources. In the 'sources' file settings you set 'perform custom build' or something -- I am too lazy to go and see how it is called right now -- and write 'build' in command line commands. I think you understand what I mean. You still have to edit the 'sources' file manualy (the previous method get rid of this).
So, it's up to you what method to use. Look also in the internet. Many people have the same problem. And many people found their way through it.
----- Original Message -----
From: Mark Roddy
To: File Systems Developers
Sent: Saturday, October 13, 2001 17:01
Subject: [ntfsd] Re: Build using Visual C++ 6.0
That works fine, except it is very fragile. It will break, for example, if you attempt to use the XP ddk header files. It is highly manual and thus prone to human error. It would difficult, for example, to provide this as a repeatable process for a team of software engineers.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alexey Logachyov
Sent: Saturday, October 13, 2001 4:11 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0
I did it this way. First, I built a project using build utility. The project doesn't have to be big. One source file is enough. Then look through the build log and copy compiler/linker options and paste them in VC in projects settings. It really works
----- Original Message -----
From: Ratmil Torres
To: File Systems Developers
Sent: Saturday, October 13, 2001 12:45 AM
Subject: [ntfsd] Build using Visual C++ 6.0
Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver from Visual C++.
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: xxxxx@hollistech.com
To unsubscribe send a blank email to leave-ntfsd-$subst('Recip.MemberIDChar')@lists.osr.com
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
I use Numega srctodsp.exe. It will convert my sources to a dsp and dsw
file. Then, I spend some time tweaking and setting up the specifics (2k,
XP, etc…) and then I save the DSP file in my source control so that
all of my other developers can use the dsp. Our principle developer
hates it and uses build instead. I prefer the IDE and DSP file for
interim development and builds (I like source browsing of the IFS kit
and DDK headers). When I am ready to make the official builds, I revert
back to using build.
Jamey
xxxxx@storagecraft.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Saturday, October 13, 2001 7:01 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0
That works fine, except it is very fragile. It will break, for example,
if you attempt to use the XP ddk header files. It is highly manual and
thus prone to human error. It would difficult, for example, to provide
this as a repeatable process for a team of software engineers.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alexey Logachyov
Sent: Saturday, October 13, 2001 4:11 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0
I did it this way. First, I built a project using build utility. The
project doesn’t have to be big. One source file is enough. Then look
through the build log and copy compiler/linker options and paste them in
VC in projects settings. It really works
----- Original Message -----
From: Ratmil Torres mailto:xxxxx
To: File Systems Developers mailto:xxxxx
Sent: Saturday, October 13, 2001 12:45 AM
Subject: [ntfsd] Build using Visual C++ 6.0
Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver
from Visual C++.
—
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
mailto:leave-ntfsd-
—
You are currently subscribed to ntfsd as: xxxxx@hollistech.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
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</mailto:leave-ntfsd-></mailto:xxxxx></mailto:xxxxx>
MessageI use CodeWright as my editor and have it execute a batch file that causes the correct environment for the normal build, nmake, etc. utilities to run. No path, lib, or include statements point to any DDK or compiler. This permits me to build 16-bit command line aps, VXDs using the 95, 98, or Me DDK, WDM drivers using the 98, Me, or W2K DDK, NT drivers using NT, W2K, or XP DDK, as required. I have to enter some environment variables that point to the various pieces and the batch files with each project call the appropriate setup files. This gives me an output that CodeWright can use to find errors & warnings, as well as the ability to build any with free or checked as desired.
----- Original Message -----
From: Jamey Kirby
To: File Systems Developers
Sent: Saturday, October 13, 2001 12:26 PM
Subject: [ntfsd] Re: Build using Visual C++ 6.0
I use Numega srctodsp.exe. It will convert my sources to a dsp and dsw file. Then, I spend some time tweaking and setting up the specifics (2k, XP, etc...) and then I save the DSP file in my source control so that all of my other developers can use the dsp. Our principle developer hates it and uses build instead. I prefer the IDE and DSP file for interim development and builds (I like source browsing of the IFS kit and DDK headers). When I am ready to make the official builds, I revert back to using build.
Jamey
xxxxx@storagecraft.com
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Saturday, October 13, 2001 7:01 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0
That works fine, except it is very fragile. It will break, for example, if you attempt to use the XP ddk header files. It is highly manual and thus prone to human error. It would difficult, for example, to provide this as a repeatable process for a team of software engineers.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alexey Logachyov
Sent: Saturday, October 13, 2001 4:11 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0
I did it this way. First, I built a project using build utility. The project doesn't have to be big. One source file is enough. Then look through the build log and copy compiler/linker options and paste them in VC in projects settings. It really works
----- Original Message -----
From: Ratmil Torres
To: File Systems Developers
Sent: Saturday, October 13, 2001 12:45 AM
Subject: [ntfsd] Build using Visual C++ 6.0
Hi, I have installed IFS Kit and Visual C++ 6.0. How can build a driver from Visual C++.
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: xxxxx@hollistech.com
To unsubscribe send a blank email to leave-ntfsd-$subst('Recip.MemberIDChar')@lists.osr.com
You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
To unsubscribe send a blank email to leave-ntfsd-$subst('Recip.MemberIDChar')@lists.osr.com ---
You are currently subscribed to ntfsd as: xxxxx@mindspring.com
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
Message>OK. You don’t want this way I can suggest another one. As far as I understand the only
reason for wanting to build drivers in VC is its convenient editor (if you need anything more,
No.
The only reason is auto-jump-to-error-line on double-click in Output window. For me, this reason is minor and I’m satisfied with
BUILD.
You can use MSVC’s editor - as editor only - together with BUILD.
Max
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
> ----------
From: Maxim S. Shatskih[SMTP:xxxxx@storagecraft.com]
Reply To: File Systems Developers
Sent: Sunday, October 14, 2001 7:38 AM
To: File Systems Developers
Subject: [ntfsd] Re: Build using Visual C++ 6.0Message>OK. You don’t want this way I can suggest another one. As far as I
understand the only
>reason for wanting to build drivers in VC is its convenient editor (if
you need anything more,No.
The only reason is auto-jump-to-error-line on double-click in Output
window. For me, this reason is minor and I’m satisfied with
BUILD.
Maybe for you. Above is obvious for me and I also can’t work efficiently
without a good symbol browser and many other things which make and editor
good one. Sure, it is possible to write code in notepad or using “copy con”
or even VC editor 
(sorry for OT)
Best regards,
Michal Vodicka
Veridicom
(RKK - Skytale)
[WWW: http://www.veridicom.com , http://www.skytale.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
> Maybe for you. Above is obvious for me and I also can’t work efficiently
without a good symbol browser and many other things which make and editor
good one. Sure, it is possible to write code in notepad or using “copy con”
or even VC editor(sorry for OT)
“Some people love watermelons, and some - pork cartilage”.
Russian proverb.
Max
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
Hi, people!
Could you tell me how I could get long file name in the IFSFN_WRITE
routine inside the IFS hook driver.
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
By sending an IRP_MJ_QUERY_INFORMATION/FileNameInformation to the
lower driver. That retrieves the LFN. FileAlternateNameInformation
retrieves the SFN.
Regards, Dejan.
Ilia Rabinovich wrote:
Hi, people!
Could you tell me how I could get long file name in the IFSFN_WRITE
routine inside the IFS hook driver.
You are currently subscribed to ntfsd as: xxxxx@alfasp.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com
–
Kind regards, Dejan M. CEO Alfa Co. www.alfasp.com
E-mail: xxxxx@alfasp.com
ICQ#: 56570367
Alfa File Monitor - File monitoring system for Win32 developers.
Alfa File Protector - File protection and hiding system for Win32
developers.
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