home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip:5294 vmsnet.networks.tcp-ip.misc:76 vmsnet.networks.tcp-ip.wintcp:264
- Newsgroups: comp.protocols.tcp-ip,vmsnet.networks.tcp-ip.misc,vmsnet.networks.tcp-ip.wintcp
- Path: sparky!uunet!eco.twg.com!eco.twg.com!reece
- From: reece@eco.twg.com (Reece R. Pollack)
- Subject: Re: WIN-TCP/DECwindows device conflict. Whats's up with that?????
- Message-ID: <1992Nov23.181414.24278@eco.twg.com>
- Lines: 33
- Sender: reece@crash.eco.twg.com (Reece R. Pollack)
- Nntp-Posting-Host: eco.twg.com
- Reply-To: reece@eco.twg.com
- Organization: The Wollongong Group (East Coast Operations)
- References: <1992Nov20.194054.1499@alw.nih.gov>
- Date: Mon, 23 Nov 92 18:14:14 GMT
- Lines: 33
-
-
- In article <1992Nov20.194054.1499@alw.nih.gov>, ramon@helix.nih.gov (Ramon J. Hontanon) writes:
- |>In upgrading our trusty VAXstationII GPX from VMS 5.0 to VMS 5.4 we
- |>found out that our version of The Wollongong Groups's TCP/IP allocates
- |>three devices (GAA0: GAA1: GAA2:) that will need to be used by
- |>DECwindows.
- |>The result: DECwindows refuses to install. The DEC people found this
- |>out, and it seems true, 'cause DECwindows starts fine if I don't run
- |>WIN/TCP. I guess my question is:
- |>
- |>What version of WIN/TCP do I need to go to in order to fix this bug?
- |>
- |>Will we be required to buy the product again, or do we just simply
- |>upgrade?
- |>
- |>The e-mail address of The Wollongong Group would also be appreciated.
-
- This is being investigated off-line, but I thought I'd post an initial
- response for everyone else.
-
- To my knowlege, we do not allocate GAA devices. We're running VMS versions
- ranging from V5.1 through V5.5 with DECwindows or Motif and there should
- be no conflicts.
-
- Here are a couple of email addresses for customer use:
-
- support@twg.com - Support requests
- sales@twg.com - Sales and product info requests
-
- --
- Reece R. Pollack
- Senior Software Engineer
- The Wollongong Group, Inc.
-