Kevin Monceaux wrote: Welcome to the club, Kevin! - If this machine wanted to be at a greater distance from here, it would need to leave this planet. :-( Why can't something like this happen in Germany? -- Andreas Freiherr Vishay Semiconductor GmbH, Heilbronn, Germany http://www.vishay.com

----- Original Message ----- From: "Huw Davies" <Huw.Davies(a)kerberos.davies.net.au> To: <classiccmp(a)classiccmp.org> Sent: Saturday, April 13, 2002 12:51 PM Subject: Re: Free MV3100/80 & Misc (Melbourne, .au) You think you got problems, I own the only Vaxen in this city. Concur. Port Pirie, South Australia. Cheers Geoff in Oz

Hmmm Replying to ones own message, grrr I can't seem to change the system password, here is what I am doing point out anything wrong... I am flolowing the directions from: http://www.vaxarchive.org/swdoc/vms/txt/vmsfaq.txt (the section MGMT5) at the >>> prompt I have entered b/1 this gets me to the SYSBOOT> prompt all good so far. then I type the followning commands: SET/STARTUP OPA0: SET WRITESYSPARAMS 0 CONTINUE this gets me to the $ prompt then I type SPAWN @SYS$SYSTEM:STARTUP And from the VMS faq this leads me to believe that it sould boot up and leave me logged in to the console. and then I could change the password. this doesn't seem to occur, it seems to boot up normaly, and then ask for user/password... Is there anything I am doing wrong? I am using VMS 6.1 if thats a help THanks heaps Benjamin

----- Original Message ----- From: <cvisors(a)carnagevisors.net> To: <classiccmp(a)classiccmp.org> Sent: Friday, April 12, 2002 2:55 PM Subject: Re: Free MV3100/80 & Misc (Melbourne, .au) I think that means you may have a console password enabled. Um. Bad karma. There is an alternate procedure in the VMS System Management Manual involving SYSUAFALT you could give that a go. Cheers Geoff in Oz

----- Original Message ----- From: <cvisors(a)carnagevisors.net> To: <classiccmp(a)classiccmp.org> Sent: Friday, April 12, 2002 7:31 PM Subject: Re: Free MV3100/80 & Misc (Melbourne, .au) Sorry, wrong FROM line, been sending a lot of traffic from that one lately.... The VMS FAQ is a good reference. At the prompt on your machine HELP (like MAN only more useful;^) The directory structure will probably have you scratching your head if you are a unix type. For a start, there is no common root, each device (disk/tape) has a root directory. path is along the lines of DUA0:[000000] for the root directory of drive 0. DOS style DIR works, but CD doesn't the VMS equivalent is SET DEFAULT which is a bit tedious, but you can define an alias for it. There are also utils that will pretty much give you a CD command. full path to a file goes like this: DUA0:[dir.subdir.subdir]filename.extension;version number. DU is disk unit A means it's the first identified controller 0 is the number of the drive on the controller. Tapes are usually MU cd's normally DU. VMS will produce multiple versions of the same file name, very handy when you find you stuffed up SYSTARTUP_VMS.COM (sorta like autoexec.bat). A .COM file is a DCL Script, like a unix shell script in a lot of ways, though probably more powerful. You run a .com file by preceding it with an @ sign. so to run reboot.com you would type @ reboot.com or @reboot. Binary executables are .EXE files, and need to be preceded with the RUN command, also you can't use command line switches with RUN so you need to define an alias for the EXE file, then you can use switches with the alias. Equivalent to unix ROOT is SYSTEM as you have discovered, unlike unix, there are not just two levels of user but everything from read only in a small area to full access to everything, and every variant inbetween. Vaguely reminscent of netware permissions in a way. (Bindery not NDS) Terminal config is via the SET TERMINAL command. SHO TERMINAL will give you the current config of your terminals. Most of the configuration files are in the SYS$MANAGER directory. System EXE files are in SYS$SYSTEM which live on SYS$SYSDEVICE which is the boot drive. These are all system Logicals so you can SET DEFAULT SYS$SYSTEM and it will take you there. There is an edt command but it's ugly, there is a better editor called EVE that works a bit like the dos edit function, it may well be configured already. SHO DEFAULT will show you the name of the current directory. SHO SYSTEM will tell you what processes are running, SHO DEV D will show the status of disks. That should give you a kickstart at least. Any questions drop me a line. CAVEAT: I'm not professionally trained in VMS, though I now manage a VMS system at work, like you I got one dropped in my lap and learned how to drive it, then moved it to my workplace where it's lived happily since. My first vax was rather bigger than yours though :^) You are fortunate to have the docs, the VMS doc set is very good and if you work your way through the system managers manual, the start is "Installing and maintaining a system"(something like that anyway) and it will give you a good walkthrough of it. One other thing, I'll be away on a detachment from the 15th to the 28th (with a brief visit back home on Anzac Day) so email will be on hold til I get back. Will probably sift through some on the eve of the 24th, but might not get time. NetBSD is the only supported one on Vaxen AFAIK. These boxes are happiest with VMS. You can also run DECWindows which is essentially X11 either on DECNET or TCP/IP or both. VMS 6.1 has UCX which is Digitals VMS stack. Or there are third party things. I think there is also a DECNET client for Linux. Used to be one for macs too, I have a Webster Appletalk/Ethernet Gateway that speaks DECNET as well as TCP/IP and Appletalk/Localtalk. Anytime. Cheers Geoff