Chapter 5 - Setup Technical Discussion

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This chapter provides technical details about Microsoft Windows 98 Setup, including background information about Safe Recovery and detailed descriptions of the Setup and system startup processes.

Overview of Setup Technical Discussion

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

You must know certain technical details when using Microsoft Windows 98 Setup within your particular computing environment. This chapter presents technical information about how to ensure the safe detection of hardware, recovery from problems, and verification of configurations. It goes on with detailed information about the startup process, system startup files, Windows 98 Setup with non-Windows 98 operating systems, removing Windows 98, and troubleshooting Windows 98 Setup.

Safe Detection, Safe Recovery, and Verification

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

This section provides technical details about the features that ensure safe hardware detection, recovery from Setup problems, and configuration verification in Windows 98 Setup.

Safe Detection in Windows 98 Setup

Devices and buses are grouped as classes in Windows 98 for purposes of detecting and installing device drivers and managing system resources. Windows 98 differentiates between devices and drivers that comply with the Plug and Play specification and earlier versions of devices and drivers (referred to in the Microsoft Windows 98 Resource Kit as legacy devices). Because of this differentiation, Windows 98 Setup detects hardware components and devices in two ways:

  • Using Plug and Play, an interactive query process, to identify Plug and Play–compliant devices and peripherals. 

  • Using a Plug and Play detection process for legacy devices and peripherals. 

After Setup detects a device, it adds configuration information to the registry and installs the appropriate device drivers. The same procedures used during Setup for detecting Plug and Play or legacy hardware devices are also used to detect or configure new devices after Windows 98 has been installed.

Windows 98 supports detection of base computer components, such as communications ports and processor type, and provides more robust detection of computer devices, such as display adapters, pointing devices, hard disk controllers, floppy-disk controllers, and network adapters.

Windows 98 Setup also tries to detect any hardware resource conflicts early in the installation process. This helps to avoid the problems that occur when such hardware resources as Interrupt Requests (IRQs), I/O addresses, and direct memory access (DMA) are used by more than one device.

To avoid computer failure during the detection process, Windows 98 uses a safe detection method to search for hints from configuration files, read-only memory (ROM) strings, or drivers loaded in memory to determine whether the computer contains each class of hardware. If no such hints are found, the detection process skips detection of the entire class. If hints are found, the detection process seeks information from specific I/O ports.

Windows 98 automatically reads the command lines in Config.sys to find hints for device class detection. Then Windows 98 loads detection modules based on information in the Msdet.inf file, which lists the hardware to be detected and points to specific INF files for each device class (for example, Scsi.inf for SCSI host adapters). Device information from the INF files is written to the registry.

For more information about the format of these files, see Appendix C, "Windows 98 INF Files."

Windows 98 can also read a particular Config.sys device= line for resource information to be avoided (that is, protected) during the detection process. This is useful if Windows 98 Setup cannot detect or support a certain device when it is known that the detection process can cause such a device to fail. For example, the detection process could render a fax modem inoperative because scanning the I/O port might confuse the device driver. Windows 98 can read the device= line in Config.sys for this model and protect the associated I/O region from other detection modules.

Windows 98 Setup asks you to confirm which classes should be skipped in the detection process. If you know that the computer has a device in one of those classes, you can force Setup to detect that device class.

Safe detection exists for four classes of devices: network adapters, SCSI controllers, proprietary CD-ROM adapters, and sound cards.

Safe Detection of Network Adapters

Windows 98 Setup performs the following kinds of steps for safe detection of network adapters:

  • Find Lsl.com in memory; if present, inquire for network adapter settings.

  • Find Ipx.com in memory; if present, inquire for network adapter settings.

  • Search the Windows, Windows for Workgroups, and LAN Manager directories for Protocol.ini; if present, read the file to find network adapter settings.

Safe Detection of SCSI Controllers

When trying to detect SCSI adapters, Windows 98 Setup checks for device drivers in Config.sys and then scans ROM strings from the SCSI adapter for manufacturers' names. If known drivers or known strings are found, the corresponding detection procedure for that class is used; otherwise, the entire class is skipped. A list of the known strings and drivers that Windows 98 Setup checks is stored internally in a detection dynamic-link library (DLL). (For more information about the SCSI devices and drivers that Windows 98 supports, see the Manufacturers and Models lists in the Add New Hardware option in Control Panel.)

Different SCSI devices require different methods for safe detection. For example, a SCSI card is typically used with a combination of hard disks, CD-ROM drives, tape backup drives, scanners, and similar devices. For everything to work (except the hard disk), some sort of device driver must be loaded in Config.sys.

For hard disk drives, however, the driver usually is not loaded in Config.sys, but INT 13 ROM is enabled. Therefore, safe detection for SCSI class devices looks for a ROM string with a manufacturer's name.

Safe Detection of Proprietary Adapters for CD-ROM

Windows 98 supports Mitsumi, SONY, and Panasonic proprietary adapters for CD-ROM. Because drivers for these devices are loaded in Config.sys, safe detection first scans Config.sys for the drivers that are present. If a device= line for such a driver is found, the corresponding detection module is loaded for that type of device.

Safe Detection of Sound Cards

Safe detection scans Config.sys and reads System.ini for hints about sound cards. If known drivers are not found, the entire class is skipped.

If Windows 98 does not have detection code for certain hardware, the equipment manufacturer can force a device to be detected by adding information about it in the Msdet.inf file. Windows 98 detection behaves as if it has detected the device and installs the device according to the INF information provided by the equipment manufacturer.

Windows 98 Setup does not detect sound cards by scanning I/O ports; instead, it checks only Config.sys and System.ini and performs detection as prescribed in Msdet.inf. Detection of sound cards by scanning I/O ports can cause the computer to stall. This is because detection calls a driver specific to a device class to send a signal to an I/O port. The driver expects a predetermined response, such as a signature from the adapter's ROM. If the wrong driver sends a signal to an I/O port address occupied by a different device class, the computer can stall.

Safe Recovery with Setup Log Files

Windows 98 Setup creates several log files: Bootlog.txt, Detlog.txt, Netlog.txt, and Setuplog.txt, as well as Detcrash.log, should Setup fail. The following sections describe these files.

Basically, the computer might stop or stall at three points during Windows 98 Setup: before, during, or after hardware detection.

  • If Setup fails before hardware detection, Windows 98 Setup recovers by reading Setuplog.txt to determine where the system stalled, what to redo, and what to skip. 

  • If Setup fails during hardware detection, the Detcrash.log file is created, containing information about the detection module that was running and the I/O port or memory resources it was accessing when the failure occurred.

    When the detection process finds this file, it automatically runs in Safe Recovery mode to verify all the devices already in the registry and then skips all detection modules up to the failed module. Safe Recovery then skips detection and any attempts to configure the failed module, in effect skipping the action that caused the failure. Then, Safe Recovery continues the detection process, starting with the next module. If the detection process is completed successfully, Detcrash.log is deleted. 

    Detcrash.log can be read only by Setup. For information about the text equivalent of this information, see "Detlog.txt: The Hardware Detection Log File" later in this chapter. 

  • Sometimes the detection process causes some devices (such as a CD-ROM drive or a network connection) to quit working. If you rerun Setup, Safe Recovery recognizes that the detection process has already been completed successfully and assumes that all the necessary hardware information is in the registry. Therefore, it skips the detection process completely at this point and continues the installation process. 

Setuplog.txt: The Setup Log File

The Setuplog.txt file is an ASCII text file that contains Windows 98 Setup information created during the installation process. While Windows 98 is being installed, corresponding entries are written to Setuplog.txt, listing information about the specific steps, their sequence, and the error conditions encountered. This file is used by Setup for recovery in case of setup failure, and it can also be used for troubleshooting errors that occur during the installation process.

Setup uses the information in Setuplog.txt to ensure that the installation does not fail twice because of the same problem. If you restart Windows 98 Setup after a setup process fails, Setup reviews the contents of Setuplog.txt to determine which steps completed successfully. If Setuplog.txt indicates that a process started but does not indicate that the process completed, that part of the installation process is skipped, and the next part is processed. Even if Setup encounters devices that cause several installation attempts, the installation process will always progress and skip the modules that failed.

Setuplog.txt is stored on the computer's root directory. Information is added to the file according to the order of the steps of the installation process. If an error occurs during installation, you can determine the probable cause of the error by examining the entries at the end of Setuplog.txt.

Information in Setuplog.txt is divided into the following basic categories:

  • Selected Setup sections, including [OptionalComponents], [System], [NameAndOrg], [Setup], [Network], [Started], [Dialogs], [Windows 98 CD-ROM], [Reinstall], and [batch_settings]. 

  • Setting up system startup parameters. 

  • Selecting the directory. 

  • Beginning the installation process. 

  • Queuing needed files in [FileQueue]. 

  • Copying needed files in [FileCopy]. 

  • Preparing to restart the system in [Restart]. 

Tip The [OptionalComponents], [System], and [NameAndOrg] sections can be copied from Setuplog.txt on a computer with a complete installation of Windows 98 and then added to equivalent sections in Msbatch.inf, as described in Chapter 3, "Custom Installations." Notice, however, that these sections in Setuplog.txt do not include networking information.

Table 5.1 shows entries in the Setuplog.txt file to check for information about the Setup process. Because entries are added to Setuplog.txt in the order that the related actions occur during Setup, you might be able to find a probable cause of any error by examining the entries at the end of the file.

Table 5.1 Summary of Setuplog.txt entries 

Setuplog.txt entry

Description

InstallType

Type of installation

InstallDir

Directory where Windows 98 is installed

detection

Detection status

RunningApp

Applications running during installation

RootFilesRenamed

Files renamed in the root directory

error

Errors logged during installation

failed

Failures that occurred during installation

[OptionalComponents]

Optional components installed

[System]

System hardware configuration

batch settings

Installation parameters (Msbatch.inf settings)

Registry

Registry initialization status

filename 

Verification that a specific file was loaded during Setup

[Choose Directory]

Location and type of Windows files

[FileCopy]

Files copied during Setup

[Restart]

Issues to be completed after the computer is restarted

Detlog.txt: The Hardware Detection Log File

The Detlog.txt file contains a record of whether a specific hardware device was detected and identifies the parameters for the detected device.

During Windows 98 Setup, after Setup restarts your computer for the first time, it begins hardware detection, which can also occur when you use the Add New Hardware option in Control Panel to add a new device. Both Windows 98 Setup and Device Manager use Sysdetmg.dll, which contains all the detection modules for each device class and specific devices.

Windows 98 loads detection modules based on information in Msdet.inf that points to specific INF files for each device class, from which information is retrieved and written to the registry. The device class installers are DLLs that work with Device Manager to install, configure, and remove devices or classes of devices in the system. Device Manager generates a list of compatible drivers for the device from the appropriate INF file. For information about using Device Manager to configure device drivers, and for information about the device classes used to identify logical device types, such as display, keyboard, and network adapters, see Chapter 24, "Device Management."

By creating an updated Detlog.txt file every time the detection process runs, the detection module tracks the detected devices and the I/O port addresses used. Any existing Detlog.txt is renamed Detlog.old. If the detection process causes Setup to stall or the computer to lock up, a binary file named Detcrash.log is created. Detlog.txt is an ASCII text file created only for users to read; Windows 98 Setup reads the binary information in Detcrash.log. Any changes made to Detlog.txt are not passed to Detcrash.log.

The Detlog.txt file can be found in the root directory of the startup drive after Windows 98 is installed. The entries in Detlog.txt are placed in the order of the hardware information discovered as each step of the detection process is carried out. Table 5.2 briefly describes entries that appear in Detlog.txt.

Table 5.2 Summary of Detlog.txt entries 

Detlog.txt Entry

Beginning of Detlog.txt:

Parameters="xxxxxx"

WinVer = ########

AvoidMem =
#####h-#####h

DetectClass: Skip Class Media

DetectClass Override:

Custom Mode:

Devices verified =

Detecting system devices:

Checking for:

Detecting network adapters:

Checking for:

Protocol.ini Section

NCD: detecting network adapter

The hardware detection process continues examining computer hardware. The "|" symbol in the IO= line (for example, IO=200-201 | 3e0-3e1) indicates a range of I/O entries that are checked during the detection process. In the Detlog.txt file, you will find a QueryIOMem: and an IO= line for each I/O address checked.

For most devices, multiple I/O addresses are checked, which can result in a detailed and redundant device detection list. The I/O address ranges checked during detection are grouped on one I/O line. Multiple addresses on an IO= line are separated by commas. For example:

Checking for: ATI Ultra Pro/Plus (Mach 32) Display Adapter 
QueryIOMem: Caller=DETECTMACH32, rcQuery=0 
IO=3b0-3bb,3c0-3df 
QueryIOMem: Caller=DETECTMACH32, rcQuery=0 
Mem=a0000-affff 

If the system stalls during hardware detection, you can determine the probable cause of the error by examining the last entries in Detlog.txt. You can use the information in this file to determine specific error conditions occurring in the hardware detection and reconfigure or replace the specific adapter or device. Table 5.3 shows specific kinds of entries to check in Detlog.txt for information about the results of the hardware detection process.

Table 5.3 Detlog.txt entries to check for troubleshooting 

Detlog.txt Entry

Description

detected

Detected devices

AvoidMem

Address ranges of UMBs avoided during detection

error

Errors logged during system detection

WinFlags

Setup mode used

Protocol.ini

Protocol.ini information that was saved during system upgrade

CustomMode

Hardware that was removed from detection in the custom Analyzing Your Computer dialog box

Devices verified

Devices found in the registry (if the value is 0, there was no existing registry, or the registry was empty)

Some additional notes on Detlog.txt and hardware detection:

  • Detection does not detect enumerated devices such as Industry Standard Architecture (ISA) Plug and Play devices, peripheral component interconnect (PCI) devices, and Personal Computer Memory Card International Association (PCMCIA) devices. For information about these devices, see Chapter 14, "Introduction to Networking Configuration." 

  • If the computer stalls during detection, and you rerun Windows 98 Setup and choose Safe Recovery, new detection information is appended to the previous Detlog.txt file. The previous version of Detlog.txt is saved as Detlog.old, overwriting any previous Detlog.old files. 

The hardware that has been tested and shown to be compatible with Windows 98 appears in the Manufacturers and Models lists in the Add New Hardware option in Control Panel.

Netlog.txt: The Network Setup Log File

Netlog.txt describes the detection results for network components during Windows 98 Setup. For information about Netdet.ini, the file that Setup uses to determine how to install networking components on computers running NetWare clients, see Chapter 17, "Windows 98 on Third-Party Networks."

Table 5.4 describes typical entries in a Netlog.txt file after you run Windows 98 Setup the first time. In this example, Client for Microsoft Networks is installed with the Internet Packet Exchange/Sequenced Packet Exchange (IPX/SPX)-compatible protocol, and both are bound to an Intel EtherExpress network adapter.

Table 5.4 Summary of Netlog.txt entries 

Netlog.txt entry

Description

ClassInstall (0x6) on Intel EtherExpress 16 or 16TP at Enum\Root\*PNP812D\0000

Network installation begins.

Examining class NET

Network detection is searching for network software of four class types: NET (network adapters), NETTRANS (protocols), NETCLIENT (clients), and NETSERVICES (such services as file and printer sharing).

Upgrade 2.00025000=VREDIR

A network client was found on the computer.

Upgrade to: VREDIR

The version of the network client was upgraded to the version included in Windows 98.

NdiCreate (Client for Microsoft Networks) OK

Setup successfully created an internal object representing the network client.

NdiCreate (Intel EtherExpress 16 or 16TP)

Setup successfully created an internal object representing the network adapter.

CreateNetwork, Batch=0

Setup referenced a batch file.

NdiCreate (IPX/SPX-compatible Protocol)

Setup successfully created an internal object representing the IPX/SPX-compatible protocol.

ClassInstall (0x6) end

 

ClassInstall (0x9) on Intel EtherExpress 16 or 16TP at Enum\Root\*PNP812D\0000

Protocols are about to be bound to the network adapter.

Validating IPX/SPX-compatible Protocol at Enum\Network\NWLINK
\0000, rc=0x0

The IPX/SPX-compatible protocol is added to the registry and bound to the network adapter.

ClassInstall (0x9) on Intel EtherExpress 16 or 16TP at Enum\Root\*PNP812D\0000

Clients are about to be bound to the network adapter.

Validating Client for Microsoft Networks at Enum\Network\VREDIR
\0000, rc=0x0

Client for Microsoft Networks is added to the registry and bound to the network adapter.

ClassInstall (0x9) end

Setup has finished binding the protocol to the network adapter.

ClassInstall (0xa) on Intel EtherExpress 16 or 16TP at Enum\Root\*PNP812D\0000

The network setup process is concluded.

ClassInstall (0xa) end

 

ClassInstall (0xc) on Intel EtherExpress 16 or 16TP at Enum\Root\*PNP812D\0000

 

ClassInstall (0xc) end

 

Windows 98 Startup Process

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

Windows 98 includes system files, Plug and Play mechanisms, and various options for starting the operating system. This section describes the Windows 98 system startup sequence.

During the real-mode startup process, devices use only static configurations; that is, no dynamic resource allocation or arbitration is provided. When the system startup process switches to protected mode, Configuration Manager ensures all devices are configured properly, as described in Chapter 28, "Windows 98 Architecture."

The system startup includes four phases:

  • Bootstrapping the system with basic input/output system (BIOS) in control. 

  • Loading MS-DOS drivers and terminate-and-stay-resident (TSR) Programs for compatibility. 

  • Initializing static VxDs in real mode. 

  • Putting the protected-mode operating system in control and loading the remaining VxDs. 

Bootstrapping in the BIOS Phase

Microsoft worked with several hardware manufacturers to define a new Plug and Play BIOS specification, which defines the interactions among a Plug and Play BIOS, Plug and Play devices, and option ROMs (sometimes called adapter ROMs). The Plug and Play BIOS enables and configures Plug and Play boot devices. The Plug and Play BIOS also passes configuration information to Configuration Manager in Windows 98 for configuring the remaining adapters and devices.

Booting with a Legacy BIOS

For legacy computers that do not have Plug and Play BIOS, the BIOS enables all devices on the ISA bus. A Plug and Play ISA card that has an option ROM must start up when the computer is turned on with the option ROM enabled.

Booting with a Plug and Play BIOS

A Plug and Play BIOS accesses nonvolatile random access memory (RAM) to determine which Plug and Play ISA cards should be enabled, where their option ROMs should be mapped, and what I/O, DMA, and other assignments are to be given to the cards.

The BIOS then programs the Plug and Play cards before the power-on self-test (POST). All cards that do not have configurations stored in the BIOS are disabled completely, reducing the chance of a conflict.

The Plug and Play BIOS also configures all devices on the motherboard. Some devices might have been disabled or assigned to different I/O addresses, IRQ settings, and so on, by Configuration Manager.

Loading Hardware Profiles and Real-mode Drivers

After BIOS initialization, the operating system attempts to determine the current configuration, including whether the computer is a docking station. This is done by using a hardware profile that Windows 98 selects before Config.sys is processed. The hardware profile is built by a detection process that collects information about interrupt usage, BIOS serial and parallel ports, BIOS computer identification, Plug and Play BIOS docking station data, and, if possible, docking station data that is unique to each original equipment manufacturer (OEM). Then the detection process builds a 2-byte value known as the current hardware profile (or the current configuration).

Each hardware profile has a name that matches a top-level menu item in a multiconfigured Config.sys file (that is, the long text in the menu, not the section name enclosed in square brackets). Windows 98 automatically selects that multiconfiguration menu item and processes the corresponding section of Config.sys.

Config.sys and Autoexec.bat are processed at this point. Although these files are not required for Windows 98, they are used for backward compatibility with applications created for MS-DOS or Windows 3.1x. In Windows 98, Config.sys and Autoexec.bat are processed much as they are processed under MS-DOS 6*.x*. Drivers and TSRs specified in these files are loaded in real mode.

For more information, see "System Startup Files" later in this chapter.

Note The real-mode MS-DOS errors are standard, as documented in the MS-DOS 6.0 Programmer's Reference. 

Initializing Static VxDs at Startup

Windows 98 supports static VxDs that load during system startup in the same way as Windows 3*.x* VxDs, and it also supports dynamically loaded VxDs. Vmm32.vxd includes the real-mode loader, the executable Virtual Machine Manager, and common static VxDs. Notice, however, that if a VxD file is in the \Windows\System\Vmm32 directory, Windows 98 loads it in addition to the combined VxDs in Vmm32.vxd.

Note If you want to update a VxD that has been bound into the monolithic Vmm32.vxd, place the VxD file in the System\Vmm32 directory. Windows 98 always checks that directory and uses any individual VxDs it finds instead of loading those bound in Vmm32.vxd.

The following list shows the VxDs typically combined to create Vmm32.vxd. (A custom list is built for each computer.) These drivers used to be specified in the [386enh] section of System.ini.

*biosxlat
*configmg
*dynapage
*ebios
*enable
*ifsmgr
*int13

*ios
*parity
*reboot
*vcache
*vcd
*vcomm
*vcond

*vdd
*vdef
*vfat
*vfbackup
*vflatd
*vkd
*vmcpd

*vmouse
*vmpoll
*vpd
*vsd
*vtdapi
*vwin32
*vxdldr

VMM32 loads VxDs in three steps:

  • VMM32 loads base drivers specified in the registry, which contains entries for every VxD not directly associated with any hardware. VxDs are located in the following branch of the registry: 

    Hkey_Local_Machine \System \CurrentControlSet \Services \VxD

  • If VMM32 finds a value StaticVxD= in any registry key, it loads that VxD and runs its real-mode initialization. For example, the following entry loads *V86MMGR: 

SYSTEM\CurrentControlSet\Services\VxD\V86MemoryManger Description=MS-DOS Virtual 8086 Memory Manager Manufacturer=Microsoft StaticVxD=*V86MMGR EMMEXCLUDE=E000-EFFF

  • VMM32 loads the static VxDs specified in the device=*VxD lines in the [386enh] section of System.ini. These VxDs are actually loaded from VMM32, and appear in System.ini only for backward compatibility. 

If a specific device conflicts with a device loaded from the registry, the device specified in System.ini takes precedence. However, if the device specified in System.ini cannot be found, an error occurs.

Many Windows 98 driver models, such as integrated office system (IOS) (for disk drivers) and the network, support dynamically loaded device drivers. These VxDs are not loaded by the VMM32 real-mode loader, but are loaded by a device loader that is responsible for loading and initializing the drivers at the correct time and in the correct order.

For example, for SCSI adapter miniport drivers, the device loader is *Ios. The entries for a SCSI adapter are found in the following registry key:

Hkey_Local_Machine \System \CurrentControlSet \Services \Class 

Because there is no **StaticVxD=**xxx line in this registry entry, the VMM32 real-mode loader does nothing when Windows 98 identifies this device.

Configuration Manager attempts to find any device node that has a DevLoader= entry in the registry. The device loader (in the previous example, *Ios) examines the registry, finds the PortDriver= entry, loads the driver and any associated support drivers, and initializes the adapter.

Loading the Protected-Mode Operating System at Startup

In the previous phase, the following elements of the operating system were loaded:

  • Win.com, which controls the initial checks and loading of the core Windows 98 components. 

  • Vmm32.vxd, which creates virtual machines and initiates VxD loading. 

  • System.ini, which is read for entries that differ from registry entries. 

After all static VxDs have been loaded, Vmm32.vxd switches the processor to operate in protected mode, and the last phase of the boot process begins. This phase involves loading the protected-mode components of the operating system.

Loading Protected-Mode VxDs at Startup

The protected-mode Configuration Manager is initialized for importing configuration information from a Plug and Play BIOS (if available); otherwise, it develops the Plug and Play hardware tree by enumerating devices and loading dynamically loadable device drivers. These device drivers are identified by loading drivers from a specific directory.

The next phase resolves device resource conflicts for every device in the tree and then informs the devices of their configuration. When all devices have been enumerated, all conflicts have been resolved, and all devices have been initialized, Windows 98 is ready to be used.

Loading the Final System Components at Startup

The remaining Windows 98 system components are loaded in the following sequence:

  • Kernel32.dll provides the main Windows components, and Krnl386.exe loads the Windows device drivers. 

  • Gdi.exe and Gdi32.exe provide the graphical device interface code. 

  • User.exe and User32.exe provide the user interface code. 

  • Associated resources, such as fonts, are loaded. 

  • Win.ini values are checked. 

  • The shell and desktop components are loaded. 

At this point, a prompt appears so that you can log on by typing a user name and a password. After you log on, Windows 98 can process user-specific configuration information. If you do not log on, default settings are used. If Windows 98 is configured for network logon, the unified Windows 98 logon can be used to log on to the network during this process.

After Windows 98 is loaded and you log on, the Startup directory is processed.

System Startup Files

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

This section describes the following files involved in Windows 98 system startup:

  • Io.sys, the real-mode operating system that replaces the MS-DOS version; VMM32 and Windows 98 device drivers take control from Io.sys. 

  • Msdos.sys, which contains special information for Windows 98, is also created. This gives compatibility with applications that require Msdos.sys to be present before they can be installed. 

  • Config.sys and Autoexec.bat. 

  • System.ini and Win.ini. 

  • Bootlog.txt, the log file that describes the system startup processes. 

Table 5.5 summarizes how Setup renames the system files from the previous operating system when Windows 98 is installed. (The Windows 98 files are renamed with .W40 file name extensions when you start the computer with the other operating system.)

Table 5.5 Setup system file naming 

Original MS-DOS file name

Renamed file under Windows 98

Autoexec.bat

Autoexec.dos

Command.com

Command.dos

Config.sys

Config.dos

Io.sys (or Ibmbio.com)

Io.dos

Mode.com

Mode_dos.com

Msdos.sys (or Ibmdos.com)

Msdos.dos

Io.sys: The Real-mode Operating System

In Windows 98, the Io.sys system file replaces the MS-DOS system files Io.sys and Msdos.sys. This real-mode operating system file contains the information needed to start the computer. Your computer no longer needs Config.sys and Autoexec.bat to start the Windows 98 operating system (although these files are preserved for backward compatibility with certain applications and drivers).

Note The Windows 98 Io.sys file is automatically renamed to Winboot.sys if you start the computer using your previous operating system.

The drivers loaded by default in Io.sys include the following files, if they are found on the hard disk:

  • Himem.sys

  • Ifshlp.sys

  • Setver.exe 

  • Dblspace.bin or Drvspace.bin if Dlbspace.ini or Drvspace.ini exists in the root of the boot drive. 

Most of the common functionality provided by the various Config.sys file entries in older operating systems is provided in Io.sys. Table 5.6 lists the common entries from Config.sys that are incorporated into Io.sys for Windows 98.

Table 5.6 Config.sys settings incorporated into Windows 98 Io.sys 

Entry

Description

dos=high

Specifies that MS-DOS should be loaded in the high-memory area (HMA). Also, the umb value is included if EMM386 is loaded from Config.sys. (Io.sys does not load EMM386.)

himem.sys

Enables access to the HMA. This line loads and runs the real-mode Memory Manager. Himem.sys is loaded by default in Windows 98.

ifshlp.sys

The 32-bit Installable File System Manager uses the services provided by this driver to assist in trapping real-mode file system and network-related APIs.

setver.exe

Optional TSR-type device. It is included for compatibility. Some MS-DOS-based applications require a specific version of MS-DOS to be running. This file responds to applications that query for the version number and sets the version number required.

files=

Specifies the number of file handle buffers to create. This is specifically for files opened using MS-DOS calls and is not required by Windows 98. It is included for compatibility with older applications. The default value is 60.

lastdrive=

Specifies the last drive letter available for assignment. This is not required for Windows 98 but is included for compatibility with older applications. If Windows 98 Setup finds this entry, it is moved to the registry. The default value is z.

buffers=

Specifies the number of file buffers to create. This is specifically for applications using Io.sys calls and is not required by Windows 98. The default value is 30.

stacks=

Specifies the number and size of stack frames. This is not required for Windows 98 but is included for compatibility with older applications. The default value is 9,256.

shell=Command.com

Indicates what command process to use. By default, the /p switch is included to indicate that the command process is permanent and should not be unloaded. If the /p switch is not specified, Autoexec.bat is not processed and the command process can be unloaded when quitting the operating system.

fcbs=

Specifies the number of file control blocks that can be open at the same time. You should use a fcbs= line in Config.sys only if you have an older program that requires such a setting. The default value is 4.

To override default values in Windows 98 Io.sys
  • Place an entry in Config.sys with the value you want. 

The values in Io.sys cannot be edited. If Config.sys contains switches or other parameters for any of the drivers or settings created by Io.sys, the Config.sys entries override the Io.sys defaults. Entries for files=, buffers=, and stacks= must be set in Config.sys to at least the default values in Io.sys.

Note Io.sys does not load Emm386.exe. If any of your applications requires expanded memory or loads data into the high memory area, EMM386 must be loaded in Config.sys.

Msdos.sys: Special Startup Values

Windows 98 Setup creates a hidden, read-only system file named Msdos.sys in the root of the computer's boot drive. This file contains important paths used to locate other Windows files, including the registry. Msdos.sys also supports an [Options] section, which you can add to tailor the startup process.

The following example shows a typical file with default values:

[Options] 
BootGUI=1 
[Paths] 
WinDir=C:\WINDOWS 
WinBootDir=C:\WINDOWS 
HostWinBootDrv=C 

Most values in the [Options] section are Boolean — that is, the value can be 1 (enabled) or 0 (disabled). Table 5.7 describes entries in Msdos.sys, using the typical default values.

Table 5.7 Msdos.sys entries

Entry

Description

[Paths] section

 

HostWinBootDrv=c

Defines the location of the boot drive root directory.

WinBootDir=

Defines the location of the necessary startup files. The default is the directory specified during Setup; for example, C:\Windows.

WinDir=

Defines the location of the Windows 98Windows 98 directory as specified during Setup.

[Options] section

 

AutoScan=

Enables ScanDisk to run automatically when your computer restarts. The default is 1. When this value is set to 1, ScanDisk will run automatically., you will be prompted if you want to run ScanDisk; if you do not respond after one minute, ScanDisk runs automatically. Setting this value to 0 disables this feature. Setting it to 2 launches ScanDisk automatically (if needed), without prompting you.

BootDelay=n

Sets the initial startup delay to n seconds. The default is 0is 2. BootKeys=0 disables the delay. The only purpose of the delay is to give the user sufficient time to press F8press ctrl after the Starting Windows message appears.

BootFailSafe=

Enables Safe Mode for system startup. The default is 0. (tThis setting is typically enabled typically by equipment manufacturers for installation.).

BootGUI=

Enables automatic graphical startup into Windows 98Windows 98. This is equivalent to putting the win statement in Autoexec.bat. The default is 1.

BootKeys=

Enables the startup option keys (that is, F5, F6, and F8). The default is 1. Setting this value to 0 overrides the value of BootDelay=n and prevents any startup keys from functioning. This setting allows system administrators to configure more secure systems. (These startup keys are described in Chapter 27, "General Troubleshooting.").

BootMenu=

Enables automatic display of the Windows 98Windows 98 Startup menu, so that the user must press CTRL to see the menu. The default is 0. Setting this value to 1 eliminates the need to press CTRL to see the menu.

BootMenuDefault=#

Sets the default menu item on the Windows Startup menu; the default is 3 for a computer with no networking components and 4 for a networked computer.

BootMenuDelay=#

Sets the number of seconds to display the Windows Startup menu before running the default menu item. The default is 30.

BootMulti=

Enables dual-boot capabilities. The default is 0. Setting this value to 1 enables the ability to start MS-DOS by pressing F4 or by pressing F8 to use the Windows Startup menu.

BootWarn=

Enables the Safe Mode startup warning. The default is 1.

BootWin=

Enables Windows 98Windows 98 as the default operating system. Setting this value to 0 disables Windows 98Windows 98 as the default; this is useful only with MS-DOS version 5 or 6.x on the computer. The default is 1.

DblSpace=

Enables automatic loading of Dblspace.bin. The default is 1.

DoubleBuffer=

Enables loading of a double-buffering driver for a SCSI controller. The default is 0. Setting this value to 1 enables double-bufferingdouble buffering, if required by the SCSI controller.

DrvSpace=

Enables automatic loading of Drvspace.bin. The default is 1.

LoadTop=

Enables loading of Command.com or Drvspace.bin at the top of 640K memory. The default is 1. Set this value to 0 with Novell NetWare or any software that makes assumptions about what is used in specific memory areas.

Logo=

Enables display of the animated logo. The default is 1. Setting this value to 0 also avoids hooking a variety of interrupts that can create incompatibilities with certain memory managers from other vendors.

Network=

Safe Mode With Networking is no longer supported in Windows 98Windows 98. This value should be set to 0 or left blank to disable this feature.

Tip for Starting an Earlier Version of MS-DOS

If you installed Windows 98 in its own directory, the earlier version of MS-DOS is preserved on your hard disk. If you set BootMulti=1 in the [Options] section in the Windows 98 version of Msdos.sys, you can start the earlier version of MS-DOS by pressing F4 when the Starting Windows message appears during system startup.

Config.sys and Autoexec.bat

For Windows 95 and Windows 98, the content and method for handling Config.sys and Autoexec.bat during system startup have changed. Windows 98 automatically loads drivers and sets defaults by using Io.sys, the registry, and other mechanisms, rather than Config.sys and Autoexec.bat.

Computers that require certain real-mode drivers or TSRs, however, will continue to require that software be loaded from these configuration files. Also, Config.sys and Autoexec.bat might be required to enable certain software options. Some options, such as long command lines, can also be enabled by using the Command.com program properties, as shown in the following illustration.

Cc768175.wrk0k05(en-us,TechNet.10).gif 

Config.sys Processing

Config.sys defaults are implemented by Io.sys, as described in the previous section. However, Config.sys can contain application-specific entries in addition to information stored in Io.sys. These are processed in the sequence they are listed. After the base Config.sys file has been read, all devices are loaded, and Command.com is started.

Windows 98 loads memory managers supplied by other vendors if they are present in Config.sys; however, some might cause errors. Similarly, Windows 98 allows the use of command shells from other vendors, but there are some differences. For example, long file names are disabled, which might also indicate that other problems could occur using these command shells.

Config.sys Changes for Windows 98

Windows 98 has predefined settings built in for most common Config.sys settings, so Windows 98 Setup removes many of these lines (such as settings for files, buffers, and stacks) if they are equivalent to the default values, by using rem to comment out the line.

Tips for Editing Config.sys in Windows 98

If you edit Config.sys in Windows 98, observe the following basic guidelines:

  • Do not include the smartdrv command. Windows 98 includes built-in disk caching, and double-buffering is now provided by Dblbuff.sys. 

  • Remove any device=mouse.sys lines or similar lines. Windows 98 includes built-in mouse support. 

Autoexec.bat Processing

Autoexec.bat is not required for Windows 95 or Windows 98, but it is included for compatibility purposes. If the computer has an Autoexec.bat file, each line is processed in sequence during system startup. Autoexec.bat can contain additional application-specific entries that are run in the sequence they are listed.

Windows 98 passes the initial environment to Command.com with the correct Windows and Windows Command directories already in the path and with the environment variables PROMPT, TMP, and TEMP already set. (TEMP= and TMP= indicate locations for temporary directories; both are specified for compatibility reasons.)

Table 5.8 describes the Autoexec.bat commands that have equivalent default settings created in Io.sys for Windows 98.

Table 5.8 Autoexec.bat equivalents for Windows 98 Io.sys default settings 

Command

Meaning

net start 

Loads the real-mode network components and validates the binding. Any errors received are placed in the Ndislog.txt file. (SYSINIT or Command.com performs the necessary net start command.)

set path 

Sets the path as specified.

The default Windows 98 environment includes the following:

tmp=c:\windows\temp 
temp=c:\windows\temp 
prompt=$p$g 
path=c:\windows;c:\windows\command 
comspec=c:\windows\command\Command.com 
Autoexec.bat Changes for Windows 98

Windows 98 Setup makes the following basic changes to Autoexec.bat:

  • Updates the path= line statement. 

  • Uses rem to comment out incompatible TSRs. 

  • Deletes any win statement (or equivalent) and Share.exe. 

  • Copies the original Autoexec.bat to Autoexec.dos. 

  • Sets the Temp directory. 

Tips for Editing Autoexec.bat in Windows 98

If you edit Autoexec.bat in Windows 98, observe the following basic guidelines:

  • Do not include other versions of Windows in your path. 

  • Start the path with C:\Windows;C:\Windows\Command (using the name for the Windows 98 directory on your hard disk if it is not \Windows). 

  • Windows 98 Setup leaves your previous MS-DOS directory in the path. Do not change this. 

  • Do not add SMARTDrive or other disk caches. Windows 98 includes built-in caching. 

  • Do not include any statements for loading mouse support software. Windows 98 includes built-in mouse support. 

  • If it is necessary to connect to a network server when you start Windows 98, create a batch file, and run it from the STARTUP directory, rather than placing an entry in Autoexec.bat. 

System.ini and Win.ini

This section describes changes related to system startup made by Windows 98 Setup to System.ini and Win.ini. Mappings for other changes between Windows 3.1x and Windows 98 are described in Chapter 31, "Windows 98 Registry."

System.ini Changes for Windows 98

Table 5.9 lists configuration options that have been added to System.ini, deleted, or moved to the registry. Most of these options for Windows 98 are now stored in the registry and are no longer required in System.ini.

Table 5.9 Changes made to System.ini entries in Windows 98 

Change

Affected entries

Affected entries

Added to the [Boot] section

comm.drv=comm.drv
dibeng.drv=dibeng.dll
gdi.exe=gdi.exe

sound.drv=sound.drv
user.exe=user.exe

Added to the [386Enh] section

device=*int13
device=*dynapage

device=*vshare
device=*vcd

Deleted in the [386Enh] section

device=*configmg
device=*vfd
device=isapnp.386
device=lpt.386
device=pagefile.386

device=serial.386
device=wshell.386
maxbps=
timercriticalsection=

Moved from the [386Enh] section to the registry

Network=
Network3=
SecondNet=

Transport=
V86ModeLANAs=

Moved from the [Network] section to the registry

AuditEnabled=
AuditEvents=
AuditLogSize=
AutoLogon=
Comment=
ComputerName=
DirectHost=
EnableSharing=
FileSharing=
LANAs=
LMAnnounce=

LMLogon=
LogonDisconnected=
LogonDomain=
LogonValidated=
Multinet=
PasswordCaching=
PrintSharing=
Reshare=
SlowLanas=
Winnet=
Workgroup=

Moved from the [Network drivers] section to the registry

All parameters

 

Moved from the [nwnblink] section to the registry

lanabase=

 

Set the related parameters using Windows 98 tools as follows:

  • Set all memory-related parameters by using the System option in Control Panel. For information, see Chapter 26, "Performance Tuning." 

  • Set parameters for hardware devices by using Device Manager in the System option in Control Panel. For information, see Chapter 24, "Device Management." 

Win.ini Changes for Windows 98

Table 5.10 shows how the font and desktop information in Win.ini is transferred to the registry in Windows 98.

Table 5.10 Changes made to Win.ini entries in Windows 98 

Change

Affected entries

Affected entries

Moved from the [Windows] section to the registry

Beep
BorderWidth
CursorBlinkRate
DoubleClickSpeed
KeyboardDelay
KeyboardSpeed

MouseThreshold1
MouseThreshold2
MouseSpeed
ScreenSaveActive
ScreenSaveTimeOut
SwapMouseButtons

Moved from the [Windows Metrics] section to the registry

BorderWidth
CaptionHeight
CaptionWidth
MenuHeight
MenuWidth
MinArrange
MinHorzGap

MinVertGap
MinWidth
ScrollHeight
ScrollWidth
SmCaptionHeight
SmCaptionWidth

In addition, Setup always adds ATMWorkaround=1 to the [Pscript.Drv] section in Win.ini.

Set the related parameters using Windows 98 tools as follows:

  • Set all mouse parameters by using the Mouse option in Control Panel. For information, see Chapter 24, "Device Management." 

  • Set parameters for the keyboard by using the Keyboard option in Control Panel. For information, see Help. 

  • Set all screen and window display parameters by using the Display option in Control Panel. For information, see Chapter 24, "Device Management." 

Bootlog.txt: The Startup Process Log

The Bootlog.txt file contains a record of the current startup process for starting Windows 98. This file is created during Setup when the Windows 98 operating system is first started from Windows 98 Setup. This file shows the Windows 98 components and drivers loaded and initialized, and the status of each.

When you use the F8 option for interactive system startup, you can choose to create a boot log during system startup. You can also use the /b switch to create a boot log when running Win.com from the command line to isolate configuration problems. For information, see Chapter 27, "General Troubleshooting."

The information in Bootlog.txt is written in sequence during startup, in roughly five major sections. Depending upon a specific error condition, you might need to examine multiple sections. Notice, however, that a loadfailed= entry means only that the related VxD refused to load. For example, loadfailed=ebios indicates that the EBIOS driver did not detect EBIOS in the computer and so reported that it should not be loaded. Table 5.11 shows the sections to examine and describes the possible errors and methods for correcting those errors.

Table 5.11 Bootlog.txt sections for determining errors 

Section and errors

Loading real-mode drivers:

No extended memory specification (XMS) memory

Incorrect MS-DOS version (message appears when driver loads)

Windows 98 does not start on a SCSI hard drive

Ifshlp.sys message occurs

Loading VxDs:

 

Cannot access D??SPACE drives

Sharing violations occur

System-critical initialization of VxDs:

System-critical initialization error occurs

Device initialization of VxDs:

 

Successful VxD initialization:

 

Table 5.12 shows the kinds of entries in Bootlog.txt to examine for information about the system startup process.

Table 5.12 Bootlog.txt entries to examine for system startup 

Bootlog.txt entry

Description

Error

Errors that were logged during startup

Fail

Failures that occurred during startup

Dynamic load success

Dynamically loaded VxDs

INITCOMPLETESUCCESS

Loaded VxDs

LoadStart, LoadSuccess,
Loading Device, Loading Vxd

Indication of loading processes

LoadFailed

Indication that component failed to load

SYSCRITINIT, SYSCRITINITSUCCESS

System initialization actions

DEVICEINIT, DEVICEINITSUCCESS

Device initialization actions

Dynamic load device, Dynamic init device

Dynamic loading and initialization of devices

Initing, Init Success, INITCOMPLETE, Init, InitDone

Initialization actions

Status

Current status indicator

For example, if you see an entry such as DynamicInitDevice=PPPMAC but there is no matching entry such as DynamicInitSuccess=PPPMAC, that VxD failed to load. If a driver in the Windows System\Iosubsys directory stalls when it is being initialized, you can sometimes successfully start the system by renaming that file.

The following shows a sample Bootlog.txt file:

Loading Device = C:\WINDOWS\HIMEM.SYS 
LoadSuccess = C:\WINDOWS\HIMEM.SYS 
Loading Device = C:\WINDOWS\EMM386.EXE 
LoadSuccess = C:\WINDOWS\EMM386.EXE 
Loading Device = C:\WINDOWS\SETVER.EXE 
LoadSuccess = C:\WINDOWS\SETVER.EXE 
Loading Device = C:\WINDOWS\COMMAND\ANSI.SYS 
LoadSuccess = C:\WINDOWS\COMMAND\ANSI.SYS 
Loading Device = C:\WINDOWS\IFSHLP.SYS 
LoadSuccess = C:\WINDOWS\IFSHLP.SYS 
Loading Vxd = VMM 
LoadSuccess = VMM 
Loading Vxd = nwlink.vxd 
LoadSuccess = nwlink.vxd 
Loading Vxd = vnetsup.vxd 
LoadSuccess = vnetsup.vxd

Windows 98 Setup with Other Operating Systems

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

This section presents details related to installing Windows 98 over an existing operating system, including changes made to system files by Windows 98 Setup and configuring for dual-booting with the previous operating system.

Microsoft Windows 98 dual-boot is supported with Microsoft Windows NT, Windows 95 and MS DOS 5.x. Dual-boot with third-party operating systems, such as Novell DR DOS and IBM OS/2, is not supported. For more information on dual booting Windows 98 with a third-party operating system, you should contact your operating system vendor.

Table 5.13 summarizes some of the available options for upgrading with Windows 3.1x, MS-DOS, and Windows NT, and how you should install Windows 98 to take advantage of these options.

Table 5.13 Upgrade versus clean installations 

Desired configuration

Install Windows 98 in a new directory

Upgrade existing Windows 3.1x/95 installation with Windows 98

Migrate existing Windows application settings and files

 

 

Cc768175.check(en-us,TechNet.10).gif

Dual boot Windows 98 and MS-DOS

 

Cc768175.check(en-us,TechNet.10).gif

 

Dual boot Windows 98 and Windows NT1

 

Cc768175.check(en-us,TechNet.10).gif

 

1 Windows 98 and Windows NT can work together properly if the computer is configured for dual booting between MS-DOS and Windows NT. However, you must install Windows 98 in a new directory.

The topics discussed in this section include the following:

  • Upgrading Windows 95 to Windows 98 keeping your current configuration settings 

  • Upgrading Windows 95 to Windows 98 changing your current configuration settings 

  • Upgrading Windows 3.1x 

  • Dual booting Windows 98 with Windows 3.1x and MS-DOS 

  • Dual booting Windows 98 with Windows NT 

Upgrading from Windows 95 to Windows 98

There are two methods for upgrading from Windows 95 to Windows 98. The method you choose depends on whether you want to retain the existing configuration settings (such as computer name, installation directory, and network settings) on your computer.

Keeping Current Configuration Settings

If you have a computer running Windows 95 and you want to upgrade it to Windows 98, keeping its current configuration settings (such as computer name, user name, and installation directory), run the Windows 98 Setup program from within Windows 95. This is the recommended method for upgrading Windows 95 to Windows 98, because it requires minimum user interaction and is the easiest method.

With this method, Windows 98 is installed in the same directory where Windows 95 was installed. Furthermore, Windows 98 Setup uses the existing configuration information to set installation defaults and to set other configuration options. Windows 98 Setup migrates all Windows 95 folders and programs to Windows 98, so they appear on the Windows 98 Start menu. Windows 98 automatically migrates all the shortcuts you had under Windows 95.

To upgrade Windows 95 to Windows 98 keeping current settings
  1. Start Windows 95. 

  2. Close all programs, including any anti-virus programs. 

    For information about closing an anti-virus program, see the program documentation and Setup.txt on your Windows 98 disk. 

  3. If you are installing Windows 98 from a compact disc, insert the Windows 98 compact disc into your CD-ROM drive. 

    – Or – 

    If you are installing Windows 98 from floppy disks, insert Setup Disk 1 into the floppy disk drive. 

    – Or – 

    If you are installing Windows 98 from source files on a network server, connect to that server and switch to the shared network directory that contains the Windows 98 source files. 

  4. On the Start menu, click Run

    The Run dialog box appears. 

  5. In the Open box, enter the location of the Windows 98 disc. For example, type the drive letter, followed by a colon (:), a backslash (\), and the word setup. For example: d:\setup

  6. Click OK

    The Windows 98 Setup Wizard starts. 

  7. Follow the on-screen instructions, as described in "Running Setup from the Windows 95 Interface" in Chapter 2, "Setting Up Windows 98." 

Changing Current Configuration Settings

If you want to upgrade your Windows 95 computer to Windows 98 but you want to change its current configuration settings (such as computer name and workgroup) or you want to install Windows 98 in a new directory, you run the Windows 98 Setup program from within MS-DOS.

Before you begin, you should be prepared to provide the following information:

  • Name of the installation directory (for example, c:\Win98). 

    If you do not know the directory in which to install Windows 98, you can use Setup to create a new one. When prompted, type a new directory name. 

  • Network information, such as your computer name, workgroup, and computer description (if your computer is on a network). 

When starting Setup from MS-DOS using either a network server or local CD-ROM drive, the real-mode network or CD-ROM drivers must be loaded. If the real-mode network drivers are running when you start Windows 98 Setup, the appropriate network client is installed automatically. Setup detects existing network components, installs the appropriate supporting software automatically, and adds the necessary network settings in the registry.

To upgrade Windows 95 to Windows 98 changing current settings
  1. Start your computer up and press F8 when the message, Starting Windows 95 appears. Then select Command Prompt Only. 

    -Or- 

    From Windows 95, click on Start, and click Shut Down. Then select Restart in MS-DOS mode

  2. If you are installing Windows 98 from a compact disc, insert the Windows 98 compact disc into the CD-ROM drive, and make it the active drive. 

    – Or – 

    If you are installing Windows 98 from floppy disks, insert Setup Disk 1 into the floppy disk drive and make it the active drive. For example, type a: if the disk is in the A drive. 

    – Or – 

    If you are installing Windows 98 from source files on a network server, connect to that server and switch to the shared network directory that contains the Windows 98 source files. 

  3. At the command prompt, type the drive letter, followed by a colon (:), a backslash (\), and the word setup. For example: 

    d:\setup 

  4. Press ENTER. 

    Setup quickly scans your computer, and then the Windows 98 Setup Wizard starts. 

  5. Follow the on-screen instructions, as described in "Running Setup from MS-DOS" in Chapter 2, "Setting Up Windows 98." 

After starting Setup from MS-DOS, Setup initializes and checks your system:

  • It runs real-mode ScanDisk to check the hard disk for errors. Unlike the protected-mode version of ScanDisk, the real-mode counterpart cannot fix errors in long file names. ScanDisk does not perform a surface scan; therefore, the disk is not checked for physical errors. 

    Note If you get file system errors during setup, you should run ScanDisk and perform a surface scan before running Setup again. 

  • It initializes the registry and checks it for corruption.

Tip When you run Windows 98 Setup, ScanDisk performs a quick check of the hard disk. You can skip this quick check (for example, if the computer uses disk compression software from another vendor) by using the /iq or /is switch with the setup command, as described in "Using the Setup Command-Line Switches" in Chapter 2, "Setting Up Windows 98." If you choose to skip automatically running ScanDisk, be sure to use another utility to check the integrity of the hard disk before running Setup.

Upgrading Windows 3.1x or Windows for Workgroups to Windows 98

If you have a computer running Windows 3.1x or Windows for Workgroups, you can upgrade it to Windows 98 by running the Windows 98 Setup program from within Windows 3.1x or Windows for Workgroups.

Most of the information needed for upgrading is automatically taken from your current installation of Windows 3.1x. Setup automatically identifies and transfers your current system settings and installed programs. Windows 98 Setup also saves settings so that you can continue to use the network configuration that you had previously.

To upgrade from Windows 3.1x or Windows for Workgroups to Windows 98
  1. Start Windows 3.1 or Windows for Workgroups. 

  2. Close all programs, including any anti-virus programs. 

    For information about closing an anti-virus program, see the program documentation and Setup.txt on your Windows 98 compact disc. 

  3. If you are installing Windows 98 from a compact disc, insert the Windows 98 compact disc into the CD-ROM drive and make it the active drive. 

    – Or – 

    If you are installing Windows 98 from floppy disks, insert Setup Disk 1 into the floppy disk drive and make it the active drive. For example, type a: if the disk is in the A drive. 

    – Or – 

    If you are installing Windows 98 from source files on a network server, connect to that server and switch to the shared network directory that contains the Windows 98 source files. 

  4. In File Manager, select the disk drive you used in step 3. 

  5. On the File menu, click Run

    The Run dialog box appears. 

  6. In the Open box, enter the location of the Windows 98 compact disc. For example, type the drive letter, followed by a colon (:), a backslash (\), and the word setup (or, you can click Browse and browse to the Setup.exe file). 

  7. Click OK

    The Windows 98 Setup Wizard starts. 

  8. Follow the instructions on your screen. 

Dual Booting Windows 98 with Windows 3.1x and MS-DOS

You can configure your computer to dual boot with Windows 3.1x as long as the computer has MS-DOS 5.0 or later by using the F4 boot-to-previous operating system feature. To dual boot Windows 98 with these operating systems, your computer's C drive must be FAT 16.

For more information about how Windows 98 Setup treats disk partitions created under other operating systems, see "Partition Requirements" in Chapter 2, "Setting Up Windows 98."

Important To take advantage of the Windows 98 dual-boot capabilities, the entry BootMulti=1 must be set in the Windows 98 Msdos.sys file in the root directory. For more information, see "Msdos.sys: Special Startup Values" earlier in this chapter.

To set up dual-boot capabilities for a new installation of Windows 98
  • During Windows 98 Setup, when you are installing Windows 98 for the first time, make sure you specify a new directory that does not already have another version of Windows in it.

Windows 98 Setup makes all of the necessary changes to preserve your existing version of MS-DOS, Windows 3.1x, or Windows for Workgroups 3.1x, and your current Autoexec.bat and Config.sys files.

If you have already installed Windows 98 without dual-boot capabilities, you can follow these steps to allow MS-DOS to dual boot with Windows 98. However, you will not be able to dual boot with your previous version of Windows.

To set up dual-boot capabilities after Windows 98 has been installed
  1. On a bootable floppy disk that starts MS-DOS 5.0 or later, rename the Io.sys, Msdos.sys, and Command.com files on the disk to Io.dos, Msdos.dos, and Command.dos.

  2. Create two empty text files named Config.dos and Autoexec.dos. You can customize these now or later to be appropriate for the MS-DOS version you will be adding. 

    Caution You must rename the MS-DOS versions of these files before copying them to the root directory. Otherwise, you will destroy your Windows 98 installation. 

  3. Copy all the .dos files to the root directory of the boot drive. This is usually drive C. Make duplicates of these files on your host drive if you want to use disk compression. 

  4. Mark the .dos files in the root directory of the boot drive with the hidden, system, and read-only attributes (attrib -r -s -h *.dos). 

  5. Change the Msdos.sys on the boot drive to include the line bootmulti=1. Instructions for making changes to Msdos.sys can be found earlier in this chapter. 

Installing Windows 98 over MS-DOS

The versions of MS-DOS supported for installing Windows 98 are versions 5.0 or later.

Tip for Running MS-DOS After Windows 98 Is Installed

If you install Windows 98 in a different directory from the one containing your previous Windows 3.1x version, you can start the computer by using the previous version of MS-DOS. To do this, make sure the entry BootMulti=1 is in the Windows 98 Msdos.sys file, and then press CTRL during system startup and choose the related option.

Files Deleted by Windows 98 Setup

This section lists MS-DOS and other files that are deleted by Windows 98 Setup. Notice, however, that these files are deleted from the old MS-DOS directory only if you install Windows 98 in the existing Windows 3.1x directory. Otherwise, the old MS-DOS files are all preserved so that you can start the computer using the older version of MS-DOS.

The Windows 98 command-line commands are stored in the Command subdirectory of the Windows directory. Deleting the related MS-DOS command file will not affect your ability to use the command under Windows 98. The versions that are deleted by Setup are known to be incompatible with Windows 98; for example, many of these MS-DOS commands do not support long file names. Table 5.14 shows files removed by Windows 98 Setup.

Table 5.14 Files removed by Windows 98 Setup 

MS-DOS and Windows 3.1x files

Ansi.sys
Attrib.exe
Chkdsk.exe
Choice.exe
Country.sys
Debug.exe
Defrag.exe
Deltree.exe
Diskcopy.exe
Display.sys
Doskey.com
D??space.bin1

COMPAQ DOS 5.0 files

Cache.exe
Cemm.exe
Cemmp.exe

Non-MS-DOS operating system files

Delpurge.exe
Delwatch.exe
Diskmap.exe
Diskopt.exe
Dosbook.exe

Pre-MS-DOS 5.0 files

Append.com
Asgnpart.com
Backup.exe
Bootf.com
Cache.sys
Cemm.exe
Cemmp.exe
Chkdsk.exe
Cmpqadap.com
Compact.exe
Configur.com
Debug.exe
Detect.com
Diskcomp.exe
Diskcopy.exe
Diskinit.com
Diskinit.exe
Dosutil.meu
Dskscan.exe
Dsksetup.com
Edlin.exe
Emm386.sys

1 Drvspace.* or Dblspace.*

System Startup with MS-DOS Multiple Configurations

Windows 98 supports multiple configurations for the same computer, and it dynamically determines which configuration is being used. If Windows 98 cannot determine the specific configuration used during system startup before processing Config.sys, it presents a menu of available configurations as listed in the registry, and it prompts you to select the configuration you want.

If you have a multiple configuration established in Config.sys, that menu is presented next. However, if you use a multiple configuration to switch between different versions of Windows, you must edit Config.sys manually to repair this configuration after Windows 98 is installed. For information about how to create multiple configurations for the same computer under Windows 98, see Chapter 24, "Device Management."

Dual Booting Windows 98 with Windows NT

If you install Windows 98 to dual boot with Windows NT, boot to MS-DOS, and then run Setup from either MS-DOS or Windows 3.1x. You will not be able to install Windows 98 to a directory with a shared Windows 3.1x/Windows NT configuration; you will need to install Windows 98 in a different directory.

You can install Windows 98 to dual boot with Windows NT on a computer. This section provides some notes for installing Windows 98 with Windows NT.

Important In order to take advantage of the Windows 98 dual-boot capabilities, the entry BootMulti=1 must be set in the Windows 98 Msdos.sys file in the root directory. For more information, see "Msdos.sys: Special Startup Values" earlier in this chapter.

To install Windows 98 to dual boot with Windows NT
  1. Ensure that the computer is configured to dual boot between Windows NT and MS-DOS. Check your Windows NT documentation for details. 

  2. Start the computer by using the MS-DOS operating system. 

  3. Run Windows 98 Setup as described in Chapter 2, "Setting Up Windows 98." 

Remember that if your computer has any Windows NT file system (NTFS) partitions, they are not available locally from within Windows 98.

If you run MS-DOS from a floppy disk in order to install Windows 98, you will not be able to start Windows NT afterward. You can restore the multiboot configuration by starting the computer with your Windows NT Boot Disks and selecting the Repair option. You will then be prompted for your Windows NT Repair Disk.

To run MS-DOS after Windows 98 has been installed, you must select the MS-DOS option from the Windows NT multiboot menu. Then, from the Windows 98 Startup menu, select Previous Version of MS-DOS.

To install Windows NT on a computer where Windows 98 is installed
  • At the command prompt, switch to the directory that contains the Windows NT source files, and then type winnt /w

The WINNT program is an MS-DOS -based application that creates the Windows NT Setup startup files and copies the system files to the hard disk from the source files. The /w switch allows WINNT to run under Windows. Using this switch also causes Windows NT Setup to skip the CPU detection process and the automatic restart at the end of Setup. You can also include the /b switch to copy the required startup files for Setup so that you do not have to create floppy disks for Setup.

For more information about the Windows NT operating system and about running computers with Windows 98 on a Windows NT network, see Chapter 16, "Windows 98 on Microsoft Networks."

Using a Windows 98 Startup Disk

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

This section describes the Windows 98 Startup Disk. You should make a Startup Disk and keep it on hand to help you boot your computer when you are having problems.

What Is New in the Startup Disk

The Startup Disk has changed significantly for Windows 98. The following items have been added:

  • The Microsoft Windows 98 Startup Menu 

  • Real-Mode IDE CD-ROM support 

  • Real-Mode SCSI CD-ROM support 

  • Edb.cab file 

  • RAMDrive 

  • New extract command: Ext.exe 

For a complete list of the contents of the Windows 98 Startup Disk, see "Contents of the Windows 98 Startup Disk" in Appendix B, "Windows 98 System File Details."

The MS Windows 98 Startup Menu

If you boot the computer using the Startup Disk, a boot menu appears allowing you to start the computer with or without CD-ROM support. The drivers on the Startup Disk support a variety of ATAPI CD-ROM drives. An example of the menu is shown below.

Microsoft Windows 98 Startup Menu 
1. Start the computer with CD-ROM support. 
2. Start the computer without CD-ROM support. 
3. View the Help file. 
Enter a choice: 1 Time remaining: 30 

If you use the Startup Disk to boot the computer and choose to load the real-mode CD-ROM drivers, but cannot access a compact disc in the drive, it is likely that the CD-ROM is connected to a sound card. The CD-ROM must be connected to the controller on the motherboard.

After you make your selection, the Config.sys file loads the CD-ROM driver (if selected) and then loads a 2-MB RAMDrive.

The Autoexec.bat file calls a second batch file, Setram.bat, to find a drive letter for the RAMDrive. The temp variables, path and comspec, are set to the RAMDrive. The files Command.com, Mode.com, Keybrd?.sys, and Keyb.com are copied to the RAMDrive root directory.

The following line in the Autoexec.bat file expands the files to the RAMDrive:

%RAMD%\extract /y /e /l %RAMD% edb.cab > NUL 

Finally, if a CD-ROM driver is loaded, MSCDEX is launched.

CD-ROM Support

Real-Mode IDE CD-ROM Support

The Windows 98 Startup Disk includes a real-mode generic ATAPI CD-ROM driver (Oakcdrom.sys) that allows the CD-ROM to function when the protected mode of the GUI interface is not available. This occurs when booting into either MS-DOS or Windows fails to boot into the GUI. Although CD-ROM manufacturers accompany CD-ROM drives with a floppy disk with the specific drivers to use, they may or may not be available when needed most.

Real-Mode SCSI CD-ROM Support

Real-mode generic SCSI CD-ROM drivers are also supported (Mylex Btdcrom.sys and Adaptec Aspicd.sys) to allow a SCSI CD-ROM to function when booting into MS-DOS.

RAMDrive

The RAMDrive created from the Config.sys file is 2 MB in size. Keep in mind that the tmp path points to this location. After the files are expanded and placed here, there is only about 1.384 MB of space available.

Warning The RAMDrive is created during the processing of the Config.sys file. Drive letter assignment for a CD-ROM is not performed until MSCDEX is loaded in the Autoexec.bat file. Therefore, customers who normally boot without a RAMDrive will find their CD-ROM drive moved one letter back.

Extract Command (Ext)

The Ext.exe command is a new and simple extract command designed to work with Extract.exe. You type ext at a command prompt. Ext.exe detects if the Win98 CDROM is in the drive and defaults to that directory for its source location. If it is not available, it defaults to A:\. Otherwise, you are asked to enter the path to the Windows CAB files.

You then enter the name(s) of the file(s) you want to extract and enter the path to the directory to extract the files to. The CAB files scroll up the screen until the file is found. A sample of the display is shown below.

Microsoft (R) Extract Command Line Helper 
---------------------------------------------------------------------- 
Please enter the path to the Windows CAB files (a:) : d:\Win98 
Please enter the name(s) of the file(s) you want to extract: 
explorer.exe 
Please enter the path to extract to ("Enter" for current directory) C:\Windows 
The Options you entered were: 
------------------------------------------------ 
Source Path : d:\Win98 
File(s) to extract : explorer.exe 
Destination Path : C:\Windows 
Is this okay? (y/n) : 

Note It takes a long time to expand the file (a 60-KB file expands in 77 seconds on an Intel 266MMX Pentium machine).

Ext Error Messages

You might have to reset the TMP variable for large files, because it points to the RAMDrive and there is a limited amount of free space available. Use the command Set TMP=C:\. Because EXT uses TMP, resetting the TEMP variable does not work. If you do not reset the TMP variable, you may get the following error message:

"Error: Out of memory while processing cabinet file Win98_41.cab" 

Tip If you receive an error "Unable to write to disk" or "Disk initialization error" when creating a Startup Disk, the disk may be defective. Insert a different disk and start again.

Starting Your Computer with the Startup Disk

Follow the following procedure to start your computer with the Startup Disk.

To start your computer with the Startup Disk
  1. Insert the disk in the floppy drive of your computer and turn the computer on. 

  2. After a few moments, you see the "Microsoft Windows 98 Startup Menu" screen. Three menu items are offered. 

  3. If you need to access the CD-ROM, for example, to restart Setup or to use the troubleshooting tools, select Start the computer with CD-ROM support

  4. If you do not want to access the CD-ROM (for example, if you need to save memory or you are running Setup from the hard drive of the machine) select Start the computer without CD-ROM support

  5. You can also select View the Help file for more information about the Startup Disk. 

For more information on setup problems and the Windows 98 Startup Disk, see "Troubleshooting Setup" later in this chapter.

Note The generic CD-ROM drivers may not work with all CD-ROM hardware. If these drivers do not function with your hardware, you will have to use the drivers that shipped with your CD-ROM.

Removing Windows 98 from a Computer

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

You can uninstall Windows 98 as long as your current configuration satisfies the following conditions:

  • You clicked Yes (recommended) on the Save System Files? dialog box that appeared when you installed Windows 98 the first time. If you clicked Yes, two files containing the saved Windows 95 system files, Winundo.dat and Winundo.ini, were created in the root directory of the partition that you designated during Setup. 

  • The system boot partition or any partition on the same physical drive where Winundo.dat is located was not compressed when you installed, and you did not compress it after installing Windows 98. 

  • You did not convert any file systems to FAT32, unless your Windows 95 version is OSR2. 

Note The retail and OSR1 versions of Windows 95 cannot read FAT32 drives.

Windows 98 can be removed from a computer by using the procedures described below. If the computer is configured for dual booting, you will be left with the previous versions of MS-DOS and Windows 3.1x intact. The recommended method for removing Windows 98 is to start the computer and use the F8 key to go to a command line, as described in the following procedure. When you do this, real-mode Windows 98 operating system files start the computer. If you encounter problems starting Windows 98 in this way, start your computer from the previous operating system (which might require using a floppy disk).

During the installation of Windows 98, you have the option of saving your Windows 95 system files. If you save your system files, you can uninstall Windows 98 and restore your Windows 95 environment. If you created shortcuts after you saved your system files, you have to delete them manually, because information about these shortcuts does not exist in the system files you saved.

Important This recovery capability is available only if you do not compress your primary partition after you upgrade to Windows 98.

To uninstall Windows 98

  1. In Control Panel, double-click Add/Remove Programs. 

  2. On the Install/Uninstall tab, click Uninstall Windows 98, and then click Add/Remove

    The Windows 98 Uninstall dialog box appears explaining that you are about to remove Windows 98 from your computer and restore Windows 95. 

  3. Click Yes to continue with the uninstall procedure. 

    A dialog box appears informing you that your disk(s) will be checked for errors. 

  4. Click Yes

    The ScanDisk program scans all non-removable hard disks, and another dialog box appears asking if you want to continue. 

  5. Click Yes

The computer restarts in MS-DOS mode, and the program Uninstal.exe runs automatically. This program is located in the \Windows\Command directory. The MS-DOS program restores the Windows 95 files and the settings contained in Winundo.dat; it then prompts you to restart the computer. Once the computer restarts, Windows 95 is restored.

Important Any programs that you have installed after installing Windows 98 must be reinstalled in the restored Windows 95 configuration.

Removing the Windows 95 System Files

To remove the Windows 95 system files, you can delete the Winundo.dat and Winundo.ini files manually. However, after doing this, the Uninstall Windows 98 and Delete Windows 98 uninstall information items (Windows 98 uninstall information) will still be displayed in the Install/Uninstall tab on the Add/Remove Programs Properties dialog box. If you want to remove the Windows 95 system files and remove the Windows 98 uninstall information, use the following procedure.

To remove the Windows 95 system files and the Windows 98 uninstall information
  1. In Control panel, double-click Add/Remove Programs. 

  2. On the Install/Uninstall tab, click Delete Windows 98 uninstall information, and then click Add/Remove

    The Windows 98 Uninstall dialog box appears explaining that if you remove these files, you can no longer uninstall Windows 98. 

  3. Click Yes to continue with the uninstall procedure. 

    A dialog box appears informing you that the files have been successfully deleted. 

  4. Click OK

    The Delete Windows 98 uninstall information and Uninstall Windows 98 items no longer appear on the Install/Uninstall tab. 

Removing Windows 98 with Command-Line Startup

Before you begin this process, make sure you have a system startup disk that contains an earlier version of MS-DOS and the Sys.com file. You need this startup disk because the Windows 98 startup files (real-mode operating system files) must be deleted, so the process for removing Windows 98 makes your hard disk temporarily unbootable.

Note The MS-DOS 6*.x* disk #1 is bootable, but the retail MS-DOS 5.0 disk #1 is not, and OEM versions may vary. To make a startup disk with MS-DOS 6*.x*, run setup /f from disk #1.

To remove Windows 98 when the computer is started to the command line
  1. Start the computer, and press CTRL when the **"**Starting Windows" message appears. 

    If you have problems starting the computer in this way, you can use the "Removing Windows 98 with Your Previous Operating System" procedure later in this chapter. 

  2. Select Command Prompt Only

  3. To make it easier to delete files and directories, copy the Windows 98 version of Deltree.exe to the boot drive. At the command prompt, type: 

    copy \windows\command\deltree.exe c:\ 

  4. To use the Windows 98 version of ScanDisk to clear invalid entries and long file names, copy the ScanDisk files from the Windows Command directory to the root directory. At the command prompt, type: 

    copy \windows\command\scandisk.* c:\ 

    Use Notepad or a similar text editor to edit Scandisk.ini in the \Windows directory. Change the entries controlling whether ScanDisk looks for invalid characters in file names and volume labels:

    • Set labelcheck=on to specify that ScanDisk should check volume labels for invalid characters. 

    • Set spacecheck= on to specify that ScanDisk should check for invalid spaces in file names. 

    For information about the entries in Scandisk.ini, see that file in the Windows directory. 

  5. To remove all entries that your earlier version of MS-DOS might see as invalid, type scandisk followed by the letter identifying the drive containing the Windows 98 installation at the command prompt. For example: 

    scandisk c: 

    If you receive error messages during the ScanDisk process, refer to Help for information to help you resolve the error. 

  6. To delete the Windows 98 directory, type in the root directory of the drive containing the Windows 98 installation: 

    deltree windows 

    In this command, windows is the name of the directory containing the Windows 98 files. 

    Caution This command deletes all subdirectories of the Windows 98 directory. Before performing this step, make sure that the Windows 98 directory tree does not contain any critical data that has not been backed up.

    This step also requires that you reinstall all Windows-based programs at the end of this procedure, so the correct drivers and settings are available in the restored Windows directory. 

  7. To delete the Windows 98 Config.sys and Autoexec.bat files, type in the root directory of the boot drive: 

    deltree Config.sys
    deltree Autoexec.bat 

  8. To delete the Winboot.ini file and the Winboot directory, if present, type: 

    deltree winboot.* 

  9. To delete the setup, boot, and detection log files, type: 

    deltree setuplog.*
    deltree bootlog.*
    deltree detlog.* 

  10. To delete the real-mode operating system files Io.sys and Msdos.sys, in the root directory of the boot drive (or from the root directory of the host drive, if the boot drive is compressed), type: 

    deltree Io.sys
    deltree Msdos.sys 

  11. To delete the Windows 98 compression drivers (Dblspace.bin and Drvspace.bin), if present, type in the root directory of the boot drive (or from the root directory of the host drive, if the boot drive is compressed): 

    deltree d??space.bin 

  12. To delete the Windows 98 command processor (Command.com), type in the root directory of the boot drive (or both from the C drive and from the root of the host drive, if the boot drive is compressed): 

    deltree Command.com 

  13. Put a bootable floppy disk with your earlier version of MS-DOS into drive A, and then restart the computer. After the computer starts from the floppy disk, put your earlier version of MS-DOS back on the boot drive (or the host drive, if the C drive is compressed) by typing sys followed by the letter identifying the boot or host drive and a colon. For example: 

    sys c: 

  14. If you have MS-DOS version 6.0 and are using compression, copy Dblspace.bin from the DOS directory to the root directory of the boot drive. Also, for all versions of MS-DOS, if you have a shell= statement referencing Command.com from a different directory, copy Command.com to the root directory. Then remove the floppy disk, and restart the computer from the hard disk.

To start the system with previous configuration files, copy Config.dos to Config.sys and Autoexec.dos to Autoexec.bat.

If you remove Windows 98 from a dual-boot installation, Windows 98 will be removed completely, and the computer will start the same way it did before installing Windows 98.

If you removed Windows 98 from an upgraded Windows 3.1x installation, drivers that were located in the Windows directory (such as Himem.sys, Ifslhlp.sys, and Emm386.exe) will be missing until you reinstall Windows 3.1x. After this, the computer will start the same way it did before Windows 98 was installed.

You might need to reinstall the previous version of MS-DOS, if needed files were removed by Windows 98 Setup.

Removing Windows 98 with Your Previous Operating System

Use this procedure if you cannot start a computer in Windows 98 real mode as described in the preceding section.

Before you begin this process, make sure you have a bootable floppy disk that contains an earlier version of MS-DOS and the Sys.com file. The process for removing Windows 98 makes your hard disk temporarily unbootable, and the Windows 98 startup files (real-mode operating system files) must also be deleted.

Note The MS-DOS 6*.x* disk #1 is bootable, but the retail MS-DOS 5.0 disk #1 is not, and OEM versions may vary. To make a startup disk with MS-DOS 6*.x*, run setup /f from disk #1.

To remove Windows 98 when the computer is started with the previous operating system
  1. Start the computer, and press CTRL when the "Starting Windows" message appears. 

  2. Select Previous Version of MS-DOS

  3. To make it easier to delete files and directories, copy the Windows 98 version of Deltree.exe to the boot drive. At the command prompt, type: 

    copy \windows\command\deltree.exe c:\ 

  4. To copy the Windows 98 version of ScanDisk files from the Windows Command directory to the root directory, type: 

    copy \windows\command\scandisk.* c:\ 

    Use Notepad or a similar text editor to edit Scandisk.ini. Change the entries controlling whether ScanDisk looks for invalid characters in file names and volume labels:

    • Set labelcheck=on to specify that ScanDisk should check volume labels for invalid characters. 

    • Set spacecheck=on to specify that ScanDisk should check for invalid spaces in file names. 

  5. To remove all entries that your earlier version of MS-DOS might see as invalid, type scandisk followed by the letter identifying the drive containing the Windows 98 installation at the command prompt. For example: 

    scandisk c: 

    If you receive error messages during the ScanDisk process, refer to online Help for information to help you resolve the error. 

  6. To delete the Windows 98 directory, type in the root directory of the drive containing the Windows 98 installation, type: 

    deltree windows 

    In this command, windows is the name of the directory containing the Windows 98 files. 

    Caution This command deletes all subdirectories of the Windows 98 directory. Before performing this step, make sure that the Windows 98 directory tree does not contain any critical data that has not been backed up. 

  7. To delete the Windows 98 real-mode operating system file named Winboot.sys, which was renamed from Io.sys when you started the computer with your previous operating system, type the following command from the boot drive (or from the root directory of the host drive, if the boot drive is compressed): 

    deltree winboot.* 

  8. Delete the Windows 98 files Msdos.w40, Command.w40, Config.w40, and Autoexec.w40 files. (The renaming of these operating system files occurred when you used F8 to start the previous operating system.) To do this, type the following command at the command prompt (if the boot drive is not compressed): 

    deltree *.w40 

    If the boot drive is compressed, you must delete Msdos.w40 from the root directory of the host drive and Command.w40 from the root directories of both the host drive and the boot drive. 

  9. To delete the setup, boot, and detection log files, type: 

    deltree setuplog.*
    deltree bootlog.*
    deltree detlog.* 

  10. If you are using Stacker version 3.1, either skip this step or back up the STAC Dblspace.bin file before completing this step. To delete the Windows 98 compression drivers (Dblspace.bin and Drvspace.bin), in the root directory of the boot drive (or from the root directory of the host drive, if the boot drive is compressed), type: 

    deltree d??space.bin 

  11. Put a bootable floppy disk with the earlier version of MS-DOS into drive A, and then restart the computer. After the computer starts from the floppy disk, put your earlier version of MS-DOS back on the boot drive (or the host drive, if the C drive is compressed) by typing sys followed by the letter identifying the boot or test drive and a colon. For example: 

    sys c: 

  12. If you have MS-DOS version 6.0 and are using compression, copy Dblspace.bin to the root directory of the boot drive. Also, for all versions of MS-DOS, if you have a shell= statement referencing Command.com from a different directory, copy Command.com to the root directory. Then remove the floppy disk, and restart the computer from the hard disk.

If you remove Windows 98 from a dual-boot installation, Windows 98 will be removed completely, and the computer will start the same way it did before installing Windows 98.

If you removed Windows 98 from an upgraded Windows 3.1x installation, you might need to reinstall your previous version of MS-DOS if some of the necessary files were removed by Windows 98 Setup. Drivers that were located in the Windows directory (such as Himem.sys, Ifslhlp.sys, and Emm386.exe) will be missing until you reinstall Windows 3.1x into the Windows directory. After you reinstall Windows 3.1x, the computer will start the same way it did before Windows 98 was installed.

To remove Windows 98 from a computer with Windows NT installed
  1. Follow the procedure "To remove Windows 98 when the computer is started with the previous operating system" earlier in this section. 

  2. Use the Windows NT Setup disk #1 to restart your computer.

  3. When prompted, choose Repair, then insert the Windows NT Emergency Repair Disk and choose the option to repair the boot files. 

  4. Restore your original MS-DOS and Windows 3.1x configuration. 

The next section provides information about solving problems that might occur during Setup or system startup. For specific information about troubleshooting procedures and the tools provided with Windows 98 (including details about using the Startup menu and Safe Mode for troubleshooting), see Chapter 27, "General Troubleshooting."

Note If you have MS-DOS-based applications that require complete access to system resources, see the information about using MS-DOS Mode in Chapter 25, "Application Support."

Troubleshooting Setup

Cc768175.spacer(en-us,TechNet.10).gif Cc768175.spacer(en-us,TechNet.10).gif

Setup uses different procedures to recover from a setup failure, depending on when the failure occurred in the setup process. Furthermore, other hardware and software issues may cause Setup to fail.

If necessary, you can uninstall Windows 98 and return to your previous Windows 95 configuration, as described later in this section. Once you have thoroughly tested all your programs, you can also remove the saved system files to free up the disk space they occupy.

If Setup fails, attempt to restart it using the following procedure.

To restart Setup after a failure

  1. Press F3 or click the Exit button.

    If the system does not respond, restart the computer by pressing CTRL+ALT+DEL. If this fails, turn off the computer, wait 10 seconds, and then turn it on again. 

  2. Start Setup again. Setup prompts you to use Safe Recovery to recover the failed installation. Choose the Safe Recovery option, and click the Continue button. Setup will skip the portion that caused the initial failure. 

  3. If Setup fails while copying files, the user may be required to manually load their Real Mode CD-ROM. The previous version of Windows 95 may no longer boot, and access to the CD-ROM is required. 

Tips for Installing Real-mode CD-ROM Drivers

This section presents tips that will make installing real-mode CD-ROM drivers easier.

Using Drivers on a Windows 98 Startup Disk

If you have a Windows 98 Startup Disk from another installation, you can use the CD-ROM drivers included on that disk.

Using Drivers from Windows 95

If you are currently running Windows 95, chances are you already have a portion of the CD-ROM drivers loaded.

To use existing CD-ROM drivers when running Windows 95
  1. On the Start menu, click Shut Down, and then select Restart in MS-DOS mode

  2. Windows 98 starts up; press F8 when you see "Starting Windows 95." 

  3. Choose Command Prompt Only. 

  4. At the C:\ prompt, type dosStart.bat

Using Drivers from Windows 3.1x or MS-DOS

If you lose access to your CD-ROM during the Windows 98 Setup process, and you are currently running Windows 3.1x, you can gain access to your CD-ROM again.

To use existing CD-ROM drivers while running Windows 3.1x
  1. Reboot the computer, and press F8 when you see "Starting Windows95." Select Command Prompt Only. If you are running MS-DOS, simply boot directly to the command prompt. 

  2. Edit Autoexec.bat by typing Edit Autoexec.bat

  3. Delete the text Rem by Windows 98 Setup in front of the line that includes the reference to Mscdex.exe. 

  4. Exit Edit by pressing ALT+F, typing x, and saying Yes to save the file. 

  5. Reboot. If Setup does not continue on its own, you should run it again, choosing Smart Recovery if prompted. 

  6. If the computer stops again during the hardware detection process, turn your machine off, wait 10 seconds, and then turn it back on. Setup should then continue and skip the offending detection module that caused Setup to hang. This process may be required more than once on some systems. 

Tip Whenever you encounter a Setup problem you cannot fix easily, restart your computer and wait 15 to 20 seconds before starting Setup again.

You can use the information in Setuplog.txt and Detlog.txt to check for the device or devices that caused the problems. Also review any messages added by Setup in the Autoexec.bat file for instructions on correcting setup problems.

The following sections describe specific setup problems and how to resolve them.

Starting Your Computer with the Windows 98 Startup Disk

If you have problems with Setup or have trouble starting Windows 98, you can use the Windows 98 Startup Disk to start your computer and gain access to your system files. You are prompted to create a Startup Disk during Windows 98 Setup. We recommend that you create extra Startup Disks after you install Windows 98 with Add/Remove Programs in Control Panel.

The Windows 98 Startup Disk contains several system and diagnostic programs, such as ScanDisk and Uninstall. The disk also contains a generic CD-ROM driver in case your computer has difficulty communicating with your CD-ROM drive.

Tip To help you troubleshoot, you can create several Startup Disks with different configurations on each disk; for example, you can save a disk with the specific drivers for your hardware.

Important Startup disks created with previous versions of Windows are not compatible with Windows 98. When you install Windows 98, you must create a new Startup Disk, either during Setup or using Control Panel.

To create a Startup Disk after installing Windows 98
  1. In Control Panel, double-click Add/Remove Programs. 

  2. The Add/Remove Programs Properties dialog box appears. 

  3. Click the Startup Disk tab, and then click Create Disk

  4. Label a floppy disk "Windows 98 Startup Disk," insert the disk in your floppy disk drive, and then click OK. Click OK again, and then follow the instructions on your screen. 

  5. Setup also creates a Windows\Command\EBD directory for emergency purposes when you can not boot your system and do not have a Startup Disk. This is created at the same time Setup prompts for the Startup Disk. To create an EBD from the MS-DOS prompt, run the Bootdisk.bat program located in the Windows\Command directory. 

Important Any files currently on the floppy disk are erased when you create a Windows 98 Startup Disk.

For more information about the Windows 98 Startup Disk, and using it to start the computer, see "Using a Windows 98 Startup Disk" earlier in this chapter.

Using the Windows 98 Setup Built-In Troubleshooting Aids

Windows 98 contains log files and includes utilities that can assist you in correcting problems that occur during the setup or startup processes. This section describes the following built-in troubleshooting aids:

  • Safe Recovery with Windows 98 Setup 

  • Installed components verification 

  • Startup diskto use ex 

  • Startup Menu options

  • Win.com switches 

Using Safe Recovery with Setup

Setup uses Safe Recovery to determine what caused an installation to fail. Safe Recovery uses the information available in Detchrash.log, for example, to avoid performing detection on the same device that caused Setup to fail before.

To use Safe Recovery if Setup fails
  1. Run Setup again.

  2. When the Safe Recovery dialog box appears, click Safe Recovery

You can also use the Setuplog.txt, Detlog.txt, and Bootlog.txt files in the root directory of the boot drive to determine why Setup failed. These text files contain, respectively, the Safe Recovery and hardware detection information in a readable form, plus a log of system startup actions. Setuplog.txt, for example, will show the point at which Setup failed.

To automatically scan these log files for installation or detection errors, you can use the following commands in a setup script. Create a batch file containing the following text and run it from the root directory of the boot drive (C:\) after an unsuccessful Setup attempt.

@echo off 
echo "Entries found in Setuplog.txt" > log.txt 
find /i /n "installtype" setuplog.txt >> log.txt 
find /i /n "installdir" setuplog.txt >> log.txt 
find /i /n "detection" setuplog.txt >> log.txt 
find /i /n "runningapp" setuplog.txt >> log.txt 
find /i /n "rootfilesrenamed" setuplog.txt >> log.txt 
find /i /n "error" setuplog.txt >> log.txt 
find /i /n "failed" setuplog.txt >> log.txt 
echo "Entries found in Bootlog.txt" >> log.txt 
find /i /n "fail" bootlog.txt >> log.txt 
find /i /n "error" bootlog.txt >> log.txt 
find /i /n "dynamic load success" bootlog.txt >> log.txt 
find /i /n "initcomplete success" bootlog.txt >> log.txt 
echo "Entries found in Detlog.txt" >> log.txt 
find /i /n "avoidmem" Detlog.txt >> log.txt 
find /i /n "detected" Detlog.txt >> log.txt 
find /i /n "error" Detlog.txt >> log.txt 
cls 
type log.txt |more 
other helpful info from Setuplog.txt… 
fsCmosAVCheck: Attempting CMOS Anti Virus Test 
fsCmosAVCheck: CMOS Anti Virus Test SUCCEEDED  
Using a Startup Disk

You can use a Windows 98 Startup Disk to load the operating system and display an MS-DOS command prompt. The Startup Disk also contains utilities for troubleshooting a malfunctioning operating system. You can create a Startup Disk during Windows 98 Setup or afterward in Control Panel.

Caution It is strongly recommended that you create a Windows 98 Startup Disk as part of Windows 98 Setup, and that you maintain an updated copy of the Startup Disk each time you change the system configuration after installing Windows 98.

If you did not create a Startup Disk during Setup, you can create one using a single floppy disk.

To create a Windows 98 Startup Disk after Windows 98 is installed
  • In Add/Remove Programs in Control Panel, click the Startup Disk tab. Then click Create Disk, and follow the instructions on-screen. 

    – Or – 

    Run the Bootdisk.bat utility from the Windows\Command directory to create a Startup disk from MS-DOS. 

Using Startup Menu Options

If the system fails to start, Windows 98 displays a Startup menu that contains troubleshooting options. You can also manually prompt Windows 98 to display the Startup menu.

To display the Windows 98 Startup menu
  • Restart the computer. Hold CTRL while the system is booting. This will take you to the boot menu. You no longer see the "Starting Windows 98" prompt. The F8 key is still functional, but the 2-second boot delay has been removed. If CTRL is mapped to other system functionality, you can use MSCONFIG and the Advanced option to enable the boot menu by default. 

Table 5.15 describes Startup menu options. The contents of this menu can vary, depending on the options specified in the Msdos.sys, and the configuration of the computer.

Table 5.15 Startup menu options 

Start menu option

Description

Normal

Starts Windows, loading all normal startup files and registry values.

Logged (Bootlog.txt)

Runs system startup creating a startup log file.

Safe Mode

Starts Windows, bypassing startup files and using only basic system drivers. You can also start this option by pressing F5 or typing win /d:m at the command prompt.

Step-by-Step Confirmation

Starts Windows, confirming startup files line-by-line. You can also start this option by pressing F8 when the Startup menu is displayed.

Command Prompt Only1

Starts the operating system with startup files and registry, displaying only the command prompt.

Safe Mode Command Prompt Only1

Starts the operating system in Safe Mode and displays only the command prompt, bypassing startup files. Same as pressing SHIFT+F5.

Previous version of MS-DOS

Starts the version of MS-DOS previously installed on this computer. You can also start this option by pressing F4. This option is available only if BootMulti=1 in Msdos.sys.

1 When you start the computer at the command prompt, you can use switches with the win command to control Windows 98 startup for troubleshooting purposes, as described in Chapter 27, "General Troubleshooting."

The following sections describe when to use these Startup menu options to troubleshoot system problems.

Tip Windows 98 uses entries in the Msdos.sys file to control Startup menu options, automatic loading of certain drivers, and path statements for system files. If Windows 98 does not start as expected, check the entries in Msdos.sys.

Safe Mode

If Windows 98 fails to start normally, select Safe Mode from the Startup menu to begin troubleshooting. Windows 98 automatically initiates Safe Mode if it detects that system startup failed (for example, if a Wnbbotng.sts signature file still exists in the Windows directory), or if the registry is corrupted (for example, if an important key such as System is missing), or if an application requests Safe Mode.

Safe Mode bypasses startup files, including the registry, Config.sys, Autoexec.bat, and the [Boot] and [386Enh] sections of System.ini, and provides you with access to the Windows 98 configuration files. You can make any necessary configuration changes, and then restart Windows 98 normally. Use Safe Mode for system startup in situations such as the following:

  • If Windows 98 seems to stall for an extended period of time. 

  • If Windows 98 does not work correctly or has unexpected results. 

  • If you cannot print to a local printer after attempting other troubleshooting steps. 

  • If your video display does not work correctly. 

  • If your computer suddenly slows down. 

  • If you need to test an intermittent error condition. 

When starting Windows 98 in Safe Mode, only the mouse, keyboard, and standard VGA device drivers are loaded. This makes Safe Mode useful for isolating and resolving error conditions caused by both real-mode and Windows drivers. The Startup menu can include three to four Safe Mode options, depending on whether the computer's hard disk is compressed or not. Each Safe Mode option disables a different portion of the startup process, as shown in Table 5.16.

Table 5.16 Startup actions disabled by Safe Mode 

Action

Safe Mode

Command Prompt Only1

Process Config.sys and Autoexec.bat

 

 

Load Himem.sys and Ifshlp.sys

 

Cc768175.check(en-us,TechNet.10).gif

 

Process registry information

 

 

Load Command.com

 

 

Cc768175.check(en-us,TechNet.10).gif

Load DoubleSpace or DriveSpace if present

 

Cc768175.check(en-us,TechNet.10).gif

 

Run Windows 98 Win.com

 

Cc768175.check(en-us,TechNet.10).gif

 

Load all Windows drivers

 

 

1 The Safe Mode Command Prompt Only option also loads DoubleSpace or DriveSpace if present.

Note Safe Mode With Networking is not supported in Windows 98.

Safe Mode Command Prompt Only

Safe Mode Command Prompt Only loads the Command.com and DoubleSpace or DriveSpace files (if present). It does not load Himem.sys, Ifshlp.sys, or Windows 98. The following are examples of when to use Safe Mode Command Prompt Only:

  • If Windows 98 fails to start, even with the Safe Mode option. 

  • If you want to use command line tools (such as when editing Config.sys). 

  • If you want to avoid loading Himem.sys or Ifshlp.sys. 

Step-by-Step Confirmation

Step-by-Step Confirmation allows you to specify which commands and drivers the system should process by confirming each line of the startup files. The following are examples of when to use Step-by-Step Confirmation:

  • If the startup process fails during loading of the startup files. 

  • If any real-mode drivers must be loaded to run Windows 98 successfully. 

  • If you need to check for registry failure messages. 

  • If you need to verify that the expected drivers are being loaded. 

  • If you need to temporarily disable a specific driver or set of drivers. 

  • If you need to check for errors in startup files. 

When you choose to confirm system startup line-by-line, the following prompts appear. (You can press ENTER to confirm or ESC to skip that part of system startup.)

  • Load DoubleSpace (or DriveSpace) driver? 

  • Process the system registry? 

  • Create a startup log file (Bootlog.txt)? 

  • Process your startup device drivers (Config.sys)? 

    Each line from Config.sys is displayed with the [Enter=Y,Esc=N] prompt. You can press TAB when the first Config.sys prompt appears to accept all options automatically. 

  • Process your startup command file (Autoexec.bat)? 

    Each line from Autoexec.bat is displayed with the [Enter=Y,Esc=N] prompt. You can press TAB when the first Autoexec.bat prompt appears to accept all options automatically. 

  • Run win.com to start Windows 98? 

  • Load all Windows drivers? 

If you press ENTER to answer Yes to each prompt, the result is the same as starting Windows 98 normally, except that the logo does not appear. Answering No to "Load All Windows Drivers?" runs Windows 98 in Safe Mode.

Using Win.com Switches

The following switches are available to start Windows 98 from the command prompt when you need to isolate an error condition:

win [/d:[f] [m] [n] [s] [v] [x]]

The /d: switch is used for troubleshooting when Windows 98 does not start correctly. The switches in Table 5.17can be used with the /d: switch.

Table 5.17 Switches used with the /d: switch 

Switch

Meaning

f

Turns off 32-bit disk access. Try this if the computer appears to have disk problems, or if Windows 98 stalls. This is equivalent to 32BitDiskAccess=FALSE in System.ini.

m

Starts Windows 98 in Safe Mode.

s

Specifies that Windows 98 not use ROM address space between F000:0000 and 1 MB for a break point. Try this if Windows 98 stalls during system startup. This is equivalent to SystemROMBreakPoint=FALSE in System.ini.

v

Specifies that the ROM routine should handle interrupts from the hard disk controller. Try this if Windows 98 stalls during system startup or disk operations. This is equivalent to VirtualHDIRQ=FALSE in System.ini.

x

Excludes all of the adapter area from the memory that Windows 98 scans to find unused space. This is equivalent to EMMExclude=A000-FFFF in System.ini.

Recovering from Common Setup Failures

This section covers how to diagnose and correct some of the most common Setup errors.

Recovering Before Your Computer Is Restarted for the First Time (First Restart)

If Setup encounters an error or stops before your computer is restarted for the first time during Setup, you must turn the computer off, turn it back on, and then run Setup again.

After the Setup Wizard has started again, Setup determines that a failure occurred, and the Safe Recovery screen appears:

Cc768175.wrk0k04(en-us,TechNet.10).gif

If you click Use Safe Recovery (recommended), Setup examines the Setuplog.txt file to determine where the failure occurred. Setup then resumes from the point where the failure occurred. If you click Do not use Safe Recovery, the Setup process will restart from the beginning.

The Safe Recovery option in Setup automatically skips previous problems so that Setup can be completed. You can also use Safe Recovery to repair damaged or corrupt installations.

Recovering During Hardware Detection

During Setup, the hardware detection phase is the most likely to cause Setup to fail. Figure 5.1 summarizes the cause, event, and solution for hardware detection problems.

Cc768175.wrk0k01(en-us,TechNet.10).gif

Figure 5.1 Cause, event, and solution for hardware problems 

Hardware detection of legacy devices, which takes place after the first restart, will only occur if Windows 98 is being set up in a new directory or into a newly formatted hard disk or when running Setup from Windows 95 and verification fails. During this phase, Setup writes data to and reads data from various hardware addresses, including I/O ports, IRQs, and memory address ranges.

During Setup, logs are maintained, which record Setup progress and store information that can be used for recovery. Table 5.18 describes the log files.

Table 5.18 Setup log files 

Log file name

Purpose

Details

Detlog.txt

Records the start of a detection test and the test outcome. Keeps a record of devices Setup finds during the detection process.

A hidden file located in the root directory of the C drive.

Detcrash.log

Records which detection steps were successfully completed so that Setup will not fail on the same problem.

A hidden file created only if a detection step caused the computer to stop responding. Located in the root directory of the C drive.

Setuplog.txt

Records what took place during Setup, including successes and failures. Used by Safe Recovery to determine where Setup will resume.

Located in the root directory of the C drive.

If a failure occurs after the first restart, hardware detection recovery uses the log files to skip the module that caused the failure so that Setup can proceed.

Caution You should not delete any of the log files described in this table; otherwise, Setup will not be able to detect failures. For example, deleting the Detcrash.log file prevents Setup from recognizing and failure and skipping it to proceed.

To restart Setup after a hardware detection failure
  1. Turn the computer off for 10 to 15 seconds.

  2. Turn the computer back on again. 

Bypassing Previous Setup Failures

When a failure occurs, Setup reloads the detection modules, checks the log files, and resumes after the point where the failure occurred, as shown in Figure 5.2.

Figure 5.2 shows an example of how Setup handles failures. In the first attempt at running Setup, there is a failure, and Setup logs it in the Detcrash.log file and restarts again. In the second attempt, it skips the point where the first failure occurred and continues with the setup process, but it encounters a second failure. It logs the second failure and restarts again. On the third attempt, it skips the points where the two previous failures occurred and then continues, this time successfully until Setup is complete.

Cc768175.wrk0k02(en-us,TechNet.10).gif 

Figure 5.2 How Setup handles failures 

Because detection can determine where a failure occurred, the installation process keeps moving forward by recognizing and bypassing the addresses where the previous attempts failed. Setup proceeds to the module where the failure occurred, checks Detcrash.log, verifies that the module caused the problem, skips the module, and then continues.

Even if the system fails several times, Setup continues to progress because it does not fail repeatedly on the same point of failure.

Tip You can easily find hardware that is not working by looking at the Device Manager tab in the System Properties dialog box accessed through the System icon in Control panel. Hardware that is not working appears with its tree expanded.

Verifying Installed Hardware

If your computer stops responding during hardware detection and you restart the computer, Windows 98 Setup may not detect some of your hardware. To verify that the computer's hardware has been detected, do the following:

To verify hardware detection
  1. In Control Panel, click System. 

  2. In the System Properties dialog box, click the Device Manager tab. 

    Expand each item in Device Manager to verify that all your hardware is listed. 

If the computer's hardware is not listed in Device Manager, then click Add New Hardware in Control Panel. If the Add New Hardware Wizard does not detect any new hardware, follow the on-screen directions and select the specific hardware from the Windows 98 hardware.

Recovering from Errors Due to Problematic Software

If Setup detects problematic software, it tries to provide instructions to correct the problem. If Setup is unable to diagnose the cause of the failure, it may present a message that states that Setup has failed. If this occurs, you must restart the computer and then restart Setup.

Troubleshooting Hard Disk Problems Using ScanDisk

Windows 98 Setup automatically runs ScanDisk to check for problems on your hard disk(s). If there are problems, Setup cannot continue until they are fixed.

Note The MS-DOS-based version of ScanDisk that Setup runs may detect long file name errors, but it cannot correct them. These errors will not prevent Setup from proceeding, but once it completes, you should run ScanDisk from within Windows 98 to correct these errors.

Fixing Hard Disk Problems

If you see a message during Setup that says you must run ScanDisk to fix problems on your hard disk and you are setting up Windows 98 over MS-DOS or a previous version of Windows, such as Windows 3.1, follow these steps.

To fix hard disk problems when setting up Windows 98 over MS-DOS or another version of Windows
  1. Exit Windows. 

  2. If you are setting up from floppy disks, insert Setup Disk 1 into the drive, and then type the following at the command prompt: 

a:scandisk.exe /all

where "a" is the drive that contains the Windows disk. 

– Or – 

If you are setting up from a compact disc, insert the compact disc and then type the following: 

<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">

d:\win95\scandisk.exe /all

where "d" is the drive that contains the compact disc.
  1. Follow the instructions on your screen and fix any problems that ScanDisk finds. 

  2. Start Windows, and then run Setup again. 

If you see a message during Setup that says you must run ScanDisk to fix problems on your hard disk and you are upgrading Windows 95 to Windows 98, follow these steps.

To fix hard disk problems when upgrading Windows 95 to Windows 98
  1. Exit Setup. 

  2. Click Start, point to Programs, point to Accessories, point to System Tools, and then click ScanDisk

  3. Check your hard disk(s) and any host drives you have for errors, and repair any problems found. 

Note If you are running Setup from MS-DOS, ScanDisk will run and you will be able to fix most problems from within Setup.

Problems Running ScanDisk During Setup

If you get a message during Setup saying that there is not enough memory to run ScanDisk, free some conventional and/or upper memory, and then run Setup again. If you have MS-DOS 6*.x*, try running MemMaker to free memory.

If you still do not have enough memory, or if you have other problems while Setup is running ScanDisk, then you can bypass ScanDisk in Setup by running Setup with the /is option. To do this, type the following command:

setup /is 

Note Bypassing ScanDisk during Setup is not recommended. If you do, there may be problems with your hard disk that could cause Windows 98 not to install or run correctly.

If you still have problems after running Setup with the /is option, try running Setup with the /iq option. To do this, type the following command:

setup /is /iq 

Problems with Compressed Drives

If you have used compression software to compress your hard disk, you may get a message saying that there is not enough space on the host partition of the compressed drive. Setup may have to copy some files to your startup drive, the host for your startup drive, or the host for your Windows drive. If you get this message, you should free up some space on the specified drive, and then run Setup again. Try one of the following:

  • Delete any unneeded files on your host partition. 

  • If you are running Windows 3.1 and have a permanent swap file, try making it smaller. In Control Panel, double-click 386 Enhanced, and then click Virtual Memory. Then modify the size of your swap file. 

    Use your disk compression software to free up some space on the host drive for the compressed drive. If you compressed your drive by using DriveSpace or DoubleSpace, follow these steps:

    1. Quit Windows. 

    2. Run Drvspace.exe or Dblspace.exe. 

    3. Select the compressed drive on whose host you want to free space. 

    4. On the Drive menu, click Change Size

If you used other compression software, such as Stacker, consult the documentation that came with it.

Note If you notice a discrepancy in the amount of free space reported by Setup and the amount of space you think is available on your host drive, it may be because Windows uses some space for creating a swap file. This may not appear to take up any space when Windows is not running.

If you create a Startup Disk during Setup, make sure you do not use a compressed disk for the Startup Disk.

Problems with SuperStor Compression

If you have compressed your hard disk by using SuperStor, Setup may not be able to find your startup drive and install Windows 98. If you get a message about this during Setup, uncompress your disk and remove SuperStor, then run Setup again.

Problems with XtraDrive Compression

If you have compressed your hard disk with XtraDrive and you are upgrading a previous version of Windows, Setup will not be able to install Windows 98 unless you turn off the XtraDrive write cache. To turn this off, follow these steps:

To turn off the XtraDrive write cache

  1. Quit Windows. 

  2. Run Vmu.exe (XtraDrive's Volume Maintenance Utility). 

  3. Choose Advanced Options, and then press ENTER. 

  4. Set the EMS cache size to 0

  5. Set the Conventional cache size to 1 (the minimum). 

  6. Set Allow Write Caching to NO

  7. At the confirmation prompt, choose Yes. You will see a message saying that you must restart your computer for the changes to take effect. 

  8. Quit Volume Maintenance Utility, and then restart your computer. 

  9. Start Windows, and then run Setup again. 

Cannot Read Setup (CAB) Files

If you have Multimedia Cloaking and are installing Windows 98 from floppy disks, Setup may not run successfully. If you see messages about Setup not being able to read CAB files, then follow these steps.

To run Setup on computers with Multimedia Cloaking
  1. Remove the line referencing Cacheclk.exe from your Config.sys and Autoexec.bat files. 

  2. Restart your computer. 

  3. Run Setup again. 

Installing from Your Local Hard Disk

One of the most common troubleshooting steps in Windows 98 Setup is installing from your local hard disk. By copying all the setup files to your hard disk, you can eliminate most of the problems associated with file copy and disk I/O issues. This also allows you to unload your CD-ROM drivers and free up conventional memory to assist with low memory errors.

To copy the setup files locally from within Windows 95
  1. Free an additional 120 MB of disk space beyond what Setup normally requires. Setup will typically require 195Mbytes for a Windows95 upgrade. 

  2. Create a temporary folder to store the Setup files on your hard drive. 

  3. Copy the contents of the Win98 folder on your Windows 98 CD-ROM to the temporary folder you just created (the subfolders underneath the Win98 folder are not required for Setup to complete successfully). 

  4. Reboot. Press F8 at the "Starting Windows95" screen, and choose "Safe Mode Command Prompt Only." 

  5. Now, switch to the temporary folder containing the Windows 98 Setup files and Type setup

To copy the setup files locally from within MS-DOS
  1. Make sure you have access to your CD-ROM drive (see above for more information). 

  2. Free an additional 120 MB of disk space in addition to what Setup normally requires. Setup will typically require 195 MB for a Windows 95 upgrade. 

  3. Create a temporary folder on the drive with plenty of free space to store the Setup files. To create a temporary directory, switch to that drive letter and type MD Win98tmp

  4. Now, switch to the Windows 98 CD-ROM drive and the Win98 directory by typing**: d:\Win98** where "d:/" is the drive letter of your CD-ROM. 

  5. Copy the Windows 98 Setup files to the temporary directory you just created by typing: Copy *.* C:\Win98tmp where "C:\" is the drive you created the temporary folder and "win98tmp" is the temporary directory you created. 

  6. After all the files are copied, reboot your system and perform a clean boot by bypassing your startup files. (For more information, see "Performing a Clean Boot" later in this chapter.) 

  7. Switch to the temporary directory to which you just copied the Setup files and start setup by typing setup

Performing a Clean Boot

If Windows 98 Setup is failing, it could be the result of third-party device drivers, utilities, or other programs running. Clean booting your system can fix many of these problems. There are several ways to perform a clean boot to install Windows 98.

To perform a clean boot using a floppy disk to start your computer
  1. If you have a Windows 98 Startup Disk, boot from that disk. This disk allows the option for loading with or without CD-ROM drivers and is a clean environment for running Setup. For more information see "Using a Windows 98 Startup Disk" in this chapter. 

  2. If you do not have a Windows 98 Startup Disk, boot from a previous Windows 95 or MS-DOS boot disk. This does not give access to your CD-ROM drivers, but this option can used if you copy the Setup files to your hard disk as described above. 

To perform a clean boot using Windows95 Safe Mode Command Prompt Only
  1. Boot your system and hold F8 at the "Starting Windows 95" screen. 

  2. Choose Safe Mode Command Prompt Only. This does not provide access to your CD-ROM drive, but this option can be used if the Setup files are copied to your hard disk as described above. 

Windows 98 Step by Step Boot

There are certain cases where you want load some drivers manually, for example, for troubleshooting purposes or when certain drivers are required by your system. You may also want to manually load your CD-ROM drivers if they were previously loaded by your system.

To perform a Windows 98 step by step boot
  1. Boot your system and hold the F8 key at the "Starting Windows95" prompt. 

  2. Choose the Step by Step option. 

  3. Now, say YES only to devices you need to. In most cases you always say YES to Himem.sys. 

Setup Could Not Back Up Your System Files

If you see an error message while Setup is saving your system files, there may not be enough disk space, particularly on compressed disks. You should free up space on the drive you are saving your system files on (the default drive is C) by removing unnecessary files.

If you get a message saying "Setup cannot continue on this system configuration," you may have an older, incompatible disk partition. Before running Setup, you will need to back up your data and then repartition your disk.

Common Setup Errors

This section describes how to diagnose and correct other Setup errors.

For more information, see the Setuplog.txt log file that Setup creates in the root directory of your startup drive.

Setup fails to start. 

If Setup fails to start, you should check memory, check for hardware detection conflicts, and check the access to the source for the Windows 98 installation files. Use the following checklist and procedures to find a solution.

  • Check the computer for viruses. 

  • Check for sufficient conventional memory. 

    Windows 98 requires 432 KB of conventional memory. If this is not available, check for unnecessary drivers or TSRs, remove them and then try again. You can also run the MS-DOS MemMaker utility to optimize conventional memory.

  • Check the RAM configuration in Config.sys. 

    For MS-DOS 4*.x* or earlier, settings should contain the following: 

device=himem.sys

For MS-DOS 5 or later, settings should contain the following: 

<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">

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

**Note** The path to these drivers is not specified in the preceding example. If you do not specify the path, you need to copy the drivers to the root of the startup drive. Using emm386 and dos=high,umb enables UMBs, but it is optional. 
  • Check for adequate XMS memory. Windows 98 requires at least 16 MB of XMS. If you are using MS-DOS 6*.x*, press F4 when you start the computer and the Starting MS-DOS message appears. Choose Step-by-Step Confirmation to verify that Himem.sys is loading. If not, make sure that verify the startup file syntax. 

  • At the command prompt, use mem /c /p to check for free conventional and XMS memory. 

  • If installing from a compact disc, check access to the drive.

  • If installing from the network, check your network connection.

  • Remove all extra entries in Config.sys and Autoexec.bat, except those required to start the system and, for a networked computer, to start the network. It is especially helpful to remove any entries related to non-Microsoft disk caching software. 

Setup starts, but an error is reported during the installation process. 

  • Restart Windows 98 Setup and use Safe Recovery. 

  • Check the Setuplog.txt or Detlog.txt files.

  • Verify that all system and networking components function normally. Run virus detection software and scandisk (specifying a Thorough Type of Test) to identify system problems that might cause errors. 

  • Check the content of the error message. Windows 98 Setup errors contain additional information about the condition causing Setup to fail. Examine the device or condition that the error describes.

  • Verify that system hardware is compatible. If Setup repeatedly fails, or if you suspect hardware conflicts with the Setup process, verify that the system components are supported. You might want to skip hardware detection. To do this, see "Setup Stops During Hardware Detection" later in this chapter. 

  • Check for a missing or damaged file. If a driver or system component file is referenced in the error, check to see if the file exists, if it is in the expected location, and if it has the correct file size, date, and version. For more information, see Chapter 27, "General Troubleshooting." 

Setup fails when run from floppy disks. 

When Setup fails when it is being run from floppy disks, you might see a message asking you to insert a disk in the floppy drive when a disk is already in the drive. Or, you might use the dir command to examine a Setup floppy disk and find that it fails or that garbled characters appear on the screen.

To solve this problem, first disable any BIOS-enable virus checking routine. Then check your computer hardware documentation or check with the manufacturer to ensure that the computer's CMOS settings are correct. If changing settings as advised by the manufacturer does not solve the problem, you can use the Drivparm utility.

To use Drivparm to solve floppy-disk hardware problems
  1. Start the computer using the most basic configuration files possible, loading no additional hardware drivers or other software in Config.sys and Autoexec.bat. 

  2. Insert a standard disk in drive A or drive B. At the command prompt, switch to that drive and type dir

  3. If this works, insert a disk from the Windows 98 floppy disks in the same drive, and type dir

  4. If this fails, garbled characters appear on the screen, or subsequent attempts to read the floppy disk fail, insert one of the following statements at the end of Config.sys. 

    For a 1.44 MB A drive, add: 

drivparm=/d:0 /f:7

For a 1.44 MB B drive, add: 

<pre IsFakePre="true" xmlns="https://www.w3.org/1999/xhtml">

drivparm=/d:1 /f:7

  1. If Config.sys contains an entry for Driver.sys, disable it by adding rem before the related command line.

  2. Save the Config.sys file, and restart the computer. Then repeat steps 2 and 3. If these steps are successful, leave the Drivparm statement in Config.sys so that you can run Windows 98 Setup. 

    If this procedure is not successful, the problem is related to the CMOS settings on the computer. For information and assistance, contact your computer manufacturer. 

You cannot access the server when installing from the network. 

  • Verify that the network domain is validating the user account. 

  • Check the user name, password, and access rights. 

  • Check basic network functionality. 

  • Check conventional and XMS memory. 

  • Check for and remove unnecessary drivers and TSRs. 

  • If using a login script, check that the login script runs properly. 

You may also be installing from a Password Protected share. If this is the case, Setup may present you with a dialog that says there is a problem with your network settings. If you choose to continue (this is not recommended), you should then get the Enter Password dialog and setup should continue.

For more information, see Chapter 14, "Introduction to Networking Configuration."

The network connection fails when you are installing from the network. 

  • Try to reconnect to the network share. 

  • If you cannot reconnect, restart the computer, and try again. 

  • Use another computer on the network to verify the installation server is working. 

  • Check the basic network connection. 

Setup stops during hardware detection. 

When Setup stalls during hardware detection, you might need to disable hardware detection for a device or class of devices. Before you do this, wait until at least three minutes have passed with neither disk nor screen activity (that is, the mouse pointer cannot be moved). Some detection routines take long enough that the computer might appear to stop temporarily.

To skip hardware detection in order to avoid problems
  1. Run Windows 98 Setup from MS-DOS and, if this is not the first attempt to install, select Safe Recovery

  2. To disable the specific device detection during Setup, in the Hardware Detection dialog box, select the option to specify the hardware devices to detect. Then make sure the check box next to the device is not checked. 

Setup cannot communicate with a device. 

If Setup cannot communicate with a specific hardware device on the system during installation, a message states that Setup has found a hardware device on your computer that is not responding and prompts you to try this device again. For persistent problems, the message provides instructions on how to exit Setup and restart the computer.

This error message can be caused by one of the following:

  • The network has stopped responding. 

  • A CD-ROM drive has stopped responding. 

  • A floppy disk drive has stopped responding. 

  • Setup can no longer access the hard drive to complete the installation process. 

Follow the recommendation in the message to turn off the computer, turn it back on, and rerun Setup with Safe Recovery. If the problem persists, identify the problem from the preceding list and correct it.

Problems occur during the file-copying phase of Setup. 

If this occurs, exit Setup, restart your computer, and rerun Setup. When prompted, select the Safe Recovery option and click Continue. The installation process should complete successfully.

If your computer stalls after all files have been copied, or if you receive an error at this point, it might be due to virus-protection software. Some computers have virus protection built into the ROM BIOS. You should disable the virus protection software or run your computer's configuration program to disable virus checking and then restart Setup. Select the Safe Recovery option, and the installation process should complete successfully.

An "Incorrect MS-DOS Version" error message appears. 

This error can occur when starting Setup from MS-DOS if you are using the 386MAX software utility. If this error occurs, temporarily disable the 386MAX commands from the startup files, and then run Setup again.

A "Standard Mode: Fault in MS-DOS Extender" error message appears. 

When running Windows 98 Setup from MS-DOS you might receive this error, indicating there might be a conflict in the upper memory region. To resolve this, either disable UMBs or remove EMM386 statements from Config.sys and rerun Setup.

A "Cannot Open File *.INF" error message appears. 

If you receive an error that states that an INF file cannot be opened, you might need to free memory by disabling SMARTDrive in Autoexec.bat, or by closing any applications running in Windows.

Setup requests a new source path. 

If this occurs, check the file source (the network drive or the CD-ROM drive).

 

Cc768175.box(en-us,TechNet.10).gif

In My Computer, double-click the CD-ROM drive, and verify that the drive and files are accessible by viewing directories and loading readable text files.
– Or –
At the MS-DOS command prompt, use the dir and type commands to verify that the drive and files are accessible by viewing directories and loading readable text files.

 

Cc768175.box(en-us,TechNet.10).gif

If the floppy disk drive is inaccessible, try reading a different disk. If that does not work, shut down and restart the computer. Check CMOS settings for the floppy disk drive using the hardware manufacturer's diagnostic routine (consult your hardware documentation).

 

Cc768175.box(en-us,TechNet.10).gif

If installing from a compact disc, verify that MSCDEX and the CD-ROM drivers are loaded and configured properly.

Setup is unable to find a valid boot partition. 

A valid MS-DOS partition must exist in order for Setup to install Windows 98. If Windows 98 Setup is unable to find a valid boot partition during installation, it displays an error message. If you receive an error message, there might be an actual partition error, but it is more likely that disk compression software or network components are mapping over the boot drive. This might occur if you are mapping a network drive to E, but E is the hidden host drive for your disk compression software, or you are using a LANtastic network and drive C is being mapped or shared.

To resolve the invalid partition error:
  • Verify the drive is not mapped over (or logically remapped). 

  • Verify a valid, active partition using Fdisk. If no valid partition exists, take appropriate drive or data recovery efforts. If no active partition exists, use Fdisk to mark an appropriate partition as active. 

  • Remove interfering drivers from the startup configuration files, and run Setup again.

  • If you are using disk compression software, ensure that none of your mapped network drive letters conflict with the host drive for disk compression. 

Setup finds insufficient disk space. 

If Setup does not find sufficient space to install Windows 98, check for space on the destination and boot drives, and if you are using compression, check actual free space.

Setup fails automated installation from Msbatch.inf. 

If the automated installation fails, check the following:

 

Cc768175.box(en-us,TechNet.10).gif

Verify the network connection if source files are on the network.

 

Cc768175.box(en-us,TechNet.10).gif

Check error messages, if any.

 

Cc768175.box(en-us,TechNet.10).gif

Check the Msbatch.inf file contents and syntax.

 

Cc768175.box(en-us,TechNet.10).gif

Check the network validation of user logon.

 

Cc768175.box(en-us,TechNet.10).gif

Check for enough memory.

 

Cc768175.box(en-us,TechNet.10).gif

Check for and remove unnecessary drivers and TSRs.

 

Cc768175.box(en-us,TechNet.10).gif

If using a logon script, verify that the script ran properly.

Troubleshooting Startup Errors

This section describes specific conditions that might interfere with starting a Windows 98 computer and how to fix them.

In general, for system startup problems, the first problem-solving method is to start Windows 98 in Safe Mode. For information about how to start in Safe Mode and use Bootlog.txt for troubleshooting, see Chapter 27, "General Troubleshooting."

Windows 98 stalls during the first restart after installation. 

Usually this occurs because of legacy hardware that was configured incorrectly before Windows 98 was installed. Remove settings for hardware services in Config.sys and Autoexec.bat. Also, ensure that any small computer system interface (SCSI) devices are terminated correctly. You might also need to disable the Industry Standard Architecture (ISA) enumerator. This software detects a new type of adapter that can be configured from the operating system. The detection sequence requires the ISA enumerator for I/O processes on some ports. Although every effort has been made to avoid ports commonly in use, you might have hardware that is also trying to use these I/O ports.

To disable the ISA enumerator
  • Remove the following line from the [386Enh] section of System.ini: 

device = ISAPNP.386

A bad or missing file error occurs on startup. 

If you receive a "Bad or missing filename" message when the system is starting (where filename might contain Himem.sys, Ifshlp.sys, and so on), do the following:

  • Check the syntax of the entry in Config.sys or other startup file. 

  • Verify the existence, location, version, and integrity of the file. 

If the file name to which the message refers is a device driver the computer needs for accessing the drive where Windows 98 is installed, move the device= line that contains the device driver to the beginning of Config.sys to allow access to the drive when Config.sys tries to load files from the Windows directory.

Windows 98 Has Damaged or Missing Core Files. 

When Windows 98 loads, it counts on key files being available and undamaged. If a system file is damaged or missing, it might prevent loading or normal operation. If Vmm32.vxd or other core files are missing or damaged, you might need to run Windows 98 Setup and select the Verify option in Safe Recovery to replace the files.

BIOS or a BIOS setting is incompatible. 

A ROM BIOS setting might prevent Windows 98 from installing or loading, because some computers have a feature that prevents applications from writing to the boot sector. This is usually in the form of anti-virus protection set through your computer's CMOS. If this is enabled, Windows 98 cannot complete the installation or cannot start properly.

If boot sector protection is enabled in the computer's BIOS, one of the following symptoms occurs:

  • Windows 98 Setup stalls. 

  • Windows 98 stalls while starting.

  • The anti-virus software prompts you to overwrite the boot sector. Choosing Yes might allow you to complete the Setup procedure, but Windows 98 stalls when it attempts to load. 

To correct this problem, disable the Boot Sector protection feature through your computer's CMOS, then reinstall Windows 98. For information about disabling this feature, consult your hardware documentation or service center.

A VxD error returns you to the command prompt. 

If a virtual device driver (VxD) is missing or damaged, Windows 98 displays an error message that indicates which VxD is involved. If the VxD is critical to the operation of Windows 98, then Windows 98 does not start and the screen displays the command prompt. You might need to run Windows 98 Setup and select Verify or Safe Recovery to replace the missing VxD.

You can selectively override a VxD that is included within Vmm32.vxd. If the same VxD is loaded twice, the second instance intercepts all the calls to that particular VxD. There are two ways to override this:

  • Copy the related VXD file into the Windows System\Vmm32 directory. 

  • Edit System.ini to add the entry device= filename**.vxd** in the [386enh] section.

You cannot use dual boot to run a previous operating system. 

To take advantage of the dual-boot support in Windows 98, you cannot install Windows 98 into an existing Windows 3*.x* directory, and the value BootMulti=1 must be defined in the Windows 98 version of Msdos.sys.

Versions of MS-DOS earlier than 5.0 do not support Windows 98 dual-boot functionality. To return to your previous operating system, you have to remove Windows 98 and reinstall your previous operating system, as described earlier in this chapter.

You can not dual boot between Windows95 and Windows 98 (unless you have a third-party boot manager installed).

A "Previous MS-DOS Files Not Found" message appears. 

When trying to dual-boot to the previous version of MS-DOS, you might receive an error message stating that your previous MS-DOS files were not found. It is probable that either the files are missing, or that your previous version of MS-DOS was not version 5.0 or later.

You must have MS-DOS 5.0 or later in order to start to a previous version of MS-DOS. Any version of MS-DOS earlier than 5.0 looks for the first three sectors of the Io.sys file in the first three sectors of the data area of the drive. In MS-DOS 5.0 or later, Io.sys is designed to be located outside the first three sectors of a drive's data area. In this situation, the only way to start to a version of MS-DOS prior to 5.0 is from a startup floppy disk.

Drivers, such as Dblspace.sys, that are loaded when you start the computer using the earlier version of MS-DOS might not be available.

Required real-mode drivers are missing or damaged. 

The previous operating system might have required certain real-mode drivers (compression, partitioning, hard disk drivers, and so on), and does not start correctly without them.

  • At system startup, press F8 and select Step-by-Step Confirmation to verify the correct loading of all specified drivers. 

  • Verify that any drivers required to support your hardware are all specified in the appropriate startup file. 

Windows 98 does not recognize a device. 

In some cases, Windows 98 is unable to recognize an installed device, and the device resources are unavailable to Windows 98. If Windows 98 does not recognize an installed device, remove it in Device Manager, and reinstall it by using the Add New Hardware option in Control Panel. You can also use Device Manager to check resource conflicts. For information, see Chapter 24, "Device Management." Or see the hardware conflict troubleshooting information in Help.

Installing drivers causes Windows 98 system startup to fail. 

If you try to install drivers for Windows 3*.x* from other vendors over Windows 98 (such as sound or video drivers), running the provided installation program can cause Windows 98 to fail to start or operate correctly.

To recover, when using a device that is supported by Windows 98
  1. Remove all entries in System.ini that were added by the installation software from another vendor. 

  2. Delete the device in Device Manager in the System properties, as described in Chapter 24, "Device Management." 

  3. Shut down and restart Windows 98. 

  4. Use the Add New Hardware option in Control Panel to reinstall the device by using the Windows 98 drivers. 

The wrong applications run after Windows 98 starts. 

  • In Windows Explorer, double-click the Windows Start Menu\Programs \StartUp directory, and then delete any items that you do not want to run when Windows 98 starts.

  • If the programs that are running do not appear in the Start Menu folder in Windows Explorer, run Registry Editor and find this key: 

HKey_Current_User \Software \Microsoft \Windows \CurrentVersion \Explorer \Shell Folders

The value of **Startup=** should be *Windows***\\Start Menu\\Program\\StartUp**, where *Windows* is the drive and directory containing the Windows 98 files. 

You experience interoperability problems with WinSock 2.0. 

If you experience interoperability problems with Windows Sockets 2.0 (WinSock 2.0) and are unable to work around the problem, uninstall WinSock 2.0 to restore your WinSock 1.1 configuration. To uninstall WinSock 2.0, go to Control Panel and double-click Add/Remove Programs. On the Install/Uninstall tab, click Restore WinSock 1.x configuration, and then click Add/Remove. Click Yes when prompted if you want to restore your original configuration.

For more information about WinSock 2.0, WinSock 1.1, and third-party TCP/IP stack issues, see "Windows Sockets 2.0 and Third-Party TCP/IP Stack Installations" later in this chapter.

Solving interoperability problems with WinSock 2.0. 

During setup, all WinSock 1.1 components are backed up. In the unlikely event that you experience interoperability problems with WinSock 2.0 and are unable to work around the problem, you can uninstall WinSock 2.0. This restores your WinSock 1.1 configuration.

When you uninstall WinSock 2.0 only the WinSock 2.0 related files are removed. The Windows 98 version of Microsoft TCP/IP and IPX/SPX stacks stay installed and will run with WinSock 1.1.

Note WinSock 1.1 is backed up only during the first time you install Windows 98. Subsequent installations of Windows 98 will not back up your WinSock configuration. If you uninstall WinSock 2.0 and want to restore it on your computer, you must reinstall Windows 98.

To uninstall WinSock 2.0 and restore WinSock 1.1
  1. In Control Panel, double-click Add/Remove Programs. 

  2. On the Install/Uninstall tab, click Restore WinSock 1.x configuration, then click Add/Remove

  3. Click Yes when prompted if you want to restore your original configuration. 

Windows Sockets 2.0 and Third-Party TCP/IP Stack Installations

If you have a third-party TCP/IP stack installed, neither Windows Sockets 2.0 (WinSock 2.0) nor the Microsoft TCP/IP stack can be installed.

When Windows 98 Setup attempts to install the Microsoft TCP/IP stack. However, if your original Windows 95 configuration included a third-party WinSock 1.1 stack, the Microsoft TCP/IP stack will not install, nor will WinSock 2.0, which is implemented as part of the TCP/IP stack.

If you want WinSock 2.0, you must remove the third-party TCP/IP stack, then reinstall Microsoft TCP/IP (not Windows 98).

If you want to install Windows Sockets 2.0 you need to do the following:

  1. Uninstall the third-party TCP/IP stack. 

  2. Reinstall Microsoft TCP/IP manually from the Network icon in Control Panel. 

Some third-party TCP/IP stacks cannot be installed after Windows 98 Setup due to conflicts with Windows Sockets 2.0, which is installed with Microsoft TCP/IP. If you want to use a third-party TCP/IP stack with Windows 98, you should install it before running Windows 98 Setup. In almost all cases, this ensures that your third-party stack is successfully upgraded. If you do not do install the stack before running Setup, you can try restoring Windows Sockets 1.1, then installing the third-party TCP/IP stack, however, this method does not always work.

For more information about the WinSock 2.0 APIs and for information on how to install the drivers, see the Microsoft Platform Developer's Kit.

Cc768175.spacer(en-us,TechNet.10).gif