Bolens BL110 only runs on half choke

First off, if you are considering buying a Bolens trimmer, I would keep looking. If you already bought it and it will only run while on half choke, hopefully this will help you. I started having issues after about a year of purchasing it. Starts ok and will run on half choke, but as soon as you fully back off the choke, it stalls.

On top of the carburetor there are two screws surrounded by an aluminum housing. They are partly flat on one side and the rest is round. Take a hack saw or dremel tool and start notching out the aluminum housing until you reach the top of the screws (be careful not to get any aluminum shavings inside the carburetor). Make a small notch in each screw until you can fit a small flat-head screwdriver in them. Rotate each screw 1/4 turn counter-clockwise. Now start it up and it should run great. If not, you have something else wrong.


Sonicwall TZ Series Bridge Wireless to LAN

Looking to have your WLAN and LAN on the same subnet and getting this error “Error: Index of the interface.: Portshield interfaces can not be assigned to L2 bridge“? Make sure your firmware is at 5.8.x.x or older. As of this posting Dell did away with the ability to bridge your W0 (WLAN) interface to X0 (LAN).

To bridge your WLAN interface to the LAN interface, follow the below the steps. I’m using a TZ210w on firmware revision :

  1. Login to the Sonicwall
  2. Wireless > Settings > Make sure Wireless Radio Mode is set to “Access Point
  3. Network > Interfaces
  4. Configure W0 interface
  5. Set IP assignment to “Layer 2 Bridged mode”
  6. Set Bridged to: “X0” and click OK
  7. Your interfaces should now look like this:







Hyper-V Time Sync

You will find a variety of opinions on the subject of time synchronization with Hyper-V, even from Microsoft. Some recommend to completely disable time synchronization integration for domain controllers, partially, or not at all. My below recommendations are opinions based on a variety of sources and may not work in your environment.

By default, the time synchronization service is enabled for any Hyper-V VM. If you have not made any time configuration changes, this may mean your virtualized domain controller is syncing time with its physical host. This could present a problem if the host is syncing with itself or with a domain controller that has incorrect time .

When a virtual machine is restarted or shut down, it does not have the “physical” ability to keep track of time. When the VM starts the time is taken from the host. This is done regardless of whether or not the time synchronization service is enabled.

Configure Your Host Servers to Obtain Time From an External Time Source

Open a CMD prompt from the host server and execute the following commands:

w32tm /config /,0x1 /syncfromflags:manual /update

net stop w32time

net start w32time

w32tm /resync /force

w32tm /query /source

Verify is listed, or whatever time source you used. If not, try restarting the time service again.

Check System log for Time-service event 37: The time provider NtpClient is currently receiving valid time data from

Configure the PDCe to Obtain Time From an External Time Source and Disable Hyper-V Time Integration

Open Hyper-V management console > Right-click the virtual machine > Settings > Integration services > de-select ‘Time Synchronization’.

Open a CMD prompt from the virtual domain controller holding the pdc emulator role and execute the following commands (typing ‘dsquery server -hasfsmo pdc’ at a command prompt will output the server holding this role):

w32tm /config /,0x1 /syncfromflags:manual /reliable:yes /update

net stop w32time

net start w32time

w32tm /resync /force

w32tm /query /source

Verify is listed, or whatever time source you used. If not, try restarting the time service again.

Check System log for Time-service event 37: The time provider NtpClient is currently receiving valid time data from

Configure Member Servers to Obtain Time From PDCe and Partially Enable Hyper-V Time Integration

Open a CMD prompt from the remaining virtual member servers and execute the following commands:

reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0

w32tm /config /syncfromflags:DOMHIER /update

net stop w32time

net start w32time

w32tm /resync /force

w32tm /query /source

Verify the PDC emulator is listed, or whatever time source you used. If not, try restarting the time service again.

Check System log for Time-service event 37: The time provider NtpClient is currently receiving valid time data from servername

Windows Time Errors and Issues

If you are seeing Windows time errors on your virtual domain controllers, such as ‘time service detected a time difference of greater than 5000 milliseconds  for 900 seconds’ or ‘the time service has stopped advertising as a time source’, then you may need to increase the interval at which the server syncs its time to help with the time drift.  The following registry settings may resolve this:


set the SpecialPollInterval value to 900 (decimal)

The SpecialPollInterval specifies how often to sync time in seconds …in this example 900 seconds = 15 minutes. The time service will only use this setting if the SpecialInterval flag is set (ex.,0x1). You may also use 0x9 which is a combination of 0x1 and 0x8 (SpecialPollInterval + client mode).

It is also recommended to configure the MaxNegPhaseCorrection and MaxPosPhaseCorrection. (See here for an example why


Microsoft recommends setting both MaxNegPhaseCorrection and MaxPosPhaseCorrection values to 48 hours (172800 in Decimal). This would tell the time service to only accept time changes that are less than 48 hours behind its current time (MaxNegPhaseCorrection) and less than 48 hours ahead (MaxPosPhaseCorrection). Anything else is ignored.

If you are having issues with your settings not working or the windows time service not starting, re-registering the time service can sometimes help. This will set windows time settings back to default.

Open a CMD prompt and type the following:

net stop w32time

w32tm /unregister

w32tm /register

net start w32time





VMware – Routing Between Host-Only Networks Using Vyatta

In this tutorial I will show one method of routing between multiple virtual host-only networks in VMware Workstation 8. This can be useful for simulating a large multi-site network in a lab environment at little cost.  In order to do so, we will be using Vyatta [vee-ah-tah] Network OS and simulating the following simple 3 site network.


Step 1 -Create Virtual Networks

This tutorial assumes you already have your VM’s created, so we will jump right to the networking.

-In the VMware Virtual Network Editor, create an interface for each virtual network you wish to simulate and route. For my example, I will need 2 interfaces for each site. One for the LAN interface and one for the WAN interface.

-Edit > Virtual Network Editor > Add Network.  I have setup my virtual networks as follows.

Step 2 – Create Vyatta VM

I will be using Vyatta 6.2 and working from the CLI (command line interface) and also showing you how to enable the GUI web interface. Vyatta 6.3 is the latest distribution since posting and now requires you to have a paid subscription to access the web interface. If the web interface does not interest you, use the latest version.

-Once you have downloaded the Vyatta LiveCD, you will need to create a new VM.

-Open VMware > File > New Virtual Machine > Typical configuration > select the Vyatta ISO as the Installer Disc Image > Vyatta is Debian based Linux OS, Debian 6 works fine for Guest OS > Give a name and location for the VM > 2GB disk space is enough for Vyatta > Choose “Customize Hardware” > You need only give Vyatta 512MB of RAM > Finish

-Now you will need to install the Vyatta OS. Once the CLI finishes loading, log in with the default credentials. Username: vyatta Password: vyatta (Note: the password will not show as you type).

-Type ‘install-system’ and press enter (no quotes) to start install process.

-Type ‘Y” to continue install.

-Vyatta will scan the drives and ask how you would like to create the required root partition. I will choose ‘Auto’.

-If you only have one drive, choose the recommended one. In my case ‘sda’.

-It will warn you any existing data on the drive will be lost of you continue. Since I have nothing on this drive I will enter ‘Y’.

-You will then be asked how big of a root partition you want to create. I will only be using this drive for Vyatta, so will allocate all available space.

-Choose to copy the recommended configuration files to the drive. The path is provided in the [brackets].

-You will then be prompted to change the default Vyatta admin password. You will need to remember this in order to log in to the CLI or web interface.

-Select which drive for the GRUB boot loader.

-Once the GRUB is configured, we will want to shutdown the VM so the virtual interfaces can be added. To shutdown, simply type ‘shutdown’ and hit enter. Vyatta will confirm that you want to do so, choose Yes.

Step 3 – Configure the Routers

-With the Vyatta VM shutdown, you will want to add all the interfaces it will be routing. Remember, in this tutorial I am simulating 3 physical routers. I will need to add the LAN and WAN interface for each router.

Before powering on the Vyatta VM, make sure you have disconnected the Vyatta ISO disc

-Power on Vyatta and log in using the admin password you set during installation. The user name should still be vyatta.

-Issue a ‘show interfaces’ command and you should see all attached interfaces.

-In order to make any configurations, you must enter configuration mode. To do so, simply enter ‘configure’.

-Now you can configure each router. First assign an IP address to each interface. I will assign mine as follows

eth0 > > Site 1 LAN
eth1 >    > Site 1 WAN
eth2 > > Site 2 LAN
eth3 >   > Site 2 WAN
eth4 > > Site 3 LAN
eth5 >   > Site 3 WAN

-To assign an IP to an interface: set interfaces ethernet eth0 address

-Assign the proper IP for the remaining interfaces. If you wish, you can also enter a description for the interface: set interfaces ethernet eth0 description “Site 1 LAN”

-After you have configured any IP and descriptions you need, you must issue a ‘commit’ command and a ‘save’ command. If you are done making configurations, enter ‘exit’ to leave configuration mode.

-You can issue another ‘Show interfaces’ command to make sure all the configurations you made are correct.

The last step is to implement a routing protocol. I will use RIP since the hop limitation does not matter in this scenario. Make sure you are back in configuration mode.

-Advertise interface: set protocols rip interface eth0  (issue this command for each interface)

-Redistribute the connected routes: set protocols rip redistribute connected

-Commit and save changes.

Step 4 – Test Routing configuration

At this point you should be able to configure the NIC’s on your other VM’s. Make sure to assign a proper NIC and default gateway to each VM. For example, Server1 in the diagram above will be assigned to VMNet0 and have a default gateway of Once you have the VM’s properly configured you should be able to ping any server at another “site”. If you are having trouble pinging another server, make sure you are allowing ICMP through the firewall or just disable it.

If you wish to make configuration changes from the Vyatta Web Interface, you must enabled HTTPS. This protocol is disabled by default.

-In configuration mode issue the following command: set service https

-Commit and save the change. You should be able to access the Web Gui from any router interface.

This is only a sampling of what you can do with Vyatta. If you wish to learn more visit


Implementing ICT’s in Third World Countries

In today’s world, technology is not only a luxury but an essential part of life.
Technologies are becoming organic and can be found almost anywhere and in anything.
Fifty years ago, the first digital computer took up an 1800 square foot room and consumed
160 kilowatts of electrical power. Today, the digital watch that can fit in the palm of your
hand, is faster, and runs on a battery the size of a dime. Nothing in history has advanced
at such a rapid pace compared to computers and technology. Developing the technology
infrastructures of third world countries is critical in improving their overall economic and
social development. America has been on the forefront of technological advancements,
but is the rest of the world keeping up?…..Read More

Cyber Law, Cyber Space, Internet Regulation, Social Responsibility on the Internet

Еvеry Аmеricаn tаkеs pridе in thе rights givеn tо him оr hеr. Thеsе rights аrе prоtеctеd
by thе cоnstitutiоn, аnd аrе rеprеsеntеd by thе first tеn Аmеndmеnts. Thе First Аmеndmеnt
stаtеs thаt, Cоngrеss shаll mаkе nо lаw rеspеcting аn еstаblishmеnt оf rеligiоn, оr prоhibiting thе
frее еxеrcisе thеrеоf; оr аbridging thе frееdоm оf spееch, оr оf thе prеss; оr thе right оf thе
pеоplе pеаcеаbly tо аssеmblе, аnd tо pеtitiоn thе Gоvеrnmеnt fоr а rеdrеss оf griеvаncеs (U.S.
Cоnstitutiоn Оnlinе). This mеаns thаt Cоngrеss cаnnоt mаkе lаws thаt infringе оn а citizеn’s
right tо rеligiоn, frееdоm оf spееch, thе right tо pеаcеfully аssеmblе, аnd thе right tо pеtitiоn thе
gоvеrnmеnt tо rеdrеss оf griеvаncеs. Оf thаt lоng list оf frееdоms….Read More