| The hack is using a program on the pc end (in turbo pascal, he uses
v6) to talk with an ethernet driver using one of the common
pc packet drivers (public domain, available for most boards and
using a common interface) to talk to the ethernet. It uses his
own ethernet protocol, talking to the ethernet driver on vms.
Remote disks are done at device level...they look exactly like
local disks, using something derived from my virtual disk
code. Remote tape is also exactly like local as far as the
rest of VMS is concerned...it transports logical I/O and leaves
everything else purely at the VMS end. All the PC sees is a device
or partition or file or whatnot. The protocol lets him transport
serial devices also...presumably a printer or the like could be
made to look local too.
The remote drivers over DECnet after all do all their communications
to unpriv'd servers (well,the servers can do logical i/o but that's
it) from user mode pieces, using a little fiddling to make them
talk to local drivers. The drivers just need to ensure they
get the bits to and from the user.
There are tcp/ip remote disk & tape available free also, but W.
hasn't been using those yet. He might, in conjunction with having
his devices on NT. As it is, he's using a slow cheap IDE disk as
extra VMS storage with the thing.
I/O on the PC end is by the way synchronous. It doesn't attempt to
have several things going at once; this is the same as remote
disk/tape over decnet.
Needless to say, while you could have several systems accessing the
same disk, you must ensure at the VMS end that only one gets
write access, or have the disks named identically and have the
vms systems all in a cluster. There's no file system integration
in here, and obviously the old cheap PC isn't up to it. However,
the old 8088 or 286 box you might otherwise toss, if it will talk
to an ATAPI or IDE drive, can become a VMS disk/tape expansion
controller with this. For those not blessed with rich uncles
this can be wonderful.
|