23 Ways To Speed WinXP, Not only Defrag

Since defragging the disk won’t do much to improve Windows XP performance, here are 23 suggestions that will. Each can enhance the performance and reliability of your customers’ PCs. Best of all, most of them will cost you nothing.

1.) To decrease a system’s boot time and increase system performance, use the money you save by not buying defragmentation software — the built-in Windows defragmenter works just fine — and instead equip the computer with an Ultra-133 or Serial ATA hard drive with 8-MB cache buffer.

 

2.) If a PC has less than 512 MB of RAM, add more memory. This is a relatively inexpensive and easy upgrade that can dramatically improve system performance.

 

3.) Ensure that Windows XP is utilizing the NTFS file system. If you’re not sure, here’s how to check: First, double-click the My Computer icon, right-click on the C: Drive, then select Properties. Next, examine the File System type; if it says FAT32, then back-up any important data. Next, click Start, click Run, type CMD, and then click OK. At the prompt, type CONVERT C: /FS:NTFS and press the Enter key. This process may take a while; it’s important that the computer be uninterrupted and virus-free. The file system used by the bootable drive will be either FAT32 or NTFS. I highly recommend NTFS for its superior security, reliability, and efficiency with larger disk drives.

 

4.) Disable file indexing. The indexing service extracts information from documents and other files on the hard drive and creates a “searchable keyword index.” As you can imagine, this process can be quite taxing on any system.

 

The idea is that the user can search for a word, phrase, or property inside a document, should they have hundreds or thousands of documents and not know the file name of the document they want. Windows XP’s built-in search functionality can still perform these kinds of searches without the Indexing service. It just takes longer. The OS has to open each file at the time of the request to help find what the user is looking for.

 

Most people never need this feature of search. Those who do are typically in a large corporate environment where thousands of documents are located on at least one server. But if you’re a typical system builder, most of your clients are small and medium businesses. And if your clients have no need for this search feature, I recommend disabling it.

 

Here’s how: First, double-click the My Computer icon. Next, right-click on the C: Drive, then select Properties. Uncheck “Allow Indexing Service to index this disk for fast file searching.” Next, apply changes to “C: subfolders and files,” and click OK. If a warning or error message appears (such as “Access is denied”), click the Ignore All button.

 

5.) Update the PC’s video and motherboard chipset drivers. Also, update and configure the BIOS. For more information on how to configure your BIOS properly, see this article on my site.

 

6.) Empty the Windows Prefetch folder every three months or so. Windows XP can “prefetch” portions of data and applications that are used frequently. This makes processes appear to load faster when called upon by the user. That’s fine. But over time, the prefetch folder may become overloaded with references to files and applications no longer in use. When that happens, Windows XP is wasting time, and slowing system performance, by pre-loading them. Nothing critical is in this folder, and the entire contents are safe to delete.

 

7.) Once a month, run a disk cleanup. Here’s how: Double-click the My Computer icon. Then right-click on the C: drive and select Properties. Click the Disk Cleanup button — it’s just to the right of the Capacity pie graph — and delete all temporary files.

 

8.) In your Device Manager, double-click on the IDE ATA/ATAPI Controllers device, and ensure that DMA is enabled for each drive you have connected to the Primary and Secondary controller. Do this by double-clicking on Primary IDE Channel. Then click the Advanced Settings tab. Ensure the Transfer Mode is set to “DMA if available” for both Device 0 and Device 1. Then repeat this process with the Secondary IDE Channel.

 

9.) Upgrade the cabling. As hard-drive technology improves, the cabling requirements to achieve these performance boosts have become more stringent. Be sure to use 80-wire Ultra-133 cables on all of your IDE devices with the connectors properly assigned to the matching Master/Slave/Motherboard sockets. A single device must be at the end of the cable; connecting a single drive to the middle connector on a ribbon cable will cause signaling problems. With Ultra DMA hard drives, these signaling problems will prevent the drive from performing at its maximum potential. Also, because these cables inherently support “cable select,” the location of each drive on the cable is important. For these reasons, the cable is designed so drive positioning is explicitly clear.

 

10.) Remove all spyware from the computer. Use free programs such as AdAware by Lavasoft or SpyBot Search & Destroy. Once these programs are installed, be sure to check for and download any updates before starting your search. Anything either program finds can be safely removed. Any free software that requires spyware to run will no longer function once the spyware portion has been removed; if your customer really wants the program even though it contains spyware, simply reinstall it. For more information on removing Spyware visit this Web Pro News page.

 

11.) Remove any unnecessary programs and/or items from Windows Startup routine using the MSCONFIG utility. Here’s how: First, click Start, click Run, type MSCONFIG, and click OK. Click the StartUp tab, then uncheck any items you don’t want to start when Windows starts. Unsure what some items are? Visit the WinTasks Process Library. It contains known system processes, applications, as well as spyware references and explanations. Or quickly identify them by searching for the filenames using Google or another Web search engine.

 

12.) Remove any unnecessary or unused programs from the Add/Remove Programs section of the Control Panel.

 

13.) Turn off any and all unnecessary animations, and disable active desktop. In fact, for optimal performance, turn off all animations. Windows XP offers many different settings in this area. Here’s how to do it: First click on the System icon in the Control Panel. Next, click on the Advanced tab. Select the Settings button located under Performance. Feel free to play around with the options offered here, as nothing you can change will alter the reliability of the computer — only its responsiveness.

 

14.) If your customer is an advanced user who is comfortable editing their registry, try some of the performance registry tweaks offered at Tweak XP.

 

15.) Visit Microsoft’s Windows update site regularly, and download all updates labeled Critical. Download any optional updates at your discretion.

 

16.) Update the customer’s anti-virus software on a weekly, even daily, basis. Make sure they have only one anti-virus software package installed. Mixing anti-virus software is a sure way to spell disaster for performance and reliability.

 

17.) Make sure the customer has fewer than 500 type fonts installed on their computer. The more fonts they have, the slower the system will become. While Windows XP handles fonts much more efficiently than did the previous versions of Windows, too many fonts — that is, anything over 500 — will noticeably tax the system.

 

18.) Do not partition the hard drive. Windows XP’s NTFS file system runs more efficiently on one large partition. The data is no safer on a separate partition, and a reformat is never necessary to reinstall an operating system. The same excuses people offer for using partitions apply to using a folder instead. For example, instead of putting all your data on the D: drive, put it in a folder called “D drive.” You’ll achieve the same organizational benefits that a separate partition offers, but without the degradation in system performance. Also, your free space won’t be limited by the size of the partition; instead, it will be limited by the size of the entire hard drive. This means you won’t need to resize any partitions, ever. That task can be time-consuming and also can result in lost data.

 

19.) Check the system’s RAM to ensure it is operating properly. I recommend using a free program called MemTest86. The download will make a bootable CD or diskette (your choice), which will run 10 extensive tests on the PC’s memory automatically after you boot to the disk you created. Allow all tests to run until at least three passes of the 10 tests are completed. If the program encounters any errors, turn off and unplug the computer, remove a stick of memory (assuming you have more than one), and run the test again. Remember, bad memory cannot be repaired, but only replaced.

 

20.) If the PC has a CD or DVD recorder, check the drive manufacturer’s Web site for updated firmware. In some cases you’ll be able to upgrade the recorder to a faster speed. Best of all, it’s free.

 

21.) Disable unnecessary services. Windows XP loads a lot of services that your customer most likely does not need. To determine which services you can disable for your client, visit the Black Viper site for Windows XP configurations.

 

22.) If you’re sick of a single Windows Explorer window crashing and then taking the rest of your OS down with it, then follow this tip: open My Computer, click on Tools, then Folder Options. Now click on the View tab. Scroll down to “Launch folder windows in a separate process,” and enable this option. You’ll have to reboot your machine for this option to take effect.

 

23.) At least once a year, open the computer’s cases and blow out all the dust and debris. While you’re in there, check that all the fans are turning properly. Also inspect the motherboard capacitors for bulging or leaks. For more information on this leaking-capacitor phenomena, you can read numerous articles on my site.

 

 

Following any of these suggestions should result in noticeable improvements to the performance and reliability of your customers’ computers. If you still want to defrag a disk, remember that the main benefit will be to make your data more retrievable in the event of a crashed drive.

 

www.BangaloreOrbit.com

Oline Portal for Bangalore and Karnataka People                                                               n

Tourist Destination | Pilgrims Destination | News | Forum | Games | Jobs | Groups |

Taste of Kannada | Bangalore Darshan | Latest Event |

Tagged : / / / /

How to create a subscribe form for your rss feed

create-a-subscribe-form-for

 

Create a subscribe form for your rss feed

 

Joomla Website with K2 Content

 

RSS To email using mailchimp

 

RSS To email using hubspot

 

RSS to email using phplist

 

Feed Burner
Tagged : / / / /

How to build when a change is pushed to Bitbucket

bitbucket-tutorials

 

Bitbucket plugin is designed to offer integration between Bitbucket and Jenkins.

 

It exposes a single URI endpoint that you can add as a WebHook within each Bitbucket project you wish to integrate with. This single endpoint receives a full data payload from Bitbucket upon push (see their documentation), triggering compatible jobs to build based on changed repository/branch.

 

Step 1 – Install “Bitbucket Plugin” at your Jenkins

 

Step 2 – Add a normal Post as Hook to your Bitbucket repository (Settings -> Hooks) and use following url:

 

https://YOUR.JENKINS.SERVER:PORT/bitbucket-hook/
and if you have setup authentication on jenkins then URL must be like

 

https://USERNAME:PASSWORD@YOUR.JENKINS.SERVER:PORT/bitbucket-hook/

 

Step 3 – Configure your Jenkins project as follows:

 

Step 4 – Under build trigger enable Build when a change is pushed to BitBucket

 

Step 5 – under Source Code Management select GIT; enter your credentials and define Branches to build (like **feature/*)

 

Note 1 – Make sure to include the slash (‘/’) on the end of the URL or the hook won’t work.

 

Note 2 – Please read the BitBucket Plugin info page as well https://wiki.jenkins.io/display/JENKINS/BitBucket+Plugin

 

Reference 1  
Reference 2 – Login issues with Jenkins url
Tagged : / / / / / /

How to configure Sonatype Nexus repository with Maven?

configure-sonatype-nexus-repository-with-maven

How to configure Sonatype Nexus repository with Maven?

 

Automatic dependencies is one of the powerful feature of Apache maven and its one of the reason Maven is very popular in developer community. Maven resolve the dependent library from local repository which is again connected with central repository or remote repository. thus we can say that Maven has 3 kinds of repository concept.

 

1. Local repostory e.g $USER_HOME/.m2
2. Central repostory e.g http://repo.maven.apache.org/maven2/
3. Private repostory e.g Sonatype Nexus, Artifactory, Archiva etc.
The diagram shown below represent how maven resolve the dependendency.

 
High Level Interaction between Local Repository, Central Repository and Remote Repository.


Dependency Management using Local Repository, Central Repository and Remote Repository.

This is How maven interact with Repository!


This is a diagram which shows the define flow in which maven try to resolve the dependency.

 

Now, We have understood that Central rrepository is in built but next questions is, How to inform the maven about the location of remote repository? In order to configure maven with remote repostory, in our case SonaType Nexus, we need to configuring host machine setting.xml and projects pom.xml to use your Nexus repos.

 

Put this in your ~/.m2/settings.xml file. This will configure the credentials to publish to your hosted repos, and will tell your mvn to use your repo as a mirror of central:

And now configure your projects.

If you want only to download dependencies from Nexus, put this in the pom.xml:

and

Add the following at the end of setting.xml

<activeProfiles>

    <!–make the profile active all the time –>

    <activeProfile>nexus</activeProfile>

  </activeProfiles>

 

Reference

https://maven.apache.org/guides/mini/guide-mirror-settings.html

Tagged : / / / / /

How can we do the security analysis using SonarQube?

security-analysis-using-sonarqube

How can we do the Security analysis using SonarQube?

For Security analysis purposes, a source code security analyzer
– examines source code to
– detect and report weaknesses that can lead to security vulnerabilities.

 

They are one of the last lines of defense to eliminate software vulnerabilities during development or after deployment. A Source Code Security Analysis Tool Functional Specification is available.

 

The SonarQube Quality Model has three different types of rules: Reliability (bug), Vulnerability (security), and Maintainability (code smell) rules. But divided another way, there are only two types: security rules, and all the rest.

 

To be clear, the standard for most rules implemented in SonarQube language plugins is very strict: no false positives. For normal rules, you should be able to be confident that whatever is reported to you as an issue really is an issue.

 

The vast majority of security-related rules originate from established standards: CWE, SANS Top 25, and OWASP Top 10. To find rules that relate to any of these standards, you can search rules either by tag or by text.

 

CWE – Common Weakness Enumeration (CWE™) is a formal list or dictionary of common software weaknesses that can occur in software’s architecture, design, code or implementation that can lead to exploitable security vulnerabilities.

 

SANS Top 25 – The SANS Top 25 list is a collection of the 25-most dangerous errors listed in the CWE, as compiled by the SANS organization.

 

OWASP Top 10 – OWASP stands for Open Web Application Security Project.The OWASP Top 10 is a list of broad categories of weaknesses, each of which can map to many individual rules.

 

XANITIZER – XANITIZER provides an integration with the code quality management platform SonarQube. It transfers all security relevant XANITIZER findings to SonarQube. It is possible to display this data in the SonarQube dashboard and the corresponding drilldown pages and time machines.

 

Reference
Tagged : / / / /

SonarQube Upgrade, Backup and Restore Process | SonarQube Tutorial

sonarqube-upgrade-backup-and-restore-process

 

SonarQube Upgrade, Backup and Restore Process

 

Today I will share the steps to upgrade from the SonarQube version 5.X to SonarQube version 6.X. We have upgrade guide which can be found http://docs.sonarqube.org/display/SONAR/Upgrading but its not complete guide thus I am sharing the steps as follows which can be followed for the production server as well.  As practice shared on the oficial guide that before upgrading to the next major release, you must upgrade to know LTS e.g
Example 1 : 4.2 -> 6.1, migration path is 4.2 -> 4.5.7 LTS -> 5.6 LTS -> 6.1
Example 2 : 5.1 -> 5.6, migration path is 5.1 -> 5.6

 

Upgrading across multiple versions is handled automatically. However, if in your migration path you have an LTS version, you must first migrate to this LTS and then migrate to your target version.

 

Remember that SonarQube upgrade procedure does not have a rollback procedure, so it is mandatory that you take a full backup of the system before performing the upgrade.

 

Process 1: Steps to Take a Full Backup of SonarQube Server?

Step 1 – Stop the production server
Windows
%SONARQUBE_HOME%/bin/windows-x86-32/StopNTService.bat
Linux
$SONAR_HOME/bin/linux-x86-64/sonar.sh stop
Step 2 – Backup the production database e.g mysql db
> mysqldump –opt -Q -h localhost -u username–password=’password’ databasename | gzip -9 > databasename.gz
Also, there is one tool which has been available to take the backup of database.
Step 3 – Backup the $SONAR_HOME directory
> zip -r Sonar_home.zip $SONAR_HOME
Step 4 – List of plugins installed
Be mindful that $SONAR_HOME/extensions/plugins directory where you can get the list of plugins installed.
Step 5 – List of custom coding rules installed
Be mindful that $SONAR_HOME/extensions/rules directory where you can get the list of custom coding rules.
Step 6 – List of configurations used
Be mindful that $SONAR_HOME/config directory where you can get sonar.properties and wrapper.conf file which has all the current configurations and setup.
Step 7 – Re-start the production server
Windows
%SONARQUBE_HOME%/bin/windows-x86-32/StartSonar.bat
Linux
$SONAR_HOME/bin/linux-x86-64/sonar.sh start
Step 8: Keep the Sonar_home.zip and databasename.gz to the safe location.

 

Process 2: SonarQube server Upgrade process.

Following are the steps to be followed to upgrade the SonarQube server.
Step 1: Stop your old SonarQube Server.
Step 2: Install/Configure a most latest version of SonarQube 
Install/Configure a most latest version of SonarQube Server in another location. The instructions is shared here (https://docs.sonarqube.org/display/SONAR/Installing+the+Server)
Step 3: Install the your required plugins/extensions compatible with your version of SonarQube. The Instructions is shared here.(https://docs.sonarqube.org/display/SONAR/Installing+a+Plugin)
Step 4: Update the contents of sonar.properties and wrapper.conf files (in NEW_SONARQUBE_HOME/conf) with the settings of the related files in the OLD_SONARQUBE_HOME/conf directory (web server URL, database, ldap settings, etc.). Do not copy-paste the old files.
If you are using the Oracle DB, copy its JDBC driver into NEW_SONARQUBE_HOME/extensions/jdbc-driver/oracle
Step 5: Start your new SonarQube Server
Windows
%SONARQUBE_HOME%/bin/windows-x86-32/StartSonar.bat
Linux
$SONAR_HOME/bin/linux-x86-64/sonar.sh start
Step 7: Verify the SonarQube Upgrade.

 

Note – SonarQube as a Linux or Windows Service
If you use external configuration, such as a script or Windows Service to control your server, you’ll need to update it to point to NEW_SONARQUBE_HOME.
In case you used the InstallNTService.bat to install SonarQube as a Windows Service, run the OLD_SONARQUBE_HOME/bin/…/UninstallNTService.bat before running the InstallNTService.bat of the NEW_SONARQUBE_HOME.
If you install SonarQube with Sql Server, it is better to chose Latin1_General_CS_AS as collation to avoid problems.

 

Some Well known Troubleshooting after upgrades.
Issues – Sonarqube upgrade 5.6 to 6.1, test coverage measue is missing
Solution – You might be missing the sonar.java.binaries. Sonar-5.6 did not need those.
Issues – Some unknown issues
Solution – Whenever you have problem with SonarQube do not forget to read the log, because only in the log you can understand the real cause of errors.

 

Reference
Tagged : / / / / / / /

Chef Internal – How Chef maintain the state of each resources internally?

chef-internal

Chef Client

A chef-client is an agent that runs locally on every node that is under management by Chef. The chef-client executable can be run as a daemon. When a chef-client is run, it will perform all of the steps that are required to bring the node into the expected state, including:

  • Registering and authenticating the node with the Chef server
  • Building the node object
  • Synchronizing cookbooks
  • Compiling the resource collection by loading each of the required cookbooks, including recipes, attributes, and all other dependencies
  • Taking the appropriate and required actions to configure the node
  • Looking for exceptions and notifications, handling each as required

RSA public key-pairs are used to authenticate the chef-client with the Chef server every time a chef-client needs access to data that is stored on the Chef server. This prevents any node from accessing data that it shouldn’t and it ensures that only nodes that are properly registered with the Chef server can be managed.

Ohai

 

Ohai is a tool that is used to collect system configuration data, which is provided to the chef-client for use within cookbooks. Ohai is run by the chef-client at the beginning of every Chef run to determine system state. Ohai includes many built-in plugins to detect common configuration details as well as a plugin model for writing custom plugins.

The types of attributes Ohai collects include but are not limited to:

  • Operating System
  • Network
  • Memory
  • Disk
  • CPU
  • Kernel
  • Host names
  • Fully qualified domain names
  • Virtualization
  • Cloud provider metadata

Attributes that are collected by Ohai are automatic level attributes, in that these attributes are used by the chef-client to ensure that these attributes remain unchanged after the chef-client is done configuring the node.

Ohai collects data for many platforms, including AIX, Darwin, Linux, FreeBSD, OpenBSD, NetBSD, Solaris, and any Microsoft Windows operating systems.

Reference
https://docs.chef.io/chef_client.html

Tagged : / / / / / /

Tasksel – Easily/Quickly Install Group Softwares in Debian and Ubuntu

tasksel-easily-quickly-install-group-softwares-in-debian-and-ubuntu
Tasksel – Easily/Quickly Install Group Softwares in Debian and Ubuntu
If you started out using an RPM-based distro before advancements like “yum” or “apt-rpm”, you’re loving the magic of “apt-get” on Ubuntu and Debian. But when it comes to installing large sets of software, which may have either dozens (if not hundreds) of packages, or those that require a good deal of integration, sometimes “apt-get” can feel like the old rpm -i guessing game. Fortunately, there’s a “tasksel” – think of it as “apt-get for apt-get”.
How To Install and Use Tasksel in Debian and Ubuntu
To install tasksel, simply run the command below:
$ sudo apt-get install tasksel
After installing Tasksel, it enables you to install one or more predefined group of packages. User need to run it from the command line with a few arguments, it provides a graphical user interface as well where one can select software to install.
The general syntax of running tasksel from the command line is:
$ sudo tasksel install task_name
$ sudo tasksel remove task_name
$ sudo tasksel command_line_options
$ sudo tasksel –list-tasks
$ sudo tasksel install openssh-server
To start the tasksel user interface, issue the command below:
$ sudo tasksel
Tasksel vs. Apt-Get
You may ask yourself why you’d want to use tasksel versus the traditional apt-get command to install software, especially when there’s an equivalent meta-package. It’s easiest to think of it like this:
On one hand, apt-get installs software as individual packages, even if those packages require others. In other words, it will install each package and respect dependencies, but otherwise assume all of them are separate.
In contrast, tasksel assumes you’re trying to install software towards a singular end-goal, such as a web server. It will take all the steps necessary to achieve that goal, including installing software as well as doing other configuration once the install is done. Getting a web server running is a good example… you might need to install apache, mysql, php, and a number of modules and add-on’s for each in order to get a proper LAMP stack running. Or you could just issue the following command:
$ sudo tasksel install lamp-server
Here are some other useful tasks available from tasksel:
Installed Ubuntu, but want to try out the latest KDE Software Collection? Just use this:
$ sudo tasksel install kubuntu-desktop
Have a computer you’d like to hook up to your home theater PC? It’s as easy as:
$ sudo tasksel install mythbuntu-frontend
Need a GUI for your server, but don’t want to waste precious resources on something like KDE or Unity?
$ sudo tasksel install lubuntu-core
Reference
Tagged : / / / / / / /

How to Start and Stop Nagios Core | Nagios Tutorial

starting-and-stopping-nagios-core
Starting Nagios Core
Init Script: The easiest way to start the Nagios Core daemon is by using the init script like so:
/etc/rc.d/init.d/nagios start
Manually: You can start the Nagios daemon manually with the -d command line option like so:
/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
Restarting Nagios Core
Restarting/reloading is nececessary when you modify your configuration files and want those changes to take effect.
Init Script: The easiest way to restart the Nagios Core daemon is by using the init script like so:
/etc/rc.d/init.d/nagios reload
Web Interface: You can restart the Nagios Core through the web interface by clicking the “Process Info” navigation link and selecting “Restart the Nagios process”:
Manually: You can restart the Nagios Core process by sending it a SIGHUP signal like so:
kill -HUP <nagios_pid>
Stopping Nagios Core
Init Script: The easiest way to stop the Nagios Core daemon is by using the init script like so:
/etc/rc.d/init.d/nagios stop
Web Interface: You can stop the Nagios Core through the web interface by clicking the “Process Info” navigation link and selecting “Shutdown the Nagios process”:
Manually: You can stop the Nagios Core process by sending it a SIGTERM signal like so:
kill <nagios_pid>
Tagged : / / / / / / / / / / / /

Steps to Start-Stop Nagios XI Server | Nagios XI Tutorial

Steps to Start-Stop Nagios XI Server

How to start and stop Naxios XI Server?

How to stop Naxios XI Server?

service nagiosxi stop

service npcd stop

service ndo2db stop

service nagios stop

service postgresql stop

service mysqld stop

service httpd stop

How to start Naxios XI Server?

service httpd start

service mysqld start

service postgresql start

service nagios start

service ndo2db start

service npcd start

service nagiosxi start

Tagged : / / / / / / / / / / / / /