home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!bu.edu!wupost!darwin.sura.net!paladin.american.edu!auvm!HARBORUC.BITNET!PARLOW
- From: PARLOW@HARBORUC.BITNET (AFP)
- Newsgroups: bit.listserv.dectei-l
- Subject: vax PUBLIC ACCESS COMMUNICATIONS software and VMS v5.5/PROBLEM
- Message-ID: <01GQTXB3FK800001HK@HARBORUC.BITNET>
- Date: 6 Nov 92 20:13:00 GMT
- Sender: "DEC's The Education Initiative Discussion List"
- <DECTEI-L@UBVM.BITNET>
- Lines: 20
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- X-Envelope-to: DECTEI-L@UBVM.BITNET
- X-VMS-To: IN%"DECTEI-L@UBVM.BITNET"
-
- We've been using the VAX Public Access Communicatios program (VAX PAC) for quite
- some time with NO problems, UNTIL we upgraded to VMS 5.5.
-
- A Description of Our Configuration:
-
- 8 stand-alone VAX nodes, 4 running VMS 5.4-3, 1 running VMS 5.5, 2 running VMS
- 5.5-1 and one running VMS 5.5-2HW. Our modems are attached to DS200 terminal
- servers running 3.1 version of terminal server software. We have
- version 1.3 of VAX PAC.
-
- A Description of the Problem:
-
- When a user on a node running VMS 5.5 tries to use a modem that is already in
- use on a different node, the VAX PAC program fails with an access violation.
- This problem does not occur on nodes running VMS 5.4-3.
-
- Has anyone else experienced this problem? If so,
- how did you cope with the problem?
-
- Please help! Thank you.
-