'; window.popUpWin.document.write(zhtm); window.popUpWin.document.close(); // Johnny Jackson 4/28/98 } //--> Windows 98 Professional Reference -- Ch 2 -- Installing Windows 98


Windows 98 Professional Reference

Previous chapterNext chapterContents

- 2 -
Installing Windows 98

Windows 98 includes new features that make it easier than previous versions to upgrade, install, or uninstall. Windows 98 Setup can take either of two approaches to installing Windows 98 on your system:

Chapter 1 described planning and configuration choices you have to make when preparing to install Windows 98. This chapter describes the actual installation process:

You can install Windows 98 either locally or over the network. This chapter discusses the principles of Windows 98 installation. For a detailed discussion of network installation techniques, see Chapter 3, "Network Installation."

Preparing to Install Windows 98

Microsoft recommends that you undertake some preliminary tasks before you install a new version of Windows. Specifically, those tasks are as follows:

The following sections discuss these preliminary installation tasks.

NOTE: Of course, part of preparation is deciding what you want from your new system. Refer to Chapter 1 for more information about planning and deployment of Windows 98.

Check System Requirements

Take a moment to ensure that the PC on which you're installing Windows 98 meets the following system requirements:

Processor: Intel 486DX 66 MHz or better (or equivalent). Pentium recommended.

RAM: 16 M minimum; 24 M recommended.

Disk space: For Typical installation: 200 M free disk space (of which 45 M is temporary disk space required by the Setup program).

For Compact installation: 21 M.

For Custom installation: As much as 250 M.

If you plan to save existing operating system files (see "Uninstalling Windows 98," later in this chapter), you need an additional 50 M of disk space. You must install Windows 98 onto a FAT partition. You can't use a Windows NT NTFS partition or an OS/2 HPFS partition.

Monitor: VGA 256 color; SuperVGA 16-bit or 24-bit color recommended.

Installation CD-ROM drive (for local installation using the Windows 98 CD-ROM) or a Source: network connection to a server that holds the Windows 98 installation files. See Chapter 3 for more on network installations.

Make Sure That Hardware Is Supported

Windows 98 is fairly efficient at detecting and installing hardware automatically, but if you want to ensure a flawless setup, you may want to verify that your hardware is supported. If your system is now working under Windows 95 and you're planning to upgrade to Windows 98, you shouldn't have a problem with hardware compatibility in most cases. If you're upgrading from another operating system, or if you're installing Windows 98 on a new system, there are several ways to check whether your hardware is supported. The easiest way may be to check the vendor documentation.

If you have Windows 98 running somewhere in your organization, a good way to check for built-in hardware support is through the Control Panel Add New Hardware Wizard:

1. In the Control Panel, double-click Add New Hardware.
2. Click Next twice to pass the first two screens. When the wizard asks whether you want Windows to search for new hardware, select No, I Want to Select the Hardware from a List, and click Next.
3. From the list of component types that appears, select the relevant component type (floppy disk controller, display adapter, CD-ROM controller, and so on) and click Next.
4. Choose a manufacturer and scan through the list of models with built-in Windows 98 support.

If your hardware device is not present in the Add New Hardware Wizard list, you still may be able to use it in Windows 98, but you may have to supply a driver for it during or after installation. Setup attempts to select a generic driver if it doesn't recognize the device. If the generic driver doesn't work, or if Setup fails to find a suitable generic driver, be ready to install a Windows 95 or Windows 98 driver directly from the manufacturer's floppy disk that accompanied the device. (See Chapter 12, "Supporting Devices," for more about installing new hardware.)

The Add New Hardware Wizard lists only the devices included on the Windows 98 CD-ROM. Microsoft provides a document called the Windows 98 Hardware Compatibility list that contains a regularly updated list of devices that have been tested for Windows 98 compatibility. You can obtain the Windows 98 Hardware Compatibility list from the Microsoft web site at http://www.microsoft.com. You can also check the HARDWARE.TXT file in the README directory of the Windows 98 installation CD-ROM for more information about specific hardware issues.

Disable TSRs and Timeout Features

Microsoft recommends that you disable all TSRs and device drivers in AUTOEXEC.BAT and CONFIG.SYS except those necessary for essential features such as hard disk control, network access, CD-ROM access, and so forth.

Some portable PCs include a timeout feature that shuts down the system after a predefined timeout period. Timeout mechanisms should be disabled before you start Setup.

Close Applications--Especially Virus Checkers--

It is best to close all applications before you start Setup. Setup attempts to detect Windows applications and prompts you to close them, but the safest approach is to close all applications before you begin.

For upgrades from Windows 3.1 (or earlier), it is especially important to disable any antivirus software and to make sure that antivirus software doesn't start automatically when the system boots. Windows 3.1 (or earlier) antivirus software is not compatible with Windows 98 (principally because of Windows 95/98's mechanism for handling long filenames; refer to Chapter 17, "File Systems: File and Disk Resources"). Running earlier antivirus programs under Windows 95/98 can cause loss of data and other unpredictable consequences. If you're upgrading from a pre-Windows 95 OS, make sure that your antivirus software doesn't start automatically. You may be able to shut off automatic startup from within the application, or you may have to manually remove the program from AUTOEXEC.BAT, WIN.INI, or the Startup program group.

NOTE: If you are converting to the FAT32 file system, make sure that your antivirus software and disk software is compatible with FAT32. The FAT32 Drive Converter Wizard searches out incompatible disk utilities and antivirus programs and describes the nature of the incompatibility, so watch for warnings when you convert to FAT32. To be on the safe side, check vendor documentation or check directly with the software vendor.

Even if your antivirus software is compatible with Windows 98, it is better to disable automatic startup of antivirus software if you're upgrading from Windows 95. Microsoft advises you to disable your antivirus software because it is an outside application and also because the changes Setup makes to your system (for example, changes to the master boot record) will appear suspicious to your antivirus program. The program may offer to "restore" the original configuration (which essentially makes the new Windows 98 system unusable); one false mouse-click could bring you hours of regret.

If the antivirus program prompts you to restore the original configuration, be prepared to click Cancel. If you're using Windows 3.x antivirus software, close the antivirus program immediately and upgrade to a Windows 95/98-compatible equivalent. If you're using compatible antivirus software and you plan to keep using it, you will eventually have to inoculate your system by registering the new configuration with the antivirus program. Consult the antivirus program documentation.

Scan and Defragment Disks

It is a good idea to defragment your hard drive before upgrading to Windows 98.

Setup automatically invokes the ScanDisk utility to scan for disk errors before beginning an installation or upgrade. However, if you use a third-party disk compression utility, you should use the accompanying disk checking utility to scan and defragment the disk before you begin. Microsoft recommends that you defragment all compressed drives because Windows 98 overestimates available disk space on highly fragmented, compressed drives.

Back Up Key System Files

It is a good idea to back up important system files for your existing operating system before you install Windows 98. Windows 98 Setup includes an option for automatically backing up system files (see the section entitled "Upgrading to Windows 98," later in this chapter). Microsoft recommends that you use this system file backup option.

If, for some reason, you choose not to use Setup's system file backup option (for example, if you want to save the required 50 M of disk space), you can back up key files by using a tape drive or floppy disks, or you can copy those files to a temporary location across the network.

Microsoft recommends that you back up the following files if you're upgrading from Windows 3.1 (or earlier):

If you're upgrading from Windows 95, make sure that you have a working Windows 95 emergency boot disk (and create a Windows 98 emergency boot disk when Setup asks you to do so; remember that Windows 95 and Windows 98 boot disks aren't compatible). Make backup copies of the Registry files SYSTEM.DAT and USER.DAT, logon scripts, proprietary configuration files, and any important real-mode drivers. See Chapter 36, "The Windows 98 Boot Process and Emergency Recovery," for more about emergency recovery.

Check Network Configuration

For upgrades from Windows 3.1 or Windows 95, Windows 98 Setup automatically creates a network configuration that matches the previous network settings. If your network configuration is working properly before you use Setup, Setup does most (or all) of the work of converting your configuration to Windows 98. If you wait until after you install Windows 98 to configure your network settings, you'll be doing the configuration on an unfamiliar system, and you'll have more unknowns if you're faced with a troubleshooting situation. It is generally a good idea to check your network configuration before you begin.

If your system isn't currently part of a network but you want it to be (for example, if you're upgrading to Windows 98 because you want an operating system you can network easily), it isn't necessary to install and configure network client software on the old OS just so that you can perform the upgrade. You can install Windows 98 and configure your network settings afterwards. (Refer to Chapters 20 through 25 for more about networking Windows 98.) If you're installing multiple systems, you can use an installation script with Setup to install Windows 98 with customized network settings. You learn more about Windows 98 installation scripts later in this chapter.

Understanding the Installation Process

Before you start to install Windows 98, it is wise to be aware of exactly what Setup is doing. The procedures and prompts that appear during installation may vary depending on your configuration and on your Setup settings. Schematically, Microsoft divides the Windows 98 Setup process into five phases:

The name of the active Setup phase appears in the bar on the left side of the screen as you progress through installation.

While the relatively few screen prompts pass across the user interface, Setup undertakes hundreds of checking, detecting, polling, and configuration tasks behind the scenes. Much of the hidden complexity within the Setup process results from the need for thorough and reliable hardware detection.

Setup can detect and configure a vast range of system hardware. Setup automatically detects not only Plug and Play devices, it also detects legacy hardware. The methods Setup uses to detect hardware are similar to the methods Windows 98 uses to detect new devices at startup. See Chapter 12, "Supporting Devices," for Plug and Play in Windows 98.

After the first boot in the Setup process (following the file-copy phase), Setup begins a systematic search for system hardware. First, Setup detects all Plug and Play devices using Plug and Play detection. Setup then employs an elaborate process for finding legacy (non-Plug and Play) components. It reads configuration files such as CONFIG.SYS and scans INF files, searching for device information. Setup scans device drivers and ROM strings, fishing for hints about system devices.

Setup uses a basic form of detection for components that can be detected and configured more reliably (for example, processors and COM ports) and uses a more robust scheme (that Microsoft has dubbed safe detection) to find devices that are more likely to cause configuration problems.

Setup uses safe detection to detect the following classes of devices:

If Setup finds hints of any of the preceding device classes, it looks directly to I/O ports (except in the case of sound cards, as noted later in this section). If Setup doesn't find any evidence of one of these device classes, it stops detecting for that class rather than risking hanging the system with a search for a nonexistent component.

For Windows 3.1 upgrades, the preliminary search for network adapters begins with a search for and a scan of the LSL.COM, IPX.COM, and PROTOCOL.INI files. The search for SCSI controllers and proprietary CD-ROM adapters begins with CONFIG.SYS. Setup searches internal ROM strings for the presence of SCSI hard drives. Setup checks CONFIG.SYS and SYSTEM.INI for information about sound cards. If it finds evidence of a sound card, however, Setup does not scan the I/O ports to locate the device (as it does with the other safe-detect device classes). Instead, Setup performs only the specific detection routines defined in the information file MSDET.INF.

NOTE: MSDET.INF is an INF file in the Windows/INF directory that defines the specific devices for which Setup searches. A manufacturer's INF can add a device to MSDET.INF, causing Windows 98 to search for that device at startup.

Windows 98 includes a Setup recovery feature. If the installation fails for some reason, and you have to start over, Setup picks up where it left off. Setup can accomplish this smart recovery because it keeps a log of installation events. When you run Setup, Setup checks for the Setup log and resumes the installation after the last successful step. See the section titled "Troubleshooting Windows 98 Setup," later in this chapter, for more about Setup recovery and the Setup log.

Windows 98 creates a log of the hardware detection process called DETLOG.TXT. If detection fails or the computer hangs, Windows 98 creates a file called DETCRASH.LOG. You learn more about DETLOG.TXT and DETCRASH.LOG later in this chapter.

Registering Windows 98

Like most software vendors, Microsoft encourages users to register their software. When you register Windows 98, you add your name to Microsoft's user database, and you provide Microsoft with a description of your Windows 98 implementation (hardware resources, system settings, and so on). If you register, you're entitled to certain benefits. Microsoft will notify you of upgrades and new products, and you may be eligible for special upgrade prices. Some third-party vendors use the Microsoft's registration database to notify users of their own products. When you register, you'll have the option of choosing whether you want to receive third-party materials.
The traditional way to register is to fill out the registration card included with the software and mail it in. Windows 98 includes a registration card, but it also provides another option: the Windows 98 Registration Wizard. The Registration Wizard prompts you for registration-related input, searches out the necessary system information, and then automatically registers your Windows 98 implementation with Microsoft over the Internet.
You can access the Registration Wizard through the Welcome to Windows 98 application. Welcome to Windows 98 typically opens automatically when you start Windows 98 for the first time (although this may depend on your OEM implementation). Otherwise, you'll find Welcome to Windows 98 in the System Tools Accessories (click Start, Programs, Accessories, System Tools, Welcome to Windows).
In the Welcome to Windows main screen, click Register Now to launch the Registration Wizard.

Using the Setup Command

The Windows 98 Setup program (SETUP.EXE) initiates and implements basic setup operations. You can use Setup to upgrade Windows 95 or Windows 3.1 systems or to perform a full installation under MS-DOS, Windows 3.0, or Windows NT systems.

NOTE: The Windows 98 Setup program can run from within MS-DOS, OS/2, Windows 3.1, Windows for Workgroups, or Windows 95. Microsoft recommends that you run Windows 98 Setup from within Windows, if possible. If you are installing Windows 98 on a system with an early version of Windows (Windows 3.0 or earlier), you must exit Windows and run Setup from DOS.

The Setup command can include a reference to an INF installation script that contains custom setup information. For more about using installation scripts with Setup, refer to "Customizing Installation," later in this chapter.

In addition to an optional installation script, the Setup command can contain one or more optional switches. Setup switches are listed in Table 2.1. Consider the following example:

setup msbatch1.inf /id /im

In this example, Setup uses configuration information located in the installation script msbatch1.inf. The /id switch tells Setup to skip the disk space check; the /im switch tells Setup to skip the memory test.

Table 2.1 Setup Command Switches

Switch Description
/T:tmpdir Specifies a temporary directory where Setup will copy its files. Replace tmpdir with the directory name. Any files already in the directory will be deleted. Setup creates the directory if it doesn't exist.
/c Does not load the SmartDrive disk cache.
/d Does not use existing Windows version for Setup.
/domain Specifies a domain name used by the client for Microsoft networks for logon
domain_name verification during Setup.
/id Skips the disk-space check.
/ie Does not create emergency boot disk.
/ih Skips the Registry check.
/im Skips the memory check.
/in Skips the setup of networking components.
/iq Skips the check for cross-linked files.
/is Skips ScanDisk and routine system check.
/iv Skips the display of billboards during Setup.
/ix Skips the character-set check.
/iw Skips the display of the End User License Agreement.

Upgrading to Windows 98 from Windows 95 or Windows 3.x

One of the first things Setup does is to search your system for existing versions of Windows. If Setup finds Windows 95, it automatically upgrades the Windows 95 system to Windows 98 and preserves system settings from the old configuration.

If Setup finds Windows 3.x, Setup asks whether you want to install Windows 98 to a new directory or to the existing Windows directory. If you install to the existing Windows directory, Setup replaces system files and upgrades the existing system. If you install to a different directory, Setup automatically configures the PC to dual-boot between the previous OS and Windows 98. You learn more about dual-boot options later in this chapter.

Setup gives you the option of preserving the existing system files so that you can uninstall Windows 98 if necessary. ( that this is for the upgrade option--installing Windows 98 to the existing Windows directory. If you install to a different directory, the existing OS remains unchanged and you aren't asked whether you want to preserve it.) If you elect to preserve the existing OS, Setup will save the existing system files in a file called WINUNDO.DAT, located in the root directory of the hard drive. (If the hard drive contains multiple logical drives, Setup asks you to specify a logical drive.) Setup also creates the file WINUNDO.INI, which contains information about the original location of the system files. If you save the existing system files, Uninstall Windows 98 becomes an uninstall option in the Install/Uninstall tab of Control Panel's Add/Remove Programs application. Setup warns you that backing up the existing system files requires approximately 50 M of disk space.

NOTE: If you install Windows 98 to a different directory, you will probably have to reinstall any existing applications to run them in Windows 98. In many cases, you can get Windows 98 to run an existing application by specifying the path to the required DLLs using the path command, but Microsoft does not support or recommend this solution.

If you compress the drive with DriveSpace or convert to FAT32 after you have saved the system files, you cannot restore the system files.

The interactive Setup process described in the following sections is designed for speed and simplicity and does not provide a full range of configuration options. Use an installation script if you want to customize the Setup process. Installation scripts are described later in this chapter.

The Windows 95/98 upgrade requires little user input. Be prepared to supply Setup with the following information:

In most cases, Setup can obtain the other necessary settings from defaults or from the existing configuration; in some situations, however, you may be asked to supply additional information.

If you're upgrading from Windows 3.x to Windows 98, you may also be asked to supply the following information:

If your present operating system isn't configured for Microsoft networking (but you have networking hardware installed on your system), you are also asked to supply networking parameters such as computer name, workgroup name, and computer description (if your computer was not previously configured for the network, as described in the following procedure).

To upgrade from Windows 95 to Windows 98, follow these steps:

1. Place the Windows 98 CD in the CD-ROM drive and double-click Setup in the top-level directory of the CD. (Alternatively, connect to the Windows 98 installation files over the network; network installation options are discussed in Chapter 3.)

NOTE: Some versions of Windows 95 can auto-detect a newer version of Windows on the CD-ROM and ask whether you want to install it before you ever click the Setup program.

2. You see an announcement that says, "Welcome to Windows 98 Setup." Additional announcements follow, proclaiming that Setup is checking your system and preparing the Setup Wizard.
3. The Windows 98 license agreement appears. You must either accept the agreement or cancel Setup. Setup then continues to check your system and prepares an installation directory.
4. Setup asks whether you want to save the existing DOS or Windows system files so that you can uninstall Windows 98 if necessary. (The uninstall option was discussed earlier in this chapter, in "Upgrading Windows 98.") Click Yes or No. Preserving the System files requires approximately 50 M of disk space.
5. Setup asks you to enter the Windows 98 Product ID number supplied by Microsoft.
6. Setup asks you to select a channel set for Internet channels. Internet channels were introduced in Chapter 1, "Deploying Windows 98." The channel sets are organized by geographical region. The default is the United States. Select a channel set.
7. Setup asks whether you want to create an emergency startup disk. An emergency startup disk lets you reboot your system and recover certain key system files in the event of a system failure (see Chapter 36, "The Windows 98 Boot Process and Emergency Recovery"). It is a very good idea to create an emergency startup disk, label it, and store it where you can find it. that, because of changes to the file system, Windows 95 emergency startup disks typically do not work under Windows 98. You should create a Windows 98 emergency startup disk when you upgrade to Windows 98. If you elect to create an emergency startup disk, Setup prompts you to insert a disk in the floppy drive and warns that any files on the disk will be deleted. When the necessary files are copied to the emergency startup disk, Setup tells you to remove the disk.
8. The file-copy phase of Setup begins. Setup starts copying files to the local hard drive. This takes several minutes. In the meantime, Setup describes Windows 98's new features and displays some misty photos of users reacting to those features with gratitude.
9. When the file-copy phase is complete, Setup announces that it will restart the computer in 15 seconds. (You can preempt the progress bar by clicking Restart Now.)
10. When the computer restarts, you'll see the Windows 98 splash screen. Setup then attempts to configure your hardware.

NOTE: If you're installing over the network, Setup has to reconnect to the installation share after the system restarts. This may require that you log on to the network by using the appropriate user-level authentication method (for example, domain, Windows NT system, NetWare server). Make sure that you have the correct credentials to access the installation share and that the appropriate Primary Network Logon is active. Otherwise, the files will be inaccessible and the installation will fail.

11. The system shuts down and restarts again. Hardware setup continues. Setup announces that it is attending to the final configuration items:
12. After these final items are configured, the upgrade is complete. The system restarts with Windows 98.

To upgrade from Windows 3.x or Windows for Workgroups to Windows 98, follow these steps:

Don't forget to disable all Windows 3.x antivirus software and to disable any auto-start capability for virus checking before upgrading to Windows 98.

1. Click the File menu in Program Manager, select Run, and enter the Setup command with the necessary path and switches. (If you're installing over the network, refer to Chapter 3, "Network Installation," for more information about initiating a network installation.)
2. Setup announces that it is checking your system. Setup launches the ScanDisk utility, which looks for disk errors. You'll see a message that says Setup is preparing the Setup Wizard.
3. Setup displays the licensing agreement. You must accept the agreement or cancel Setup.
4. Setup asks you to provide a name for the Windows directory. The default option is C:\Windows. Alternatively, you can click Other Directory and enter a directory name. If you provide a different directory name, Microsoft displays a warning that only advanced users use a different directory name. If you want the old operating system to remain accessible in a multiboot configuration, select Other Directory and enter a different directory name.
If you choose to install Windows 98 into the directory that contains the existing operating system, Setup asks if you want to save the system files of the previous operating system. Saving the system files enables you uninstall Windows 98. See "Uninstalling Windows 98," later in this chapter, for more information.
5. The remaining installation steps are similar to the steps for DOS-based installation, described in the following section.

Installing Windows 98 on DOS, Windows 3.0, and Windows NT Systems

You can install Windows 98 on a system running MS-DOS, Windows 3.0, or Windows NT.

With each passing year, the number of DOS machines diminishes--and the number of DOS-only machines capable of supporting a Windows 98 upgrade is small to begin with (see "System Requirements," earlier in this chapter). For what it's worth, however, you can run Setup on any computer with MS-DOS 5.0 or later.

You can upgrade Novell's DR-DOS to Windows 98 in the same way that you upgrade MS-DOS, except that you cannot configure a dual-boot with DR-DOS.

You can configure Windows 98 to dual-boot with OS/2, but you can't run Setup from OS/2--you must configure an MS-DOS/OS/2 dual-boot and then upgrade MS-DOS to Windows 98. Remember that Windows 98 cannot read HPFS partitions.

If you're installing on a Windows 3.0 system (or earlier) or a Windows NT system, you have to run Setup from MS-DOS--you can't install from Windows.

If you perform a new installation to a reformatted or a newly formatted hard disk, you will need a CD-ROM-enabled boot disk to access the Windows 98 CD-ROM. The steps for creating a CD-ROM-enabled boot disk are described later in this chapter. If your PC's BIOS supports CD-ROM boot, you can boot directly to the Windows 98 CD.

For installations from MS-DOS, Setup does not migrate settings from the previous operating system. You can, however, define a specific configuration using an installation script. (Windows 98 installation scripts are described later in this chapter.)

For network installations, Setup must be able to reconnect to the installation share under Windows 98 if it is to complete the installation process. If real-mode network drivers are running when you start the Windows 98 installation from MS-DOS (as they would have to be if you're installing over the network), Setup installs the required network client. You can specify additional networking information by using an installation.

If you're running MS-DOS-based Setup on an MS-DOS, Windows 3.0, or Windows NT machine, you have to supply the following information:

Additional choices may appear depending on what Setup finds on your system.

Follow these steps to install Windows 98 on MS-DOS, Windows 3.0 systems or to perform a new installation:

1. Start Setup from the MS-DOS prompt. If you are performing a local installation to a reformatted hard disk, boot your PC using a CD-ROM-aware boot floppy disk (see "Creating a CD-ROM-Aware Boot Floppy Disk," later in this chapter). The Setup command should include the required path and switches and the path and name of an installation script if you are using one.
2. Setup announces that it is checking your system. It may launch the ScanDisk utility, which looks for disk errors. (See Chapter 17, "File Systems: File and Disk Resources," for more information about ScanDisk.)
3. Setup displays the licensing agreement. You must accept the agreement or cancel Setup.
4. Setup asks you to provide a name for the Windows directory. The default option is C:\Windows. Alternatively, you can click Other Directory and enter a directory name. If you provide an alternative directory name, Microsoft displays a warning that only advanced users use a different directory name.
5. Setup asks whether you want to save the existing DOS or Windows system files so that you can uninstall Windows 98 if necessary. (The uninstall option was discussed earlier in this chapter, in "Upgrading Windows 98.") Click Yes or No. Preserving the System files requires approximately 50 M of disk space.
6. Setup asks you to enter the Windows 98 Product ID number supplied by Microsoft.
7. Setup announces that it is preparing files and then prompts you to select a Setup option (Typical, Portable, Compact, or Custom). Windows 98 Setup options were discussed in detail earlier in this chapter and in Chapter 1. Choose a Setup option.
8. Setup asks you to enter user information. Enter an (optional) name and a company name. that the name you enter is not related to a user name or to the computer name. The name and company name are part of the licensing information. The name and company name you enter appear in the General tab of the Control Panel System application.
9. A dialog box asks if you want to select optional Windows components. (See Chapter 1 for a detailed discussion of Windows optional components.) The Setup option you chose in step 7 (Typical, Compact, Custom, or Portable) defines a set of default components that appear in this dialog box. You can add or remove components from the set. Choose Install the Most Common Components if you are satisfied with the default set. Select Show Me the List if you want to select additional components. Remember that you can add a component at any time, even if you don't choose it during Setup, by using the Control Panel Add/Remove Programs application (described in Chapter 6, "Control Panel"). If you chose the Custom option in step 7, you are automatically given the chance to select Windows components.
10. Setup asks for a computer name, a workgroup name, and a computer description. These parameters appear in the Identification tab of Control Panel's Network application. The computer name identifies the computer on the network. The computer name must be 15 characters or fewer; each character can be an alphanumeric character or one of the following characters: ! @ # $ % ^ & ( ) - _ ` { } ~ .
The workgroup name describes the group of computers to which the PC belongs. The group can be a workgroup, and Windows NT Server domain, or a NetWare server network.
The computer description appears along with the computer name in network resource lists (such as Network Neighborhood, if you select Details from the Network Neighborhood View menu).
11. Setup asks you to select a channel set for Internet channels. Internet channels were introduced in Chapter 1, "Deploying Windows 98." The channel sets are organized by geographical region. The default is the United States. Select a channel set.
12. Setup asks if you want to create an emergency startup disk. An emergency startup disk lets you reboot your system, regain access to your hard drive, and replace or recover certain key system files in the event of a system failure (see Chapter 36, "The Windows 98 Boot Process and Emergency Recovery"). It is a very good idea to create an emergency startup disk, label it, and store it where you can find it. that, because of changes to the file system, Windows 95 emergency startup disks typically do not work under Windows 98. You should create a Windows 98 emergency startup disk when you upgrade to Windows 98. If you elect to create an emergency startup disk, Setup prompts you to insert a disk in the floppy drive and warns you that any files on the disk will be deleted. When the necessary files are copied to the emergency startup disk, Setup tells you to remove the disk.
13. The file-copy phase of Setup begins. Setup starts copying files to the local hard drive. This takes several minutes. In the meantime, Setup describes Windows 98's new features.
14. When the file-copy phase is complete, Setup announces that it will restart the computer in 15 seconds. (You can preempt the progress bar by clicking Restart Now.)
15. When the computer restarts, you see the Windows 98 splash screen. Setup then attempts to configure your hardware.

NOTE: If you're installing over the network, Setup has to reconnect to the installation share after the system restarts. This may require that you log on to the network by using the appropriate user-level authentication method (such as domain, Windows NT system, NetWare server). Make sure that you have the correct credentials to access the installation share and that your new Windows 98 configuration will give you access to the appropriate logon. Otherwise, the files will be inaccessible and the installation will fail. See the discussion earlier in this section.

16. The system shuts down and restarts again. Hardware setup continues. Setup announces that it is attending to these final configuration items:
Setup asks you to enter the correct time zone and to set or verify the system time.
17. After these final items are configured, the upgrade is complete. The system restarts with Windows 98.

Dual-Booting Windows 98 with Windows 3.x and DOS

When you run Windows 98 Setup from a Windows 3.x machine, Setup prompts you to name the Windows 98 directory. If you install Windows 98 in the existing Windows directory, Setup converts your existing Windows 3.x installation into a Windows 98 installation--you won't be able to boot to Windows 3.x (although you can still boot to DOS, as described later in this section).

If you install Windows 98 to a directory that is different from the existing Windows 3.x directory, Setup automatically configures your PC to dual-boot with MS-DOS. To start MS-DOS on a dual-boot-enabled Windows 98 system, do either of the following:

From the DOS prompt, you can start Windows 3.x by typing the WIN command.

If you originally installed Windows 98 to the Windows 3.x directory, you cannot start Windows 3.x, but you can still configure your PC to boot to MS-DOS. To enable your Windows 98 PC to dual-boot to DOS, perform the following steps (your system must have MS-DOS 5.0 or later):

1. Turn off the hidden and read-only attributes for the file MSDOS.SYS in the top-level directory of the boot drive (usually drive C) by using the following command: 
attrib -h -s -r msdos.sys
2. Edit MSDOS.SYS. Change the value of the BootMulti parameter in the [Options] section of MSDOS.SYS to BootMulti=1. This change enables the multiboot feature for your PC.
3. Insert a DOS 5.0 (or later) system disk. Turn off the hidden and read-only attributes for the files IO.SYS and MSDOS.SYS (as described in step 1).
4. Copy the files IO.SYS, MSDOS.SYS, and COMMAND.COM from the MS-DOS system disk to the boot drive, giving the new files a .DOS extension: 
copy a:\MSDOS.SYS c:\MSDOS.DOS
copy a:\IO.SYS c:\IO.DOS
copy a:\COMMAND.COM C:\COMMAND.DOS

5. Create files called AUTOEXEC.DOS and CONFIG.DOS in the top-level directory of the boot drive. Your multiboot MS-DOS system will use these files in place of AUTOEXEC.BAT and CONFIG.SYS. Add any commands to these files that you want to include in AUTOEXEC.BAT and CONFIG.SYS files. (If you copy these files from a DOS floppy disk, edit the path references as necessary--watch out for references to drive A and make sure that all referenced files are accessible.)

After you complete these steps, reboot your system and start MS-DOS by pressing F4, F8, or the left Control key at system startup.

NOTE: If you're using disk compression software, Microsoft warns that you should also copy IO.DOS, MSDOS.DOS, COMMAND.DOS, CONFIG.DOS, and AUTOEXEC.BAT to your host drive. See Chapter 17, "File Systems: File and Disk Resources," for a discussion of file compression and host drives in Windows 98.

Booting to DOS can be useful in certain situations, but it is worth noting that there are also several options for redefining and customizing the MS-DOS operating environment from within Windows 98. If you're having trouble getting an MS-DOS application to work under Windows 98, try configuring the DOS properties for the application within Windows 98 before you resign yourself to booting DOS. See Chapter 11, "Windows 98 Architecture and Application Support," for more information about using MS-DOS applications in Windows 98.

Using Windows 98 with Windows NT Systems

Setup cannot perform a true upgrade--converting Registry and system settings, replacing the old OS, and so on--from Windows NT to Windows 98.

If you're considering converting a Windows NT computer to Windows 98, or if you're planning a Windows 98/Windows NT dual-boot configuration, be aware that Windows 98 can't read a Windows NT NTFS partition and that Windows NT 4.0 or earlier can't read a Windows 98 FAT32 partition. (Microsoft says that Windows NT 5.0 will support FAT32 partitions.) See Chapter 1, "Deploying Windows 98," and Chapter 17 for more about file system choices. Any directories used by both Windows NT and Windows 98 must reside on a FAT16 partition.

NOTE: Many people would say that converting a Windows NT machine to Windows 98 would actually be more of a downgrade, given Windows NT's superior security and stability. There are, of course, always exceptions for particular users in special situations. If you are running Windows NT 3.5 (or earlier) and you prefer the Windows 95/98 user interface, consider upgrading to Windows 4.0 rather than Windows 98. Windows 4.0 uses the Windows 95 user interface and includes many of the advanced features provided by Windows 98.

The Windows 98 Setup program won't run under Windows NT. If you want to convert a Windows NT system to Windows 98, first make sure that you have a working Windows NT emergency repair disk. Then boot to MS-DOS or Windows 95 from a CD-ROM-enabled floppy disk and run Setup. Do not install Windows 98 to the same directory that contains Windows NT. When Setup is complete, your system will boot to Windows 98--you cannot start Windows NT. If you want to restore the Windows NT boot capability, boot to your Windows NT emergency repair disk and choose the repair option to repair the Windows NT boot files.

If your system is presently dual-booting Windows NT with another operating system (DOS, Windows 95, or an earlier version of Windows), you can upgrade the other operating system to Windows 98. You will still be able to boot to DOS from the Windows 98 startup menu, as described in the section "Dual-Booting Windows 98 with Windows 3.x and DOS."

If your system currently isn't using either Windows 98 or Windows NT, the easiest way to configure a Windows 98/Windows NT dual boot is to install Windows 98 first and then install Windows NT to a different directory. Windows NT's Setup program takes care of configuring the dual boot, and both operating systems will appear in Windows NT's boot menu.

Creating a CD-ROM-Aware Boot Floppy Disk

If you're performing a full installation on a newly formatted hard drive, you'll need a floppy boot disk that provides access to the Windows 98 installation files. You may also need to use a CD-ROM-enabled boot floppy if the Windows 98 installation fails in a way that requires you to boot from a floppy to restart the installation. The Windows 98 CD is a bootable CD, so you can boot to it directly if your PC's BIOS supports CD-ROM boot.

The Windows 98 emergency startup disk includes a generic real-mode ATAPI CD-ROM driver. Once you have installed Windows 98 on your system, you can boot from the Windows 98 emergency startup disk and then access your CD-ROM by entering the drive letter at the command prompt (assuming that the generic driver works with your CD-ROM drive; it is a good idea to test as soon as possible to ensure that the startup disk can reach your CD). Windows 98 startup disks, however, are not always compatible with Windows 95 PCs because of the changes to the kernel necessary for supporting FAT32. If you're upgrading to Windows 98 from Windows 95 or an earlier version of Windows, you need a boot floppy that loads the necessary CD-ROM drivers. Some vendors may supply a CD-ROM-enabled boot floppy along with the Windows system software. If you don't have a CD-ROM-enabled boot floppy, you must create one.

To enable the CD-ROM drive from a boot floppy, you must load real-mode CD-ROM drivers. The exact procedure for how to do this depends on your hardware and on your configuration. The general procedure is as follows:

1. Specify the filename of your real-mode CD-ROM driver in CONFIG.SYS by using the DEVICE or DEVICEHIGH command, as shown here: 
DEVICE=CDROMDRV.SYS /D:mscd001
In this syntax, the following parameters are used:

CDROMDRV.SYS The real-mode driver for the CD-ROM drive. Make sure that the driver is present in the directory or provide a complete path to the driver.

D: The drive letter designation for the CD-ROM.

mscd001 The field name. Whatever you use for this name in CONFIG.SYS must match the corresponding value in AUTOEXEC.BAT. The values MSCD001, MSCD002, MSCD003, MSCD004, and so on are often used. If you use a name that matches an actual filename, the file with that filename will be inaccessible while the driver is active on the system.

2. Load the MSCDEX driver (MSCDEX.EXE) in AUTOEXEC.BAT and reference it to the CD-ROM driver designation defined in CONFIG.SYS (see step 1), as shown here: 
MSCDEX.EXE /D:MSCD001
In this syntax, /D:MSCD001 matches the parameter provided with the DEVICE command in CONFIG.SYS (see step 1).

Make sure that the file MSCDEX.EXE is present in the directory or provide a complete path. Look for MSCDEX.EXE on your OEM Windows 98 CD or on the CD-ROM manufacturer's driver disk. You can also find MSCDEX.EXE in the Windows\COMMAND directory of a Windows 98 PC.

Consult your CD-ROM manufacturer for additional instructions.

Customizing Windows 98 Setup with Installation Scripts

A Windows 98 installation script is a file that describes a complete Windows 98 configuration. The Windows 98 Setup program can install Windows 98 according to the specifications defined in an installation script. The installation script provides automatic answers for installation screen prompts, and it also specifies aspects of the configuration that otherwise could not be defined through Setup, such as the default gateway and the LMHOSTS file.

An installation script is basically a text file that uses the INF format (a format used for installing devices and applications on Microsoft systems). Although it is possible to create an installation script from scratch, more typically, network administrators create installation scripts in the following ways:

You can modify an installation script using a text editor application such as Windows 98's Notepad accessory. Appendix D provides a detailed description of installation script structure.

To run Setup using an installation script, provide the path and name of the script along with the Setup command. For example, if your installation script is named FREDINF.INF, and if it is located in the C:\ directory, you would initiate Setup using the following command:

setup c:\Fredinf.inf

The one-line Setup command is the easy part. The tricky part is creating the right installation script so that you get exactly the installation you want. Installation scripts are especially useful for network installations in which you may have to install several identical or nearly identical systems and you don't want to take the time to answer all the screen prompts. But you can also use installation scripts for local installations. You can save yourself some steps and free yourself from interactive Setup's baby-sitting duties if you use an installation script.

Here are some of the uses for an installation script:

The following sections introduce the installation script template files and describe how to create installation scripts using the Batch98 utility.

Using Installation Script Templates

Microsoft provides several sample installation scripts you can adapt for your own situations. These sample scripts are part of the Windows 98 Resource Kit. You can obtain the Windows 95 Resource Kit online at www.microsoft.com/windows95/info/w95reskit.htm. At this writing, it appears that the sample scripts won't be available with the Windows 98 Resource Kit.

The sample scripts are well commented and are a useful tool for learning how installation scripts work. The best way to learn to use the sample installation script files is to open them with a text editor and study them. You can use some of the scripts as is; some scripts require additional editing. (The comments tell you what to do.) Modify and merge the scripts to suit your purposes. (For more information about the structure of installation scripts, refer to Appendix D, "Installation Script.")

NOTE: The sample scripts are a valuable resource for learning about installation scripts, but if you want a quick and simple way to create a script for a specific situation, consider the Batch98 utility (described in the next section) before you bury yourself too deeply in the sample scripts. You may find it useful to generate a script using Batch98 and then check that script by comparing it to an appropriate sample script.

The sample installation scripts available with the Windows 95 Resource Kit are as follows:

Script Name Description
AUTOMATE.INF Shows how to implement an automated installation.
DEFAULT.INF Shows how to implement an interactive (non-automated) setup, but with different default settings.
INIPREP.INF Shows how to modify and remove settings in INF files.
MINBATCH.INF Shows the minimum script required for automated upgrade.
MSNET.INF Shows how to configure Microsoft networking components.
MWNET.INF Shows how to configure Microsoft Client for NetWare Networks and other NetWare-related items using an installation script.
REGIONAL.INF Shows how to configure regional settings such as keyboard layout, language preferences, locale.
USERPROF.INF Shows how to configure user profiles, group policies, and remote administration of the Registry.

For more information about configuring and troubleshooting installation scripts, see Appendix D.

Creating Installation Scripts with Batch98

Microsoft's Batch98 utility (tools\reskit\batch\batch.exe on the Windows 98 CD) enables you to create Windows 98 installation scripts for automated installations. Batch 98 is also part of theWindows 98 Resource Kit which you can purchase in book form, or you can electronically through Microsoft: www.microsoft.com.Batch98 (shown in Figure 2.1), which provides an interface for entering configuration information that will become part of the installation script. Batch98 offers significantly more customization than you get if you interactively step through the Setup process, but it still offers only a subset of possible Windows 98 configuration settings.

Figure 2.1

The Batch98 dialog box.

You can use a Batch98-generated installation script to automatically configure the following elements:

Batch98 also enables you to preconfigure responses to Setup prompts. You can tell Setup to auto-accept the user license agreement or to answer No to all version-conflict messages.

You can also use Batch 98 to specify an exported Registry file (that is, a .REG file; see Chapter 10, "Mastering the Windows 98 Registry") that will accompany the automated installation. In this way, you can extend the scope of Batch98 to include features that aren't referenced directly in the Batch98 user interface.

Using Batch98

To use Batch98, install and launch the Batch98 application (refer to Figure 2.1). Enter or modify the settings that Batch98 will use when generating the installation script by clicking one of the four System Settings buttons described in the following chart. The System Settings dialog boxes are discussed in greater detail later in this chapter.

Button Description
General Setup Setup prompts, user information, computer name, desktop icons,
Options printers, and other configuration options.
Network Network protocol, client, and service information. You can also define
Options access control settings (share-level or user-level).
Optional Optional Windows 98 components. These are the optional components
Components available (after Setup is complete) through the Windows Setup tab of the Control Panel Add/Remove Programs application. The defaults do not precisely coincide with any of the basic installation types (Custom, Typical, Portable, Compact). If you're going to use the defaults, you may want to scan through the list to make sure that you know what you're getting. that if you use the Gather Now button (described in the next paragraph) to gather the current Registry settings, Batch98 selects the components currently installed on the system as optional components.
Advanced Options Designate a Registry file and/or a System Policy file.

You can use the Gather Now button in the Batch98 dialog box to automatically assign values for the system settings parameters that coincide with the present configuration of the machine you're using. Gather Now scans the Registry for all settings applicable to Batch98.

When you have finished configuring system settings for the Windows 98 installation script, click Save Settings to INF to save the installation script. The default name for the script is MSBATCH.INF. Make sure that the reference to the installation script in the Setup command (as described in the preceding section, "Customizing Windows 98 Setup with Installation Scripts") includes a complete path to the directory in which you save the script.

After an installation script is created, you can review or revise the settings by opening the file using the Open command in the Batch98 File menu. You can then make your modifications and click Save in the File menu to save any changes.

The following sections detail the Batch98 System Settings dialog boxes and describe a few advanced features, as follows:

Batch98 General Setup Options

Click the General Setup button in the Batch98 dialog box to invoke the General Setup Options dialog box. The General Setup Options dialog box contains several tabs defining various aspects of the installation process and the general configuration. The tabs and settings of the General Setup Options dialog box are described in Table 2.2.

Table 2.2 Batch98 General Setup Options

Tab Setting Comment
Install Info Product ID Optional Windows 98 Product ID number.
Directory Installation Destination directory for Windows 98 files.
  Installation Do Not Show Disables Setup warning that appears when a previous version of Windows is in a directory other than the
Directory installation directory.  
  Uninstall Options uninstall information during Setup. Radio buttons let you choose whether or not to create
  User Info Responses to computer- and user-info prompts that normally appear during Setup:
  User Name  
  Company Name  
  Computer Name  
  Workgroup  
  Description  
Setup Prompts Auto-Accept End-User License Agreement Do Not Prompt for Emergency Startup Disk Items cause Setup to skip or auto-respond to certain prompts that appear during the Setup process (for a fully automated installation, select all the boxes):Auto-Answer "No to All" to Version Conflict Dialogs Automatically Reboot PCI and PnP Machines During Setup Do Not Search Source Folder for New Devices Skip the PC Card Microsoft warns (PCMIA) Wizard that this option enables protected-mode socket services, which may cause problems. If you don't have a PC card, you normally don't have to check this box for unattended installation.
Regional Settings Time Zone Region-specific settings such as time zone, language, and keyboard layout: Keyboard Layout Language and dialect settings
Desktop   Lets you decide whether to include the standard icons and miscellaneous accouterments on the desktop:
  My Documents  
  Internet Explorer  
  Network Neighborhood  
  Outlook Express  
  Recycle Bin  
  Setup the Microsoft Network  
  Delete Online Service from the Desktop After Setup  
  Do Not Show Windows 98 Welcome Screen  
  Do Not Show the Windows 98 Registration Wizard  
Printers   Lets you add one or more printers automatically during Setup (see Figure 2.3). Use this dialog box to install either a local or a network printer.
  Printer Name  
  Printer Type Printer model (must be the exact name of printer driver; see the printer model designations listed in the Add Printer Wizard).
  Printer Port Printer port for a local printer; share name and path for a network printer.
MRU Locations   Most Recently Used (MRU) lists are the lists of recent paths or names that appear throughout Windows 98 when you click the down arrow to the right of a text box. Use the MRU Locations tab to enter paths that will appear in the MRU list during Setup. Enter an item and click Add MRU.
Display Settings   Display settings for color depth and resolution. These settings appear in the Settings tab of the Control Panel Display application.
User Profiles   Lets you choose whether or not the system will use User Profiles. If you choose to enable User Profiles, you can opt to include desktop icons and Network Neighborhood contents and/or Start Menu and program groups in the profile settings.

The Setup Prompts tab (shown in Figure 2.2) lists the auto responses you need to accomplish an unattended installation. By default, all items in the Setup prompt are enabled except Skip the PC Card (PCMIA) Wizard option. Microsoft warns that enabling the Skip the PC Card option can cause problems because so doing enables protected mode socket services. If you don't have a PC card, you can leave the Skip the PC Card option deselected and, most likely, you won't get a prompt from Setup.

Network Options

The Network Options button in the Batch98 dialog box invokes the Network Options dialog box (see Figure 2.3). The Network Options dialog box lets you configure network protocols, services, and clients; it also lets you choose share-level or user-level access. The Network Option settings are roughly similar to the values configured in the Control Panel Network application (as described in Chapter 5). The tabs of the Network Options dialog box are described in Table 2.3.

Figure 2.2

Batch98's Setup Prompts tab.

Figure 2.3

Batch98's Network Options dialog box.

Table 2.3 Batch98 Network Options

Tab Comment
Protocols Choose IPX/SPX-Compatible, NetBEUI, Microsoft 32-Bit DLC, or TCP/IP. Click the TCP/IP Settings button to configure TCP/IP settings. If you select more than one protocol, you can choose one as the default.
Services You can choose No File and Print Sharing, File and Printer Sharing for Microsoft Networks, or File and Print Sharing for NetWare Networks. (You must choose one of the three options.) Each of the network service options offers a number of configuration settings.
Clients Choose Client for Microsoft Networks, Client for NetWare 3.x/4.x Networks, and/or NetWare Directory Service. Then set logon options.
Access Identical to the Access Control tab in the Control Panel Network application.
Control Choose share-level or user-level access; designate a source for user and group information--a Windows NT domain, a Windows NT Server or Workstation (v3.51 or v4.0), or a NetWare Server.
Additional Choose Banyan DOS/Windows 3.1 Client or Novell NetWare 3.x or 4.x
Clients Workstation Shell. You can also add other clients by entering the appropriate strings for protocol, client, and services.

Batch98's network options provide a quick and efficient way of fine-tuning the network configuration during Setup, but they have one major limitation (at least, at this writing). Batch98's network options do not provide the capability to enter a separate network configuration for each network adapter. The settings you enter in the Network Options dialog box apply to all adapters present on the system at the time of setup. This applies not only to systems (with two or more adapter cards) but also to systems that include both a network card (such as an Ethernet card) and also the dial-up adapter provided automatically when you install dial-up networking.

The configuration for the dial-up adapter is often different from the configuration for the network adapter card. For example, you may want to obtain an IP address automatically through DHCP for your dial-up Internet account, and you may have a static IP address on your local LAN. (Microsoft actually recommends that you not even configure TCP/IP properties for the dial-up binding but instead configure TCP/IP properties through individual dial-up networking connections.) If you plan to use more than one adapter on the new system, you may have to modify the settings for one of the adapters in the Network application after Setup. Another consequence of the two-adapter problem is that, if you configure the installation script to enable file and print sharing for the local network, Setup may configure file and print sharing on the dial-up adapter. (Sharing files with the Internet from a Windows 98 machine presents some serious security issues--this should never happen by accident.)

Batch98's inability to recognize multiple adapters also applies to the Registry Scan feature invoked through the Gather Now button (described earlier in this chapter). If you have multiple adapters, Batch98 simply uses one of the adapters to formulate the network configuration settings. Make sure that the settings you use to generate the installation script coincide with the settings you need to connect to the installation share and to log on at the conclusion of Setup.

Optional Components

The Optional Components button invokes the Optional Components dialog box, which lets you choose Windows 98 components (accessories, system tools, multimedia and communications components, and so forth). This list is similar to the list of components you'll encounter if you choose Select Components during installation or if you choose Windows Setup in the Control Panel Add/Remove Programs application. For some reason, Batch98's default components do not correspond to any of the standard installation types (Custom, Typical, Compact, or Portable). Choose the components you want to install on the new system. If you use the Batch98's Gather Now button to collect existing Registry settings, the components now on the system are enabled for the installation script.

Advanced Options

The Advanced Options button invokes the Advanced Options dialog box (see Figure 2.4). You can used the Advanced Options dialog box to designate either of the following items:

Figure 2.4

Batch98's Advanced Options dialog box.

Windows 98's Registry editor (described in Chapter 10) lets you export the partial or complete copy of the Registry to a text file. That Registry text file (which, by default, has a .REG extension) provides a complete description of the Registry or a branch of the Registry. Batch98's Advanced Options dialog box lets you add an exported Registry file to the installation script.

Enter the Registry filename in the uppermost text box in the Advanced Options dialog box. You can also browse for a Registry file by clicking the Browse button. You must click the Add button to add the file to the current Registry file list.

Generating Multiple Installation Scripts with Batch98

On Microsoft networks, each computer must have a unique computer name. Even if all other settings on all computers are identical, each computer requires a unique computer name if it is to coexist with other computers on the network. If your network is a TCP/IP network with manually configured IP addresses, each computer also needs a unique IP address. Batch98 includes a Multiple Machine-Name Save feature that uses a collection of installation script settings (as defined in Batch98) to generate a series of installation scripts--with each script bearing a unique computer name and (optionally) a unique IP address.

The Multiple Machine-Name Save feature works a little like a list processor. The script settings are "merged" with a file that contains a list of computer names and IP addresses. The format for the list file (called the machine name file) is as follows:

computer1
computer2, 155.121.131.45
Zoro
BrueghelElder, 162.134.14.66

Each line starts with a computer name (in this example, computer1, computer2, Zoro, or BrueghelElder); each computer name appears on a separate line. If you want to configure an IP address for the computer, separate the IP address from the computer name with a comma. that you don't need an IP address for every entry.

A blank line marks the end of the file.

Batch98 does not check for errors in the list file (such as illegal computer names, duplicate IP addresses, and so forth). It is a good idea to check each line of the file carefully to make sure that the information is correct.

When you perform a multiple machine-name save, Batch98 asks you for the name of the machine name file and the name of the directory in which you want to save the set of installation scripts. The filenames for the scripts are BSTP0001.INF, BSTP0002.INF, BSTP003.INF and so on (up to BSTP9999.INF).

To use Batch98's Multiple Machine-Name Save feature, follow these steps:

1. Create a machine name file of computer names and IP addresses, as described earlier in this section.
2. Use Batch98 to create an installation script specification.
3. In the main Batch98 dialog box (refer to Figure 2.1), pull down the File menu and select Multiple Machine-Name Save.
4. In the Multiple Machine-Name Save dialog box, click the Machine Name File button and select the machine name file you want to use. Click the Destination of Save button to choose a directory for the installation scripts.
5. Click the Save Files button to generate and save the installation scripts.

Uninstalling Windows 98

As this chapter has described, if you're performing an upgrade, you can configure your system so that you can uninstall Windows 98 at a later date and revert to your previous operating system.

To set up Windows 98 so that you can automatically uninstall it, follow these steps:

1. Install Windows 98 to the previous Windows directory.
2. When Setup asks if you want to save system files, click Yes.

If you have to uninstall Windows 98, go to the Control Panel and double-click the Add/Remove Programs application. In the Install/Uninstall tab, select Windows 98 and click Add/Remove.

If you didn't set up Windows 98 for the uninstall option, use the following procedure to uninstall Windows 98. You'll need a bootable floppy to complete this procedure--see step 10:

1. Boot Windows 98 in command-line mode by pressing F8 or the left Control key at startup and selecting Command Prompt Only; alternatively, boot to another operating system using the F8 startup menu (if you're configured to dual boot) or boot to a startup disk. Microsoft recommends that you copy the SCANDISK.EXE , SCANDISK.INI, and DELTREE.EXE files from the \Windows\commands directory to the root directory.
2. Run ScanDisk to delete any long filenames on your system (if you're reverting to DOS or Windows 3.x/3.1.x). Edit the file SCANDISK.INI to set the following parameters:

labelcheck=on Checks for invalid characters in volume labels

spacecheck=on Checks for invalid spaces in filenames

3. Run ScanDisk on your boot drive: 
scandisk c:
4. Delete the Windows directory (and all subdirectories) using deltree command:

deltree windows If your Windows directory is called windows

5. Delete IO.SYS, MSDOS.SYS, CONFIG.SYS, and AUTOEXEC.BAT from the root directory of your boot drive.
6. Delete the winboot directory (if it exists): 
deltree winboot.*
7. Delete the following log files from the root directory: 
setuplog.*
bootlog.*
detlog.*
8. Delete the DBLSPACE.BIN and DRVSPACE.BIN compression drivers from the root directory of the boot drive or host drive (if the drive is compressed).
9. Delete COMMAND.COM from the root directory.
10. Boot to a bootable DOS floppy. If you are removing Windows 98 in a dual-boot situation and you want to be able to boot to another operating system that is currently present on your system, the system files on the boot disk (for example, autoexec.bat, config.sys) should contain the commands necessary to boot the other operating system. Or, the autoexec.bat and config.sys files from the other operating system may be stored in your root directory under the names AUTOEXEC.DOS and CONFIG.DOS, in which case you can simply rename these files (after you perform the SYS command--see step 13). Be ready to copy a version of COMMAND.COM that is compatible with the new operating system to the root directory (see Step 12). You may want to include COMMAND.COM on the boot floppy. Also, be sure the floppy boot configuration supports the SYS command (contains the file SYS.COM). Restore the system files using the SYS command: 
sys C:
In this syntax, C: is the boot drive (or host drive if the drive is compressed).
11. If you have a compressed drive, make sure that the file DBLSPACE.BIN is in the root directory of the boot drive. If it isn't, place a copy of DBLSPACE.BIN in the root directory.
12. Make sure that COMMAND.COM is in the root directory of the boot drive. If it isn't, place a copy of COMMAND.COM in the root directory.
13. In the root directory, change the name of CONFIG.DOS to CONFIG.SYS. Change the name of AUTOEXEC.DOS to AUTOEXEC.BAT. (This action restores the CONFIG.SYS and AUTOEXEC.BAT files from the previous operating system.)

Troubleshooting Setup

Any process as internally complicated as Windows 98 Setup offers untold opportunities for errors and failures. The state of the computer after a failure--and therefore the procedure for recovery--depends on where in the process Setup failed.

If your system stops unexpectedly during Setup, follow these steps (in this order):

1. Press F3 or click the button labeled Exit.
2. Press Ctrl+Alt+Del.
3. Turn off your computer, wait 15 seconds, and then restart.

Windows 98 includes built-in mechanisms for troubleshooting Setup. Setup logs each step of the installation process and can later use the logged information to circumvent many types of failures.

Setup stores information on the installation in the following log files:

SETUPLOG.TXT A log of installation events.

DETCRASH.LOG A record of the hardware detection process, created if Setup fails during hardware detection. Setup also creates a text file equivalent to DETCRASH.LOG called DETLOG.TXT.

When you restart your computer after a crash, Setup attempts to use the logged information to retrace its steps and resume the installation.

Using Setup's Built-In Recovery Features'

If Setup fails during the early phase of an installation (before hardware detection), when you restart, Setup asks whether you want to use Safe Recovery to resume the installation process. If you elect to use Safe Recovery, Setup reads the log file SETUPLOG.TXT and uses the information to determine the point at which the installation failed.

NOTE: If you choose not to use Safe Recovery, Setup starts over with the installation.

Setup records the start and completion of each installation step in SETUPLOG.TXT. When you attempt to recover after a crash, Setup reads SETUPLOG.TXT to learn which steps began but did not finish--those unfinished steps are the most likely to have caused the failure. Setup then skips any steps that might have caused the failure and proceeds from that point with the installation. If Setup fails again because of another installation step, Setup again recovers (after rebooting), skips the step that caused the failure, and resumes the installation.

If Setup fails during hardware detection, Setup places the hidden file DETCRASH.LOG in the root directory of the drive on which you're performing the installation. (Windows 98's elaborate detection routines for non-Plug and Play hardware are a common cause of installation failures.) DETCRASH.LOG includes a record of memory and I/O port information at the moment of the crash. After the computer restarts, if Setup finds DETCRASH.LOG, it immediately switches the operating system to Safe Mode, checks the devices currently in the Registry, skips the failed component, and proceeds with the installation.

Windows 98's built-in Safe Recovery can successfully circumvent many types of installation failures. However, Safe Recovery does not always solve the problem. In some cases, Setup cannot recover the installation. Also, because Safe Recovery finishes the installation by skipping failed components, the resultant system may include hidden instabilities. , however, that the Do Not Use Safe Recovery option does not really solve the problem, either, because you will most likely be executing an instant replay of the failed installation. Microsoft recommends the Safe Recovery option when restarting after an installation failure.

Inspecting the Logs

If Setup fails and you want to determine why, you can do what the Safe Recovery feature does: Read the setup log files and look for suspicious entries. Look for components that started to install and never finished. Look for error messages or other unusual entries. The logged entries are sequential: Start at the end of the file for the last events.

SETUPLOG.TXT is an ASCII text file you can read with a text editor such as Notepad. DETCRASH.LOG is a binary file only Setup can access directly, but when DETCRASH.LOG is created, an equivalent ASCII file called DETLOG.TXT is also created (as a hidden file) in the root directory of the drive on which you're performing the installation.

You may also want to examine the following files:

NETLOG.TXT A log of the detection and installation of networking components.

BOOTLOG.TXT A log file created during the system startup process. BOOTLOG.TXT is a tool for troubleshooting all types of Windows 98 startup problems. A BOOTLOG.TXT file is created automatically when Windows 98 boots for the first time during Setup.

Table 2.4 shows Windows 98 Setup log files and some entries to watch for in each of the files.

Table 2.4 Setup Log Files and Some Critical Troubleshooting Entries

Setup Log File Contents Entries to Watch
SETUPLOG.TXT Log of Setup process error (system error) failed (installation failure) [not Configured] (items that were not configured) COMPLETE (indicates that a section completed successfully)
DETLOG.TXT Log of hardware error (system error) detection process detected (devices detected) devices verified (devices with settings in (the ASCII equivalent of DETCRASH.LOG) Registry) AvoidMem (UMB address ranges Setup avoided)
NETLOG.TXT Log of network NDiCreate (object_name) (Setup successfully
  component detection created an internal object, where object_name is the name of the protocol, adapter, service, and so on) Validating (adds object to the Registry and creates binding)

Troubleshooting Tips

Some of the most common causes of Setup failures are listed here:

Some of the preparatory steps described earlier in this chapter are important for avoiding trouble, and these steps are important remedies if trouble is found. For example, you should disable TSRs and timeout features, check the system requirements, and disable display utilities and video drivers. It is also good idea to scan your hard disk for viruses before you start Setup.

Some other common Setup problems are described in the following sections.

ScanDisk

If ScanDisk displays a message that says you don't have enough memory, try freeing some conventional or upper memory. See Chapter 11, "Windows 98 Architecture and Application Support," or Chapter 32, "Windows 98 Configuration Files."

If you're running Setup from MS-DOS, Setup may report errors from long filenames. Setup proceeds in spite of these errors.

If you can't get ScanDisk to work in Setup, you can always disable Setup's ScanDisk check using Setup's /is switch.

Compressed Drives

If you are installing Windows 98 to a compressed drive, you may see an error message warning you that there is not enough space on the host partition. See Chapter 17 for a discussion of host drives and compression software in Windows 98. If you have an uncompressed drive available, try installing Windows on the uncompressed drive instead. If that isn't possible, delete files on the host partition. Alternatively, free up space on the host drive (refer to the documentation for your compression software). For Windows 3.1 systems, if you have a permanent swap file, try making the swap file smaller: click Virtual Memory in the 386 Enhanced Control Panel.

Conventional Memory

Windows 98 Setup needs 432 K of conventional memory. The purpose of removing unnecessary TSRs is to free up conventional memory. Microsoft recommends the following CONFIG.SYS settings for making the best use of available memory:

MS-DOS 5.0 or later:

device=himem.sys
device=emm386.exe noems
dos=high,umb

Also try using the MS-DOS MEMMAKER utility to optimize memory (if it is available on your system).

MS-DOS Boot Partition

Windows 98 can't install unless your system has an MS-DOS boot partition. If you see a message that says Setup can't find a valid boot partition, you may have a hard disk problem. However, Microsoft points out that this error may also result from a hidden compression host drive or a network drive mapping over the boot drive. Verify the viability of the boot partition using Fdisk. Check all drive mappings and host drive assignments.

Incorrect Configuration of Legacy Hardware

Some hardware detection problems are caused by hardware that was configured incorrectly under the previous operating system. If Setup's Safe Detection and Safe Recovery features can't circumvent the problem, try disabling the ISA enumerator in the SYSTEM.INI file:

device=ISAPNP.386

Default User Policy Settings

Default User Policy settings can cause a failure when Setup attempts to launch Windows.

Conclusion

This chapter described the Windows 98 Setup process and discussed some preliminary tasks you must attend to before installing Windows 98. The chapter also outlined procedures for upgrading to Windows 98 and performing a full installation from a newly formatted disk. You also learned about automating the installation process using Windows 98 installation scripts, and you learned how to uninstall Windows 98.

Chapter 3 discusses network installation techniques.

Previous chapterNext chapterContents

� Copyright, Macmillan Computer Publishing. All rights reserved.