Showing posts with label caution. Show all posts
Showing posts with label caution. Show all posts

Improving Wireless Networking on Vista (and XP?)

Some commands for the Command Prompt:
  • netsh int ipv4 reset
  • netsh winsock reset
  • netsh int tcp set global rss=enabled chimney=disabled autotuninglevel=normal congestionprovider=ctcp ecncapability=enabled timestamps=disabled
  • ipconfig /release
  • ipconfig /renew
Registry change from Microsoft KB928233:
  • DhcpConnForceBroadcastFlag 0

Traditional Antivirus is Wasteful

A response to this LifeHacker post:

Traditional real-time antivirus scanning is wasteful, IMO. Viruses can come through in what you download, or if your networking settings are weirdly insecure-- but it's not like you can just "catch" a virus. To warn people that their computers might be unknowingly infected is unnecessarily alarmist; a virus or trojan would have to come from a downloaded or copied file. I scan every file I download by having Free Download Manager call ClamWin (and A-Squared Command Line), which I update hourly (I even made an AutoHotkey script so that the scan happens in the background). This precaution makes more sense than scanning every file whenever it is read or written, and it is hugely better for your I/O performance.

All in all, though, blacklist-paradigm antivirus does not make a lot of sense nowadays for on-access scanning, because viruses (and more relevantly, other kinds of malware) spread before virus definitions are created. Furthermore, on-access scanning of files involves a huge performance cost. If you scan all incoming files, extra file scanning doesn't make any sense unless the virus definitions have been updated in the interim. I'm perplexed, for instance, by Avast!, which can scan all files + emails + IMs... if all files are being scanned, why the extra scanning repetition due to its route of entry?

However, blacklist-oriented antivirus seems wise for periodic on-demand scanning. For this, Norton Security Scan available free through Google Pack is a nice choice.

A better choice for so-called real-time antivirus, though, is behavior-based scanning such as Threatfire, but I prefer Mamutu ($30 for 1 year). Threatfire would interfere with several programs (especially the kind that export files to other formats: PDF Creator, AutoHotkey EXE compiler) even when "suspended," so I can't recommend it unless you're allergic to spending money on security software (as I tend to be). Comodo Firewall is another free alternative in this vein, but it is quite confusing.

Additionally, you can take some preventive measures by using SpywareBlaster. I paid for the privilege of auto-updating and to support its development, but you don't have to.

The one thing that irritates me most about many anti-malware products: the false positives. Since trying out Comodo BOClean and having it shut down a program I wrote myself as a trojan, I've been very suspicious of claims that BOClean has caught malware other antivirus missed. When I see claims like that, I wonder about the likelihood that it is a false positive. (To be clear, I do NOT recommend Comodo BOClean.)

A final note is that I think infrequently-updated real-time antivirus like AVG, which allows only daily updates in its free version, is the worst (if used by itself), because you're exposed to the newest threats while suffering an I/O performance hit.

PNRP 2.0 Upgrade for XP is Bad News

After installing KB 920342, wireless networking completely stopped working for me. Between Bonjour, ThinkVantage Access Connections, Intel PRO/Set Wireless, and all the other networking items, I have no idea what completely choked after installing this upgrade to a feature that I don't even understand. I recommend avoiding it.

In fact, perhaps the optional updates in Microsoft Update aren't really worth it:
  • A Root Certificates Update led to redundant friendly names
  • A new driver for Lenovo locked my keyboard and trackpoint, even in safe mode
  • And now, PNRP 2.0

Beware If Taking the AHCI Plunge

With a recent BIOS update, I noticed a new option for AHCI vs. IDE mode. Even though Vista has support for this new supposedly feature-rich disk technology, those drivers are disabled after installation. Vista won't even boot after making the change in BIOS to AHCI unless you first do the following:
To resolve this issue, enable the AHCI driver in the registry before you change the SATA mode of the boot drive. To do this, follow these steps:
1.Exit all Windows-based programs.
2.Click Start, type regedit in the Start Search box, and then press ENTER.
3.If you receive the User Account Control dialog box, click Continue.
4.Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
5.In the right pane, right-click Start in the Name column, and then click Modify.
6.In the Value data box, type 0, and then click OK.
7.On the File menu, click Exit to close Registry Editor.
From KB 922976

Some Services Are Just Supposed to Run "Manual"

I tweak with Services settings for better security and performance, but it's a silly endeavor, because the services themselves are quirky: they might not start correctly if they are set to Manual when they should be Automatic (3rd party services especially, it seems) and vice versa!

Here are some services that should have their startup types be Manual even though they are running most of the time:

  • COM+ Event System
  • Network Connections
  • Network Location Awareness (NLA)
  • Remote Access Connection Manager
  • Telephony
  • Terminal Services

Fix Wireless Network Reconnection

If you're having problems with reconnecting to your wireless network after wake/resume from sleep/standby, or if you are getting errors upon connecting due to cancellation or timeout, or if you are having other problems with your wireless in Windows XP SP2 or Vista, try these solutions:


  1. Update wireless adapter drivers if necessary (Vista SP2 Beta might also fix)
  2. Disable unused network adapter(s) in Device Manager (except hidden devices)
  3. Disable power management of wireless adapter: mark Maximum Performance in adapter properties (if available in driver itself) and in advanced settings for power profiles in Windows [More on the latter in Vista]
  4. Also: in Properties for wireless adapter in Device Manager, on Power Management tab, uncheck 'Allow computer to turn off this device to save power'
  5. Set DhcpConnForceBroadcastFlag registry key to 0 [More]
  6. Reset networking with the following from the command line and reboot:
netsh int ip reset
netsh winsock reset

How to Disable the Annoying Blinking LED for an Atheros Wireless Adapter

In Regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318} and look the key for your wireless adapter.
Back it up then delete the following keys:

gpioPinFunc1
gpioLedCustom
gpioFunc1ActHi


After, restart.

If you want to have a visual cue of network activity, you can right-click the network icon in the notification area of the taskbar and select Turn On Activity Animation, and this is more subtle and less distracting than the amber LED. By the way, the button to turn the wireless adapter on and off still works after deleting the above keys.

Crossposted here