http://nfl.cpa.delvenetworks.com/delve/player/carousel/embed_code.html?channelId=de89a8aeb3e422bac4eb48567f10ebd0&mediaId=08afc1cc5c4e450fba007f4ae9f9b235
Showing posts with label africa. Show all posts
Showing posts with label africa. Show all posts
WE HAVE MOVED!!!
Monday, April 26, 2010 | 0 comments
In an attenpt to make this Blog easier to navigate and give my readers a greater choice of material without scrolling through older post's, I have gone to another Blog Template, and also changed the URL. I believe the new format is more eye-appealing and easier to read--Soooooooooo---We have moved---Windows Tips and Tricks ( Formerly the Hillbilly Hacker) is now located at Windows tips and Tricks Tips and Tricks as I wish to leave no reader behind, please visit the new site, leave a comment, let me know what I can do to make your visit more enjoyable, ask questions, and remember to subscribe to my feed.
Ehow Vs. Firehow---My Review
Friday, April 23, 2010 | 0 comments
Recently due to the massive changes at ehow, I decided to give Firehow a shot at my articles. Due to the low google Ranking of Firehow compared to ehow, I was concerned about the amount of views I would receive and the structure of pay. Ehow paid me very well on numerous articles I submitted, so I decided to use one or two of these articles--submitted to Firehow as a comparison.
I found submission to Firehow very simple, and with the same "Low Restrictions" that ehow offered. Submission is quick and easy, publishing is a breeze.
One thing I do like about Firehow is there Realtime stats on earnings and views. From the articles I have written and submitted to Firehow, I have noticed that the "earnings" seem to be a penny per 3 views. Today I submitted an article about Social Bookmarking to Increase Traffic, and within an hour it had 32 views reaping me a dime, however, that was in just an hour, and I did not spend a great deal of time writing the article, nor was it one of my finer SEO moments. As far as the views I was concerned about, my other article submitted to Firehow has overtaken the article on ehow, and Associated Content two days running in views. Now, granted, alot of these hits may be fellow members and the view numbers may indeed decrease, this remains to be seen.
Keeping in mind that I have not been with Firehow very long, and their payment structure is just as "Cloudy" as ehows, it does seem that the "Penny per 3 Hits" is holding true with Firehow. Ehow paid very well on many articles that had few hits, and paid little for some articles that had massive hits, which is probably associated with click throughs. If it continues to hold true, I somewhat like a "Payment per View" scenario.
All in All, I am sad that ehow has disbanded the ability to publish through their format and send writers to Demand Studios, for they paid me well. However, if my experience with Firehow continues to be as it is now regarding the earnings (If I am Correct), and the views do hold up, firehow would be a great place for writers who are looking for something comparable to ehow, have been turned down elsewhere, and are looking for a place to Submit and earn money for their articles.
I found submission to Firehow very simple, and with the same "Low Restrictions" that ehow offered. Submission is quick and easy, publishing is a breeze.
One thing I do like about Firehow is there Realtime stats on earnings and views. From the articles I have written and submitted to Firehow, I have noticed that the "earnings" seem to be a penny per 3 views. Today I submitted an article about Social Bookmarking to Increase Traffic, and within an hour it had 32 views reaping me a dime, however, that was in just an hour, and I did not spend a great deal of time writing the article, nor was it one of my finer SEO moments. As far as the views I was concerned about, my other article submitted to Firehow has overtaken the article on ehow, and Associated Content two days running in views. Now, granted, alot of these hits may be fellow members and the view numbers may indeed decrease, this remains to be seen.
Keeping in mind that I have not been with Firehow very long, and their payment structure is just as "Cloudy" as ehows, it does seem that the "Penny per 3 Hits" is holding true with Firehow. Ehow paid very well on many articles that had few hits, and paid little for some articles that had massive hits, which is probably associated with click throughs. If it continues to hold true, I somewhat like a "Payment per View" scenario.
All in All, I am sad that ehow has disbanded the ability to publish through their format and send writers to Demand Studios, for they paid me well. However, if my experience with Firehow continues to be as it is now regarding the earnings (If I am Correct), and the views do hold up, firehow would be a great place for writers who are looking for something comparable to ehow, have been turned down elsewhere, and are looking for a place to Submit and earn money for their articles.
Microsoft Tries to Avoid Windows Blue Screen Repeat
Wednesday, April 14, 2010 | 0 comments
Microsoft took steps Tuesday to avoid repeating the debacle two months ago that left Windows XP users staring at the notorious "Blue Screen of Death" error message after they applied a patch.
In February, a security update that fixed two flaws in the Windows kernel -- the operating system's most important component -- wreaked havoc when it was applied by users, who almost immediately flooded Microsoft 's support forum with reports of crippled computers .
As the number of reports grew, Microsoft first stopped automatically serving the MS10-015 update, then confirmed that a rootkit caused the crashes . Only PCs that had been previously infected with the Alureon rootkit were incapacitated, Microsoft's investigation found.
Microsoft restarted distribution of the update only after it had come up with a way to block rootkit-infected PCs from receiving the patches. "If detection logic included in Automatic Update discovers abnormal conditions in certain operating system file configurations, the update will fail and customers will be presented with an error message that offers alternative support options," said Jerry Bryant, general manager with the Microsoft Security Response Team, in early March.
MS10-021 , one of the 11 updates issued yesterday as part of Microsoft's monthly Patch Tuesday cycle , also fixed flaws in the Windows kernel. But Microsoft is hoping that this month's update won't trigger a repeat Blue Screen of Death.
"This security update includes package detection logic that prevents the installation of the security update if certain abnormal conditions exist on 32-bit systems," stated the MS10-021 bulletin. "These abnormal conditions on a system could be the result of an infection with a computer virus that modifies some operating system files, which renders the infected computer incompatible with the kernel update."
One security expert applauded the move.
"I give Microsoft a big tip of the hat for not taking [the February incident] as a one-off," said Jason Miller, data and security team manager at network compliance and security vendor Shavlik Technologies. "The kernel is something that if something goes bad, that's not good. Patching the kernel is not like patching a media player."
Microsoft obviously learned a lesson. Even though the February update crashed a relatively small number of PCs, the problem actually affected many more, he argued. "It may have affected just a few people, but it scared almost everyone into not patching," Miller said.
Although scattered reports of problems with Tuesday's security updates have been posted on Microsoft's support forum, Computerworld did not find any message threads describing Blue Screen of Death crashes after users applied yesterday's MS10-021 kernel update.
Enterprises should still test the update before widely deploying it, Miller recommended. "With every kernel patch, you really have to test. We're pretty adamant about that," he said.
Microsoft also urged users to apply MS10-021 to protect themselves. Although attacks had not been found in the wild exploiting any of the eight vulnerabilities addressed by the update, the company noted that users would "likely...see reliable exploit code developed for one or more of these eight vulnerabilities" in the next 30 days.
This month's security update, including MS10-021, can be downloaded and installed via the Windows Update and Microsoft Update services, as well as through Windows Server Update Services.
Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld . Follow Gregg on Twitter at @gkeizer or subscribe to Gregg's RSS feed . His e-mail address is gkeizer@ix.netcom.com .
In February, a security update that fixed two flaws in the Windows kernel -- the operating system's most important component -- wreaked havoc when it was applied by users, who almost immediately flooded Microsoft 's support forum with reports of crippled computers .
As the number of reports grew, Microsoft first stopped automatically serving the MS10-015 update, then confirmed that a rootkit caused the crashes . Only PCs that had been previously infected with the Alureon rootkit were incapacitated, Microsoft's investigation found.
Microsoft restarted distribution of the update only after it had come up with a way to block rootkit-infected PCs from receiving the patches. "If detection logic included in Automatic Update discovers abnormal conditions in certain operating system file configurations, the update will fail and customers will be presented with an error message that offers alternative support options," said Jerry Bryant, general manager with the Microsoft Security Response Team, in early March.
MS10-021 , one of the 11 updates issued yesterday as part of Microsoft's monthly Patch Tuesday cycle , also fixed flaws in the Windows kernel. But Microsoft is hoping that this month's update won't trigger a repeat Blue Screen of Death.
"This security update includes package detection logic that prevents the installation of the security update if certain abnormal conditions exist on 32-bit systems," stated the MS10-021 bulletin. "These abnormal conditions on a system could be the result of an infection with a computer virus that modifies some operating system files, which renders the infected computer incompatible with the kernel update."
One security expert applauded the move.
"I give Microsoft a big tip of the hat for not taking [the February incident] as a one-off," said Jason Miller, data and security team manager at network compliance and security vendor Shavlik Technologies. "The kernel is something that if something goes bad, that's not good. Patching the kernel is not like patching a media player."
Microsoft obviously learned a lesson. Even though the February update crashed a relatively small number of PCs, the problem actually affected many more, he argued. "It may have affected just a few people, but it scared almost everyone into not patching," Miller said.
Although scattered reports of problems with Tuesday's security updates have been posted on Microsoft's support forum, Computerworld did not find any message threads describing Blue Screen of Death crashes after users applied yesterday's MS10-021 kernel update.
Enterprises should still test the update before widely deploying it, Miller recommended. "With every kernel patch, you really have to test. We're pretty adamant about that," he said.
Microsoft also urged users to apply MS10-021 to protect themselves. Although attacks had not been found in the wild exploiting any of the eight vulnerabilities addressed by the update, the company noted that users would "likely...see reliable exploit code developed for one or more of these eight vulnerabilities" in the next 30 days.
This month's security update, including MS10-021, can be downloaded and installed via the Windows Update and Microsoft Update services, as well as through Windows Server Update Services.
Gregg Keizer covers Microsoft, security issues, Apple, Web browsers and general technology breaking news for Computerworld . Follow Gregg on Twitter at @gkeizer or subscribe to Gregg's RSS feed . His e-mail address is gkeizer@ix.netcom.com .
Subscribe to:
Posts (Atom)
Posts
