Answers from e-Zine!

elcome back to "Answers from e-Zine!", your source for answers to all your OS/2 questions! In each issue we bring you tips, tricks, questions and answers from our readers and contributors. If you've got a question or tip you would like to share with us, send it in!

TIP -- Regarding last issue's Answers from e-Zine! column, your explanation on how to cause Boot Manager to boot the last used partition was too cumbersome. You can accomplish this with Boot Manager using SETBOOT rather than FDISK. This method is a lot less nerve-wracking.

From an OS/2 command window, type:

   setboot /0

to remove any default partition setting in Boot Manager. No FDISK or FDISKPM needed!
- Rob

TIP -- In last issue's Answers from e-Zine! column, you said that the PAUSE.SYS driver is needed to pause the boot process so details of the IBM1S506.ADD driver can be read.

In fact, the latest IBM1S506.ADD allows you to add a switch /W in your CONFIG.SYS which will make it pause after displaying info on each controller.

   IBM1S506.ADD /W

will do the trick. You will need an updated IBM1S506.ADD file though; the one included on the Warp 3 and Warp 4 CDs does not allow this switch.
- Eric W. Burgin

Q -- I have been trying to upgrade from Warp 3 to Warp 4. One file keeps causing the install to fail: aha152x.add. This is an Adaptec SCSI driver that causes the problem. What can I do?

A -- Duplicate diskette one of your installation disks. Edit the CONFIG.SYS and place 'REM' in front of any of the devices like the AHA drivers you do not use or have like the Adaptec SCSI card. Make sure you place a semicolon in front of the matching lines in the SNOOP.LST file as well. This should help you get past the hang-ups that occur when OS/2 goes through trying to identify your hardware system configuration. Of course, it also means that support for the Adaptec SCSI card will not be installed.

- Randy Van Heusden

Q -- Each time I open a Netscape Navigator bookmarks window the window moves to a slightly different spot on the screen. I would like it to always open in one place. Is there any way to stop windows in OS/2 applications from charging all over the screen from one run to the next?

A -- Unfortunately, this is something that is different for each program. If you are working with OS/2 Command Windows, you can hold down the Shift key, click the maximize button at the top right of the Command window, drag the window to where you want it to be, then release. Now future Command windows will always appear exactly in that spot.

With some PM applications, the author of the program was smart enough to include an ability to save window positions (for example, PMMail, PMView and many others have this feature).

However, some windows of some applications -- for example, Netscape Navigator for OS/2's bookmark window -- can not be set to open in one place. I'm afraid the Navigator bookmark window will always shimmy around a bit each time you open it.

The reason people might want windows to behave like this is to allow multiple windows to open and have each one overlapping the last, or "cascading" as it is often called. This easily allows one to see part of and click on any of the open windows. However, it's annoying if you are only opening one window at a time and you want it to stay put.

- OS/2 e-Zine! Staff

That's it for this month. If you have a tip or question that you don't see covered here, don't forget to send it in!

Copyright © 1998 - Falcon Networking

ISSN 1203-5696