[Fredledingue]

Installed Files Checker 4.8
(by Fredledingue)
Homepage - more infos
Direct download


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

This application is very useful and handy everytime you install or uninstall something. You can also do a check regularly without installing or uninstalling anything, for keeping a watch on your system or just for fun.
It takes only a few seconds.
If something goes wrong you can always try to find out what has changed since it was all right.

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

What's new?



4.8
-Fixed unability to check files when the DOS version is changed (w98) and the DIR command gives a different output.
-Improved: lower risk of false modified or missing/added couples in normal times thanks to the fix above.
-Added buttons "See Archives" and "Setings"

4.7
-Fixed: The folder being checked not properly showing
-Fixed: New bug where folders didn't open from their link in the results page (bug in "Escape" method)

4.6
-New: Support for Windows XP and other OSes using the same DOS version.
-New: Displaying system file versions (exe, dll etc) for added and modified files
-Improved: Slightly faster
-Improved: Option to shrink or expand table cells containing long names
-Improved: Style (color, table, font etc) and better html code
-Improved: Focus directly on the "comment" box
-Improved: Displaying the folder being checked when this one takes a long time to do
-Fixed: Potential mistakes when more than 50 files have been added or missing in the same folder
-Fixed: White space preceding file names when the hour in the file date is followed by "a" or "p" (very minor bug)
-Fixed: Main window hiding the taskbar when enlarged for viewing details
-Changed: Location of the program's registry entries


4.5b (silent update - no effect while using)
-Fixed minor bug with registry (ProgramFilesDir)

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


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

This post has been edited by Fredledingue: 03 August 2011 - 06:32 AM

[eidenk]

I am using this usually : http://www.xs4all.nl...ware/syslog.zip

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

[MDGx]

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]:

[Version]
Signature=$CHICAGO$
[DefaultInstall]
CopyFiles=LST1
[LST1]
FILE1.TXT
FILE2.TXT
LIST1.TXT
LIST2.TXT
WHATEVER.???
[DestinationDirs]
LST1=28700
[SourceDisksNames]
1=,,0

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

This post has been edited by MDGx: 28 May 2006 - 06:57 PM

[Fredledingue]

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)

"MDGX" said:

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]:

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.

This post has been edited by Fredledingue: 29 May 2006 - 02:10 AM

[PROBLEMCHYLD]

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.

This post has been edited by PROBLEMCHYLD: 29 May 2006 - 10:06 AM

[Fredledingue]

Nice to read that's working!

PROBLEMCHYLD, on May 29 2006, 09:34 AM, said:

1 thing though can you write a code so we don't have to use the bat.file

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.

[MDGx]

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.

This post has been edited by MDGx: 29 May 2006 - 04:01 PM

[Fredledingue]

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

"MDGx" said:

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.

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.

This post has been edited by Fredledingue: 30 May 2006 - 02:07 PM

[Fredledingue]

"MDGx" said:

There is not equivalent for batch files [DOS mode] for "C:\Program Files" set %variable% location in 9x OSes.

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

[MDGx]

Yes, I was talking about your list_files_in_text.bat file, part of your SFC script:
http://www.geocities...heck_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.

This post has been edited by MDGx: 30 May 2006 - 03:19 PM

[Fredledingue]

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

Quote

because I have this line in my autoexec.bat:
SET DIRCMD=/A/O:GEN/P/V

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!

This post has been edited by Fredledingue: 05 June 2006 - 01:57 PM

[RainyShadow]

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

[MDGx]

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:

@echo off
echo Creating list of your System files.
echo This may take 1 - 2 minutes.
echo.
echo Creating list of your C root files.
echo Please wait...
set list=WINF_B.TXT
dir C:\ /O:GN /-P>> %list%
dir C:\ /O:GN /A:S /-P>> %list%
dir C:\ /O:GN /A:H /-P>> %list%
echo Creating list of your Windows files.
echo Please wait...
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%
echo Creating list of your Program files.
echo Please wait a bit longer...
dir C:\PROGRAMS /O:GN /S /-P>> %list%
dir C:\PROGRAMS /O:GN /A:S /S /-P>> %list%
dir C:\PROGRAMS /O:GN /A:H /S /-P>> %list%
CLS
EXIT

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

HTH

[Fredledingue]

RainyShadow,

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

[Fredledingue]

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.

Quote

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

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.

Quote

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

That's normal.

Quote

Please note that my "C:\Program Files" folder is actually called "C:\PROGRAMS"

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.

This post has been edited by Fredledingue: 01 June 2006 - 04:00 PM

[MDGx]

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:

 1.gif (3.1K)
Number of downloads: 36

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

[Fredledingue]

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.

[MDGx]

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:

Quote

[HKEY_USERS\.Default\Software\Microsoft\Windows Script Host\Settings]
"Timeout"=dword:00000000
"DisplayLogo"=dword:00000000

And this is what I had originally:

Quote

"Timeout"=dword:00000003

Thanks again for your cool tool.
Excellent job.

[eidenk]

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.

[Fredledingue]

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.