Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Seeking Some Books (Primarily Standards)
Date: Sun, 23 Jul 2023 21:20:37 +0000	[thread overview]
Message-ID: <CM0S1nsB3plYMCm_EThOVywHz__h5LV2mRjDs-9qs2vT-ZROCLbpUB5fgrImGRGs9zOPp0GId9MroguSRMxMjVQxq_vlaI3BYSl1wRkhVcs=@protonmail.com> (raw)

Good afternoon or whichever time of day you find yourself in.  I come to you today in my search for some non-UNIX materials for a change.  The following have been on my search list lately in no particular priority:

- Standards:
    COBOL 68
    C 89
    C++ 98
    Minimal BASIC 78
    Full BASIC 87
    SQL (any rev)
    IS0 9660 (CD FS, any rev)
    ISO 5807 (Flow Charts, any rev)

- Manuals:
    PDP-11/20 Processor Handbook
        (EAE manual too if it's separate)
    WE32000 and family literature
    GE/Honeywell mainframe and G(E)COS documents
    The IBM 704 FORTRAN Manual (The -original- FORTRAN book)
    The Codasyl COBOL Report (The -original- COBOL book)
    Any Interdata 7 or 8/32 documentation (or other Interdata stuff really)
    The Ti TMS9918 manual
    The Philips "Red Book" CDDA standard
    If it's part of one, the Bell System Practices Issue containing, or separately otherwise, BSP 502-503-101 (2500 and 2554 reference) 

If any of these are burning a hole in your bookshelf and you'd like to sell them off, just let me know, I'll take em off your hands and make it worth your while.  I'm not hurting for any of them, but rather, I see an opportunity to get things on my shelf that may facilitate expansion of some of my existing projects in new directions in the coming years.

Also, I'm in full understanding of the rarity of some of these materials and would like to stress my interest in quality reference material.  Of course, that's not to dismiss legitimate valuation, rather, simply to inform that I intend to turn no profit from these materials, and wherever they wind up after their (hopefully very long) tenure in my library will likely have happened via donation.

- Matt G.

P.S. On that last note, does anyone know if a CHM registration of an artifact[1] means they truly have a physical object in a physical archive somewhere?  That's one of the sorts of things I intend to look into in however many decades fate gives me til I need to start thinking about it.

[1] - https://www.computerhistory.org/collections/catalog/102721523

             reply	other threads:[~2023-07-23 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 21:20 segaloco via COFF [this message]
2023-07-24  1:10 ` [COFF] " Stuff Received

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='CM0S1nsB3plYMCm_EThOVywHz__h5LV2mRjDs-9qs2vT-ZROCLbpUB5fgrImGRGs9zOPp0GId9MroguSRMxMjVQxq_vlaI3BYSl1wRkhVcs=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.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).