All,
I've just downloaded the new Forceware Network Access Manager (nvFirewall) for Windows XP. It is basically your typical personal firewall wrapper for your TCP/IP stack with hardware acceleration for nForce4-Ultra and nForce4-SLI boards.
Upon first use, I noticed that it used my web browser for its GUI administration, connecting to a port on my localhost address. This perked my interest as to what http daemon they were using.
To my shock and horror, they were using Apache for Win32! This beast consumes over 23MB of memory on my system!
Perhaps my head is still stuck in the early 1990s when I ran AmigaOS quite well on a system with no more than 4MB of memory, but does it strike anyone as bad that my GUI for my hardware firewall consumes 23MB? Heck, if you include the memory to run Firefox (18MB), it jumps to a whopping 41MB of memory!
This is nuts. This is so bad that I've already uninstalled the software from my computer.
Does anyone else agree with me on this?
I've just downloaded the new Forceware Network Access Manager (nvFirewall) for Windows XP. It is basically your typical personal firewall wrapper for your TCP/IP stack with hardware acceleration for nForce4-Ultra and nForce4-SLI boards.
Upon first use, I noticed that it used my web browser for its GUI administration, connecting to a port on my localhost address. This perked my interest as to what http daemon they were using.
To my shock and horror, they were using Apache for Win32! This beast consumes over 23MB of memory on my system!
Perhaps my head is still stuck in the early 1990s when I ran AmigaOS quite well on a system with no more than 4MB of memory, but does it strike anyone as bad that my GUI for my hardware firewall consumes 23MB? Heck, if you include the memory to run Firefox (18MB), it jumps to a whopping 41MB of memory!
This is nuts. This is so bad that I've already uninstalled the software from my computer.
Does anyone else agree with me on this?