FarmSoft Studios Graphic Design & Web Design

Ever wanted to filter out the files that were less than 1GB with the simple ‘du’ (disk usage) command? Simple. Add the -h flag and a little grep magic, and you’re all set:

du -h | grep '[0-9]G'

A nice article on that process here:
http://mobiforge.com/developing/story/lightweight-device-detection-php

So you have your new iPhone^®, sync it up to your corporate Exchange^® server, and go on your merry way. Later that day, you go to take a picture of that adorable pose your daughter is in. “Ha!” you think, “The iPhone has a great camera for times just like this!” You smile as you pull your sleek little device out. Your smile quickly fades as you frantically search in vain for the camera app. You flip violently through the pages of apps, and finally succumb to your stupidity, and search for camera in spotlight. No Go. Your daughter is long gone, and you’re still there trying to figure out what is wrong. You go through every setting, making sure the restrictions are off in the settings panel. Yep, all’s good there… Hmm. As a last ditch effort, you get on the phone, and call your IT manager, asking if there is anything that he knows of to make a camera disappear in your iPhone.
“Oh, yeah,” he says. “I didn’t check the box to allow your camera in Exchange. I’ll be right on that.” “Nice,” you think silently.

Ok, so nice story. But you want to know how to get your camera back. Here’s the lowdown:
I found a solution to the problem.

Exchange 2007 has active sync policies. One of the options is to disallow the camera.

To resolve the problem do the following.

1. Open Exchange Management Console
2. Click “Organization Configuration”
3. Click “Client Access”
4. On the right you should see your active sync policies. Right click the policy and chose “Properties”
5. Click the “Device” tab
6. Check “Allow camera”

You should be all set. For those of you who are NOT connected to an Exchange server, check the restrictions pane under Settings > General > Restrictions

Calendar sync works in XP 64 using compatibility mode

Well it does work for me – two way sync with Outlook 2007!

Simply save the installer to your machine, right click on the installer executable and select properties in the second tab Compatibility check the checkbox “Run this program in compatibility mode for: Windows XP.

Run the installer

Then before running the program, navigate to the installed executable with windows explorer. It will probably be in: C:\Program Files x86\Google\Google Calendar Sync\ right click on GoogleCalendarSync.exe and do the same as for the installer. Compatibility with Windows XP

run the sync…

via Windows XP 64-bit Edition is not compatible with Google Calendar Sync at this time – Calendar Help.

I was greeted by the following error this evening from within my SugarCRM instance:

MySQL error 1194: Table 'contacts' is marked as crashed and should be repaired

So this is what I did to fix it:

[root@crm ~]# mysql -p
Enter password: ********
Welcome to the MySQL monitor.  Commands end with ; or \g.

mysql> use sugarcrm
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> CHECK TABLE contacts;
+-------------------+-------+----------+-----------------------------+
| Table             | Op    | Msg_type | Msg_text                    |
+-------------------+-------+----------+-----------------------------+
| sugarcrm.contacts | check | error    | Found wrong record at 73544 |
| sugarcrm.contacts | check | error    | Corrupt                     |
+-------------------+-------+----------+-----------------------------+
2 rows in set (0.18 sec)

mysql> REPAIR TABLE contacts;
+-------------------+--------+----------+-----------------------------------------------------+
| Table             | Op     | Msg_type | Msg_text                                            |
+-------------------+--------+----------+-----------------------------------------------------+
| sugarcrm.contacts | repair | info     | Key 1 - Found wrong stored record at 73544          |
| sugarcrm.contacts | repair | info     | Found block with too small length at 78096; Skipped |
| sugarcrm.contacts | repair | warning  | Number of rows changed from 892 to 877              |
| sugarcrm.contacts | repair | status   | OK                                                  |
+-------------------+--------+----------+-----------------------------------------------------+
4 rows in set (0.26 sec)