Path: utzoo!utgpu!ugw.utcs.utoronto.ca!CUNYVM!IBMTCP-L Date: Mon, 12 Feb 90 06:52:26 EST Reply-To: IBM TCP/IP For VM List Sender: IBM TCP/IP For VM List From: no-name To: UofToronto LAN redistribution Message-ID: <90Feb12.071820est.58291@ugw.utcs.utoronto.ca> Newsgroups: list.ibmtcp-l Distribution: ut Approved: devnull@gpu.utcs.toronto.edu Ethernet connections for TCP/IP on IBM ====================================== The following summarises the dilemma we are currently faced with. Presumably others have had to face the same problem and I would be pleased to hear of any comments. We have been users of FAL since its initial release, and also used its predecessor (DRG) for a short time before this. Our Ethernet connection is using an old DACU, which is no longer supported by IBM, although it currently works very well without any problems. However we have heard of other users who having experienced problems with their DACU are unable to get it fixed for weeks or even months. As TCP/IP connection from our IBM is fairly critical to our operations this gives arise to some qualms. We could replace the DACU with an 8232, but this is expensive and really gives us no extra function. It is however supported at the moment, but I believe this too will become obsolete soon (when the 3172 (?) becomes available). We therefore have the choice of: 1. Sticking with the DACU, and crossing our fingers. 2. Replacing it with the 8232 now, if we can afford it. 3. Hanging on so we can replace it with the new box, hoping that the DACU will survive until then. I should be interested to hear how other sites have reacted to this situation and why. Is there a 4th alternative? Anything that involves source modification to FAL is questionable as we don't have the VS/Pascal pp (We are still using the old Pascal/VS). Also is there any statement about continuing support for the DACU in FAL? Chris King (Philips Research Laboratories, Redhill, Surrey, U.K.) (e/mail - kingcb@prl.philips.co.uk)