Answers from e-Zine!

Welcome back to your source for answers to all your OS/2 questions! Each month 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!

Q -- I think it's really great that OS/2 comes with fax software and since I have a separate fax line, I want to set up my fax modem to operate as a full time fax machine. Is there any way to make FaxWorks Lite automatically start in "answer all calls" mode?

A -- Unfortunately, there is no way to get the version of FaxWorks Lite that ships with OS/2 to start in auto-answer mode, but the full retail version can do this.

Assuming you have FaxWorks or PMfax v3.0 (they are basically the same product but named differently depending on who markets them), just add "-R" in the Parameters field of the program object's Properties notebook. This will cause the program to start in "answer all calls" mode.

Now put a shadow of the PMfax object in your Startup folder and every time you boot OS/2, the program will start, ready to answer incoming faxes. If you need to order PMfax, you can find more info at Keller Group Inc.'s web site.

Q -- I have been using my Microcom 28,800 modem with Warp 3. The COM.SYS device driver did not support 28,800 throughput on the modem, so I resorted to using SIO.SYS (the shareware utility).

I now have Warp 4 installed and I am still using SIO.SYS. Has the COM.SYS driver in Warp 4 been updated to handle these faster speed modems?

A -- The answer is, "yes, it now works." The 28.8 kbps speed is now supported with a throughput of 115.2 kbps bus-to-modem speed. However, you can usually run a 28.8 modem at 57.6 kbps without any problems.

I've been running my 28.8 modem with the stock COM.SYS drivers in Merlin (aka Warp 4) since I bought it and have had no problems (except for some noisy phone lines around my house, but that is another story).

Tip -- Many people ask us how they can start certain OS/2 applications minimized. There is a trick that will accomplish this but it is not immediately obvious. Basically, you have to check the "Start minimized" checkbox on the "Session" page of the object's Properties notebook. But, of course, OS/2 automatically grays out this checkbox for all valid OS/2 program objects, preventing you from clicking it.

So how do you select this option? First, go to the "Program" page of the notebook and delete the file name from the "Path and file name" field (or just delete a few characters from it). This will prevent the notebook from finding a valid EXE file and temporarily "confuse" it, making the "Start minimized" and "Close window on exit" checkboxes on the "Session" page available. Switch to the "Session" page, check the "Start minimized" button, switch back to the "Program" page, fix or reenter the file path and name and you're all set to have the program start minimized.

Note though, this method can still be foiled by conscientious programmers. Some applications save their windows' size and position each time they are shut down, recreating the same size and position when they are next run. If this is the case, this information may override your "Start minimized" instruction.

Q -- I have two files, DOOMOS2.ZIP and DMOS2_19.ZIP. The first is Doom for OS/2 (NOT the DOS version but the real port) v1.6 while the other is v1.9. The v1.6 file runs like a charm but the second always crashes a few seconds after I start it. However, it runs long enough for me to read the opening message that it is a BETA of Doom for OS/2, written by id Software and ported by IBM (and that the file is not to be copied).

When I call id Software and IBM, no one knows anything about it (I get the old, "Call the other guy -- he'll know about it."). What's up with Doom?

A -- From The Ultimate OS/2 Gaming Page:

The first file is the v1.6 beta of Doom for OS/2 which was ported by Softport (formerly WinWare Corporation). This version didn't use DART or FSDIVE (Full Screen DIVE), but instead used the normal MMPM/2 and DIVE.

The second file is the v1.9 port which does take advantage of FSDIVE and DART. In fact, Jim Thomas, the person who did the port, tells me that Doom/2 is now finished except for the networking code. However, don't expect an "official" release from IBM, id, or anyone else any time soon.

Note that if you're running Warp 3 you'll need to install the DART subsystem to run the v1.9 beta, which may be why this file crashes on your system. My advice is to get Warp 4, which includes DART, but you can install FixPak 26 for Warp 3 and the Netscape for OS/2 plug-in pack instead.

Or the crashing could have something to do with an incorrect version number. The v1.9 beta will die when the demo starts if you run from a .wad file that isn't the correct version. The solution to this problem is to start the game before the demo starts.

For those who don't have the latest copy of Doom for OS/2, which has been patched to eliminate the expiration date, it is now available from The Ultimate OS/2 Gaming Page (ZIP, 670k).

Q -- I've been using OS/2 and its GUI PPP dialer for two years now. Unfortunately, with the popularity of the Windows 95 operating system, my ISP decided to switch its server to automatic authentication that is compatible with Windows 95. Since last weekend, I can no longer log on from home using OS/2. Is there a solution for this? I booted Windows 95 and it logged on just fine but my preferred system is still OS/2.

A -- The answer to your problem, unfortunately, is to switch to another dialer. I use InJoy v1.1 which is available at BMT Micro. It's a very good dialer; it lets you define several programs (FTP, Browser, e-mail) to run automatically at startup. As I remember, it's not very expensive either.

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!

--

[Our Sponsor: Mensys - The one place to go in Europe for all OS/2 Warp software.]

Copyright © 1997 - Falcon Networking