Software Forum

Hi,
I was trying latest AU beta build 2.4.1.3089 and noticed the following.

Sometimes, while erasing history, AU replies with an error message...
"Error deleting file or folder - Cannot delete something[1]: It is being used be another person or program...."

It looks that it cannot delete some IE temp files, found them in-use by IE. Closing all IE instances allows AU delete those files.
Also this error message has it's own window, appearing as a separate task in windows taskbar.

Besides that, latest beat works fine

Regards

Hi Inray,

Unlike other programs, AU does not use the Windows API 'DeleteFile' to delete files. AU uses the same function that is used by Windows Explorer. So the dialog you see is the one built-in Windows itself. If AU can't delete it, it means Explorer can't delete it.

Hari, that sounds right.
Btw only AU beta (2.4.1) gives that error. AU 2.4.0 under same circumstance shows no error message.
Don't you think that it would better if AU ignore those errors and skip files in use, instead replying with multiple error messages ?

Correction
Just re-downloaded AU beta from http://www.acelogix.com/downloads/au_beta.exe and looks that you've changed something. Now it doesn't display those errors.
Addentum
Nope, it still displays error messages when files are in use by IE.

May i ask if is possible for you to post here a note when you upload a new beta build ?

PS: 1. Reg cleaning new layout is much better than before
2. Suggestion: Manifest webupdate.exe, looks a bit ugly when pops up over AU

Thanks

2.40 checks if the files are in use. But on one user's Win98, it caused BSOD. I could do nothing, as it was the CreateFile API of Windows that caused it. So I had to turn the checking off in the beta. Seems I have to find another way.

Were you running IE and trying to delete the files ?

thanks

Were you running IE and trying to delete the files ?

In one case yes, IE was running. Some other times, AU shows the error message with no IE been active (double checked in task manager).

Btw notice similar behavior under XP, SP1, SP2, 2k3 and 2000

Regards

OK, I'll make it work like 2.40 and issue the user with BSOD a custom build.