John Fitzsimons <
[email protected]> wrote:
Here is an idea. Do something that nobody else has been able to do
(despite claims to the contrary in this newsgroup). Make a program
that can list all the .exe files one has on a computer. EXCLUDING
the .exe files that are simply compressed files.
This is NOT simply a list of (registry) "installed programs". An
application can run without making entries in the registry.
I think the little app I made is ready.
1) As Sieste said, grab the newest version of SH Archive Identifier,
aka: SHAID:
It looks like the latest version is 2.70, released on 29 July 2000.
Downloadable from the author's site:
Unzip it.
2) Grab my .exe. It is an executable file. Place it in the same
directory where SHAID was unzipped. All it needs to run properly is
SHAID's "archid.exe" - make sure that my "ID.exe" is in the same
place. These two files can be placed in a subdir alone to ease
congestion, or, just drop it in the SHAID subdir. No matter.
http://www.woundedmoon.org/SHAID/ID.exe 55,296 bytes.
3) Execute "ID.exe" - it uses SHAID to make the reports.
After executing, look In the same location for:
SFX.TXT - list of all .exe files identified as sfx.
PROGRAM.TXT - list of all .exe files not identified as sfx.
ERROR.TXT - list of errors, with line numbers for files found in:
TEMP.TXT - the complete list of .exe files on the drive.
Most errors that I've had in XP are paths that are too long for SHAID,
even after using short paths. The programs that I have installed on XP
have a bunch of overly long path and filenames.
I also found a couple of directories that have names that SHAID will
not accept:
C:\Downloads\BV\
www.blackviper.com\pub\mozilla.org\firefox\releases\1.0.6\win32\en-US\Firefox
Setup 1.0.6.exe ---- exit errorlevel = 253 (
www.blackviper.com is in
the directory name)
I screwed up when making this directory, naming it: \ANv10068.exe\
C:\Archive\AtlantisNova\ANv10068.exe\
The SHAID docs contain the return values that are displayed.
The display shows the SHAI output and a countdown. It's better than
staring at a blank screen, but it does make the program run slowly.
It's interesting to see the different compressions used. Hit Pause on
the keyboard to better read the screen.
After it's fully debugged, I'll remove the excess display, and the
program will run quite a bit faster... There is no documentation yet
either. After getting some feedback, debugging, etc. I'll fix it up
right!
The current version is hard coded for C:
I'll add other partitions if there is any interest.