Hi David
Thanks for your reply
I don't know if this isn't an incorrect setting.
UseRAS=1 is for dial-up connections, but I assume for dial-up modems only and I don't know if a DSL modem would fall into that category
I tried both ways; first I used always connected, then dialup
I have a DSL LINE which is always on
I have a Dsl modem which connects to ISP
I bought the modem seperately - Dynamode[Hardware/software]
( ie My ISP doesnt use connection software - It just provides you with your user name and PW to connect to them)
Dynamode emulates a Dialup modem,
The connection it installs is called wiptech
The connection phone number is p0,38
To connect to my ISP I doubleclick the wiptech icon and it dials into my ISP
Avast used to run alright although it would connect to the internet when I rebooted, rather than using my internet settings like my previous Antivirus did "AntiVir classic"
I googled and the solution was to set my dialup networking To Never Dial a connection
It worked okay.Avast only connected to the update server when I connected to the internet with IExplorer.
then there was an Avast Program Update.
After that I noticed that my other Apps were no longer able to automatically initiate a connection when I launched the App.
Such as Bit torrent. News reader, IExplorer. etc or when my internet connection became disconnected.
Setting my Dialup connection and internet connection to Always dial my default connection was to no avail as on reboot they both returned to never dial a connection
I Disabled AVAST in MSCONFIG and the setting stayed correct
ie always dial my connection.
Some observations:
Changing the connection settings in IE changes the connection settings in Dialup networking and VICE VERSA
My situation mirrors this
http://forum.avast.com/index.php?topic=656.msg3162#msg3162I'm wondering whether this is a conflict between Avast and Win9x OS's
Vlk The Moderator gave a reason why this behaviour was occurring!
It is still necessary to use the UseRAS setting.
Let me explain this little more. By default, avast uses the PING command to find out whether the computer is online (or, to be more specific, whether it can access at least one of its update servers). The problem with PING is that is causes the 'Dial a connection' dialog to appear under Win9x, forcing the user to take an action. That is of course unacceptable, so avast tries to always disable this feature before performing the PING. The problem is, however that unsuccessful PINGs take a lot of time, so in result the 'never dial a connection' setting effectively gets activated too often (and for too long time) - in fact almost all the time... Basically, this is caused by the poor design of the dial-up support in Win9x where the 'never dial a connection' setting is system-wide, whether it should actually be process-wide (as is almost everything else).
So we added the UseRAS feature that uses a different approach. Instead of the PINGs, it periodically queries the status of the modem. Of course, this only works if you have a dial-up modem (so this setting should never be used if the connection is implemented by other means). In addition, there was a bug in build 229 that caused the modem status query to always succeed... Version 235 should have it right, I believe, but from your post, I'm starting to doubt it...
Vlk[/shadow]
I alo notice that Avast uses:
RPCSS.exe which is the RPC(Remote Procdure Call) API handler
What does Avast need RPCSS for?
Is it linked in with this problem?