home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
osinmrqa.txt
< prev
next >
Wrap
Text File
|
1996-12-24
|
17KB
|
470 lines
OSINMRQA - OS/2 WARP 4.0 INSTALL FREQUENTLY ASKED QUESTIONS
10/09/96
=======================================================================
OS/2 Warp 4.0 Install Frequently Asked Questions
=======================================================================
Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------
DESCRIPTION
Questions and Answers on OS/2 Warp 4.0
RESOLUTION
How do I get my PCMCIA Token-Ring adapter to work with OS/2 Warp 4.0 on
an IBM ThinkPad 760CD?
The IBM ThinkPad 760CD uses most available interrupt values. To
get a PCMCIA Token-Ring adapter to work in a 760CD, set INTERRUPT=11
in the PROTOCOL.INI file. You can do this during or after
installation:
* During installation, from the Network Adapters and Protocols
window, click on Settings.
* After installation, use MPTS to reconfigure your adapter:
1. Select System Setup (the Toolbox) from the WarpCenter, then
select MPTS Network Adapters and Protocol Services
(or type MPTS, then press Enter, at an OS/2 command prompt).
2. Select Configure.
3. Select LAN adapters and Protocols, then Configure.
4. In the Adapter and Protocol Configuration window, under
Current Configuration, select the adapter, then press Edit.
5. Type 11 in the System Interrupt Level field.
6. After closing MPTS and saving your changes, shut down and restart
the system for the changes to take effect.
Note: For further assistance configuring an IBM ThinkPad, contact
either the IBM PC Company (1-800-772-2227) or the manufacturer
of the adapter.
How do I create product diskettes for OS/2 Warp 4.0?
To create product diskettes for OS/2 Warp 4 and its networking
products, do the following:
1. Insert the OS/2 Warp 4 CD-ROM in the CD-ROM drive.
2. At an OS/2 command prompt, type:
D:\PRODDSKS (where D: is the CD-ROM drive letter)
3. From the Main window, access the help file containing the
usage instructions.
What prior versions of OS/2 can OS/2 Warp 4.0 be installed over?
OS/2 Warp 4 can be installed over the following versions of OS/2:
* All OS/2 versions prior to OS/2 Warp 3.0
(OS/2 v. 2.01, OS/2 v. 2.1, OS/2 v. 2.11)
* OS/2 for Windows 2.1
* OS/2 Warp with WIN-OS/2 support (blue box)
* OS/2 Warp for Windows (red box)
* OS/2 Warp Connect
* OS/2 Warp Server Client
* OS/2 Warp Preload
In addition, OS/2 Warp 4 can be installed over the following
operating systems, providing either dual boot or dedicated
DOS/Windows session environments:
* DOS v. 3.1 or later, including PC DOS 7
* Microsoft Windows 3.1 and 3.11
* Microsoft Windows for Workgroups 3.1 and 3.11
* Microsoft Windows 95
You must first format the partition before installing over the
following systems; However, these operating systems may reside
on a separate partition:
* Any version of Microsoft Windows NT
* Any version of OS/2 for SMP
* OS/2 Warp Server 4.0
How do I create the three OS/2 Warp 4 Installation Startup Diskettes?
Note: If you plan to format the partition before installation,
create the Installation Startup Diskettes first. You must
have either a DOS or an OS/2 Operating System available to
use the CDINST command.
To create OS/2 Warp 4 Installation Diskettes:
1. Insert the OS/2 Warp 4 CD-ROM in the CD-ROM drive.
2. Open a command prompt session, and type:
D:\CDINST; then press Enter
(where D: is the CD-ROM drive letter)
3. Follow the directions on screen to make the three diskettes needed
to install OS/2 Warp 4. You will be prompted to label and create
Diskette #1, Diskette #2, and then the Install Diskette.
After the third diskette (Install Diskette) is created, you will
be prompted to press Enter to start the installation. Leave
the third diskette (Install Diskette) in the disk drive; it is
the first diskette of the installation.
I cannot run CHKDSK from the OS/2 Warp 4 Installation Diskettes when I
exit to a command prompt. How do I run CHKDSK?
CHKDSK.COM is no longer on Diskette #2. Make the Utility Diskettes
once the system is installed, or make Diskette #3 from the image on
the OS/2 Warp 4 CD-ROM: \OS2IMAGE\DISK_3.
To create Utility Diskettes:
1. Double click on the OS/2 System folder.
2. Double click on the System Setup folder.
3. Double click on Create Utility Diskettes.
4. Select the Drive Letter where Utility Diskettes will be created.
5. Click on Create.
6. Select the source drive and directory, for example: D:\OS2IMAGE
(Where D: is the CD-ROM drive letter).
7. Click on OK.
8. Follow the prompts to insert diskettes into Drive where Diskettes
are to be created.
9. Click on OK.
Note: You will need four (1.44 MB capacity) diskettes to make the
Utility Diskettes.
When installing OS/2 Warp 4.0, TME/10 NetFinity or
Remote Access Client did not install. How do I install them?
If you had a previous version of System View on your system, you
must remove it before OS/2 Warp 4 will allow you to install TME/10
NetFinity. If you had a previous version of LAN Distance on your
system, you must remove it before OS/2 Warp 4.0 will allow you to
install Remote Access Client.
Once System View or LAN Distance is removed, you can use Selective
Install to install TME/10 NetFinity or Remote Access Client.
1. Insert the OS/2 Warp 4 CD-ROM in the CD-ROM drive.
2. Double click on the OS/2 System folder.
3. Open the System Setup folder.
4. Open the Install/Remove folder.
5. Double click on Selective Install For Networking.
6. Choose Easy or Advanced Installation path. Click on Next.
7. Select Let Me Choose From All The Services. Click on Next.
8. Select the Networking Products that you wish to Install.
- File and Print Client
- NetWare Client
- Mobile Office Services
- System Management Client "TME/10 Netfinity"
- TCP/IP Services
- Remote Access Client
My installation of OS/2 Warp 4.0 fails during the first three diskettes.
What should I try next?
If you have problems with the first three diskettes during the
first phase of the installation process, do the following:
Insert the Installation Diskette and restart the system.
Do the following:
1. When the white band "OS/2" displays in the upper left
corner of your screen, press Alt+F1.
2. From the Selection window, select F6, disable detection of
your hardware.
If the above procedure does not work, do the following:
1. Insert the Installation Diskette and restart the system.
2. When the white band "OS/2" displays in the upper left corner,
press Alt+F2 to display the Loading Device Driver window.
This helps you identify the device driver that is attempting
to load.
3. Edit the CONFIG.SYS file and comment out the device driver
statement.
4. Restart the system.
Where can I find the latest device drivers for OS/2 Warp 4.0?
If support for your hardware is not included in OS/2 Warp 4, you will
need additional device drivers in order to start your OS/2 Warp 4
installation. For instance, your CD-ROM drive might be attached
to a hard disk controller that is not
supported. If you see a message during the first three installation
diskettes that your CD-ROM is not supported, this is generally
the reason.
IBM has supplied you with an additional CD-ROM labeled "Device
Driver Pak."
Once you are have OS/2 Warp 4 installed, you can access the following
World Wide Web site for a complete listing of over 2500 devices
that are supported by OS/2 Warp 4.
The web-site includes information about each compatible device by
category, and where to find the device driver. Information is
provided for over 400 device manufacturers.
The World Wide Web address is: www.austin.ibm.com/pspinfo/os2hw.html
Once you obtain the appropriate device driver, follow the instructions
for the type of device provided by your supplier.
For BASEDEV= device drivers add your device driver to Diskette #1:
1. Make a backup copy of Diskette #1.
2. If there is enough room on Diskette #1 copy the device driver file
to Diskette #1.
3. If there is not enough room on Diskette #1 and you are installing
to a non-microchannel system, erase the following files:
IBM2ADSK.ADD
IBM2SCSI.ADD
CLOCK02.SYS
SCREEN02.SYS
This should free an additional 55K.
4. Edit the CONFIG.SYS file on Diskette #1 to add the device
driver statement to the CONFIG.SYS as the FIRST LINE in the
CONFIG.SYS. For example:
BASEDEV=XXXXXXXX.YYY
where: XXXXXXXX.YYY is your device driver name
Add any necessary parameters as stated in the hardware device's
product documentation.
5. Add the following statement to the CONFIG.SYS file to ensure the
driver is copied throughout installation:
SET COPYFROMFLOPPY=1
6. Use the modified Diskette #1 when prompted for Diskette #1 during
the installation process.
7. If you lose connection to your hard disk or CD-ROM, during the
installation process or when restarting your system, make
sure that the device driver statement is in the CONFIG.SYS
and the device driver file has been copied to the
\OS2\BOOT\ directory.
For DEVICE= device drivers, add your device driver to Diskette #2:
1. Make a backup copy of Diskette #1 and Diskette #2.
2. Copy your device driver to Diskette #2.
3. Edit the CONFIG.SYS file on the Diskette #1 to add the device
driver statement to the CONFIG.SYS as the FIRST LINE in the
CONFIG.SYS file. For example:
DEVICE=XXXXXXXX.SYS
where: XXXXXXXX.SYS is your device driver name
4. Add any necessary parameters as stated in the hardware device's
product documentation.
5. Use the modified Diskette #1 and Diskette #2 when prompted during
installation process.
6. If you lose connection to your hard disk or CD-ROM, during the
installation process or when restarting your system, make
sure that the device driver statement is in the CONFIG.SYS
and the device driver file has been copied to the
\OS2\BOOT\ directory.
The progress indicator has stopped while installing OS/2 Warp 4.0
What should I do?
If the progress indicator stops moving during the installation process
and the CD-ROM and disk lights on your workstation indicate no install
activity, do the following:
1. Minimize the progress indicator by doing the following:
a. Press Alt+Shift+F3. The Minimize button appears in the
top right corner of your screen.
b. Press the Minimize button.
2. Open an OS/2 window and view the following files to help
you locate the problem. You might be able to solve the problem
yourself.
Each OS/2 Warp network product produces log files as they
are installed; they are stored in subdirectories in the following
path:
\IBMINST\LOGS\
The OS/2 Warp network product install status, including
which products were installed, is stored in the following file:
\IBMINST\LOGS\LOCINSTU\LOCAL.L2
The response files used for local install of OS/2 network
products are stored in:
\IBMINST\RSP\LOCAL\
The response files used for remote install of OS/2 network
products are stored in:
\IBMINST\RSP\REMOTE\
How do I turn off prerequisite checking, when installing OS/2 Warp 4.0
Networking features?
During installation, OS/2 Warp checks for sufficient disk space
(DASD), checks that all prerequisite software is installed, and
auto detects your network adapter. To disable this checking
during the install process, you can use the following three
switches:
* NoDASD: Turns off DASD checking. This enables you force a
product to be installed when the software thinks
there is not enough disk space.
Warning: If you disable DASD checking you might run out
of disk space during install and OS/2 Warp will
not operate properly.
* NoPrereq: Turns off prerequisite checking. This enables you to
force a product to be installed when the software thinks
that it cannot be installed.
* NoSniff: Turns off the network card detection. This may be
necessary if the detection logic hangs the system
while detecting adapters.
To set these switches, add one or more of the following environment
variables to the CONFIG.SYS file located on Diskette #1.
CONNECT_DASD=NO
CONNECT_PREREQ=NO
CONNECT_SNIFF=NO
For example, to install OS/2 Warp without checking DASD
for network products, do the following:
1. Add the following statement to the CONFIG.SYS file located on
Installation Diskette #1 (local or remote install diskette):
SET CONNECT_DASD=NO
2. Restart the installation process.
What are the hardware and memory requirements of VoiceType for OS/2
Warp 4.0?
VoiceType for OS/2 Warp (hereafter called VoiceType) requires
a minimum of a Pentium or equivalent processor and 24 MB of memory.
Performance will not be satisfactory with 486 or equivalent
processors.
VoiceType should work with any OS/2 Warp supported audio card that
provides 16 bit, 11 KHz sampling. The following sound cards were
tested with VoiceType:
Compaq Audio Business (AD1848)
CS4231/4248
CS4232/4236
ESS 688 * Battery Box
ESS 1688
ESS 1688 in IBM ThinkPads *
ESS 1788
ESS 1868 PnP
ESS 1888
IBM M-ACPA
Jazz 16 *
Mwave in Audiovation audiocard
Mwave in IBM ThinkPads *
ProAudio Spectrum
SoundBlaster 16
SoundBlaster 32
SoundBlaster AWE 32
SoundBlaster 16 PnP
SoundBlaster AWE 32 PnP
Vibra 16
Note: The audio devices marked with * require the optimal battery pack
in addition to the Andrea NC-50 microphone. The battery pack is
sold separately and can be ordered from Andrea Electronics.
To order contact Andrea Electronics.
If it appears that your audio card does not work with VoiceType,
make sure your audio card and microphone are connected
correctly and are working properly. To check them, use the Check
Installation utility in the VoiceType folder and the Digital Audio
Recorder in the Multimedia folder.
VoiceType works best with a close talking or a unidirectional
microphone. Andrea Electronics NC-50 and ANC-500 microphones were
tested with VoiceType.
Andrea Electronics for Models NC-50, ANC-500
USA and Canada:
Ordering .............: 1-800-707-5779
Technical Support ....: 1-800-442-7787
Outside USA and Canada: Ordering and Technical Support: 1-718-729-8500
World Wide Web address: http://www.andreaelectronics.com
Knowles Electronics for Models VR-3185, VR-3565
USA and Canada .......: 1-800-276-8516
Europe ...............: 44-1-444-87-27-84
Asia/Pacific .........: 886-2-9114931 Ext. 213
Japan ................: 81-3-34391151
Australia ............: 1-800-643766
warp4
______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.