From: MsgPost.v1.00@mtask.omahug.org (MsgPost v1.00)
Newsgroups: comp.os.os2.misc
Subject: [4 of 6] OS/2 Frequently Asked Questions Rel. 2.0e
Date: 02 Sep 92 07:53:02 CST
Reply-To: msgpost.v1.00@mtask.omahug.org
Organization: Multitasking Systems, Kansas City
Followup-To: comp.os.os2.misc

a DIP switch or jumper setting).  In rare cases it may be necessary to
switch third party VGA/SuperVGA adapters into 8-bit mode and/or disable
"autosense."  See Question 11 for more SuperVGA advice.

OS/2 is particularly sensitive to bad RAM or cache memory (often
reflected in TRAP 2 error messages).  Use a thorough RAM testing
utility, and try not to mix 9 chip and 3 chip SIMMs/SIPPs.

The HP DeskJet and DeskJet Plus printers work, without loss of
functionality, using the Epson EPL-6000, Epson EPL-7000, or LaserJet
Classic driver (with Fast System Fonts disabled).  As of this writing a
DeskJet 500C color driver (for OS/2-specific programs) is not yet
available.

Allow several minutes for OS/2 2.0 to build your desktop (and display
icons) at the end of installation -- take the Tutorial offered to you in
the meantime.  Select Shutdown and reboot once after installation
completes to ensure that DOS/Windows applications will operate properly.
Avail yourself of the "Start Here" icon, the other online help, and the
README file located in the root directory.  They will help in getting
started with the WPS and in properly configuring your system.

When installing over a beta version of OS/2 (except OS/2 2.0 level
6.177H, the Limited Availability release) be sure to reformat.

To install the OS/2 2.0 DOS/Windows upgrade DOS or OS/2 must already
reside on the hard disk.  If Diskette 1 is not write protected then the
installation program will record a file indicating that upgrade terms
have been satisfied and, in the future, will not require DOS or OS/2 on
the hard disk to install.

OS/2 uses the same diskette format as DOS, so use DISKCOPY to backup the
installation diskettes and verify that none have been corrupted.

Owners of IBM PS/2s should make sure that any applicable ECAs
(engineering changes) have been performed.

Try disconnecting any tape backup device if "Cannot find COUNTRY.SYS"
messages are encountered when booting OS/2.

Contact IBM for a fix to install OS/2 2.0 on certain Zeos notebooks.

An Always IN-2000 SCSI adapter with BIOS version 3.06A or 3.20 requires
an updated BIOS from the manufacturer.  A companion 8-pin serial PROM
chip may also need to be updated.  Contact Always at 818-597-9595.

------------------------------

(11)	Will OS/2 2.0 work with my SuperVGA adapter?

If you have a SuperVGA adapter, OS/2 2.0 should initially be installed
using the standard VGA driver.  Then consult the README file OS/2 copies
to your root directory for more information on SuperVGA support.

OS/2 2.0 comes with basic mode switching capabilities to handle
applications which utilize SuperVGA modes.  If OS/2 2.0 detects a
SuperVGA adapter it will list two SuperVGA support files, VSVGA.SYS and
BVHSVGA.DLL, in your CONFIG.SYS file.  (A replacement VSVGA.SYS file,
dated April 20, 1992, or later, fixes Tseng 4000 and TRAP E problems.  A
replacement BVHSVGA.DLL file, dated April 21, 1992, or later, fixes
installation problems involving Western Digital/Paradise PVGA1D chipset
adapters.  Both are available from shareware/freeware sources; see
Question 9.)

To enable this mode switching support you must start a DOS full screen
session, issue the command SVGA ON, EXIT, Shutdown, and reboot.  (In the
same DOS full screen session and prior to SVGA ON you may run utilities
which customize refresh rates.  The new refresh rates will take effect
after you reboot.  You may also wish to run such a utility from
AUTOEXEC.BAT.)  SVGA ON creates a text file called \OS2\SVGADATA.PMI
which describes your SuperVGA adapter to the system.  Then you may
install high resolution drivers.

Aside from DOS applications (which may require their own drivers), OS/2
2.0 requires up to three high resolution support files:

\OS2\DLL\DISPLAY.DLL                 Workplace Shell display driver
\OS2\MDOS\WINOS2\SYSTEM\VGA.DRV      Win-OS/2 full screen driver
\OS2\MDOS\WINOS2\SYSTEM\SWINVGA.DRV  Win-OS/2 "seamless" driver

You may replace any one of these individually for high resolution
operation in each given mode, but be sure to keep a backup copy of the
original file(s).  The "seamless" Win-OS/2 and WPS desktop driver files
must match (in terms of resolution and number of colors) if you wish to
run Windows programs "seamlessly."  Any suitable Windows SuperVGA driver
will work as a Win-OS/2 full screen driver, but be sure to use the
EXPAND utility (as described in README) when installing.

OS/2 1.3 SuperVGA drivers often serve, with some limitations, as WPS
desktop drivers.  Use the command DDINSTAL to replace DISPLAY.DLL.
Setting IOPL=YES in CONFIG.SYS may be required with a SuperVGA adapter.

As of this writing Trident, Orchid and STB (Tseng 4000 chipset), and ATI
(due to third party efforts) are the only SuperVGA vendors with OS/2 2.0
high resolution drivers, although several other manufacturers have
promised drivers.  When available they will be provided through
shareware/freeware sources (see Question 9).

Some SuperVGA adapters cause problems with DOS/Win-OS/2 sessions.  Try
turning VIDEO_ROM_EMULATION off, HW_ROM_TO_RAM on, and/or DOS_RMSIZE to
624 in DOS Settings.

If you have an ATI Ultra, Vantage, or other 8514/A hardware compatible
adapter, install OS/2 using the 8514/A driver.  For the Graphics Ultra
and Graphics Vantage change the line DEVICE=...VVGA.SYS to
DEVICE=...VSVGA.SYS in CONFIG.SYS; Shutdown and reboot.

IBM was unable to test all SuperVGA adapters, so if you are experiencing
problems report them through IBM's toll free support (800-237-5511 in
the U.S.) or to the adapter manufacturer.

If SuperVGA continues to cause problems the stock VGA driver may be used
(preventing DOS/Windows applications from using SuperVGA modes,
however).  In CONFIG.SYS change DEVICE=...VSVGA.SYS to ...VVGA.SYS and
SET VIO_VGA...(BVHVGA,BVHSVGA) to ...(BVHVGA).

OS/2 2.0's installation program has difficulty with certain Oak video
adapters.  Temporarily replace the video adapter to install OS/2, or
contact IBM for a patch.

------------------------------

(12)	Will OS/2 2.0 work with my printer?

OS/2 2.0 includes support for Hewlett-Packard LaserJets, DeskJets (see
Question 10), and PaintJets; IBM ExecJets, Proprinters, Quickwriters,
Quietwriters, Pageprinters, and Laserprinters; Epson dot matrix and
laser printers; Postscript devices; and other printers (e.g. Panasonic)
compatible with these families.  A variety of IBM and HP plotters is
also supported.

DOS/Windows printer drivers continue to work for DOS/Windows
applications.  OS/2 2.0 includes a large assortment of Windows printer
drivers for Win-OS/2.  If necessary install Windows printer drivers
using the Win-OS/2 Control Panel.  OS/2 2.0 and OS/2 1.3 printer drivers
are interchangeable, by and large.

If your printer is not compatible with one of the drivers supplied with
OS/2, check with the printer manufacturer first then with
shareware/freeware sources (see Question 9).  If you own an IBM printer,
check with the Lexmark BBS (606-232-5653).

------------------------------

(13)	How do I access HPFS partitions on my hard drive without booting
	from the hard drive?  I'm getting error messages now -- how do I
	"repair" my hard disk?

With IBM OS/2 2.0, insert the Installation Diskette, Shutdown (if
necessary), and reboot.  When prompted insert Diskette 1 and press
ENTER.  When prompted, press ESC.  You will be given an OS/2 command
line prompt.  From there you can make necessary changes to your hard
disk -- an OS/2 character mode text editor on diskette is handy for such
changes.  (Make sure you backup CONFIG.SYS before making any changes so
that you can easily revert to the old version should things go wrong.)

You may use this diskette boot method to run CHKDSK on your FAT or HPFS
partitions.  After you reach the command line, insert Diskette 2.  Do
not log to another drive.  Type CHKDSK X: /F to repair most kinds of
damage to your hard disk, replacing X with the appropriate drive letter.
(If you are checking a HPFS disk, use /F:3.)  OS/2 CHKDSK will also
remark your hard disk as accessible, if possible, should OS/2 "lock it
out" for some reason.

"Errors" may be reported by CHKDSK if OS/2 was booted from the hard
disk.  These "errors" are normal.  Since the hard drive is in use by
OS/2 itself (and files are open) CHKDSK is unable to accurately report
errors.

The best way to avoid the need to perform CHKDSK is to always select
Refresh then Shutdown.  Click on the Workplace Shell desktop background
using mouse button two to bring up the appropriate menu.  Also, avoid
manipulating OS/2-related files when using native DOS.  Finally, enable
autochecking for all your hard disk volumes.  For HPFS volumes use the
/AUTOCHECK parameter in the IFS=...HPFS line in your CONFIG.SYS.  For
FAT volumes use the AC parameter in the DISKCACHE line of your
CONFIG.SYS.  See the online Command Reference for details.

------------------------------

(14)	I can't install OS/2 2.0 from Drive B.  What's wrong?

IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless your
BIOS supports booting from Drive B), or across a network (contact IBM
for more information on network installation procedures).  If you have
the wrong disk size go back to your dealer and obtain the correct media.
Otherwise you could go inside your machine and swap floppy drive cable
connectors, use your system's setup utility to set the new CMOS
parameters, and then install OS/2 from the "new" Drive A.  Sometimes the
floppy drive cable connectors will not be the same.  If so you can
obtain an adapter plug.

You may also use IBM's new twin "bootstrap" diskette images, available
from shareware/freeware sources (see Question 9), to boot from a 5.25
inch Drive A and install using 3.5 inch OS/2 diskettes inserted into
Drive B.

------------------------------

(15)	Is there a Norton Utilities for OS/2?

Not yet, although Norton Desktop, Norton Utilities, and Norton Commander
all work under OS/2 2.0's DOS/Windows sessions (with limitations noted
in Question 4).  But the GammaTech Utilities should fill the role.

Newsgroups: comp.os.os2.misc