PMP Mail Archive: (no subject)

PMP Mail Archive: (no subject)

(no subject)

gsonger@tsoft.com
Wed, 5 Aug 1998 07:28:21 +0100

Message-ID: <35C7CE03.5C929D07@tsoft.com>
Date: Tue, 04 Aug 1998 20:14:11 -0700
From: Gail Songer <gsonger@tsoft.com>
X-Mailer: Mozilla 4.03 [en] (Win95; I)
MIME-Version: 1.0
To: pmp@pwg.org
Subject: Re: PMP> Re: COnfig Changes
References: <9808041423.AA08572@snorkel.eso.mc.xerox.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: pmp-owner@pwg.org

Hey!

As keeper of the FAQ I am more than happy to add these variables
and have a new version ready to go as soon I hear the word.

The only comment that I have is that this was not intended to be a
complete list but was to give a flavor of the things that could cause
a config change. Should this intent change? Do we want to state ALL
those things that an ideal implementation would count as config
changes? Should the list be an "only" list or an "at least" list?

Gail

Ira Mcdonald x10962 wrote:

> I agree with Harry and Jay that all of these MIB variables should
> be added to what constitutes a config change
>
> Cheers,
> - Ira McDonald (High North Inc)
>
> ------------------------------------------------------
> [Harry's note]
> From: Harry Lewis <harryl@us.ibm.com>
> To: <pmp@pwg.org>
> Subject: PMP> COnfig Changes
> Message-Id: <5030100024028591000002L012*@MHS>
> Date: Mon, 3 Aug 1998 09:58:39 PDT
> Mime-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> Sender: pmp-owner@pwg.org
> Status: R
>
> There is a FAQ (#7) - that explains what constitutes a config change.
> We have some questions...
>
> 1) The following variables weren't included:
>
> prtGeneralInputDefaultIndex
> prtGeneralOutputDefaultIndex
> prtGeneralMarkerDefaultIndex
> prtGeneralMediaPathDefaultIndex
>
> This seems inconsistent with other listed 'default' settings --
> prtChannelDefaultPageDescLangIndex, prtInterpreterDefaultOrientation,
> prtInterpreterDefaultCharSetIn, prtInterpreterDefaultCharSetOut.
>
> 2) These variables were also not included but could be considered chang=
> es
> to the configuration although they do not effect operations.
>
> prtGeneralCurrentLocalization
> prtConsoleLocalization
>
> Harry Lewis - IBM Printing Systems
> =