Date: Fri, 14 Mar 1997 17:45:13 -0500 (EST)
From: Paul W Brannan <brannanp AT musc DOT edu>
To: "Mike A. Harris" <mharris AT blackwidow DOT saultc DOT on DOT ca>
cc: evand AT scn DOT org, OpenDOS Mailing List <opendos AT mail DOT tacoma DOT net>
Subject: Re: [opendos] BAD Filesystems
In-Reply-To: <Pine.LNX.3.95.970313020958.955C-100000@capslock.com>
Message-ID: <Pine.ULT.3.95.970314173853.22450A-100000@atrium.musc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

> file - tells you what type a given file is. ie: JPEG, WAV,
>        executable, shared library, AVI movie, C source file,
>        etc... 

I think I found a program like this on simtel (?) that does this.  Or
maybe I got it off a local BBS.  I thought it was a great idea, but I can
usually do that by myself by just looking at the file.

> update - A utility that you run every now and then (twice a week 
>          on my system) which updates a database of every single
>          file on your entire hard disk, and all mounted disks.
>          This database is used by the locate command.  Any time a
>          new package is installed somewhere, update should be run
>          manually.  

Don't know of one of these for DOS.

> locate - A filefind program that works IMMEDIATELY!!!!!!  Since
>          uses the lightening fast database created by update, it
>          doesn't need to scan your whole hard drive looking for
>          files.  

I found one of this too, I think on SimTel.  It's called DM.  You type DM
/s to update the database, and then you can find a file with dm <file>.
And you can also get a list of all matching files.

> binstat - a bash script that scans all of the directories in your
>           path looking for executable files of any type, as well
>           as shared libraries.  It gives a statistics report
>           telling you how many executables you have, what type
>           they are, what libraries are ACTUALLY USED by a
>           currently installed program.

I don't think one of these for DOS is necessary.
At least not yet.

> A port of binstat to DOS would allow you to find out what windows
> DLL's are NOT being used by any existing installed software for
> example.  Then you could delete them, or automate such a task.

Get FDDLL from Ziff publications.  It's a freeware utility that was
featured in PC Magazine a while back.  Works pretty well, too.

Paul