Snippet tool untuk Win XP

Bagi anda pengguna windows vista, 7 atau 8 tentu akan menyukai memiliki dan memakai tool bawaan windows Snippet tool. Karena dengan tool kecil bericon gunting ini kita bisa mengambil/capture apapun yang ada di layar monitor kita dan menyimpanya dalam bentuk file jpg yang extra kecil, tanpa mengurangi kualitas gambar tersebut. Namun bagaimana bila kita masih suka memakai windows xp yang tidak memiliki fitur tool ini ... maka setelah mencari dan melihat hasil dari beberapa tool saya lebih menyukai tool bernama Capture screenshoot Lite yang memiliki icon dan cara kerja hampir sama dengan yang di windows vista/7/8.

OK Langsung aja untuk mendapatkan tool tersebut tinggal download di link ini.

Bila tidak bisa mendownload di link tersebut silakan googling dengan keyword "Capture screenshoot Lite".Tool ini seperti tool kecil lainya tinggal install dan setelah di jalankan dia akan running di systray meskipun udah di close dengan pemakaian memory sekitar 27Mb, jadi ketika membutuhkanya tinggal double klikicon tool gunting tersebut di systray kita.

Dan tinggal buat kotak crop di layar kita sesuai gambar yang ingin di simpan, dan tekan Ctr-C dan Ctrl-V di mana kita ingin memakai gambar tersebut atau klik tombol simpan untuk menyimpan gambar tersebut.

Cara menambahkan header and footer untuk halaman spesifik

Biasanya kalo kita pakai Header atau footer maka dia akan muncul di setiap halaman di word kita, nah di artikel ini diajarkan cara membuat header / footer untuk spesific halaman tertentu, atau cuma untuk beberapa halaman saja.

1. Buat header/footer di halaman pertama yang kita inginkan, hal ini akan membuat semua halaman memiliki header dan footer yang sama secara otomatis.

2. Contoh header / footer yang dibuat.

3. Untuk mengatur supaya header berikutnya berbeda dengan yang sudah ada maka klik Page Layout tab dan pilih breaks -->Next Page

4. Hal ini akan membuat duplikasi halaman dengan template seperti halaman sebelumnya tapi akan ditandai sebagai section berikutnya (section baru).

5. Double click pada header dari halaman yang baru dan anda akan bisa liat bahwa header / footer section sebelumnya adalah section 1 dan yang baru adalah section 2.

6. klik tab Design contextual tab (Green) dan un-toggle tombol Link to Previous .

7. Setelah unklik tombol Link to previous maka word tidak akan menyamakan header dan footer halaman berikutnya dengan yang sebelumnya.

PLC Preventative Maintenance Checklist

Setting up a routine maintenance schedule will increase the longevity of your Programmable Logic Controllers (PLCs) and minimize the chance of system malfunction. Your schedule for PLC preventative maintenance will depend on the controller’s environment - the harsher the environment the more frequent maintenance will be needed.
 
We recommend the following practices at least quarterly to keep your system in good operating condition:
•    Backup PLC Program – Save a copy of your PLC program during routine maintenance to ensure a fairly up-to-date backup. In the event a PLC becomes inoperable and has to be replaced, this backup file can be downloaded onto a new PLC.
•    Check LED Indicators – Check the power and battery LED indicators. If the power LED indicator is off or flickering or if the battery LED indicator is on or flickering this may be a preliminary sign of a low battery or potential power issues. 
•    Replace the Battery – If the Battery OK light is flickering or on, it is time to change the battery.  Avoid catastrophic problems if you were to lose main control power by changing the battery regularly – it easy – watch these videos to learn more.
•    Check Operating Environment – Check temperature, humidity and other environmental factors to make sure that your PLC is operating within the proper conditions.  Also make sure there is good airflow in the cabinet by cleaning filters in the enclosure.
•    Check Operating Voltage – Check the input voltage that is powering your PLC to make sure that the voltage is within the appropriate range and free from power spikes or ‘brown out’ conditions.
•    Check Program Functionality – During routine maintenance, check the functionality to make sure the system or equipment that is being controlled is operating as intended.
•    Look For Indications Of Overheated Components – Check the CPU and modules for distorted, warped, or discolored cases and burnt odors.
•    Clear Dust And Check Venting – Do not allow dirt and dust to accumulate on the PLC’s components. The central processing unit and I/O system are not designed to be dust proof. Check to be sure none of the PLC and module cooling vents are clogged or blocked by dust or debris. Make sure that there is sufficient heat dissipation space around the PLC. If heat dissipation is obstructed, circuit malfunction can occur and if conductive dust reaches the electronic boards, it can cause a short circuit, resulting in possible permanent damage to the circuit board.
•    Inspect Batter Status – Check battery and replace if necessary.
•    Check Connections – Make sure that all communication cables, plugs, sockets, terminal strips, wiring and modules are connected properly. If your PLC system is located in an area that experiences constant vibrations that could possible loosen terminal connections, perform this check more often and consider installing a vibration detector.
•    Identify Updates Needed – Check for any product notices, patches and upgrades and update as necessary.
•    Remove Unnecessary Items – Keep any items such as drawings, installation manuals or other materials away from the PLC system. Leaving these items on top of the CPU rack or other enclosures can obstruct airflow and create hot spots, ultimately causing a system malfunction.
•    Audit Parts In Use – Conduct an audit to check each component of your PLC system and determine if parts are good or need replacement.
•    Take Inventory Of Replacement Parts – Keep a stock of replacement parts on hand to minimize downtime resulting from component failure. Having the right spare in stock during a failure situation can result in shutdown for only minutes instead of hours or days.

Source : http://blog.qualitrol.com/blog/plc-preventative-maintenance-checklist

Translated by Google : 



Menyiapkan jadwal pemeliharaan rutin akan meningkatkan umur panjang Programmable Logic Controller Anda (PLC) dan meminimalkan kemungkinan kerusakan sistem. Jadwal Anda untuk PLC perawatan pencegahan akan tergantung pada lingkungan controller - keras lingkungan yang pemeliharaan lebih sering akan dibutuhkan.
 
Kami merekomendasikan praktek-praktek berikut setidaknya tiga bulan untuk menjaga sistem Anda dalam kondisi operasi yang baik:
 
• Backup PLC Program - Menyimpan salinan program PLC Anda selama pemeliharaan rutin untuk memastikan cadangan yang cukup up-to-date. Dalam hal PLC yang menjadi dioperasi dan telah diganti, file cadangan ini dapat didownload ke PLC baru.
• Periksa Indikator LED - Periksa daya dan baterai LED indikator. Jika indikator daya LED mati atau berkedip-kedip atau jika indikator baterai LED menyala atau berkedip ini mungkin merupakan tanda awal dari baterai rendah atau masalah listrik yang potensial.
• Ganti Baterai - Jika OK Lampu baterai berkedip atau, sekarang saatnya untuk mengganti baterai. Menghindari masalah bencana jika Anda kehilangan daya kontrol utama dengan mengubah baterai secara teratur - mudah - menonton video ini untuk mempelajari lebih lanjut.
• Periksa Lingkungan Operasi - Periksa suhu, kelembaban dan faktor lingkungan lain untuk memastikan bahwa PLC Anda beroperasi dalam kondisi yang tepat. Juga pastikan ada aliran udara yang baik di kabinet dengan membersihkan filter di kandang.
• Periksa Tegangan Operasi - Periksa tegangan input yang powering PLC Anda untuk memastikan bahwa tegangan berada dalam kisaran yang tepat dan bebas dari lonjakan listrik atau 'cokelat keluar' kondisi.
• Periksa Fungsi Program - Selama perawatan rutin, memeriksa fungsi untuk memastikan sistem atau peralatan yang dikendalikan beroperasi sebagaimana dimaksud.
• Diperhatikan Indikasi Of Kepanasan Komponen - Periksa CPU dan modul untuk terdistorsi, melengkung, atau kasus berubah warna dan bau terbakar.
• Hapus Debu Dan Periksa Terbuang - Jangan biarkan kotoran dan debu yang menumpuk pada komponen PLC. The central processing unit dan I / O sistem tidak dirancang untuk menjadi bukti debu. Periksa untuk memastikan tidak ada PLC dan modul ventilasi pendingin tersumbat atau terhalang oleh debu atau kotoran. Pastikan bahwa ada ruang pembuangan panas yang cukup di sekitar PLC. Jika disipasi panas terhambat, sirkuit kerusakan dapat terjadi dan jika debu konduktif mencapai papan elektronik, dapat menyebabkan korsleting, sehingga kemungkinan kerusakan permanen pada papan sirkuit.
• Periksa Adonan Status - Periksa baterai dan ganti jika perlu.
• Periksa Koneksi - Pastikan bahwa semua kabel komunikasi, colokan, soket, strip terminal, kabel dan modul tersambung dengan benar. Jika sistem PLC Anda berada di daerah yang mengalami getaran konstan yang mungkin bisa melonggarkan koneksi terminal, melakukan cek ini lebih sering dan mempertimbangkan memasang detektor getaran.
• Mengidentifikasi Pembaruan Dibutuhkan - Periksa setiap pemberitahuan produk, patch dan upgrade dan memutakhirkan seperlunya.
• Hapus yang tidak perlu Item - Jauhkan item seperti gambar, manual instalasi atau bahan lain yang jauh dari sistem PLC. Meninggalkan barang-barang ini di atas rak CPU atau lampiran lain dapat menghambat aliran udara dan menciptakan hot spot, akhirnya menyebabkan kerusakan sistem.
• Bagian Audit Penggunaan - Melakukan audit untuk memeriksa setiap komponen sistem PLC dan menentukan apakah bagian yang baik atau perlu diganti.
• Ambil Inventarisasi Bagian Penggantian - Jauhkan stok suku cadang di tangan untuk meminimalkan downtime akibat kegagalan komponen. Memiliki cadangan yang tepat di saham selama situasi kegagalan dapat mengakibatkan penutupan hanya menit bukan jam atau hari.

Partition tabel restoration with Testdisk at Linux

Minggu ini minggu yang mendebarkan buat saya karena saya hampir saja kehilangan semua data di laptop saya karena percobaan saya dalam menginstall Linux ubuntu berdampingan dengan Win 7.

Sebabnya karena ketidak tahuan saya dalam teknik instalasi linux yang ternyata berbeda dengan instalasi windows. Bila di windows kita tinggal ikuti langkah langkah dan instalasi di salah satu drive yang udah disiapkan tidak akan mengganggu drive lain tapi ternyata di Linux bisa menghapus semua data partition table dan diganti dengan versi linux.

Ok setelah partisi windows saya terhapus dimana saya memiliki 2 windows yaitu Win 7 dan Win XP, maka saya cuma bisa booting lewat linux live usb saya, karena linux belum terinstall di hardisk. OK langsung aja berikut cara recovery nya masih dalam english ...

TestDisk is OpenSource software and is licensed under the terms of the GNU General Public License (GPL v2+).
TestDisk is powerful free data recovery software! It was primarily designed to help recover lost partitions and/or make non-booting disks bootable again when these symptoms are caused by faulty software: certain types of viruses or human error (such as accidentally deleting a Partition Table). Partition table recovery using TestDisk is really easy.
TestDisk can

• Fix partition table, recover deleted partition
• Recover FAT32 boot sector from its backup
• Rebuild FAT12/FAT16/FAT32 boot sector
• Fix FAT tables
• Rebuild NTFS boot sector
• Recover NTFS boot sector from its backup
• Fix MFT using MFT mirror
• Locate ext2/ext3/ext4 Backup SuperBlock
• Undelete files from FAT, exFAT, NTFS and ext2 filesystem
• Copy files from deleted FAT, exFAT, NTFS and ext2/ext3/ext4 partitions.

TestDisk has features for both novices and experts. For those who know little or nothing about data recovery techniques, TestDisk can be used to collect detailed information about a non-booting drive which can then be sent to a tech for further analysis. Those more familiar with such procedures should find TestDisk a handy tool in performing onsite recovery.

Symptoms

If this hard disk's primary partition contained an operating system, it would most likely no longer boot up - due to its corrupted boot sector. If the hard disk was a secondary (data) drive or you can connect the drive to another computer in its secondary channel (usually where a CD/DVD drive is connected), the following symptoms would be observed:

1. Windows Explorer or Disk Manager displays the first primary partition as raw (unformatted) and Windows prompts: The drive is not formatted, do you want to format it now?
   [You should never do so without knowing why!]
2. A logical partition is missing. In Windows Explorer, that logical drive is no longer available. The Windows Disk Management Console now displays only "unallocated space" where this logical partition had been located.

Running TestDisk executable

If TestDisk is not yet installed, it can be downloaded from TestDisk Download then Extract the files from the archive including the sub-directories or if we have Linux live we can install it from software center Linux.
To recover a lost partition or repair the filesystem from a hard disk, USB key, Smart Card, etc., you need enough rights to access a physical device.

• Under DOS, run TestDisk.exe
• Under Windows, start TestDisk (ie testdisk-6.13/testdisk_win.exe) from an account in the Administrator group. Under Vista, right-click testdisk_win.exe and then "Run as administrator" to launch TestDisk.
• Under Unix/Linux/BSD, you need to be root to run TestDisk (ie. sudo testdisk-6.13/testdisk_static)
• Under MacOSX, if you are not root, TestDisk (ie testdisk-6.13/testdisk) will restart itself using sudo after confirmation on your part.
• Under OS/2, TestDisk doesn't handle a physical device, only a disk image. Sorry.

To recover partition from a media image or repair a filesystem image, run

• testdisk image.dd to work from a raw disk image
• testdisk image.E01 to recover files from an Encase EWF image
• testdisk 'image.???' if the Encase image is split into several files.

To repair a filesystem not listed by TestDisk, run testdisk device, i.e.

• testdisk /dev/mapper/truecrypt0 or testdisk /dev/loop0 to repair the NTFS or FAT32 boot sector files from a TrueCrypt partition. The same method works with filesystem encrypted with cryptsetup/dm-crypt/LUKS.
• testdisk /dev/md0 to repair a filesystem on top of a Linux RAID device.

Log creation

• Choose Create to instruct Testdisk to create a log file containing technical information and messages, unless you have a reason to append data to the log or you execute TestDisk from read only media and must create the log elsewhere.
• Choose None if you do not want messages and details of the process to be written into a log file (useful if for example Testdisk was started from a read-only location).
• Press Enter to proceed.

Disk selection

All hard drives should be detected and listed with the correct size by TestDisk:

• Use up/down arrow keys to select your hard drive with the lost partition/s.
• Press Enter to Proceed.

If available, use raw device /dev/rdisk* instead of /dev/disk* for faster data transfer.

Partition table type selection

TestDisk displays the partition table types.

• Select the partition table type - usually the default value is the correct one as TestDisk auto-detects the partition table type.
• Press Enter to Proceed.

Current partition table status

TestDisk displays the menus (also see TestDisk Menu Items).

• Use the default menu "Analyse" to check your current partition structure and search for lost partitions.
• Confirm at Analyse with Enter to proceed.

Now, your current partition structure is listed. Examine your current partition structure for missing partitions and errors.
The first partition is listed twice which points to a corrupted partition or an invalid partition table entry.
Invalid NTFS boot points to a faulty NTFS boot sector, so it's a corrupted filesystem.
Only one logical partition (label Partition 2) is available in the extended partition. One logical partition is missing.

• Confirm at Quick Search to proceed.

Quick Search for partitions

TestDisk displays the first results in real time.

(click on thumb to display the image).

During the Quick Search, TestDisk has found two partitions including the missing logical partition labeled Partition 3.

• Highlight this partition and press p to list your files (to go back to the previous display, press q to Quit, Files listed in red are deleted entries).
  

All directories and data are correctly listed.

• Press Enter to proceed.

Save the partition table or search for more partitions?

• When all partitions are available and data correctly listed, you should go to the menu Write to save the partition structure. The menu Extd Part gives you the opportunity to decide if the extended partition will use all available disk space or only the required (minimal) space.
• Since a partition, the first one, is still missing, highlight the menu Deeper Search (if not done automatically already) and press Enter to proceed.

A partition is still missing: Deeper Search

Deeper Search will also search for FAT32 backup boot sector, NTFS backup boot superblock, ext2/ext3 backup superblock to detect more partitions,

it will scan each cylinder

(click on thumb).

After the Deeper Search, the results are displayed as follows:
The first partition "Partition 1" was found by using backup boot sector. In the last line of your display, you can read the message "NTFS found using backup sector!" and the size of your partition. The "partition 2" is displayed twice with different size.
Partitions listed as D(eleted) will not be recovered if you let them listed as deleted. Both partitions are listed with status D for deleted, because they overlap each other. You need to identify which partition to recover.

• Highlight the first partition Partition 2 and press p to list its data.

The file system of the upper logical partition (label Partition 2) is damaged

(click on thumb).

• Press q for Quit to go back to the previous display.
• Let this partition Partition 2 with a damaged file system marked as D(deleted).
• Highlight the second partition Partition 2 below
• Press p to list its files.

It works, your files are listed, you have found the correct partition!

• Use the left/right arrow to navigate into your folders and watch your files for more verification
  

Note: FAT directory listing is limited to 10 clusters - some files may not appear but it doesn't affect recovery.

• Press q for Quit to go back to the previous display.

• The available status are Primary, * bootable, Logical and Deleted.

Using the left/right arrow keys, change the status of the selected partition from D(eleted) to L(ogical). This way you will be able to recover this partition.
Hint: read How to recognize primary and logical partitions?
Note: If a partition is listed *(bootable) but if you don't boot from this partition, you can change it to Primary partition.

• Press Enter to proceed.

Partition table recovery

It's now possible to write the new partition structure.
Note: The extended partition is automatically set. TestDisk recognizes this using the different partition structure.

• If all partitions are listed and only in this case, confirm at Write with Enter, y and OK.

Now, the partitions are registered in the partition table.

NTFS Boot sector recovery

The boot sector of the first partition named Partition 1 is still damaged. It's time to fix it. The status of the NTFS boot sector is bad and the backup boot sector is valid. Boot sectors are not identical.

• To copy the backup of the boot sector over the boot sector, select Backup BS, validate with Enter, use y to confirm and next OK.

More information about repairing your boot sector under TestDisk Menu Items. The following message is displayed:
The boot sector and its backup are now both OK and identical: the NTFS boot sector has been successfully recovered.

• Press Enter to quit.

• TestDisk displays You have to restart your Computer to access your data so press Enter a last time and reboot your computer. 

from : http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

Setelah partition table diperbaiki selanjutnya kita coba masuk kembali ke windows 7, bila kita masih belum berhasil boot ke windows 7 kita bisa perbaiki dengan cara boot ke DVD instaler win 7 dan memilih opsi untuk repair, kemudian masuk ke DOS dan jalankan command berikut untuk memperbaiki MBR, Bootsector dan BCD table .

> bootrec /fixmbr
> bootrec /fixboot
> bootrec /rebuildbcd

Kemudian restart kembali dan kita akan bisa login ke windows 7 kita dan bisa memperbaiki partition yang mungkin tidak sesuai dengan yang kita inginkan dengan Partition Magic.

rec: 12032015@v1tr4