Share an Internet Connection With Multiple Computers

Linux offers the ability to act as both firewall and router for 
multiple computers. You can easily set this up using iptables. 

Execute the following commands on your Linux box. This example assumes 
that eth0 is the network interface connected to the cable or DSL modem. 

# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE 
# modprobe ip_conntrack_ftp 
# echo 1 > /proc/sys/net/ipv4/ip_forward 
# iptables -P INPUT DROP 

Of course, this is greatly simplified; it's just the basics to get you 
up and running quickly. 

Keep in mind that it doesn't matter what systems you're running on your 
network, be it Windows, Macs, or other Linux systems. All you need to 
do is tell those clients to use this Linux machine as the gateway.

Manually resetting AUTOCHK.EXE for a drive

A crash can sometimes cause the dirty bit to be set when there was no data pending to be written, provoking a disk check the next time the system is rebooted. This in turn can cause a disk check to run persistently at each reboot, even when the dirty bit has not been set. If a disk check is running at each reboot regardless of whether or not the system was shut down cleanly, then the problem is no longer the dirty bit per se, but rather the way AUTOCHK.EXE has been configured to run at startup. 

There are a few ways to manually override this. The first is to run CHKDSK /F on the drive in question; if it runs successfully, the AUTOCHK.EXE command is cleared and the system will no longer be checked at each reboot. Another way to do it is to edit the Registry directly and remove the AUTOCHK command. To do this, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager in the Registry and look for a REG_MULTI_SZ value with the name BootExecute. Set the value of BootExecute to a null value. This will prevent AUTOCHK from running on next reboot. 

On the whole, it's safest to first attempt to use CHKDSK /F on the drive that is being repeatedly checked at startup. Editing BootExecute should only be done if CHKDSK doesn't seem to be working. Running CHKDSK also has the added bonus of manually clearing the dirty bit.