| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2900.1 | | BAGELS::BRANNON | Dave Brannon | Thu Sep 07 1989 20:18 | 6 |
| a NDU disk is a single VMS file, not a VMS directory. So the
quick answer is no. How about using DECnet-DOS's NFT to directly
copy the files from those directories to your pc. That can also
be incredibley fast.
-Dave
|
| 2900.2 | Nothin works on the first try..... | SHARE::DOYLE | | Fri Sep 08 1989 17:00 | 12 |
|
re .1
I tried using nft, getting examples out of the Vaxmate MSDos book.
However I fear I'm not getting my Syntax right.
Could you type out an Example line?
Also I believe I need to define the Address of the node I wish to
transfer from.
Is this correct?
If so, how can I get these Addresses?
Thanx Ed
|
| 2900.3 | | BAGELS::BRANNON | Dave Brannon | Fri Sep 08 1989 20:55 | 17 |
|
to define the node:
1. type NCP
2. then type HELP DEFINE NODE
that will tell you the syntax to define a node address and node
name. Or if you already a have a VAX system defined you can
just do a COPY NODE new_nodename FROM nodename (that will go
look up the new_nodename in the nodename's NCP database and copy
it to your NCP database)
using NFT gets tricky depending on the RMS file type. If it is
a Stream_lf file, use NFT COPY/BLOCK remote_filespec *.*
otherwise just use NFT COPY remote_filespec *.*
-Dave
|
| 2900.4 | its easy and fast too... | NAC::BRANNON | value added | Sat Sep 09 1989 00:48 | 16 |
| Most of the DECnet-DOS and DECnet-VAXmate programs have a builtin
help command.
ncp help
nft help
etc.
I've been using things like
"nft copy/block norse::amiga:[upload]*.* b:"
to automagically pull them across the net and down to my floppy
to bring home.
Now if only there was a DECnet-Amiga from Digital...
regards,
dennis (DECnet-DOS Development)
|
| 2900.5 | seems too slow. | SHARE::DOYLE | | Mon Sep 11 1989 13:43 | 7 |
| Well, I was able to define the nodes and use nft, (Thanks Guys!).
But I'm only getting rates of 198-398 bytes per second.8'(
Vms copying seems to be the fastest and then transfer from my M: drive to
A: drive using Decnet.
Are 198-398 bytes per second typical?
Ed
|
| 2900.6 | sometimes it is | BAGELS::BRANNON | Dave Brannon | Mon Sep 11 1989 17:50 | 15 |
| the speed really depends on what the network path is between
you and that remote system.
I usually do all copying with FTSV on the VAX directory, check to
make sure everything is in stream_lf format and then use NFT
COPY/BLOCK to get it to the pc (that way doesn't tie up the pc for
so long). Blazing speeds over the same ethernet segment.
Coping directly from the remote VAX to my pc is usually done only
when I'm almost out of quota on my VAX account, because of the
speed difference you mentioned - a slow file copy ties up the
use of the pc too long, makes you really appreciate operating
systems that can walk and chew gum at the same time :-)
-Dave
|
| 2900.7 | | NAC::BRANNON | value added | Wed Sep 13 1989 22:06 | 12 |
| re .5:
M: drive??? Sounds like PCSA rather than just DECnet-DOS.
What ethernet card are you using? And what version of PCSA?
What version number does nft<return> display?
The bytes per second figure is related to how long it took to copy
from the remote system. Try comparing numbers with copying the
same files from your local vax with nft.
dennis
|