You'll now want to add ICQ's Net Agent Detect to the list (which is probably empty unless you've already been in here). Make sure 'Enabled' is checked, then click 'Show'Ħ. In the window on the right, double-click on 'Run these programs at user logon'ĥ. Under 'User Configuration', click 'Administartive Templates'Ĥ. Go to the Group Policy Editor (Run->'gpedit.msc')Ģ. Here's how to do it (am using WinXP Pro):ġ. They did not come across a solution, however it did give me an idea.

I was browsing through the boards here and came across a thread discussing this problem: The previous solution was to move Net Detect Agent *out* of the Startup folder, put a shortcut on the Desktop, and use that when you wanted to connect. This occurs despite the fact that 'Net Detect Agent' and 'automatically connect to internet when no connection present' are checked. The Problem is that when XP loads, ICQ pops up and says 'no connection detected'. Save time by identifying the types of changes that do not alter how the system works and creating documented procedures in your QMS that outline how these changes are addressed.Įxamples of changes to validated systems that can be effectively handled as procedures include:Īdopting a risk-based approach can reduce validation efforts, costs, and project duration.It seems lots of people are having problems with ICQ and WinXP not finding a network/internet connection upon XP startup (especially those on DSL modems like myself, or those with LAN/T1's, etc.) However, not every computer system change requires full revalidation. When software or hardware is updated or substantially changed, risk assessment and revalidation is critical to ensuring the system still functions appropriately for its intended use. Once you’ve identified the risks and impacts of each, you can document how you will respond, including identifying appropriate controls and verifying that the controls are applied successfully.

Icq to g o