ReInvoking MiniportInitialize from protocol driver

Hi experts,

I want to make Ndis call (reinvoke) my MiniportInitialize from protocol
driver. This has to be done without removing and reinserting my device.


First iam trying to make Ndis to call my MiniportHalt & then recall
MiniportInitialize.


Any suggestion welcome

Thanks in advance

Stephan
Wed Oct 11 08:46:14 CDT 2006

AFAIK, the only way to disable and re-enable an NDIS miniport driver is
via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
SetupDi can AFAIK only be used from user-mode, you will need to put the
code in e.g. some Service or a Notify Object for the protocol.

Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
only be used if you have the miniport handle.

Stephan
---
haideepu wrote:
> Hi experts,
>
> I want to make Ndis call (reinvoke) my MiniportInitialize from protocol
> driver. This has to be done without removing and reinserting my device.
>
>
> First iam trying to make Ndis to call my MiniportHalt & then recall
> MiniportInitialize.
>
>
> Any suggestion welcome
>
> Thanks in advance

haideepu
Thu Oct 12 00:18:59 CDT 2006

Hi Stephan

Thanx for your reply...
Our driver doestn't have Intermediate driver
...NdisIMDeInitializeDeviceInstance() can only be used with
Intermediate driver.....We tried by calling the same with miniport
handle from protocol driver ...But we r getting
NDIS_STATUS_FAILURE.....

And More over We want to call MiniportInitialize() without being
DriverEntry Called. If we use SetupDi calls that may unload driver,
which shouldn't happen...

We are searching for some way to make Ndis invoke MiniportHalt() and
then invoke MiniportInitialize(), where it can read the changed
registry settings....We will change the registry settings from our
application before making our protocol driver to invoke
MiniportHalt.....When MiniportInitialize gets called ...it can read the
changed registry settings..

Suggestions plzzzzz

Thanx in adv

---Pradeep




Stephan Wolf [MVP] wrote:
> AFAIK, the only way to disable and re-enable an NDIS miniport driver is
> via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
> SetupDi can AFAIK only be used from user-mode, you will need to put the
> code in e.g. some Service or a Notify Object for the protocol.
>
> Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
> only be used if you have the miniport handle.
>
> Stephan
> ---
> haideepu wrote:
> > Hi experts,
> >
> > I want to make Ndis call (reinvoke) my MiniportInitialize from protocol
> > driver. This has to be done without removing and reinserting my device.
> >
> >
> > First iam trying to make Ndis to call my MiniportHalt & then recall
> > MiniportInitialize.
> >
> >
> > Any suggestion welcome
> >
> > Thanks in advance

soviet_bloke
Thu Oct 12 00:38:50 CDT 2006

Hi mate

> And More over We want to call MiniportInitialize() without being
> DriverEntry Called. If we use SetupDi calls that may unload driver,
> which shouldn't happen...

But why do you present the above requirement???? What are your overall
objectives????

Anton Bassov

haideepu wrote:
> Hi Stephan
>
> Thanx for your reply...
> Our driver doestn't have Intermediate driver
> ...NdisIMDeInitializeDeviceInstance() can only be used with
> Intermediate driver.....We tried by calling the same with miniport
> handle from protocol driver ...But we r getting
> NDIS_STATUS_FAILURE.....
>
> And More over We want to call MiniportInitialize() without being
> DriverEntry Called. If we use SetupDi calls that may unload driver,
> which shouldn't happen...
>
> We are searching for some way to make Ndis invoke MiniportHalt() and
> then invoke MiniportInitialize(), where it can read the changed
> registry settings....We will change the registry settings from our
> application before making our protocol driver to invoke
> MiniportHalt.....When MiniportInitialize gets called ...it can read the
> changed registry settings..
>
> Suggestions plzzzzz
>
> Thanx in adv
>
> ---Pradeep
>
>
>
>
> Stephan Wolf [MVP] wrote:
> > AFAIK, the only way to disable and re-enable an NDIS miniport driver is
> > via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
> > SetupDi can AFAIK only be used from user-mode, you will need to put the
> > code in e.g. some Service or a Notify Object for the protocol.
> >
> > Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
> > only be used if you have the miniport handle.
> >
> > Stephan
> > ---
> > haideepu wrote:
> > > Hi experts,
> > >
> > > I want to make Ndis call (reinvoke) my MiniportInitialize from protocol
> > > driver. This has to be done without removing and reinserting my device.
> > >
> > >
> > > First iam trying to make Ndis to call my MiniportHalt & then recall
> > > MiniportInitialize.
> > >
> > >
> > > Any suggestion welcome
> > >
> > > Thanks in advance

haideepu
Thu Oct 12 00:47:59 CDT 2006

Hi

My Objective is simple....I want to reinvoke my MiniportInitialize
without removing my device

any advice??

--Pradeep



soviet_bloke@hotmail.com wrote:
> Hi mate
>
> > And More over We want to call MiniportInitialize() without being
> > DriverEntry Called. If we use SetupDi calls that may unload driver,
> > which shouldn't happen...
>
> But why do you present the above requirement???? What are your overall
> objectives????
>
> Anton Bassov
>
> haideepu wrote:
> > Hi Stephan
> >
> > Thanx for your reply...
> > Our driver doestn't have Intermediate driver
> > ...NdisIMDeInitializeDeviceInstance() can only be used with
> > Intermediate driver.....We tried by calling the same with miniport
> > handle from protocol driver ...But we r getting
> > NDIS_STATUS_FAILURE.....
> >
> > And More over We want to call MiniportInitialize() without being
> > DriverEntry Called. If we use SetupDi calls that may unload driver,
> > which shouldn't happen...
> >
> > We are searching for some way to make Ndis invoke MiniportHalt() and
> > then invoke MiniportInitialize(), where it can read the changed
> > registry settings....We will change the registry settings from our
> > application before making our protocol driver to invoke
> > MiniportHalt.....When MiniportInitialize gets called ...it can read the
> > changed registry settings..
> >
> > Suggestions plzzzzz
> >
> > Thanx in adv
> >
> > ---Pradeep
> >
> >
> >
> >
> > Stephan Wolf [MVP] wrote:
> > > AFAIK, the only way to disable and re-enable an NDIS miniport driver is
> > > via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
> > > SetupDi can AFAIK only be used from user-mode, you will need to put the
> > > code in e.g. some Service or a Notify Object for the protocol.
> > >
> > > Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
> > > only be used if you have the miniport handle.
> > >
> > > Stephan
> > > ---
> > > haideepu wrote:
> > > > Hi experts,
> > > >
> > > > I want to make Ndis call (reinvoke) my MiniportInitialize from protocol
> > > > driver. This has to be done without removing and reinserting my device.
> > > >
> > > >
> > > > First iam trying to make Ndis to call my MiniportHalt & then recall
> > > > MiniportInitialize.
> > > >
> > > >
> > > > Any suggestion welcome
> > > >
> > > > Thanks in advance

Alireza
Thu Oct 12 03:14:30 CDT 2006

You can not do this from kernel mode. As Stephan said, you have to do it
from user mode.
If for some reason unloading and reloading your miniport driver is not
desirable, (I think) you can reference the driver object so it does not go
away.

Your mail implies that you own the miniport driver as well as the other
driver (protocol driver) that wants to force the adapter to reinitialize. I
guess what you want to change is not a private property, rather it is
something like adapter's MAC address and therefore you have to reinitialize
the adapter in order for NDIS to update adapter's information. But in that
case, I am not sure why you are worried about driver getting unloaded and
reloaded again.

-ali

"haideepu" <pradeep.bhureddy@gmail.com> wrote in message
news:1160632078.970102.206560@i42g2000cwa.googlegroups.com...
> Hi
>
> My Objective is simple....I want to reinvoke my MiniportInitialize
> without removing my device
>
> any advice??
>
> --Pradeep
>
>
>
> soviet_bloke@hotmail.com wrote:
>> Hi mate
>>
>> > And More over We want to call MiniportInitialize() without being
>> > DriverEntry Called. If we use SetupDi calls that may unload driver,
>> > which shouldn't happen...
>>
>> But why do you present the above requirement???? What are your overall
>> objectives????
>>
>> Anton Bassov
>>
>> haideepu wrote:
>> > Hi Stephan
>> >
>> > Thanx for your reply...
>> > Our driver doestn't have Intermediate driver
>> > ...NdisIMDeInitializeDeviceInstance() can only be used with
>> > Intermediate driver.....We tried by calling the same with miniport
>> > handle from protocol driver ...But we r getting
>> > NDIS_STATUS_FAILURE.....
>> >
>> > And More over We want to call MiniportInitialize() without being
>> > DriverEntry Called. If we use SetupDi calls that may unload driver,
>> > which shouldn't happen...
>> >
>> > We are searching for some way to make Ndis invoke MiniportHalt() and
>> > then invoke MiniportInitialize(), where it can read the changed
>> > registry settings....We will change the registry settings from our
>> > application before making our protocol driver to invoke
>> > MiniportHalt.....When MiniportInitialize gets called ...it can read the
>> > changed registry settings..
>> >
>> > Suggestions plzzzzz
>> >
>> > Thanx in adv
>> >
>> > ---Pradeep
>> >
>> >
>> >
>> >
>> > Stephan Wolf [MVP] wrote:
>> > > AFAIK, the only way to disable and re-enable an NDIS miniport driver
>> > > is
>> > > via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
>> > > SetupDi can AFAIK only be used from user-mode, you will need to put
>> > > the
>> > > code in e.g. some Service or a Notify Object for the protocol.
>> > >
>> > > Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
>> > > only be used if you have the miniport handle.
>> > >
>> > > Stephan
>> > > ---
>> > > haideepu wrote:
>> > > > Hi experts,
>> > > >
>> > > > I want to make Ndis call (reinvoke) my MiniportInitialize from
>> > > > protocol
>> > > > driver. This has to be done without removing and reinserting my
>> > > > device.
>> > > >
>> > > >
>> > > > First iam trying to make Ndis to call my MiniportHalt & then
>> > > > recall
>> > > > MiniportInitialize.
>> > > >
>> > > >
>> > > > Any suggestion welcome
>> > > >
>> > > > Thanks in advance
>

fat_boy
Thu Oct 12 04:48:50 CDT 2006


haideepu wrote:
> Hi
>
> My Objective is simple....I want to reinvoke my MiniportInitialize
> without removing my device
>

No you dont. You want to give new registry settings to your Ndis
driver from an application. The problem is is that an Ndis driver can
only get to its registry area during initialisation.

What I did to solve this is to create an interface accessible by an
application, NdisMRegisterDevice(). This interface has an
IOCTL_SET_PARAMS method.

The Ndis driver uses these params immediately, AND stores them in a
different part of the registry (in the service entry).

The next time the Ndis driver reloads, it checks the service entry for
data. If it is there, it copies it to its regstry area, and deletes
the data in the service entry.




> any advice??
>
> --Pradeep
>
>
>
> soviet_bloke@hotmail.com wrote:
> > Hi mate
> >
> > > And More over We want to call MiniportInitialize() without being
> > > DriverEntry Called. If we use SetupDi calls that may unload driver,
> > > which shouldn't happen...
> >
> > But why do you present the above requirement???? What are your overall
> > objectives????
> >
> > Anton Bassov
> >
> > haideepu wrote:
> > > Hi Stephan
> > >
> > > Thanx for your reply...
> > > Our driver doestn't have Intermediate driver
> > > ...NdisIMDeInitializeDeviceInstance() can only be used with
> > > Intermediate driver.....We tried by calling the same with miniport
> > > handle from protocol driver ...But we r getting
> > > NDIS_STATUS_FAILURE.....
> > >
> > > And More over We want to call MiniportInitialize() without being
> > > DriverEntry Called. If we use SetupDi calls that may unload driver,
> > > which shouldn't happen...
> > >
> > > We are searching for some way to make Ndis invoke MiniportHalt() and
> > > then invoke MiniportInitialize(), where it can read the changed
> > > registry settings....We will change the registry settings from our
> > > application before making our protocol driver to invoke
> > > MiniportHalt.....When MiniportInitialize gets called ...it can read the
> > > changed registry settings..
> > >
> > > Suggestions plzzzzz
> > >
> > > Thanx in adv
> > >
> > > ---Pradeep
> > >
> > >
> > >
> > >
> > > Stephan Wolf [MVP] wrote:
> > > > AFAIK, the only way to disable and re-enable an NDIS miniport driver is
> > > > via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
> > > > SetupDi can AFAIK only be used from user-mode, you will need to put the
> > > > code in e.g. some Service or a Notify Object for the protocol.
> > > >
> > > > Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
> > > > only be used if you have the miniport handle.
> > > >
> > > > Stephan
> > > > ---
> > > > haideepu wrote:
> > > > > Hi experts,
> > > > >
> > > > > I want to make Ndis call (reinvoke) my MiniportInitialize from protocol
> > > > > driver. This has to be done without removing and reinserting my device.
> > > > >
> > > > >
> > > > > First iam trying to make Ndis to call my MiniportHalt & then recall
> > > > > MiniportInitialize.
> > > > >
> > > > >
> > > > > Any suggestion welcome
> > > > >
> > > > > Thanks in advance

haideepu
Thu Oct 12 05:30:05 CDT 2006

Hi Ali,

Thanx for ur reply...
ya...What we r trying to change in the registry is some sort of
propraitary only..we can't reveal the details..

We r using the same driver for multiple devices...and we want one
device to work even we disable the other with same driver...as u said
if we unload driver other device may not work......this is our
problem.....

Objective is ..recall MiniportInitialize without DriverEntry being
called...that is we don't want to unload ..and reload driver....

May I know some details on....referencing the driver object so it does
not go away.
I tried with sample "../src/setup/devcon/" disabling the device and
enabling it...It works ...but
It unloads and reloads driver..which should not happen

any advice??

--Pradeep Reddy


Alireza Dabagh [MS] wrote:
> You can not do this from kernel mode. As Stephan said, you have to do it
> from user mode.
> If for some reason unloading and reloading your miniport driver is not
> desirable, (I think) you can reference the driver object so it does not go
> away.
>
> Your mail implies that you own the miniport driver as well as the other
> driver (protocol driver) that wants to force the adapter to reinitialize. I
> guess what you want to change is not a private property, rather it is
> something like adapter's MAC address and therefore you have to reinitialize
> the adapter in order for NDIS to update adapter's information. But in that
> case, I am not sure why you are worried about driver getting unloaded and
> reloaded again.
>
> -ali
>
> "haideepu" <pradeep.bhureddy@gmail.com> wrote in message
> news:1160632078.970102.206560@i42g2000cwa.googlegroups.com...
> > Hi
> >
> > My Objective is simple....I want to reinvoke my MiniportInitialize
> > without removing my device
> >
> > any advice??
> >
> > --Pradeep
> >
> >
> >
> > soviet_bloke@hotmail.com wrote:
> >> Hi mate
> >>
> >> > And More over We want to call MiniportInitialize() without being
> >> > DriverEntry Called. If we use SetupDi calls that may unload driver,
> >> > which shouldn't happen...
> >>
> >> But why do you present the above requirement???? What are your overall
> >> objectives????
> >>
> >> Anton Bassov
> >>
> >> haideepu wrote:
> >> > Hi Stephan
> >> >
> >> > Thanx for your reply...
> >> > Our driver doestn't have Intermediate driver
> >> > ...NdisIMDeInitializeDeviceInstance() can only be used with
> >> > Intermediate driver.....We tried by calling the same with miniport
> >> > handle from protocol driver ...But we r getting
> >> > NDIS_STATUS_FAILURE.....
> >> >
> >> > And More over We want to call MiniportInitialize() without being
> >> > DriverEntry Called. If we use SetupDi calls that may unload driver,
> >> > which shouldn't happen...
> >> >
> >> > We are searching for some way to make Ndis invoke MiniportHalt() and
> >> > then invoke MiniportInitialize(), where it can read the changed
> >> > registry settings....We will change the registry settings from our
> >> > application before making our protocol driver to invoke
> >> > MiniportHalt.....When MiniportInitialize gets called ...it can read the
> >> > changed registry settings..
> >> >
> >> > Suggestions plzzzzz
> >> >
> >> > Thanx in adv
> >> >
> >> > ---Pradeep
> >> >
> >> >
> >> >
> >> >
> >> > Stephan Wolf [MVP] wrote:
> >> > > AFAIK, the only way to disable and re-enable an NDIS miniport driver
> >> > > is
> >> > > via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
> >> > > SetupDi can AFAIK only be used from user-mode, you will need to put
> >> > > the
> >> > > code in e.g. some Service or a Notify Object for the protocol.
> >> > >
> >> > > Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
> >> > > only be used if you have the miniport handle.
> >> > >
> >> > > Stephan
> >> > > ---
> >> > > haideepu wrote:
> >> > > > Hi experts,
> >> > > >
> >> > > > I want to make Ndis call (reinvoke) my MiniportInitialize from
> >> > > > protocol
> >> > > > driver. This has to be done without removing and reinserting my
> >> > > > device.
> >> > > >
> >> > > >
> >> > > > First iam trying to make Ndis to call my MiniportHalt & then
> >> > > > recall
> >> > > > MiniportInitialize.
> >> > > >
> >> > > >
> >> > > > Any suggestion welcome
> >> > > >
> >> > > > Thanks in advance
> >

Pankaj
Thu Oct 12 06:20:02 CDT 2006

If the same driver has other devices then disabling and enabling of one
device (i.e the miniport) from user mode will not unload the driver.

Driver is only unloaded when it is not needed anymore by anyone.


Pankaj

On Thu, 12 Oct 2006, haideepu wrote:

>
> Hi Ali,
>
> Thanx for ur reply...
> ya...What we r trying to change in the registry is some sort of
> propraitary only..we can't reveal the details..
>
> We r using the same driver for multiple devices...and we want one
> device to work even we disable the other with same driver...as u said
> if we unload driver other device may not work......this is our
> problem.....
>
> Objective is ..recall MiniportInitialize without DriverEntry being
> called...that is we don't want to unload ..and reload driver....
>
> May I know some details on....referencing the driver object so it does
> not go away.
> I tried with sample "../src/setup/devcon/" disabling the device and
> enabling it...It works ...but
> It unloads and reloads driver..which should not happen
>
> any advice??
>
> --Pradeep Reddy
>
>
> Alireza Dabagh [MS] wrote:
>> You can not do this from kernel mode. As Stephan said, you have to do it
>> from user mode.
>> If for some reason unloading and reloading your miniport driver is not
>> desirable, (I think) you can reference the driver object so it does not go
>> away.
>>
>> Your mail implies that you own the miniport driver as well as the other
>> driver (protocol driver) that wants to force the adapter to reinitialize. I
>> guess what you want to change is not a private property, rather it is
>> something like adapter's MAC address and therefore you have to reinitialize
>> the adapter in order for NDIS to update adapter's information. But in that
>> case, I am not sure why you are worried about driver getting unloaded and
>> reloaded again.
>>
>> -ali
>>
>> "haideepu" <pradeep.bhureddy@gmail.com> wrote in message
>> news:1160632078.970102.206560@i42g2000cwa.googlegroups.com...
>>> Hi
>>>
>>> My Objective is simple....I want to reinvoke my MiniportInitialize
>>> without removing my device
>>>
>>> any advice??
>>>
>>> --Pradeep
>>>
>>>
>>>
>>> soviet_bloke@hotmail.com wrote:
>>>> Hi mate
>>>>
>>>>> And More over We want to call MiniportInitialize() without being
>>>>> DriverEntry Called. If we use SetupDi calls that may unload driver,
>>>>> which shouldn't happen...
>>>>
>>>> But why do you present the above requirement???? What are your overall
>>>> objectives????
>>>>
>>>> Anton Bassov
>>>>
>>>> haideepu wrote:
>>>>> Hi Stephan
>>>>>
>>>>> Thanx for your reply...
>>>>> Our driver doestn't have Intermediate driver
>>>>> ...NdisIMDeInitializeDeviceInstance() can only be used with
>>>>> Intermediate driver.....We tried by calling the same with miniport
>>>>> handle from protocol driver ...But we r getting
>>>>> NDIS_STATUS_FAILURE.....
>>>>>
>>>>> And More over We want to call MiniportInitialize() without being
>>>>> DriverEntry Called. If we use SetupDi calls that may unload driver,
>>>>> which shouldn't happen...
>>>>>
>>>>> We are searching for some way to make Ndis invoke MiniportHalt() and
>>>>> then invoke MiniportInitialize(), where it can read the changed
>>>>> registry settings....We will change the registry settings from our
>>>>> application before making our protocol driver to invoke
>>>>> MiniportHalt.....When MiniportInitialize gets called ...it can read the
>>>>> changed registry settings..
>>>>>
>>>>> Suggestions plzzzzz
>>>>>
>>>>> Thanx in adv
>>>>>
>>>>> ---Pradeep
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Stephan Wolf [MVP] wrote:
>>>>>> AFAIK, the only way to disable and re-enable an NDIS miniport driver
>>>>>> is
>>>>>> via SetupDi. See the "...\src\setup\devcon\" sample in the DDK. Since
>>>>>> SetupDi can AFAIK only be used from user-mode, you will need to put
>>>>>> the
>>>>>> code in e.g. some Service or a Notify Object for the protocol.
>>>>>>
>>>>>> Sure there is also NdisIMDeInitializeDeviceInstance(). But this can
>>>>>> only be used if you have the miniport handle.
>>>>>>
>>>>>> Stephan
>>>>>> ---
>>>>>> haideepu wrote:
>>>>>>> Hi experts,
>>>>>>>
>>>>>>> I want to make Ndis call (reinvoke) my MiniportInitialize from
>>>>>>> protocol
>>>>>>> driver. This has to be done without removing and reinserting my
>>>>>>> device.
>>>>>>>
>>>>>>>
>>>>>>> First iam trying to make Ndis to call my MiniportHalt & then
>>>>>>> recall
>>>>>>> MiniportInitialize.
>>>>>>>
>>>>>>>
>>>>>>> Any suggestion welcome
>>>>>>>
>>>>>>> Thanks in advance
>>>
>
>

Stephan
Thu Oct 12 10:39:45 CDT 2006

Several things come to mind:

- What's wrong with the driver getting unloaded?

- IIRC, the driver will not get unloaded as long as the driver
maintains a "private" device object, which it created using
NdisMRegisterDevice(). Thus, if you call NdisMRegisterDevice() from
DriverEntry(), you will not get unloaded unless you call
NdisMDeregisterDevice().

- If that does not help, simply open a file handle from your user-mode
program to the miniport and keep it open. You can use either a private
or the miniport's standard device object (owned by NDIS, see e.g.
http://www.ndis.com/faq/QA10290101.htm).

- Also, driver unload can be detected by the miniport in an unload
handler, see NdisMRegisterUnloadHandler().

- Using IO/ controls to a "private" device object is actually a perfect
way to tell the miniport about new configuration parameters and/or to
trigger a re-read of registry settings.

- More, a miniport *can* read its registry settings even after
MiniportInitialize(). The important part is that everything must be
done at IRQL PASSIVE_LEVEL. If necessary, this can be achieved by using
a work item callback, see NdisScheduleWorkItem().

Stephan

Maxim
Thu Oct 12 15:22:00 CDT 2006

> We r using the same driver for multiple devices...and we want one
> device to work even we disable the other with same driver...

PnP does this automatically.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

haideepu
Mon Oct 16 01:24:27 CDT 2006

Hi Stephan Wolf

Thanks for your replies....
"..\src\setup\devcon" Worked for me ..thats what i want...
Thanks a lot

--Pradeep

Maxim S. Shatskih wrote:
> > We r using the same driver for multiple devices...and we want one
> > device to work even we disable the other with same driver...
>
> PnP does this automatically.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com