usr/share/man/cat4/vax/acc.0

ACC(4)            BSD Programmer's Manual (VAX Architecture)            ACC(4)

N\bNA\bAM\bME\bE
     a\bac\bcc\bc - ACC LH/DH IMP interface

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     p\bps\bse\beu\bud\bdo\bo-\b-d\bde\bev\bvi\bic\bce\be i\bim\bmp\bp d\bde\bev\bvi\bic\bce\be a\bac\bcc\bc0\b0 a\bat\bt u\bub\bba\ba0\b0 c\bcs\bsr\br 1\b16\b67\b76\b60\b00\b0 v\bve\bec\bct\bto\bor\br a\bac\bcc\bcr\bri\bin\bnt\bt a\bac\bcc\bcx\bxi\bin\bnt\bt

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     The a\bac\bcc\bc device provides a Local Host/Distant Host interface to an IMP. It
     is normally used when participating in the DARPA Internet.  The con-
     troller itself is not accessible to users, but instead provides the hard-
     ware support to the IMP interface described in imp(4).  The configuration
     entry for the imp must also include the _\bp_\bs_\be_\bu_\bd_\bo_\b-_\bd_\be_\bv_\bi_\bc_\be as shown above.

D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
     a\bac\bcc\bc%\b%d\bd:\b: n\bno\bot\bt a\bal\bli\biv\bve\be.\b.  The initialization routine was entered even though the
     device did not autoconfigure.  This indicates a system problem.

     a\bac\bcc\bc%\b%d\bd:\b: c\bca\ban\bn'\b't\bt i\bin\bni\bit\bti\bia\bal\bli\biz\bze\be.\b.  Insufficient UNIBUS resources existed to ini-
     tialize the device.  This is likely to occur when the device is run on a
     buffered data path on an 11/750 and other network interfaces are also
     configured to use buffered data paths, or when it is configured to use
     buffered data paths on an 11/730 (which has none).

     a\bac\bcc\bc%\b%d\bd:\b: i\bim\bmp\bp d\bdo\boe\bes\bsn\bn'\b't\bt r\bre\bes\bsp\bpo\bon\bnd\bd,\b, i\bic\bcs\bsr\br=\b=%\b%b\bb.\b.  The driver attempted to initialize
     the device, but the IMP failed to respond after 500 tries.  Check the ca-
     bling.

     a\bac\bcc\bc%\b%d\bd:\b: s\bst\btr\bra\bay\by x\bxm\bmi\bit\bt i\bin\bnt\bte\ber\brr\bru\bup\bpt\bt,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.  An interrupt occurred when no out-
     put had previously been started.

     a\bac\bcc\bc%\b%d\bd:\b: o\bou\but\btp\bpu\but\bt e\ber\brr\bro\bor\br,\b, o\boc\bcs\bsr\br=\b=%\b%b\bb,\b, i\bic\bcs\bsr\br=\b=%\b%b\bb.\b.  The device indicated a problem
     sending data on output.

     a\bac\bcc\bc%\b%d\bd:\b: i\bin\bnp\bpu\but\bt e\ber\brr\bro\bor\br,\b, c\bcs\bsr\br=\b=%\b%b\bb.\b.  The device indicated a problem receiving da-
     ta on input.

     a\bac\bcc\bc%\b%d\bd:\b: b\bba\bad\bd l\ble\ben\bng\bgt\bth\bh=\b=%\b%d\bd.\b.  An input operation resulted in a data transfer of
     less than 0 or more than 1008 bytes of data into memory (according to the
     word count register).  This should never happen as the maximum size of a
     host-IMP message is 1008 bytes.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     netintro(4)

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     The a\bac\bcc\bc interface appeared in 4.2BSD.

4.2 Berkeley Distribution        June 5, 1993                                1