Date: Tue, 18 Mar 1997 21:45:13 -0500 (EST) From: "Mike A. Harris" Reply-To: "Mike A. Harris" To: Paul W Brannan cc: evand AT scn DOT org, OpenDOS Mailing List Subject: Re: [opendos] BAD Filesystems In-Reply-To: Message-ID: Organization: Total disorganization. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 14 Mar 1997, Paul W Brannan wrote: > > 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 . > And you can also get a list of all matching files. Well my "update" command was wrong. The command is "updatedb", but that was just a simple typo. The "updatedb, locate" commands work like what you say DM does. Unfortunately, I've got 2 executables called DM which I use allready, and an alias called DM which does something different alltogether. :o) Nothing another alias couldn't handle though. alias updatedb=dm /s alias locate=c:\whatever\dm.exe > > 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. No, since shared libs aren't in DOS yet, the best that could be done would be a utility which displays the executable types. Such as: DOS EXE's: 345 DOS COM's: 56 Win3.1 EXE's: 0 :o) And possibly a listing for which Windows DLL's are used. To do this there would need to be code to detect that an EXE loads a particular DLL. Since I know nothing about Windows programming, I don't know if it is even possible to detect this. The standard windows SYSTEM DLL's would need to be left alone, but other DLL's could be reported as being unused anyways. > > 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. Where can I get it for free? Sounds like pretty soon we will solve all of the Windows problems. And all from DOS! (Or even Linux :o) Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris Computer Consultant | Coming soon: dynamic-IP-freedom... My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html mailto:mharris AT blackwidow DOT saultc DOT on DOT ca Question: Does anyone know how to get talk to work in Linux?