Installed Files Checker 4.5
(by Fredledingue)
Homepage - more infos
Direct download
Alternative website

Quickely compare files in the "Windows" folder, the "Program Files" folder, the root of "Drive C" and also in folders of your choice (and their subfolders) to help you to track changes in your system.

What's new?

4.3
-Optimized: For Windows Script Host 5.1 and possibly below for work on non-updated w98.
ATTENTION: WSH 5.6 still strongly recommanded (faster).
-Added: Personal comment on the reportss
-Added: Indexing in a Html page the repport file names and the comments for easier re-viewing
-Fixed: Configuration interface not lauunching the application
-Improved: Other minor details

4.4
-Improved: Use of registry for communication among separate scripts (should avoid "file already exists" errors)
-Added: WSH version detection (click "About")
-Fixed: Comment field disapearing after "Closing Help"


4.5
-Improved: Configuration panel now reads old settings if any.
-Improved: Use of registry (finished) and other minor things in the code.
-Fixed: Configuration panel showing an "Ok" dialog box instead of "Yes No".
-Fixed: Configuration panel not showing the Program Files folder

UPDATE NOTE

After updating from 4.0 to upper versions, the first scan after the update may contain a lot of false results.

"We can do it fast... or we can do it realy fast!"

See also:
The W98 System Restore (or Back Up) Script Project

I am using this usually : http://www.xs4all.nl/~hneel/software/syslog.zip

Now I've tried yours and the batch file fails to do anything.

The batch has C:\WINDOWS for Windows directory.
Must not be hard-coded because not everybody has Win9x in C:\Windows [I don't].
The proper syntax is:

%windir%

if you plan to use the batch from within Windows UI, or:

%winbootdir%

if you plan to use the batch from native/true/pure MS-DOS mode [outside Windows UI].

The batch also uses C:\PROGRA~1 for "C:\Program Files" [commented out/remarked in your batch] = same here, must not be hard-coded, not everybody has that exact directory location. For example I have C:\PROGRAMS .
Proper syntax would be to use an INF file [example]:which can be called from within the batch [example]:

START /W RUNDLL32 %windir%\SYSTEM\ADVPACK.DLL,LaunchINFSection WHATEVER.INF,DefaultInstall

The batch also has "set list=C:\MYDOCU~1\WHSCRIPT\CHECKS~1\WINF_B.TXT".
I don't have that directory, and I bet others don't either.
Proper syntax would be for example to use the %temp% variable instead:

set list=%temp%\WINF_B.TXT

Same goes for "set list=C:\MYDOCU~1\WHSCRIPT\CHECKS~1\FLIST1B.TXT" [commented out/remarked in your batch].

HTH

Ha, you'r right.

I re-edited the batch file and it should work now. (download here)

I replaced "C:\WINDOWS" with "%windir%".
(I don't plan to run the batch from outside windows)

Also replaced "set list=C:\MYDOCU~1\WHSCRIPT\CHECKS~1\WINF_B.TXT"
with simply "set list=WINF_B.TXT"
(The full path is not needed, I think, because the bat and the vbs work inside the same directory)



I'm never learned inf coding... There is no equivalent of %windir% for the Program File folder?
Anyway I think I could find workarounds such as asking the user where is the program file the first time he uses the program.
Even better: asking the user all the other folders he wants to scan.
...
For the time being we will stick with the windir.

I noticed that the list created by the batch file is not the same in XP as that in w98 so bear in mind that's for for w98 (and OS with similar DOC handling) only.
But it shouldn't be difficult to make an XP version in the nearest future.

Thanks for your comments and help.

Your script is very handy 1 thing though can you write a code so we don't have to use the bat.file
Other than that the tool is really useful.

Nice to read that's working!



What do mean? About closing the window? There should be a trick to do that automaticaly on exit, but for some reason it doesn't work.
I could try a pure VBS solution to browse through the entire directory and subdirectories but I doubt very much it will be as fat as DOS. There is no such a thing as "dir /s" in VBS. that' very stupid.
I'll see.

Now I will work on a script for checking the program files and other folders of your choice, beside the windows folder.

Your batch works ok now.

There is not equivalent for batch files [DOS mode] for "C:\Program Files" set %variable% location in 9x OSes.
Only NTx OSes have that feature.
The only way is to write an INF or REG file which can be called from within a batch.
REG file also works, but the INF method is more elegant and more flexible.

You should consider adding DOS/Windows mode detection if you plan to use this only for Windows 9x UI mode.
Examples:

-------snip-------
IF "%OS%"=="Windows_NT" GOTO END

IF "%windir%"=="" GOTO END

IF "%winbootdir%"=="" GOTO END

MEM /C | FIND /I "vmm32">NUL
IF ERRORLEVEL 1 GOTO END

whatever...

:END
CLS
EXIT
-------snip-------

Replace the "exit" line at the end of your batch with:

CLS
EXIT

Make sure there is no space or blank/invisible characters/tabs after CLS or EXIT [the way it is now].
That should close the batch automatically upon completion.
FYI:
The CLS + EXIT method works only if the batch starts with:
@ECHO OFF
as 1st line.

And you can remove these lines after you add the CLS + EXIT lines:

echo -------------------------------------
echo PLEASE CLOSE THIS WINDOW TO CONTINUE.
echo -------------------------------------

HTH

BTW:
I noticed on the PC I already tried your tool on [1.4 GHz P3 + 512 MB RAM] that it is very slow to create the list.
Is there a way to streamline/optimize/tweak the VBS file to make it faster?
Or have you considered using a batch to do this instead?
Thanks.

MDGx,
Thanks for the codes, I will try them.



If by "your tool" you mean my system files checker (other tools on my sites are indeed slow sometimes): the VBS file does NOT make the list of the files in the windows directory. That's the role of the batch file.
But this batch file is launched via the VBS script so you should NEVER use the batch file yourself!

The VBS is only comparing the previous list with the new one. Normaly the comparison process should take a few seconds, maybe up to ten seconds if you made MASSIVE changes in your system before. And I don't think you will ever wait that long...unless there is an error in the vb script. --->

Please check if the result given by the script is consistant with the reality.
In case of programing error on my part, the list of changes may be much longer than it should.

I of course ran many tests myself but ther might be some cases I didn't think of.

You can also e-mail me WINF_A and B and I will run the test myself.

I will post a debug version if needed.

Now if it's the DOS prompt window that stays abnormaly long without responding, it's a DOS issue not VBS.
VBS doesn't interfere in this process.
On my 1.8hz PC it takes 10 or 15 second to do the WINF_A list.
Or you have a very slow and very fragmented HD... coming from you that would be surprising.

So I need to know if it's slow during the DOS promt or after you closed it.

Please give as many details as possible on what happends.
Thanks.

No. But there is one in VBS.
As soon as I have time I will impement it.

Yes, I was talking about your list_files_in_text.bat file, part of your SFC script:
http://www.geocities.com/fredledingo/check_system.zip

The long delay was happening no matter which file [VBS or BAT] I was running.
But I found why your batch was taking so long to create the files list [actually it got stuck at the 1st screen], because I have this line in my autoexec.bat:

SET DIRCMD=/A/O:GEN/P/V

which prompts the user to press a key to display the next screen. Otherwise the DIR command waits for input without moving on.
This SET variable adds the /P switch anytime a DIR command is run, even from within batch files.
So in your batch you need to add the /-P switch [allows moving on to next screen without any user input] on all DIR lines to prevent this from happening [example]:

dir %windir% /O:GN /S /-P >> %list%
dir %windir% /O:GN /A:S /S /-P >> %list%
dir %windir% /O:GN /A:H /S /-P >> %list%

This way the entire script took only a split second on my PC.
But I also added a CLS line b4 the EXIT line at the end, so the batch can close automatically.

Good job, your script works now.

HTH

P.S.:
I know there is a way to place set variables in VB scripts, but I don't have any experience with VB, so I don't know the code.

The new, first full version, is out!

History:

0.6
-Uncomplete test release

0.7
-First complete release
-Renamed to "Installed Files Checker" to avoid confusion with "System File Checker".
-Scan the root of drive C, the Windows folder, the Program Files folder and also folders of your choice.
-Added ifc_config.vbs
-Improved interface and other bug fixes

Test this version in an empty folder if you already tested checksystem6.

MDGx



Yeah, I knew that you geeks always have something special in your PC...

I still didn't add the /-P thing in the bat file but it's a matter of day. It's because the PC I'm doind scripts on is not going properly on the internet and I forgot what to add exactely.
If you are not afraid you can add the code yourself in ifc_config.vbs or in the bat file after running checksystem7.

You will notice that there is no batch file in the distro: it's created by ifc_config.vbs

I was wrong: there is no way to find out the program files folder in VBS: The folder this idi0t refers to is the Start/Program (shortcuts) folder.
So I build some workaroud instead.

Anyway the only file you have to doubleclick on is checksystem9.vbs.

Have fun!

The Program Files location is stored in the registry as "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProgramFilesDir"
You just need a way to import its value into a VBS usable variable

I have tried your newest version:
http://www.geocities.com/fredledingo/Insta...les_Checker.zip

When I run checksystem7.vbs it just exits without doing anything.

When I run the other VBS file [ifc_config.vbs], it creates the IFC.BAT file and then exits.

I had to add /-P to all DIR lines to make IFC.BAT work.
I also had to add CLS + EXIT lines at the end to force it to close automatically.
This is the modified IFC.BAT that works properly on my computer:

Please note that my "C:\Program Files" folder is actually called "C:\PROGRAMS" [another geek tweak ].

HTH

RainyShadow,

Thanks for this info.
The next version will read it in the reg. No problem.

MDGx
I told you that "/-p" was still not implemented in the version 0.7.
Now it is (as a silent update). If you download the zip file again, it should work.

That's not possible: It should either pop up a message box written by me (in this case tell me what it reads before it exits without-doing-anything) or an error (then tell me the line where the error is).
Remember to use any new version in a new empty folder.


That's normal.


Check the bat file: It should be that UNLESS you have also another folder called "C:\Program Files". In this case you should normaly see that he detected it and you can act accordingly.

...and

cls
exit

should be found (in lowercase) at the end of the batch file.

I have just downloaded your IFC package again [as instructed]:
http://www.geocities.com/fredledingo/Insta...les_Checker.zip

Now when I run checksystem7.vbs it does properly display the messages, prompts to start the program and creates IFC.BAT, then exits [see error message below].
TXT file(s) not created.

If I run IFC.BAT by itself, the text file [WINF_B.TXT] is properly created.
I have to manually exit the batch though, still no CLS + EXIT lines at the end.

When I run ifc_config.vbs , I get this error message:

Click to view attachment

I'm using current WSH version:
http://www.mdgx.com/add.htm#MSE

BTW:
I always test new apps/tools/whatever in an empty/dedicated folder. [I'm a geek, remember? ]

HTH

MDGx,
That's very strange. I can't reproduce the error but I see what it is.

If you got there it means that when asked "Do you want to scan more folders with Installed Files Checker?", you clicked "yes".
Then, normaly a little folder browser dialog opens reading: "Select the folder that you want to add.".
Did you see this?
If yes, then at this moment, you selected something that is not a folder.
If not it's a problem in your computer. Probably in the dll where this dialog is. I don't think it's WSH (I have the same WSH version as yours. (5.6)) because other softwares use that too. Maybe this dialog is different in windows ME (as you ran W98toME)???...

After the error, the script exits without finishing to write the batch file.

I uploaded version 0.8 to counter this problem. (same link as above). PLease try it.

I found out what was wrong:
WSCRIPT.EXE had a 3 seconds timeout [have no idea where that came from] after which the script was automatically closed.
I have disabled the timeout/close setting, and now it works 100%.

These are the registry key + values after I corrected the timeout:And this is what I had originally:
Thanks again for your cool tool.
Excellent job.

It does not work here. I did a first scan and then deleted a 2000 files subfolder in the application data folder and reran the toll and it gave me an error message, couldn't handle it.

Eidenk,

You deleted a folder with 2000 files in it? Right?

Do you remember what the error was saying? "Out of range" or "Out of file" something like that?

I will see if I can reproduce the error.
It's a very difficult script.

Stupidely I clicked on the error message too fast.

Eidenk

Never mind.

I ran my program yesterday and stumble across an error too.
Thought I knew this error could happend, it didn't when we tested on the Windows Directory alone.

One minute ago, I uploaded the version 0.9 that fixed the error I got (I hope it was the same error for you).

download here

Do you remember if there was a red circle with a white cross symbol in the message box? No? You realy don't remember that?

________________

MDGx,

Keep on trying my scripts: One day will be debug your whole computer!

No sorry I don't remember that either. I'll try again and if there is an error I will write it down next time.

It seems it is doing allright now.

BTW : Very usefull aviutil page you have on your site.

I have tried the current version of your script [0.9 beta].

Works ok, except 1 small annoyance:
Is it possible to add code to your vbs scripts to keep the dialog prompts [yes/no/ok/cancel/exit/etc] on top of all other open windows [in the foreground]?
When I run your checksystem9.vbs files from within File Manager (FM) or from within Windows Explorer (WI), one of the prompt dialogs hides behind the front window, and the entire script fails to create the list TXT file because of this.
That dialog prompt becomes visible again only after I minimize or exit FM or WI, but by that time I already closed the scripts, unaware of that hidden dialog.

This never happened before with any of your older versions.

HTH

P.S.:
Tweaking and debugging is my business...
... except for VBS, which I have no experience with.

MDGx

Unfortunately there is no way to tweak that in VBS (that would require installing eventualy autoit3x.dll etc).



I don't understand. as long as the dialog is there, this script will be waiting for somebody to click on a button and it can wait forever. So you can't materialy "close the script" unless you killed the "wscript" task on the tak manager. And even doing so, will have the same effect as pushing on a button in the dialog if there is one visible and then after that you will see either the next dialog or nothing at all.

(FYI.
You can kill a VBS running only if it doesn't respond. If in a script there is a loop that pop up a dialog all the time without being able to stop it, killing the task won't kill the task! Or it will sometimes do it after 2 or 3 minutes. That's a bug from the task manager. That's why some geek put a WSH timeout in their registry. )

One possibility is that timeout of yours is back in your registry.

Another is that you ran the script twice.

Another is that due to a bug in my script or a file being not there, the config script is launched. I can't say what it is now.

Again, I need more information about what the dialog are saying and when they appeared.
Posting a snapshot was perfect but the text only is already very useful.

For the moment I can only suggest to run it from a shortcut, all windows minimized...

If things goes well I will remove the beta-warning dialog, and maybe another one too in the next release. That will be less annoying.

Maybe a totaly silent version that can run from the startup menu with the bat part included in autoexec.bat. So that you will have everytime you start your computer a report before windows is running. But that's just ideas.

HTH

Hi,

instead of running the DIR command three times for each desired folder,
why not run it only once, using for example 'dir C:\ /O:GN /A /-P'?

And, BTW, why are you using a batch file at all? You can process
directories (and their subdirectories) with VBS very well.

And, BTW2, why don't you use SFC?

Regards
Andreas

Does it list all the files including the system and the hidden files?
Note that I'm not a DOS specialist.

Yes but a batch file is much faster. I didn't make comparison tests but I feel it's faster.
While in DOS you just have to add /S to get all the sub and sub-sub folders it takes 20 lines of code in VBS to get the same effect.


Can you track files changes in SFC? AFAIK it's basicaly checking the file system for errors.
The advantage of VBS is that you can easily modify the source for your own need.

SFC does NOT check the file system for errors, Scandisk does this.
Actually SFC can do pretty much the same as your script, except that it can easily restore changed/deleted files. And yes, it tracks file changes, new files, deleted files. For changed files it displays a comparison between the old and new file, including file size, date and version. Also it can be used for folders different than the windows one, simply by creating a new profile and specifying what kind of changes to track.
Simply, SFC can do the same job as your script (and more). Maybe that's why i still haven't tried it yet

SFC is not very good really. Mostly because of it's speed. You can't run it frequently ( after each time you install something) for quick checking of eventual file changes or you spend your entire computing time with it.

And if you run it only when you have a problem after you have used your computer without probs for a long time, you'll get lost in all it will find that has changed since last time you did run it.

IMO.

Yes, sorry I mixed up.
Anyway, SFC is a basic tool to repair/restore files that have changed. Thus it tracks indeed file changes. But it will give only a fraction of the informations that Installed File Checker will give you.

And as Eidenk suggested, the advantage of my script is speed and flexibility.
For example, SFC has been totaly useless in regard to the internet problem I have at the moment... but it was cool to read that 0 files were changed...and that 800 were added!
No. We realy need something for daily use.

These are two different tools for different needs. One tracks and eventualy restores crucial files, the other gives you everything that changed since last time.

TBS, with an extensive and tedious combination of settings, SFC can be improved.
More interresting is running SFC to eventualy restore some files, after running Installed File Checker.

Note that everytime I install a piece of software I use Total Uninstal (not freeware anymore ) that also "do the same job as my script (and MUCH more)".
But again Total Uninstal is also for another use on another time.

__________________

Warning to all! New version.

Download the version 2.0 or above from my website because I detected an important error in Installed File Checker 0.9!

http://www.geocities.com/fredledingo/vbscripts.htm

Error description for version prior to 1.0:
Sometimes the batch process will list files in a directory as unsorted.
So if, in the result file, you see the line "Added: Too many files in directory. Files unsorted" then the following added and removed files are not true.
If files are listed unsorted, previous versions of my script messed up. (fixed in v.1.0)
Strangely, some folders will have the files listed normaly most of the time, then one time the files won't be sorted eventhought the content of the folder had not been modified.


Thought this error has been fixed in the main vbscript, if somebody cam help me with a trick to avoid unsorted list from within the batch file, it will be greatly appreciated.

I have seen one small error more: some unchanged files, maybe one or two, are sometimes listed as missing then, as added again.

I still don't know what is causing this error.

Version 2.0 released today!

It's an important update. The comparison engine has been entirely rewritten.

Prior versions had errors (fake reports of file missing or added).

I worked a lot on this very complicated script so I hope it's finaly working within some pallatable level of reliability!

Known bug:

Sometimes it will list something like that:



I will investigate if this a serious problem or just an entry to be ignored. IMO it can be simply ignored...

Note: The number following "Added" or "Missing" has no meaning and is there for debugging purpose.
I'm planning newer versions, hopefully as fast and more reliable, but I need time...

Advice: run this script often if you don't want to be overwhelmed by the amount of changes it's finding everytime!

version 2.1
-Added: Exclusion list
-Fixed: New folders sometimes not checked (verify batch file and new folders)
-Improvemed the function to avoid unsorted lists
-Updating the batch file for new unsorted folder found during the process
-Fixed: Various potential errors
-Less garbage in the reports! (when listed by blocks)
-Lists of scanned and excluded folders added at the top of the report (also in ScanList.txt)
-Added: Duration of the process (for debuging purpose and curiosity)

-->duration: 5.4 seconds

Version 2.4 released!

2.2
-Improved: Exclusion list setting
-Other minor improvements

2.3
-Removed some debug informations and pop-ups
-Fixed: Mistakes in file path when the script reaches the end of the list

2.4
-Fixed: Various potential errors but maybe not all! :mad:
-Fixed: lists with "0 items" not appearing anymore.
-Improved: Display of small block of files, now listed individualy
-Imrpoved: Naming of the report files (_yymmdd_hhnnss ). Now they will list chronologicaly in Explorer

New project started:
The W98 System Restore (or Back Up) Script Project which is using the same comparison engine.

Hi Fred thanks for your work but due it requiring windows scripting host I am unable to test/give feedback. I disabled/never installed WSH when I locked down my pc against the trojans/worms/viri the script kiddies released

WSH only launches VBS and JS files that you open yourself. If a virus can lauch a VBS file outside the protection of Internet Explorer, it can do it with EXE files as well.
When a VBS file or a VBScript in a web page is launched IE always gives you a warning message that the code can be dangerous.
Having WSH is not more dangerous than having the possibilitiy to run EXE files on your computer.

Note that I disabled scripts in MS-Office!

If I remember correctly bubbleboy amongst a host of others executes just by viewing the infected email in the preview pane of O.E, no user intervention, not similar to running an exe. Probably ok if using OE6 or above and fully patched system (until the next one)
Only pointed it out in case your vbs gets a low uptake/feedback because of the manner its scripted, no malice intended

oscradog,

If there is a software that run dangerous script codes, this software shouldn't be installed on a PC. The problem is that M$ has integrated scripts too much in OE, IE and MS-Office. It's somehow possible to disable that but very few poeple will do it because they don't know.

But are your sure that uninstalling WSH is disabling any script use? I thought WSH was only handling scripts in VBS and JS files... I think that in order to disable scripts on your computer you need to unisntal the script engines and script libraries... then most of the website you are visiting would popup errors constantly and maybe some softwares too... I always believed that IE and OE ran scripts no matter WSH is installed or not... but I can be wrong.

I understand that some poeple may be afraid of using VBS file by fear of viruses. That's undeserved: professionals use VBS scripts for managing servers and networks. They are not always viruses.
+Some poeple may still not have WSH 5.6 installed.
+EXE files look more serious and familiar. without EXE files some poeple may just not know what to do and won't spend time reading the readme.
I know that! Allas.

Maybe one day I try to learn to translate VBS into VB and compile exe's. But that won't be soon.

Anyway: I did these scripts for myself and for mental sport. Public recognition is not my goal but i'm happy if what I do can be usefull for one or two persons.

2.5
-Fixed: Potential errors in reported file paths.

2.6:

-Added HTML output with tables and links to folders
-Improved: TXT output sorted by folder, then by type of change: easier reading
-Fixed: Program not responding (infinite loop) in some case
-Fixed: Files with "hidden" and "system" atributes not listed twice

Important update

2.7
-Fixed an important bug which appeared in version 2.6: many files not reported and wrong paths (Sorry for those who used 2.6 )

2.8
-Fixed more errors.

On My Webpage

2.9 Christmass Release
Nothing very special for xmass but I thought it would be cool to release it today:
-Fixed more errors in checksystem*.vbs, especialy in filepaths. (again)

Makes no mistake: it still can make mistakes.


On my Webpage

Merry xmass!

new update! Visit My Website

Installed_Files_Checker 3.0 works great on my Win98 SE PC.

Keep up the good work.

Best wishes.

Thanks MDGx,
At least i see that one person has been testing it.

I'm working actively on the system restore project and a more graphiocal (hta) interface (maybe a progress bar too).
It looks very promising. I'm very exited about that now. I hope to release a pre-beta version in two or three weeks.

Great release this time:


4.0
-Added: HTA graphic interface to display results and a progressbar
-Added: Summary display (also works without the HTA interface)
-Completely new comparison engine (more use of the memory), which means:
* Much faster for large numbers of file change.
* Speed is more consistant, more predictable.
* Smaller and simplier code (the last one became a monster after all the fixes)
* More reliable
-Fixed: Won't restart the batch file anymore (if that ever happened to you)