Marty> In mibtree, I see:
Marty> prtConsoleDisplayBufferText.1.1 : 50:4F:57:45:52:53:41:56:45:20:4F:4E
Marty> which is pretty non-useful if you want to understand the
Marty> text...
Marty> ucd-snmp-3.6.1 snmpwalk shows:
Marty> prtConsoleDisplayBufferText.1.1 = "READY"
Scotty in general relies on the MIB definition. The Printer-MIB (I
guess this is what you are talking about) defines the SYNTAX of
prtConsoleDisplayBufferText as OCTET STRING (SIZE(0..255)). Hence,
scotty displays the value in hex since an OCTET STRING may carry
arbitrary binary data.
(This object will probably never carry binary data. Something like
DisplayString would probably a more appropriate data type.)
In scotty 2.1.X, the SNMP_Walk procedure in .../library/snmp.tcl is
called to do MIB walks. You can modify it do convert OCTET STRING
values into printable ASCII strings - but you will get strange results
on some other MIB objects that contain binary data.
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.