[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::hackers_v1

Title:-={ H A C K E R S }=-
Notice:Write locked - see NOTED::HACKERS
Moderator:DIEHRD::MORRIS
Created:Thu Feb 20 1986
Last Modified:Mon Aug 03 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:680
Total number of notes:5456

285.0. "What's on my system???" by 58430::HOWARD (armed and presumed dangerous...) Tue Aug 12 1986 02:27

    I work on numerous customer machines. As part of this work I often
    find it necessary to determine exactly what software (type and version)
    is running on a particular machine. What I would like to develop
    is a program/procedure which can identify the types and versions
    of various Digital products running on a VAX.
    I have played with the SHCOMMA utility fom the toolshed and it has
    alot of potential here. Unfortunately it doesn't exactly go out
    and identify the products on a system. What I am looking for is
    ideas of things to look for in identifying various products. A list
    of what I have thought of to date follows:
    
    	1) - DCL commands from the DCL tables
    	Question: are there any products which would not have some
    identifying signature in the DCL tables
    
    	2) - help libraries in sys$help
    
    	3) - executables in sys$system
    
    To be more specific, I have a list of products which I want ot be
    able to identify. If this would be of help I'll post it here (it's
    a list of about 30 of our most common products). Comments would
    be appreciated.
    
    						Til next time,
    						Robin.
T.RTitleUserPersonal
Name
DateLines
285.1CLT::GILBERTeager like a childTue Aug 12 1986 03:3914
I'd go after the EXEs in SYS$SYSTEM, for several reasons.

To get the version numbers, you have to read the EXEs, anyway.
SHCOMMA is 'forinternaluseonly'.
While most Digital products get DCL verbs, most OEM products do not.

The approach I'd take is to get a directory of .EXEs in SYS$SYSTEM
(oh, what the heck -- get those in SYS$SHARE, too), parse the contents
of SYS$UPDATE:VMSKITBLD.DAT, and see which files aren't listed there.
For these non-VMS .EXEs, read the first block, and display the version.

Also, take a look at the callable Sort/Merge documentation, in particular
the equal-key callback routine.  This should be useful for 'throwing away'
those files that also appear in VMSKITBLD.
285.2ANALYZE/IMAGEFROST::HARRIMANyou want it when?Tue Aug 12 1986 12:414
    Ever heard of ANALYZE/IMAGE? That will even give the first block
    in an almost human-readable format, including the dates...
    
    
285.3Not all show up in SYS$SYSTEMAKOV68::NORRISWhat is it, Miss Pfeffernuss?Tue Aug 12 1986 12:489
    I'd also look at the top level of SYS$SYSROOT and SYS$SYSDEVICE.
    Some products build their own directories; WPS-PLUS/VMS, ALL-IN-1,
    LSE, etc.
    
    It's also possible to build these products on a different disk,
    so there's a lot of places you could look.
    
    Ed
285.4Try VERSIONSNANDI::LAMIACheap, fast, good -- pick twoTue Aug 12 1986 13:325
    Also see the VERSIONS tool from the toolshed.
    
    Press Select to add the Toolshed Notes catalog to you notebook now.
    
    Walt