🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: cu.slug
Article #374

Band transfer

#374
From: reti
Date: Wed, 10 Dec 1997 00:00
23 lines
1534 bytes
    Date: Mon, 8 Dec 1997 18:24 EST
    From: David Gadbois <gadbois@cyc.com>

    I picked up some XL1201s recently and have been having some strange
    networking problems with a few of them.  Every thing works great,
    except for band transfer.  Some times it works, sometimes it doesn't.

Does nothing at all happen? Do blocks transfer but not checksum?  Does it
go into the debugger?  Do the Peek network meters show errors?

    I have tried replacing networking gear, isolating machines, both the
    Chaos and TCP transports.  There doesn't seem to be any correspondence
    with the I/O or processor board revision levels.  The fact that only
    band transfer is affected makes me think there is a software or
    configuration problem.  One possibility is the version 333 IFEP files,
    which I haven't used before.  Any ideas?

The I333 fep files aren't involved in any kind of network activity.

    --David Gadbois

    Food for Mabry's daemon: Lisp.
Technical Details
Message-ID: <881805435.27392@news.Colorado.EDU>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <199712082324.RAA29112@Wiggum.cyc.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10077e,5af369ef70cb6d2f
X-Google-Attributes: gid10077e,public
From: reti@ai.mit.edu
Subject: Band transfer
Date: 1997/12/10
Message-ID: <881805435.27392@news.Colorado.EDU>
X-Deja-AN: 297093396
Distribution: cu
Sender: daemon@lace.colorado.edu
References: <199712082324.RAA29112@Wiggum.cyc.com>
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <19971211014422.8.RETI@[128.52.40.65]>
Organization: University of Colorado at Boulder
Newsgroups: cu.slug