Re[2]: Large data in registry

NTFSD
1

> Anyway that part of documentation is for win32 application and for drivers

situation is not same.

There are only one registry are only once on the PC, so what
applies to the Win32 registry interface, that also applies to NT
registry interface. It’s limitation of registry itself,
not limitation of API.

update. Next argue for registry were that driver will support only XP and
higher versions so there is no limit on whole registry size but I will
extend chunk size to 2 MB to make reading faster for case that config grow.

Anyway - if I would, eventually, find that an application increased
my registry size to 100MB, that application is going
to be thrown away to Recycle Bin with the speed of light :slight_smile:

BTW why can’t you use files ? Store configuration in registry but data
in file. They are not accessible at boot time if they are outside
%SystemDir%, that’s true, is that problem for your software ?

L.

2

> There are only one registry are only once on the PC, so what

applies to the Win32 registry interface, that also applies to NT
registry interface. It’s limitation of registry itself,
not limitation of API.

That 2 kB for registry is not limitation but best practise and best practise
for boot loading driver will surely be different.

Anyway - if I would, eventually, find that an application increased
my registry size to 100MB, that application is going
to be thrown away to Recycle Bin with the speed of light :slight_smile:

Yes, speed of light is right speed to get rid of such application :slight_smile: but
fortunately is not case of my driver. You should pick approx. 2 milions
individual folders and files to make config data such big. I just state
really extreme example to make discussion more interesting :slight_smile:

BTW why can’t you use files ? Store configuration in registry but data
in file. They are not accessible at boot time if they are outside
%SystemDir%, that’s true, is that problem for your software ?

I don’t like “test if already possible to read loop” concept in
initialization. To read directly from disk is actually beyond my time and
skill potential. I dont know (not found) about another possible solution.

3

Jan:

It’s (using a file) is really not that hard, and there are plenty of
examples of it in the documentation and actual source examples as well.

ms-help://MS.WDK.v10.6001/Kernel_d/hh/Kernel_d/Other_e2d82c31-1c65-4d34-
88e2-74514e59343d.xml.htm (this is an MSDN local link; just search the
web if you don’t have the April 2007 MSDN installed)

It’s not like it would be the end of the world or anything, but, as
every reply to this question has said, nobody wants stuff like this in
their registry. While you certainly are under no obligation to
implement what is suggested here, I do wonder why you asked this
question in the first place if you’re not going to even consider doing
so, as “I don’t think I can” is not a very good reason. If you really
believe that, don’t write drivers, and if you just don’t feel like
learning something new, which is no harder than using the registry,
don’t write drivers.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Milan
Sent: Wednesday, September 05, 2007 06:21
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re[2]: Large data in registry

There are only one registry are only once on the PC, so what
applies to the Win32 registry interface, that also applies to NT
registry interface. It’s limitation of registry itself,
not limitation of API.

That 2 kB for registry is not limitation but best practise and best
practise
for boot loading driver will surely be different.

Anyway - if I would, eventually, find that an application increased
my registry size to 100MB, that application is going
to be thrown away to Recycle Bin with the speed of light :slight_smile:

Yes, speed of light is right speed to get rid of such application :slight_smile: but
fortunately is not case of my driver. You should pick approx. 2 milions
individual folders and files to make config data such big. I just state
really extreme example to make discussion more interesting :slight_smile:

BTW why can’t you use files ? Store configuration in registry but data
in file. They are not accessible at boot time if they are outside
%SystemDir%, that’s true, is that problem for your software ?

I don’t like “test if already possible to read loop” concept in
initialization. To read directly from disk is actually beyond my time
and
skill potential. I dont know (not found) about another possible
solution.

NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Hi,
thanks for reply.
What is that example about? About using file or about reading file during
SYSTEM BOOT?

In first case I’m using files a lot in my driver and have no problem to
read, write, … and in fact it could be easier to keep that config data in
file but there is limitation during system boot .

In second case pls be more exact in what is that example about because I
cannot find it.

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
Jan:

It’s (using a file) is really not that hard, and there are plenty of
examples of it in the documentation and actual source examples as well.

ms-help://MS.WDK.v10.6001/Kernel_d/hh/Kernel_d/Other_e2d82c31-1c65-4d34-
88e2-74514e59343d.xml.htm (this is an MSDN local link; just search the
web if you don’t have the April 2007 MSDN installed)

It’s not like it would be the end of the world or anything, but, as
every reply to this question has said, nobody wants stuff like this in
their registry. While you certainly are under no obligation to
implement what is suggested here, I do wonder why you asked this
question in the first place if you’re not going to even consider doing
so, as “I don’t think I can” is not a very good reason. If you really
believe that, don’t write drivers, and if you just don’t feel like
learning something new, which is no harder than using the registry,
don’t write drivers.

mm

5

Jan:

http://support.microsoft.com/kb/891805

You’ve got to learn to google.

Yes, there is a limitation on where the file can be stored; if that’s a
deal breaker, than you can’t do this.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Milan
Sent: Wednesday, September 05, 2007 10:55
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re[2]: Large data in registry

Hi,
thanks for reply.
What is that example about? About using file or about reading file
during
SYSTEM BOOT?

In first case I’m using files a lot in my driver and have no problem to
read, write, … and in fact it could be easier to keep that config data
in
file but there is limitation during system boot .

In second case pls be more exact in what is that example about because I
cannot find it.

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
Jan:

It’s (using a file) is really not that hard, and there are plenty of
examples of it in the documentation and actual source examples as well.

ms-help://MS.WDK.v10.6001/Kernel_d/hh/Kernel_d/Other_e2d82c31-1c65-4d34-
88e2-74514e59343d.xml.htm (this is an MSDN local link; just search the
web if you don’t have the April 2007 MSDN installed)

It’s not like it would be the end of the world or anything, but, as
every reply to this question has said, nobody wants stuff like this in
their registry. While you certainly are under no obligation to
implement what is suggested here, I do wonder why you asked this
question in the first place if you’re not going to even consider doing
so, as “I don’t think I can” is not a very good reason. If you really
believe that, don’t write drivers, and if you just don’t feel like
learning something new, which is no harder than using the registry,
don’t write drivers.

mm

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

6

Yes maybe I got to learn to google :slight_smile: How you found it? I put all
combination of local file you mentioned with no success.

Anyway I found exactly same link in msdn.microsoft.com but most informations
I’m using are from http://www.osronline.com/showThread.cfm?link=69255 which
make me decide to use registry.

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
Jan:

http://support.microsoft.com/kb/891805

You’ve got to learn to google.

Yes, there is a limitation on where the file can be stored; if that’s a
deal breaker, than you can’t do this.

mm

7

mm,

You do know that doesn't work at all for a boot start driver, right? OK,
maybe *I* don't know that. I do know that it didn't work when *I* was the
boot device, so I had to be up and running before any FS access would work,
so I had to put a binary in the registry, as the alternative would have been
to somehow use the FS support in ntldr. :slight_smile: Then again, it was a few 4K
pages, not hundreds.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

"Martin O'Brien" wrote in message
news:xxxxx@ntfsd...
Jan:

How to open a file from a kernel mode device driver and how to read from or write to the file - Microsoft Support

You've got to learn to google.

Yes, there is a limitation on where the file can be stored; if that's a
deal breaker, than you can't do this.

mm

8

Phil:

I just searched for a kernel mode file example; I never really
considered the implications of boot. Not one of my finer moments.

Thanks,

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Philip D. Barila
Sent: Wednesday, September 05, 2007 11:42
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re[2]: Large data in registry

mm,

You do know that doesn't work at all for a boot start driver, right?
OK,
maybe *I* don't know that. I do know that it didn't work when *I* was
the
boot device, so I had to be up and running before any FS access would
work,
so I had to put a binary in the registry, as the alternative would have
been
to somehow use the FS support in ntldr. :slight_smile: Then again, it was a few
4K
pages, not hundreds.

Phil

Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

"Martin O'Brien" wrote in message
news:xxxxx@ntfsd...
Jan:

How to open a file from a kernel mode device driver and how to read from or write to the file - Microsoft Support

You've got to learn to google.

Yes, there is a limitation on where the file can be stored; if that's a
deal breaker, than you can't do this.

mm

---
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
OSR Seminars – OSR

You are currently subscribed to ntfsd as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

9

Jan:

Please accept my apologies. As Phil just pointed out, I missed the
whole point here. Sorry about that, and please disregard what I wrote.

mm

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Milan
Sent: Wednesday, September 05, 2007 11:36
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re[2]: Large data in registry

Yes maybe I got to learn to google :slight_smile: How you found it? I put all
combination of local file you mentioned with no success.

Anyway I found exactly same link in msdn.microsoft.com but most
informations
I’m using are from http://www.osronline.com/showThread.cfm?link=69255
which
make me decide to use registry.

“Martin O’Brien” wrote in message
news:xxxxx@ntfsd…
Jan:

http://support.microsoft.com/kb/891805

You’ve got to learn to google.

Yes, there is a limitation on where the file can be stored; if that’s a
deal breaker, than you can’t do this.

mm

—
NTFSD is sponsored by OSR

For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

You are currently subscribed to ntfsd as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com