TWEAK: Performance Tip -- Exclude from AV Scan

When you have been using Windows-based computers long enough you will notice that performance degrades over time. There are a lot of causes to this and disk fragmentation is one of them. But little do users know that what contributes a lot to the degradation is the presence of the anti-virus. Add fragmentation to the mix and the performance decline worsens.

For an average user, however, running without an anti-virus is synonymous with suicide. The performance hit that's a consequence of the anti-virus is more acceptable than having to re-install the OS and recover the files. Anti-virus are created to behave with paranoia as the foremost consideration. And it will be very paranoid -- it will scan every file accessed; it will scan memory; it will scan as you boot; it will scan even when you're not doing anything!

Not everything that is in your computer can be infected by a virus. So it is wise to make your anti-virus a little bit smarter than it was programmed to be. What does this mean? It means, exclude files you know to be safe from being scanned. Plain text files are perfect candidates for this. Anything that is text-based (and don't automatically execute) are generally safe. Their extensions are .txt, .log and the like.

Aside from text-based files, multimedia files like mp3, avi, mp4 and mkv are generally safe, especially if they came from trusted sources. It is wise then to make the anti-virus skip them. Also, the anti-virus is not that friendly with Windows page file. It scans that too! Your computer system can perform better if that file is skipped from being scanned.

McAfee. With McAfee, this configuration is in the VirusScan Console under Tasks > On Access Scanner Properties.

Click on "All Processes" and get to the "Exclusions" tab. There is an Exclusions button that will allow you to control the behavior of the On-Access Scanner module.

ESET NOD32. With NOD32, this configuration can be set by pressing "F5" thus opening the Advanced Configuration menu.

Then go to Computer > Antivirus and antispyware > Real-time file system protection. Click on the Setup button and include all file system extensions.

For directory exclusions, go to Computer > Antivirus and antispyware > Exclusions and put the paths to be excluded from on access scans.

I get good performance from my computer when I set it up this way. There is always a drawing of lines between security and functionality. In the end, what matters is for you have to have your say in the matter.

Read More

FAQ: clock_gettime Error Compiling Xymon Client

"There’s No Such Thing As A Silly Question" -- does the cliche sound familiar? In this part of pimp-my-rig reloaded, technical questions are answered. Mail them to me and I will post the answers here. If you have a better answer, by all means share it with us.

Q. I recently received an email from a previous colleague asking for help regarding errors in compiling XYmon client on a machine running Fedora 13. Yes, the host is a bit old but since the application running is mission critical downtime is not acceptable and putting it under the microscope with a xymon client is a well-thought move.

To give you a better picture of the error, here are a few lines of the xymon client compile, after running "make -s".

(other lines snipped for brevity)
...
timefunc.c: In function âtimespec_textâ:
timefunc.c:140: warning: pointer targets in assignment differ in signedness
timefunc.c:187: warning: pointer targets in passing argument 2 of âaddtobufferâ differ in signedness
/var/tmp/xymon-4.3.7/include/../lib/strfunc.h:16: note: expected âchar *â but argument is of type âunsigned char *â
../lib/xymonclient.a(timefunc-client.o): In function `getntimer':
/var/tmp/xymon-4.3.7/lib/timefunc.c:67: undefined reference to `clock_gettime'
../lib/xymonclient.a(timefunc-client.o): In function `gettimer':
/var/tmp/xymon-4.3.7/lib/timefunc.c:55: undefined reference to `clock_gettime'
collect2: ld returned 1 exit statustfc
make[1]: *** [../client/xymon] Error 1
make: *** [common-client] Error 2

So as you can see, the error is fatal and compilation will not complete successfully. I have been through this error before and made notes of the things done to resolve.

A. Xymon was built to take into account regular expressions on things being monitored -- log files, directory sizes, etc, etc. These files can be monitored by classes and/or pattern matches that can be defined by regular expressions. And for xymon to function properly, the pcre-devel (PERL Compatible Regular Expressions) rpm has to be installed.

So install pcre-devel via yum.

[root@host /var/tmp] yum -y install pcre-devel
Loaded plugins: fastestmirror, presto, refresh-packagekit
Loading mirror speeds from cached hostfile
 * fedora: mirror.cse.iitk.ac.in
 * updates: mirror.cse.iitk.ac.in
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package pcre-devel.i686 0:7.8-3.fc12 set to be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                   Arch         Version             Repository     Size
================================================================================
Installing:
 pcre-devel                i686         7.8-3.fc12          fedora        278 k

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 278 k
Installed size: 0.9 M
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 278 k
(1/1): pcre-devel-7.8-3.fc12.i686.rpm                    | 278 kB     00:02     
--------------------------------------------------------------------------------
Total                                           271 kB/s | 278 kB     00:02     

Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : pcre-devel-7.8-3.fc12.i686 [###########################] 1/1

Installed:
  pcre-devel.i686 0:7.8-3.fc12

Complete!

Once pcre-devel is installed, xymon client will compile with a few warnings that can be ignored. Do a "make install" after compile completes. Run the xymon client via "/home/xymon/client/runclient.sh start". The path /home/xymon is the path chosen when running "./configure.client" (or "./configure -client").

This step is optional, but I found that it solves some issues with other versions of Fedora/RedHat based systems. Before running ./configure, define the environment variable LIBRTDEF. Do it with command "export LIBRTDEF=-lrt"

In running xymon client, pcre-devel is more often than not a major dependency. So better install it before doing the compile.

Read More

HOW-TO: Determine if the SSD Supports TRIM

The gigantic technological leap SSD offered than conventional hard drives is nothing compared to the upgrade gap between a next generation processor or video card. It is bounds and leaps greater. Since its introduction over a year ago, SSDs have always been the talk of the town when it comes to raw performance.

This technology is, however, dependent on another technology that has to be supported by the operating system -- TRIM. Trim is the difference that makes conventional storage manage data better than SSDs. When data is written to a "virgin" cell of an SSD, it is a straight write but if the cell to be written has old junk (deleted data) the undergoing process is a read-modify-write. Imagine a heavily fragmented drive when a delete is performed, performance would suffer. And this questions the long-term performance of the SSD.

Windows 7 is where trim got introduced. The trim command reorganizes data to be written and also deletes junk data existing on the NAND cell. It scrubs junked data when a delete is performed so that when a write command is subsequently performed on a NAND cell, it is always "already" clean.

How then do you determine if your drive supports TRIM? You can use the software CrystalDiskInfo to determine and ensure that the SSD supports trim. Download the software from its webpage. I used the portable zipped version of the software.

This is how CrystalDiskInfo looks like (refer to screenshot).

As seen from the screenshot, the OCZ Vertex3 60GB SSD supports the TRIM feature. You may then tweak the OS to take advantage of the trim feature on the SSD.

On Windows 7, the command to use is "fsutil.exe behavior set DisableDeleteNotify 0". The feedback will be "DisableDeleteNotify = 0" (as seen below).

If your SSD supports TRIM, better make use of it so long term performance of your SSD will not suffer. Windows 7 supports trim, so might as well make it the default operating system. Here's a guide to migrate from the conventional drive to the SSD.

Read More

HOW-TO: Upgrade to SSD (the Faster Easier Way)

Guides from the net abound with procedures and guides on upgrading from a conventional hard drive to a faster and better SSD. The procedures involve creating a backup image of Windows 7 and restoring that same backup image to the SSD. Like many, I have tried to follow this procedure and it does not always end well. The backup image creation is the easy part but the restore does not always succeed. On my part, the backup image on the USB drive could not be restored to the SSD.

The only other alternative is to do a complete install of Windows 7 and this is even worse than the above procedure. That's what I thought too, until I recently found an easier way of doing things, and even better -- the tool to use is FREE!

The tool or software I'm referring to is the Aomei Partition Assistant (download here). You can download the Home Edition and it will work for your desktop or notebook. As of this writing, the latest version available is version 4.0.

Download the Aomei Partition Assistant and install it. No reboot required.

This guide was done using my notebook (Dell Latitude D630) so I connected the SSD to the notebook via a USB to SATA adapter. On a desktop, things are a bit simpler by just installing the SSD on a vacant SATA port.

Launch the application, then click on the system/boot drive. On a conventional install, the boot drive should have two (2) partitions. The reserved partition (usually 100MB in size) and the system partition (where Windows 7 is installed).

Click on the "reserved" (or System Reserved) partition and click on Copy Partition. A similar window like below is opened. Copy to the "Unallocated" drive which pertains to the SSD. Do the same for the system partition. You may opt to resize the system partition to fit the SSD. Then "Apply" the change.

You will be prompted to reboot. And before the operating system boots, the PreOS mode of Aomei kicks in to copy the partitions. Once done the computer will reboot. At this point, you can intervene and shutdown the computer to unplug the hard drive and replace it with the SSD.

I followed the same procedure outlined above. And I could feel the difference of the upgrade. Aomei Partition Assistant has made my upgrade easy, straight-forward and hassle-free.

This procedure can also be used to upgrade to a bigger faster drive or to a RAID volume, not just an SSD.

Read More

TWEAK: AHCI Plugin for BartPE

I was back to playing around with BartPE in order to sysprep-clone laptop drives with Windows 7. At first, I got stuck with the BOOTMGR is missing error but I knew I got stuck in this before and got to recall the solution I did.

The next error I faced was the dreaded blue screen of death (BSOD) with stop code 0x0000007B. I knew this was because of the AHCI mode of the SATA drives on the new generation intel chipsets on the laptop. I didn't want to go to WinPE 2.x or the Windows 7 based PE since it is difficult to dissect the innards of the .wim files, and I have working plugins for BartPE.

So I decided to create my own AHCI plugin. I downloaded the floppy image of the drivers from the intel download page. NOTE: Make sure to download the floppy image (filename starts with: f6flpy).

Extract the files inside the floppy image. Only two (2) files are required, namely iastor.inf and iastor.sys. Create a directory named iaahci inside the PEbuilder plug-in directory and copy the files there under directory files. Rename them to iaAHCI.inf and iaAHCI.sys respectively so they will not conflict with other intel RAID drivers.

If your PEBuilder directory is C:\PEBuilder, you should have the files iaahci.inf and iaahci.sys under C:\PEBuilder\plugin\iaahci\files. Open a command prompt (as Administrator) and compress iaAHCI.sys via makecab.

Copy the code below and save as a .inf file under C:\PEBuilder\plugin\iaahci directory. If copy-paste doesn't work for you, you can try to copy the code here: http://pastie.org/3437076.

; PE Builder v3 plug-in INF file
; - plugin for intel mobile ahci drivers
; - by tox (http://www.pimp-my-rig.com)
;

[Version]
Signature="$Windows NT$"

[PEBuilder]
Name="Intel (Mobile) AHCI Drivers"
Enable=1

[SourceDisksFiles]
files\iaAHCI.sy_=4
files\iaAHCI.inf=20

[SetValue]
"txtsetup.sif","SourceDisksFiles","iaAHCI.SY_", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","SourceDisksFiles","iaAHCI.inf", "1,,,,,,,20,0,0"
;(format)HardwareIdsDatabase -- "txtsetup.sif","HardWareIdsDatabase","SCSI\NVIDIA__Raid_Disk_20_____", """nvrd327r"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_27C1&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_27C5&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_2922&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_2929&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_3A02&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_3A22&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_3B29&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_3B2F&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_3B22&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_1C02&CC_0106", """iaAHCI"""
"txtsetup.sif","HardWareIdsDatabase","PCI\VEN_8086&DEV_1C03&CC_0106", """iaAHCI"""
;(format)SCSI.Load -- "txtsetup.sif","SCSI.Load","ql2200", "ql2200.SY_,4"
"txtsetup.sif","SCSI.Load","iaAHCI", "iaAHCI.SY_,4"
;(format)SCSI -- "txtsetup.sif","SCSI","rr2644", """HighPoint RocketRAID 2644x4 SAS"""
"txtsetup.sif","SCSI","iaAHCI", """Intel(R) Mobile Express Chipset SATA AHCI Controller"""

Now try rebuilding BartPE and use it on the laptop of your choice to sysprep the image. You can also use the built BartPE to rescue broken systems.

AHCI was the culprit of my BSOD and having the plugin above I was able to boot into a Windows XP based PE environment to do the cloning.

Read More