Google Adsense AdLinks

The Google Adsense Search is a much overlooked feature of the Adsense program.
When you register at the the Adsense program, you can choose to serve content bases ads, but also you can select to join Adsense Search.
What Adsense search does is that it gives you the option to place a “Google Search” field on your website, similar to the one below. You can define the look of the search field from within your publisher center, and choose where to display the Google logo, submit button, colours etc.
It is possible for you to “brand” your search result page, by defining the colours used, and even include a logo (50 x 50 px).
A great feature about the Google Adsense Search fields is that you can choose to have the results displayed on a new page, and thereby keeping the visitor on your site.
You can then choose from 2 different types of search :
Google Adsense Search
Google Adsense Site Search

Google Adsense search directs your visitor to a page containing both Adsense ads and search results from Google. This is the type of search listed on the bottom of the navigation bar on this page.
The second type of search, Google Adsense Site Search, searches all recorded pages from your site that is listed in Google’s database. It then shows the user a result page, containing pages from your site that matches the search criteria, as well as search relevant Adsense Ads.
You can track the performance of your search fields, by creating a tracker from your Adsense Publisher center. Any clicks made from the result pages, counts towards your Adsense income.

Removing Unnecessary Programs from Starting Automatically

Many programs add portions of themselves starting automatically on every login.
This can be either in the Startup Folder or the Registry.

One easy way to tell is by looking at how many icons are in your system tray. If you have a large number, perhaps unnecessary resources are being allocated them as well as increasing your boot time.

Typical examples are Microsoft Office, Office FindFast, Real Player, ATI Video setting etc.

You can remove them in one of three main ways:

In the Start / Programs / Startup Folder

In the Registry under HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Run

If you have Win98, WinME or Windows2000 you can use MSCONFIG to easily remove programs. This is my preference since it allows you to toggle them back on again in case you make a mistake

Access Stored User Names and Passwords

The Stored User Names and Passwords applet lets you assign user names and passwords to use when needing to authenticate yourself to services in domains other than the one you are currently logged into. The normal way of running this applet can be difficult to find quickly, so here is a way to launch it using a desktop shortcut using the rundll32.exe program:

——————————————————————————–

Click on START – RUN and type the following (follwed by ENTER):

rundll32.exe keymgr.dll,KRShowKeyMgr

Read Full Story at

Avoiding the Autoclose and Autoshrink Options

Q
In the Microsoft SQL Server 2000 Resource Kit, I read about a procedure that checks all databases for options that you should avoid using. I understand why I should avoid using options such as offline, DBO-use only, statistics off, truncate log on checkpoint, and so on. However, the inclusion of two of the options—autoclose and autoshrink—puzzles me.

Autoclose. Closing a file when it is not in use sounds like a prudent thing to do. Yet I see files opening and closing all the time in the error log in SQL Server, even though I know that I never use the database except for viewing in Enterprise Manager. Does viewing a list of databases in Enterprise Manager make the files open? It makes sense to me to use autoclose on databases that I use only occasionally as import staging areas, and which I access for only a fraction of the time my online transaction processing (OLTP) database is in use. SQL Server Books Online says that the autoclose option is automatically set to YES for the SQL Server Personal Edition and to NO for all other editions. Has this option been included only for the Personal Edition?

Autoshrink. The autoshrink option also sounds helpful. However, would using autoshrink on my import staging areas, where I bring in quantities of data for short periods of time, keep these areas small for backups?

A
Autoclose is available in all editions of SQL Server 2000. The amount of memory you save by using this option is relatively small but might be important on memory-constrained systems running the Personal Edition. However, enabling autoclose for the other editions isn’t a good idea, because every time you try to access the database, the query will be slowed by the amount of load time it takes to mount the database. As for the question about your files opening and closing, yes, when you enumerate a database in Enterprise Manager, you access the database, which opens the files.

Leaving autoshrink on for production systems also isn’t a good practice (unless you really need to), because autoshrink might start when your system is otherwise busy with production work, and slow down the system. However, enabling this option is a good idea for desktop or remote systems that don’t get a lot of DBA attention and whose databases could grow out of control before you detect the problem.

Commands take effect right away.

If you are an experienced Cisco router user, you probably just groaned. However, I find that this concept escapes new users.
As you type commands into the configuration mode, they immediately take effect. For example, if we change the router’s name, we see that the very next line contains the new router name:
Router1#config terminal
Enter configuration commands, one per line. End with CNTL/Z. Router1(config)#hostname MyRouter
MyRouter(config)#^Z
MyRouter#
As you can see, we changed the router’s name to MyRouter, which was immediately processed. This concept applies to everything in the router’s configuration mode.