home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!news.nd.edu!mentor.cc.purdue.edu!pern.cc.purdue.edu!smb
- From: smb@pern.cc.purdue.edu (Scott M. Ballew)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: ParNet problem
- Keywords: parnet
- Message-ID: <Bzo2Ew.L6o@mentor.cc.purdue.edu>
- Date: 22 Dec 92 15:16:08 GMT
- References: <1992Dec21.222306.26860@cc.uow.edu.au>
- Sender: news@mentor.cc.purdue.edu (USENET News)
- Organization: Purdue University
- Lines: 27
-
- In article <1992Dec21.222306.26860@cc.uow.edu.au> beato@cc.uow.edu.au (Michael Beaton) writes:
- > ...
-
- > The network comes up ok but it doesn't work for very long, sometimes
- >only a few seconds, but usually for a couple of minutes. I can access files
- >for a while but then the machine that I'm using to access the others files,
- >hangs and sometimes the other machine resets with a software error.
-
- > ...
-
- > Also how long can the cable be ?? It's about 3 metres long.
-
- This is a problem I saw when we recently moved. When we set up our
- A2000 (server) and A1000 (client), the A1000 would seem to work for a
- while, then it would either guru (GOMF caught these), hang, or just
- plain fail to correctly read a file. Since we had just built a new
- cable, I checked it and rechecked it several times for problems.
- Finally, we went back to the older cable and some extra jumpers to
- make up the length. All worked fine. My best guess is that we had a
- problem with crosstalk between wires in the new cable. Both the
- working and non-working cables were about the same length 17 feet
- (certainly more than 3 meters) but the working cable is a flat ribbon
- cable and the other was a 25 wire bundle. This may be what you are
- experiencing. Does anyone have a _real_ maximum length for these
- cables?
-
- Scott
-