From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8176 invoked from network); 18 Aug 2020 14:12:30 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 18 Aug 2020 14:12:30 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id C146D9CAC1; Wed, 19 Aug 2020 00:12:29 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A4CFB9CAAD; Wed, 19 Aug 2020 00:12:00 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=ccil-org.20150623.gappssmtp.com header.i=@ccil-org.20150623.gappssmtp.com header.b="Hvu6pbrP"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 911B19CAAD; Wed, 19 Aug 2020 00:11:58 +1000 (AEST) Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) by minnie.tuhs.org (Postfix) with ESMTPS id C0FFA9C8BB for ; Wed, 19 Aug 2020 00:11:57 +1000 (AEST) Received: by mail-qk1-f175.google.com with SMTP id n129so18324054qkd.6 for ; Tue, 18 Aug 2020 07:11:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QkgqZ6KJ6P6L7Y+0FatUPOduB2SrdfBqonJO7VxrVc4=; b=Hvu6pbrPJs3jYdwcjssNFsujQupBEUp0+WnB6nFAH7Rl+GBvCO3zwbt1Yl/LfpAwkR UV0tKZmvxS2yfewdK/DeeeBiAi1gAnfX0H9O+8IRfZKra7MCmOiT59KQgt7iSUowzXIK y4FAWRsidHAO+nfn+1Y1HpO7+AmqBxmNqSOodMyBvBLkWn6CRidLRo0sFSnc6ukWtlXG cQUtQMbN6a6lE7zEaWKJmzunsrnwRnYqk0fWyCvQ/3cs4qeiTxOfBPBIVzxNTcioBnbe bNtr80f8CishX7KzoaUeeRnMKgDH98KjtjhdB/NKFzYEt7Cr+ugKqgHkCVxE3mLbeHOe uyiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QkgqZ6KJ6P6L7Y+0FatUPOduB2SrdfBqonJO7VxrVc4=; b=pRcTEmIT+y5FXnVYiJ5aCfIrkcoOGZ3EutRODTZaBvsR/Frnr6CXDP/arZi2e3WtDS BCnulkU6k37HW6IhL+a8Uz+HZGsMuQUhT5eI5aeIzy/ARV0EYcVMJts5F8mFtPqcchQt hlDEpDW2HN6E5wbFoXfpRrcRwLlVaDihkXhrKWBopRtsTrn/2pvT9HIX9kVVa5yJ7CmB SDVPwHMTBUkeqrJQF1rcZHL9l3jzVrjdaOlSM09KMwHnGAFNIsuYP/vMU47c/fg2oAz/ bDA0Q76WhRRIDWR593cnQ3hR7cCCfjmVqdF7oIzxgNqxQ7CnMBkdwNwJjdjiSMm5ZSPC V80Q== X-Gm-Message-State: AOAM5319dpH6OzMIr7wsZxxbNOf/LufqhxJwUn7nBc2uUI1dgXbA3tgu 40ah5aX4Yt5NDteR7oH348kCZukolQXjOPCBN/PEAQ== X-Google-Smtp-Source: ABdhPJw+YO2Qsq71181ZI+P8O7oqrh0JVb1ESB4/yIsMIynBG/vwboZKO8zIUsf5JTKA29WYC9lhq3lFbGzLP4OgBdQ= X-Received: by 2002:a05:620a:110d:: with SMTP id o13mr17502675qkk.60.1597759916775; Tue, 18 Aug 2020 07:11:56 -0700 (PDT) MIME-Version: 1.0 References: <202007200847.06K8l8DF026646@freefriends.org> <20200720094648.GE15253@ancienthardware.org> <20200801013605.GG10778@mcvoy.com> <20200818135716.GA93457@clarinet.employees.org> In-Reply-To: <20200818135716.GA93457@clarinet.employees.org> From: John Cowan Date: Tue, 18 Aug 2020 10:11:45 -0400 Message-ID: To: Derek Fawcus Content-Type: multipart/alternative; boundary="00000000000046b63c05ad277884" Subject: Re: [TUHS] A/UX [was Linux is on-topic] X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000046b63c05ad277884 Content-Type: text/plain; charset="UTF-8" No, that definitely wasn't it: this is of the "numeric code plus text string" type, although it's interesting because it has multiple-length text strings to trade off verbosity/helpfulness. It kind of reminds me of what you get in ADVENT when you move to a place you have been before. You get only a brief description, but if you type DESCRIBE you get the full monty. That must have saved a lot of LA34/36 paper. :-) On Tue, Aug 18, 2020 at 10:07 AM Derek Fawcus < dfawcus+lists-tuhs@employees.org> wrote: > On Thu, Aug 13, 2020 at 04:04:22PM -0400, John Cowan wrote: > > But this reminded me: Does anyone remember a system of any sort where > there > > were *two* corresponding sets of alphanumeric error codes, one short and > > meaningless like F32 and the other somewhat meaningful like POWER_LOW? I > > made up this example, but I have a feeling I saw or read about such > > a system. I can't pin it down with Dr. Google. > > Something early from Digital Research? > > Not quite what you describe, but a late DR OS had the following scheme. > > > http://bitsavers.org/pdf/digitalResearch/flexos/1073-2003_FlexOS_Users_Guide_V1.3_Nov86.pdf > > page 4, and 128 onwards: > > The help level can have a value between 1 and 4. Your computer > manufacturer sets a default help level which you can override with DEFINE. > > 1 Displays the FlexOS function, the error source module, and the > return code. > 2 Identifies the command and type of error in one sentence. > An example of a level 2 error message is "COPY: Write error." > 3 Expands on the level 2 message and includes more specific > information. > An example of a level 3 message is "COPY: An error occurred writing > report.txt on a:". > 4 Expands on the level 3 message and often suggests a possible > solution to the error. > An example of a level 4 message is "COPY: An error occurred writing > report.txt on a: The disk a: is full. You can erase unnecessary files to > free up space." > > Where for scheme 1 it gave something like: > > Error Code = 80137712 > System Source Module = Pipe System > Function Returning the Error = write_data > Error Argument (long in HEX) = 123456 > Error Argument (character string) = string > > With only one of the last two lines printed, depending upon the function > in question. > > DF > --00000000000046b63c05ad277884 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No, that definitely wasn't it: this is of the "nu= meric code plus text string" type, although it's interesting becau= se it has multiple-length text strings to trade off verbosity/helpfulness.= =C2=A0 It kind of reminds me of what you get in ADVENT when you move to a p= lace you have been before.=C2=A0 You get only a brief description, but if y= ou=C2=A0type DESCRIBE you get the full monty.=C2=A0 That must have saved a = lot of LA34/36 paper.=C2=A0 :-)


On Tue, Aug 18, 2020 at 10:07= AM Derek Fawcus <= dfawcus+lists-tuhs@employees.org> wrote:
On Thu, Aug 13, 2020 at 04:04:22PM -0400, = John Cowan wrote:
> But this reminded me: Does anyone remember a system of any sort where = there
> were *two* corresponding sets of alphanumeric error codes, one short a= nd
> meaningless like F32 and the other somewhat meaningful like POWER_LOW?= =C2=A0 I
> made up this example, but I have a feeling I saw or read about such > a system.=C2=A0 I can't pin it down with Dr. Google.

Something early from Digital Research?

Not quite what you describe, but a late DR OS had the following scheme.

=C2=A0 ht= tp://bitsavers.org/pdf/digitalResearch/flexos/1073-2003_FlexOS_Users_Guide_= V1.3_Nov86.pdf

page 4, and 128 onwards:

=C2=A0 =C2=A0 The help level can have a value between 1 and 4. Your compute= r manufacturer sets a default help level which you can override with DEFINE= .

=C2=A0 =C2=A0 1 Displays the FlexOS function, the error source module, and = the return code.
=C2=A0 =C2=A0 2 Identifies the command and type of error in one sentence. =C2=A0 =C2=A0 =C2=A0 An example of a level 2 error message is "COPY: W= rite error."
=C2=A0 =C2=A0 3 Expands on the level 2 message and includes more specific i= nformation.
=C2=A0 =C2=A0 =C2=A0 An example of a level 3 message is "COPY: An erro= r occurred writing report.txt on a:".
=C2=A0 =C2=A0 4 Expands on the level 3 message and often suggests a possibl= e solution to the error.
=C2=A0 =C2=A0 =C2=A0 An example of a level 4 message is "COPY: An erro= r occurred writing report.txt on a: The disk a: is full. You can erase unne= cessary files to free up space."

Where for scheme 1 it gave something like:

=C2=A0 =C2=A0 Error Code =3D 80137712
=C2=A0 =C2=A0 System Source Module=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =3D Pipe System
=C2=A0 =C2=A0 Function Returning the Error=C2=A0 =C2=A0 =C2=A0 =3D write_da= ta
=C2=A0 =C2=A0 Error Argument (long in HEX)=C2=A0 =C2=A0 =C2=A0 =3D 123456 =C2=A0 =C2=A0 Error Argument (character string) =3D string

With only one of the last two lines printed, depending upon the function in= question.

DF
--00000000000046b63c05ad277884--