André L. S.

I’ve found many tutorials about this topic, but only one, found in Luis Gallardo’s blog, worked for me.

Luis’s tutorial explain how to install on Ubuntu 9.10, so some steps are not necessary. I’ll show necessary steps to install on Ubuntu 10.04.

You need to download drivers from Avasys site. Go to this link, scroll down the page, choose “Epson Stylus CX4300/CX4400/CX4450/CX5500/CX5600/DX4400/DX4450“, “Ubuntu” and version “10.04“, click “Next”.

Now, download “iscan-data_1.9.0-1_all.deb“, “iscan_2.26.4-2.ltdl7_i386.deb” and “iscan-plugin-cx4400_2.1.3-1_i386.deb“. After, run commands:

sudo dpkg -i iscan-data_1.9.0-1_all.deb
sudo dpkg -i iscan_2.26.4-2.ltdl7_i386.deb
sudo dpkg -i iscan-plugin-cx4400_2.1.3-1_i386.deb

Make sure the scanner is connected and turned on and run command

lsusb

Should appear a list of devices connected to the USB ports, like this:

Bus 003 Device 004: ID 04b8:083f Seiko Epson Corp. Stylus DX4450
Bus 003 Device 003: ID 04fc:05d8 Sunplus Technology Co., Ltd
Bus 003 Device 002: ID 04f3:0216 Elan Microelectronics Corp.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 18e3:9101 Fitipower Integrated Technology Inc
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The first line (“Bus 003 Device 004: ID 04b8:083f Seiko Epson Corp. Stylus DX4450“) means the scanner was detected on address 003:004.

These steps are enough for the scanner be detected for XSane, but only root can to use.

To fix this “little” problem, edit file /lib/udev/rules.d/40-libsane.rules and add the following lines:

# Epson CX5600
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="083f", MODE="0664", GROUP="saned", ENV{libsane_matched}="yes"

Turn off and turn on your scanner. To see if the problem was fixed, run command lsusb again. The output should be like this:

Bus 003 Device 004: ID 04b8:083f Seiko Epson Corp. Stylus DX4450

Note the number of “Bus” and “Device”, with them run command

ls -l /dev/bus/usb/<BUS>/<DEVICE>

Replace <BUS> and <DEVICE> by respective numbers:

ls -l /dev/bus/usb/003/004

You will see something like

crw-rw-r--+ 1 root saned 189, 129 2011-07-01 14:01 /dev/bus/usb/003/004

Now you can to use your scanner with any user owned to group saned.

I’ve just updated my WordPress to version 3.2, when update has been finished a page with error code 500 was displayed. In log file had many entry of Fatal error: Allowed memory size of 33554432 bytes exhausted

To know if it your problem too, edit file error_log in wp-admin directory and and take a look at last rows.

The following process fixed this for me, but your host server should allow sizing PHP memory at runtime.

Open and edit file wp-settings.php at root of WordPress directory and put the row bellow after “<?php”:

define('WP_MEMORY_LIMIT', '64M');

Here I’ve set up to 64MB to PHP, but how to know amount of MB to set up?

In error message, the long number means amount of bytes allocated to PHP: “Fatal error: Allowed memory size of 33554432…”. This number represents 32MB (do this calculation to converts byte in megabytes 33554432 / (1024^2) = 32).

Just set a number greater than the result in line above.

I’ve was analysing blog access chart and, curiously, I see how are the most usable browsers.

The fight between Firefox and Internet Explorer is old and, little time ago, Microsoft’s browser lost first position to Firefox. Now, with Google Chrome more stable and accessible, the three firsts position may be changed again.

In one year of interval, this blog had 35,738 visits, where the Firefox was most usable browser, responsible for 14,705 (41.75%) of access, distantly followed by Internet Explorer (10,542 access, or 29.5%) and Google Chrome (8,679 access, or 24.29%). Opera came in 4th and Safari came in 5th.

Below the chart generated by Google Analytics with complete list of browsers and amount of access:

Chart generated by Google Analytics between 06/07/2010 and 06/07/2011 (click to zoom)

Will be a matter of time to Internet Explorer to leave second position to Google Chrome

Sometimes our applications depends of third-part applications for tests or to access resources of emulator that aren’t available by default.

In directories of SDK, commonly in platform-tools, there is an executable called adb, with it we’ll to install third-part applications.

You will need an application (.apk). Browse internet or copy from your Android smartphone using applications like AppSaver.

- Run the emulator, you can use SDK Manager or Eclipse plugins.

- Using DOS Command (Windows) or terminal (Linux), open directory platform-tools and run commando line below:

$ adb install <.apk path>

This message will be displayed

$ adb install Application.apk
125 KB/s (1091937 bytes in 8.474s)
        pkg: /data/local/tmp/Application.apk
Success

Now, the third-part application is available at emulator menu, like have installed in your smartphone.

Agora o aplicativo estará disponível no menu do emulador.

If you’re trying to install Android SDK on Windows 64 bits and is receiving the error message “JDK not found”, the solution found by http://www.eighthourlunch.com/node/161, basicaly insert some entries at Windows registry, after this, the Google Android SDK will found your JDK instalation.

The .REG file are available here .

Before run file, open it with notepad and change path “C:\\Program Files\\Java\\jdk1.6.0_23″ to your JDK directory, and the path “C:\\Program Files\\Java\\jre6″ to your JRE directory.

This fix has worked for me.