Demo = http://techsupportbase.net63.net/wordpress/?wptheme=Greeny
Download = http://techsupportbase.net63.net/wordpress/wp-content/uploads/2011/08/Greeny.zip
My Projects
Demo = http://techsupportbase.net63.net/wordpress/?wptheme=Greeny
Download = http://techsupportbase.net63.net/wordpress/wp-content/uploads/2011/08/Greeny.zip
Sporty Blue theme
Fine out more about the themes functions and click the pic.


I write this guide about two weeks ago, but I Delayed the publication of this guide, because of pyxf86config bug, which cause following livna-config-display errors on boot:
Checking for module nvidia.ko: [ OK ]
Enabling the nvidia driver: Traceback (most recent call last):
File “/usr/sbin/nvidia-config-display”, line 28, in
import livnaConfigDisplay.ConfigDisplay
File “/usr/lib/python2.7/site-packages/livnaConfigDisplay/ConfigDisplay.py”, line 29, in
import xf86config
File “/usr/lib/python2.7/site-packages/xf86config.py”, line 1, in
import ixf86config
ImportError: /usr/lib/python2.7/site-packages/ixf86configmodule.so: undefined symbol: xstrtokenize
[FAILED]
But now, on my own testing and others testing, everything seems to work well with pyxf86config and livna-config-display when pyxf86config bug has been fixed.
This guide works with GeForce 6/7/8/9/200/300 series cards and also with GeForce FX cards.
su - ## OR ## sudo -i
If not then update kernel and reboot
yum update kernel* reboot
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm rpm -Uvh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
Select kmod, kmod-PAE or akmod from following.
kmod-nvidia
yum install kmod-nvidia xorg-x11-drv-nvidia-libs
or
kmod-nvidia-PAE kernel
yum install kmod-nvidia-PAE
or
akmod-nvidia
yum install akmod-nvidia xorg-x11-drv-nvidia-libs
kmod works fine for most people, but it doesn’t work on systems with different kernel
Full spec of kmod and akmod differences, check this.
Select kmod, kmod-PAE or akmod from following.
kmod-nvidia and kmod-nvidia-PAE
yum --enablerepo=rpmfusion-nonfree-updates-testing install kmod-nvidia-173xx xorg-x11-drv-nvidia-173xx-libs.i686
or
kmod-nvidia-PAE kernel
yum --enablerepo=rpmfusion-nonfree-updates-testing install kmod-nvidia-173xx-PAE
or
akmod-nvidia
yum --enablerepo=rpmfusion-nonfree-updates-testing install akmod-nvidia-173xx xorg-x11-drv-nvidia-173xx-libs.i686
kmod works fine for most people, but it doesn’t work on systems with different kernel
Full spec of kmod and akmod differences, check this.
This should not be necessary, but I recommend this, because of pyxf86config bug.
Open /etc/X11/xorg.conf file and check following rows:
32-bit
Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
EndSection
64-bit
Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules"
EndSection
If section files is missing then it have to be added manually.
This should not be necessary, but missing rdblacklist=nouveau nouveau.modeset=0 is the most common reason which causes black screen / blank screen on boot with nVidia drivers. So it’s good to check followin also. 😉
Open /boot/grub/grub.conf file and check that the kernel row have following rdblacklist=nouveau nouveau.modeset=0:
title Fedora (2.6.35.6-48.fc14.i686)
root (hd0,0)
kernel /vmlinuz-2.6.35.6-48.fc14.i686 .... rdblacklist=nouveau nouveau.modeset=0
initrd /initramfs-2.6.35.6-48.fc14.i686.img
reboot
Please let me know if you have some problems with nVidia drivers installation. You could also tell you if you got the drivers installed using this guide and what graphics card you have?
This is guide, howto install nVidia proprietary drivers on Fedora 14 and disable Nouveau driver. I write this guide about two weeks ago, but I Delayed the publication of this guide, because of pyxf86config bug, which cause following livna-config-display errors on boot:
Checking for module nvidia.ko: [ OK ]
Enabling the nvidia driver: Traceback (most recent call last):
File “/usr/sbin/nvidia-config-display”, line 28, in
import livnaConfigDisplay.ConfigDisplay
File “/usr/lib/python2.7/site-packages/livnaConfigDisplay/ConfigDisplay.py”, line 29, in
import xf86config
File “/usr/lib/python2.7/site-packages/xf86config.py”, line 1, in
import ixf86config
ImportError: /usr/lib/python2.7/site-packages/ixf86configmodule.so: undefined symbol: xstrtokenize
[FAILED]
But now, on my own testing and others testing, everything seems to work well with pyxf86config and livna-config-display when pyxf86config bug has been fixed.
This guide works with GeForce 6/7/8/9/200/300 series cards and also with GeForce FX cards.
su - ## OR ## sudo -i
If not then update kernel and reboot
yum update kernel* reboot
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm rpm -Uvh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
Select kmod, kmod-PAE or akmod from following.
kmod-nvidia
yum install kmod-nvidia xorg-x11-drv-nvidia-libs
or
kmod-nvidia-PAE kernel
yum install kmod-nvidia-PAE
or
akmod-nvidia
yum install akmod-nvidia xorg-x11-drv-nvidia-libs
kmod works fine for most people, but it doesn’t work on systems with different kernel
Full spec of kmod and akmod differences, check this.
Select kmod, kmod-PAE or akmod from following.
kmod-nvidia and kmod-nvidia-PAE
yum --enablerepo=rpmfusion-nonfree-updates-testing install kmod-nvidia-173xx xorg-x11-drv-nvidia-173xx-libs.i686
or
kmod-nvidia-PAE kernel
yum --enablerepo=rpmfusion-nonfree-updates-testing install kmod-nvidia-173xx-PAE
or
akmod-nvidia
yum --enablerepo=rpmfusion-nonfree-updates-testing install akmod-nvidia-173xx xorg-x11-drv-nvidia-173xx-libs.i686
kmod works fine for most people, but it doesn’t work on systems with different kernel
Full spec of kmod and akmod differences, check this.
This should not be necessary, but I recommend this, because of pyxf86config bug.
Open /etc/X11/xorg.conf file and check following rows:
32-bit
Section "Files"
ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib/xorg/modules"
EndSection
64-bit
Section "Files"
ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
ModulePath "/usr/lib64/xorg/modules"
EndSection
If section files is missing then it have to be added manually.
This should not be necessary, but missing rdblacklist=nouveau nouveau.modeset=0 is the most common reason which causes black screen / blank screen on boot with nVidia drivers. So it’s good to check followin also. 😉
Open /boot/grub/grub.conf file and check that the kernel row have following rdblacklist=nouveau nouveau.modeset=0:
title Fedora (2.6.35.6-48.fc14.i686)
root (hd0,0)
kernel /vmlinuz-2.6.35.6-48.fc14.i686 .... rdblacklist=nouveau nouveau.modeset=0
initrd /initramfs-2.6.35.6-48.fc14.i686.img
reboot
Please let me know if you have some problems with nVidia drivers installation. You could also tell you if you got the drivers installed using this guide and what graphics card you have?
While upgrading via PackageKit is coming, there’s a pretty decent way of doing it with PreUpgrade.
First, update your current system:
yum update
Install preupgrade:
yum install preupgrade
Run the preupgrade tool, and follow the prompts (remote upgrades over VNC also supported):
preupgrade
PreUpgrade will prompt to reboot your computer and will update your system automatically. All of your packages should be updated and your repositories configured for you (I also had RPMFusion, Chromium and yum-rawhide which all updated as expected). On one of my systems, even the NVIDIA driver was automatically updated and configured. Now you’re booted into your new Fedora 14 system.
OK, this is where things get a little tricky. Some packages might be no-longer supported, there might be removed dependencies and the like. So, there are two neat commands that we will use to identify these packages, so that you can remove them.
package-cleanup --orphans
package-cleanup --leaves
But wait.. I discovered that there’s a more important step to do first, or you’ll cause yourself a headache!
On my machine, this wanted to remove some pretty important packages, like kdelibs.
[username@shem ~]$ sudo package-cleanup --orphans
[sudo] password for username:
Loaded plugins: refresh-packagekit, remove-with-leaves
akonadi-1.4.0-3.fc13.x86_64
kdeedu-marble-4.5.2-2.fc13.x86_64
kdeedu-marble-libs-4.5.2-2.fc13.x86_64
kdelibs-4.5.2-8.fc13.x86_64
kdelibs-common-4.5.2-8.fc13.x86_64
schroedinger-1.0.10-1.fc13.x86_64
xorg-x11-drv-wacom-0.10.8-2.fc13.x86_64
Fedora (unlike certain other distros I know) provides major updates to the latest versions of packages (like OpenOffice.org, KDE, GNOME, etc). Yay! It’s possible that your new Fedora system is running the same version of, say KDE, as your old one. This was indeed the case with my Fedora 13 to 14 upgrade (both run KDE 4.5.2 at time of F14 release).
Actually, the build of some important packages on Fedora 13 (like kdelibs-4.5.2-8.fc13.x86_64) were actually more recent than on the newer Fedora 14 system (kdelibs-4.5.2-5.fc14.x86_64).
The package-cleanup tool correctly lists kdelibs-4.5.2-8.fc13.x86_64 as being an orphan and if you were to remove this, you’d break your system badly. In fact, if you’re running yum’s brilliant new autoremove deps feature, as I am, you’ll lose most of your system. It makes sense – you are telling yum to remove kdelibs, so it goes and removes everything that relies on it! Yikes.
So first, we need to fix this by running the yum distro-sync command which recognises that we need to downgrade that kdelibs packages (and not remove it!).
[chris@shem ~]$ sudo yum distro-sync
Loaded plugins: refresh-packagekit, remove-with-leaves
Setting up Distribution Synchronization Process
Resolving Dependencies
--> Running transaction check
---> Package akonadi.x86_64 0:1.4.0-1.fc14 will be a downgrade
---> Package akonadi.x86_64 0:1.4.0-3.fc13 will be erased
---> Package kdeedu-marble.x86_64 0:4.5.2-1.fc14 will be a downgrade
---> Package kdeedu-marble.x86_64 0:4.5.2-2.fc13 will be erased
---> Package kdeedu-marble-libs.x86_64 0:4.5.2-1.fc14 will be a downgrade
---> Package kdeedu-marble-libs.x86_64 0:4.5.2-2.fc13 will be erased
---> Package kdelibs.x86_64 6:4.5.2-5.fc14 will be a downgrade
---> Package kdelibs.x86_64 6:4.5.2-8.fc13 will be erased
---> Package kdelibs-common.x86_64 6:4.5.2-5.fc14 will be a downgrade
---> Package kdelibs-common.x86_64 6:4.5.2-8.fc13 will be erased
---> Package schroedinger.x86_64 0:1.0.9-2.fc14 will be a downgrade
---> Package schroedinger.x86_64 0:1.0.10-1.fc13 will be erased
---> Package xorg-x11-drv-wacom.x86_64 0:0.10.8-1.20100726.fc14 will be a downgrade
---> Package xorg-x11-drv-wacom.x86_64 0:0.10.8-2.fc13 will be erased
--> Finished Dependency Resolution
--> Finding unneeded leftover dependencies
Found and removing 0 unneeded dependencies
----
Dependencies Resolved
=================================================
Package Arch Version Repository Size
=================================================
Downgrading:
akonadi x86_64 1.4.0-1.fc14 fedora 677 k
kdeedu-marble x86_64 4.5.2-1.fc14 fedora 14 M
kdeedu-marble-libs x86_64 4.5.2-1.fc14 fedora 902 k
kdelibs x86_64 6:4.5.2-5.fc14 fedora 12 M
kdelibs-common x86_64 6:4.5.2-5.fc14 fedora 1.7 M
schroedinger x86_64 1.0.9-2.fc14 fedora 276 k
xorg-x11-drv-wacom x86_64 0.10.8-1.20100726.fc14 fedora 73 k
---
Transaction Summary
=================================================
Downgrade 7 Package(s)
---
Total download size: 30 M
Is this ok [y/N]
Once we downgrade these packages, we can then remove any other orphans we might have, with package-cleanup –leaves and package-cleanup –orphans (I didn’t have any). One last thing to note – Fedora will not replace packages from the newer release if they are exactly the same version. For this reason, you will probably have some F13 packages still installed on your computer – don’t worry, that’s correct. They will be upgraded in time (if required).
So, now I think I know how to successfully upgrade the system without breaking it
If anyone has some other tips or corrections, please let me know! Hope that’s helpful.

Here’s an article for beginners in the practice of CSS Layouts, my reason for writing this one came from remembering the difficulty I once had position elements in CSS. After many frustrating attempts with relative and absolute position techniques I finally found the holy grail of CSS the “Float” attribute!
Ok so I’ve started to design my web site and have learnt how to position things using the position: relative and position: absolute; heres some examples of these below:

This works well, for basic positioning, but when your layouts become a little more complex as they always tend to do, tyring to position div’s within div’s using this method can become a real struggle.
Troubles can start when elements positioned as absolute can often position themselves to the entire page as apposed to the containing div, which can sometimes become a real nightmare.
Other simple tasks such as creating multiple divs in-line with each other for navigations etc can also involve many un-nessisary left right positioning values. So save yourself the trouble and crack open a can red bull and give yourself some wings!
The float attribute allows you to position objects to either the left or right of your page
tag, for example using the following section of code creates a page with two boxes one on the left hand side the other on the right.

Now this is the cool thing about Float, unlike the other positioning attributes it makes it so easy to position elements right next to each other. For example if your wanted to create a navigation menu that spanned left to right with say 5 different boxes, the Float attribute makes this so simple.
When you create a floated div tag using the following code: float: left;providing it fits into the length of the page it will position this flush with the side of a previous floated element, see below.

If you then wanted to start your next element below this new set of navigation boxes, simply add the “clear” setting to the next tag followed by the side setting of the previous float tag, the example above also shows how this set of elements was started on a newline using the clear: left; setting.
float: left; clear: left;
Also using the following setting on your element will drop it onto the next line underneith any left or right floated elements:
float: left; clear: both;
Float: center; does not exist
Don’t ask me why this has never been added to the CSS library but it is easily fixed, if you want to center a div within a float tag simply create a div without the use of the float attribute and use the following margin settings:
</div>
Margin auto does not work in IE?: Yes another IE related bug but heres the fix, for Internet Explorer you will also need to add the following to your CSS for this centering to work.
html, body {
text-align: center;
}
Float inside a Float
When adding a div tag with the float attribute within another div try to remember that the preceeding tag must also have the float attribute applied to it. Think of this tip as a fix for when you float something and it dosent seem to take effect on your layout.
</div>
FARBGEL is looking to incorporate a new class of clients: the wholesale range, (Police, NHS, Defence Clubs, Youth centres, Gay and Bisexual centres, ETC. website and looking at incorporating:
Enhancing performance, by sending out email campaigns and contacting clients on many levels (phone, mail, in person).
DEVELOPING THE WEBSITE
The project is to develop a high level website which holds a product called FARBGE. The website needs a complete remake (GUI, Content, and structure). New clients can view and contact Farbgel about wholesaling the product in which the company supplies, in which is the main focus. Creating; a fully functional, commercial, and accessible environment. Includes in summary:
But first, I’d like to introduce you to Dan Floersch of BleedingBaseball.com.
We selected Dan’s question on the blog post “What is Your Biggest Challenge?” and we’re providing a more detailed answer that you can also use.
He sells a baseball trivia book and says his biggest challenge is finding his target audience online.
Here are our 10 most effective targeting strategies in a blueprint customized for Dan’s needs.
However, these strategies will work for any business-so as you read this blueprint, think about how you can make these strategies work for you.
Targeting Tip 1: Just Say No to Lists
“Should I be accessing baseball related e-mail lists?” Dan asked us.
Our answer is an unqualified “No.”
They’re too expensive and there’s little chance that people who have never heard of you will respond to an unasked-for email from you. On top of that, you run the risk of getting slammed with spam complaints.
Targeting Tip 2: Grow a List of Keywords Using the Google Keyword Tool
Everyone who is trying to reach an audience online should know about the Google Keyword Tool.
This handy free tool allows you to explore the exact words and phrases people are typing into Google when searching for information. Be sure to look for “long-tail” keywords that clearly represent people who are interested in what you offer but don’t have a lot of competition.
Dan, we plugged these five keyword phrases into the Google Keyword Tool:
· baseball trivia
· baseball quizzes
· baseball facts
· baseball book
· baseball history
… and we came up with a list of 124 associated keywords, many of which would be perfect for you to use in your SEO and paid search efforts. Here are some particularly good ones for you
to start out with:
Keyword
Global Monthly Searches
Approximate CPC
(Google Adwords)
If you were to successfully target just these twelve keywords, you would be able to put your product in front of 18,790 people who you’re probably not reaching right now-and that’s huge.
You can grow this list huge by adding team-specific, league-specific, and player-specific keywords as well, such as “Babe Ruth trivia,” “Boston Red Sox trivia,” and so forth.
A good keyword list should have at least 100 keywords on it.
Targeting Tip #3: Run Google AdWords ads
Google AdWords is the fastest way to get your product in front of people who are actively searching for what you offer.
Start by experimenting with the keywords in the list above. Make sure your ads lead directly to landing pages that give searchers exactly what they’re looking for–preferably in the form of a compelling downloadable freebie.
For example, if you’re going to run an ad targeting the keyword, “baseball trivia questions,” link to a page that offers a free eBook titled something like, “49 baseball trivia questions that even the most die-hard fans can’t answer.”
Targeting Tip #4: Run Facebook Ads
Did you know you can create Facebook ads that target people based on the interests on their personal profile?
This means you can use Facebook ads to promote your downloadable freebie only to people who have identified themselves as baseball fans. It’s a great way to grow your fan base!
To save money on your ads, make sure they point to a custom tab on your Facebook Page rather than to your website.
Targeting Tip #5: Become Active on Facebook Pages/Groups Related to Your Interest
Dan, simply enter “baseball” into the search bar at the top of Facebook and start looking for pages to like and groups to join.
Use your “Bleeding Baseball” account to interact on the pages you like but don’t overtly promote your book-instead make interesting comments that make people want to engage with you. If they feel like they know you personally, they’ll be more interested in your book.
Targeting Tip #6: Become Active on Industry-Specific Forums and Blogs
To find forums and blogs that appeal to your target market, go to Google and do a search on terms such as “baseball + forum,” “baseball + blog,” and “baseball trivia + blog”
Be sure to offer fun and helpful comments on the forums and blogs you like best. Take the time to listen and give people what they really want. Then be sure to link back to your site via your post signature.
Targeting Tip #7: Find Your Audience on Twitter
Go to Twitter and do searches to identify people who are interested in baseball. Follow them and chances are good they’ll follow you back, if they see you offer fun baseball-related tidbits of information instead of a constant barrage of promotional messages.
When people follow you, send them a personal message thanking them. Relate to them on a personal level and they will be more likely to be interested in buying your book.
Targeting Tip #8: Write Short Articles and Post them on Popular Sites
Dan, this should be easy for you as you have a whole book full of interesting content to work with.
Create a series of short 400-700 word articles and approach the owners of popular baseball blogs and websites to see if they would be interested in publishing your article. Make sure you include a link back to your site in your “About the Author” blurb. This is a great way to introduce yourself to a larger audience.
Targeting Tip #9: Grow Your Site Content with a Blog
Dan, I see you don’t have a blog on your site. I would put that on your “to-do” list right away. Having a blog is a great way to grow a site full of valuable content that’s optimized for your best keywords, so it appeals to the search engines as well as your human visitors. Plus, it’s a great way to encourage repeat visits.
Targeting Tip #10: Include an Opt-in on Every Page of Your Site
Dan, your site visitors are some of the most targeted people you can find-and yet you’re not making any effort to stay in touch with them if they don’t immediately buy your book.
Studies show it takes a minimum of 6-7 points of contact for someone to be comfortable enough to make a purchase online. We recommend you help your visitors over that hump by encouraging them to sign up for your downloadable freebie and then using email to grow a strong relationship with them over time.
Bonus Tip: Use Email to Close the Deal
At strategic times of the year-the beginning of the baseball season, Father’s Day, the end of the regular season, the final series of the World Series, and Christmas-promote your book to your mailing list. Give them an exclusive subscriber’s discount and you’d be surprised at how many of them will take you up on your offer!
I hope these strategies have given you a better idea of how to reach your audience online and convert them into buyers. If you have any questions, let me know.
All the best,
Posted from WordPress for Android
While SEOs can provide clients with valuable services, some unethical SEOs have given the industry a black eye through their overly aggressive marketing efforts and their attempts to manipulate search engine results in unfair ways. Practices that violate our guidelines may result in a negative adjustment of your site’s presence in Google, or even the removal of your site from our index. Here are some things to consider:
“Dear techsupportbase.net,
I visited your website and noticed that you are not listed in most of the major search engines and directories…”
Reserve the same skepticism for unsolicited email about search engines as you do for “burn fat at night” diet pills or requests to help transfer funds from deposed dictators.
If you feel that you were deceived by an SEO in some way, you may want to report it.
In the United States, the Federal Trade Commission (FTC) handles complaints about deceptive or unfair business practices. To file a complaint, visit: http://www.ftc.gov/ and click on “File a Complaint Online,” call 1-877-FTC-HELP, or write to:
Federal Trade Commission
CRC-240
Washington, D.C. 20580
If your complaint is against a company in a country other than the United States, please file it at http://www.econsumer.gov/.