Re: reaching dos (NCSA) and selecting Vax disks
sandy@ibm550.sissa.it
Wed, 16 Feb 1994 17:48:58 +0100
>>>>> On Wed, 16 Feb 1994 15:43:14 GMT,
J.Petersen@qmw.ac.uk (J.H.Petersen) said:
> ... And now I can reach our local nasty Vax VMS
> cluster, where I print out preprints on the double-sided
> laserprinter. Though it does often seem to hang while I am
> efs'ing to there.
Is this efs, or FTP hanging? If you C-g, efs will pop the *ftp ...*
buffer. If this buffer shows that the FTP command has actually
completed, but efs is still in a wait-state, then efs is not
understanding your server's return codes. If the FTP command has not
been completed, then the problem is with your connection. When testing
this, beware that the command might happen to run at the instant that
you pop the buffer, so experiment a bit, if there is doubt.
> Can one somehow use Vax `environment variables' to change disks,
> as one can in normal ftp?
efs supports unix environment variables in filenames, just like usual
in emacs. It is legal to put USER@HOST constructs in environment
variables. However, doing this might fool autoloading, as efs only
starts doing its own environment variable substitution once it's
loaded. Anyway, autoloading doesn't work right in 1.4. This has been
fixed in 1.5.
> However I can't reach my own PC (with Dos and NCSA TCP/IP server
> software) here when I'm logged in to the local Unix host where
> I'm running Emacs & efs. When I try to find-file on it, it
> logs in, but then complains:
> Can't list dos or OS/2 disks
The NCSA DOS server support is in efs-pc.el, along with many other DOS
servers, and OS/2. If you send me some output from your server, I'll
investigate. PWD should be good for a start. What version of the
server are you running? Also, _exactly_ what did you give as the
filename to your find-file attempt. Your problem should be easy to
fix.
--sandy