Hi Mark,
Hi,
ThankYou very much for showing interest. I am extremely sorry for
mailing you on your personal ID. But I really need your help. I am
developing Virtual Miniport Driver. As you mentioned that you are also
writing the same driver, I am looking for your kind help.
These are the some settings I did in my VMiniport driver.
DriverEntry:
VhwInitializationData.SpecificLuExtensionSize = 0;
VhwInitializationData.AdapterInterfaceType = Internal;
VhwInitializationData.TaggedQueuing = TRUE;
VhwInitializationData.AutoRequestSense = TRUE;
VhwInitializationData.ReceiveEvent = TRUE;
VhwInitializationData.AutoRequestSense = TRUE;
VhwInitializationData.MultipleRequestPerLu = TRUE;
VhwInitializationData.MapBuffers =
STOR_MAP_NON_READ_WRITE_BUFFERS;
FindAdapter:
ConfigInfo->MaximumTransferLength = 0x10000;
ConfigInfo->NumberOfPhysicalBreaks = 17;
ConfigInfo->NumberOfBuses = 1;
ConfigInfo->MaximumNumberOfTargets = 1;
ConfigInfo->CachesData = FALSE;
ConfigInfo->VirtualDevice = TRUE;
ConfigInfo->InitiatorBusId[0] = 7;
ConfigInfo->ScatterGather = TRUE;
ConfigInfo->Master = TRUE;
I am using Windows Vista(SP1). and I have following problems.
I have tried (one by one)
VhwInitializationData.MapBuffers = STOR_MAP_NO_BUFFERS,
VhwInitializationData.MapBuffers = STOR_MAP_ALL_BUFFERS, and
VhwInitializationData.MapBuffers = STOR_MAP_NON_READ_WRITE_BUFFERS
But irrespective of any settings for MapBuffers, Initially I got
Srb->DataBuffer = and SGList = NULL. I
could read and write on/from the requested blocks.
However, after some read writes, I got Srb->DataBuffer = NULL and SGList
= NULL.
I tried to get original MDL using StorPortGetOriginalMdl() which returns
an Mdl that has
Mdl->StartVa = 0x00000000, Mdl->MappedSystemVa = 0x00000000,
Mdl->MdlFlags = -30650, Mdl->ByteCount = 0x1000
What could be the reason for this behaviour? Why I am getting DataBuffer
= NULL and Mdl->StartVa = NULL ?
I just need the Virtual Address for data given in SRB and I hope
Srb->DataBuffer is a virtual address of data buffer that I want. Is
there any other way to do this ?
Please help.
Thanks & Regards,
Bhavin
Mark Roddy wrote:
> You are getting called at /HwStorFindAdapter/ but not at
> /HwStorInitialize/?
>
> Generally this would be because you have failed to convince storport
> that you have enough of a device to continue with. Of course storport
> virtual miniports are for all practical purposes undocumented in the WDK.
>
> There is better documenation than the woeful stuff in the WDK here
> online at MSDN: http://msdn.microsoft.com/en-us/library/bb986556.aspx
>
> In particular you appear to have to support
> /VirtualHwStorFindAdapter./ Wouldn’t a sample driver be nice?
> Somebody should pay me to write one
> Here is my clue: provide a VIRTUAL_HW_INITIALIZATION_DATA object
> instead of a HW_INITIALIZATION_DATA object in your call to
> StorPortInitialize. Just a guess on my part.
>
> On Wed, Jul 16, 2008 at 10:24 AM, bhavin.thummar
> >
> wrote:
>
> Hi,
>
> I am working on a virtual storport miniport driver. For developing
> this I have gone through the I2O code as reference.
> but I am facing problem with this. My HwInitialize routin has not
> been called for some reason.
>
> Can anyone help me to resolve this problem? Can someone please
> provide me the sample virtual storport miniport driver code?
>
> Regards,
> Bhavin
> –
>
> Disclaimer: This e-mail message and all attachments transmitted
> with it
> are intended solely for the use of the addressee and may contain
> legally
> privileged and confidential information. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, copying, or other
> use of
> this message or its attachments is strictly prohibited. If you have
> received this message in error, please notify the sender
> immediately by
> replying to this message and please delete it from your computer. Any
> views expressed in this message are those of the individual sender
> unless otherwise stated.Company has taken enough precautions to
> prevent
> the spread of viruses. However the company accepts no liability
> for any
> damage caused by any virus transmitted by this email.
>_____
>
>
> —
> 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@hollistech.com
> mailto:xxxxx
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
> mailto:xxxxx
>
>
>
>
> –
> Mark Roddy
> — 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@einfochips.com To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
> Email Scanned for Virus & Dangerous Content by :
> www.CleanMailGateway.com
>
–
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
_____ </mailto:xxxxx></mailto:xxxxx>