home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
INSTAL.FAX
< prev
next >
Wrap
Text File
|
1994-12-11
|
19KB
|
511 lines
Many known Installation workarounds 8/12/94
OSINSTAL.FAX
OS/2 Installation Information
The following list explains various reported solutions on
on installing 2.1.
Please review the "Installation Guide" and the README.INS file
located on DISKETTE 3 prior to installing 2.1. There is a wealth
of information on configuration and installation troubleshooting.
If after reviewing the documentation you find that a specific
hardware device in your configuration is not supported, it is
recommended that you contact the supplier or manufacturer to
see if they supply the device specific driver.
==============================================================================
Problem: "SYSTEM CANNOT FIND THE FILE KBD01.SYS" ERROR MESSAGE
ON BOOT UP AFTER A SUCCESSFUL INSTALL
=========================================================================
On a system with a Micropolis SCSI 1 gig harddrive the
user is getting "system cannot find the file KBD01.SYS this
driver program or data file is not located in the default
path or the path specified for it not in the config.sys file.
Install this file in the correct directory or the appropriate
config.sys file statement." Upon checking the CONFIG.SYS the
correct statements are there and the file is located in the
correct place on the harddrive.
Workaround:
Disable the "Read ahead cache" on the Micropolis Drive.
There is a utility on the Micropolis BBS called UTIL.EXE
which will allow the user to disable the "Read ahead cache"
on the Micropolis 1 GB Drive Model 2112.
==============================================================================
Greater then 16 MB in MOD 80 will not install 2.X
=========================================================================
Fix:
The trick is to get the correct RAM init code installed on the
hard drive using the Reference Diskette. This requires a modified
FDDF.ADF file and EMO option diskette level 1.3. You can also remove
the EMO card for the installation if you have 4 meg on the planer.
==============================================================================
Installing OS/2 2.x on top of Lan Server 3.0 with HPFS386
=========================================================================
1) Use the BACKACC command to back up all access control
profiles on the drive containing OS/2 (e.g. BACKACC C:\ /S)
2) Use the NET command to delete all access control profiles
for the drivce containing OS/2
3) Reboot from the ServicePak diskettes and install the service
pack
4) On restart after installing the ServicePak, restart the server
and use RESTACC to restore the access control profiles
saved above (e.g. RESTACC C:\ /s)
5) At this point access control profiles should be reset as they
were before.
If the Service program still fails to find the SYSLEVEL files on
reboot, I would suggest making sure that all directories have the ARCHIVE attrib
ute bit removed before continuing. This can be done using the ATTRIB command.
==============================================================================
Hang with White screen after installation with no system activity:
========================================================================
* There is a fix available on Compuserve and the Raleigh BBS (919)
517-0001 for the following problems in a file called 21WPSF.ZIP.
1) White desktop after installing OS/2 2.1 over another version
of OS/2.
2) "shutdown complete" message is displayed underneath the
"shutting down please wait" message.
3) Mass duplication of template objects after creating a shadow.
If you have the white desktop with the environment noted above it is
recommended to get the 21WPSF.ZIP fix from Compuserve or the BBS.
If however you do not have access to a modem the following workarounds
have had a high success rate.
1) Do CHKDSK x: /f (for FAT )
CHKDSK x: /f:3 (for HPFS) on OS/2 Partition from OS/2
See Page 137 in the "Installation Guide for instructions on
on how to running CHKDSK.
2) Check the OS/2 CONFIG.SYS file on the root directory for the
following 2 statements. If you have more than one set of these
two statements, REM out the first set in the config.sys file.
SET USER_INI=C:\OS2\xxxxx.INI
SET SYSTEM_INI=C:\OS2\xxxxxx.INI
If you do have two sets, EDIT the CONFIG.SYS with any EDITOR
by either copying the file to a diskette and editing on another
machine or boot up with a DOS diskette and Run EDIT or EDLIN
to "REM" out the duplicate set of SETUSER and SETSYSTEM
lines. (e.g. REM USER_INI=C:\OS2\xxxxx.INI)
If the preceding instructions did not fix the problem continue....
3) Try setting the video card to 8 bits and moving the video
card to an 8-bit slot, also disable the auto-switching
capability of the card if possible.
Contact the manufacturer or hardware technical literature for
instructions if necessary.
4) If ATI 8514 Ultra or Graphics Ultra locks with white screen on otup.
boot, the older ATI ROM chips return an incorrect monitor ID when
queried by OS/2. Call ATI at 416-882-2626 to
obtain an update. Remember, these boards MUST be set up as
an 8514 PRIMARY display and the statement
DEVICE=C:\OS2\MDOS\VVGA.SYS
MUST be changed to
DEVICE=\OS2\MDOS\VSVGA.SYS
5) Remake desktop.
The following steps will allow the customer to delete and re-
create the desktop. You DO lose CUSTOMIZATION!! This will
fix problems caused by corrupted Extended Attributes on the
desktop, such as the common problem with Shutdown and Lockup
missing from the desktop popup menu:
1. Restart your computer using the OS/2 Installation Diskette,
then insert Diskette 1.
2. Press Esc to access an OS/2 full screen; then change to the
\OS2 directory.
3. Type:
MAKEINI OS2.INI INI.RC (and press enter)
MAKEINI OS2SYS.INI INISYS.RC (and press enter)
4. Delete the hidden file WP ROOT. SF in the startable partition
Type:
For FAT system : DEL WP?ROOT.?SF and press enter
or
For HPFS system : DEL "WP ROOT. SF" and press enter
6) Delete the desktop.
CD OS!2_2.0_D (DESKTOP for OS/2 2.1) and delete this directory &
all subdirectories under it. (FAT)
or
"OS!2 2.0 DESKTOP" and delete this directory and all sub-
directories under it. (HPFS)
NOTE: If Makeini.exe has been run before, or Alt-F1 was ed befo
used, other DESKTOPS may have been created.
Delete all desktops. sktops.
(e.g. OS!2_21.0_D is another desktop that can be
deleted.
==============================================================================
TRAP0002 on IBM 8590, 8595
=========================================================================
If you are experiencing problems with a Model 90 or 95,
ensure the system is at the latest engineering change
(EC) level. Call 1-800-IBM-SERV if the following conditions
are met.
If the Model 90 or 95 is a 33 MHz system and you are having
intermittent difficulty identifying memory parity errors such
as TRAP 0002, forcing you to restart the system, then
ECA053 might apply. If the microprocessor card has part
number 84F9356, contact IBM representative to assist you
with a replacement.
If the Model 90 is experiencing intermittent memory errors,
ECA084 might apply if the part number of memory riser
card is N33F4905 or 84F9356. Contact 1-800-IBM-SERV. ve
For both the Model 90 and 95, you must ensure that the he
single inline memory modules match in pairs. This means s
that each pair of single inline memory modules, as described in
system technical reference manual, must be matched in memory size
and speed. Mixing these modules can cause some computers to
report memory errors.
==============================================================================
SYS02025 and SYS02027 on OEM with PHOENIX bios 1.03 on OS/2 2.1
Install Diskette.
========================================================================
Work around:
1) Make backup copy of OS/2 2.1 Install diskette.
2) Del OS2LDR /* from backup diskette */
Del OS2BOOT /* from backup diskette */
3) Copy OS2LDR /* from original to backup */
Copy OS2BOOT /* from original to backup */
The SYS02025 and SYS02027 errors have also been found when the user
swaps the floppy drive cables without updating CMOS. Updating CMOS
corrects the problem (3.5 and 5.25 cable swap).
Note that there is a tool available on the Raleigh BBS and Compuserve
that allows you to install OS/2 2.X from the B drive, when the B drive
is 3.5 and and A drive is 5.25 and the diskettes are 3.5. This utility
is called INST21L (if you have blue labels on your disks) or INST21M
(if you have salmon label on your disks).
=======================================================================
If you have an external modem, please turn it off during install.
=======================================================================
==============================================================
MEMORY RELATED PROBLEMS
==============================================================
Common Symptom: Trap 2, Trap 6 or other Trap at
60000x:9084.
These problems are caused by:
Mismatched memory simms (from different manufactures) -
this is especially common if you recently added memory to
your system, or if it was assembled from parts (not a
recognized brand of clone).
Mismatched memory simms (different classes) 1x9 simms
cannot be mixed with 1x3 simms. Also, the 1x9 simms seem
to be more reliable than the 1x3 simms.
Slow memories on 486 machines (you may need 60 or 70ns
memories).
Cache problems.
Solution: Replace memory and/or tune wait states, disable
cache during install, turn turbo switch off.
==============================================================
SCSI PROBLEMS
==============================================================
These problems are caused by:
incorrect BIOS
need OS/2 compatible driver from manufacturer
incorrect identification of adapter by OS/2
mismatched settings of SYNCH/ASYNCH mode for SCSI
controller, hard drive, causes slow drives, misssing icons
Solution: Update BIOS, get driver from manufacturer, change
settings.
Known problems:
AMI SCSI - slow, noisy disk - ATBUS workaround - get ATBUS FAX
FUTURE DOMAIN 16XX SCSI controller - hang on LOGO screen
after reboot following good install - check for interrupt
conflict
Always Technology SCSI - BIOS upgrade -
Bernoulli Boxes - See IOMEGA Support
Colorado Memories Tape Drive - fix available from Colorado -
PROCOMM+ SCSI disk adapters (Microchannel) - Contact PROCOMM
Early versions of IBM 16-bit SCSI adapters - update
microcode
Removable media support - Bernoulli (IOMEGA), and SyQuest -
support is limited, treats them like big floppies - see
readme
All Adaptec adapters - SCSI hard disks must be configured as
SCSI target ID 0 or 1 to be able to start up from that hard
disk - see readme
BIOS will not recognize - configure as non startup drive -
see readme
Adaptec AHA-174x adapter with IBM WDS-3180 80MB SCSI, IBM
WDS-3160 160MB SCSI - Adapter will not recognize in
'STANDARD MODE' (AHA-154x emulation). Adapter should be
configured in 'ENHANCED MODE' - see readme
Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0,
and Future Domain TMC-1660/1670/1680 w/BIOS revision level
2.0 can cause "Disk Read Error" on installation disk for
model 35 and 40 - need BIOS upgrade - see readme
AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are
incorrectly recognized as Adaptec adapters - see readme for
workaround
Always IN2000 SCSI adapter - causes Internal Processing
Error - need BIOS upgrade VCN1-02
Quantam Plus Hardcard - need EPROM upgrade - see readme for
more info
SUMO SCSI adapters - Contact manufacturer
====================================================================
FDISK PROBLEMS
====================================================================
Some common problems:
selections to dump or more disk.
Insufficient disk space for swapper file growth on low
memory systems - suggest install selections to dump or more
disk.
Incorrect setup information in CMOS memory for hard drive
being used - see if it works under another operating
system.
Slow, noisy disk or FDISK errors (especially on RLL, MFM, or
ESDI disks) - ATBUS FAX
Nonstandard or out of date BIOS (especially with IDE drives)
- disk inaccessible or FDISK errors. Look for Phoenix or
AMI standard BIOS and check dates - SEE BIOS FAX
Incorrect identification of adapter by OS/2
Trying to install on a drive which was compressed using a
stacker utility - suggest uncompressing the disk or
reformatting.
Trying to install over a Beta version of OS/2 2.0 (1.3 is
OK) - reformat first.
Trying to install HPFS with less than 6M of memory - not supported
Trying to install on less than 4M (user may think he has
4M, but some cache arrangements or ROM to RAM remapping can
steal some) - try to disable these features in CMOS setup.
Disk corruption/failure (it won't even support DOS) - try
high and low level format or get new drive.
Quantum IDE hard disks require a free ROM update from Quantum.
Install hangs on Disk 1 - this may be caused by having disk
caching enabled on the drive controller card - try
disabling it - also try turning off the controller's
asynchronous memory refresh capabilities if applicable.
already reside on the hard disk.
IBM OS/2 2.X can only be installed from Drive A, like DOS
(unless you swap drive cables/change CMOS setup to fool
system)
Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT
files can cause problems and is not recommended - recover
using original config.sys in OS2 SYSTEM.
If you have Windows 3.1 installed on your system do not
migrate your Windows desktop.
If you are using the IBMINT13.I13 driver to access an MFM,
RLL, or ESDI hard drive, and the hard drive has more than
1024 cylinders, be certain your hard disk adapter's sector
translation mode is enabled.
COUNTRY.SYS problems are usually a symptom of a disk which
is not recognized by OS/2, and may be caused by the
following:
Conflict with another device attached to the same controller
card. Try removing anthing like a tape backup, which may be
the cause of the conflict.
On a P70, you need ECA068, contact IBM CE.
===============================================================
BIOS PROBLEMS
===============================================================
Many of the problems above have old bios as their root
cause, so there is a lot of overlap between this and other
problems - see details on how to check dates in MORETIP or
info APAR #II06078
Some common causes:
- Wrong keyboard BIOS
- Outdated video adapter BIOS
In many cases these problems stem from old standard BIOS
which is easily replaced, but in some cases, customer has
old "custom" BIOS (manufacturer has included functionality
specific to the motherboard on the BIOS). In this case
there may be no upgrade path and the motherboard may need
to be replaced.
For more detailed information on BIOS, see INFO APAR II06082
===================================================================
ADAPTER CONFLICT PROBLEMS
===================================================================
On ISA machines, interrupt conflicts and memory mapping
conflicts can cause a variety of problems. For example,
many SuperVGA adapters use large chunks of upper memory,
and many hard disk adapters have on board ROMs which can be
mapped into this area as well. Also, Soundblaster boards
use INT 7, which conflicts with many printers. Adapters
must cooperate in their use of memory and interrupts and
must not share address space or interrupts. Callers should
be encouraged to check interrupt level settings on their
boards. Also try removing cards that are not needed during
install. Sometimes you will get a Trap D at 160:FFFxxxxx.
==================================================================
VIDEO ADAPTER PROBLEMS
==================================================================
Install problems resulting from video adapter conflicts
typically occur on disk 6 or later. This is when the
graphical install icons come up, and it is the first place
where more complex calls are made to the video BIOS. One
notable exception is the Oak video card. Try another video
card during install, or try the card in an 8 bit slot
during install. Try some different adapter DIP switch
settings listed in your adapter manual. Make sure video
card is in VGA mode with auto-sense turned off.
Some specific problems:
If you have a super VGA adapter, install should always be
done as VGA. If you have an ATI Ultra, Vantage, or other
8514/A hardware compatible ada ter, use 8514/A driver for
install.
C0000005 is displayed on the screen during install (e.g.
Western digital PVGA1D) - need fixed version of BVHSVGA.DLL
Hang on Disk1 right after LOGO screen caused by OAK video
card BIOS problem. Workaround is to patch loader file -
see Install Adapter APAR
video card is in VGA mode with auto-sense turned off.
White screen after installation with no system activity -
Try setting the video card to 8 bits and moving the video
card to an 8-bit slot, also disable the auto-switching
capability of the card if possible.
Out of Synch/Install problems - caused by problems
addressing card in 16-bit mode, switch to 8 bit mode (using
jumpers or dip switches on board) and put in 8 bit slot.
Install Adapter APAR
Some super VGA cards have ROMs with conflicting addresses
for some hard disks.
====================================================================
OTHER PROBLEMS
====================================================================
Failures very early on install disk (especially Zeos
notebooks) - try applying patch to sysinstx.com in Install
Other APAR
Dual Boot feature does not allow boot back to OS/2 from DOS
- there may be a disk cacheing utility or a TSR which
blocks this. Request DUALBOOT FAX
12/31/99