Installed (System) Files Checker.hta

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

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:

[HKEY_USERS\.Default\Software\Microsoft\Windows Script Host\Settings]

"Timeout"=dword:00000000

"DisplayLogo"=dword:00000000

And this is what I had originally:

"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.

[eidenk]

Stupidely I clicked on the error message too fast.

[Fredledingue]

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!

Edited June 5, 2006 by Fredledingue

[eidenk]

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.

[eidenk]

It seems it is doing allright now.

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

[MDGx]

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.

[Fredledingue]

MDGx

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

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.

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

[ack-hh]

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

[Fredledingue]

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'?

Does it list all the files including the system and the hidden files?

Note that I'm not a DOS specialist.

And, BTW, why are you using a batch file at all? You can process

directories (and their subdirectories) with VBS very well.

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.

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

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.

[RainyShadow]

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

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

Edited June 6, 2006 by RainyShadow

[eidenk]

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.