From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: OS/2 Frequently Asked Questions Rel. 2.0i (2 of 2)
Followup-To: comp.os.os2.misc
Supersedes: <1992Dec2.033717.17753@midway.uchicago.edu>
Reply-To: sip1@midway.uchicago.edu
Organization: University of Chicago Computing Organizations
Date: Sat, 9 Jan 1993 06:06:56 GMT
Expires: Mon, 15 Mar 1993 23:59:59 GMT

Archive-name: os2-faq/user/part2
Version: 2.0i

[Continued from Part 1]

/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.

Several utilities (including SE20BOOT), available from sources listed in 
Question 8, can create a single, bootable OS/2 diskette (as a 
convenience).  Preloaded versions of OS/2 2.0 can create a bootable 
diskette pair from the Welcome folder.  (This step, along with a full 
BACKUP after a diskette boot, should be performed immediately upon 
receipt of any IBM preloaded OS/2 2.0 system.)

IBM has released a patch (UHPFS) which remedies "CPS: Extent" errors on 
HPFS volumes.  This patch is available from sources listed in Question 
8.

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

(13)	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 (see "Remote 
Installation and Maintenance," IBM Pub. No. GG24-3780-00).  If you have 
the wrong disk size go back to your dealer and obtain the correct media.  
Otherwise you could open 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 twin "bootstrap" diskette images, available from 
sources listed in Question 8, to boot from a 5.25 inch Drive A and 
install using 3.5 inch OS/2 diskettes inserted into Drive B.  However, 
this procedure is not recommended.

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

(14)	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).  Also, Norton Commander is now available for OS/2 2.0.

However, the GammaTech Utilities should fill the role.  Contact their 
publisher at 405-359-1219.  Note that OS/2 2.0 has a built-in UnDelete 
utility (see the README file or online help), and HPFS is resistant to 
fragmentation (see Question 17).

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

(15)	Sometimes OS/2 2.0 will freeze when I run an application.  What do
	I do?

Before rebooting with CTRL-ALT-DEL, try CTRL-ESC.  Do not hit additional 
keys, do not move the mouse.  Wait up to a minute.  Either the Window 
List or an error message should pop up.  You may close the offending 
application at that point; allow some time for it to close.  (Try ALT-
ESC if you have disabled CTRL-ESC in that application's DOS Settings.)  
Note that the WPS can recycle, independent of running applications, if 
it crashes.

If the system is badly disabled, sometimes pressing CTRL-ALT-NUMLOCK 
twice will result in a prompt to create a dump diskette.  You may do so 
(the online Command Reference describes dump diskettes), or at that 
point you may reboot with CTRL-ALT-DEL.

To prevent applications from automatically restarting, see Question 28.  
To restore the desktop to "factory defaults," use ALT-F1 when OS/2 2.0 
starts.  See the README file in your OS/2 root directory for details.

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

(16)	How can I get answers to my OS/2 questions?

If your question is not answered in this List, post a note to the 
appropriate Usenet conference: comp.os.os2.apps carries discussions 
related to finding or using any application running under OS/2, 
comp.os.os2.networking looks at networking issues, comp.os.os2.advocacy 
deals with opinions and speculation, comp.os.os2.programmer addresses 
anything related to OS/2 programming, and comp.os.os2.misc is for any 
other OS/2-related discussion.  These groups are watched closely by OS/2 
experts from IBM.  Also, comp.lang.rexx discusses REXX programming.  A 
LISTSERVer distributes its own OS/2 conference by mail; send a single 
line message with the word HELP to listserv@cc1.kuleuven.ac.be for full 
instructions; or send the same message to listserv@frors12.circe.fr for 
information on an unedited mailing list.  To subscribe to the Multimedia 
Presentation Manager/2 mailing list, send a single line message with the 
phrase SUBSCRIBE MMOS2-L to mail-server@knex.gwinnett.com.

Your local FidoNet BBS may carry OS/2 echo conferences and/or OS2NET.  
If not, ask your system operator to join them.  CompuServe ("FIND OS/2") 
and Prodigy are also excellent resources.

The IBM NSC BBS's message areas, product database, and PS/2 Assistant 
file(s) are invaluable resources.  Information on the new OS/2 BBS is 
included in the OS/2 2.0 package.  In the U.S. IBM has toll free 
technical support (800-237-5511), an OS/2 Hotline (general information, 
orders, upgrades, 800-3-IBM-OS2), the HelpWare Center (800-PS2-2227), a 
software order line (800-IBM-CALL), two FAX information services (800-
IBM-4FAX and 800-IBM-3395), and an educational inquiries line (800-222-
7257).  In Canada call IBM Personal Systems Software at 800-465-1234.

OS/2 2.0 developers should contact the IBM Developer Assistance Program 
(407-982-6408); membership is free.  (You may also join on CompuServe 
with GO OS2DAP.)  The OS/2 Professional Developer's Kit CD-ROM, 
containing a wide selection of development tools and code, and the OS/2 
2.1 Beta CD-ROM are both available from IBM (800-3-IBM-OS2 to order in 
the U.S. for $15 each; in Canada, call 800-465-1234; in Australia, call 
Rohaini Cain or Mike Voris at 13-2426 ext. 7684; elsewhere, contact your 
local IBM office).

IBM offers classes worldwide to help in using and programming OS/2 2.0; 
call your local IBM branch office (or the OS/2 Hotline) for more 
information.  OS/2 has its own magazines as well: OS/2 Developer 
Magazine (800-WANT-OS2), OS/2 Monthly (72550.2440@compuserve.com or 800-
365-2642), Inside OS/2 (502-491-1900), OS/2 Professional (???-???-????), 
and OS/2 Newsletter (714-495-3757).

OS/2 2.0 books include The Design of OS/2 (Addison-Wesley, 617-944-
3700), 10-Minute Guide to OS/2 (Alpha, 317-573-2634), OS/2: User's Guide 
and Tutorial (Computer Information Assoc., 708-766-4677), Inside OS/2 
(New Riders, 317-571-3259), OS/2 Inside and Out (Osborne/McGraw-Hill, 
800-227-0900), OS/2 Application and Development Tools (Premier, 203-378-
6200), Using OS/2 2.0 (Que, 317-573-2500), OS/2 2.0 Complete (Abacus, 
616-698-0330), and various titles from Van Nostrand Reinhold (212-254-
3232) and QED (800-343-4848).

IBM's OS/2 "redbooks" (power user guides) are IBM No. GBOF-2254.  (To 
order IBM publications phone your local IBM office and ask for the 
Librarian or call 800-7654-IBM.)  The redbooks are also available in 
electronic form from sources listed in Question 8.

Any of the regular DOS or Windows resources (e.g. books, magazines, 
shareware/freeware sources) will be useful since both environments come 
with OS/2 2.0.

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

(17)	Why should I use HPFS?  What does it offer me?  Does it work with
	DOS?

HPFS offers long file names (up to 254 characters including the path, 
greatly exceeding the "8 dot 3" limit in DOS's FAT file system), 
contiguous storage of extended attributes (without the EA DATA. SF file 
used by FAT), resistance to file fragmentation, improved media error 
handling, smaller cluster size, support for larger file storage devices 
(up to 512 GB), and speedier disk operation, particularly on large hard 
disks, on systems with more than 6 MB of RAM.  HPFS is not case 
sensitive, although it does preserve case in file names.

However, HPFS is not currently supported on removeable media, although 
some programs (e.g. BACKUP) preserve long file names on such FAT disks.  
Also, native mode DOS cannot access a HPFS partition.  However, 
DOS/Windows sessions running under OS/2 can use all files that conform 
to the "8 dot 3" naming conventions, even if they are stored on HPFS 
volumes.

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

(18)	I'm a Unix wizard.  How do I make OS/2 resemble Unix?

A great number of GNU and Unix utilities have been ported to OS/2 native 
mode and are available from sources listed in Question 8.  A uucp 
package, UUPC/Extended, is available via anonymous ftp from 
sun.soe.clarkson.edu, directory pub/uupc; mail help@kew.com with 
questions.

In addition, the Hamilton C Shell is available from Hamilton Labs (508-
358-5715 or mail 3890321@mcimail.com).  The Thompson Toolkit, a Bourne-
like shell, and awk are published by Thompson Automation (206-224-1639).  
MKS (519-884-2251 or mail pat@mks.com) publishes a number of standard 
Unix utilities for OS/2.  For OS/2-specific X Windows server support, 
IBM provides an optional package available with its TCP/IP 1.2.1 for 
OS/2.  The TCP/IP 1.2.1 base package includes a news reader as a sample 
application.

DOS and Windows based utilities and aids still work fine under OS/2 2.0.

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

(19)	I prefer Windows.  How do I make OS/2 2.0 resemble Windows (or
	OS/2 1.3)?

Spend some time with the WPS first.  Browse the online Tutorial, Master 
Help Index, and Start Here facilties.  Consult the Unofficial Guide to 
the Workplace Shell, available from sources listed in Question 8.

If you still prefer Windows-like behavior, follow the instructions 
beginning on p. 29 in the "Migrating to the OS/2 Workplace Shell" 
booklet.

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

(20)	I would like to set up an OS/2 BBS.  What is available?

OS/2 is an excellent environment for BBS operation (even using 
DOS/Windows software), including large multiline facilities.  Related 
software will enable FidoNet capabilities, gateways to Usenet/UUCP, 
nodelist processing, additional file transfer protocols, and more.

Five popular OS/2-specific BBSes are Maximus and Simplex (available from 
sources listed in Question 8), Omega Point/2 (BBS 404-564-1961), Magnum 
(818-706-9800, BBS 818-706-9805), and Multi-Net (503-883-8099, BBS 503-
883-8197).

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

(21)	Can I use COM3 and COM4 in OS/2?

COM3 and COM4 are supported on most PS/2s without any additional effort.  
On (E)ISA machines, some additions are required to CONFIG.SYS.  Using a 
text editor, include "(port number, base address, interrupt number)" 
parameters next to the COM.SYS and VCOM.SYS filenames.  One example:
	DEVICE=C:\OS2\COM.SYS (3,3E8,5) (4,2E8,10)
	DEVICE=C:\OS2\MDOS\VCOM.SYS (3,3E8,5) (4,2E8,10)
Parameters for COM1 and COM2 need not be included (unless they are 
somehow nonstandard).  OS/2 must end up with sequentially numbered 
logical COM ports, if possible.  For example, if (physical) port two is 
not installed but port three or port four is installed start numbering 
using (2,...) in the DEVICE lines.  If these efforts fail, try IBM's 
patched COM drivers or the SIO drivers (available from sources listed in 
Question 8).

Note that AT bus COM ports cannot be used at the same time if they share 
interrupts because of bus design limitations (cf. "Under the Hood: How 
Interrupts Work," Byte, February, 1992).  An adapter which provides more 
flexibility in interrupt selection (e.g. the 16-bit model from Boca 
Research) may prove helpful.  Also, PolyCom, a replacement driver 
available from sources listed in Question 8, supports up to eight ports 
with the right hardware.

"Smart" (coprocessor controlled) multiport communication adapters should 
be used when installing more than four ports.  Such an adapter will work 
with OS/2 if the manufacturer has written an appropriate driver.  
Examples include IBM's ARTIC products, Digiboard (612-943-9020), 
Stargate (216-349-1860), Arnet (615-834-8000), Computone (404-475-2725), 
Comtrol (612-631-7654), CTC Systems (415-966-1688), Equinox (305-255-
3500), I-Concepts (214-956-7770), Specialix (408-378-7919), and Stallion 
(408-395-5775) adapters.

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

(22)	How do I start a background process from the OS/2 command line?

Look up the START and DETACH commands in the online Command Reference.

If you wish to start a DOS session with nondefault settings, use a 
utility such as STARTD.  If you wish to start an OS/2 session from a DOS 
session, try OS2EXEC.  Both (and several others) are available from 
sources listed in Question 8.

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

(23)	What are CSDs, how do I tell which I have, and where do I get
	them?

CSDs are Corrective Service Diskettes, or bug fixes (Service Paks), 
periodically issued by IBM.  The OS/2 CSD level number may be obtained 
using the command SYSLEVEL from an OS/2 command line prompt.  CSDs are 
cumulative, i.e. only the most recent CSD is required to bring a system 
up from any previous CSD level.  However, CSDs only apply within a major 
version number.  For example, an upgrade, not a CSD, would bring OS/2 
Version 1.3 up to Version 2.0.  Note also that each national language 
(e.g. French, U.K. English) uses a distinct CSD.

CSDs may be ordered at 800-3-IBM-OS2.  Customers with IBM customer 
numbers (usually large sites) should call 800-237-5511 or order through 
IBMLink.  Outside the U.S., ask an authorized IBM dealer or 
representative for the CSD.  CSDs may also be downloaded from the IBM 
NSC BBS, CompuServe ("FIND OS/2"), or from sources listed in Question 8.  
And CSDs may be ordered through IBM's new OS/2 BBS.

The latest, current OS/2 2.0 CSD level will be listed in this List and 
in the PS/2 Assistant files.

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

(24)	How do I add new Adobe Type Manager typefaces?

OS/2 2.0 comes with built-in ATM for OS/2 and Win-OS/2.  A basic set of 
typefaces comes with OS/2 2.0 and is installed (if selected) for use 
under OS/2's ATM.  To install these same typefaces for use under Win-
OS/2's ATM, go to the Win-OS/2 ATM Control Panel and install the 
typefaces from the last Printer Diskette.  (Note that certain foreign 
language characters, German particularly, do not display correctly when 
using these typefaces.  To remedy this problem edit each of the INF 
files on this diskette so that the line "Pi true" reads "Pi false" and 
then proceed with installation under Win-OS/2.)

Each typeface should come with three separate files with PFB, AFM, and 
PFM extensions.  To install a typeface for use under Win-OS/2, use the 
ATM Control Panel.  To install a typeface for use with OS/2-specific 
applications, select OS/2 System -> System Setup -> Font Palette -> Edit 
Font -> Add.

PFM files may converted to AFM files using the PFM2AFM utility, 
available from sources listed in Question 8.  (However, these converted 
AFM files sometimes produce unusual results.)  For information on 
obtaining AFM files for Adobe commercial typefaces send a single line 
message with the word HELP to ps-file-server@adobe.com.  Many public 
domain typefaces for OS/2's ATM are available from sources listed in 
Question 8.

With the exception of the basic set of typefaces that comes with OS/2 
2.0, typeface files may be shared by OS/2 ATM and Win-OS/2 ATM.  To do 
so, install the typefaces using both the Font Palette and Win-OS/2 ATM 
Control Panel, specifying the target path each time (most conveniently 
\PSFONTS).

Note that IOPL=YES should appear in CONFIG.SYS; the modules WPPWNDRV, 
BVHSVGA, and PMATM are marked as requiring I/O privilege.

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

(25)	How do I tweak OS/2 2.0 for maximum performance?

For OS/2 overall, the CONFIG.SYS parameters MAXWAIT, TIMESLICE, 
PRIORITY, PRIORITY_DISK_IO, PROTECTONLY, and cache settings (in the 
DISKCACHE line, for FAT; or IFS line, for HPFS) can be tweaked.  The 
swap file should be placed on the most used partition on the least used 
hard disk, and its location is controlled by the SWAPPATH line.  See the 
online Command Reference for details.

FAT partitions should be periodically defragmented.  A shareware 
defragmenter for DOS called DOG (Disk OrGanizer) works well, as do many 
others.  (You can boot DOS from a floppy disk to run such a utility.)

For the Workplace Shell, drag shadows of most often used items to the 
desktop or folders closer to the "surface" -- opening folders takes 
time.  Drag shadows of program objects you use often (e.g. the Win-OS/2 
full screen Program Manager) to the Startup folder.  Disable animation 
(go to OS/2 System -> System Setup -> System -> Window).  Use the faster 
Details View when opening drive and folder objects; to set Details View 
as the default, open the settings notebook for the object, select the 
Menu tab, click on ~Open, then the Settings button, then select the 
Default Action.

Try reducing the number of on screen colors or dropping down in screen 
resolution to enhance speed.  Close (not just minimize; check the Window 
List) unnecessary objects and applications.  Consider adding more RAM.

For DOS programs, run full screen instead of windowed if speed is 
important.  In DOS Settings for each application: reduce conventional, 
XMS, DPMI, and EMS memory allocations to the bare minimums required for 
maximum performance; turn off VIDEO_RETRACE_EMULATION unless necessary; 
adjust IDLE_SENSITIVITY; turn off DOS_BACKGROUND_EXECUTION if not 
needed; change the HW_TIMER setting (particularly for games); enable 
VIDEO_FASTPASTE if possible; turn on HW_ROM_TO_RAM.  Communications 
programs should use hardware handshaking where possible (use OS/2's MODE 
COMx command if necessary), and a buffered UART can prove helpful.  (DOS 
programs running under OS/2 will not be aware of a buffered 16550AF 
UART.  OS/2 virtualizes the serial port and manages the buffer itself.)  
For faster printing set the DOS program's output port to LPTx.OS2 (where 
x is the printer port number) -- use a "print to file" option if 
necessary.  Disable any DOS print spoolers; rely on OS/2's spooler 
instead.  Increase CONFIG.SYS's PRINTMONBUFSIZE values.  Other, standard 
steps to enhance DOS performance (e.g. increasing BUFFERS in CONFIG.SYS) 
of course apply.

For Windows programs, run using a full screen desktop if speed is vital.  
The Win-OS/2 Full Screen icon set up by the installation program has 
poor Settings.  For better performance perform some of the same steps 
outlined in the preceding paragraph, including VIDEO_RETRACE_EMULATION 
off.  The same printer output advice also applies.  In addition, the 
Print Manager should be disabled (OS/2 provides a systemwide spooler).  
From the Win-OS/2 desktop close the Print Manager, uncheck the "Use 
Print Manager" box from the Win-OS/2 Control Panel -> Printers section, 
then, using a text editor, edit the \OS2\MDOS\WINOS2\SYSTEM.INI file, 
removing the ",!printman" entry from the MAVDMApps line.  (This last 
step will keep a warning dialog box from appearing each time you start 
the Win-OS/2 desktop.)  Consider disabling the Public setting in the 
Clipboard.  If available, set VIDEO_8514A_XGA_IOTRAP to off and 
VIDEO_SWITCH_NOTIFICATION to on (unless mouse control is lost).

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

(26)	What networking products are available for OS/2 2.0?

In addition to DOS/Windows products, OS/2-specific TCP/IP support is 
available from IBM (800-IBM-CALL), Essex Systems (508-532-5511), FTP 
Software (send mail to info@ftp.com), and others.  (A freeware SLIP 
implementation, KA9Q, is available via anonymous ftp from ucsd.edu.)  
NetWare Requester for OS/2 is available from Novell (800-873-2831) and 
IBM; NetWare Server (atop OS/2 2.0) has been demonstrated by IBM.  IBM 
offers both NetWare and LAN Server 3.0 (Basic and Advanced) with LAN 
requesters.  Microsoft sells LAN Manager 2.1a (which comes bundled with 
OS/2 1.3).  An OS/2 2.0 LAN Manager Requester, part no. 96F8359, is 
available from IBM; Microsoft offers a similar requester with LAN 
Manager 2.1a.  DEC sells Pathworks for OS/2.  A Banyan Vines OS/2 2.0 
requester is due shortly, and the current DOS requester works in a 
specific DOS session.

NDIS MAC drivers for most network adapters are available from sources 
listed in Question 8, as well as vax.ftp.com via Internet anonymous ftp.  
Drivers for 3Com adapters are available via anonymous ftp from 
ftp.3com.com, from the 3Com Support BBS, or from CompuServe ("GO 
THREECOM").

Peer-to-peer networking under OS/2 2.0 is best accomplished (at the 
moment) with a TCP/IP product, like IBM's.  TCP/IP (with NFS) is 
available for nearly all platforms, so it is a particularly good choice 
in a mixed environment.  Artisoft is reportedly working on an OS/2 
version of LANtastic; contact the company for details.  IBM may have its 
own offering in the near future (beyond the peer-to-peer support now in 
LAN Server 3.0).

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

(27)	Should I worry about viruses when running OS/2 2.0?

At present there are no OS/2-specific viruses.  However, DOS/Windows 
viruses can conceivably infect an OS/2 2.0 system.  DOS/Windows 
antivirus tools are just as useful in preventing such infection.  Also, 
IBM has an antivirus package which runs under OS/2 directly (without 
DOS/Windows emulation), McAfee's OS/2 SCAN and CLEAN have been released, 
and others (Dr. Solomon and Dr. Cohen) are in development.

But OS/2 2.0 is likely to be much more resistant to viruses because of 
its design.  Viruses running in one virtual DOS/Windows session are 
likely to be confined to that session.  Low level disk access is 
curtailed under OS/2 2.0, thus preventing most virus infection at that 
level.  And when a DOS/Windows virus does trigger, it is far less likely 
to disrupt the entire system.

OS/2 2.0 is by no means virus proof -- no system is.  But it should 
prove more resistant to virus infection.

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

(28)	Are there any clever tricks that apply to OS/2 2.0?

If you have installed the optional bitmaps, try clicking on the WPS 
desktop background once with mouse button one and pressing CTRL-ALT-
SHIFT-O.

If you have a color monitor, try editing your CONFIG.SYS file so that
	SET PROMPT=$e[32;40m$e[1m[$P]$e[0m
to obtain a more colorful OS/2 command line prompt.  You can do the same 
for your DOS sessions if you edit PROMPT in AUTOEXEC.BAT, assuming you 
have ANSI.SYS loaded.

To force DIR to display your directories in alphabetical order, with the 
subdirectories listed first, add the line
	SET DIRCMD=/O:GN
to CONFIG.SYS; and, if you wish the same for your DOS command line 
sessions, use DOSKEY (see the online Command Reference) in AUTOEXEC.BAT.  
DOSKEY also enables command history.  (Shutdown and reboot for changes 
to CONFIG.SYS to take effect.)

Hold down SHIFT while resizing text windows to make size changes 
permanent.

While running a DOS graphics program in a window, use the graphics cut 
and paste feature to clip a picture and paste it into the Icon Editor.  
You can then quickly and easily create custom icons for your 
applications.

To disable the automatic application restart feature, create a 
STARTUP.CMD file in the root directory of your OS/2 boot drive with the 
following REXX script:
	/*  */
	call RxFuncadd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs'
	call SysLoadFuncs
	call SysIni 'USER', 'PM_WorkPlace:Restart', 'DELETE:'
	'exit'
or add the line SET RESTARTOBJECTS=STARTUPFOLDERSONLY to your 
CONFIG.SYS.  To manually disable automatic application restart when 
booting OS/2, hold down the left CTRL, left SHIFT, and F1 keys 
simultaneously from the time the mouse pointer appears until icons are 
displayed on the desktop.

Use the Alarms applet to automatically start programs at specified 
times.

If you wish to dispense with the WPS (and its overhead), particularly on 
low memory systems, change the line SET RUNWORKPLACE... in CONFIG.SYS to 
read SET RUNWORKPLACE=C:\OS2\CMD.EXE (replacing "C," if necessary, with 
a different drive letter).  In fact any program with job control (e.g. 
Enhanced Editor, HyperAccess/5) can be used as the shell.

To implement a small scroll back buffer for your OS/2 command line 
windows, use the command MODE CO80,102.  This procedure may be automated 
by adding "/K MODE CO80,102" in the Optional Parameters section of the 
OS/2 Window program object settings.

A clever way to manipulate files that are locked when the WPS is running 
(e.g. display drivers) is to add the line CALL=CMD.EXE at the end of 
CONFIG.SYS.  Then Shutdown and reboot.  The system will restart with an 
OS/2 command line prompt.  Type EXIT to proceed into the WPS.  Using 
CALL is also a convenient way to configure OS/2's serial ports using the 
MODE command.  For example:
	CALL=C:\OS2\MODE.COM COM2:38400,N,8,1,OCTS=OFF,RTS=ON,BUFFER=ON
configures COM2 for high speed RTS handshaking and buffered I/O.  You 
can also use either CDD2 or SHIFTRUN; both utilities are available from 
sources listed in Question 8.

Another way, which works well with display drivers, is to copy the new 
DISPLAY.DLL to its own directory (say, C:\NEW), then place that 
directory name first in LIBPATH in CONFIG.SYS.  Shutdown and reboot.  
OS/2 will use that DISPLAY.DLL before it attempts to use the one located 
in \OS2\DLL.  (This method is required when using a 16-bit OS/2 2.0 
display driver with OS/2 2.0 CSD level 06055 or later; see Question 10.)  
To switch back to the old driver, edit CONFIG.SYS and remove C:\NEW from 
LIBPATH, then Shutdown and reboot.

To shutdown without a mouse, press CTRL-ESC, select the Desktop, then 
press the spacebar (to deselect any icons, if necessary), SHIFT-F10, and 
select Shutdown.

If your video driver does not support "seamless" Windows, try running 
the Win-OS/2 Program Manager in a DOS window.

Selective Install should be used with caution when changing mouse or 
display drivers.  Verify that proper changes have been made to 
CONFIG.SYS.

If your settings notebooks do not display but are listed in the Window 
List, click on the name of the settings notebook in the Window List 
(brought up with CTRL-ESC) with mouse button two and select Cascade.

If you wish to force a program object to start an OS/2 application 
minimized, temporarily change the program name to introduce an error 
(e.g. LOTUS.EXE to LOTUS.EX), turn to the second page of the notebook, 
check Start Minimized, then turn back to the first page and correct the 
program name.

If your \OS2\*.INI files have grown large, use the CopyINI or WPSBackup 
utilities to shrink them.  Both are available from sources listed in 
Question 8.

To run Framemaker for Windows under Win-OS/2 3.0, patch the file 
MAKER.EXE (using PATCH or DEBUG).  Around offset $1DDD1C in the file you 
should see a series of bytes as follows: 9A FF FF 00 00 A8 20 75 17.  
Change the second to last byte from $75 to $EB.

To restart the Workplace Shell (without saving desktop settings, perhaps 
after an accidental Arrange), use a utility such as psPM (available from 
sources in Question 8) to terminate PMSHELL.

To get rid of a WPS object that cannot be deleted, try one of the 
following:

(a)	click on the object with mouse button two, select Open -> 
Settings, select the General tab, uncheck the Template box, close, and 
delete;

(b)	drag a folder template from the Templates folder, drag the 
stubborn object to this folder, then drag the folder to the Shredder;

(c)	from the OS/2 command line, delete the object directly using the 
RD command.  (Many objects are actually represented as subdirectories 
below \"OS!2 2.0 Desktop" or similar);

(d)	insert a blank diskette in Drive A, drag the object to the Drive A 
disk object, then format the diskette;

(e)	use the WPSTools or Black Hole, available from sources listed in 
Question 8.  (The WPSTools can also recreate desktop objects that have 
been lost.)

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

(29)	What do I need for OS/2 multimedia applications?

Information on IBM's OS/2 multimedia extensions (MMPM/2) and tools, 
multimedia hardware, and IBM multimedia titles (e.g. Illuminated 
Manuscript) is available through IBM's Multimedia Office (800-426-9402 
ext. 150).  Drivers for the SoundBlaster are available through sources 
listed in Question 8.  VideoLogic's (617-494-0530) DVA-4000 supports 
video capture and video display in OS/2 windows as does New Media 
Graphics's (508-663-0666) Super VideoWindows.  Tecmar (216-349-0600) 
offers various OS/2 multimedia products.

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

(30)	How do I measure OS/2 performance and memory usage?

OS/2 does not treat system resources like DOS.  Memory is treated as a 
virtual resource, used intelligently.  For example, OS/2 will retain 
unused, "dormant" code in memory if that memory is not otherwise 
required, on the assumption that that code may be used again.  Also, all 
but a small portion of OS/2 (and most applications, no matter how many 
are running) may be paged to disk should a large amount of physical 
memory be required.  Utilities which display "free" memory, then, are 
only useful for rough, relative measurements.

Similarly, utilities which purport to measure system load (e.g. Pulse) 
should not be relied upon for definitive performance measurement.  
Subjective assessments are often much more reliable.  Pulse (and similar 
utilities) rely on a measurement of processor time allocated to a thread 
running at OS/2's lowest priority.  This method is sometimes subject to 
erroneous results.

That said, more rigorous system performance optimization and monitoring 
tools include SPM/2 (IBM), BenchTech (Synetik, 303-241-1718), and 
Performance 2.0 (Clear & Simple, 203-658-1204).

Note that OS/2's swap file is designed to behave with hysteresis.  It 
will not shrink in size as easily as it grows, under the assumption that 
swap space needed once may be needed again.  It should shrink given 
enough time and continued, less intense system loads.

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

(31)	What can I do to promote OS/2?

OS/2 is selling well, but there are steps you can take to assure that 
hardware devices and software will be available for OS/2 in the future.  
Customer requests do matter.

Politely, firmly, and repeatedly request driver support from printer, 
video adapter, and other hardware manufacturers.

When you receive a mailing for DOS/Windows software with a postpaid 
envelope, return the order form marked "Please send information on your 
OS/2 version."

Start a users' group at your location.  Contact Gene Barlow (214-402-
6456) at IBM for assistance.

Correspond with members of the computer trade press.  Ask for reviews of 
OS/2 software, hardware compatibility testing with OS/2, OS/2 
benchmarking, etc.  Respond politely but forcefully to press you think 
unfair; praise good reporting.

When you purchase a new system, ask the vendor to install OS/2 2.0, and 
to offer credit for dropping DOS and Windows.  If the vendor refuses, 
you may wish to take your business elsewhere.

Make sure your company (or yourself) specifies OS/2 compatibility when 
purchasing new products.

Demonstrate OS/2 to friends, relatives, and associates.

Ask your computer store to stock OS/2 software titles, have OS/2 
demonstration machines, etc.

Pass along useful OS/2 shareware and freeware to your local BBS.  Be 
sure to register OS/2 shareware.

Write an outstanding piece of shareware or freeware (see Question 16 for 
details on joining DAP).  IBM has been known to recognize such work with 
rewards.  Also, ask authors of DOS/Windows shareware and freeware if 
they would port to OS/2, or volunteer.

Recommend products that work well under OS/2; dissuade people from 
purchasing products that do not.

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

(32)	My background bitmap does not display correctly.  What's wrong?

Color bitmap images used for the WPS screen or folder backgrounds may 
not display correctly (may have distorted or missing colors) due to 
incorrect matching with OS/2's default palette.  Unlike Windows, OS/2 
does not adjust the palette to accommodate background bitmaps (to keep 
the rest of the desktop from experiencing color distortions).  (Palette 
control is now available to applications running under the 32-bit 
graphics engine with an appropriate display driver, however.)

To remedy the problem you may use the numerous background images which 
have been specifically prepared for the WPS (so-called "BGA images," 
available from sources listed in Question 8) or you may use an image 
editing/conversion utility which can create a proper, palette-matched 
bitmap file.  For example, FracInt 17.2 (available from sources listed 
in Question 8) may be used to import noninterlaced GIF, Windows BMP, and 
PCX files and save them as palette matched OS/2 BMP files.

Note that background bitmap images impose some additional overhead, 
taking up RAM and disk resources.  You should probably use them 
sparingly.

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

(33)	What is the best way to partition my hard disk for OS/2?

[Answer under construction; suggestions welcome.]

There is no single best way to partition your hard disk for OS/2.  For 
some advice on the subject you should consult the IBM OS/2 Installation 
and Planning Guide, available for download from sources listed in 
Question 8, and the OS/2 Installation Guide in the OS/2 package.

It can be useful to place OS/2 by itself in a separate partition of 
about 40 or 50 MB.  If you then elect to experiment with beta releases 
of OS/2, you can reformat that particular partition quite easily to 
erase all old code.  The swap file can be placed on another partition; 
its location is determined by the SWAPPATH line in CONFIG.SYS.

Partitioning should be performed by booting the OS/2 Installation Disk.  
Executing FDISK from the command line will not allow certain functions 
to be performed.

-- 
Timothy F. Sipples      | Read the OS/2 FAQ List 2.0h, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [Read the List, THEN post to ONE OS/2 newsgroup.]