earle@jplopto.UUCP (09/18/87)
Some users where I consult have need for a/the VT100Tool. So I pulled it
off of uunet. Lo and behold, well gosh darn it Vern, lookie here. The damn
thing sucks in one of the window libraries (/usr/lib/libsuntool.a), and rips
out some of the object modules inside, and replaces them with its own.
Needless to say, this makes VT100Tool horribly SunOS release dependant; if
libsuntool.a changes in some way, there stands the possibility that this
will no longer work. Alas, such is the case; `vt100tool' will no longer
load due to incompatibilities with the newer (SunOS 3.4) libsuntool.a - it
generates unresolved references at `ld' time. So, the questions are:
(1) Ed Lafferty (ell@mitre-bedford.ARPA), are you out there? Wot's the deal?
(2) If indeed the problem is unresolvable, is this an acceptable substitute -
running a shelltool with -Wh 24 -Ww 80, and running the `screen' program
as the argument to the shelltool (with `<< VT100Tool >>' as the label)?
`screen' purports to have VT100 emulation with ANSI 3.64 extensions, and
indeed seems to do so (haven't built `vttest' yet to see), but I notice
the termcap entries for `screen' and `vt100' are quite different. (Oliver
Laumann, are you there?) Since I've never seen the original `vt100tool'
in action, I don't know what this substitute is missing (other than the
obvious fact it doesn't handle alternate graphics character sets); to
offset any defficiencies you get the multiplexed tty sessions inside the
quasi-vt100tool ...
Greg Earle earle@jplopto.JPL.NASA.GOV
Sun Consultant earle%jplopto@jpl-elroy.ARPA [aka:]
Rockwell International earle%jplopto@elroy.JPL.NASA.GOV
Seal Beach, CA ...!cit-vax!elroy!smeagol!jplopto!earle