home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.networks.tcp-ip.multinet:2621 vmsnet.mail.pmdf:2828
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!waikato.ac.nz!canterbury.ac.nz!chmeds.ac.nz!gordon
- Newsgroups: vmsnet.networks.tcp-ip.multinet,vmsnet.mail.pmdf
- Subject: New Multinet with Old PMDF - Can it be?
- Message-ID: <1993Jan7.181626.167@chmeds.ac.nz>
- From: gordon@chmeds.ac.nz
- Date: 7 Jan 93 18:16:25 +1200
- Lines: 29
-
- Problem: old version of PMDF, new version of Multinet don't get on.
-
- Situation: VMS 5.5, I just installed Multinet 3.1. We are still using
- PMDF version 3. I'd like to upgrade, just now that isn't an option as we
- haven't the money. We might be able to later, but the problem is now.
-
- Mail in fails. An opcom message from multinet server indicates that the server
- failed, "service SMTP: abort" (that's all, apart from the PID).
-
- The installation process requires that the file multinet:smtp_server.exe
- be replaced with the PMDF-supplied version. I did that; but its an old
- .exe file, and may be built with an inappropriate version of the Multinet
- libraries. Rebuilding from the PMDF distribution screws up - it wants a
- file [multinet-plus.lib]lib.olb, which of course no longer exists (its an
- *OLD* version of PMDF).
-
- The PMDF configuration file is exactly as we had for CMUTEK TCP/IP, with
- the obvious change of CTCP to MTCP.
-
- Has anyone got PMDF version 3 running with a modern Multinet? Or any
- suggestions to tide things over until we can get PMDF version 4.1?
-
- Cheers
- Gordon, terribly perplexed
- ---
- Gordon Findlay, Computer Scientist, Christchurch School of Medicine
-
-
- Mail temporarily to chchmeds@otago.ac.nz (their system works!)
-