What Does “On My Mac” mean in Apple Mail? Or “On My Computer”, etc.

 Computers, Education, Tech Support  No Responses »
Oct 072010
 
Apple-Mail-On-my-mac.png

We’ve all seen it.  The little “On My Mac” label in Apple Mail, or Entourage’s “On My Computer” label…

Apple Mail - On my mac.png

Almost every modern mail package offers a similar feature, but many people don’t understand what this means…  So here’s the scoop.

There are three different major ways to handle email:

  • Post Office Protocol (POP 3)
  • IMAP

POP, or Post Office Protocol is an older standard from 1984.  The core issue with POP is it is designed to remove your mail  from the server and it is only stored on your local machine.

Pros:

    • Your Mail is stored locally so the server does not have to have much storage or processing power, excellent for old hardware.
    • Supported by just about every mail package on the market due to it’s age

Cons:

    • Your Mail is stored locally, so you can not share mail between mail clients, without duplicating each mail message.
    • Does not support folder access on the Server (all folders are local to your machine).
    • No multipart messages, or Flag Support

IMAP, or “Internet Message Access Protocol”, was designed in 1988 to fill in gaps that Pop created.  For example, the major issue with pop is that you are unable to share basic information between different mail applications.  So IMAP allows the server to track if a message has been read, deleted, forwarded, etc, so that all IMAP clients are aware of this.

Simply stated if you check your mail from home, when you get to work, your work mail will be read as well.  Anything you delete from your work computer, will also be deleted from your home computer.  You also can have folders that are on the server so you can organize your email, and depending on the installation IMAP supports server based searches.

Pros:

    • Tracks the state of your email, and your mail clients can use this information to keep themselves all in sync.
    • Supported by almost all major email packages
    • More robust, and you can have multiple email programs using the same email account simulateously.
    • Folders can be created, and stored on the server, allowing all applications to access those mail messages.

Cons:

    • Your mail is stored on the server, but most email packages cache the mail locally to help reduce any lag…  As well as granting off-line access to your mail.
    • More complex then POP, and slightly slower, depending on the mail application used.
    • Has a larger “disk storage” requirement than POP3.

So, in Apple Mail, you will see the Server name, and the “Inbox”.  If you have an IMAP connection, you can place folders on the server and organize your mail on the server.  The “On My Mac” or “On My Computer” refer to folders / mailboxes that have been created on your local computer and stored there. If you have a computer failure, and don’t have backups, that mail will be lost with no way to recover it.

Now, Pop3 does have unofficial support for “Keeping your mail on the server for XXX days”.  But this is not a standard and how it works will vary widely  depending on your mail applications.  For example, some applications only allow 7 days, or up to 30…  But even so, your read / delete and reply status will not be stored with the mail.  So if another mail package connects and downloads the mail it will appear to be unread.

IMAP is currently the better choice, assuming it’s available.  In most cases your mail provider should support IMAP connections…

 Posted by Benjamin at 9:21 am  Tagged with: , , , , , ,

Microsoft Office 2011 & Exchange limitations…

 Computers, Education, Macintosh, Reviews  No Responses »
Sep 292010
 

Well, this doesn’t seem to be very clear on the Microsoft site(s) that I have looked at…

But, Office 2011 only supports Exchange 2007 or higher. So if you run Exchange 2003, the only way you’ll be able to connect to the Exchange server is through IMAP, which will eliminate your ability to use your Calendar, Contacts, Public Folders, and Delegation features through the exchange server.

You could still use your local calendar, and contacts, but no server based resources. So Outlook for the Mac is really not that useful for Exchange 2003 users….

In addition, Outlook for the Mac, does not have any interoperability with iCal. You will need to export your iCal calendar and import it into Outlook & cease updating in iCal… If you wish to do your calendaring through Outlook.

This is the second version of Office that Microsoft has virtually crippled in one form or another.

Office 2008 completely removed VBA, which is thankfully returned in Office 2011… But that broke cross-platform functionality, and seriously hampered anyone that uses any sort of macro functionality….

Office 2011 doesn’t work with the main calendaring solution on the Macintosh. Which I suspect that doesn’t have iSync functionality, and that is a large step backwards from Office 2008. Why is it important?

Simply, iSync is a synchronization tool that is built into the OS. It is often leveraged to synchronize Calendar, and Address book data between different applications… This way NOW X can simply sychronize to the iSync database, and not have to know how to read a CSV, Tab deliminated file, or some other more exotic file format. So Office 2008 can then synchronize to that Database and not have to be concerned with who modified it last, and just use the data.

Office 2011 thus can only export a calendar as a Tab-delimited text file, or as a Outlook for Mac Data file… One format that probably will take some effort to import into anything without any issues (Tab-delimined), or another format that nothing else can read (.olm).

For now, I wouldn’t recommend moving to Office 2011 for email purposes. The other applications (Word, Powerpoint, Excel, Document Connection) are solid enough, to deserve to be upgraded. But if you are using email, stick with your current email application.

 Posted by Benjamin at 8:14 am  Tagged with: , , , ,

The 3 Stooges? on my computer? (What is Moe.exe?)

 Computers, Windows  No Responses »
Jul 022010
 

So you’ve found moe.exe running on your Windows system, and have no idea  why it is using memory and CPU time.  You haven’t started it, so is it dangerous?

So What Is It?

Moe.exe is the Mesh Operating Environment, which is the core syncing engine for the new Windows Live Sync Beta, as well as the older Live Mesh.  The new Live Sync is based on Mesh technology, and still includes the same syncing engine.

So what does that mean?  Moe.exe is the application that synchronizes folders between your computers and online storage at SkyDrive. Even if you do not use the SkyDrive system, if you installed Windows Live Essentials Beta, it will be loaded.

You may notice it consuming a fair amount of CPU resources while it is syncing your files or checking for changes.  Unfortunately, Live Sync currently is slightly resource intensive.

Other applications that maybe loaded as well are WLSync, and WLRemoteClient.

The How-to-Geek website has a much more elaborate write up on MOE / Windows Live Sync, you can View the article at What is moe.exe and Why is it Running?)

 Posted by Benjamin at 1:08 pm  Tagged with: , ,

Repairing Disk Permissions

 Add comments
 
9FD79213-8035-4279-9E2D-53BA4A0F6BA9.jpg

Occasionally in OS X some key file ownership and permissions get changed for whatever reason by applications and more frequently, program installers. When ownership and permissions get changed, things just don’t work as they should. The symptoms might be programs quitting unexpectedly, preferences not being remembered, programs not launching, etc. This is where Repair Disk Permissions utility comes in. This utility, which is part of the Apple Disk Utility program, corrects the ownership and permissions according to Apple specifications. Frequently, this corrects many system and program errors. Repair Disk Permissions is a OS X specific utility and UNIX does not have such issues. Hopefully, this a concern and procedure that will go away in the future.

Table of contents

Background Information

Mac OS X is based on OPENSTEP technology, which is similar to Unix. As in Unix-based systems, Mac OS X assigns specific access privileges, known as permissions, to each of your programs, folders, and documents, which are associated with a particular owner, a group, or groups. When an error in your permissions settings occurs, it may cause significant problems. For example, your applications may not launch or your system may respond sluggishly.

Repair Disk Permissions

Rogue installers — applications that temporarily change, but fail to reset, permissions on System-related files or folders during a software installation — are a primary cause of permissions-related problems.  Permissions may be changed after running  a poorly written Installer, or a poorly designed application…  Generally they are not a major concern, but if your system is running sluggish, or you are having odd application problems, it may be worth checking your permissions.  It would not be a bad idea to run an Repair permissions after installing any 3rd party software that uses it’s own custom installer, or after a large number of updates..

Verify or Repair?

In general, given the choice between the Verify or Repair buttons in Disk Utility, select Repair to save time. Verify only checks for problems. If problems are found, you then need to run the corresponding Repair. Repair both verifies and, if problems are found, attempts to perform the required repair.

How does Disk Utility check file permissions?

Many things you install in Mac OS X are installed from package files (whose filename extension is “.pkg”). Each time something is installed from a package file, a “Bill of Materials” file (whose filename extension is “.bom”) is stored in the package’s receipt file, which is kept in  /Library/Receipts/ . If you look in the Receipts folder, for example, you should see all kinds of files that end with .pkg, including some that were created when Mac OS X was installed (for example, BaseSystem.pkg). Don’t worry, these files don’t take up much disk space and you shouldn’t put them in the Trash.

Each of those “.bom” files contains a list of the files installed by that package, and the proper permissions for each file.

In Mac OS X v10.5 or earlier, when you verify or repair disk permissions Disk Utility reviews each of the .bom files in /Library/Receipts/ and compares its list to the actual permissions on each file listed. If the permissions differ, Disk Utility reports the difference (and corrects them if you use the Repair feature).

Does Disk Utility check permissions on all files?

No. Files that aren’t installed as part of an Apple-originated installer package are not listed in a receipt and therefore are not checked. For example, if you install an application using a non-Apple installer application, or by copying it from a disk image, network volume, or other disk instead of installing it via Installer, a receipt file isn’t created. This is expected. Some applications are designed to be installed in one of those ways.

Also, certain files whose permissions can be changed during normal usage without affecting their function are intentionally not checked.

Tip: If you remove receipts from /Library/Receipts/, the files installed by those packages cannot be verified or repaired, which is why you shouldn’t delete things from /Library/Receipts/ . See Disk Utility shows a “No Valid Packages” alert.

Mac OS X v10.5 or later: While started from the Leopard Install DVD, a user’s home directory permissions can be reset using the “Reset Password” utility.

Should I start up from a Mac OS X install disc to repair disk permissions?

When possible, disk permissions should be repaired while started up from a Mac OS X volume (hard disk) that contains Mac OS X, instead of a Mac OS X installation disc. Mac OS X software updates may change permissions on some files to improve security. When this occurs, the version of Disk Utility on the Mac OS X volume is updated to account for the new permissions. Running Disk Utility while started from the Mac OS X volume ensures that the changes made by software updates are preserved.

Mac OS X v10.6 Snow Leopard notes:

  • In Mac OS X v10.6.x, Disk Utility can only verify/repair permissions of other Mac OS X v10.6.x disks. If you need to verify/repair a Mac OS X v10.5.x or earlier Mac OS X version, you will need to use a Leopard or earlier disk.
  • You don’t need to repair disk permissions prior to installing Mac OS X v10.6 over a previously-installed OS. The Installer will do this automatically.

Repairing your Disk Permissions

  1. To open Disk Utility, from your Applications folder, open your Utilities folder and double-click the Disk Utility icon.
  2. In the column on the left, click your startup disk’s icon.   Typically this is labelled “Macintosh HD”.
  3. Click the First Aid tab.
  4. Click Repair Disk Permissions. Disk Utility will reset any files and folders with incorrect settings.

Please note, under Mac OS X Leopard (10.5.x) the Repair Disk Permissionis may take up to 30 minutes to an hour or so minutes to run.  Under Tiger (10.4) this was significantly shorter (5-10 minnutes), and under Snow Leopard (10.6) it usually takes about 15-30 minutes.

Warning & Error messages

According to Apple’s Knowledge base, the following warnings are  messages that may appear in the Disk Utility log window when repairing disk permissions should be ignored.  You can also usually ignore any “ACL found but not expected…” message. These messages can occur if you change permissions on a file or directory. These messages are accurate but are generally not a cause for concern.

  •  Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources/DiskManagementTool" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Resources/Locum" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconfig" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writeconfig" has been modified and will not be repaired.
  • Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not be repaired.
  • Permissions differ on "Library/Application Support/Apple/ParentalControls/ALRHelperJobs", should be drwxrwxr-x , they are drwxr-xr-x .
  • Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
  • Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
  • Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
  • Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
  • Warning: SUID file "usr/bin/setregion" has been modified and will not be repaired.
  • Permissions differ on "Library/Application Support/Apple/ParentalControls/ContentFiltering", should be drwxrwxr-x , they are drwxr-xr-x .
  • Permissions differ on "Library/Application Support/Apple/ParentalControls", should be drwxrwxr-x , they are drwxr-xr-x .
  • Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner" has been modified and will not be repaired.
  • Warning: SUID file "System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper" has been modified and will not be repaired.
  • Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r--.
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r--.
  • Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-
  • Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeComponents.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTimeJava/QuickTimeJava.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/AppleVAH264HW.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTime3GPP.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeH264.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeIIDCDigitizer.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeImporters.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeMPEG.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeMPEG4.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeStreaming.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/QuickTime/QuickTimeVR.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "Library/Internet Plug-Ins/QuickTime Plugin.plugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Library/Internet Plug-Ins/QuickTime Plugin.webplugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/Frameworks/QTKit.framework/Versions/A/Resources/QTKitIBPlugin.ibplugin/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/Spotlight/QuickTime.mdimporter/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "Library/Audio/Plug-Ins/HAL/iSightAudio.plugin/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/Frameworks/QuickTime.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/AnnotationInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/AudioSettingsInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/DataRefInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/HintTrackInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/NetworkInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/SettingsInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "Applications/QuickTime Player.app/Contents/PlugIns/VisualTrackInspector.propPane/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/Resources/QTMediaKeys.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/Resources/QTMime.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTAdvanced.prefPane/Contents/Resources/QTTransport.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTPlugIn.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegister.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegister.prefPane/Contents/Resources/QTAbout.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTStreaming.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTUpdate.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileDeviceHelper.app/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobileSync.app/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/CodeResources", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are -rw-r--r-- .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/Info.plist", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/Info.plist", should be -rw-rw-r-- , they are -rw-r--r-- .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/MacOS/JavaPluginCocoa", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/MacOS/JavaPluginCocoa", should be -rwxrwxr-x , they are -rwxr-xr-x .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/MacOS", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/MacOS", should be drwxrwxr-x , they are drwxr-xr-x .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/Resources/Localizable.strings", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/Resources/Localizable.strings", should be -rw-rw-r-- , they are -rw-r--r-- .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/Resources", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/Resources", should be drwxrwxr-x , they are drwxr-xr-x .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/version.plist", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents/version.plist", should be -rw-rw-r-- , they are -rw-r--r-- .
  • Group differs on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents", should be 80, group is 0.
  • Permissions differ on "Library/Internet Plug-Ins/JavaPluginCocoa.bundle/Contents", should be drwxrwxr-x , they are drwxr-xr-x .
  • Permissions differ on "System/Library/Components/AudioCodecs.component/Contents/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • Permissions differ on "System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrwxr-xr-x .
  • The following messages that may appear in Mac OS X Server may also be safely ignored:
  • Permissions differ on "private/var/db/openldap/openldap-data", should be drwxr-xr-x , they are drw------- .
  • Permissions differ on "private/etc/postfix/master.cf", should be -r--r--r-- , they are -rw-r--r-- .
  • Permissions differ on "usr/share/caldavd/lib/python/dsattributes.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Permissions differ on "usr/share/caldavd/lib/python/dsquery.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Permissions differ on "usr/share/caldavd/lib/python/pydirector/pdamp.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Permissions differ on "usr/share/caldavd/lib/python/pydirector/pdconf.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Permissions differ on "usr/share/caldavd/lib/python/pydirector/pdmain.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Permissions differ on "usr/share/caldavd/lib/python/pydirector/pdnetworktwisted.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Permissions differ on "usr/share/caldavd/lib/python/twisted/web2/filter/gzip.pyc", should be -rw-r--r-- , they are -rw-r----- .
  • Any messages that contains the word "WebObjects"


    •  Posted by Benjamin at 8:17 am  Tagged with: , , , , , , , , , , , , , , , ,

    How do I migrate my information to a new Macintosh?

     Computers, Macintosh, Tech Support  No Responses »
    Dec 282009
     

    First, the brick & mortar Apple Stores will offer to migrate your data for free, if the new system is purchased from them, the main hassel is the wait, and bringing in the old system.

    Alternatively, on the new system, as soon as it is booted will offer to migrate the old computers data. All you would need is one of the following an ethernet cable, Wireless network, or a Firewire cable.

    see http://support.apple.com/kb/HT3322

    To use Migration Assistant, both Macs must be FireWire-equipped or be connected to the same Ethernet or wireless network.

    Tip: If you have a MacBook Air or MacBook (13-inch, Aluminum, Late 2008), make sure both computers are connected to the same Ethernet or wireless network. See this article.

    Note: If you experienced issues while using some files or applications on your previous computer, you may not want to transfer those files and applications to your new computer. If you do, you may transfer issues or incompatible files.

    To transfer files via Migration Assistant Before performing migration, use Software Update on your older Mac to ensure you get the latest updates for Mac OS X. If you’re using a portable Mac, make sure the power cable is connected. On your new Mac, open Migration Assistant, located in the Utilities folder in your Applications folder. Read the Introduction screen, then click Continue. If a dialog appears, type your admin password, then click OK. In the Migration Method screen, select “From another Mac,” then click Continue. If you are using FireWire, connect a FireWire cable between your new Mac and your earlier Mac, then click Continue. If you are using a wireless network, click “Use Network to transfer files and important settings over a wireless network”, then click Continue.

    Follow the instructions in Migration Assistant to restart your earlier Mac if necessary. Select the hard disk and user accounts from which you want to transfer, and select whether you want to transfer applications, files and folders, or your Library folder. Note: When you first open a transferred application on your new computer, you may need to re-enter the application’s serial number or registration code.

    Select whether you want to use your old network, time zone, and Sharing settings, and then click Transfer. When Migration Assistant is finished transferring files, click Quit.

     Posted by Benjamin at 9:23 am  Tagged with: , , , , , , , , ,

    Why is USB slower than Firewire?

     Computers, Hardware, Macintosh, Tech Support, Windows  No Responses »
    Dec 252009
     

    Take this quote from Macworld:

    When we connected the MacBook Pro to a 2TB Western Digital My Book Studio drive and copied a 1GB file to it from the internal hard drive, we found that it took 23 percent less time over FireWire 400 than over USB 2.0. Duplicating that file using FireWire 400 on the WD drive took 10 percent less time than when run over USB 2.0. To see how the different connections performed in more typical backup tasks, we copied over a 2.5GB folder containing 5000 individual files and folders. In that test, we found the FireWire 400 transfer to be 26 percent faster than USB 2.0. Using AJA’s System Test application, we found the MacBook Pro’s FireWire 400 connection to be 46 percent faster than USB in the writing tests. In the reading tests, however, the edge went to USB, which was nine percent faster than FireWire 400.

    But this doesn’t make sense, does it?

    USB 1, is primarily aimed at keyboards, joysticks, and other low speed transfers, after all, it is limited to 12 Mbit/s.

    USB 2, upgrades the transfer rate to a peak of 480 Mbit/s, and is quite useful for large file transfers (eg, Hard Drives, Optical drives, etc…).

    USB 3, is not yet finalized, and while on paper it will be significantly faster than USB 2, it is not yet ready for mainstream use.

    Firewire 400, can transfer data at 100,l 200 or 400 Mbit/s half-duplex (12, 24, or 49 megabytes/second).

    Firewire 800, allows a transfer rate of 786 Mbit/s full-duplex, and is backward compatible to Firewire 400.

    In addition, there is a S1600, S3200, S800T, and (unreleased at this point) P1394d for the firewire family, each of these are significantly faster, but may require different cables (eg Fiber).

    So why is Firewire 400 (400 Mbit/s) faster than USB (480 Mbit/s)?

    Sadly, it is due to hardware limitations.

    • USB relies on the host-processor to manage low-level communications, where Firewire delegates the low-level communications to the Firewire devices themselves.  This means less or no CPU usage during data transfers.
    • Being host based, USB requires every packet to be processed by the CPU.  This copying a file from one USB drive, to another, requires the file to be “sent” to the CPU, and then back to the other drive.  Thus taking roughly 2x bandwidth, in comparison to the Firewire drive(s).
    • USB is based on a tiered-star topology, which may require multiple devices to pass communications along thus reducing the available bandwidth between the devices communicating.
    • USB 1.x, and 2 can not directly communicate with the CPU, the CPU must poll the devices.  This means that the data transfers can not occur until the CPU polls the device again.
    • USB typically only have a single single USB controller, which means the bandwidth is divided between the ports (eg 480 Mbit/s / 4 ports = 120 Mbit/s per port).  Some motherboards do have multiple controllers, but even then there are typically only 2 controllers, for 6 or 8 USB ports.
    • In most cases these controllers are connected to the Southbridge, which is typically limited to 120 or 180 MB/s.
    • The 480Mbit/s measurement is of Peak performance (eg Burst rate), where Firewire’s speed is sustained.  So while USB is faster, it can not sustain that rate.

    Overall, both USB and Firewire have a high rate of speed for data transfers, but Firewire currently has a slight edge.  Will this difference in speed matter for most people, not necessarily, but for any time intensive data transfer Firewire will be faster.  At least until USB 3 is released, and even then Firewire 1600 or 3200 would be faster, and they are already on the market…

     Posted by Benjamin at 11:38 am  Tagged with: , , , , ,

    Internet Explorer is Slow? Speed it up…

     Computers, Tech Support, Virus Related, Windows  1 Response »
    Nov 112009
     

    Ever wonder why your internet connection seems slow…  Part of it maybe the web browser your using…Internet Explorer, especially the earlier versions of it (6,  and 7), can be rather foolish with it’s default settings….

    How To Delete Temporary Internet Files and Cookies

    Internet Explorer caches web pages you visit and cookies coming from those pages. While designed to speed up browsing, if left unchecked the burgeoning folders can sometimes slow IE to a crawl or cause other unexpected behavior. In general, the less is more principal works well here – keep the Internet Explorer cache small and clear it often. Continue reading »

     Posted by Benjamin at 11:09 am  Tagged with: , , , ,

    Where did these directories come from?

     Computers, Macintosh, Tech Support  No Responses »
    Oct 292009
     

    I just had someone ask me about some folder’s they found on there system…  They were concerned that they folder’s in question where taking up a bit of space, and they wanted to clean up there hard drive…

    For example:

    • /Developer (from old Mac)
    • /opt (from old Mac)

    The common factor, was the “(from old Mac)”…. I was able to safely say that it was safe to remove the folders, assuming they had removed any data they needed from the folders…  Why could I do safely say that?

    “(from old Mac)” is what the Migration Utility add’s to folders that it is copying over from your OLD MAC, when there is a naming conflict.

    In otherwords, it didn’t overwrite the new developer tools that came with your new system, it gave the old copy from your old system a slightly different name by appending “(from old Mac)” to the folder name.

    Yes, you can safely remove them, assuming there isn’t some data that you need from those folders…

     Posted by Benjamin at 12:53 pm  Tagged with:
    Page 1 of 3 1 2 3
    © 2011 The Matrix Data BankSuffusion theme by Sayontan Sinha