On Sunday, 09/30/2007 at 12:28 EDT, Adam Thornton <[EMAIL PROTECTED]> wrote: > On Sep 29, 2007, at 11:01 PM, Alan Altmark wrote: > > Yes, but are you sure that's what you want? > > I want a pony. Like so: > > CP QUERY PONY > HCP1337E No pony for you > Ready(666);
Quick! Call the stable! Something's wrong! That should be Ready(1337);-) > CP SET PRODID PONY530 STATE ENABLED > Ready; > > CP QUERY PONY > Yay! You have a pony! > Ready; That's the SET & QUERY PRODUCT commands. In this case, the PRODID is subject to change without notice and would not be a good indicator of the presence of ESM controls. SET PRODUCT provides the ability to gate startup of the server side of the equation, but you can enable the server and not include the CP mods. Technically, DIAG 0xA0 subcode 4 will only tell you if someone modified CP to respond "yes" instead of "no", but as a practical matter, that's not really an issue. When used together, and accepting the inherent risks, you *can* compare the intent (from QUERY PRODUCT) and the system's configuration (from DIAG 0xA0-4). > CP QUERY PONYLEVEL > Pony version 5 release 3, service level 0701 > Ready; No no. Bad pony! No hay for you. Tread lightly. No need for two commands where one will do. CP QUERY PONY Yay! You have pony version 5 release 3, service level 0701, you lucky dog. And I'm extremely reluctant to point it out, but QUERY PONYLEVEL would more properly give "PONY LEVEL 2". What you gave was QUERY PONYRELEASE. No need to repeat our mistakes. :-) Alan
