Indikasi Blinking Errors PIXMA iP1800 (by LED Blinking in Orange Alternately):

BLINKING 2   : Out of Paper or Paper feed error (kertas yg masuk tidak pas atau kertas belum di masukkan)
BLINKING 3   : Paper Jam (kertas keluar jalur)
BLINKING 4   : Tinta cartridge habis
BLINKING 5   : Cartridge tidak dikenali
BLINKING 7   : Posisi Cartridge tidak tepat
BLINKING 8   : Ink absorber penuh
BLINKING 14 : Cartridge tidak dikenal

Pesan di desktop PC:

ada indikasi kuning pada saat print pada dialog box di kanan bawah pada salah satu icon catridge

Tata cara mereset Printer Canon IP1980, 1880, 1800 (sejenis)
Yang pelu diperhatikan:
1. Generator tool bisa dipakai setelah printer tidak blinking / green led
2. Jangan lupa click tombol Lock Release kemudian Set Destination pilih 1800 (ASA)
3. Centang Cleaning dan EPROM Clear
4. Masukkan kertas Klik test pattern 1, biasanya pada proses ini printer kembali blinking orange
dan setelah beberap saat kembali normal (green led)
5. Tahap Akhir Klik pada tombol Main dan Pattern.
6. Untuk memastikan printer sudah sip, Klik EPROM information perhatikan CLTime. Ciri khas printer harus direset, tanggal di CL Time menunjukan tanggal sekarang. Kalo sudah direset tanggal sudah berubah.

Cara kedua mereset IP1980 dan sejenisnya, cabut cartridge printer anda dan ganti dengan cartride yang masih normal dengan demikian printer akan mengenali cartridge baru.

Cara ketiga pakai software IPTools

iP Tool versi 0.9.2 adalah software resetter untuk printer Canon type iPxxxx. Adapun type yang dapat direset oleh sofware ini adalah :

iP1200, iP1300, iP1600, iP1700, iP1800, iP2200, dan iP2500

untuk softwarenya silahkan download di link dibawah ini ato kirim komentar tulis alamat email anda, insyaallah akan saya kirim via email.

- http://www.ipt.nm.ru

- IP Tool (Download indowebster)

Alternatif resetter tool:

- Software Resetter Canon IP 1880 (General Resetter Tool) (Download indowebster)

Cara ketiga ini penulis sudah pernah mencobanya dan berhasil. Percobaan dilakukan pada printer canon Ip 1880 dengan blinking 4 (low ink catridge), ketika print muncul dialog di kanan bawah dengan status pada indikasi catridge hitam.

contact email : This e-mail address is being protected from spambots. You need JavaScript enabled to view it

According to the media, the Austrian hacker Peter Kleissner got a offer from Microsoft. This wouldn’t be news-worthy if Kleissner hadn’t programmed and offered to sell a so called bootkit – that is a rootkit that hides within the Master Boot Record of a hard disk and gets loaded before the operating system kernel and thus can hide very well within the OS. As it gets loaded so early, a bootkit in general is also capable of bypassing even full disk encryption for example with TrueCrypt.

Kleissner “wrote” this software after analysing the Sinowal bootkit. His publicly available code shows many similarities with Sinowal – also our detection routines for Sinowal got triggered by it. No wonder, it seems he just disassembled Sinowal and modified the sources a little so that the Vista/Win7 boot chain was working again (see Kleissners comment in the Sinowal analysis of RSA, near in the bottom of the page).

So, Kleissner seems to have built his “breakthrough” code upon already existing malware, the work of those people trying to invade your systems and steal your data. Sadly his skills in self-marketing seem to exceed those he has in the fields of self-reflection, ethics and his sense of responsibility.

Unfortunately, he was working for an antivirus company while doing all this. His former employer reacted promptly after getting informed and dismissed him. You have to be able to trust someone to hunt for malware, not to produce it. Especially if you are offering security products – security is very much about who to trust.

Now obviously Microsoft thinks it is a good idea to work with people that proved to work on the bad side of security. This isn’t going to raise my trust in Microsoft and the products of the Redmond company. Quite contrary it is destroying the trust they earned over the last few years – where they introduced the Secure Development Lifecycle, showed increased attention for security problems and risks and also entered the antivirus market.

Security companies – like Microsoft is, too – should really think about their actions and the consequences those actions have on the trust of users. If the company can’t be trusted anymore because of their actions it has no chance in the security market anymore.