The AppZapper is the uninstaller that Apple forgot. This application is one of my most essential tools when managing my Macs, as it performs a safe and extended clean uninstall of an application, along with the targeted application’s associated sub-files. AppZapper is particularly needed with applications that do not have a reliable uninstaller feature programmed within. Another brilliant aspect of AppZapper is that it protects the system files, and also provides a audit log of the applications that have been uninstalled. Although it is seldom used, I rely on it, and it is definitely worth the small cost.

Like so many others who continue to support Oracle8i databases for required legacy systems, I was engaged on a impaired database that required the recovery of 9 datafiles. I have performed this type of recovery in the past with the odd datafile, but none to this extent of involvement.

It is noteworthy to mention that several sins exists with this legacy system, specifically, using a de-supported Oracle8i database on an non-certified Windows operating system. Regardless, real life solutions and equations seldom show mercy.

ERROR:
The Oracle8i database reside on Windows 2003 clustered architecture, and when the Event Logs were examined, no related events were recorded. However, the only reported errors was that of the database’s Alertlog.

KCF: write/open error block=0x2f4b4 online=1
file=9 S:\ORADATA\CIM4644\DATA\CIM_DATA02.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 1450) Insufficient system resources exist to complete the requested service.'
Automatic datafile offline due to write error on
file 9: S:\ORADATA\CIM4644\DATA\CIM_DATA02.DBF

APPLIES TO:

• Oracle8i Enterprise Edition 8.1.7.4.1
• Oracle FailSafe 3.3.3
• Windows 2003 Enterprise Edition, SP3

SOLUTION:
To address this issue rather quickly, I connected onto the database as the SYSDBA and performed a simple ‘recover database’ statement.

c:\> sqlplus /nolog

SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup mount;
ORACLE instance started.

Total System Global Area 2098952220 bytes
Fixed Size                    75804 bytes
Variable Size             421076992 bytes
Database Buffers         1677721600 bytes
Redo Buffers                  77824 bytes
Database mounted.

SQL> recover database;
Media recovery complete.

SQL> alter database open;

Database altered.
SQL>

Yet, I still receive an error when the application is launched and begins to access it’s related tables objects.

Errors in file r:\oradata\CIM4644\bdump\cim4644SMON.TRC:
ORA-00604: error occurred at recursive SQL level 1
ORA-00376: file 12 cannot be read at this time
ORA-01110: data file 2: 'S:\ORADATA\CIM4644\DATA\CIM_DATA07.DBF'

Performing a simple recovery command did not extend down to the datafile recovery, so additional steps are required. To identify what datafiles required additional recovery, I execute a simple PLSQL command to show me these remaining datafiles that are in need of recovery.

SQL> select file_name from dba_data_files df, v$recover_file vf where df.file_id = vf.file# order by 1;
SQL>

For each datafile reported, I simply execute a recovery command that is datafile specific.

SQL> recover datafile 'S:\ORADATA\CIM4644\DATA\CIM_DATA07.DBF';

ORA-00279: change 37719885 generated at 11/06/2010 03:04:19 needed for thread 1
ORA-00289: suggestion : U:\ORADATA\CIM4644\ARCHIVE\CIM4644T001S6760.ARC
ORA-00280: change 37719885 for thread 1 is in sequence #6760

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

Log applied.
Media recovery complete.
SQL>

Once the datafile is successfully recovered, I am then able to bring the datafile online.

SQL> alter database datafile 'S:\ORADATA\CIM4644\DATA\CIM_DATA07.DBF' online;

Database altered.
SQL>

With all the questionable datafiles recovered successfully and brought online, I then perform an export of the application’s schema to ensure no data corruption.

c:\> exp <account>/<password>@<tnsnames> file=my-test-export_201011a.dmp log=t_my-test-export_201011a.log owner=<schema name> grants=yes rows=yes indexes=yes

I have found that a quick data export of a schema provides an excellent means of quickly
determining data corruption.

If you have grown rather tired of the standard Mac OS X login wallpaper image, there are several different methods to accomplish a wallpaper background change that are quite simple. If you are new to the Mac world, you could use a system utility named Loginox, which once installed, will make simple work of it. I personally have not installed this tool. Mainly because it’s very seldom that I change my login wallpaper.

Another method is by utilising the command line of OS X, of which I have detailed the steps below. As I am comfortable with using the command line, I much prefer this method.

Dependencies:

• A desired JPG wallpaper image of your liking is required. One can find some very talented designs of wallpapers at DeviantART, InterfaceLIFT, etc.

Considerations:

• It is considered best practice to create a backup of any file(s) prior to being altered, of which is provided within the guide below. Also, I found that it is best to properly resize the JPG image to match your monitor’s resolution size. This can be accomplished with any graphic editing software, such as Pixelmator, or with Mac’s inherent Preview application.

Applies to:

• Mac OS X 10.6 Snow Leopard

Procedural Guide:

1. Launch a terminal session within your Mac operating system by:

• selecting Applications
• then, Utilities
• then, Terminal.app

2. Place your desired wallpaper into your home directory. To determine what the path of your home directory is, simply type at the command prompt:

   	pwd
   	

3. Using your terminal session, create a backup of your current DefaultDesktop logon wallpaper: Note: You will be required to provide your password as the DefaultDesktop.jpg image is considered a system file.

   	sudo mv /System/Library/CoreServices/DefaultDesktop.jpg /System/Library/CoreServices/DefaultDesktop.jpg.old
   	

4. Once a backup of your current logon wallpaper image has been completed successfully, then, simply place your new logon wallpaper into position:

   	sudo cp MyNewDefaultDesktop.jpg /System/Library/CoreServices/DefaultDesktop.jpg
   	

5. Restart your computer for the changes to take effect.

6. Note: If you wish to undo your handy work, simply type:

   	sudo cp /System/Library/CoreServices/DefaultDesktop.jpg.old /System/Library/CoreServices/DefaultDesktop.jpg
   	

For those who are uncomfortable with messing about within the computer’s system files, there is another alternative that is again, quite simple. Once can alter the ‘com.apple.loginwindow‘ preference file to pointe at a different path where the JPG image is located. However, many times a wallpaper image file is accidently moved to the bin, and therefore your preference file will need to once again be altered to reflect the proper path. To alter the ‘com.apple.loginwindow‘ preference file, the following example is provided:

sudo defaults write /Library/Preferences/com.apple.loginwindow DesktopPicture "$HOME/Pictures/MyDifferentWallpaper.jpg"

When it comes to monitoring my Mac computers, Bjango’s iStat Menus for Mac is absolutely brilliant. It is an application that I rely on constantly, mainly in part because I place a lot of pressure on my systems frequently. The Bjango development lot have put tremendous amounts of functionality and reliability into not only iStat for Mac, but also with their iStat iPhone monitoring application. There is a very reasonable cost to the iStat Menus of 16$ at the time of this article, and if you demand professional tools as I do, this will not disappoint.

The iStat iPhone application will allow the monitoring of one’s iPhone, and, one can also monitor any Mac or Linux operating system by either WiFi, or thru 3G… provided you have made allowances on your firewall. To monitor your Mac from the iPhone is very simplistic once you have installed Bjango’s iStat Server for Mac OS X, however, the iStat Server for Linux & Solaris is rather tricky to install, and is well worth the efforts I assure you.

Based on Apple’s latest beta release of FaceTime for Mac, I elected to give this application a proper spin. Prior to this, I have not used FaceTime on my iPhone because I utilise a Google Voice number, and the iPhone FaceTime currently requires one’s root number. However, I am glad that I made the time to have a go with the Mac version, because I was quite impressed. The setup, configuration and calls are quite simple really.

It is noteworthy to mention that FaceTime for Mac requires an email address for ‘Mac to Mac’ FaceTime connections, and it builds it’s contact list from one’s local Mac Address Book application. As I manage all of my contacts within my Google Apps account, I was able to sort this rather quickly by having the Mac Address Book sync with my Google Apps contacts.

Dependencies:

• Requires your Apple ID account and password.

Considerations:

• Mac to Mac FaceTime requires the use of an email address to establish a connection.
• Mac to iPhone 4 requires the root number of an iPhone 4 to establish a connection. (Note: Google Voice number is not supported currently).
• Currently have yet to be successful with iPhone 4 to Mac.

Versions Tested:

• Mac OS X Snow Leopard
• Mac FaceTime Beta Version 0.9 (92)

Guide:
Installation of the FaceTime application on one’s Mac is very simplistic, with some of the basic steps provided below.

1. Download the FaceTime for Mac (roughly 14MB) from Apple’s website, and simply place into your ‘Downloads’ folder.

2. With the download completed, navigate to your ‘Downloads’ folder, and DOUBLE+CLICK the FaceTime.dmg file to mount the application for installation.

3. Once mounted, the application installation UI will be presented. DOUBLE+CLICK the FaceTime.mpkg icon, and simply follow the prompts to complete the installation.

4. Once the FaceTime application has been successfully installed, navigate to your ‘Applications’ folder and launch the application by selecting the FaceTime.app icon.

5. When presented, populate your Apple ID and password, then select ‘Sign In’.

6. You will be provided the option of using your Apple ID email address, or supplying an alternate email address. Note: One will receive an email from Apple to register the email address if not already registered.

   Enter the email address you would like to use as your FaceTime email address. This email address will be used by other Mac’s desiring to contact you via FaceTime.

7. If you have not registered an email address that different from your Apple ID, then Apple will require validation by sending an verification email to the FaceTime email address that you specified.

   Once you have received your verification email from Apple, simply click the ‘Verify Now’ link within your email to confirm. You will be required to authenticate with your Apple ID and password.

8. Make sure to note, when you want someone to call you using FaceTime, they simply have to have your email address.

9. With all the steps completed successfully, your FaceTime application will present all of the current contacts in your Mac Address book on the far right side.

10. To initiate the FaceTime call, simply select the phone number for someone using FaceTime on their iPhone 4, or select the email address of someone utilising Mac FaceTime initiate a FaceTime call.

I first came to know of the TrueCrypt application from a colleague a few years ago, and it’s absolutely brilliant, not to mention free. What I particularly require of this application is the volume feature, where one can create a highly encrypted ‘disc’ of any desirable size and formats, thus allowing one to store sensitive documents, databases, passwords, etc.

This brings me neatly to the use of TrueCrypt with Dropbox. With TrueCrypt, I can create a reasonably sized volume, say 128mb in size, and have this container accessible from all of my Mac and Linux computers, and the odd Microsoft Windows computer. Additionally, all changes made, are synchronised with Dropbox’s functionality once you dismount the volume.

I stumbled across an interesting thread on the internet that describes the ‘say‘ command of Mac OS X, and with a bit more research, I was able to piece together the steps required to make a geeky ringtone. I had completely forgotten about the ‘say‘ command, basically because I really never use it on a day to day basis. Although forgotten, it still remains a functional command to have at the ready for developmental use.

Dependencies: None.

Considerations: None.

Versions Tested:

• Mac OS X Snow Leopard
• Apple iTunes 10.0

Guide:
Creating your own geeky ringtone is really quite simple. You will need to choose a voice for a start, and I have composed a list below.

       Syntax: say [-v VoiceName] “Statement to speak”

Female Voices

• $ say -v Agnes "hello world"
• $ say -v Kathy "hello world"
• $ say -v Princess "hello world"
• $ say -v Vicki "hello world"
• $ say -v Victoria "hello world"

Male Voices

• $ say -v Bruce "hello world"
• $ say -v Fred "hello world"
• $ say -v Junior "hello world"
• $ say -v Ralph "hello world"

Novelty Voices

• $ say -v Albert "hello world"
• $ say -v "Bad News" "hello world"
• $ say -v Bahh "hello world"
• $ say -v Bells "hello world"
• $ say -v Boing "hello world"
• $ say -v Bubbles "hello world"
• $ say -v Cellos "hello world"
• $ say -v Deranged "hello world"
• $ say -v "Good News" "hello world"
• $ say -v Hysterical "hello world"
• $ say -v "Pipe Organ" "hello world"
• $ say -v Trinoids "hello world"
• $ say -v Whisper "hello world"
• $ say -v Zarvox "hello world"

Once you have decided upon the voice that you fancy, and what phrase your voice will emulate, all that remains are a few steps to complete the ringtone.

1. Simply launch Application › Utilities › Terminal.app

The following example will produce a aiff (Audio Interchange File Format) file that will be suitable for converting into a ringtone.

say -v Zarvox -o MyRingTone.aiff "Your mobile is talking to you"

2. To convert your produced aiff file into a ringtone, simply import your file into iTunes by selecting File › Add to Library.

3. Once the file has successfully imported, locate the file within your iTunes ‘Music’ folder by simply choosing Music, and then from the iTunes toolbar, select View › As List. This will display all of your music files in a detailed view.

Select and highlight your aiff file, then right click on the file, and select ‘Create AAC Version. (Note: Your import settings must be set to ‘AAC Encoder’. iTunes › Preferences › Import Settings › Import Using).

Once completed, an additional file with the same name will appear in your Music folder, only with a m4a extension.

4. Launch Finder to locate your newly created m4a file. Select your home folder, then navigate to Music › iTunes › iTunes Media › Music › Unknown Artist › Unknown Album.

5. Simply rename the file’s extension from m4a to m4r. The m4r format is recognised by both iTunes and the iPhone as a proper ringtone. Once completed, all that remains is to import your new ringtone properly into iTunes by selecting File › Add to Library.

Your new ringtone should now appear in the iTunes ‘Ringtones’ section. Simply sync your iPhone to introduce the new ringtone onto your mobil.

I will sometimes become engaged with the odd website development, and as such, I always test the website’s rendering and functionality using the state of the art browsers, namely Chrome, Firefox, Opera and Safari. Google’s Chrome browser is most definitely in my top of the range applications for my Macs and Linux systems. I must confess that I was not always impressed with Chrome, however, I decided to ‘think different’ and give it a proper spin. It’s simplicity, speed and secure features impresses even those reluctant few who have difficulty with change.

Apart from Chrome’s Incognito Mode, what I particular love about the Chrome browser is it’s minimalistic design that simplifies a safe browsing experience.

Continuing on with my Parallels Desktop 6 for Mac development and testing, I came across an interesting challenge with Ubuntu. Once Ubuntu is virtualised with Parallels, the login screen resolution remains consistent with the actual display resolution size. However, once Parallels Tools are installed, the login size of the screen becomes 1024×768, regardless of what one sets the display resolution size to.

I suffered this same exact issue with Ubuntu using VMware Fusion, however, the solution for Parallels was much easier and cleaner. After researching the internet for quite some time, I finally found a simple solution which resides in the ‘/etc/X11/xorg.conf‘ file.

When Parallels Tools are installed, the ‘/etc/X11/xorg.conf‘ is configured with Parallels standard settings. When Ubuntu is started, it reads the xorg.conf file for instructions on proper display sizing. Specifically for the login display size, it reads the ‘Modes’ values within the ‘Display’ subsection of ‘Screen’.

That in mind, the login display size will always be displayed at whatever the first entry within the ‘Modes’ values settings. By simply adding one’s desired display size to the beginning of the ‘Modes’ values, its sorted.

Dependencies: The Ubuntu versions listed below must be completely installed, and Parallels Tools installed.

Considerations: Installation of Parallels Tools will allow for the proper enablement of Ubuntu’s Visual Desktop Effects, sound and mouse functionality.

Versions Tested:

• Parallels Desktop 6 for Mac
• Ubuntu 9.04 x64 (Jaunty Jackalope)
• Ubuntu 9.10 x64 (Karmic Koala)
• Ubuntu 10.04.1 LTS x64 (Lucid Lynx)

Installation Guide:
1. Launch a terminal session within Ubuntu by simply selecting from the toolbar; Applications › Accessories › Terminal.

Using your terminal, the following syntax to edit the ‘xorg.conf’ file is provided as an example.

sudo gedit /etc/X11/xorg.conf

2. I have provided my current ‘xorg.conf’ file as an example, where line 49 has my entry for a desired 1920×1200 login display size.

#
# X.Org server configuration file generated by Parallels Guest Tools.
#

# Generic Keyboard section
Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver	"kbd"
	Option	"XkbModel"	"pc105"
	Option	"XkbLayout"	"us"
	Option	"XkbOptions"	"grp:alt_shift_toggle"
EndSection

# Generic Mouse section
Section "InputDevice"
	Identifier	"Generic Mouse"
	Driver	"mouse"
	Option	"SendCoreEvents"	"yes"
EndSection

# Parallels Mouse section
Section "InputDevice"
	Identifier	"Parallels Mouse"
	Driver	"prlmouse"
	Option	"Device"	"/dev/input/mice"
	Option	"Protocol"	"auto"
EndSection

# Parallels Video section
Section "Device"
	Identifier	"Parallels Video"
	Driver	"prlvideo"
EndSection

# Parallels Monitor section
Section "Monitor"
	Identifier	"Parallels Monitor"
	VendorName	"Parallels Inc."
	ModelName	"Parallels Monitor"
EndSection

# Parallels Screen section
Section "Screen"
	Identifier	"Parallels Screen"
	Device	"Parallels Video"
	Monitor	"Parallels Monitor"
	Option	"NoMTRR"
	SubSection	"Display"
		Modes	"1920x1200" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

# DefaultFlags section
Section "ServerFlags"
EndSection

# DefaultLayout section
Section "ServerLayout"
	Identifier	"DefaultLayout"
	Screen	"Parallels Screen"
	InputDevice	"Parallels Mouse"	"CorePointer"
	InputDevice	"Generic Keyboard"	"CoreKeyboard"
	InputDevice	"Generic Mouse"
EndSection

With my ongoing quest to give Parallels Desktop virtualisation a proper spin with Ubuntu, I was quite amazed at how simple it is to install Parallels’ tools. When I was researching the internet on how to accomplish this, I was amazed at how many threads were being written regarding the installation’s complexity. Now mind you, I started with Parallels Desktop 6, and therefore, I am not quite exactly sure all that was required in regards to Parallels’ previous versions.

Dependencies: The Ubuntu versions listed below must be completely installed.

Considerations: Installation of Parallels Tools will allow for the proper enablement of Ubuntu’s Visual Desktop Effects, sound and mouse functionality.

Versions Tested:

• Parallels Desktop 6 for Mac
• Ubuntu 9.04 x64 (Jaunty Jackalope)
• Ubuntu 9.10 x64 (Karmic Koala)
• Ubuntu 10.04.1 LTS x64 (Lucid Lynx)

Installation Guide:
1. With your version of Ubuntu currently running within Parallels virtualisation, simply select from the toolbar; Virtual Machine › Install Parallels Tools

2. A warning is presented (if one has not already disabled it) indicating that you are about to install Parallels Tools, with some brief details on how the task is performed. Select Continue.

3. The Parallels Tools Installation CD will be mounted on your Ubuntu’s desktop. Typically, the folder of the mounted CD will open. With this, you will be able to see the exact path to the installation files. Some Ubuntu versions mount in different locations, so this path is key, and will be used in the next step.

4. Launch a terminal session within Ubuntu by simply selecting from the toolbar; Applications › Accessories › Terminal.

Using your terminal, the following code is provided as an example.

lpurefoy@lpurefoy-desktop:~$ pwd
/home/lpurefoy
lpurefoy@lpurefoy-desktop:~$ cd /media/cdrom0
lpurefoy@lpurefoy-desktop:/media/cdrom0$ ls
install  installer  kmods  tools  version
lpurefoy@lpurefoy-desktop:/media/cdrom0$ sudo ./install
[sudo] password for lpurefoy: ******************

5. Parallels Tools UI installer will then appear with the Welcome window, and will guide you thru the remaining steps. Select Next.

6. To proceed, select Next.

7. Some additional components currently not present, and are required to be downloaded in order to complete the installation. Select Next to continue.

8. The wizard will download the required files. No action is required.

9. Once the downloaded files are in place, the remaining installation steps are completed, and if all went well, a Congratulations window is presented. All that remains is the restart of Ubuntu. Select Reboot.