The numeric value is the measure at which Spam gets deleted.  Messages are assigned points based on how ‘spammy’ they appear.  Given that piece of info, the lower the number, the fewer messages get through.

• Open the VBE and select Tools, Options
• Select the Docking tab and make sure the window in question has no checkmark in that tab
• Close the options window. If you don’t see it yet, select Window, Cascade.
• Now open the Options dialog again and check the docking property of the window you just (hopefully) got back.
• Drag it to where you want it docked.

Done!  Now get back to work!

1) Make sure that the php.ini for the cli is updated to include the zend framework. See the /etc/apache2/php.ini for the changes required.

2) When creating the /data and /scripts folders, they need to be in the root of your quickstart app, beside your “public” folder.

3) I didn’t have the Sqlite driver installed on my machine so that had to be installed before I could create the database.

AN ERROR HAS OCCURED: The sqlite driver is not currently installed

To fix this, I installed the “php-mdb2-driver-sqlite” package from Synaptic.

After fixing these 3 problems, the data loading script worked like a charm!

There was one more glitch getting the Quickstart app completed. Apparently in Ubuntu 11.10, Sqlite has been upgraded to Sqlite3 where Zend is still using the older version. Here’s a workaround to add the prior version to get through: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/875262/comments/10

sudo apt-get install gimp-plugin-registry

See the details.

http://www.photofriday.com/calibrate.php

It won’t be perfect, but the price is right and you have nothing to lose but a few minutes of fiddling.

BEGIN
   DECLARE
       -- Equivalent of a package level variable
       i   INTEGER := 0;

      PROCEDURE doStuff (description IN VARCHAR2)
      IS
         i   INTEGER;
      BEGIN
         DBMS_OUTPUT.put_line ('description is ' || description);

         i := i + 1;
      END;

      FUNCTION calcStuff (i_value IN INTEGER)
      return integer
      iS
         i_dummy   INTEGER;
      BEGIN
         i := i + 1;
         DBMS_OUTPUT.put_line ('Function called ' || i || ' time(s)' );

         return i_value + i;
      END;

   BEGIN
      -- Call our shiny new procedure
      doStuff ('one');
      doStuff ('two');
      doStuff ('three');

      -- Call our new function
      DBMS_OUTPUT.put_line ('Function returned: ' || calcStuff(100));
      DBMS_OUTPUT.put_line ('Function returned: ' || calcStuff(150));
      DBMS_OUTPUT.put_line ('Function returned: ' || calcStuff(200));

   END;
END;

#!/bin/bash
files=$#
count=1
message=`echo "Dumping EXIF from $files files"`

(while [ $# -gt 0 ]; do

	# Strip off the file extension, including the "."
	upperExt=`echo $1 | sed 's/.*\(\..*\)/\1/' | tr '[a-z]' '[A-Z]'`

	if [ -f "$1" ]
	then
		# Get the file name without the extension
		# trimmed=`echo $1 | sed 's/\(.*\)\..*/\1/'`

		if [ $upperExt = ".JPG" -o  $upperExt = ".JPEG" -o  $upperExt = ".PPM" -o $upperExt = ".CR2" -o $upperExt = ".NEF" -o $upperExt = ".OTHER_RAW_EXTENSION" ]
		then
			# Output EXIF data to a new text file named the same as the original image.
			exiftool -canon -S "$1" > "$1.txt"
		fi
	fi
	# Output the zenity progress bar
	sav=`echo "(($count / $files) * 100)" | bc -l`
	echo $sav
	count=`expr $count + 1`
shift
done) | zenity --progress --auto-close --auto-kill --text "$message"

The fix is to sidestep mod_security for those requests. Ideally it should be limited to the offending request, but in the interest of getting people running, I simply added a .htaccess file in the /admin folder of the broken sites with the following contents.

<IfModule mod_security.c>
    SecFilterEngine Off
    SecFilterScanPOST Off
</IfModule>

Remove any proprietary ATI/AMD drivers from your Natty installation. You can put them back on after we install the new kernel.

Now that you’ve checked for anf removed any ATI proprietary drivers, visit this URL and pick out the kernel that you want to try. http://kernel.ubuntu.com/~kernel-ppa/mainline/

In my case, I was running the latest natty kernel on a new (but low-end) Toshiba C650D laptop. It was crashing constantly, never running for more than an hour. As there weren’t any clear indicators in the logs, and the hardware worked fine on Windows, I wanted to try a different kernel. I wanted to the newest kernel possible in the hopes that whatever issue had been resolved.

I opened the above Url and scrolled way down to the bottom of the page. All the way to “v3.0.4-oneiric”. It was dated four days ago – that ought to be new enough! As I’m running 64 bit 11.04, I need the “amd64″ binaries. Download the appropriate ones, “headers…all” and the “headers” and “image” file for my architecture.

 linux-headers-3.0.4-030004_3.0.4-030004.201108301138_all.deb linux-headers-3.0.4-030004-generic_3.0.4-030004.201108301138_amd64.deb linux-image-3.0.4-030004-generic_3.0.4-030004.201108301138_amd64.deb 

Next, open a terminal window and cd to the folder where your binaries are located. Run the following command to install the new kernel:

 /sudo dpkg -i /linux-headers-3.0.4-030004_3.0.4-030004.201108301138_all.deb linux-headers-3.0.4-030004-generic_3.0.4-030004.201108301138_amd64.deb linux-image-3.0.4-030004-generic_3.0.4-030004.201108301138_amd64.deb 

Let it run for a minute or two and if there are no errors reboot. If you have errors, fix them, try the install command again and reboot. If Grub doesn’t prompt you to choose a kernel, check it from terminal once you’re logged in. with the following:

 /uname -r /

There you have it! Running a 3.0 kernel on Ubuntu 11.04, Natty.