Monday, September 24, 2012

10 tips for speeding up Outlook

If you've used Microsoft Outlook for a while, you know that it can slow down… way down. In fact, when not looked after, Outlook can become nearly useless. Fortunately, there are several things you can do to make Outlook not only usable, but significantly improved. And none of these techniques requires a single configuration change to your Exchange server (IMAP or POP3).

Of course, some of these suggestions might seem to have a bit more "'duh" factor than others. But you never know what level of skills you're dealing with, so we'll cover all the bases. In the end, you should have a much faster Outlook experience.

1: Update Windows

Many people don't realize that with Windows updates, the updates for Microsoft Office are also "hidden." But it's not just the Office updates that can help speed up Outlook. Make sure you allow the updates to happen. Why? There are times when Microsoft might update Exchange. In some cases, those updates can either break or cause problems with the communication between Outlook and Exchange. Or Microsoft might issue a patch to the application to resolve a speed issue or security hole.

2: Download complete items

When you connect Outlook with either IMAP or POP3, you should have Outlook set up to download the complete message (instead of just the header). If you do this, Outlook won't have to sync with the server every time you click on a new item (as it will already be in the data file.) How you do this will depend upon which version of Outlook you're using. But basically, you're looking for the setting Download Complete Item Including Attachments.

3: Archive your Inbox

I can't tell you how many times I see clients with thousands upon thousands (and in some cases tens of thousands) of emails in their Inbox. This can cause serious issues, especially when using PST files. Instead of just letting those Inbox folders grow to outrageous proportions, set up auto archiving so that your Inbox retains only a portion of those emails. I like to tell clients to keep the current and previous months' email in the Inbox and archive everything else. When you archive, you effectively create a new data file, so Outlook doesn't have to strain against the weight of an oversize PST or OST file

4: Use Cached Exchange Mode

If you use Cached Exchange Mode in Outlook, you effectively take the data file from the server (PST) and cache it on your local machine (OST). This can go a long way toward speeding up your Outlook experience because Outlook doesn't have to read its data file across a network. Instead, all it has to do is read the locally stored data file. This option (obviously) is available only when connecting Outlook with an Exchange server.

5: Compact your PST file

When the Outlook PST file gets out of hand, a built-in tool can keep the size of that file under control. One of the issues is that even when you delete email from your Inbox, the size of the PST file may remain the same. If you're using Outlook 2010, you can go to Account Settings | Data Files and select the data file to be compacted. Once you've selected the file click Settings | Advanced | Outlook Data File Settings and click Compact Now. Depending on the size of your data file, this process can take some time.

6: Repair your PST file

Scanpst is often my go-to tool when Outlook is acting off kilter. It will scan through your data file and look for data inconsistencies and errors. Here's the thing about Scanpst — it's not always the easiest tool to find. Do yourself a favor and search through your C drive to locate the Scanpst.exe file. Make note of its location (usually within the Office installation folder). But be forewarned: This tool can cause PST files to become unusable. Make sure you back up that data file before you start the repair tool. Fortunately, should Scanpst find errors, it will prompt you to make a backup before it attempts to fix the errors.

7: Cut down on the published and shared calendars

Yes, it's easy to publish and share your calendars with others. The problem is, the more you do it, the more drag you're putting on Outlook. The more data Outlook has to share and pull down from the Internet, the slower it will perform. Sure, it's fine to have one or two shared calendars (and even more if you have a lightning-fast data pipe). Just know that the more data you have to push and pull, the slower your connection will be.

8: Disable RSS

By default, Outlook will sync RSS feeds from Internet Explorer to the RSS reader in Outlook. If you have a lot of RSS feeds bookmarked in IE, that syncing could easily bring Outlook to a crawl. Disable this feature (if you don't use Outlook as an RSS reader) from within Outlook 2010 by going to Options | Advanced and then unchecking both options under RSS Feeds.

9: Disable add-ins

How many times have you installed some program only to find it installed something else behind your back? This can happen to Outlook as well as Internet Explorer. Sometimes those add-ins can cause major Outlook slowdowns. To find out what add-ins you have installed in Outlook 2010, go to Options | Add-ins. Select COM Add-ins from the drop-down and click the Go button. The resultant window will list all add-ins available to Outlook. Search through this list and uncheck any that might seem suspect.

10: Fix ShoreTel Windows 7 integration

If you use the ShoreTel Communicator, you might notice some issues when trying to open and use Outlook. The problem lies in an incompatibility issue between ShoreTel and Windows 7. The fix is simple. Open up the Task Manager and look for a process called Agent.exe. Right-click that entry and click Properties |Compatibility. Choose the Run This Program In Compatibility Mode For option and then select Windows XP (Service Pack 3).

Other tricks?

There's no reason why anyone should have to struggle with a bogged down Outlook that will have you pulling your hair out strand by strand. These tips should help you enjoy a much speedier and reliable Outlook experience.

Thursday, September 20, 2012

Beginning of SQL Server Architecture – Terminology

SQL Server Architecture is a very deep subject. Covering it in a single post is an almost impossible task. However, this subject is very popular topic among beginners and advanced users.  Here Anil Kumar who is expert in SQL Domain to help Pinal write  a simple post about Beginning SQL Server Architecture. As stated earlier this subject is very deep subject and in this first article series he has covered basic terminologies. In future article he will explore the subject further down. Anil Kumar Yadav is Trainer, SQL Domain, Koenig Solutions. Koenig is a premier IT training firm that provides several IT certifications, such as Oracle 11g, Server+, RHCA, SQL Server Training, Prince2 Foundation etc.


In this Article we will discuss about MS SQL Server architecture.

The major components of SQL Server are:

  1. Relational Engine
  2. Storage Engine
  3. SQL OS

Now we will discuss and understand each one of them.

1) Relational Engine: Also called as the query processor, Relational Engine includes the components of SQL Server that determine what your query exactly needs to do and the best way to do it. It manages the execution of queries as it requests data from the storage engine and processes the results returned.

Different Tasks of Relational Engine:

  1. Query Processing
  2. Memory Management
  3. Thread and Task Management
  4. Buffer Management
  5. Distributed Query Processing

2) Storage Engine: Storage Engine is responsible for storage and retrieval of the data on to the storage system (Disk, SAN etc.). to understand more, let's focus on the concepts.

When we talk about any database in SQL server, there are 2 types of files that are created at the disk level – Data file and Log file. Data file physically stores the data in data pages. Log files that are also known as write ahead logs, are used for storing transactions performed on the database.

Let's understand data file and log file in more details:

Data FileData File stores data in the form of Data Page (8KB) and these data pages are logically organized in extents.

Extents: Extents are logical units in the database. They are a combination of 8 data pages i.e. 64 KB forms an extent. Extents can be of two types, Mixed and Uniform. Mixed extents hold different types of pages like index, system, data etc (multiple objects). On the other hand, Uniform extents are dedicated to only one type (object).

Pages: As we should know what type of data pages can be stored in SQL Server, below mentioned are some of them:

  • Data Page: It holds the data entered by the user but not the data which is of type text, ntext, nvarchar(max), varchar(max), varbinary(max), image and xml data.
  • Index: It stores the index entries.
  • Text/Image: It stores LOB ( Large Object data) like text, ntext, varchar(max), nvarchar(max),  varbinary(max), image and xml data.
  • GAM & SGAM (Global Allocation Map & Shared Global Allocation Map): They are used for saving information related to the allocation of extents.
  • PFS (Page Free Space): Information related to page allocation and unused space available on pages.
  • IAM (Index Allocation Map): Information pertaining to extents that are used by a table or index per allocation unit.
  • BCM (Bulk Changed Map): Keeps information about the extents changed in a Bulk Operation.
  • DCM (Differential Change Map): This is the information of extents that have modified since the last BACKUP DATABASE statement as per allocation unit.

Log File: It also known as write ahead log. It stores modification to the database (DML and DDL).

  • Sufficient information is logged to be able to:
    • Roll back transactions if requested
    • Recover the database in case of failure
    • Write Ahead Logging is used to create log entries
      • Transaction logs are written in chronological order in a circular way
      • Truncation policy for logs is based on the recovery model

3) SQL OS: This lies between the host machine (Windows OS) and SQL Server. All the activities performed on database engine are taken care of by SQL OS. It is a highly configurable operating system with powerful API (application programming interface), enabling automatic locality and advanced parallelism. SQL OS provides various operating system services, such as memory management deals with buffer pool, log buffer and deadlock detection using the blocking and locking structure. Other services include exception handling, hosting for external components like Common Language Runtime, CLR etc.

I guess this brief article gives you an idea about the various terminologies used related to SQL Server Architecture. In future articles we will explore them further.

Guest Author 

The author of the article is Anil Kumar Yadav is Trainer, SQL Domain, Koenig Solutions. Koenig is a premier IT training firm that provides several IT certifications, such as Oracle 11g, Server+, RHCA, SQL Server Training, Prince2 Foundation etc.

Reference: http://blog.sqlauthority.com

Tuesday, September 18, 2012

Web Application Projects versus Web Site Projects in Visual Studio

Ref.: MSDN


In Visual Studio you can create web application projects or web site projects. You create or open a web application project by choosing New Project or Open Project in the Visual Studio File menu. You create or open a web site project by choosing New Web Site or Open Web Site in the File menu.

Each type of project has advantages and disadvantages, and it is helpful to understand the differences between them in order to select the best project type for your needs. You must select the appropriate project type before you create a project, because it is not practical to convert from one project type to the other.

Note Note

For some scenarios, you do not have a choice. For example, if you want to create an ASP.NET MVC application, you must use a web application project.

This topic contains the following sections:

Scenarios


Scenarios in which web application projects are the preferred choice include the following:

  • You want to be able to use the Edit and Continue feature of the Visual Studio debugger.
  • You want to run unit tests on code that is in the class files that are associated with ASP.NET pages.
  • You want to refer to the classes that are associated with pages and user controls from standalone classes.
  • You want to establish project dependencies between multiple web projects.
  • You want the compiler to create a single assembly for the entire site.
  • You want control over the assembly name and version number that is generated for the site.
  • You want to use MSBuild or Team Build to compile the project. For example, you might want to add prebuild and postbuild steps.
  • You want to avoid putting source code on a production server.
  • You want to use the automated deployment tools that are available in Visual Studio.

Scenarios in which Web site projects are the preferred choice include the following:

  • You want to include both C# and Visual Basic code in a single web project. (By default, a web application is compiled based on language settings in the project file. Exceptions can be made, but it is relatively difficult.)
  • You want to open the production site in Visual Studio and update it in real time by using FTP.
  • You do not want to have to explicitly compile the project in order to deploy it.
  • If you do precompile the site, you want the compiler to create multiple assemblies for the site, which can include one assembly per page or user control, or one or more assemblies per folder.
  • You want to be able to update individual files in production by just copying new versions to the production server, or by editing the files directly on the production server.
  • If you precompile the site, you want to be able to update individual ASP.NET web pages (.aspx files) without having to recompile the entire site.
  • You like to keep your source code on the production server because it can serve as an additional backup copy.

Summary of Differences


The following table summarizes the main differences.

Area

Web application projects

Web site projects

Project file structure

A Visual Studio project file (.csproj or .vbproj) stores information about the project, such as the list of files that are included in the project, and any project-to-project references.

There is no project file (.csproj or .vbproj). All the files in a folder structure are automatically included in the site.

Compilation

  • You explicitly compile the source code on the computer that is used for development or source control.
  • By default, compilation of code files (excluding .aspx and .ascx files) produces a single assembly.
  • The source code is typically compiled dynamically (automatically) by ASP.NET on the server the first time a request is received after the site has been installed or updated.

You can precompile the site (compile in advance on a development computer or on the server).

  • By default, compilation produces multiple assemblies.

Namespaces

Explicit namespaces are added to pages, controls, and classes by default.

Explicit namespaces are not added to pages, controls, and classes by default, but you can add them manually.

Deployment

  • You copy the assembly to a server. The assembly is produced by compiling the application.
  • Visual Studio provides tools that integrate with Web Deploy (the IIS web deployment tool) to automate many deployment tasks.
  • You copy the application source files to a computer that has IIS installed on it.
  • If you precompile the site on a development computer, you copy the assemblies produced by compilation to the IIS server.
  • Visual Studio provides tools for deployment, but they do not automate as many deployment tasks as the tools available for web application projects.


Project File Structure


Web application projects use Visual Studio project files (.csproj or .vbproj) to keep track of information about the project. This makes it possible to specify which files are included in or excluded from the project, and therefore which files are compiled during a build.

For web site projects, all files in a folder structure are automatically considered to be included in the web site. If you want to exclude something from compilation, you must remove the file from the web site project folder or change its file-name extension to an extension that is not compiled and is not served by IIS.

An advantage of using project files in web application projects is the following:

  • It is easy to temporarily remove files from the site but still make sure that you do not lose track of them, because they remain in the folder structure. For example, if a page is not ready to be deployed, you can temporarily exclude it from the build without deleting it from the folder structure. You can deploy the compiled assembly, and then include the file in the project again. This is especially important if you are working with a source control repository.

An advantage of using folder structure without project files in Web site projects is the following:

  • You do not have to manage the project's structure exclusively in Visual Studio. For example, you can copy files into the project or delete them from the project by using File Explorer.

Compilation


For web application projects, you typically build the project in Visual Studio or by using the ASP.NET batch compiler on a computer that is not the production IIS server. All code-behind class files and standalone class files in the project are compiled into a single assembly, which is then put in the web application project's Bin folder. (The .aspx and .ascx files are compiled dynamically in a manner similar to what is done for web site projects.)

For web site projects, you do not have to manually compile the project. web site projects are typically compiled dynamically by ASP.NET (on both the development computer and the production IIS server). You can choose between batch compilation mode, which typically produces one assembly per folder, and fixed compilation mode, which typically produces one assembly for each page or user control.

Advantages of the compilation model for web application projects include the following:

  • You can use MSBuild to create a custom batch-compilation process.
  • It is easy to specify assembly attributes such as name and version.
  • Compiling in advance makes sure that users do not have to wait while the site compiles on the production server. (If the site is very large, dynamic compilation of a web site project might take a noticeable amount of time. Dynamic compilation occurs when a request for a site resource is received after an update to the site, and the request that triggers compilation might be delayed while the required resources are compiled. If the delay is unacceptable, you can precompile the site. However, then some of the advantages of dynamic compilation are lost.)
  • You have complete control over where you put code files in the project folder structure, and how you how classes in the project refer to each other. (Dynamic compilation requires that the source code for any classes that are used throughout the site must be in the App_Code folder. You cannot refer to a page or user control class from a class in App_Code.)

Advantages of the compilation model for Web site projects include the following:

  • You can test specific pages regardless of the state of other pages. This is because running an individual page does not require that the whole site compile successfully, only the page and any components it depends on, such as code in the App_Code folder or the Global.asax file. (In a web application project, if there are compilation errors anywhere in the site, you cannot create the assembly and therefore cannot test even the pieces of the site that compile.)
  • It is easy to update a Web site in production. You can update individual source code files on the production server without having to explicitly recompile the site. You can update individual files that are ready for deployment even if other files are not ready due to compile errors. You can also open the Web site on the production IIS server directly in Visual Studio and update the Web site in real time.
  • Precompiling to multiple assemblies can have a performance advantage in some scenarios. A typical example is a site that has many pages with lots of code written for them. Most of the pages are rarely requested and only some are used frequently. If you compile a site like this into multiple assemblies, the production server can load only the assemblies that are required for the current requests. If a page is not requested, its corresponding assembly is not loaded.

Note Note

There is no difference in performance between a web site project and a web application project. The only significant exceptions are the ones that have already been noted, and as a practical matter they apply only to very large sites. The first request to the web site might require the site to be compiled, which can result in a delay. And if the web site is running on an IIS server that is short on memory, including the entire site in a single assembly might use more memory than would be required for multiple assemblies.

Deployment


To deploy a web application project, you copy the assembly that is created by compiling the project to an IIS server. In contrast, to deploy a web site project, you typically copy the project source files to an IIS server.

Advantages of the deployment strategy for web application projects include the following:

  • You can avoid deploying source code to the IIS server. In some scenarios, such as shared hosting environments, you might be concerned about unauthorized access to source code on the IIS server. (For a web site project, You can avoid this risk by precompiling on a development computer and deploying the generated assemblies instead of the source code. However, in that case you lose some of the benefits of easy site updates.)
  • Deployment often involves other tasks in addition to copying assemblies or code to a server. For example, database scripts might have to run in production, and connection strings in the Web.config file might have to be changed for a production server. Visual Studio provides tools such as one-click publish that work with web application projects to automate many of these tasks. These tools are not available for web site projects.

Advantages of the deployment strategy for web site projects include the following:

  • If you make a small change to a web site, you do not have to redeploy the whole site. Instead, can copy just the changed file or files to the production IIS server. You can also edit files directly on the production server. (Because a web application project's code files are compiled into a single assembly file, you must deploy the whole site even for small changes, unless the only change is to an .aspx or .ascx file.) 


Friday, September 14, 2012

RAID in Linux

From: NextStep4IT


The term RAID is an acronym for the phrase, Redundant Array of Independent Disks. RAID is a way of combining the storage available across multiple disks and supplying users a single, unified virtual device.
RAID can be used to provide:

  • data integrity
  • fault tolerance
  • improved performance
  • greater storage capacity

Hard disks are mechanical devices involving moving parts and unfortunately tend to fail over time. There are also physical limits to the speed at which data can be read and/or written to disks. RAID helps mitigate this risk by protecting data stored on hard disks and improving disk performance by writing the data to multiple
physical locations according to several different schemas, known as "RAID Levels". Furthermore, RAID can be provided by either dedicated, specialized hardware or by the operating system at a virtual layer.



Hardware RAID vs. software RAID?

Hardware RAID solutions exist that operate as dedicated devices, usually as PCI expansion cards or directly on the motherboard. The independent disks attach to the hardware interface. In a true hardware RAID, the operating system simply writes data to the hardware RAID controller which handles the multiplicitous reads and writes to the associated disks. Other so−called hardware RAIDs rely on special drivers to the operating system; these act more like software RAIDs in practice. With current technology, hardware RAIDconfigurations are generally chosen for very large RAIDs.

Additionally, some operating systems, including Linux®, provide RAID functionality within a software layer.RAID partitions are logically combined and a virtual device appears to higher layers of the operating system in place of the multiple constituent devices. This solution is often a high−performance and inexpensive alternative available for RAID users.

 

RAID levels

There are many RAID levels. It will be impossible to list them all here. Here we mention the most common & most important RAID types, all of which are fully supported by Linux.

 

RAID0 (Striping)

 

This level is achieved by grouping 2 or more hard disks into a single unit with the total size equaling that of all disks used.

Practical example: 3 disks, each 80GB in size can be used in a 240GB RAID0 configuration.

RAID0 works by breaking data into fragments and writing to all disk simultaneously. This significantly improves the read and write performance.

On the other hand, no single disk contains the entire information for any bit of data committed. This means that if one of the disks fails, the entire RAID is rendered inoperable, with unrecoverable loss of data.

RAID0 is suitable for non-critical operations that require good performance, like the system partition or the /tmp partition where lots of temporary data is constantly written. It is not suitable for data storage.

Usable Space in Raid level0 = (smallest disk) * (no. of disks)

RAID1 (Mirroring)

 

This level is achieved by grouping 2 or more hard disks into a single unit with the total size equaling that of the smallest of disks used.

 

This is because RAID1 keeps every bit of data replicated on each of its devices in the exactly same fashion, create identical clones. Hence the name, mirroring. Practical example: 2 disks, each 80GB in size can be used in a 80GB RAID1 configuration.

 

Usable space of Raid level1= smallest-disk

On a side note, in mathematical terms, RAID1 is an AND function, whereas RAID 0 is an OR. Because of its configuration, RAID1 reduced write performance, as every chunk of data has to be written n times, on each of the paired devices. The read performance is identical to single disks.Redundancy is improved, as the normal operation of the system can be maintained as long as any one disk is functional.

RAID 1 is suitable for data storage, especially with non-intensive I/O tasks.

 

 

RAID5 

 

This is a more complex solution, with a minimum of three devices used. Two or more devices are configured in a RAID0 setup, while the third (or last) device is a parity device. If one of the RAID 0 devices malfunctions, the array will continue operating, using the parity device as a backup. The failure will be transparent to the user, save for the reduced performance.

RAID 5 improves the write performance, as well as redundancy and is useful in mission-critical scenarios, where both good throughput and data integrity are important. RAID 5 does induce a slight CPU penalty due to parity calculations.

Usable Space for Raid Level5 = smallest-disk*(no of disk -1)

 

Linear RAID

 

This is a less common level, although fully usable. Linear is similar to RAID0, except that data is written sequentially rather than in parallel. Linear RAID is a simple grouping of several devices into a larger volume, the total size of which is the sum of all members. For instance, three disks the sizes of 40, 60 and 250GB can be grouped into a linear RAID the total size of 350GB.

 

Linear RAID provides no read/write performance, not does it provide redundancy; a loss of any member will render the entire array unusable. It merely increases size. It's very similar to LVM. Linear RAID is suitable when large data exceeding the individual size of any disk or partition must be used.

Now, move backup to tape or other server:

 

Nested RAID Levels

 

RAID0+1

 

Exapmle of RAID Level 0+1

 

RAID 0+1 (also called RAID01), is a RAID level used for both replicating and sharing data among disks.The minimum number of disks required to implement this level of RAID is 3 (first, even numbered chunks on all disks are built – like in RAID0 – and then every odd chunk number is mirrored with the next higher even neighbour) but it is more common to use a minimum of 4 disks.

 

The difference between RAID0+1 and RAID 1+0 is the location of each RAID system — RAID0+1 is a mirror of stripes although some manufacturers (e.g. Digital/Compaq/HP) use RAID0+1 to describe striped mirrors, consequently this usage is now deprecated so that RAID0+1 and RAID1+0 are replaced by RAID10 whose definition correctly describes the correct and safe layout, i.e. striped mirrors.

RAID1 + 0

RAID1+0, sometimes called RAID1&0 or RAID10, is similar to a RAID0+1 with exception that the RAID levels used are reversed — RAID10 is a stripe of mirrors.

Hard disks are mechanical devices involving moving parts and unfortunately tend to fail over time. There are also physical limits to the speed at which data can be read and/or written to disks. RAID helps mitigate this risk by protecting data stored on hard disks and improving disk performance by writing the data to multiple

Monday, September 10, 2012

10 things you should know before buying a Galaxy S III smartphone

When it was time to upgrade from my Galaxy Nexus (in part because my husband was anxious to get my hand-me-down), the choice seemed obvious. I liked the Nexus a lot, but there were a couple of things I didn't like about it. One biggie was the lack of a microSD card slot for expanding storage. I also longed for even more screen real estate than I got with the Nexus's 4.65 inch screen (which includes the onscreen buttons). Finally, the camera quality on the Nexus, although much better than many phones, wasn't up to what I had come to expect from my previous (HTC) Androids.

The Galaxy S III seemed to fulfill my wish list, and more. With a gorgeous 4.8 inch Super AMOLED screen (and the buttons beneath the display so they don't take up any of that space), microSD support, and a reportedly excellent camera, it was my dream come true. Or was it? I got my S III more than a week ago, and I've played with it enough to discover both some pleasant surprises and a few gotchas. If you're thinking about getting an S III, and especially if you're trading up from a Nexus, here are a few things you might want to know to help you make the decision.

The good

First, let's look at a few things you might not know about the S III that will come as pleasant surprises.

1: MicroSD on steroids

You probably know that the S III, unlike the Nexus, has a microSD slot so you can add storage space. What you might not know is that it isn't limited to the 32 GB maximum card capacity like most phones. Not only does it support microSD and SDHC, it also supports SDXC, which have a theoretical capacity of up to 2 TB. Transfer speed is also faster.

The Galaxy S III specs say it supports up to a 64 GB card, but it's unclear whether that's because that is currently the largest size available or there is a software limitation. In practical usage right now, you can add a whopping 64 GB of storage to the S III for around $55.

2: Motion controls

The Nintendo Wii popularized the concept of interacting with an interface via motion on a gaming device, and Microsoft's Kinect took it to the next level and expanded it from the game console to the PC. Now Samsung has brought motion control to the phone, in a big way.

There's a whole set of gestures you can use with the S III that you won't find on the Nexus or most other phones. You can double tap the top of the device to go to the beginning of a list. You can tilt the phone forward or back to zoom in or out of a picture or Web page. Simply by placing the phone to your ear, you can call the currently displayed contact. You can shake the phone to update (refresh a Web page, rescan for Wi-Fi devices, etc.). You can pan (move the phone left or right or up or down) to move around a large onscreen image. You can briefly pause a video or mute sound by placing your hand over the screen.

If you don't want your phone doing things because of the way you hold it, don't worry. You have to activate the motion feature in Settings before you can use these and other built-in gestures.

3: Pop-up Play

This was another pleasant surprise. It works like the picture-in-a-picture feature on TVs. A limitation of smartphone screens has been the inability to display more than one app at a time. With the tiny screens of the past, it just wasn't practical. With a screen this big, it starts to make sense. The Galaxy S III doesn't go as far as I'd like in this department (side-by-side display of any running apps would be awesome) but the Pop-up Play feature does let you play an HD video in a small window while you use another app (email, Web, etc.) on your phone.

4: Camera bonuses

I care about the camera quality in my smartphone, because I take a lot of impromptu photos. Sure, if I know I'm going to be taking pictures, I'll load up one of the high-end Nikon DSLRs — but often, I'm out and about with no intention of playing photographer and I want a phone cam that can give me a decent shot of that once-in-a-lifetime photo op.

The Nexus was a big step forward, with its quick shutter, but the pictures weren't always as sharp as I wanted. Part of that was "operator error" — it's hard to hold a little phone steady as you tap the onscreen button. That's why I prefer hardware buttons. Well, the S III doesn't have that, but it does have the next best thing. You can delay the shot after you tap, giving you time to steady the phone/camera, or you can use S Voice to take the picture (just say "cheese"), so you don't even have to tap at all.

There's more to it than stability, though. The S III provides an 8 MP camera in contrast to the Nexus's 5 MP, and noise levels are lower, too. Photos simply look better, especially those taken in low light. And videos are sharper and more fluid.

There are some interesting shooting modes. In addition to the (now fairly standard) smile detection and panorama, there's a "beauty" mode that automatically smoothes facial features, a "cartoon" mode (that I've not found very useful) and "buddy photo share" that will use facial recognition to match up people in your photos to the pictures of your contacts and automatically send people pictures of themselves. A nice bonus is that you can edit the shortcuts to make it more convenient to get to the controls you use often.

Another photo feature might not matter a lot to the average phone user, but for those of us who write about phones, or to a lesser extent IT pros who support phones and may need to remotely demonstrate to a user how to configure something, the ability to take screenshots of the phone's display is important.

Once upon a time, getting a screenshot on an Android device was surprisingly difficult. Some phones had to be rooted before you could install screen capture software. Some of us even resorted to taking pictures of the screen with a camera (which presented the challenge of dealing with the glare on the glass).

Samsung made it a lot easier with the Nexus: You could do it by pressing and holding the volume down button and the power button simultaneously. You had to do it just right, though, or you might end up turning the phone off. With the S III, taking a screenshot is as simple as swiping your palm across the screen. Amazing. If you want to illustrate how Android and its apps work, this is the phone for you.

5: Great phone

A problem with some smartphones is that they're heavier on the "smart" than on the "phone." That's okay if you want to use your device primarily as a miniature computer, but if you plan to talk on it a lot (or even a little), it's nice if it also functions as a better-than-average phoneo.

The S III does. Call quality is crystal clear, and you can customize it with personalized equalization settings. This feature actually tests your ears with different frequencies and tones, measuring how well each ear hears them, and creates an equalization curve for each ear.

But that's not all. The whole calling experience has been improved. Lots of phones let you set custom ringtones for different contacts, but that doesn't help if you have the ringer turned off. The S III lets you set customized vibrations for different contacts. How cool is that? You can also answer (or reject) a call by voice command, and you can set up a rejection list to automatically reject those numbers you never want to hear from.

If you leave the phone app to go back to the home screen to check mail, look up a contact, or whatever, the status bar turns green so you won't forget you're in a call. Can't hear the caller? There's an Extra Volume button on the screen during a call, that lets you increase it beyond the maximum you get from pressing the up/down volume hardware key. There's even a key to let you create a memo from within a call.

The not-so-good

These are some cool features, and there are more (such as the Siri-like S Voice application that goes way beyond Google's voice search) But the S III still isn't quite the perfect phone. Here are some of the not-so-good things I've encountered in making the transition from the Nexus.

6: Speaking of that microSD card

It's great to have the extra storage space of a massive 64 GB card, but what exactly did you want to do with that space? If you only wanted to put your pictures, videos, music, etc., on it, no problem. But if you thought you'd be installing apps on it, think again. The S III doesn't support moving apps to the external microSD card, as you could do with most previous Android phones.

It can be done — by rooting the phone and using a third-party app, such as links2sd or Directory Bind. But many folks don't want to root their phones because it voids the warranty. The 16 GB version of the S III has about 11 GB available on its internal storage disk (sd). That's probably enough app space for most people, but some are going to run out of room.

7: No USB mass storage mode

If you're upgrading from an older (pre-ICS) Android phone or you got your start with Windows Mobile, you're probably used to being able to plug your phone into a PC via USB and seeing it pop up in Windows Explorer as a hard drive. Unfortunately, the UMS (Universal Mass Storage) mode that enabled that isn't supported in the Galaxy S III.

Apparently, you're supposed to use the Samsug Kies app instead. That's going to make a lot of people unhappy; it requires installing software on your computer (like syncing an iPhone via iTunes or a Windows Phone 7 via Zune — ugh), and it's slow as molasses. Sure, it has an "easier" interface that those moving from an iPhone might like. But many Android users prefer power and more control over "simple."

The alternative to installing Kies is to use MTP (Media Transfer Protocol) or PTP (Picture Transfer Protocol) mode. This has advantages (you can still use the phone while it's connected to the computer), but it's not as easy to use. If you're willing to root your phone, you can use an app like Easy UMS to enable USB Mass Storage. It would have been nice if the S III just supported both UMS and MTP/PTP.

8: S Voice tries hard, but…

Samsung's answer to Apple's Siri suffers from some of the same problems I've heard iPhone users complain about. It works fine for simple things (and I do love that ability to use voice to trip the camera shutter), but it gets easily confused if you ask it to do something complex. Making a call by voice takes me three times as long as doing it the old fashioned way, since you go through the "found more than one match" business. Trying to search the Web with it proved to be a bit of a pain. And it seems to get frustrated with you when you don't like its results and keep trying — it froze up on me a few times and I had to kill the process.

Voice recognition is getting better, but in my opinion it's not ready for prime time yet for most uses. I'm sure my Texas accent doesn't help. If you're getting the phone primarily for this voice feature, prepare to be disappointed (or maybe not, if you have a perfect Midwestern non-accent that it can understand).

9: Missing photo options

Even though there's a lot to love about the S III's camera, there are also some things I miss about my Nexus camera. Mostly, I miss the great editing tools that were built in. You could adjust the brightness and contrast, add a vignette, and achieve all sorts of additional effects right there in the camera.

With the S III, unless I'm just not finding it (in which case they should make it a lot more obvious), the only editing options are to crop and rotate. Sure, I can download a photo editing app, but that involves extra steps. I really liked the simple but comprehensive set of editing tools in the Nexus. This isn't a deal breaker, but it's something that's good to know when you're considering the switch.

10: Wi-Fi connectivity problem

Overall, despite the small complaints above, I was immediately impressed with my Galaxy S III and loved using it — except for one very big problem. It was blazing fast and reliable on 4G, but I soon noticed that Wi-Fi was just plain wacky. It would load a page quickly, and then the next page would take forever and/or time out completely. S Voice would give me "Network error. Try again." messages. The Facebook app would give me "Connection Lost" errors. Often.

My old Galaxy Nexus (now my husband's) sitting right beside it, connected to the same wireless network, had no such problems. I started researching and found out this is a fairly common problem with the S III. There is a fix that works for some, which involves going into service mode and turning off power saving in the Wi-Fi settings. It doesn't work for everybody, though, and if you discover the problem during the return period, I'd recommend taking the phone back to the carrier and telling them it has a defective Wi-Fi radio. Although a number of people are reporting this problem, it seems to be a small percentage, so your chances of getting another one with the problem are low. Still, the possibility that you'll encounter this is something to be aware of if you're thinking about getting an S III.

Wednesday, September 5, 2012

10 Outlook defaults you can customize to work the way YOU want

Perhaps no other Office app lends itself to customization as much as Outlook does. But with all that flexibility often comes confusion and frustration because users don't always know how to help themselves work more efficiently. Changing Outlook's out-of-the-box settings can help you reduce repetitive tasks and help you work a bit more efficiently via the interface. Here are some useful tweaks to make.

Note: This article covers 2007 and 2010; the instructions for 2007 will often be similar for Outlook 2003, but this article doesn't include specific instructions for 2003.

1: Opening folder

When you launch Outlook, it displays Outlook Today view or moves straight to a specified folder. Opening to your preferred folder can eliminate a few clicks and put you right where you want to start your session. To specify which folder Outlook selects when launching, do the following:

  1. Click the File tab and choose Options (under Help). In Outlook 2007, choose Options from the Tools menu, click the Other tab, and skip to step 3.
  2. Choose Advanced in the left pane.
  3. In the Outlook Start And Exit section, click Browse. In Outlook 2007, click the Advanced Options button in the General section and click Browse.
  4. In the resulting dialog, select the folder you want as the default. Figure A shows a secondary Inbox selected, but your view will be unique to your system.
  5. Click OK. Figure B shows the new setting.
  6. Click OK again.

Figure A

Select the folder you want Outlook to select when launched.

Figure B

Check the setting here.

The next time you launch Outlook, it will open to the window specified in step 4. Your default window can be your Inbox or the Calendar, Tasks, or Contacts window. If you create a custom Inbox, you can specify it (as shown in Figure A). The default window can be almost any Outlook folder.

2: Custom address book

If you save addresses in a custom address book, making Outlook default to that address book will allow you to access your contacts with just a few clicks. To make a custom address book the default, do the following:

  1. On the Home tab, click Address Book in the Find group. In Outlook 2007, click the Address Book icon on the Standard toolbar or press [Ctrl]+[Shift]+B.
  2. From the Tools menu, choose Options. The default setting is Start With Global Address List (GAL). If yours is different, someone has already changed it. If you're on Exchange, the GAL is usually members of your organization. This list won't contain the contacts you add yourself. Your contacts are personal to you and are in the Contacts list.
  3. If you want Outlook to default to your contacts, click the Start With Contact Folders option. Or click Custom to make a custom address book the default and set the order of reference using the arrow icons to the right.
  4. To set the actual default address book, select the appropriate book from the When Opening The Address Book, Show This Address List First drop-down (Figure C). In Outlook 2007, it's the When Sending Mail… option.
  5. Click OK.

Figure C

Figure C

You can control which address book Outlook uses as the default.

3: Message format

Most users know that they can send email in different formats:

  • Plain Text uses text characters with no formatting, so it's compatible with all email clients.
  • HTML applies HTML formatting. Most clients can handle HTML, but they don't always render the HTML coding by default.
  • Rich Text allows simple text formatting that's specific to Outlook.

Mobile technologies are quickly displacing this setup, but for now, many users still prefer Plain Text because it's less trouble — many lists and Web clients don't allow anything else. You can set this default, as follows:

  1. Click the File tab and choose Options under Help. In Outlook 2007, choose Options from the Tools menu, click the Mail Format tab, and skip to step 3.
  2. Choose Mail in the left pane.
  3. In the Compose Messages section, choose Plain Text from the Compose Messages In This Format drop-down, shown in Figure D.
  4. Click OK.

Figure D

You can set the default message format.

You may want to let the default setting handle most of your messages, but you can easily change the default for individual messages. In the message window, click the Format Text tab and choose the appropriate format in the Format group.

4: Appointment interval

Calendar view defaults to 30-minute intervals. If you maintain a different schedule, you might want to change the default interval as follows:

  1. Right-click the timebar in the day or one of the week views.
  2. Choose one of the intervals shown in Figure E.

Figure E

This shortcut is the easiest way to reset the default interval.

5: Appointment reminder

Outlook reminds you 15 minutes before a scheduled appointment. If you often change the reminder time when you create appointments, change that default reminder to better suit the way you work, as follows:

  1. Click the File tab and choose Options under Help. In Outlook 2007, choose Options from the Tools menu, click the Preferences tab (if necessary), and skip to step 3.
  2. Choose Calendar in the left pane.
  3. In the Calendar Options section, choose the appropriate reminder time from the Default Reminders drop-down, shown in Figure F.
  4. Click OK.

Figure F

Don't work around the default — set a reminder time that best reflects your scheduling needs.

You're not limited to the listed times, either. For instance, if you want a three-minute reminder, enter "3 minutes."

6: Name order

When you click To in the message window to access the default address book, Outlook displays contact names in First Name, Last Name order. If you have a long list, you might prefer to see contacts alphabetized by last name first. To make this change, do the following:

  1. Click the File tab. In Outlook 2007, choose Account Settings from the Tools menu and skip to step 3.
  2. In the resulting window, choose Account Settings from the Account Settings drop-down.
  3. Click the Address Books tab.
  4. Choose the appropriate account (probably Outlook Address Book) and click Change (just above the list of accounts).
  5. In the resulting dialog box, click the File As (Smith, John) option in the Show Names By option, shown in Figure G.
  6. Click Close twice.
  7. Exit Outlook and reopen it. Outlook won't recognize this change until you do.

Figure G

Display contacts by last name first.

7: Reading pane

The quickest way to see more message text in the Reading Pane is to display less data about the message in the header section. To reduce this section to a single line, do the following:

  1. In the Mail window, click the View tab.
  2. From the Change View drop-down, choose Single, as shown in Figure H.

Figure H

Reduce the header information to a single line to free up space in the Reading Pane.

Outlook 2007 users have a very different route:

  1. With the Reading Pane open, choose Current View from the View menu. Then, choose Customize Current View.
  2. Click the Other Settings button.
  3. In the Other Options section, uncheck the Use Compact Layout option.
  4. Check the Always Use Single-Line Layout option.
  5. Click OK twice.

8: Work week

The default work week displays only five days — Monday through Friday. If you work a nontraditional week, you can change this default to display the days you need, as follows:

  1. Click the File tab and choose Options under Help. In Outlook 2007, choose Options from the Tools menu, click Calendar Options in the Calendar section, and skip to step 3.
  2. Choose Calendar in the left pane.
  3. In the Work Time section, check the days you want to include in your work week. You can include only a few or all seven. Figure I shows a work week that includes Monday through Saturday.
  4. From the First Day Of Week drop-down, choose the day that represents the first day of your work week.
  5. Click OK.

Figure I

Your calendar will accommodate your work week schedule.

9: Download interval

Outlook downloads mail at regular intervals, but you can disable that feature or change the default interval. Do so as follows:

  1. Click the Send/Receive tab. In Outlook 2007, choose Options from the Tools menu, click the Mail Setup tab, click Send/Receive in the Send/Receive section, and skip to step 3.
  2. Click the Send/Receive Groups drop-down in the Send & Receive group and choose Define Send/Receive Groups.
  3. Enter the interval in minutes to the right of the checked Schedule An Automatic Send/Receive Every option to change the interval. You can also uncheck the option to disable the feature and download your mail manually.
  4. Click Close.

10: Months in To-Do

Many of us schedule events well beyond the current month, but the To-Do Bar displays only the current month. With just a few clicks you can display the current and future months, as follows:

  1. Click the View tab. In Outlook 2007, Choose To-Do Bar from the View menu.
  2. Choose Options from the To-Do Bar drop-down in the Layout group. In Outlook 2007, choose Options.
  3. In the Show Date Navigator section, enter the number of months (up to 9) to display in the Number Of Month Rows option, as shown in Figure J. (Enter 0 to display no months.)
  4. Click OK.

Figure J

Entering 3 will display the current and next two months in the To-Do bar.

ITWORLD
If you have any question then you put your question as comments.

Put your suggestions as comments