IP: you need a UCX license or a NET-APP-SUP-250 (or higher number) license loaded. Next set def sys$manager and @tcpip$config Note this assumes that you've installed TCPIP along with VMS. It's an optional item to install like DECnet. The DEC IP stack supports telnet, ftp and xdm. Filesystem: yes I understand what you mean. I run two Tru64 unix systems and a linux box and have the same problems with those as you now have with VMS :-) The two OSes are not that dissimilar even though initial appearances might be deceiving. Verzonden vanaf mijn draadloze BlackBerry -toestel -----Original Message----- From: Mark Benson <md.benson at gmail.com> Sender: owner-hecnet at Update.UU.SE Date: Sat, 18 Jun 2011 11:17:54 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Introduction On 18 Jun 2011, at 08:43, hvlems at zonnet.nl wrote: Is the alpha on the network and does it have IP running? Not yet. I need to get on that. I get twitchy having enterprise hardware with no LAN. I assume one it's on a LAN I can telnet or SSH it? Did you already learn about search paths? A logical name like sys$manager translates to sys$sysdevice:[sys0.sysmgr] but also to another logical name: sys$startup. Which translates to another directory (to improve confusion). Ah. Yes, see what I mean. As a long time UNIX nerd the filesystem doesn't seem so 'logical' to me :) EDIT doesn't work you said. How about SET TERM/DEV=vt100 EDIT whatever Yep that would have been it. I complained the CRT (maybe meant terminal) wasn't ANSI enabled. Would have worked if i'd told it it was a VT100 terminal. Thanks :) I should know that, a lot of UNIXs require terminal spec at login in single user mode too. -- Mark Benson My Blog: <http://markbenson.org/blog> Follow me on Twitter: http://twitter.com/mdbenson "Never send a human to do a machine's job..."