The problem is that using a class driver will require implementation of
all the required IOCTL codes. Why re-invent the wheel? Chances are,
required changes between OS version in the future will be easier;
including back support to NT 4.0. If you write a miniport driver, you
reduce the required command set to some simple SCSI commands. This
allows the upper class driver to do what it does best; provide the disk
class interface.
Jamey
xxxxx@storagecraft.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Pashupati
Sent: Wednesday, October 17, 2001 11:37 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Virtual disk mapped to a remote disk
ramdisk would be a good starting point for the design u r talking, in
you case u would pick up the disk space on remote system. u could use
eiher tdi or kernel socket calls
----- Original Message -----
From: “Namita Lal”
To: “NT Developers Interest List”
Sent: Thursday, October 18, 2001 10:51 AM
Subject: [ntdev] Re: Virtual disk mapped to a remote disk
> If we assume that I cannot use iScsi for my implementation, is it
completely
> neccessary for me to write a Scsi Miniport( or a monolithic
> port/miniport) driver in order to export a virtual disk on NT ? I am
> not looking for a solution for network attached storage. I need to
> develop a virtual disk driver on windows that will appear to be a
> local
disk
> and will intercept commands and pass them over to another machine
> probably running Linux which will then replay these commands, using a
> NBD-like interface, on the actual disk. I know that some translation
> of semantics will be required for this to work. I was thinking more
> along the lines of taking a FileDisk driver for
windows
> which emulates files on disks as virtual disks and modifying it to
> virtualize entire disks remotely. To do this I could use the transport
stack
> either by employing TDI (which seems to be a tough problem from kernel
mode
> as Jamey pointed out) or some other method.
> I do not know if this approach is viable though.
>
> Regards,
> Namita
>
> ----- Original Message -----
> From:
> To: “NT Developers Interest List”
> Sent: Wednesday, October 17, 2001 12:00 AM
> Subject: [ntdev] Re: Virtual disk mapped to a remote disk
>
>
> > Hi,
> >
> > If you will talk from your virtual block driver to own server you
> > can implement anything you want. I mean protocol. CoolDev use
> > modified SMB
or
> > HTTP.
> >
> > So you have to write either SCSI miniport or monolithic SCSI port
> > driver and TDI client driver that will talk to server that’s running
> > on remote machine. CoolDev had project when vitual DVD volumes were
> > located at MS
> IIS
> > server (not our bright idea…).
> >
> > You’d better start with free demo from CoolDev.Com and then just
> > replace the parts with own driver step-by-step…
> >
> > Regards,
> > Anton
> >
> > P.S. Do not ask Victor about this stuff, I’m just too lazy to
> > re-login
at
> > my name -))
> >
> > On 10/16/01, ““Namita Lal” ” wrote:
> > > This is a multi-part message in MIME format.
> > >
> > > ------=_NextPart_000_0009_01C15671.A565F420
> > > Content-Type: text/plain;
> > > charset=“iso-8859-1”
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > Hi,
> > >
> > > I need to write a virtual disk solution for windows NT and 2000
> > > that = will allow me to export a remote disk on one system and use
> > > it as a = local disk in a transparent manner on another. =20 I
> > > know that I will have to fake my device somewhere in the storage
stack
> =
> > > on the client system and use TDI interface to communicate to a
> > > daemon
=
> > > running on the server to which the disk is attached.=20 Can this
> > > be done? Does anyone have any ideas about how to approach
this
> =
> > > problem exactly?=20
> > >
> > > Thanks in Advance,
> > > Regards,
> > > Namita
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@calsoftinc.com To
> > > unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> > > ------=_NextPart_000_0009_01C15671.A565F420
> > > Content-Type: text/html;
> > > charset=“iso-8859-1”
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > >
> > > > > > http-equiv=3DContent-Type>
> > >
> > >
> > >
> > >
> > >
Hi,
> > >
> > >
I need to write a
virtual =
> > > disk solution=20
> > > for windows NT and 2000 that will allow me to export
a remote
> =
> > > disk=20
> > > on one system and use it as a local disk in a transparent
> > > manner
on
> =
> > >
> > > another.
> > >
I know that I will
have
> =
> > > to fake my=20
> > > device somewhere in the storage stack on the client system and =
> > > use TDI=20 interface to communicate to a daemon running on
> > > the server to
which
> =
> > > the=20
> > > disk is attached.
> > >
Can this be done? Does
anyone
> =
> > > have any=20
> > > ideas about how to approach this problem exactly?
> > >
Thanks in Advance,
> > >
Regards,
> > >
Namita
> > > —
> > > You are currently subscribed to ntdev as:
xxxxx@calsoftinc.com> > > To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)
@lists.osr.com> > >
> > —
> > You are currently subscribed to ntdev as:
xxxxx@calsoftinc.com > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)
@lists.osr.com> >
> —
> You are currently subscribed to ntdev as:
xxxxx@Legato.COM To
> unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)
@lists.osr.com>
—
You are currently subscribed to ntdev as:
xxxxx@storagecraft.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)
@lists.osr.com—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)
@lists.osr.com> > >
> > >
> > > ------=_NextPart_000_0009_01C15671.A565F420–
> >
> >
>
>