|
Miscellaneous Setup Issues |
Switches and Meaning:
/?
Provides help for syntax and use of setup command-line switches.
/C
Instructs Windows 95 Setup not to load the SmartDrive disk cache.
/d
Instructs Windows 95 Setup not to use the existing version of Windows
for the early phases of Setup. Use this switch if you have problems starting
Setup that might be due to missing or damaged supporting files for Windows.
/id
Instructs Windows 95 Setup not to check for the minimum disk space
required to install Windows 95.
/ih
Runs ScanDisk in the foreground so that you can see the results. Use
this switch if the system stalls during the ScanDisk check or if an error
results.
/iL
Loads the Logitech mouse driver. Use this option if you have a Logitech
Series C mouse.
/iq
Instructs Windows 95 Setup not to perform the ScanDisk quick check
when running Setup from MS-DOS. You probably want to use this switch if
you use compression software other than DriveSpace or DoubleSpace.
/is
Instructs Windows 95 Setup not to run the ScanDisk quick check when
starting Setup from Windows. You probably want to use this switch if you
use compression software other than DriveSpace or DoubleSpace.
/nostart
Instructs Windows 95 Setup to copy a minimal installation of the required
Windows 3.x DLLs used by Windows 95 Setup, and then to exit to MS-DOS without
installing Windows 95.
script_filename
Instructs Windows 95 Setup to use settings in the specified script
to install Windows 95 automatically; for example, setup msbatch.inf specifies
that Setup should use the settings in MSBATCH.INF. For more information,
see Custom, Automated, and Push Installations.
/t:tempdir
Specifies the directory where Setup is to copy its temporary files.
This directory must already exist, but any existing files in the directory
will be deleted.
v - This switch enables Verify Only mode. Detection has two stages:
1. Verify existing devices in the registry.
2. Detect new devices.
This switch tells Detection to perform only stage 1. This switch is used by the PCMCIA Wizard to verify legacy devices in the registry.
The default is disabled.
Example: setup /p v
In information technology, legacy applications and data are those that have been inherited from languages, platforms, and techniques earlier than current technology. Most enterprises who use computers have legacy applications and databases that serve critical business needs. Typically, the challenge is to keep the legacy application running while converting it to newer, more efficient code that makes use of new technology and programmer skills. In the past, much programming has been written for specific manufacturers' operating systems. Currently, many companies are migrating their legacy applications to new programming languages and operating systems that follow open or standard programming interfaces. Theoretically, this will make it easier in the future to update applications without having to rewrite them entirely and will allow a company to use its applications on any manufacturer's operating system.
In addition to moving to new languages, enterprises are redistributing
the locations of applications and data. In general, legacy applications
have to continue to run on the platforms they were developed for. Typically,
new development environments account for the need to continue to support
legacy applications and data. With many new tools, legacy databases can
be accessed by newer programs.
You should consider the following questions before proceeding with Windows 95 Setup on an individual computer:
Is the installation drive checked and defragmented?
Check the Windows 95 README file and SETUP.TXT on the installation disks for any notes related to your computer hardware. If any specific computer component is not supported, Windows 95 selects a generic driver or uses the existing driver installed on the computer. If you install support manually for a hardware component that doesn’t appear in the installation dialog boxes, select the model that your hardware can emulate or that is of the closest type. (All supported hardware components are listed when you run the Add New Hardware wizard, as described in Devices.)
Do the computer components meet the minimum requirements?
Read Installation Requirements, and check your computer hardware and software components. Verify that all components meet the minimum requirements.
Are all unnecessary TSRs and time-out features disabled?
Disable all TSRs and device drivers loaded in CONFIG.SYS or AUTOEXEC.BAT (or in any batch files called from AUTOEXEC.BAT), except those required for partition or hard disk control, network drivers, or any driver required for operation of a device such as video, CD-ROM, and so on. Some portable computers (such as the IBM ThinkPad®) automatically suspend operation after a specified time-out interval, or when the cover is closed. You should disable this feature while Windows 95 Setup is running.
Is the installation drive checked and defragmented?
Windows 95 Setup automatically runs ScanDisk to check the integrity of the drive where Windows 95 is to be installed. However, you might want to check and defragment the hard disk drive thoroughly before beginning Setup, using your usual defragmentation software. Also, be sure to defragment all compressed drives, because a highly fragmented compressed drive reports more available disk space than is available. If you use disk compression software other than DriveSpace or DoubleSpace, be sure to run the disk-checking utility provided with your compression software. For information, see the documentation provided with the compression software.
When you run Windows 95 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 Setup Command-Line Switches) found in your Reskit. 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.
Are all key system files backed up?
Any time you upgrade an operating system, backing up critical business or personal data is a prudent precaution. The files you should back up before installing Windows 95 include the following:
All initialization (.INI) files in the Windows directory
All Registry data (.DAT) files in the Windows directory
All password (.PWL) files in the Windows directory
All Program Manager group (.GRP) files in the Windows directory
All critical real-mode drivers specified in CONFIG.SYS and AUTOEXEC.BAT
CONFIG.SYS and AUTOEXEC.BAT in the root directory
Proprietary network configuration files and login scripts
Does the networking software work correctly?
Make sure that the network software is running correctly before you
start Windows 95 Setup. Windows 95 uses the settings from the existing
network configuration to set up the new configuration. Check the Windows
95 README file for additional notes related to your networking software.
Windows 95 Setup creates several log files: BOOTLOG.TXT, DETLOG.TXT, NETLOG.TXT, and SETUPLOG.TXT, plus DETCRASH.LOG if Setup fails. The following sections describe these files. Basically, there are three points at which the computer might stop or stall during Windows 95 Setup: before, during, or after hardware detection.
If Setup fails before hardware detection, Windows 95 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 in your Reskit.
Sometimes the detection process causes some devices to quit working (such as a CD-ROM drive or a network connection). 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.