Windows 98 Installation & Configuration Handbook

Previous chapterNext chapterContents


- 26 -

Using Windows 98 Software


by Rob Tidrow

Exploring the Windows 98 Architecture

Before you delve into the nitty-gritty of how applications work with Windows 98, it is important that you understand a few foundation concepts regarding the Windows 98 architecture. As you know, Windows 98 is an operating system. Operating systems provide the link between hardware and software. When a software application needs to write a file to the hard disk, print a document, or display something onscreen, the operating system provides these services.

Windows 98 executes software differently, depending on the type of software you are running. Software is divided into three basic categories:

The Windows 98 application execution environment changes depending on the type of software. The key architectural areas that differ include the Virtual Machine (VM), multitasking, and internal messaging.

Simulating Computer Resources with Virtual Machines

To meet the various needs of each type of software application, Windows 98 creates a fictional computer called a virtual machine. A virtual machine is an environment created by the operating system and processor that simulates a full computer's resources. To the software application, the virtual machine appears to be a real computer.

The operating system keeps track of the application needs and hardware resources. Windows 98 determines which resources each application will have access to and when it can have access. All software applications in Windows 98 run in virtual machines (VM).

Each DOS application runs in a separate MS-DOS VM. For example, if you ran a DOS-based version of WordPerfect and a DOS-based version of Lotus 1-2-3, Windows 98 would create two separate MS-DOS VMs, one for each DOS-based program. Providing each DOS application with its own VM is beneficial because most DOS-based programs were created in a single application environment. That is, DOS-based programs usually assume that they are the only program executing at any particular point in time. This single-mindedness of DOS applications has been known to cause grief (system hang-ups, sudden reboots, and general protection faults) when running DOS applications under Windows 3.x.

Another benefit of the single DOS VM is that each DOS application is shielded from other DOS applications as well as Windows 3.x and Windows 98-type applications. Thus, a misbehaving DOS, Win16, or Win32 application cannot bring down another DOS application (that is, suspend its execution). The MS-DOS VM insulates the DOS application from other misbehaving programs.

In addition to the MS-DOS VM, Windows 98 creates another virtual machine environment called the System VM. The System VM executes the following:

The system services, such as the kernel (which is the core program of the operating system), graphics, and Windows management execute in a separate area (memory address). Each Windows 98 32-bit application executes in its own separate memory address. This design prevents 32-bit applications from interfering with other currently executing 32-bit, 16-bit, or DOS applications.

However, the 16-bit Windows applications all run in the same memory address within the System VM. This design aspect of the Windows 98 architecture was done to maintain downward compatibility with the old Windows 3.x 16-bit applications. So although Windows 98 is compatible with the older Windows 3.x applications, Windows 98 doesn't offer any better protection against misbehaving 16-bit applications than did Windows 3.x. That is, a misbehaving 16-bit application can still bring down all currently executing 16-bit applications (and can crash Windows 98 at times).

Multitasking Your Applications

Running multiple programs at the same time is called multitasking. Windows 98 provides a multitasking feature that enables multiple applications to run concurrently by sharing processor cycles. A processor cycle is a time slice that the operating system gives a program so that the program can use the CPU, or central processing unit. In Windows 98, this enables you to print a document while sending email and editing a spreadsheet at the same time. Under the PC cover, all three applications are sharing CPU time, one slice at a time.

First, you need to familiarize yourself with some terms:


NOTE: Windows 98 supports multitasking on one microprocessor. Windows 98 doesn't support Symmetric Multiprocessing (SMP), which enables the use of multiple microprocessors within one PC. Windows NT and OS/2 Warp do support SMP.

In Windows 98, each executing DOS and Windows application is a single process. For example, if you have Word for Windows 97, Paradox for DOS, and Lotus 1-2-3 for Windows 3.x running, the CPU is handling three processes (in addition to the operating system work). Within a process, Windows 98 allows 32-bit applications to schedule individual threads of execution. This is called multithreaded processing.

How an application multitasks depends on the type of application (DOS, 16-bit, or 32-bit). For DOS and 32-bit applications, Windows 98 uses preemptive multitasking. In preemptive multitasking, each thread is executed for a preset time period, or until another thread with a higher priority is ready to execute. The Windows 98 Task Scheduler manages multitasking and ensures that no one application monopolizes the processor. At any time, the operating system can preempt (take control away from) an application and hand the system resources to another application with a higher priority task.

For Windows 3.x (16-bit) applications, Windows 98 uses a cooperative multitasking system. In cooperative multitasking, the program (rather than the operating system) is in control of CPU scheduling. Although programs should yield to the operating system after a reasonable amount of time, we have all encountered the Windows 3.x program that fails to return control of the system resources back to the operating system and eventually locks up the entire system. Windows 98 uses the less reliable cooperative multitasking model to provide compatibility with existing 16-bit Windows 3.x programs.

For Windows 98 (32-bit) applications that choose to schedule their own threads of execution (multithreaded processing), Windows 98 again uses the cooperative multitasking method. Up to 32 levels of priority can be assigned.

How Applications Communicate

Applications communicate with the operating system via the Windows 98 messaging system. The messaging system passes information between the hardware, the applications, and the operating system. For example, when a user moves the mouse, Windows 98 converts the hardware interrupt into a message that is sent to the appropriate message queue.


CAUTION: Although each DOS and 32-bit application has its own message queue, all the 16-bit applications share one common message queue. Thus, if a 16-bit application hangs, all running 16-bit applications must wait until the hung application is cleared. If the hung application is not cleared, all 16-bit applications might lose their messages.

Understanding Windows 98 Software Features

Since the release of Windows 95 in the fall of 1995, many applications have been released that are written for Windows 95, including business applications, games, multimedia applications, and graphics and design packages. In many cases, applications released for previous versions of Windows, the Macintosh, MS-DOS, or IBM's OS/2 have been upgraded for Windows 95. These same applications can run on Windows 98 just as they did on Windows 95. This means that if you've standardized on an application or suite of applications to run under Windows 95, you can often find an upgrade product that runs well under Windows 98.

The following sections describe features and benefits of Windows 98 applications.

Reviewing the Designed for Windows Logo Program

If you are upgrading to Windows 98 from Windows 95, you probably have purchased applications that adhere to the Designed for Windows 95 Logo program. This logo is used to let consumers know that an application is designed to take full advantage of the Windows 98 environment. Likewise, each Windows 98 application must adhere to specific guidelines issued by Microsoft to receive the authorization to place the Designed for Microsoft Windows logo on its packaging.

In March 1997, Microsoft released the Designed for Windows NT and Windows 95 Logo program, which includes specifications for applications to run on both Windows 95 and Windows NT. Applications designed to run on Windows 98, must adhere to these same guidelines, plus additional ones designed to take advantage of new features in Windows 98. The following list describes some of the Windows 98 logo requirements:


NOTE: To find out more about the Windows logo requirements, visit the Designed for Microsoft Windows Logo Programs Web site at http://www.microsoft.com/windows/thirdparty/winlogo. When an application developer submits an application to be tested for compliance to the Windows 98 logo requirements, Microsoft does not do the testing. Rather, a third-party, independent testing laboratory at Veritest, Incorporated (http://www.veritest.com/microsoft.htm) conducts the testing.

You also can learn about the PC 98 System Design Guide, a related program headed by Microsoft and Intel, that presents guidelines for Windows 98 and Windows NT Workstation 5 computers. Visit http://www.microsoft.com/hwdev/pc98.htm to see the guidelines for designing hardware devices for these operating systems.


Reviewing the Zero Administration Windows (ZAW) Initiative

In a move to make network computing easier, Microsoft released the Zero Administration Windows (ZAW) Initiative in late 1996. ZAW attempts to reduce the cost of ownership by lessening the burden of administrating desktop operating systems and applications by automating many tasks, such as automatic updates of operating systems and automated application installation. The Windows Update feature in Windows 98 is an example of ZAW (see Chapter 2, "Installing Windows 98 on a Desktop and Laptop"). Administrators will have the capability to "lock-down" users' configuration settings, eliminating inadvertent system changes on the part of the user. In addition, ZAW provides users the flexibility of roaming between PCs without requiring applications and files to be transferred from one computer to another. Instead, applications, operating system properties, and files reside on a centralized network server.


NOTE: You can read more about ZAW on the Web at http://www.microsoft.com/windows/platform/info/zawmb.htm. Developers and administrators interested in implementing ZAW should get the Zero Administration Kit from Microsoft. You can find information on how to download the kit from the Get the Zero Administration Kit Today Web page at http://www.microsoft.com/windows/zak/getzak.htm.

Examining Benefits of Windows 98 Software

For many users and organizations, upgrading to Windows 98 applications means investing a large amount of time and economic resources. Before investing in new versions, you might want to consider some of the advantages of using Windows 98 applications on Windows 98. The following are some key advantages of Windows 98 software:

In the following sections, you learn how each feature can save you both time and money.

Fast Processing

The easiest way to understand the difference between 16-bit processing and 32-bit processing is to imagine each as a highway with 16 or 32 lanes. Imagine your data as buses and cars commuting at rush hour. When the traffic is heavy and the heat is on, 32 lanes provide for more throughput, fewer accidents, and less stress on system resources. In your computer, the Windows 98 operating system is already running at 32-bit speed. The more 32-bit applications you use, the more work gets done, fewer GPFs occur, and less stress is on the computer resources.

As covered in the beginning of this chapter, DOS applications execute in separate virtual machines (VMs). Windows 3.x (16-bit) applications execute in the System VM in a single address space. Windows 98 (32-bit) applications also run in the System VM but in separate address spaces. This means that if DOS applications crash, they cannot bring down the system, other DOS applications, or other Windows (16- or 32-bit) applications. On the other hand, Windows 3.x (16-bit) applications can bring down other 16-bit applications if they crash running under Windows 98. The fastest, best protection exists for the 32-bit applications, which execute within the 32-bit Windows 98 operating system. Windows 98 (32-bit) applications, however, cannot bring down other 32-bit, 16-bit, or DOS applications if they crash.

Preemptive Multitasking

The 32-bit applications use preemptive multitasking, where each thread is executed for a preset time period, or until another thread with a higher priority is ready to execute. The Windows 98 Task Scheduler manages multitasking and ensures that no one application monopolizes the processor. At any time, the operating system can preempt (take control away from) an application and hand the CPU to another application with a higher priority task.

This is better than the quirky Windows 3.x (16-bit) applications, which use a cooperative multitasking system in which the program (rather than the operating system) is in control of CPU scheduling. Although programs should yield to the operating system after a reasonable amount of time, we have all encountered the Windows 3.x program that fails to return control and eventually locks up the entire system.

Multithreaded Processing

Windows 98 32-bit applications can take advantage of multithreaded processing (schedule their own threads of execution). Multithreaded processing is not available for DOS or Win16 applications. The advantage of multithreading is that each thread can use the same address space as its parent process and provides an environment in which you get to do your work faster. For example, printing a document in Word for Windows 98 is much faster than in Windows 3.1, and you get control of your document back quicker because Word for Windows 98 takes advantage of multithreaded processing for print jobs.

Easier Maintenance

Consolidation of the system initialization and setup files into a single database--which is maintained by the operating system--makes the Win32 platform easier to use. Once consumers move to Win32 and no longer need DOS or Win16 applications, the AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, SYSTEM.INI, and other INI files will no longer be needed. This information is kept in the Registry database and automatically modified as software and hardware is installed, removed, and updated. This feature coupled with the Plug and Play standard makes Windows 98 a self-configuring system.

How Windows Uses the Registry

DOS depended on the AUTOEXEC.BAT and CONFIG.SYS configuration files to initialize and set system parameters on what resources were available and how they should be used. Windows 3.x relied on initialization files (which had a file extension of INI) to tell Windows and Windows applications what resources were available and how to work with those resources.

When Microsoft began designing Windows 95, they identified many problems with these resource setting files. These files were difficult to maintain, often contained remnants of old program setups no longer needed, and usually required user intervention to improve performance. To solve these problems, Windows 95 borrowed a good idea from Windows NT: the Registry. Windows 98 uses the same Registry introduced in Windows 95.

The Registry is a single database that contains system and application execution information. Ultimately, the Registry replaces all INI files as well as AUTOEXEC.BAT and CONFIG.SYS. (Most systems, because of their need to support legacy hardware and device drivers, still use the AUTOEXEC.BAT and CONFIG.SYS files.) The Windows 98 Registry replaces REG.DAT, which was used by Windows 3.1 to store file extension application associations and register OLE applications.

Exploring the Registry

The Windows 98 Registry consists of three data files:

Precautions are taken to protect these data files. First, the Registry data is kept in binary format, so that the files cannot be read or edited by a regular text editor. Second, the file attributes are set to read-only, hidden, system files. This prevents accidental deletion.

When you first install Windows 98, the setup program creates the SYSTEM.DAT file and enters the data regarding installed hardware. If you installed to the Windows 3.x directory, setup copies the data from REG.DAT into the new SYSTEM.DAT file. From then on, whenever you install new hardware or change a configuration, Windows 98 automatically updates the SYSTEM.DAT data file.

You can view the hardware data stored in SYSTEM.DAT by opening the Control Panel folder and selecting System. Figure 26.1 shows the installed devices, as reported by SYSTEM.DAT.

FIG. 26.1 The Device Manager page displays installed devices by type.

Using the Registry Editor

The Registry Editor (REGEDIT) is located in the Windows 98 folder. To run the Registry Editor, choose Run from the Start menu, type REGEDIT, and press Enter. Figure 26.2 shows the Registry Editor and data for My Computer.

FIG. 26.2 The Registry Editor stores information about your computer.


CAUTION: Before you open the Registry Editor and start modifying the settings, be sure that you understand what you are changing and why. If the modification you want can be effected by using Control Panel or by setting some other property, make the change there. Avoid using the Registry Editor unless it is absolutely necessary.

Microsoft advises that you don't use the REGEDIT utility unless you are on the phone with one of their technicians. That's why they didn't include a shortcut or program item for it by default--you have to manually create one.
Incorrect edits to the Registry could prevent Windows from working properly and result in a loss of critical data.

Any time you edit the Registry, you should make a backup copy of the SYSTEM.DAT, SYSTEM.DA0, USER.DAT, and USER.DA0 files in case you experience problems with Windows 98 or an application after modifying the Registry. Depending on the size of these files, you might be able to back them up to floppy disks. In some cases, these files can become too large to store on one floppy disk, requiring that you back up the files on to a tape backup or other device (such as an Iomega Zip drive).


The Registry is organized into matched keys and values. The keys are listed on the left pane as a hierarchical tree. As you double-click items and drill-down within branches, the values appear in the right pane. To change a key's value, right-click the value in the right pane. The Registry Editor then displays an object menu: Modify, Delete, and Rename. Figure 26.3 shows the Edit Binary Value dialog box for a Registry value.

FIG. 26.3 Enter or edit the Value Data in the Edit Binary Value dialog box.

As you change entries, the Registry Editor automatically changes the applicable database file (DAT). However, many changes don't take effect until you restart Windows 98.


NOTE: Windows 98 maintains backup copies of the Registry data in the Windows 98 folder. Windows uses this data during the startup process if the previous shutdown process was interrupted or Windows was shut down improperly. The backup files SYSTEM.DA0 and USER.DA0 are used by Windows 98 in the event that the actual DAT files become corrupt.

Using the Remote Registry Service

To edit Registry files on a remote computer, run REGEDIT.EXE and choose Registry, Connect. You also must have the Microsoft Remote Registry Service installed on all remote computers. To install this, use the following steps:

1. Open Control Panel and double-click the Network application.

2.
Click the Add button to display the Select Network Component Type dialog box.

3.
Double-click the Service component to display the Select Network Service dialog box.

4.
Click the Have Disk button to display the Install from Disk dialog box.

5.
Click the Browse button and locate the \ADMIN\NETTOOLS\REMOTREG folder on the Windows 98 CD-ROM. Click OK to display the Select Network Service dialog box.

6.
Select the Microsoft Remote Registry option in the Models listbox and click OK. This installs the Remote Registry Service on the system. Do this on each computer you want to connect to via a remote connection.

Handling Application Crashes

Sometimes you might experience system crashes or GPFs (General Protection Faults) running applications under Windows 98. Although Windows 98 is designed to handle GPFs much more efficiently than Windows 3.x, you might have situations in which your entire system locks up, causing you to reboot the computer. Under normal situations, Windows 98 applications that experience GPFs only require that you close the offending application, enabling you to continue running Windows 98 and other applications you may be running.

One reason for applications to behave in a nonstandard way (that is, applications that lock up the entire system) is because of missing, outdated, or corrupted Dynamic Link Libraries (DLLs). You can fix this problem by reinstalling the application or querying the manufacturer for any known bugs about the application.

Another reason why a Windows 98 application fails to perform as designed is because of a known bug in Windows 98. To search for known bugs published by Microsoft, use the Microsoft Knowledge Base. This is available from several sources, including on the World Wide Web at http://www.microsoft.com/kb/default.asp. You can get the Knowledge Base on CD-ROM as well by subscribing to the Microsoft Developer Network (1-800-759-5475).

To handle a GPF, press Ctrl+Alt+Del. This displays the Close Program dialog box, which shows the status of all running applications including the application that crashed. Select the offending application and click End Task. The application closes. If, when you display the Close Program dialog box, an application is still executing or if Windows still thinks an application is still executing, another dialog box displays telling you that the application is still executing and that you need to wait until it's finished or end it prematurely. Click End Task.

Understanding File Systems and Modifying Their Properties

Before you start fine-tuning the file system for running your applications, you might want to explore the design of the Windows 98 file system. Operating systems use a file system to organize files, store files, and control how files are named. Windows 98 continues to use the DOS file allocation table (FAT) file system as its default file system. However, Windows 98 uses the installable file system (IFS) introduced in Windows 95. IFS is a program that provides an interface between the application file requests and various supported file systems.

Windows 98 ships with the following installable file systems:

In addition to these supported file systems, vendors may create and add their own installable file systems. A vendor might create an installable file system to enable users to access and work with UNIX or Apple files, for example.

The IFS Manager can work with Application Programming Interface (API) calls from Win32 applications and interrupt 21 (INT 21H) calls generated by Win16 or DOS applications. The file-system design in Windows 98 supports up to 32 layers from the input/output subsystem (IOS) down to the hardware level. Each layer has defined interfaces with the layers above and below. This enables each component to cooperate with its neighbors.

VFAT

The FAT file system was developed to work with DOS. A clear advantage of FAT is that a drive formatted for FAT can be read by DOS, Windows NT, Windows 98, and OS/2. However, the DOS FAT file system has the following limitations:

VFAT is a 32-bit virtualized FAT file system. The VFAT.VXD file system driver (FSD) controls this file system and uses 32-bit code for all file access. VFAT is a protected-mode implementation of the FAT file system. The VFAT system supports long filenames (up to 255 characters), eliminates the over-reliance on INT 21H, uses 32-bit processing, and allows multiple, concurrent threads to execute file system code.

CDFS

The CDFS replaces MSCDEX TRS, which is used to support most CD-ROM devices. CDFS is a 32-bit protected mode ISO 9660-compliant CD-ROM file system. With Windows 98, CD-ROMs larger than 4GB are supported using the CDFS.VXD and CDVSD.VXD drivers. Applications send file requests to the CDFS, which handles the request and passes it to the IOS. The IOS routes the request to the type-specific driver (TSD), which converts the logical request to a physical request. From there, a special SCSI translator sends the request to the SCSI port driver and then to the Miniport driver.

Network Redirector

The Network Redirector installable file system is a 32-bit protected mode VXD responsible for implementing the structure of a remote file system. When an application sends or receives data from a remote device, it sends a call to the Redirector. The Redirector communicates with the network via the protocol driver. Windows 98 supports two kinds of redirectors:

Using FAT32

Windows 98 includes a new 32-bit file system called FAT32. FAT32 first was released in an original equipment manufacturer (OEM) release of Windows 95 called the Windows 95 OEM Service Release 2 (OSR-2). The FAT32 file system can support disk partitions in excess of 2GB. The new FAT32 file system also uses 4KB clusters for partitions of up to 8GB. This improves on the old MS-DOS FAT system that uses 32KB clusters, which results in a large amount of wasted hard drive space for small files (in essence, if you have a file that is only 1KB, it consumes 32KB of your hard drive).

One downside to the 4KB cluster size is if you work with mostly very large files, the system works longer to read all these smaller clusters compared to the time it takes to read larger clusters. Overall, however, your system should see a performance gain when converting to the FAT32 system.

You can set up your file system as a FAT32 file system by running the Drive Converter (FAT32) utility. The conversion process can take several hours to complete, during which time you cannot use your system. When you are ready to convert your file system to FAT32, use the following steps:

1. Choose Start, Programs, Accessories, System Tools, Drive Converter (FAT32). The Drive Converter (FAT32) Wizard appears.

2.
Click Next.

3.
Select the drive you want to convert, as shown in Figure 26.4.

FIG. 26.4 Use the Drives field to select the drive you want to convert to FAT32.

4. Click Next. A dialog box appears, telling you that some operating systems will not be able to access a FAT32 drive.

5.
Click OK. Drive Converter looks for applications that may conflict with a FAT32 file system.

6.
Click Next. You can create a backup of your files before setting up FAT32 on your system. This ensures that you can revert to these backed up files in case FAT32 conversion inadvertently corrupts your drive.

7.
Click Create Backup to start Microsoft Backup. Otherwise, click Next. Windows needs to restart your computer in MS-DOS mode to begin the conversion process.

8.
Click Next to continue.

Working with Long Filenames

Whereas DOS limited users to filenames that were up to eight characters plus a three- character extension (8.3), Windows 98 supports the use of long filenames (LFNs). The long filenames follow these filenaming rules:


NOTE: An exabyte is a billion gigabytes. A stack of 3 1/2-inch disks equal to the capacity of 16EB would be 2,300 times the distance from the earth to the moon.

Preserving Long Filenames

Windows 98 maintains FAT 8.3 filenames for each long filename. A file named East Coast Sales.EXCEL, for example, would have a FAT name of EASTCOAS.EXC. By doing so, Windows 98 ensures that a program designed for FAT filenames can access and work with files created under Windows 98. Long filenames also provide additional information about a file, such as the date of the last file modification.

The following rules are used by the Windows 98 file system to convert long filenames into the DOS 8.3 format:

If you have three files in Windows 98 called East coast budget.xls, East coast expenses.xls, and East coast sales.xls, for example, their 8.3 DOS filenames become EASTCO~1.XLS, EASTCO~2.XLS, and EASTCO~3.XLS, respectively.

Note that 8.3 filenames do not preserve the case of characters (all uppercase).

Several problems arise when using a file in a Windows 98 application and in a non-LFN-aware application:


NOTE: The Windows NT 4.0, Windows 95, and Windows 98 long filename schemes are compatible. However, Windows NT 3.5 and earlier versions do not support LFNs in the FAT file system. Windows 98 supports LFNs in FAT and FAT32.
Also, the OS/2 LFN naming scheme is not compatible with Windows 98 LFNs.


CAUTION: Do not use disk or backup utilities that are not aware of long filenames. If you need to use a backup/restore utility that does not support LFNs, Microsoft supplies a utility called Long File Name Backup (LFNBK) that preserves the LFNs. (This comes on the Windows 98 CD-ROM, or you can contact Microsoft for this utility.) You also can download a copy of this file from the Microsoft Web site at

http://www.microsoft.com/windows95


Modifying File-System Properties

Windows 98 automatically sets file-system properties to optimize the performance based on the current configuration. However, at times, you might need to set a certain property or become aware of a unique need to boost performance. The System Properties dialog box, which is accessed through the Control Panel, enables you to view and set disk and CD-ROM file-system properties.

To set file-system properties, follow these steps:

1. Choose Start, Settings, Control Panel.

2.
Double-click the System icon.

3.
Select the Performance page in the System Properties dialog box that appears.

4.
Click File System. The File System Properties dialog box appears, as shown in Figure 26.5.

FIG. 26.5 Increase the read-ahead optimization to speed up performance.

5. Set the desired options.

6.
Select the CD-ROM page and set CD-ROM properties as desired, as shown in Figure 26.6. You learn more about these options in Chapter 12, "Installing and Configuring CD-ROM and DVD Drives."

FIG. 26.6 To optimize the CD-ROM performance, select the correct access pattern.

7. Choose OK twice to implement the changes the next time Windows 98 loads.

Troubleshooting the File System

If an application does not respond properly to the Windows 98 file system, you can use the File System Troubleshooter to detect the cause of the problem. Using the Troubleshooter, you can disable the following Windows 98 file-system features:

To start the File System Troubleshooter, follow these steps:

1. Choose Start, Settings, Control Panel.

2.
Double-click the System icon.

3.
In the System Properties dialog box that appears, select the Performance page.

4.
Choose File System.

5.
Select the Troubleshooting page, as shown in Figure 26.7.

6.
Select the setting to be tested.

7.
Click OK twice to test the setting.

FIG. 26.7 Use the Troubleshooting page to disable file-system properties when trying to locate a problem.


Previous chapterNext chapterContents


© Copyright, Macmillan Computer Publishing. All rights reserved.