Re: Creating a Windows File System Driver...
- From: "Don Burn" <burn@xxxxxxxxxxxxxxxx>
- Date: Thu, 14 Apr 2005 06:58:57 -0400
Please point out some useful file systems done with the GNU ntifs.h, I know
of no commercial product that has used it. The claim that the IFS kit was
not useful, begs the question why a well documented kit, with the sources to
real file systems is not useful. The fact that the IFS kit has had a
library to make redirectors easier I geuss is also not useful.
If you are complaining about the price remember that till not long ago, you
needed MSDN (at then $495) and VC++ (at then roughly $395) to build a driver
for windows period. A professional is someone who recognizes that they may
have to spend money for quality tools. If you don't like that I suggest you
develop for Linux.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"Dr Pizza" <drpizza@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OJNGCPIQFHA.1392@xxxxxxxxxxxxxxxxxxxxxxx
> Actually, for some reason that's not entirely clear to me (not that I'm
> complaining!) the IFS kit has had its price slashed. It's now apparently
> $109. Not just for upgrades, for everyone.
>
> The ntifs.h is accurate enough for a number of useful drivers. Which is
> more than can be said for the IFS kit which was, until recently,
> prohibitively expensive, for no real benefit to end-users.
>
> "Don Burn" <burn@xxxxxxxxxxxxxxxx> wrote in message
> news:nk87e.3600$OU6.301@xxxxxxxxxxx
>> First you are going to need the Windows IFS kit
>> http://www.microsoft.com/whdc/DevTools/IFSKit/default.mspx this will cost
>> you about $1000. Second you should probably get training from OSR this
>> costs $3450. The locate a copy of Rajeev Nagar's "Windows NT File
>> System Internals", it is many years out of date and used copies are
>> expensive, but it is the only book on the subject. Also, go to
>> http://www.osronline.com/ and sign up for the NTFSD newsgroup where file
>> system types hang out. Then if you are highly experienced in Windows
>> drivers, expect 18-24 months of hard work to have a file system.
>>
>> Note, there is a piece of crap of open source that implies it is a header
>> for writing Windows file systems. The contents of the header are in part
>> stolen, and are full of bugs. Attempting to use this header is a great
>> way to slow down your efforts. The real Windows IFS kit contains
>> documentation and samples including FAT and CDFS.
>>
>>
>> --
>> Don Burn (MVP, Windows DDK)
>> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> Remove StopSpam from the email to reply
>>
>>
>>
>> "eagleone" <eagleone@xxxxxxxxx> wrote in message
>> news:425cc976$0$22159$626a14ce@xxxxxxxxxxxxxxx
>>> It may be hard to do but I'd like to know how to create my own file
>>> system for windows? Do you know any related papers or source free
>>> drivers covering this subject.
>>>
>>> Thanks.
>>
>>
>
>
.
- Follow-Ups:
- Re: Creating a Windows File System Driver...
- From: Dr Pizza
- Re: Creating a Windows File System Driver...
- From: Slava M. Usov
- Re: Creating a Windows File System Driver...
- References:
- Re: Creating a Windows File System Driver...
- From: Don Burn
- Re: Creating a Windows File System Driver...
- From: Dr Pizza
- Re: Creating a Windows File System Driver...
- Prev by Date: Re: Lock pages in memory
- Next by Date: Re: Wrapper class or function (10 bytes to double).
- Previous by thread: Re: Creating a Windows File System Driver...
- Next by thread: Re: Creating a Windows File System Driver...
- Index(es):
Relevant Pages
|
