Configuring the Operating System to Support Applications

     

One of the major tasks of desktop support personnel is to troubleshoot problems with applications. This task may include troubleshooting installation problems or compatibility issues. To successfully troubleshoot such problems, you should have a general idea of how applications can be installed on Windows XP.

Installing Applications

Applications can be installed in a number of different ways. For example, an application can be installed from a Web site or from a CD-ROM that you purchased. Table 1.1 outlines several different methods for installing applications.

Table 1.1. Methods for Installing Applications

Method

Description

Systems Management Server (SMS)

SMS is software designed to allow large organizations to easily and efficiently deploy critical business applications to users.

Group Policy Object (GPO)

Applications can be deployed using a GPO. Applications can be published to users or assigned to both users and computers.

Local (from CD)

Most applications that are purchased come with a CD that contains the executable used to install the application.

Network

Applications can be installed across the network. The required files must be placed in a shared folder.

MSI files

Some software vendors include MSI files that can be used to facilitate the installation of the application. An MSI file is also referred to as a Windows Installer Package.

MST files

MST files can be used to customize the installation of a Windows Installer Package. For example, an MST file may specify that only specific features of an application be installed.


Most applications purchased today are compatible with Windows XP. However, older applications may not be compatible. In these situations, you should run the Program Compatibility Wizard , discussed later in the chapter.

Most applications require very little interaction from the user other than clicking through a series of windows and accepting default installation settings. Many applications require you to provide only registration information. Most newer applications are installed automatically using a feature known as autoplay , or you are required to locate the application's installation executable (often Setup.exe ).

Applications that support autoplay begin the installation as soon as the CD is inserted into the CD-ROM drive. If an application supports autoplay but the setup program does not automatically launch, verify that your CD-ROM has been enabled (through the Properties window for your CD-ROM drive). Another common method of installing an application is to locate the application's installation executable. After you've located the installation executable, simply double-click the icon to launch setup.

Configuring Application Compatibility Settings

Most programs run properly on Windows XP. The main exceptions are some older games and other programs that were written specifically for an earlier version of Windows. These programs may run poorly or not at all after you first upgrade to Windows XP. In most cases, though, you can use a compatibility mode in Windows XP to start these programs working again. Other programs that may not run properly on Windows XP include specialized drivers that are incompatible with Windows XP. Only an update from the manufacturer can resolve incompatible driver problems.

Most importantly, you make no trade-off. You do not give up any of the new features and excellent performance in Windows XP. Compatibility mode applies small pieces of code that support these older programs so they will work with Windows XP.

graphics/note_icon.gif

You can use a tool called QFixApp to determine any compatibility fixes that are required to resolve application compatibility issues. For more information, visit the following URL:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/maintain/lgcyapps.asp


Changing Application Compatibility Settings

Often, you can identify compatibility issues by error messages such as that shown in Figure 1.1. In other cases, a program may not start, or it may perform erratically, with no error message to explain it. Then you should use the Program Compatibility Wizard to find the specific issue and available fixes.

Figure 1.1. The error window helps identify compatibility problems.

graphics/01fig01.gif


Using the Program Compatibility Wizard

You should run the Program Compatibility Wizard before you try other ways of updating your programs or drivers because it identifies compatibility fixes written specifically for Windows XP. If the wizard does not solve your problem, you can try other steps listed at the end of this chapter.

If a compatibility problem prevents you from installing a program on Windows XP, run the Program Compatibility Wizard on the Setup file for the program. The file may be called Setup.exe or something similar, and is probably located on the Installation disc for the program.

To run the Program Compatibility Wizard, follow these steps:

  1. Click Start, point to All Programs, point to Accessories, and then click Program Compatibility Wizard.

  2. Follow the wizard's instructions to select the program's executable file, choose a compatibility mode, set the visual options, and then test the program.

The wizard prompts you to test your program in different modes and with various settings. For example, if the program was originally designed to run on Windows 95, set the compatibility mode to Windows 95, as shown in Figure 1.2, and try running your program again. The wizard also allows you to try different settings, such as switching the display to 256 colors and the screen resolution to 640 480 pixels. The wizard launches your program with the selected settings and allows you to test how the program works. The final page of the wizard enables you to select whether to permanently apply the compatibility settings, abandon the changes, or save them and run the wizard again to apply different settings. It is likely that you will need to repeat this process until you find the correct compatibility mode.

Figure 1.2. Use the Program Compatibility Wizard to set a program to run in a previous version of Windows compatibility mode.

graphics/01fig02.gif


As an alternative to running the Program Compatibility Wizard, you can set the compatibility properties for a program manually by following these steps:

  1. Right-click the program icon on your desktop or the shortcut on the Start menu for the program you want to run, and then click Properties.

  2. Click the Compatibility tab and change the compatibility settings for your program.

The Compatibility tab, as shown in Figure 1.3, is available only for programs installed on your hard drive. Although you can run the Program Compatibility Wizard on programs or Setup files on a CD-ROM or floppy disk, your changes will not remain in effect after you close the program. For more information about an option on the Compatibility tab, right-click the option and then click What's This.

Figure 1.3. Setting program compatibility manually.

graphics/01fig03.jpg


Configuring and Troubleshooting File System Access and File Permission Problems on Multiboot Computers

Multiple operating systems can be installed on a computer. This procedure is referred to as multibooting . You can configure a computer to multiboot with Windows XP and another operating system such as Windows 98.

graphics/tip_icon.gif

For multibooting to work, you should install the operating systems in a specific order. If you are multibooting Windows XP and Windows 2000, Windows XP should be installed after Windows 2000 has been installed. Generally, the rule of thumb is to install all non-Microsoft operating systems and earlier versions of Windows first. So, if you plan to multiboot Windows XP and Windows 98, Windows 98 should be installed first.


If you are multibooting a computer with Windows XP and an older operating system such as Windows 95, you must address compatibility issues in regards to the file system.

Normally, when you install Windows XP, it is recommended that you format partitions with the NT File System ( NTFS ) to take advantage of additional features not included with the File Allocation Table ( FAT ) , such as file-level security and encryption.

The main point to keep in mind when multibooting Windows XP with another operating system is file system access. NTFS is not supported by all operating systems. Therefore, any partitions that are formatted with NTFS will not be accessible when you boot under another operating system. For example, if you multiboot a computer with Windows XP and Windows 95, any partitions formatted with NTFS are not readable when booted under Windows 95.

Windows 2000 introduced the basic and dynamic disks. This is another point that must be considered when multibooting a computer. Older operating systems such as Windows NT 4.0, Windows 95, and Windows 98 use partitions as opposed to basic and dynamic disks. When you multiboot one of these operating systems with Windows XP, they must be installed on a basic disk that is formatted with FAT. Any disks that are converted to dynamic disks are not readable under the legacy operating systems. For example, if your computer is configured with two hard disks and one of the disks is converted to a dynamic disk, the disk is not readable when booted under a legacy operating system. This, however, is not an issue if you are multibooting with Windows 2000 because Windows 2000 supports dynamic disks.

graphics/alert_icon.gif

If you plan to use applications under two different operating systems, you must install them on both partitions. For example, if you want to use Office under two operating systems, you must install the application twice.


Configuring Access to Applications on Multiuser Computers

Often a computer is shared among multiple users. However, you may not want all users to have access to every application that is installed on the computer. In such instances, you can use file permissions to control access to various applications. For example, certain applications may be used for specific job functions. One user performing one job function may not need access to applications required to perform another job function.

graphics/note_icon.gif

To take advantage of NTFS permissions to control access to applications, the applications must be installed on an NTFS partition. FAT and FAT32 do not support local permissions. Also, keep in mind that if you are multibooting and plan to use NTFS permissions to limit access to applications, the operating systems must support NTFS.


To control access to an application, locate the application's executable within Windows Explorer and use the Security tab from the application's properties window to configure which users can run the application.

graphics/tip_icon.gif

If the Security tab is not available, you must turn off simple file sharing. See Table 1.4 for more information. To configure the permissions, you must also be the owner of the resource or have been granted the ability to do so by the owner.




MCDST 70-272 Exam Cram 2. Supporting Users & Troubleshooting Desktop Applications on a Windows XP Operating System (Exam Cram 2)
MCSA/MCSE 70-291 Exam Cram: Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure (2nd Edition)
ISBN: 0789736187
EAN: 2147483647
Year: 2003
Pages: 119
Authors: Diana Huggins

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net