INFO-VAX Thu, 18 Jan 2007 Volume 2007 : Issue 35 Contents: Re: "no such file" from one node only RE: "reverse pathworks" ? Re: (Update) Re: Is this a (permanent) disk failure? Re: BACKUP - how much of the tape has been used Re: BACKUP causing alpha node to crash Re: BACKUP causing alpha node to crash Re: BACKUP causing alpha node to crash Re: BACKUP causing alpha node to crash Re: BACKUP causing alpha node to crash Re: DECWindows SET/DISPLAY & CREATE/TERM/DETACH problem on Alphaserver DS10L Re: DECWindows SET/DISPLAY & CREATE/TERM/DETACH problem on Alphaserver DS10L F$SEARCH in date order? How long to really setup a VMS system ? Re: Nonstop UNIX takes another loss Re: Nonstop UNIX takes another loss Re: SIMH hints and tips please Re: SIMH hints and tips please ---------------------------------------------------------------------- Date: 17 Jan 2007 20:18:14 -0800 From: "BIO" Subject: Re: "no such file" from one node only Message-ID: <1169093894.495361.215000@51g2000cwl.googlegroups.com> Everyone - (just to tidy up some lingering loose ends): re: *Every* file? How will deleting two files fix anything then? I guess I misinterpreted Hein's suggestion. A dump/dire on directory files works just fine on both nodes - now. Apparently (I suppose I should have guessed this yesterday, but ...) dump/dire is not intended to be used on non-directory files, but even VMS help doesn't make this clear and the command does run without any suggestion that I'm doing something stupid (other than the crap-out message). Hindsight is wonderful. re: This was run on the bad node. Right? Yep. Both nodes. re: But did he also do a ANA/DISK/REPAIR from the "good" node and then from the "bad" node ? Yep. Both nodes. And thank you all for your suggestions, but it is now too late to do any further investigation. Ingemar ------------------------------ Date: Wed, 17 Jan 2007 21:29:52 -0500 From: Subject: RE: "reverse pathworks" ? Message-ID: <63A4454BFCE1C048B2683DBB63A363330136100D@ETP-CIN-US-EX01.etp1.com> -----Original Message----- From: mb301@hotmail.com [mailto:mb301@hotmail.com]=20 Sent: Tuesday, January 09, 2007 5:55 AM To: Info-VAX@Mvb.Saic.Com Subject: Re: "reverse pathworks" ? Pierre wrote: > hi, > > with pathworks (ou SAMBA) I can access OVMS file from a PC. is there a > way to reverse this process and access PC files from OVMS ? > > TIA, > Pierre. Have you heard of a product called "LANutil32" for OpenVMS it allow you to copy/get files from PC. Example- $ landir \\my_pc\sharename%\ntusername:ntpassword Volume <\\my_pc\> has no label. Directory of \\my_pc\ autoexec.dat config.sys . . To put a file or .bat procedure. $ create fred.bat cd \ echo "hello" ^z $ lanput fred.bat \\my_pc\sharename%\ntusername:ntpassword Works from VAX/VMS V5.5-2 though to OpenVMS 7.3-2. I don't believe they are devloping the product any more. Also the paswords are sent in clear text.=20 ------------------- What is the hesitation with Samba? I use Samba to push PDF's created by our MANMAN MRP system out to our Citrix environment. The following command line connects and pushes out the entire structure: $ smbclient "''share_name'" "''password-goes-here'" "-I" server-name "-U" "AD username" "-W" "domain" -c "cd ""''citrix_target'""; ls; prompt ; recurse; mput Accounting; mput Manufacturing; mput OTHER; mput Sales; ls" Barry Treahy, Jr =20 Vice President/CIO Midwest Microwave, Inc. Emerson Network Power Connectivity Solutions E-mail: Barry.Treahy@EmersonNetworkPower.com Phone: 480/314-1320 Cell: 480/216-9568 Fax: 480/661-7028 =20 ... but it's a DRY HEAT! This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorized to retain, read, copy or disseminate this message or any part of it. =0D ------------------------------ Date: 17 Jan 2007 21:52:46 -0800 From: TFTAJLLYMXZP@spammotel.com Subject: Re: (Update) Re: Is this a (permanent) disk failure? Message-ID: <1169099566.769712.45490@q2g2000cwa.googlegroups.com> No worries, this is simply a hobbyist system. I imagine that if I were PAID to run a system, and posted what I did, I wouldn't have a job very much longer! Cheers, Alder There's not much on the disk to backup, since I use it entirely for user home directories, and I'm about the only person ever logging in. I do that as SYSTEM 99 times out of a 100. Richard B. Gilbert wrote: > TFTAJLLYMXZP@spammotel.com wrote: > > Strangely, the disk in question mounted without complaint today. I had > > left the machine powered down for two days because of other priorites > > around here, and because the machine failed to complete the initial > > boot cycle - stopping before reaching the ">>>" prompt - immediately > > after my last posts on this topic. > > > > Well, today I can report that all is again well. Like most of us, > > there's nothing like a little nap to improve our disposition. I had > > slid the machine over a few feet the day I noticed the drive had gone > > down, so it appears that all has settled in at the new location. Hard > > to know, exactly, but all's well that ends well. > > > > Thanks to everyone who offerred ideas on this. > > > > Cheers, > > > > Alder > > I hope you are making regular backups of this disk. Your problems may > be been due to a chance glitch that will never happen again but I > wouldn't count on it. If it were mine and at a commercial site, I'd > have it replaced or move it to somewhere that was not critical. > > You DON'T want to have your pager go off at three AM some morning and > learn that the disk has failed, cannot be revived, and has hosed a > critical job! ------------------------------ Date: 17 Jan 2007 16:44:27 -0800 From: "AEF" Subject: Re: BACKUP - how much of the tape has been used Message-ID: <1169081067.671188.99280@q2g2000cwa.googlegroups.com> Andrew Black (delete obvious bit) wrote: > Hi > I run a number of BACKUP to saves sets on a DLT > Is there a way of finding out at the end of it how much of the tape has > been used? > > Andrew If you don't use compression (or "compaction") and you use BACKUP/LIST you can look at the totals at the end of each save-set listing. Multiply the sum of those totals by 512 bytes and that's how much tape you've used up, more or less (uh, add 10% for redundancy groups unless you used /GROUP=something-other-than-10). AEF ------------------------------ Date: 17 Jan 2007 23:43:35 +0100 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: BACKUP causing alpha node to crash Message-ID: <45aeb4a7$1@news.langstoeger.at> In article <45ae2b17$0$9523$c3e8da3@news.astraweb.com>, JF Mezei writes: >So a directory listing on the FTP site could look like: > >FTP> ls >200 PORT command successful. >150 Opening ASCII mode data connection for file list. > >000_ALPHA_V83A_MASTER_ECO_LIST.ZIPEXE >000_ALPHA_V83A_MASTER_ECO_LIST.txt >001_VMS83A_RMS-V0100.ZIPEXE >001_VMS83A_RMS-V0100.txt >002_VMS83A_ADDENDUM-V0200.ZIPEXE >002_VMS83A_ADDENDUM-V0200.txt >003_VMS83A_SECSRV-V0100.ZIPEXE >003_VMS83A_SECSRV-V0100.txt >004_AXP_DNVOSIECO01-V83.ZIP >004_AXP_DNVOSIECO01-V83.txt >005_VMS83A_UPDATE-V0100.ZIPEXE >005_VMS83A_UPDATE-V0100.txt > >This way, you would know that 006 is the latest kit, no matter what date is > show by the FTP server. And you would see a clear order that the patches >of various names (UPDATE, ADDENDUM etc) were released. No way. If another UPDATE ECOs appears which replaces some but not all of the ECOs in the directory, all files would have to be renamed just to follow your numbering scheme... -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ------------------------------ Date: 17 Jan 2007 23:49:35 +0100 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: BACKUP causing alpha node to crash Message-ID: <45aeb60f$1@news.langstoeger.at> In article , norm.raphael@metso.com writes: >My quibble with UPDATE ECO's is that they become prerequisites, so they >must be installed even if one has previously installed each component >ECO as it was released. What is the problem with that? Reboot/Downtime? PCSI does not replace files when the files in the kit are not newer than the ones on disk. If you have all included ECOs installed, the installation would not replace anything (except the PCSI history) and you could avoid rebooting (even if the ECO release notes state that a reboot is required). But UPDATE does most likely include more than you have already installed... > I think there ought to be a way to run the UPDATE >ECO that skips those component patches already in place and marks the >database that UPDATE Vxxxx has been applied, and/or just the marking if >the system manager determines that all ECO's in it that are needed on that >instance have been applied (This is because sometimes ECO's that are not >mandatory are included in UPDATE ECO's - which seems counter-intuitive). Have you tried that this is not already the case with PCSI? -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ------------------------------ Date: 17 Jan 2007 23:41:09 +0100 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: Re: BACKUP causing alpha node to crash Message-ID: <45aeb415@news.langstoeger.at> In article , rdeininger@mindspringdot.com (Robert Deininger) writes: >Dunno what you mean by "master ECO text". ALPHA_VxxA_MASTER_ECO_LIST.TXT >You should definitely consider the release notes required reading before >you install a patch. Yup. >Naming conventions for VMS patches have evolved a bit over the years, but >here are some guidelines... > >1. When patches have the same name (e.g. V83A_ADDENDUM), the one with the >highest version supersedes all the others. The content is cumulative. >You would rarely, if ever, need to install V0100 and V0200. If V0200 is >shipping, V0100 is redundant. Yes, now it is. But I was once bitten by a SYS ECO which did not replace all lower numbered SYS (?) ECOs on that platform. IIRC, it was on VAX (= VMSINSTAL). It was clearly stated in the release notes of this ECO, but I didn't read it carefully enough (means say version 9 replaced version 3, 4 and 6, but not v1,2,5,7 and 8 and I assumed if I install v9, it's the only ECO I need) >4. UPDATE kits have been used for quite a few releases now. Generally, >there is NO new content in UPDATE kits; they are just bundles of existing >patches. UPDATE kits are made specifically to reduce the work of >installing individual patches. But we all were bitten more than once, where the UPDATE kit contained more than the sum of all the ECOs it contained/replaced. And where it also was not cleary stated in the release notes what else got fixed. So, always install the UPDATE ECO, even then if you already have all ECOs installed it supercedes. If the UPDATE ECO is only the sum of all ECOs it replaces, there is no harm, as the files don't get replaced if the images in the kit are not newer than on disk. But if it is more than the sum, you're on the safe side. >Generally all customers should install UPDATE kits. UPDATE kits will >usually be prequisites for most patch kits that come later. And that is the other reason to always install the UPDATE kit. And the last reason is, that UPDATE ECOs are "installation rating: 1" where they contain/replace ECOs of "installation rating: 3" which you were not allowed to install cause of company policy (eg. 'we don't have the problem' until 2 weeks later you were bitten by it) My personal policy is to keep all my machines on the same ECO level (after some tests of course) even for rating 3 ECOs where/when only one system had the bug and not all others... >UPDATE kits usually get an extended test cycle, so when they are issued >there may be a few very recent individual patches that are NOT included in >the UPDATE. Not only. Some ECOs are explicitely not included in the UPDATE ECO even if they are months old. Why could be open to discussion, but is not. >5. I think ADDENDUM kits are a recent (V8.3?) addition to the lineup. >These are basically "stuff that didn't make it in time for the release", >or "stuff that didn't make it in time for the previous ADDENDUM kit". >Alas, occasionally there is "stuff to fix stuff in the previous ADDENDUM >kit". ADDENDUM was the first ECO for V8.3. UPDATE is currently the only V8.3 ECO on Alpha... -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ------------------------------ Date: Wed, 17 Jan 2007 21:14:30 -0500 From: JF Mezei Subject: Re: BACKUP causing alpha node to crash Message-ID: <45aed860$0$8766$c3e8da3@news.astraweb.com> Peter 'EPLAN' LANGSTOEGER wrote: > No way. If another UPDATE ECOs appears which replaces some but not all > of the ECOs in the directory, all files would have to be renamed just > to follow your numbering scheme... No. That is the whole point of sequential numbering. Patches would be listed in the order in which they were released. So you would know that a patch numbered 010 is more recent than one numbered 009. Anyways, this is moot. I seem to be the only one with this opinion. ------------------------------ Date: Thu, 18 Jan 2007 02:59:00 GMT From: John Santos Subject: Re: BACKUP causing alpha node to crash Message-ID: Peter 'EPLAN' LANGSTOEGER wrote: > In article <45ae2b17$0$9523$c3e8da3@news.astraweb.com>, JF Mezei writes: > >>So a directory listing on the FTP site could look like: >> >>FTP> ls >>200 PORT command successful. >>150 Opening ASCII mode data connection for file list. >> >>000_ALPHA_V83A_MASTER_ECO_LIST.ZIPEXE >>000_ALPHA_V83A_MASTER_ECO_LIST.txt >>001_VMS83A_RMS-V0100.ZIPEXE >>001_VMS83A_RMS-V0100.txt >>002_VMS83A_ADDENDUM-V0200.ZIPEXE >>002_VMS83A_ADDENDUM-V0200.txt >>003_VMS83A_SECSRV-V0100.ZIPEXE >>003_VMS83A_SECSRV-V0100.txt >>004_AXP_DNVOSIECO01-V83.ZIP >>004_AXP_DNVOSIECO01-V83.txt >>005_VMS83A_UPDATE-V0100.ZIPEXE >>005_VMS83A_UPDATE-V0100.txt >> >>This way, you would know that 006 is the latest kit, no matter what date is >> show by the FTP server. And you would see a clear order that the patches >>of various names (UPDATE, ADDENDUM etc) were released. > > > No way. If another UPDATE ECOs appears which replaces some but not all > of the ECOs in the directory, all files would have to be renamed just > to follow your numbering scheme... > Why? JF's scheme allows skipped numbers (for withdrawn or obsolete patches). The main problem, as I see it, is that there way to many obsolete patches in the directories. By "obsolete", I mean patches that have been replaced3 by UPDATE ECOs. Until they recently zapped all the dates (05-Jan-2006), you could tell which ones were recent by the dates, but that doesn't work any more. Its not a big deal with V8.3, because there aren't that many patches yet, but take a look at V7.3-2 (Alpha). There are about 150 files in the directory. If any new ECOs were released between the last time I looked (mid December) and Jan 5, good luck finding them. Check the version numbers of all 150 against $ product show history (which doesn't support "/page", by the way.) It's way to easy to miss something. And I do keep a file listing all the ECOs I've applied on all the systems I currently manage (3 vaxes, 14 Alphas, 1 Itanium, clusters with common system disks only listed once) with dates installed, status (withdrawn, replaced, obsolete, bundled into an UPDATE ECO, etc.) I do subscribe to the ECO notification mailing list, but it's not perfect (or my spam filter has eaten some of the notifications and I didn't notice.) Moving the obsoleted ECOs to a subdirectory would help a lot. (Or maybe a set of subdirectories, e.g. ./obsolete-UPDATE-V0100, ./obsolete-UPDATE-V0200, etc.) -- John Santos Evans Griffiths & Hart, Inc. 781-861-0670 ext 539 ------------------------------ Date: 17 Jan 2007 12:41:21 -0800 From: "urbancamo" Subject: Re: DECWindows SET/DISPLAY & CREATE/TERM/DETACH problem on Alphaserver DS10L Message-ID: <1169066481.761420.168600@v45g2000cwv.googlegroups.com> OK, I'm still having this problem. I've tried everything I can think of, but short of reinstalling OpenVMS I can't find anything else to try. It is DEFINITELY a problem with DECWindows. I can telnet from the Alpha to port 6000 and this is opened, I can display X-applications from the VAX no problem, the alpha just isn't trying. Anyone get any other suggestions I would be most greatful. Thanks, Mark. Bob Koehler wrote: > In article <1168552763.671601.148190@i56g2000hsf.googlegroups.com>, "urbancamo" writes: > > Please help! > > > > I've got a VAXStation 4000/90 and an Alphaserver DS10L. I can > > SET/DISPLAY from the VAX and CREATE/TERM/DETACH a DECTerm on my Linux > > laptop, but the Alphaserver refuses to open one. I am using OpenVMS > > 7.3-1 on both. The DS10L does not have a graphics card installed, the > > VAX does. I wasn't aware this would make any difference when starting X > > applications on a remote terminal. > > > > Are you sure the Linux X server is allowing the Alpha to connect? > Usually xhost is the control mechanism, but I could conceive of a > mechanism which uses back-translation of the IP address. > > Try an explicit xhost+ of the Alpha's IP address, and if that > doesn't work, a onetime xhost+ (allowing everyone in). > > I'm assuming you're using the same protocol to access the Alpha > from Linux as you do the VAX, not getting SSH on one and TELNET > on the other. ------------------------------ Date: 17 Jan 2007 20:03:22 -0800 From: "David B Sneddon" Subject: Re: DECWindows SET/DISPLAY & CREATE/TERM/DETACH problem on Alphaserver DS10L Message-ID: <1169093002.413504.18780@v45g2000cwv.googlegroups.com> urbancamo wrote: > OK, > > I'm still having this problem. I've tried everything I can think of, > but short of reinstalling OpenVMS I can't find anything else to try. Reinstalling is not the VMS way... > It is DEFINITELY a problem with DECWindows. I can telnet from the Alpha > to port 6000 and this is opened, I can display X-applications from the > VAX no problem, the alpha just isn't trying. > > Anyone get any other suggestions I would be most greatful. > > Thanks, > > Mark. Are you still using DHCP on the Alpha? Why? Turn it off, configure a fixed address and use xhost on the Linux box as already discussed. What are the boxes connected to? A hub? A switch? Grab a copy of DBS-ETHERWATCH and install it on the VAX and watch what traffic is actually going over the network between the Alpha and Linux box. Dave ------------------------------ Date: Wed, 17 Jan 2007 16:59:03 -0600 From: geary@eris.io.com (Mark Geary) Subject: F$SEARCH in date order? Message-ID: <1PudnczmwoOqNzPYnZ2dnUVZ_u-unZ2d@io.com> One of my co-workers needs to process all files in a directory in date order, starting with the oldest. It's been five years since I worked on this system and I can't remember the proper DCL incantations to do this. Under the Bourne Shell (what I'm doing these days) I would say: for i in $(ls -rt1); do process $i done I remember using F$SEARCH, but that gives files in alphabetic order and I can't find any way of sorting them by date. Can anyone help? Mark Geary -- Don't forget to stop and eat the roses. ------------------------------ Date: Thu, 18 Jan 2007 01:18:53 -0500 From: JF Mezei Subject: How long to really setup a VMS system ? Message-ID: <45af117a$0$5323$c3e8da3@news.astraweb.com> OK, I know, insert CD, boot the alpha from CD and follow the prompts and you have VMS running in about an hour. But in reality, how long does it REALLY take to get a virgin system fully loaded with all the prerequisite stuff, configured, tested and ready to go into production without any more improvements being done to it ? (I am talking about full IP stack, extra utilities like ethermon loaded, SNMP/syslog configured to talk to the rest of the corporate network, email, various automated system monitoring tasks , handling if system failures and ensuring the systartup_vms and shyshutdown procedures are complet and robost etc etc. In other words, how long does it take to get a system from fully naked to fully dressed in formal wear, realy to go a lights out fully automated state ? (as opposed to a customer starting to be able to use it even though the system may still need nightly reboots to test new procedures etc) ------------------------------ Date: 17 Jan 2007 14:10:13 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: Nonstop UNIX takes another loss Message-ID: In article , rdeininger@mindspringdot.com (Robert Deininger) writes: > In article <1169042285.377185.315540@51g2000cwl.googlegroups.com>, > "n.rieck@sympatico.ca" wrote: > >>Nonstop UNIX takes another loss as the Toronto stock exchange moves to >>LINUX on AMD Opteron or Intel Xeon >> >>http://www.itbusiness.ca/it/client/en/home/News.asp?id=41862 > > I wonder what they mean by "HP NonStop Unix". That name isn't familiar to me. Just another "expert" reporter who thinks "if it isn't a PC, then it must be UNIX". ------------------------------ Date: 17 Jan 2007 12:31:32 -0800 From: "n.rieck@sympatico.ca" Subject: Re: Nonstop UNIX takes another loss Message-ID: <1169065892.501523.148290@a75g2000cwd.googlegroups.com> Robert Deininger wrote: > In article <1169042285.377185.315540@51g2000cwl.googlegroups.com>, > "n.rieck@sympatico.ca" wrote: > > >Nonstop UNIX takes another loss as the Toronto stock exchange moves to > >LINUX on AMD Opteron or Intel Xeon > > > >http://www.itbusiness.ca/it/client/en/home/News.asp?id=41862 > > I wonder what they mean by "HP NonStop Unix". That name isn't familiar to me. IIRC, Compaq purchased Tandem in 1997 and DEC in 1998. (HP later merged with Compaq but I digress). Tandem had some really cool hardware used by some financial institutions and stock excanges which allow two CPUs to run together in lock-step fashion through some custom glue, When one the CPUs failed to match the other, the glue was used to determine which one was at fault while isolating the other. They called this technolog NonStop. NonStop functions were supposed to be added to Alpha but this idea was later scrapped, Neil Rieck Waterloo, Ontario, Canada, http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: 17 Jan 2007 14:43:25 -0800 From: "David B Sneddon" Subject: Re: SIMH hints and tips please Message-ID: <1169073805.106185.279180@11g2000cwr.googlegroups.com> VAXman-@SendSpamHere.ORG wrote: > Now I have a couple of questions. > > 1. Can you still use the Mac when SimH/VAX is running? I recall it > was quite a CPU hog. Yes it is a bit of a CPU hog but MacOS seems to handle it well and you can do other things when simh is running. > 2. Can you access both the SimH/VAX and the Mac OS X? Yes, for example I can ssh from work into my iMac, start simh then use DECnet over IP from work into the simh/VAX. > 3. Could I fire up X11 on the Mac and then access the SimH/VAX run- > ning on the Mac? Don't know about that one, never tried it. > > -- > VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM Dave ------------------------------ Date: Thu, 18 Jan 2007 02:09:29 +0100 From: Paul Sture Subject: Re: SIMH hints and tips please Message-ID: In article <00A61DD8.CC30AC50@SendSpamHere.ORG>, VAXman- @SendSpamHere.ORG wrote: > In article , Paul > Sture writes: > > > > > >Update. > > > >I've found out that you don't need to run it via sudo. You can change > >the ownership of /dev/bpf* - though I'm in unfamiliar territory here, > >and don't know the potential security pitfalls *there*. Perhaps someone > >knowledgeable in Unix could comment on that... > > > >Having got my Simh VMS system talking to the outside world to fetch ECOs > >etc, I then discovered that I could no longer reach the Mac from the > >outside world. This turned out to be the port forwarding behaviour of my > >router. As opposed to previous routers I have owned, with this one you > >specify the MAC address rather than the IP address. As a result, > >incoming connections were being routed to the Simh/VAX IP address rather > >than the Mac one. The only cure was to reboot the router. > > > >This took some prolonged head scratching (and a few curses on the way) > >:-) > > > >The solution there for me was to use my Airport card as well as the > >normal ethernet connection and use different MAC addresses for the > >Simh/VAX and the Mac itself. > > Now I have a couple of questions. > > 1. Can you still use the Mac when SimH/VAX is running? I recall it > was quite a CPU hog. Yes. Simh runs in "nice" mode - at a lower priority. It appears to soak up all the idle CPU, but I'm not seeing any slowdown due to that. Heavy I/O isn't too friendly, but that's the case for Mac apps anyway on this system. > 2. Can you access both the SimH/VAX and the Mac OS X? > Access from where? I can use the router's port forwarding to connect with, say, telnet on one and ftp on the other. However, I can't yet ping between the two (I thought I could at one stage, but not at the moment). > 3. Could I fire up X11 on the Mac and then access the SimH/VAX run- > ning on the Mac? Not until I can at least ping between the two - I'm not sure I trust my router (which is doing the wireless connection too) to be doing the right thing here... Sigh, it's late here now; I'll have another go tomorrow, and see what tcpdump et al reveal. -- Paul Sture ------------------------------ End of INFO-VAX 2007.035 ************************