About Plagiarism

Bismillah . Be balance between Mind, Body & Soul

Taken from : Copy Scape

  The Threat of Plagiarism Plagiarism is a serious and growing problem on the Web. At any moment, anyone in the world can copy your online content and instantly paste it onto their own site. After making minor changes, they will claim your content as their own.

The Web is built on the hard work of honest people who devote their time and energy to creating original content. The global epidemic of content theft violates people's rights and discourages the creation of new web content.

Copyscape was created as a free public service to address this growing problem. The resources below can help you protect your rights online and defend against the threats of plagiarism and content theft.

  Preventing Plagiarism

As with many other things in life, it is best to prevent plagiarism before it happens. This simple Guide to Preventing Plagiarism will help you prevent plagiarism of the content on your site.

  Detecting Plagiarism

It is up to you to find out whether someone has copied your content without permission. Copyscape provides a free service that lets you easily search for plagiarism online and identify instances of content theft. Simply type in the URL of your original content, and Copyscape does the rest. Copyscape also offers professional services for more advanced needs.

  Responding to Plagiarism

If you discover that someone has stolen your content, it is best to act quickly. This practical Guide to Responding To Plagiarism lists some of the actions you can take to track down the perpetrators and ensure that your content is removed from the offending site.

  Understanding Your Rights

The Copyscape Resource Center will help you understand your rights and the laws that regulate online plagiarism. Since copyright laws vary from place to place, the list also includes links to copyright information for different countries.

  Learning from Others

The Copyscape Forum provides a central place to share experiences, post questions and tips, and discuss how best to combat web plagiarism with people who face similar issues around the world.

More information on Copyscape is available here. 



 
In defending your rights online against plagiarists, it's important to be both vigilant and proactive. These four easy steps should help protect your content from being stolen:

1. Place a plagiarism warning banner on each of your pages to deter plagiarists from stealing your work.
2. Include copyright notices on each of your pages to assert ownership over your content (© is © in HTML).
3. Use the automatic Copysentry service to detect and identify illegal copies of your content as they appear.
4. If your content has been copied without permission, take immediate steps to have it removed.

Click here for more information on Copyscape and the terms and conditions of use.

Get a Rush of Visitors with Feedjit Rush

With Feedjit Rush, your website or brand will appear over 2 Million times in front of a geotargeted audience or 6 Million times in front of a global audience of bloggers and blog visitors as fast as our network will allow. Whether it's your big launch day or you need to open the floodgates for a few hours, Rush gives your traffic and your brand an instant boost. 

Rush's cost in CPM terms is 2.5 cents CPM (cost per thousand impressions) for geotargeted ads and 0.82 cents CPM for global ads (that's less than one cent!). We're able to offer this incredible pricing because we are not reselling ad inventory. You will appear on our own media properties including our large network of blogs and websites who use the Feedjit Live Traffic Feed.  

What will my ad look like?

Your ad is completely customizable. You can choose the font family, size and style for each line of text. Your ad will appear in the footer of our Live Traffic Feed. You can see an example on the left of this page. The orange arrow shows where the ad will appear.

How many impressions will I get?

Your geotargeted ad will appear 2 Million times across our network of blogs in the countries you select. Your global ad will appear 6 Million times across our worldwide network of blogs. This usually takes a few hours, depending on the time of day and current traffic levels. Geotargeted ads take longer to run depending on which countries you select.

How many people will click my ad and visit my site?

Click through rate depends on the text in your ad. Performance varies depending on what you are selling, whether it is targeted at blog authors and readers, and how effective the copy in your ad is. We make no gaurantees of click through performance.

What day and time will my ad appear?

Your ad can be scheduled to run as soon as it's approved, which usually takes a few minutes. You can also schedule your ad to run at an exact date and time.

How will I know when my ad goes live and once it's complete?

We will email you the moment your ad goes live and we can send you an optional SMS. We also send you an email and optional SMS once your ad has completed running. Once you've signed up we send you a URL where you can watch your ad impressions and clicks in real-time.

What kind of ads can I post on Feedjit Rush?

Your ad must be family friendly and spam free. We do not allow work from home schemes, adult content and online gambling. We reserve the right to dissaprove certain ads from appearing on our network. If we do not approve

Source: http://feedjit.com/

Perbedaan Web Hosting Dengan Domain

Pengguna Internet pemula sering bingung membedakan web hosting dengan nama domain. Banyak yang mengira untuk memiliki sebuah website cukup dengan memesan nama domain saja atau sebaliknya. Tak jarang hal ini menimbulkan salah paham antara pengguna dengan perusahaan web hosting.

Web hosting berbeda dengan nama domain walaupun keduanya terlihat sebagai satu buah website. Web hosting artinya menyewa disk space di sebuah server web, sedangkan nama domain adalah nama yang didaftarkan disuatu registrar (pendaftar domain) untuk digunakan sebagai sebuah alamat website.

Masih bingung? Kita coba buat analogi sbb:

Web hosting

Analoginya adalah anda menyewa sebuah toko di sebuah lokasi kompleks pertokoan dan anda membayar biaya bulanan/tahunan. Disana anda bisa menempatkan show room, perabotan, barang dagangan, dll.

Nama domain

Analoginya adalah anda mendaftarkan nama perusahaan anda ke Departemen Perdagangan/Kehakiman. Nama perusahaan tersebut tercatat dengan alamat anda perusahaan anda di lokasi pertokoan tersebut. Jadi, web hosting berhubungan dengan lokasi (host), sementara nama domain berhubungan dengan identitas (nama orang, nama perusahaan, merek, brand, dsb.)


Sekian ^_^

How to Debug 'The System cannot Execute the specified program' message.

Here is another unofficial preview of a topic that I am going to send out to you from MSDN. As always, standard disclosure that this post is provided "AS IS" with no warranties, and confer no rights and use of this sample is subject to the terms specified at http://www.microsoft.com/info/cpyright.htm 

Loading C/C++ application may fail if dependent Visual C++ libraries can not be found. In this section the most common reasons for a C/C++ application failing to load are described with proposed steps to resolve the problems.

One of the most common errors messages one may see when dependent Visual C++ DLLs cannot be found is a message box with a text saying “ The system cannot executed the specified program”. Below several things are listed that may help to understand a reason for this error.

1. Dependency walker can show most of dependencies for any particular application or Dll. If you see some of DLLs are missing, please insure that these DLLs are correctly installed on the computer on which you are trying to run your application.
2. Manifest is used by the operating system loader to load assemblies that your applications depend on. It can be either embedded inside the binary as a resource or saved as an external file in the application's local folder. To check whether manifest is embedded inside the binary, open your binary in Visual Studio and browse through resources of this binary. You should be able to find a resource with name RT_MANIFEST. If you cannot find manifest embedded inside the binary, check for external file named something like ..manifest. If manifest is not present, you need to ensure that the linker generates manifest for your project. You need to check linker's option "Generate manifest" in Project Properties dialog for this project.

Note: It is not supported to build VC++ projects without manifest generation. All C/C++ program built in Visual C++ 2005 have to include a manifest describing its dependencies on Visual C++ libraries.

3. If manifest is embedded inside the binary, ensure that ID of RT_MANIFEST is correct for this type of the binary. Such for applications ID should be equal to 1, for most DLLs ID should be equal to 2. If you found this file export it as a file and open in a XML or just a text editor. For more information on manifest and rules for its deployment, see Manifest.
4. Please be aware that on Windows XP, if an external manifest is present in the application's local folder, the operating system loader uses this manifest over a manifest embedded inside the binary. On Windows Server 2003, this works vice versa – external manifest is ignored and embedded manifest is used when present.
5. It is recommended for all DLLs to have a manifest embedded inside the binary. External manifest are ignore when DLL is loaded thought LoadLibrary() call. For information see, Assemblies manifest.
6. Check all assemblies enumerated in the manifest for their correct installation of the computer. Each assembly specified in the manifest by its name, version number and processor architecture. If your application depends on side-by-side assemblies, check that these assemblies are installed on this computer properly, so they can be found by the operating system loader that uses steps specified in Searching sequence while searching for dependent assemblies. Remember that 64bit assemblies cannot be loaded in 32bit process and cannot be executed on 32bit operating system.

Example:

Let's assume we have an application appl.exe built with Visual C++ 2005. This application may have  its manifest either embedded inside appl.exe as a binary resource RT_MANIFEST with ID equal to 1, or store as an external file appl.exe.manifest. The content of a manifest may be something like below:

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

  <dependency>

    <dependentAssembly>

      <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50215.4631" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b">assemblyIdentity>

    dependentAssembly>

  dependency>

assembly>

To the operating system loader this manifest says that appl.exe depends on an assembly named Microsoft.VC80.CRT, version 8.0.50215.4631 and built for 32bit x86 processor architecture.

The dependent side-by-side assembly can be installed as either shared assembly or as private assembly. For example, Visual Studio 2005 installs CRT assembly as a shared side-by-side assembly and it can be found in the directory

C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50215.4631_x-ww_b7acac55  (assuming C:\Windows is the operating system's root directory).

The assembly manifest for a shared Visual C++ CRT assembly is also installed in

C:\WINDOWS\WinSxS\Manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50215.4631_x-ww_b7acac55.manifest

And it identifies this assembly and lists its content (DLLs that are part of this assembly):

xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

      <noInheritable/>

      <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50215.4631" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>

      <file name="msvcr80.dll" hash="3ca5156e8212449db6c622c3d10f37d9adb12c66" hashalg="SHA1"/>

      <file name="msvcp80.dll" hash="92cf8a9bb066aea821d324ca4695c69e55b27cff" hashalg="SHA1"/>

      <file name="msvcm80.dll" hash="7daa93e1195940502491c987ff372190bf199395" hashalg="SHA1"/>

assembly>

Side-by-side assemblies can also use publisher configuration files, also called policy files, to globally redirect applications and assemblies from using one version of a side-by-side assembly to another version of the same assembly. You can check policies for shared Visual C++ CRT assembly in 

C:\WINDOWS\WinSxS\Policies\x86_policy.8.0.Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773\8.0.50215.4631.policy

which content is something like

assembly>

xml version="1.0" encoding="UTF-8" standalone="yes"?>

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

      <assemblyIdentity type="win32-policy" name="policy.8.0.Microsoft.VC80.CRT" version="8.0.50215.4631" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>

      <dependency>

            <dependentAssembly>

                  <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"/>

                  <bindingRedirect oldVersion="8.0.41204.256" newVersion="8.0.50215.4631"/>

            dependentAssembly>

      dependency>

assembly>

The policy above basically specifies that any application or assembly that asks for version 8.0.41204.256 of this assembly should use version 8.0.50215.4631 of this assembly, which is the current version installed on the system. If  a version of the assembly mentioned in the applications manifest is specified in the policy file, the loader looks for a version of this assembly specified in the manifest in the WinSxS folder, and if this version is not installed load fails. And if assembly of version 8.0.50215.4631 is not installed also, load fails for applications that ask for assembly of version 8.0.41204.256.

However CRT assembly can also be installed as a private side-by-side assembly in the applications local folder. If the operating system fails to find CRT or any other assembly as a shared assembly, it starts looking for this assembly as a private assembly. It searches for private assemblies in the following order:

1.    Check the application local folder for a manifest file with name .manifest. In this example, the loader tries to find Microsoft.VC80.CRT.manifest file in the same folder as appl.exe.

a.  If the manifest has been found, the loader loads CRT Dll from the application folder.

b.  If CRT DLL is not found, load fails.

2.     Try to open folder in appl.exe local folder and if it exists, load manifest file .manifest from this folder.

a.  If the manifest has been found, the loader loads CRT DLL from folder.

b.  If CRT DLL is not found, load fails.

See Assembly Searching Sequence for more detailed description on how loader searches for dependent assemblies. If the loader fails to find dependent assembly as a private assembly, load fails and "The system cannot executed the specified program” is display. To resolve this message dependent assemblies and DLLs that are part of them has to be installed on this computer as either private or shared assemblies.