From: bdc@world.std.com (Brian Chase)
Subject: DEC documentation preservation [RE: VS3100m76 ethernet problem (fwd)]
Date: Wed, 8 Mar 2000 15:40:19 -0800 [thread overview]
Message-ID: <Pine.SGI.4.04.10003081539590.22863-100000@world.std.com> (raw)
I saw the following on the linux-vax list. It seems to me it might be
worthwhile for us to get more info on the scope of the project, its terms,
and to see if we can collectively contribute to it. We'd all benefit from
having better access to old DEC documentation.
-brian.
---------- Forwarded message ----------
Date: Wed, 8 Mar 2000 16:33:44 -0500 (EST)
>From: quayle at infinet.com
Reply-To: linux-vax at mithra.physics.montana.edu
To: linux-vax at mithra.physics.montana.edu
Subject: RE: VS3100m76 ethernet problem
> > I took out the Owners manual that I forgot to send you, but it
> > states that 0000.0001 is normal, and if the last digit is anything
> > else it should/could still work normaly. Every error in the Error Code
> > table is 0000.x00y (for example: 0000.600C Loopback failed).
The Dallas/Fort Worth DECUS local users group is scanning all Digital
documentation, no matter how old. You might contact them
(denton at dsserv.com or wisniewski at dwlug.decus.org) to see if they'd like to
copy your manuals.
You get a free copy of everything they've scanned when they finish.
reply other threads:[~2000-03-08 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SGI.4.04.10003081539590.22863-100000@world.std.com \
--to=bdc@world.std.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).