The system cannot find the file specified.

[system]

@igor post:19

My guess would be a misconfigured TEMP folder.
But if you weren’t using those stupid runtime functions, but rather Windows API directly, you’d get a (slightly) better error code

Ha ha ha.
Cross checked the runtime, wouldn’t get anything more interesting anyway. Would lose easy cross-compiling on other systems though (and without the need of hundreds of #ifdef). Big deal. :

Alanrf, the ‘runtime part’ of igor’s msg was pointed to me

[alanrf]

Then slap Igor for not supporting the team … and I’ll give him kudos for honesty.

By the way, I think you are still misunderstanding my point about the error message.

I’m not asking that you tailor an error message to the user for every error condition, your logs are clearly the place for the error reporting details.

But the net here is that (for whatever reason) avast could not connect to any server to get the update.

So a simple “avast could not connect to the internet” would be a lot clearer as a “coverall” to the user than the error messages now.

That’s all.

[igor0]

@kubecj post:21

Cross checked the runtime, wouldn’t get anything more interesting anyway.

Well, you’d distinguish between “File not found” and “Path not found” at least.

@alanrf post:22

But the net here is that (for whatever reason) avast could not connect to any server to get the update.

Not in your case I think - it seems like a misconfigured %TEMP%.

[alanrf]

No it is not a misconfigured temp.

This is the temp folder that has been used with avast by this user for in excess of a year and is the system temp folder. Avast is also installed on the I: drive and seems to have no problem writing (its error log for example) there.

Edit: I just connected remotely to this user’s system. avast is still installed on the I: drive and avast’s webshlock.txt file was created successfully at the last system start and is in the I:\Temp folder which is defined in the WinXP system variables as the temp folder location. All the user’s system starts since the problem have been without errors from avast, but I did have him edit the avast4.ini file to delay the avs update process to 90 seconds after the incident occurred.

By the way precisely the same error log is to be found posted in June by a user in the avast Swiss forum ... the only difference is the drive is C: and the temp file is using the windows defined defaults for placement of the temp folder.

http://forum.avast.ch/viewtopic.php?p=22&sid=384604c7fdf2476812623a0abcc062f7

[system]

All of this was “then”, and this is “now”. Sixteen months later, I have version 4.7-892, and everytime I reboot, I get the dreaded red box that says “Cannot find specified file.”

As an uninformed user, all this tells me is Avast isn’t working because there’s a file either missing or unavailable. Can you be a little more specific?

In reading the forum, this is apparently an ongoing problem?

[Lisandro]

@jmarkt post:25

As an uninformed user, all this tells me is Avast isn’t working because there’s a file either missing or unavailable. Can you be a little more specific?

Can you update? Manually, automatically? Every time or just you can’t after login?
Against what are you complaining?

[system]

The program is “complaining”…that it “cannot find the specified file”…whatever that is? I don’t know if it’s not automatically updating or what. I assume the red warning window isn’t a good thing, but it doesn’t give me a clue as to what to do about it.

Are you suggesting it’s OK to simply ignore the problem?

[Lisandro]

@jmarkt post:27

I assume the red warning window isn’t a good thing

It’s not. You’re not able to update

@jmarkt post:27

but it doesn’t give me a clue as to what to do about it.

Basically, check:

1. If the servers.def file is corrupt or 0KB (C:\Program Files\Alwil Software\Avast4\Setup\servers.def).
   You can try and download the servers.def file, http://files.avast.com/iavs4x/servers.def and replace the one in the avast setup folder.

2. If your subscription allows the update right now (i.e., if it is not expired).

3. If your firewall settings and allow avast.setup to connect.
   If you’re not sure, just turn off your firewall (to be sure the update failure is not due to it).
   Maybe you should ‘remove’ avast.setup entry, try to update, receiving a new alert from the firewall, allowing it and checking it to remember.

4. Check your proxy settings into avast!:
   Left click the avast icon > Settings
   Update (Basic) > Details > Proxy
   Make sure your browser is not set to “Work Offline” (this option is generally in the File menu).
   If it doesn’t help, try switching from “Auto-detect” to “No proxy” (I’m assuming you’re not connecting to the Internet via proxy).
   You can run proxycfg -d in a DOS window to make your computer connect direct, without proxy. You can run proxycfg -h for help.

@jmarkt post:27

Are you suggesting it’s OK to simply ignore the problem?

For sure not… you need to update…

[alanrf]

jmarkt

any change in the status of your problem?