| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1632.1 | Can't copy from PAULY unsing Ver. 5.0 | CGFSV2::CADAMS | Clint Adams - Calgary, Canada | Wed Sep 07 1988 20:36 | 13 |
|
After a week of trying to get SpudClock from PAULY using FTSV, I have
discovered that since we went to VMS Ver. 5.0 on our MicroVax I cant
copy (FTSV or DCL) from PAULY (I think it's a PRO). I can do a
directory but when I try to copy anything it just sits there, zero
blocks get transfered, no error messages from DecNet, Copy, FTSV,
nobody.
Seems weird, I can copy fine from a Ver 4.7 machine, maybe we have
something setup wrong on our Ver. 5.0 machine. Anybody else tried this
since upgrading.
Regards... Clint
|
| 1632.2 | No problem here... | WINERY::COLLUM | | Wed Sep 07 1988 20:46 | 5 |
| I have V5.0 up and running along with FTSV (or SPOOL as its called
now). Haven't had any problems. I just copied a file from PAULY
using both copy and FTSV.
Jim
|
| 1632.3 | Spudclock | RBW::WICKERT | MAA DIS Consultant | Wed Sep 07 1988 20:56 | 6 |
|
Are there any secrets to using SPUDCLOCK? I've try to use it but
nothing happens!
-Ray
|
| 1632.4 | ok from here | WJG::GUINEAU | | Wed Sep 07 1988 21:57 | 12 |
|
WJG is V5.0. I've used copy/spool to PAULY with no problems.
The same stuff is at: WJG::SYS2:[AMIGA.NEW]
This is where I put new stuff before I download it (gets confusing if I just
mix it with WJG::AMIGA: stuff!). Once I DL it, I move it all to WJG::AMIGA:
John
|
| 1632.5 | | STAR::BANKS | In Search of Mediocrity | Thu Sep 08 1988 00:43 | 9 |
| fwiw:
I've been completely unable to ever copy anything on PAULY from
STAR:: (which runs whatever's the latest, meaning V5.0-n). I used
to have a cohort copy stuff for me from his system (RAINBO, MOSAIC),
but lately, even that doesn't work.
Perhaps, if it ain't the node PAULY itself that's biting us, maybe
something in between?
|
| 1632.6 | | CSC32::J_PARSONS | Like Lesser Birds on the 4 Winds... | Thu Sep 08 1988 11:45 | 2 |
| I've also totally unsuccessful in copying anything from PAULY for
the past several weeks.
|
| 1632.7 | v5 improvements | PUGH::MCDONALDA | | Thu Sep 08 1988 12:43 | 3 |
| I seem to be running 4.7, and just copied some files over before
I read this note!
|
| 1632.8 | | HYSTER::DEARBORN | Trouvez Mieux | Thu Sep 08 1988 14:12 | 9 |
| I've copied and downloaded several files from Pauly to my Amiga.
None of them have successfully DeArced on the Amiga. I get "fails
CRC check" and machine lock-ups every time I try.
I've never had this problem before.
Randy
|
| 1632.9 | | WJG::GUINEAU | | Thu Sep 08 1988 14:17 | 4 |
| I take back my previous reply. I just tried again and can't get anything.
DIR works fine, but COPY or FTSV don't.
John
|
| 1632.10 | File format may be a problem | NAC::PLOUFF | Beautiful downtown Littleton | Thu Sep 08 1988 15:14 | 17 |
| re: .8
Depending on how you download, you may have been bitten by the "many
VMS file format" problem. Some programs like standard VMS (actually
RMS) files, with variable or fixed record lengths. Others insist
on 'stream-LF' format files, which are compatible with Unix-style
C programs. Try using cvtarc to change file formats. What works
for me is:
$cvtarc u filename
then Kermit or VAX-ARC, etc.
From the general thread of this note, people are having a hard time
copying from PAULY::. Paul has mentioned at least once in a previous
note that he either prefers or enforces file transfers outside east
coast business hours. I have had no problem using SPOOL (aka FTSV)
to copy at, say, 8 PM.
|
| 1632.11 | Can't get there from here | MEMORY::SOVIE | SSDD | Thu Sep 08 1988 15:40 | 12 |
|
Pauly has been unavailable to me for at least 2 weeks.
Apollo>dir pauly"amiga"::
%DIRECT-E-OPENIN, error opening PAULY"amiga"::*.*;* as input
-RMS-E-FND, ACP file or directory lookup failed
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Apollo>
I haven't asked my sys$manager why this path is down so long.
dean
|
| 1632.12 | | MTWAIN::MACDONALD | WA1OMM 7.093/145.05/223.58 AX.25 | Thu Sep 08 1988 17:18 | 11 |
| RE: .11
The node PAULY is currently unavailable. It's been up an down for
the past couple weeks, possibly due to a bad board. There have been
a large number of downloads -- i.e., people trying to copy every
file on the machine -- during work hours. This, coupled with the
fact that several of us in the office use it as a printer queue,
may be contributing to some of you not being able to copy files,
and the recent downtime.
Paul
|