| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 46957 | 2004-07-11 00:33:00 | Changing the startup type of a software firewall | agent (30) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 251422 | 2004-07-11 00:33:00 | In Windows 2000 or XP, open Computer Management and select Device Manager. On the View menu, tick 'Show hidden devices'. Expand 'Non-Plug and Play Drivers'. If, like me, you use Kerio Personal Firewall (2.1.5), you should see a driver called 'Kerio Personal Firewall Driver'. Open the properties for the driver, and go to the Driver tab. Here you should see an area to change the startup type - on my computer it is set to System. For a summary of the available startup types, right click and select "What's This?", or go here (www.microsoft.com). To get to the point, I'm wondering if anyone knows whether changing KPF from the System to the Boot startup type would render a computer unusable - as the warnings from Microsoft state. Even if you don't use KPF, I suspect you could do much the same with other software firewalls, or even antivirus products if you so wished. I for one would be glad to try getting Kerio to load earlier in the boot process, as opposed to later - which, gathering from what I have read about these startup types, changing it to Boot would initialise the firewall earlier. That said, I don't use any disk imaging products like Norton Ghost, and I'm not sure if System Restore is capable of rolling back something like this if it all goes haywire. So, does anyone have any opinions on whether this is a safe thing to try, or even better, could anyone try it out and inform the rest of us if it is safe? |
agent (30) | ||
| 251423 | 2004-07-11 01:12:00 | generally speaking it wouldn't be a good idea to play with the startup types. no doubt kerio (or other) would have set it to whats best. it may require certain drivers/devices to be enabled before being loaded. you could just ask at the kerio forums. | tweak'e (174) | ||
| 251424 | 2004-07-11 03:06:00 | Well, yes, it might depend on other drivers being loaded. So, I'll set all my drivers to the Boot startup type :p I have posted this question at the Kerio forums, but I posted it here as well, in case anyone here knows... or is willing to try. |
agent (30) | ||
| 251425 | 2004-07-11 04:41:00 | AFAIK, Kerio starts up before Windows logon. Early enough for me. If something is is on your system and initialised before this, I'm sure Kerio will nab it as soon as it tries to do anything untoward. Or, are you worried that the something will attempt to disable Kerio before it has loaded? Cheers Murray P |
Murray P (44) | ||
| 251426 | 2004-07-11 07:42:00 | No, in fact, I learnt my lesson with malware firstly when I opened an email that appeared on my desktop, and secondly, when I installed a certain P2P software and found my computer ground to a halt with all the additional products being downloaded. Anyhow, I'm generally one of those people who like to tinker with things that are new to them. Like this one time when I was younger, and I touched two wires together to see what they did... Nevertheless, Kerio does start up before you logon - though if you're quick enough to logon, that won't be so true. It's more the fact that in SP2, the Windows Firewall is started on a basic level before even the network is started. I don't like parts of SP2, so I won't be installing it, and I wouldn't touch Windows Firewall with a 10 foot bargepole - so making KPF start earlier would be a nice change. |
agent (30) | ||
| 1 | |||||