can anybody suggest me?

NTDEV
1

Hi ALL,

1.Whether is it compulsry that any device which is going to interact with
Windows Operating system should have an OSM?

2.Whether the operating system cross verify the class Type we mention in the
INF & with the class code what it gets from the PCI(Classcode registers)?

3.Isn’t possible for driver to register this(Intelligent I/O Controller)
device with the NDIS by telling it to the OS in the INf file that it is a
class of type “NET” & so that i get the support for this?

4.Isn’t Possible to write a WDM Driver to this (Intelligent I/O Controller)
Device & then write another Virtual NDIS Driver so that i can communicate
with this for my TCP/IP applications?

Just try to reply me on these issues still more.

Any suggestions more welcome.

Regards,
Vishwanath M.

----- Original Message -----
From:
To: “NT Developers Interest List”
Sent: Friday, May 17, 2002 4:40 PM
Subject: [ntdev] RE: please reply to this…

Vishwanath,

It seems you need a LAN OSM (or write one yourself?).
MS has Storage OSM and a LAN OSM was scheduled for NT5 (it was called at
that time). What the situation is now,
I don’t know.

You’ll have to ask MS what the status of LAN OSM is.
If you want to write one yourself, study the I2O specs first (the URL I sent
you earlier).
Get some SW for your board (test sw from the vendor, docs, source code…
whatever).

Just out of curiosity, How come you have such a board with no drivers? Are
you the vendor? or do you only have drivers
for other OSs ?

Robin

> -----Original Message-----
> From: vishwanath [mailto:xxxxx@deccanetdesignstele.com]
> Sent: Friday, May 17, 2002 12:33 PM
> To: NT Developers Interest List
> Subject: [ntdev] RE: please reply to this…
>
>
> Hi Robin,
>
> Isn’t possible to write the MiniportIP driver for this Intelligent I/O
> Controller.Yeah As you said this has the classcode(0E0001) &
> I am trying
> many possibilities like changing all the things in the INF
> file & trying it
> to get registered it with NDIS.
> As you said where can i get the complete information to these kind of
> drivers?Just if u have any URLs or materials just try to send
> me by mail.
>
> Anyway i am sending the INF in a seperate mail.you can check it out.
> Any suggestions most welcome.
>
> Regards,
> Vishwanath M.
>
>
>
>
>
>
>
> ----- Original Message -----
> From:
> To: “NT Developers Interest List”
> Cc:
> Sent: Friday, May 17, 2002 3:12 PM
> Subject: [ntdev] RE: please reply to this…
>
>
> Vishwanath,
>
> Please continue posting to the list. The chances are far
> greater to get help
> there.
> The .inf file you sent was unfortunately cut off by our virus
> checker, so I
> can’t comment it.
>
> If your device is ‘intellignet’, then it could be a I2O type device.
> from I2O spec:
>
> —


>
> If it is a I2O type device and you’ll need completely
> different drivers
> alltogether. I believe MS has something there (OSM) but I’m not sure.
> I2O is a world of its own. See also http://www.intelligent-io.com/
>
> Robin
>
>
> > -----Original Message-----
> > From: vishwanath [mailto:xxxxx@deccanetdesignstele.com]
> > Sent: Friday, May 17, 2002 4:52 AM
> > To: Mitra, Robin
> > Subject: Re: [ntdev] RE: please reply to this…
> >
> >
> > Hi Robin,
> >
> > Yeah the device is a Generic Device which needs to
> > communicate with all the
> > TCP/IP Applications, for that purpose only i wanted to
> > register it with the
> > NDIS & I tried all the possibilities with INF file also,but i
> > couldn’t get
> > succeded.So i am here by attaching you the INF file which i
> > am using it.
> > The characteristics of this device are PCI card & is an
> > intelligent I/O
> > Controller which should get registered with the Network subsystem.
> > DeviceID -0661
> > VendorID-10CC
> > With this input i had written the INF file.
> >
> > Just try to correct me, if i am doing wrong.
> >
> > Regards,
> > Vishwanath M.
> >
> > ----- Original Message -----
> > From:
> > To: “NT Developers Interest List”
> > Sent: Thursday, May 16, 2002 10:05 PM
> > Subject: [ntdev] RE: please reply to this…
> >
> >
> > > If your Initialize isn’t being called, then probably your
> > .inf file is
> > > wrong.
> > >
> > > We’ll need more info on what exactly you want to do.
> > > What do you mean by Intelligent I/O Controller ? Some generic I2O
> > > (raid-)device?
> > > How is it related to SCSI Drivers (if at all)?
> > >
> > > Robin
> > >
> > > > -----Original Message-----
> > > > From: vishwanath [mailto:xxxxx@deccanetdesignstele.com]
> > > > Sent: Thursday, May 16, 2002 4:00 PM
> > > > To: Mitra, Robin
> > > > Subject: Re: [ntdev] RE: please reply to this…
> > > >
> > > >
> > > > Hi Robin,
> > > >
> > > > Can u tell me how i can do this?
> > > > B’cos i am having a device called Intelligent I/O Controller
> > > > which i wanted
> > > > to register it to the NDIS & i am trying it to register it
> > > > with the NDIS,
> > > > but it is giving problem after DriverEntry,like it
> > doesn’t call the
> > > > initialize routine of the driver.Even i am trying the different
> > > > possibilities,but i am not getting intialize called with the
> > > > Device on th
> > > > system.
> > > >
> > > > Any help will be appreciated…
> > > >
> > > > Regards,
> > > > Vishwanath M.
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From:
> > > > To: “NT Developers Interest List”
> > > > Sent: Thursday, May 16, 2002 6:54 PM
> > > > Subject: [ntdev] RE: please reply to this…
> > > >
> > > >
> > > > > you can register anything to Ndis. Of course if you ALSO
> > > > want to register
> > > > it
> > > > > someone else i.e. scsi, then it depends what you want to do.
> > > > >
> > > > > Robin
> > > > >
> > > > > -----Original Message-----
> > > > > From: vishwanath [mailto:xxxxx@deccanetdesignstele.com]
> > > > > Sent: Thursday, May 16, 2002 1:38 PM
> > > > > To: NT Developers Interest List
> > > > > Subject: [ntdev] please reply to this…
> > > > >
> > > > >
> > > > > Hi ALL,
> > > > >
> > > > > Is it possible to register a SCSI Device to the NDIS
> subsystem?
> > > > > If so how is it possible just mail me or just give me some
> > > > URL for the
> > > > same.
> > > > >
> > > > > Please do reply me…
> > > > >
> > > > > Regards,
> > > > > Vishwanath M.
> > > > > —
> > > > > You are currently subscribed to ntdev as:
> > xxxxx@exgate.tek.com
> > > > > To unsubscribe send a blank email to %%email.unsub%%
> > > > >
> > > > >
> > > > > —
> > > > > You are currently subscribed to ntdev as:
> > > > xxxxx@deccanetdesignstele.com
> > > > > To unsubscribe send a blank email to %%email.unsub%%
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> > xxxxx@deccanetdesignstele.com
> > > To unsubscribe send a blank email to %%email.unsub%%
> > >
> > >
> >
> >
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@deccanetdesignstele.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@exgate.tek.com
> To unsubscribe send a blank email to %%email.unsub%%
>

—
You are currently subscribed to ntdev as: xxxxx@deccanetdesignstele.com
To unsubscribe send a blank email to %%email.unsub%%

2

> 1.Whether is it compulsry that any device which is going to interact with

Windows Operating system should have an OSM?

What is OSM?

2.Whether the operating system cross verify the class Type we mention in the
INF & with the class code what it gets from the PCI(Classcode registers)?

PCI class is a part of hardware ID. So, the OS will use it if some other IDs will not match.

3.Isn’t possible for driver to register this(Intelligent I/O Controller)
device with the NDIS by telling it to the OS in the INf file that it is a
class of type “NET”

No. If you want your device to be both a device and a network adapter - I would suggest writing 2 driver binaries - NDIS and
non-NDIS.
The reason is that for NDIS miniport, the dispatch table belongs to NDIS, and combining a miniport with a usual driver in a single
binary is not fun.

4.Isn’t Possible to write a WDM Driver to this (Intelligent I/O Controller)
Device & then write another Virtual NDIS Driver so that i can communicate
with this for my TCP/IP applications?

I would recommend this.

Max

3

Hi Maxim,

I mean(OSM) to say that each kind of device should have its own
subsystem?like Network devices have NDIS & SCSI devices have SCSI Port.In
the same way is there any support for Intelligent I/O Controller in the
Windows operating system?

Maxim if u recommend me to do 2-binaries likes WDM & NDIS,How can i mention
the DeviceID & VendorID in the INF file?like do you have any sample INF file
for this or is it available in any sites?

moreover if i do 2-binaries whether microsoft is going to give the Digital
signature for these kind of drivers?

Regards,
Vishwanath M.

----- Original Message -----
From: “Maxim S. Shatskih”
To: “NT Developers Interest List”
Cc: “NT Developers Interest List”
Sent: Saturday, May 18, 2002 10:42 AM
Subject: [ntdev] Re: can anybody suggest me?

> > 1.Whether is it compulsry that any device which is going to interact
with
> > Windows Operating system should have an OSM?
>
> What is OSM?
>
> > 2.Whether the operating system cross verify the class Type we mention in
the
> > INF & with the class code what it gets from the PCI(Classcode
registers)?
>
> PCI class is a part of hardware ID. So, the OS will use it if some other
IDs will not match.
>
> > 3.Isn’t possible for driver to register this(Intelligent I/O Controller)
> > device with the NDIS by telling it to the OS in the INf file that it is
a
> > class of type “NET”
>
> No. If you want your device to be both a device and a network adapter - I
would suggest writing 2 driver binaries - NDIS and
> non-NDIS.
> The reason is that for NDIS miniport, the dispatch table belongs to NDIS,
and combining a miniport with a usual driver in a single
> binary is not fun.
>
> > 4.Isn’t Possible to write a WDM Driver to this (Intelligent I/O
Controller)
> > Device & then write another Virtual NDIS Driver so that i can
communicate
> > with this for my TCP/IP applications?
>
> I would recommend this.
>
> Max
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@deccanetdesignstele.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>

4

> I mean(OSM) to say that each kind of device should have its own

subsystem?like Network devices have NDIS & SCSI devices have SCSI Port.In
the same way is there any support for Intelligent I/O Controller in the
Windows operating system?

Is it an I2O controller? They have a subsystem for them.

Maxim if u recommend me to do 2-binaries likes WDM & NDIS,How can i mention
the DeviceID & VendorID in the INF file?like do you have any sample INF file
for this or is it available in any sites?

Try to root-enumerate the NDIS driver. To impose dependency on driver load, use PnP device interfaces and arrival notifications.

Max

5

Hi Maxim,

Now in the present operatingsystems(of Windows) is there support for I2O
controller.Can u let me know where can i get more information on
implementing these drivers,like we have NDIS support routines in DDK,in the
same way do we have any support for implementing these drivers also.

Maxim can you explain once again what u mean by the root enumerate the NDIS
driver.Is it possible to write only an NDIS miniport driver for this I2O
Controller?

Regards,
Vishwanath M.

----- Original Message -----
From: “Maxim S. Shatskih”
To: “NT Developers Interest List”
Sent: Saturday, May 18, 2002 4:44 PM
Subject: [ntdev] Re: can anybody suggest me?

> > I mean(OSM) to say that each kind of device should have its own
> > subsystem?like Network devices have NDIS & SCSI devices have SCSI
Port.In
> > the same way is there any support for Intelligent I/O Controller in the
> > Windows operating system?
>
> Is it an I2O controller? They have a subsystem for them.
>
> > Maxim if u recommend me to do 2-binaries likes WDM & NDIS,How can i
mention
> > the DeviceID & VendorID in the INF file?like do you have any sample INF
file
> > for this or is it available in any sites?
>
> Try to root-enumerate the NDIS driver. To impose dependency on driver
load, use PnP device interfaces and arrival notifications.
>
> Max
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@deccanetdesignstele.com
> To unsubscribe send a blank email to %%email.unsub%%
>
>