Using the P3120 and other Lexmark printers in Linux

I have the Lexmark P3120 AIO, and for the longest time I could never get it working in Linux. Well, I finally figured it out (printing only), when I saw that the P3150 was confirmed working and I was only 30 model numbers behind. I used the Z600 drivers for Linux that were provided by Lexmark. Lexmark’s Linux driver support is halfhearted and incompleted, but the Z600 driver works for a wide range of Lexmark printers.

To check if your printer will work either with the Z600 or Z700 drivers, consult Gentoo’s Lexmark Printers guide.
If you’re using Gentoo, well lucky you. Just follow the instructions on the Z600/Z700 ebuilds there.
If you’re using RedHat, it’s even easier. Get the Z600 RPM provided by Lexmark.
If you’re using Ubuntu, there are guides for Breezy users on the Ubuntu website:
Ubuntu Wiki guide
However, I prefer the Honey Badger IT guide. Keep trying until one of them works for you. I think using alien to convert the RPM to a .deb is the best way (look on the guides!).
Edgy users will need to copy the PPD from the driver (after following one of the above guides, that is!) to /usr/shared/ppd, because that’s where CUPS looks for the PPD in Edgy.

Bug – Compatibility issue with Internet Explorer and Autodesk VIZ 2007 registration

This bug affects Autodesk VIZ 2007 (and possibly its older-sibling 3ds max 8 ) during registration when Internet Explorer 7 Beta is installed on the system. After Autodesk VIZ 2007 installs, the first time the user runs it it will complain that it cannot find a file in C:\Documents and Settings\User\Local Settings\Temp\~RT65.tmp\. The file in question was RTEaseReAuthBeginReg.html, or possibly a similar file. This file exists in C:\Program Files\Autodesk\VIZ2007\WebDepot. After copying the file to the ~RT65.tmp directory, VIZ will have IE7 open the file repeatedly. Every time, the Information Bar appears about potentially unsafe ActiveX content. Opening the file repeatedly causes more and more tabs to open.

The best potential fix is to remove IE7, and use IE6 instead.

To Be Verbs

It seems that a lot of people are enjoying my “To Be” Verbs Analysis” program, and, well, some aren’t. Since only the school has Writer’s Workbench, people have trouble finding time to use it. Well, now they can do it at home. Mitchell pointed out that “It doesn’t work!” because it wasn’t picking up “wasn’t”, “weren’t”, and “isn’t”. It’s fixed now, along with a minor issue with having “Dr.”, “Mr.”, and words like that.

If you could, spread it to any of your friends that might need it too.

X-Window Compositing

I tried using compositing on X-Window (with Kompmgr, of course), and it is amazing. However, it is still in the developmental stages and isn’t very well-known.

It features window transparency, shadows, fading in/out for everything, and more. I’m beginning to see why Windows Vista has nothing innovative. Microsoft showed off how the little icons would reflect the file’s contents – KDE and GNOME have had this for forever for text files. Vista will have fancy see-through windows and stuff – compositing in X does this just fine (kinda slow without a good GFX card though). It seems the only new thing Vista will have is the nice little start button.


I recently changed my system to a dual-boot setup with Ubuntu GNU/Linux, and it worked magically for awhile. However, I was using Windows XP to make a FAT32 partition (seems like I had to make it in Windows for it to be recognized), when my GRUB boot loader messed up. I couldn’t boot my computer. Luckily, I had Ubuntu Live handy, and I booted into a live session.

I made a rescue floppy by going into GRUB’s folder (with stage1 and stage2), and running the following commands:

dd if=stage1 of=/dev/fd0 bs=512 count=1
dd if=stage2 of=/dev/fd0 bs=512 seek=1

I now had a bootable floppy. With the floppy, I can boot into the GRUB prompt. From there, I could either type in some commands to boot Linux, or I could install GRUB. I installed it by:

grub> root (hd1,0) or whatever partition Linux is on
grub> setup (hd0)

I now had GRUB back again!

I was testing browsers…

… and I noticed something odd – Opera, Firefox, and Internet Explorer all handle DOM Style colors differently when a script gets the color as a string. Let’s say you make something’s color red.

  1. Internet Explorer will keep the format you wrote it – if you put #FF0000, it will give “#FF0000″. If you put rgb(255, 0, 0), it will give “rgb(255, 0, 0)”.
  2. Firefox will turn everything into the rgb(###, ###, ###), turning “#FF0000″ into “rgb(255, 0, 0)”.
  3. And to complicate everything, Opera converts all the colors into #hex notation, making rgb(255, 0, 0), become “#FF0000″.

Bothersome, ain’t it?