JockMullin
MIS
Not having heard any alerts, I yesterday updated my system with the latest Tuesday batch of MS updates to my XP Pro SP2 OS.
Subsequently I was unable to log into my ISP (Compuserve) - a connection which requires execution of a script (CIS.SCP) which is supplied with XP and was working fine previously.
Contacted CIS and was told to replace the $LOGON and $PASSWORD tokens in the script with my actual login and password in quotes. That did not help, still got "Login or Password Invalid on Domain" following modem connect.
Tried setting up a new dialup connection - that also failed but this time the log indicated an error when trying to set the port parameters.
Finally got running agin by restoring my system from the checkpoint taken before the update. It turns out RASMANS.DLL was replaced by the update. AFAIK the script itself was not changed.
It seems possible this may have implications to anyone using a script based internet connection.
I'll just bet NOBODY in Redmond uses dialup.
Jock
Subsequently I was unable to log into my ISP (Compuserve) - a connection which requires execution of a script (CIS.SCP) which is supplied with XP and was working fine previously.
Contacted CIS and was told to replace the $LOGON and $PASSWORD tokens in the script with my actual login and password in quotes. That did not help, still got "Login or Password Invalid on Domain" following modem connect.
Tried setting up a new dialup connection - that also failed but this time the log indicated an error when trying to set the port parameters.
Finally got running agin by restoring my system from the checkpoint taken before the update. It turns out RASMANS.DLL was replaced by the update. AFAIK the script itself was not changed.
It seems possible this may have implications to anyone using a script based internet connection.
I'll just bet NOBODY in Redmond uses dialup.
Jock
