Copy Link
Add to Bookmark
Report
OS2 Discussion Forum Volume 9205 Issue 02 - Part II
From @pucc.Princeton.EDU:OS2@BLEKUL11.BITNET Thu May 14 04:27:00 1992
Received: by csd4.csd.uwm.edu; id AA08737; Thu, 14 May 92 04:26:57 -0500
Message-Id: <9205140926.AA08737@csd4.csd.uwm.edu>
Received: from FRMOP11.BITNET by pucc.Princeton.EDU (IBM VM SMTP V2R2)
with BSMTP id 1986; Thu, 14 May 92 05:23:57 EDT
Received: from FRMOP11 by FRMOP11.BITNET (Mailer R2.08) with BSMTP id 4661;
Thu, 14 May 92 11:24:19 GMT
Date: Thu, 14 May 92 11:00:01 +0200
Reply-To: "Moderated discussion forum on OS/2" <OS2%BLEKUL11.BITNET@pucc.Princeton.EDU>
Sender: "Moderated discussion forum on OS/2" <OS2%BLEKUL11.BITNET@pucc.Princeton.EDU>
From: "Moderator of OS/2 Discussion Forum" <OS2MOD%BLEKUL11.BITNET@pucc.Princeton.EDU>
Subject: OS/2 Discussion Forum 920502 - Part II
To: Multiple recipients of <OS2%BLEKUL11.BITNET@pucc.Princeton.EDU>
Status: OR
OS/2 DISCUSSION FORUM 920502 - Part II
**************************************
------------------------------------------------------------------------
Date: Fri, 8 May 1992 07:43 EDT
From: Erich Schlaikjer <schlaikjer@cheers.gs.com>
Subject: Maximum number of (frame) windows in PM
Organization: Goldman, Sachs & Co.
On OS2 v1.21, I've just discovered that there seems to be a rather low limit
to the number of PM windows one can make. In a test program I can make a little
less than 100 fame windows before I get the error PMERR_HEAP_MAX_SIZE_REACHED.
At that point, NO process on my system can make any more windows. This limit
seems to be unaffected by the actual amount of memory still available
(DosMemAvail shows 8 meg free). Is there anything I can do to increase the
number of windows I can make? Please let me know! Thanks.
Erich Schlaikjer London 774-2412 Home 0923-854584
------------------------------------------------------------------------
From: "Bill Wilson" <BILL@carpenter.msstate.edu>
Date: 8 May 92 04:34:04 CDT
Subject: Re: OS/2 2.0 in a Network Environment ?
Hello Juergen,
I know at least partial answers to most of the questions you asked
in your message of April 30th. Here they are in order:
1. You can start a Novell session in a DOS box using the Netware
Shells for DOS. However, I have had problems trying to do this
in a regular DOS box, the response is SSSSLLLLLOOOOOOWWWWW!!!
I have had good luck with booting specific DOS boxes from either
floppies or image files though. The performance seems to be the
same as under regular DOS.
2. I am not sure if FTP's PCTCP will work in a DOS box, but I believe
it should. I use NCSA Telnet to do the same thing using a packet
driver. This seems to work okay in any type of DOS box.
3. OS/2 2.0 seems to handle the network adapter and packet driver
I used under DOS, at least in a DOS box. See 1 and 2.
4. A friend of mine has tried using Netware Lite in a DOS box, but
not as a server. Anyway, it didn't work. It crashed very badly....
he had to reboot his system.
5. That same friend of mine tried running Windows 3.1 in standard
mode in a DOS box. He told me it didn't work, but I don't know
how hard he tried.
6. (I don't know the answer to the question about price for the
Windows 3.1 compatible version of OS/2, but I have *heard*
that it will be free to present owners.)
Well, I hope this helps out some. I may have gotten long-winded here, but
then again, I like my OS/2 a lot. I like to talk about it.
|-----------------------|
|----- Bill Wilson -----|
|-- Mississippi State --|
|- Nuclear Engineering -|
|-----------------------|
------------------------------------------------------------------------
Date: Mon May 11 17:45:13 BST 1992
From: Mike O'Carroll <mike@elec-eng.leeds.ac.uk>
Subject: Touchstone
Anybody tried running EESOF Touchstone 1.7 under OS/2 2.0?
I get some error about failure to initialise the memory manager.
I don't think it requires protected mode, but the EMS values no
doubt need juggling.
--
Mike O'Carroll, Department of Electronic & Electrical Engineering,
The University, Leeds, LS2 9JT, UK
E-mail: mike@ee.leeds[.ac.uk]
UUCP: ...uunet!mcsun!uknet!lena!mike
------------------------------------------------------------------------
Date: Wed, 13 May 92 10:58
From: RY90@DKAUNI2.BITNET
Subject: memory with os2 2.0
Hallo,
I hope this is the right address for my question.
I recently installed OS2 2.0 on an 486 with 32MB RAM.
But it seems, that OS2 does only take 8MB of the RAM.
(memory in an 4os2 window) Is this correct? Did I have
to change something in the config.sys? (I think so)
In hope on an answer
Juergen
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Juergen Egeling, Werderstr. 41, 7500 Karlsruhe
------------------------------------------------------------------------
Date: Tue, 12 May 92 11:49:56 -0700
From: hodges@ampere.EE.UCLA.EDU (hodges@ampere.ee.ucla.edu)
Subject: *** NEW OS/2 WORD PROCESSOR IN DEVELOPMENT ***
TCI Software Research, Inc. has recently released Scientific Word for
Windows, a word processor designed for scientists and engineers. This
new product is reviewed in the May 26 issue of PC Magazine.
I spoke with Fred Osborn at TCI today and he confirmed that TCI has a
native OS/2 version under development which should be released in a few
months. The OS/2 version is *NOT* being created using a windows porting
technology -- it will be a genuine 32-bit OS/2 PM product.
A unique feature of this program is that it stores documents in LaTeX
format. Thus, it can read and write standard LaTeX document files.
Since LaTeX is a well established standard, Scientific Word for OS/2
will fit nicely in science and engineering workgroups. Note that this is
a real wordprocessor, not just a WYSIWYG viewer for LaTeX.
A couple of points of interest about TCI. This is the company that has
been selling T3 ("T cubed") scientific word processing system for many
years. They also wrote the equation editing subsystem for Lotus Ami Pro.
However, it appears that a different approach to equation editing is
being used in Scientific Word than was used in Ami. Fred explained that
it is based on an object oriented concept (I have not yet seen it).
Fred says that if you buy the Windows version now at regular price (they
also have an introductory sale price) then TCI will provided a low cost
upgrade to the OS/2 version when it is released. He also confirms that
the Windows version does work properly under OS/2 2.0.
TCI Software Research, Inc.
1190 Foster Road
Las Cruces, New Mexico 88001 USA
Phone: (800) 874-2383 or (505) 522-4600
Ask for Fred Osborn (seems like a decent chap)
Richard Hodges
UCLA & JPL
------------------------------------------------------------------------
Date: Wed, 13 May 92 16:04:47 EST
From: Tobias Teuber <TEUBER@DGOWISO1>
Subject: Accessing remote databases in an OS/2-DBServer/Requester Config
I am looking for somebody who is experienced in using a remote database which i
s installed on an OS/2 Database Server. The remote database shall be accessed b
y the OS/2 Query Manager on an OS/2 Database Requester Workstation.
We have installed OS/2 Extended Edition Version 1.3 on two OS/2 Workstations;
one workstation is defined as a Database Server and the other as a Database Req
uester. They are connected by an IBM Token-Ring.
We can catalogue the remote workstation and the remote database using Query Man
ager on the database requester workstation, but if whe try to open the remote D
atabase, OS/2 Query Manager says
"QRW2272W Transmission error 12336 while sending/receiving of data of the remot
e database"
Please contact me if you are dealing with the same or similar problems with rem
ote SQL-databases or if you know somebody who has solved the problem
using OS/2 1.3 Communications Manager, Database Manager and Query Manager.
Thank you.
Tobias Teuber
Universitaet Goettingen
Institut fuer Wirtschaftsinformatik
Abteilung Wirtschaftsinformatik I
W-3400 Goettingen
Germany
------------------------------------------------------------------------
Date: Wed, 13 MAY 92 22:47:09 GMT
From: KEMPSON@TEX.AC.UK
Subject: Borland software for OS/2 2.0
I've read in several places that Borland will be releasing a 32 bit
compiler for OS/2 2.0 "in the next few months". I called Borland UK Sales
yesterday to enquire.
Q. When will Borland C for OS/2 2.0 be available ?
A. It's being developed in the labs. We don't expect to see it before
the end of the year.
Q. Will you be releasing versions of Quattro or your other products
for OS/2 2.0 ?
A. I'm not aware of any plans to do so.
In both cases the Borland person went away to check before answering.
Perhaps the new OS/2 marketing machine need oiling ??
Niel Kempson
------------------------------------------------------------------------
Date: Wed, 13 May 92 18:05 CDT
From: Sean Fahey <Y13SPF1@NIU.BITNET>
Subject: Bernoulli drive, COM port conflict
Two Questions:
1) Has anyone made progress getting OS2 2.0 to acknowledge
a Bernoulli drive (by IOMEGA)? I've tried the IBMINT13.I13
driver and the RCD.SYS driver in the OS2 confog.sys using
the BASEDEV command. IOMEGA claims they will have the driver
completed by mid-June. The OS2 file README says that these
drives are partially supported but tech. support says they're
not sure how to do it. What gives?
(Relevant info: 44 Meg Bernoulli, OS2 2.0, parallel port
adapter, Northgate Eleganmce 386)
2) Although I'm asking my communiction package to access the
COM4 port (3E8,IRQ4) for my modem, OS2 says that another
application is using COM3 and it doesn't like it. As far
as I know, no other application is open (other than OS2).
I've included COM.SYS (3,2E8,3) (4,3E8,4) and the same for
VCOM.SYS in the DEVICE command of the config.sys.
bye,
Sean
-----------
email address: y13spf1@niu y13spf1%niu.bitnet@uicvm.uic.edu
CGS y13spf1@vm.cso.niu.edu
NIU
DeKalb, Il 60115
-----------
------------------------------------------------------------------------
Feed from the Listearn OS2-L OS/2 Non-Editored Discussion List :
------------------------------------------------------------------------
Date: Thu, 7 May 92 10:45:28 CET
Reply-To: "IBM OS/2 Unedited Discussion List" <OS2-L@FRORS12>
From: Jose Maria Blasco <UBASIR16@EBCESCA1>
Subject: REXX questions
Some experiences/questions about REXX:
* The online reference is extremely poor (and in some cases plain wrong)
when dealing with the most interesting RexxUtil functions (i.e., the
object manipulation functions). SysCreateObject works, but the
parameter description is vague and the examples are wrong. I've been
successful in creating a new folder via
Call SysCreateObject "WPFolder","Folder Title","<path>"
and also with
Call SysCreateObject "WPFolder","Folder Title","<WP_DESKTOP>"
which puts the new folder right on the desktop. "<WP_DESKTOP>" seems to
be a special kind of named location which refers to the desktop; there
are others, and this is not mentioned in the docs. I got the
information from the docs in the WPSTOOLS from LISTSERV@BLEKUL11. What
I seem not to be able to do is to use a symbolic path, like
"Desktop\OS/2 System".
The fourth parameter is a setup string which allows you to create
templates, specify (again) the object title, set it unmovable or
undiscardable, etc (again from WPSTOOLS). I'd like to know if there are
special options for the setup string if you are creating a WPProgram
object (i.e., I'd like to be able to create a program object with the
settings already filled).
* EAUTIL shows that files which have a WP name <> their physical name do
so by storing an EA called .LONGNAME. LONGNAME is 10 hex digits plus
the long name. Clould someone please point me to the appropiate source
to know whats is the standard list of EAs and their format? The
RexxUtil docs say nothing about that. Now I can get the WP name of a
file (via SysGetEA), but not of a directory (even when the EAs for a
directory *do* have a .LONGNAME EA).
* Where are the pointers to the WPProgram objects stored? I cannot find
them in the EAs for the containing folder; I read in the Unoficial
Guide to the WPS that they are stored in the .INI files. Could somebody
please post more details?
* Since you can drop an object over a .CMD's file or program icon and the
.CMD is passed the filename (or pathname for folders) as the only
argument, I wrote a test program which tried to PKZIP the folder and
contents preserving the EAs. This seems to work, *if* you use it only
as a pure backup method (i.e., you restore the folder exactly where it
was). If I try to restore the folder somewhere else, strange link
effects seem to happen between the original and the copied versions of
the file. Also, EAUTIL is *awfully* slow. Is there some version of
PKZIP (or any other compression program) which preserves EAs and is
reasonable fast? And, still better, is there some version of a
compression program which can safely backup and restore WPS folders?
Thanks in advance for any help you can provide.
Jose Maria
------------------------------------------------------------------------
Feed from the Usenet (UUCP/Internet) comp.os.os2.* newsgroups :
------------------------------------------------------------------------
From: gess@knex.Gwinnett.COM (Gess Shankar)
Subject: Will Zachmann and Ziff-Davis
Date: 5 May 92 15:04:01 GMT
Organization: Knowledge Exchange, GA, US of A
Came across an interesting post in IBM's NSC BBS, which I thought will
interest readers of this group.
----------------------Original Message follows-----------------------------
Message : 12614 (OS/2 2 0 General Q & A) Date... : 5/ 1/92 (1:30 Pm)
From... : Dave Both Refer.. : None
To..... : All Sec'ty. : Public
Subject : Will Zachman in trouble Rec'vd. : No
From: Jay Sottolano 8/231-4739
Workstation Marketing Support
Connecticut Central Trading Area
Subject: William Zachmann and PC/Week
Steve,
I just spoke with Will Zachmann from PC Week earlier. As you know,
he has been one of the strongest OS/2 advocates within the Trade Press
community we have had for the past year. Will informed me that PC Week,
actually Ziff-Davis Publishers, has been receiving a LARGE amount of
pressure from Microsoft to have Mr. Zachmann take some of the emotion
and commentary out of his articles. Apparantly, from Will's comments,
his meeting with Ziff-Davis yesterday was not very pleasant. I took it
from his comments that they had a very heated discussion as to his
possible future at Ziff-Davis.
I thought what would be helpful would be to have our OS/2 friends
(IBMers and Customers), write Ziff-Davis, and tell them that they enjoy
seeing Will's OS/2 pieces. In a magazine full of Microsoft articles,
there are many times that Will's voice is the only positive comments
people can read. If you agree, would you pass this along to my
counterparts. Thanks in advance.......
FYI...Dave (:>)
-------------------------------end of original message ----------------------
------------------------------------------------------------------------
From: richp@netcom.com (Richard Paulson)
Subject: response to PC mag article (long)
Date: Tue, 12 May 92 03:55:08 GMT
Organization: Netcom - Online Communication Services (408 241-9760 guest)
I pulled this off of America Offline, and thought that it might be
interesting for all the OS/2 fans who may be miffed at the PC mag
April 29 article on OS/2 2.0 and Windoze 3.1 ......
AN OPEN LETTER TO PC MAGAZINE
Richard E. Hodges
University of California, Los Angeles
and
Jet Propulsion Laboratory
Disclaimer: These are my personal views and do not reflect the official
position of my employer. I am not an employee, consultant or
stockholder of IBM Corporation. I do not have any financial interest in
DOS, Windows or OS/2, or in any applications programs designed for
use on these systems.
INTRODUCTION
I have just read the April 29 issue of PC Magazine and strongly
disagree with the observations and conclusions of Michael J. Miller in
comparing Windows and OS/2. This letter provides a point-by-point
rebuttal to the main points that I have found objectionable in two
articles by Mr. Miller. This will be addressed below.
In contrast, the article "OS/2 2.0: Does It Fulfill the Promise" by Joe
Salemi provides a fair and honest appraisal of OS/2 2.0. Joe Salemi
has done a masterful job learning the facts and presenting a useful
overview of OS/2. His feature article and additional sidebars, "Guided
Tour of the Workplace Shell" and "Debunking the Myths of OS/2" are
refreshing in that they directly report the facts without introducing
personal preferences and bias. It is indeed rare to find a journalist
that maintains his objectivity when evaluating operating system
software.
Another highlight of this issue is the short piece by William F.
Zachmann, "32-bit GUI Alternatives." Mr. Zachmann has clearly and
accurately delineated the key reasons that OS/2 is more appropriate
on the desktop than any currently available versions of Unix. As a
person that uses Unix based systems frequently, I can personally
confirm that Mr. Zachmann's evaluation is correct. It is useful for this
information to be summarized for those who may have heard of Unix
but do not have first hand experience with the system.
Finally, Charles Petzold's piece on Windows NT holds some academic
interest, but seems inappropriate in an issue devoted to currently
available desktop operating systems. This article is particularly
inappropriate in view of Microsoft's statement that NT is a server
operating system, not a desktop system. Furthermore, Microsoft's
abysmal track record on meeting an announced delivery date with
systems software causes one to seriously question the credibility of
statements such as, "Microsoft is predicting the retail release by the
end of 1992." This credibility is stretched even further by the fact that
to this date, Microsoft has not yet produced a reliable multitasking
operating system.
WINDOWS ENTERS ITS PRIME;
OS/2 IS A FASCINATING TECHNOLOGY BUT A DUBIOUS CHALLENGER
My complaint with Michael J. Millers article is primarily centered on
his general recommendation of Windows 3.1 over OS/2 2.0. I can
appreciate that Windows 3.1 is useful to people with relatively modest
requirements or low end systems which cannot run OS/2. However, for
those of us who have more capable hardware, there is no need to be
stuck with the limitations of Windows. Thus, rather than make a
blanket recommendation as Mr. Miller does, it would be more
appropriate to recommend the system that is best for a particular
class of hardware. It appears that Mr. Miller feels compelled to try to
justify his dubious recommendation. In what follows, I will identify
some comments that appear to be designed to support a prejudiced
conclusion.
I wonder why Mr. Miller says, "... developers can write 32-bit
applications, which theoretically can be faster than 16-bit applications
normally created for Windows or OS/2 1.x." THEORETICALLY? This is
not a theoretical hypothesis: it has already been proven with 32-bit
DOS extenders and with beta versions of 32-bit OS/2 applications that
32-bit flat memory model programs are from 50% to 100% faster than
16-bit segmented memory model programs. One would expect the
editor-in-chief of PC Magazine to be well aware of this fact. From the
context of his statement, it appears that Mr. Miller is attempting cast
some shade of doubt on the established fact that 32-bit applications
run faster and thereby cast doubt on the potential of OS/2.
Mr. Miller observes that, "From a technical standpoint, OS/2 2.0 does
appear to be a 'better DOS than DOS.' Of course, the same can be
said of DESQview, which is simpler to install, or Windows." This is
complete nonsense! Does DESQview or Windows allow one to boot
different versions of DOS simultaneously? Virtualize device drivers?
Multitask sessions under the control of a preemptive time slice
multitasking system? Provide true protection between DOS sessions?
Can either DESQview or Windows truly be called a "better DOS than
DOS" as PC Magazine concludes OS/2 is? Of course not! The
statement that DESQview is "simpler to install" also needs
examination. I have known Ph.D electrical engineers who specialize in
writing complex computer software who spent days setting up
DESQview and QEMM and getting all the device drivers plugged into
the correct holes in memory. OS/2 automatically handles all of this
tedious setup. The statement about installation is false.
Finally, I question the basis for Mr. Miller's conclusion that, "General
users probably will not find OS/2 a compelling environment because of
the complexity and size of the environment (a full installation requires
about 30MB), the relative difficulty of installing and maintaining it, and
the lack of many applications native to OS/2." I wonder if Mr. Miller
even reads the articles that appear in PC Magazine? OS/2 is inherently
designed to be easy-to-use, as explained in the article by Joe Salemi.
Even if it takes 30MB of disk space (Mr. Salemi's article states that,
"Realistically, OS/2 will eat up about 18MB to 20MB on a average
system.") if one wants an easy-to-use, high performance and rock solid
system then the price is greater disk space. Many people are willing to
get a larger hard disk and some additional RAM if it makes the
computer easier to use. And where is the basis for the claim that OS/2
is difficult to maintain? There is no justification given for this
statement. In my experience, I find exactly the opposite is true. You
just turn it on and it works. And it keeps working. OS/2 is more
complex than DOS in the same sense that a Ford Taurus is more
complex than a Model T Ford. More complex does not imply more
difficult to use and maintain.
Mr. Miller suggests Windows as an easy-to-install, easy-to-maintain
and easy-to-use system. He states, "Windows 3.1 makes it safe to
jump in the water." Question: If Windows is so easy to maintain, then
why does PC Magazine run a Windows column covering all kinds of
nitty-gritty details of memory managers, PIF files, special config.sys
settings to avoid UAE's, and the like? Evidently, it takes alot of fine
tuning just to make the system work. OS/2 doesn't require all this
constant tweaking - it just works. If Windows is so easy to install, then
why is PC Magazine compelled to devote pages 195 to 235 to all kinds
of special "tips" to help people get Windows 3.1 working as they
undoubtedly expect? Apparently, Windows is no simple matter to get
up and running reliably, but Mr. Miller makes no mention of this fact. In
the article on OS/2, Joe Salemi states that everything you need to know
is a mouse click away on the Workplace Shell desktop. Does OS/2
require special "tips" on avoiding system crashes (UAE's) as PC
Magazine feels is necessary for Windows? Obviously not. On the
contrary, Joe Salemi reports, "We tried to test OS/2's protection
capabilities by deliberately inducing a UAE (Unrecoverable Application
Error) in a Windows window. But our attempt failed completely with all
of the Windows applications on the test system, including some that
will crash when running under Windows 3.0. This is testimony to
OS/2's stability."
>From what is written in PC Magazine, it is obvious that Windows
requires a considerable amount of fine tuning to make it work properly.
On the other hand, OS/2 is not difficult to install. The statement that
OS/2 is difficult to install is manifestly false.
Mr. Miller's remarks about lack of OS/2 applications is also
questionable when considered in the context of comparing OS/2 to
DOS/Windows. OS/2 provides better support for DOS programs than
Windows does. OS/2 supports Windows programs. OS/2 supports
OS/2 1.x programs, of which there are some very good ones. And there
are many genuine 32-bit OS/2 2.0 programs already under
development. These multi-threaded 32-bit programs will be far
superior to anything showing up in Windows, and they will be available
this year. Some major applications, such as Corel Draw!, Lotus 123/G
and Lotus Freelance Graphics, are expected within a few months. In
the light of these facts, does Mr. Miller conclude that Windows
provides more choices for software support than does OS/2? The way I
see it, OS/2 offers more choices, and better choices.
DECISIONS, DECISIONS
Perhaps the most unreasonable part of Michael J. Miller's article is
the insert on page 115. First of all, the "Five reasons to buy Windows"
should be ADDED to the list of reasons to buy OS/2. Look at what is
stated:
COMMENTS ON "FIVE REASONS TO BUY WINDOWS"
1. "You can create documents rich with fonts, graphics and more."
Same goes for OS/2. Soon you will even able to do it alot faster by
using 32-bit applications.
2. " You can run multiple applications." You can do it even better in
OS/2 because of the preemptive time sliced multitasking system and
Super Fat and High Performance File Systems.
3. "You can combine applications." Same goes for OS/2.
4. "If you do not like Windows, you can always remove it." Again,
OS/2's convenient selective install allows you to remove Windows
support - the advantage is that you don't have to sacrifice DOS
multitasking, improved network support, superior file systems and
other OS/2 improvements that are provided to DOS sessions.
5. "All of the major developers are focusing their resources on
Windows." Fine. OS/2 will run these programs. Note that many major
developers are ALSO focusing resources on OS/2 32-bit applications,
so you will have the option to run BETTER versions of their software
instead of the old 16-bit Windows stuff.
COMMENTS ON "FIVE REASONS TO BUY OS/2"
1. "You bought into IBM and Microsoft's hype the first time around,
and now you are stuck." HYPE? STUCK? This is nonsense. Those of
us who have ENJOYED two years of genuine high performance multi-
tasking (and are not accustomed rebooting our machines several
times daily) do not consider ourselves "stuck". We know that what IBM
has told us is not "hype". The "hype" was foisted on poor suckers who
got "stuck" with Windows 3.0 and suffered through nearly two years of
UAE's and deplorable performance.
2. "You need to develop a high-end application that requires 32-bit
processing and a real multitasking, multi-threaded environment."
WHAT ABOUT THOSE OF US WHO JUST WANT TO BUY AND USE
THESE "HIGH-END APPLICATIONS"? In other words, those of us who
want to make proper use of the hardware that we ALREADY OWN!
Lotus, WordPerfect, Borland, Corel, Micrografx, DeScribe and many
other vendors will provide this capability very soon. Don't you think this
is worth mentioning? And knock off the Windows NT smoke screen.
That is a SERVER operating system.
3. "You need an application that requires multiple communication
sessions." What does MULTIPLE mean? I just want to connect to a
network, be able to run applications, communicate on a modem and
format diskettes without my system crashing, balking or forcing me to
become a junior computer scientist. OS/2 has been doing this for over
two years. Windows has not, and still does not.
4. "You are an IBM-only shop." Oh, please. This is a veiled attempt to
propagate the old myth that OS/2 only runs on IBM hardware. I'm
writing this using OS/2 on a Toshiba portable! Why should IBM-only
shops have the exclusive rights to a reliable and easy-to-use
computer, while everybody else is relegated to use a system based on
16-bit real mode segmented junk left over from the CP/M days.
5. "You are ready to meet the future today." THE FUTURE! Get
serious. We have had 386 machines for over FIVE YEARS and are now
finally getting an operating system to take advantage of it. This isn't
THE FUTURE. This is just getting around to running the hardware we
already have at FULL SPEED. Why should I pay a premium to upgrade
from a 20 MHz 386 to a 33 MHz 386 when the software is running my
machine at HALF SPEED?
COMMENTS ON "FIVE REASONS NOT TO BUY OS/2"
1. "There are few applications." Excuse me, but more applications run
on OS/2 2.0 than on any other platform in existence. I am sure you are
not aware of it, but there are some EXCELLENT OS/2 applications. Try
out Freelance Graphics for OS/2. IBM's TCP/IP for OS/2 is as good as
it gets on ANY system. PMX (Presentation Manager X-Windows) works
great. Mr. Miller further states, "But the reason to choose an operating
system access to unique applications." Well, that is ONE reason. Of
course, as Windows users will tell you, it doesn't necessarily do you
any good if the system can't run these apps EFFICIENTLY and
RELIABLY. Also, some of us believe that multi-threaded 32-bit
applications qualify as being unique since they (1) Run the 386 at its
full potential and, (2) Minimize the appearance of the hourglass. The
fact that these will be available IN ADDITION to nearly all the apps that
run under DOS and Windows makes it even more unique when
compared to, say, Unix, Macintosh, or DOS/Windows.
2. "Unix already offers a 32-bit multitasking operating system." Does
Mr. Miller read PC Magazine? Try reading, "32-bit GUI Alternatives: No
Contest." on page 193. If you read that article, you will learn that Unix
costs over $1000, requires substantially greater hardware
requirements, does not run DOS and Windows apps effectively and
does not have a single standardized GUI. One could also mention the
steep learning curve for a DOS user and the fact that Unix applications
cost many times more than DOS, Windows or OS/2 apps - assuming
one is available. Unix is not an issue.
3. "You can only run some Windows applications." Well, that is also
true of Windows itself! OS/2 will run Windows 2.1 apps. Will Windows
3.0? OS/2 will run nearly all Windows 3.0 apps including (as I
understand it) all of the ones on the list of over 30 that Microsoft warns
will not run properly under Windows 3.1. Really, this should be listed
as a reason NOT TO BUY WINDOWS 3.1.
4. "The installation process is ridiculous." I totally disagree. If you can
figure out how to insert a diskette into a floppy drive, then you can
install OS/2. In my judgment, it is easier than installing DOS. It does
take longer, but that is because the system is doing things that I don't
have to do. A great deal of information must be loaded onto the disk in
order to make OS/2 easy for a human being to use. This takes time. So
what?
5. "You inherit the problems of three operating systems." Actually, you
inherit the ADVANTAGES of two operating systems (DOS and OS/2) and
three graphical environments (Windows, Presentation Manager and
Workplace Shell) while AVOIDING THE DISADVANTAGES associated
with all of them. Again, Mr. Miller has made a misleading statement
that misrepresents the situation.
COMMENTS ON "FIVE REASONS NOT TO BUY WINDOWS"
1. " You have to relearn your applications." Maybe not if you run OS/2!
Just run it AS IS and learn more later if you like. This is not always
possible with Windows.
2. "Windows is slower than DOS." With OS/2 you have a couple of
options. The OS/2 DOS sessions are darned good. Also, when the 32-
bit OS/2 versions show up, you can learn them at your leisure and
check to see if they are too slow. 32-bit OS/2 apps will narrow the
performance gap with character based DOS programs, and should
actually be an improvement over graphical DOS apps.
3. "There are still more DOS applications than Windows applications."
Of course, as PC Magazine observed, OS/2 is "better DOS than DOS."
Also, you can run DOS applications FASTER and MORE RELIABLY
under OS/2 than under Windows. So, if this is a reason not to buy
Windows, it could be a reason to consider OS/2.
4. "You do not have the hardware." I agree with Mr. Miller's comments
here. You get what you pay for.
5. "If you want multitasking, DESQview does a better job with DOS
applications." Not better than OS/2 - IF you have enough memory to run
OS/2 properly. Again, this is another reason to consider OS/2
Rich Paulson
Santa Clara, Ca.
richp@netcom.com
------------------------------------------------------------------------
END OF OS/2 DISCUSSION FORUM 920502 - Part II
*********************************************
