🚀 go-pugleaf

	The following steps will smooth the installation of OS/2 ver. 3 (Warp), 
and will avoid several bugs in the installation procedure.  The problems
include corrupted OS/2 AUTOEXEC.BAT and CONFIG.SYS (already documented in
Computers & High Technology), multiple DOS statements on one line in DOS
AUTOEXEC.BAT and CONFIG.SYS, and Windows failing to run from DOS and OS/2.
Do these steps before installation.

1.	The 3.5" drive must be the A: drive in order to boot.  If it is not,
	the drives must be swapped.  First, switch off the machine, and unplug
	the power cable.  Open the lid.  Unplug the ribbon cable to the A: and
	B: drives, and re-connect the drives to the spare sockets in the cable.
	If there are no spare sockets on the drive cable, obtain a new 5-socket 
	cable.  Then at boot, press DEL (or whatever) to bring up the CMOS
	setup screen, and change over Drive A and B to show the 3.5" drive in
	A: position, and 5.25" in the B: position.  (To avoid an expensive
	mistake, first mark each drive with a texta, to indicate the
	orientation of the colored edge of the cable, which corresponds to
	pin 1.)

2.	If installing (or re-installing) over a dual boot version of OS/2 ver
	2, first save or backup any of your own files in OS/2 directories, then 
	delete all OS/2 files and directories in the root directory (most of
	the files/directories start with the characters OS2, but there's
	DESKTOP, NOWHERE, MAINTENA.  Some files are hidden).

3.	Edit both the AUTOEXEC.BAT and CONFIG.SYS files.  Position the cursor 
	after the last line, and press ENTER.  Save the files.

4.	Delete or rename the AUTOEXEC.BAK and CONFIG.BAK files.

5.	If you are using the Microsoft Speaker Driver for Windows, uninstall
	it. ("Wall paper" may also prevent Windows from running in OS/2.  If
	you have installed one, uninstall that also.)

6.	Use FORMAT /S to make a bootable 3.5" floppy disc, and copy to it an 
	editor, a file and directory browser such as FILE IT!, and your DOS 
	CONFIG.SYS and AUTOEXEC.BAT files.  This will enable you to boot up 
	and make corrections to DOS and/or OS/2 files when DOS and/or OS/2 
	won't boot.

After installation:

	From OS/2, edit the C:\OS2\SYSTEM\CONFIG.DOS and 
	C:\OS2\SYSTEM\AUTOEXEC.DOS files.  Inspect the last few lines.  If 
	there are two DOS statements on the same line, make them into separate 
	lines.  (Alternatively, edit your CONFIG.SYS and AUTOEXEC.BAT files 
	when in DOS.)

When running OS/2:

1.	After a crash, check your main disc, as OS/2 automatically runs CHKDSK. 
	You could find some 200 files of the form EA00000.CHK or FILES0000.CHK 
	in the root directory.  Check their content and delete them.

2.	From the OS/2 desktop, if a DOS application hangs, and you have to 
	re-boot OS/2, press and hold CTRL-SHIFT-F1 as soon as the white desktop 
	appears (release the keys momentarily when disc activity stops). 
	Release the keys when the desktop has been rebuilt.  This will prevent 
	OS/2 from automatically re-starting the hung job.  If you neglect to do 
	this, each new boot will waste time re-starting the job.  In time, 
	several such jobs will tie up resources, and may lock up the system.


(My letter (above) appeared in The Australian, "Computers & High Technology",
page 18 on 6/12/94.)

   Another installation problem can occur when you have multiple copies of
Windows (e.g. a backup or a different version).  THe OS/2 user's manual
states that multiple copies of Windows are not supported.  However,
what it *doesn't* say is that multiple copies will confuse OS/2, and may 
result in the wrong path to Windows being set up for the OS/2 icons.  (As
the last step of installation, OS/2 looks at all the files in your system
including all drives).  It will alter the .INI files of the first Windows
that it finds, but will set up a path to the last copy of Windows that it finds.
To fix this, press the right-hand mouse button on the Windows icons on
the desktop, choose "settings" and check that the correct path has been set up.