home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 15 Message
/
15-Message.zip
/
os2v9104.zip
/
OS2-9106.003
< prev
next >
Wrap
Internet Message Format
|
1991-06-17
|
30KB
Date: Mon, 17 Jun 91 13:53:26 +0200
Subject: OS/2 Discussion Forum 910603
Reply-to: Moderated discussion forum on OS/2 <OS-2@BLEKUL11.BITNET>
************************************************************************
OS/2 Discussion Forum Mon, June 17, 1991 Volume 9106 Issue 03
Relevant addresses :
submissions : OS-2@BLEKUL11.BITNET (bitnet)
OS-2@cc1.kuleuven.ac.be (domain)
subscriptions : LISTSERV@BLEKUL11.BITNET (bitnet)
LISTSERV@cc1.kuleuven.ac.be (domain)
moderator : OS-2@BLEKUL11.BITNET (bitnet)
OS-2@cc1.kuleuven.ac.be (domain)
************************************************************************
Today's topics:
New files on LISTSERVer
Re: Byte and "Window Wars"
Problems with mailslot delivery
Appletalk and Novell
Feed from the Usenet (UUCP/Internet) comp.os.os2.* newsgroups :
Re: OS/2 Statistics Package
DPMI Support in OS/2 v 2.0?
Re: Floppies
HPFS utilities
8514/A cards: buy ATI, not Western Digital
Re: DPMI Support in OS/2 v 2.0?
HPFS Long Filenames and FAT (was Re: HPFS : How-Pathetic-File that-Sucks)
REXX and LAN Servers
Re: Killing threads
Re: Killing threads
Re: VIO, KBD and MOU calls.
Re: VIO, KBD and MOU calls.
------------------------------------------------------------------------
Date: Thu, June 13, 1991 08:00:00 +0200
From: Moderators of the OS/2 Discussion Forum
Subject: New files on LISTSERVer
This is a list of new or updated OS/2 related files available from the
LISTSERV of the OS/2 Discussion Forum at BLEKUL11.
filename filetype Remarks
-------- -------- -------------------------------
REXREF ZIPXXE1 IPF REXX Online Reference
REXREF ZIPXXE2 IPF REXX Online Reference
REXREF ZIPXXE3 IPF REXX Online Reference
* Files donated by GOLDSTEIN_L@UCOLMCC
filename filetype Remarks
-------- -------- -------------------------------
CHK4DLLS ZIPXXE Checks EXE for DLL, loads DLL
OS2LMOUS ZIPXXE Instructions on using a Logitech mouse with OS/2
OS2EPSON ZIPXXE1 Epson printer drivers for OS/2 (4-91)
OS2EPSON ZIPXXE2 Epson printer drivers for OS/2 (4-91)
S12430 ZIPXXE1 OS/2 Epson printer driver from Excel 2.20 (4-26-90)
S12430 ZIPXXE2 OS/2 Epson printer driver from Excel 2.20 (4-26-90)
ET1024 ZIPXXE1 Driver for Tseng graphics cards in 1024x768 SVGA
ET1024 ZIPXXE2 Driver for Tseng graphics cards in 1024x768 SVGA
ET1024 ZIPXXE3 Driver for Tseng graphics cards in 1024x768 SVGA
ET800 ZIPXXE1 Driver for Tseng graphics cards in 800x600 SVGA
ET800 ZIPXXE2 Driver for Tseng graphics cards in 800x600 SVGA
VGAOS2 ZIPXXE1 OS/2 1.2 Paradise SVGA drivers 1024x768. (os2_12x.exe)
VGAOS2 ZIPXXE2 OS/2 1.2 Paradise SVGA drivers 1024x768. (os2_12x.exe)
VGAOS2 ZIPXXE3 OS/2 1.2 Paradise SVGA drivers 1024x768. (os2_12x.exe)
VGAOS2 ZIPXXE4 OS/2 1.2 Paradise SVGA drivers 1024x768. (os2_12x.exe)
VGAOS2 ZIPXXE5 OS/2 1.2 Paradise SVGA drivers 1024x768. (os2_12x.exe)
* Files distributed via comp.os2.binaries
filename filetype Remarks
-------- -------- -------------------------------
DIFFPTCH ZIPXXE1 diff. file and directory comparator
DIFFPTCH ZIPXXE2 diff. file and directory comparator
DIFFPTCH ZIPXXE3 diff. file and directory comparator
DIFFPTCH ZIPXXE4 diff. file and directory comparator
DIFFPTCH ZIPXXE5 diff. file and directory comparator
F77_DRAW ZIPXXE1 Graphical (no PM) Library
F77_DRAW ZIPXXE2 Graphical (no PM) Library
GNUFU14 ZIPXXE1 GNU File Utilities
GNUFU14 ZIPXXE2 GNU File Utilities
GNUFU14 ZIPXXE3 GNU File Utilities
GNUFU14 ZIPXXE4 GNU File Utilities
GNUFU14 ZIPXXE5 GNU File Utilities
GNUFU14 ZIPXXE6 GNU File Utilities
GNUFU14 ZIPXXE7 GNU File Utilities
GNUFU14 ZIPXXE8 GNU File Utilities
GNUFU14 ZIPXXE9 GNU File Utilities
GNUFU14 ZIPXXE10 GNU File Utilities
GNUINFO ZIPXXE1 GNU info program (standalone version)
GNUINFO ZIPXXE2 GNU info program (standalone version)
GNUINFO ZIPXXE3 GNU info program (standalone version)
GNUINFO ZIPXXE4 GNU info program (standalone version)
GNUINFO ZIPXXE5 GNU info program (standalone version)
ICONS-HS ZIPXXE ICO files
NEKO ZIPXXE Cat catches your mouse game
OS2YOU22 ZIPXXE1 Remote & LAN operation software
OS2YOU22 ZIPXXE2 Remote & LAN operation software
OS2YOU22 ZIPXXE3 Remote & LAN operation software
OS2YOU22 ZIPXXE4 Remote & LAN operation software
ZIPV101 ZIPXXE ZIP file viewer
* Files donated by David Geldreich.
filename filetype Remarks
-------- -------- -------------------------------
PMCHESS ZIPXXE1 PM version of GNU Chess 3.1
PMCHESS ZIPXXE2 PM version of GNU Chess 3.1
PMCHESS ZIPXXE3 PM version of GNU Chess 3.1
SH164 ZIPXXE1 Unix-like Shell SH v1.6.4
SH164 ZIPXXE2 Unix-like Shell SH v1.6.4
SH164 ZIPXXE3 Unix-like Shell SH v1.6.4
These files are distributed AS IS, we can not guarantee anything about
their working. These files are all XXencoded ZIP files. To use these
files you must first XXdecode (We recommend our own version of XXdecode
which works under OS/2) and UNZIP (We recommend PKZIP also under OS/2).
We still welcome all OS/2 related files for distribution on our LISTSERV.
Send your files to TEWOS-2@BLEKUL14.BITNET / TEWOS-2@Liris.kuleuven.ac.be
we will arange everything for distribution.
------------------------------------------------------------------------
Date: Thu, 13 Jun 91 17:38 EDT
From: "ERIC WEBB" <EWZ@NCCIBM1.BITNET>
Subject: Re: Byte and "Window Wars"
A few comments on the June 1991 issue of BYTE, which drew righteous
indignation from a couple of folks. I refer to the article "WINDOW WARS."
The unhappiness related primarily to the "Worst" comments devoted to PM
versus the "Worst" points about Windows 3.0.
First, BYTE compared eight GUIs for potential users. When a single BYTE
article compares Windows, the Macintosh, Open Look, Ensemble, NextStep,
Motif, OS/2 PM, and Amiga Workbench, one can hardly expect an in-depth
technical analysis of each.
Second, if the "worst" thing BYTE says about OS/2 PM 1.xx is that it may
be hard to obtain from OEM sources and reletively few applications are
available, PM for OS/2 Version 1 got off easy! I think the worst point
about this version is lack of concurrent VM8086 sessions. Remember, BYTE
did not review PM for OS/2 Version 2!
Windows, PM, and the Macintosh had fewer "Worst" points than the other
GUIs. Perhaps Steve Jobs may dispute these points for NextStep.
Third, for a fair critique, the "Best" points should have been included.
For PM:
. applications are stable and compatible with each other
. multitasking capabilities built in from ground up
. provides on-line help
. macro and task automation capabilities included
For Windows 3.0:
. many applications available
. runs older DOS applications and new Windows-specific programs
. in enhanced mode (read 386), can multitask DOS applications
. macro and task automation capabilities included
. provides on-line help
. relatively inexpensive to buy (with caveats - although most
DOS systems include DOS and Windows in the base price)
I think these are fair and accurate points. (Although I think we are
comparing an operating system with a DOS extender. Still the focus was
on the GUI aspect). The article does not address Windows 2.0, so one
can't compare Windows application available before Windows 3.0. Let's
face it, Microsoft convinced developers to write for Windows 3.0 before
it became available. So now there are, according to the article's source
(Dataquest), about 1200 Windows applications available 18 months after
availability.
IBM/Microsoft could never convince developers to invest in OS/2 1.xx
PM applications because version 1 is so clearly an intermediate step to
a more elegant solution: OS/2 version 2. Unfortunately, in the rush to
make Windows applications, most developers could not afford the resources
to also make PM Version 2 applications.
I am an OS/2 Version 2 fan, and know that eventually it will become the
popular OS everyone originally expected. Until development increases
and general availability occurs, don't expect Joe computer user to buy
into anything other than DOS/Windows.
I don't know what problems you had with Windows (was it 3.0?). My own
experience is positive. I crank up three or four DOS applications and
two or three Windows applications on Monday, and context switch and
multitask until Friday. No worries. In fact, I don't know anyone who
has real problems with Windows (I hear odd hardware and sloppy BIOS
can make life unpleasant).
All in all, I eagerly await OS/2 version 2. I need power applications
like SAS, which need a large virtual address space to flex its muscles.
Also, I do some modeling on the mainframe which could run on a 32-bit
micro. Right now, my alternative to DOS/Windows is not OS/2 version 1
but Unix and X (Open Look or Motif).
Eric Webb
U.S. EPA National Computer Center
RTP, North Carolina
------------------------------------------------------------------------
Date: Fri, 14 Jun 91 19:53 N
From: <MAKI@FINKUO>
Subject: "PROBLEMS WITH MAILSLOT DELIVERY"
We use Lan Manager's mailslots for broadcasting information
to workstations. The problem is that mailslots quite often
do not reach the workstations. Some workstations get the
mailslots and some don't. The propability of the delivery
seems to be dependent on the load of the workstations. Quite a
little extra load causes about 10% of the mailslots to vanish.
We have had this problem with:
OS/2 SE 1.1 and 3 Open 1.1 and
OS/2 SE 1.3 and Lan Manager 2.0 (version B + patches).
Lan Manager-manuals say that delivery to workstations is not always
certain. Does anyone know on what parameters (Lan Manager or OS/2) depends
the delivery of the mailslots. How can I decrease the propability of
losing mailslots.
Thanks for any advice.
Santtu Maki
------------------------------------------------------------------------
Date: Fri, 14 Jun 91 13:41:10 EDT
Reply-To: Server-Requester Discussion List <SRVREQ-L@INDYCMS.BITNET>
From: J_PASSEN@UNHH.UNH.EDU
Subject: Appletalk and Novell
I am currently running NetWare v3.11 with a mix of DOS and Macintosh
machines. All machines have a Cabletron Ethernet card connected to the
server via a 10 base T hub (including the Macs). Server access is fine,
however, I have just added an Imagewrite II connected via appletalk to
the network. When a Mac user tries to print, the request is sent to the
NetWare queue and hangs there...it never gets to the printer. Any suggestions
on what steps need to be taken to make this scenario work??
Thanks, Jeff Passen
University of New Hampshire
Computing and Information Services
Durham, NH 03824
------------------------------------------------------------------------
Feed from the Usenet (UUCP/Internet) comp.os.os2.* newsgroups :
------------------------------------------------------------------------
From: baer@uwovax.uwo.ca
Subject: Re: OS/2 Statistics Package
Date: 17 Jun 91 02:11:28 GMT
In article <1991Jun13.002655.13254@midway.uchicago.edu>, sip1@quads.uchicago.edu
(Timothy F. Sipples) writes:
> What statistics packages are available for OS/2 (e.g. SAS, Gauss)?
> Does anyone have any recommendations for a good OS/2 statistics package?
For econometric stuff, Shazam is available in an OS/2 version (for the same
price, I believe, as the DOS version. Has a variety of procedures, including
OLS, GLS 2SLS, probit/logit models, etc.
Lisrel is available in an OS/2 version and was, as of last year, the only
way to get around the DOS 640K limitation (*very* critical for this program
since many users want to estimate models with > 25 variables). Other latent
variable model programs accomplish the same with DOS extenders, but these
generally don't allow users to run foreground processes (pending better
interfaces). BMPD announced an OS/2 version of EQS, but when I phoned
them they said their announcement was in error, and that no OS/2 version
was being worked on (this info. is about 6 months old, though).
Douglas Baer,
University of Western Ontario, London, Canada N6A 5C2
Internet: BAER@UWO.CA Bitnet: BAER@UWOVAX
------------------------------------------------------------------------
Date: Tue, 11 Jun 91 08:01:29 EDT
From: Marc Cohen 8/443-3945 <mlcohen@bcrvmpc1.vnet.ibm.com>
Subject: DPMI Support in OS/2 v 2.0?
>From: feustel@netcom.COM (David Feustel)
>Message-ID: <1991Jun10.215740.22830@netcom.COM>
>Date: 10 Jun 91 21:57:40 GMT
>
>Does anyone know whether DPMI is going to be supported in OS/2 v 2.0?
>--
>David Feustel, 1930 Curdes Ave, Fort Wayne, IN 46805, (219) 482-9631
>EMAIL: feustel@netcom.com or feustel@cvax.ipfw.indiana.edu
In the released product, extended memory will be available through
XMS and DPMI(DOS Protect Mode Interface).
Marc L. Cohen vnet: MLCOHEN at BCRVMPC1
internet: mlcohen@bcrvmpc1.vnet.ibm.com
------------------------------------------------------------------------
Date: 12 Jun 91 12:24:37 GMT
From: bking@ersys.edmonton.ab.ca (Barry King)
Subject: Re: Floppies
rdippold@cancun.qualcomm.com (Ron Dippold) writes:
> Here's a question about OS/2 2.0 that I'd really like the answer to...
>
> Currently whenever I multitask DOS apps, accessing the floppy drives really
> grinds the rest of the system down. With Windows 3 it's not too bad, you can
> tell that something is going on and things move in little "jerks." With
> DesqView 386 it's _really_ bad, I can hardly do anything in the other windows
> until the disk access is finished.
>
> Luckily I don't need the floppies often, but when I need it it's a real pain.
> How does OS/2 2.0 do with floppies?
>
If you are happy with the pathetic performance of Windows when it
accesses the floppy drive then you should be extremely happy with the way
floppy access is handled under OS/2. This includes OS/2 1.x BTW. You
can fire up two (more if you want - whatever) OS/2 windows, perform say a
diskcopy in one window and type a file in the other. The typed file
displays smoothly without jerks and spasms and the floppy diskette copy
proceeds as expected. Copying a floppy under OS/2 has zero effect on
communications performance. You get a barely perceptable slow down of
the system as one might expect.
OS/2 is a preemptive multi-tasking operating system and handles things
much differently than Windows or Desqview - these latter products are
really just fancy DOS extenders and not true operating systems.
Barry King bking@ersys.edmonton.ab.ca
Edmonton Remote Systems: Serving Northern Alberta since 1982
------------------------------------------------------------------------
Date: 12 Jun 91 22:45:11 GMT
From: janeri@Lise.Unit.NO (Jan Eri)
Subject: HPFS utilities
I have previously posted a request for info about the GammaTech
fileutilities for HPFS. Since I got a lot of response from others
that would like the same info, here goes:
OS/2 HPFS - Utilities for the OS/2 High Performance File System
- Optimize HPFS Volumes
- Recover erased files
- Attach comments to files
- Customize dir list utility
- Locate lost or duplicate files
- Change file attributes
- Supports long file names
- Supports extended attributes
$72.50 Includes shipping
Gamma Tech
(405) 359-1219
P.O. Box 70
Edmond, OK 73083
(Thanx Terry)
Now, if only someone could provide us poor Norwegians with a FAX number too!!
Jan
--
/ l
/ l ^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
l--/ l Jan Eri - - The Norwegian Institute of Technology , Acoustics
l l l Internet : janeri@lise.unit.no
l--\ l CompuServe : 100015,2071
\ l ^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
\ l "Music is a better drug" - Staale Krapyl
------------------------------------------------------------------------
Date: 13 Jun 91 14:48:48 GMT
From: goldman@mbcl.rutgers.edu
Subject: 8514/A cards: buy ATI, not Western Digital
I thought I should post my experiences with the Western Digital 8514/A plus
card, for anyone thinking of going the 8514/A compatible route.
I bought the card about a year ago, to use with os/2 1.2 in a clone (Dataworld
386/20, AMI bios 4/89). The card never! worked right for me; I would
always get occasional, spontaneous crashes that would freeze the whole system,
forcing me to do a hard reboot. (The mouse cursor would stop moving, and then
I'd have to hard reboot.) The problems only got worse when I made a
little LanMan 2.0 network, consisting of a couple of machines with
WD ethernet cards. Whenever I tried to backup networked drives (Sytos Plus
software 1.10; Alliance 60 Meg Tape Drive; QIC-36 interface), the
machine with the 8514/A card and the tape drive (NOT! the one where the
networked drives resided) would go on the fritz. The screen would get
completeley munged, as if the 8514/A card was no longer putting out the
right vertical or horizontal scan rate. Then I could soft reboot, but
the screen would remain munged until I hard rebooted.
A week ago, I bought the ATI 8514/A ultra card. All the problems went away.
I might as well also report that I saw a comment on the IBM Atlanta BBS,
under the topic "OS/2 on non-IBM hardware" a statement from a guy who said
"We returned all our Western Digital cards and replaced them with ATI ones.
The Western Digital card is neither hardware nor register compatible with
the IBM card". Also, Alfred Poor, in a recent review of 1024x768 cards
in PC magazine, said that, in order to get the Western Digital card to
work under Windows 3.0 enhanced mode, you have to have an "emmexclude="
statement (or something like that) in your Windows.ini file.
So my advice is: if you're thinking of buying a Western Digital 8514/A card,
don't.
Adrian
--
Adrian Goldman | Internet: Goldman@MBCL.Rutgers.Edu
Molecular Biology Computing Laboratory | Bitnet: Goldman@BioVAX
Waksman Insitute, | Phone: (908) 932-4864
Rutgers University, | Fax: (908) 932-5735
Piscataway, NJ 08855 USA |
------------------------------------------------------------------------
Date: 13 Jun 91 19:55:46 GMT
From: barry@gpu.utcs.utoronto.ca (Barry Lay)
Subject: Re: DPMI Support in OS/2 v 2.0?
In article <1991Jun10.215740.22830@netcom.COM> feustel@netcom.COM (David Feustel
) writes:
#
# Does anyone know whether DPMI is going to be supported in OS/2 v 2.0?
# --
# David Feustel, 1930 Curdes Ave, Fort Wayne, IN 46805, (219) 482-9631
# EMAIL: feustel@netcom.com or feustel@cvax.ipfw.indiana.edu
My understanding (gleaned from an IBM presentation where I asked this very
question) is that OS/2 will support up to 48 meg of expanded and extended
memory for the DOS boxes. The expanded memory is DPMI only, that is, no
VCPI support. Maybe QuarterDeck will come up with QEMM/2.
Barry
------------------------------------------------------------------------
From: steveha@microsoft.UUCP (Steve HASTINGS)
Subject: HPFS Long Filenames and FAT (was Re: HPFS : How-Pathetic-File
that-Suck s)
Date: 13 Jun 91 21:02:23 GMT
In article <13213@aggie.ucdavis.edu> s142029@fred.ucdavis.edu writes:
> You have created a file on HPFS with filename abcdefghihj.klmnop.qrstuv,
>on you hard disk. But then there's no way for you to back it up on the floppy
>with the original name. So you save it with abcdefgh.klm . So what's the use
>of HPFS anyway?
1) HPFS is useful, even if all you ever use are 8.3 filenames. I typically
use 8.3 filenames, just so it will be as easy as possible to copy files to
other drives (DOS volumes, etc.) With HPFS, you have much faster disk
access. My compiles run much faster on HPFS than FAT, and faster still on
HPFS386. Plus, you get much more efficient file storage on large hard
disks; the internal fragmentation for files is much smaller.
2) BACKUP and RESTORE can stash long filename files on a floppy, keeping
the names intact when you RESTORE the files back onto the HPFS volume.
3) File Manager can copy long filename files to a FAT volume, converting the
long name to a legal 8.3 name. It also stashes the complete long filename
in the Extended Attributes for the file. (FAT volumes can have Extended
Attributes; they are kept in a hidden file.) Then, later, you can use File
Manager to copy the file onto another HPFS volume, and the full name will
come back. This is in the online manual, under the COPY command; I found
it quickly by using the help Search command, and looking for HPFS.
--
Steve "I don't speak for Microsoft" Hastings ===^=== :::::
uunet!microsoft!steveha steveha@microsoft.uucp ` \\==|
------------------------------------------------------------------------
Date: 14 Jun 91 15:24:01 GMT
From: larrys@watson.ibm.com
Subject: REXX and LAN Servers
Anthony Green (green@roboco.uucp) sent me a note asking me about REXX
.CMD files on a LAN Server, but everytime I try to send a reply, the mail
bounces for some reason.
So...Here are the responses from the IBMers. I don't know if I needed to
clear this with anyone before posting it, but I don't see any information
that is confidential, trade secrets, etc..
Cheers,
Larry Salomon, Jr. (aka 'Q') LARRYS@YKTVMV.BITNET
OS/2 Applications and Tools larrys@ibmman.watson.ibm.com
IBM T.J. Watson Research Center larrys@eng.clemson.edu
Yorktown Heights, NY
Disclaimer: The statements and/or opinions stated above are strictly my
own and do not reflect the views of my employer. Additionally, I have a
reputation for being obnoxious, so don't take any personal attacks too
seriously.
----- OS213 FORUM appended at 17:02:04 on 91/06/13 GMT (by ALLENMJ at GDLVM7) -
Subject: Question about REXX protection violation
Ref: Append at 16:08:46 on 91/06/13 GMT (by LARRYS at YKTVMV)
REXX needs write access to the directory as it tries to write a 'complied'
version of the exec into the file's extended attribute space.
MikeAllen ALLENMJ at GDLVM7
----- OS213 FORUM appended at 02:36:51 on 91/06/14 GMT (by RRKURTZ at PKEDVM9)
Subject: Question about REXX protection violation
Ref: Append at 17:02:04 on 91/06/13 GMT (by ALLENMJ at GDLVM7)
Mike, what if you run it from you C: drive then place it on a LAN drive?
Wouldn't the P-code (compiled stuff) already be there then or would REXX
still need write access?
Dick Kurtz
----- OS213 FORUM appended at 11:25:28 on 91/06/14 GMT (by MCGUIRE at GDLVM7) -
Subject: Question about REXX protection violation
Ref: Append at 02:36:51 on 91/06/14 GMT (by RRKURTZ at PKEDVM9)
The problem is actually caused by servers that don't support file extended
attributes. Turns out an attempt to read the extended attributes from such
a server completes with a zero return code, but returns no data. Rexx was
naively expecting that a zero return code meant it had received the data
it needed and it started to process a garbage buffer.
Rick McGuire - SAA Rexx Development, Endicott
------------------------------------------------------------------------
From: seg@ingres.com (scott e garfinkle)
Subject: Re: Killing threads
Date: 11 Jun 91 17:44:30 GMT
In article <1991Jun8.234338.8440@fwi.uva.nl> delft@fwi.uva.nl (Andre van Delft)
writes:
>It is possible to launch a thread under OS/2, and to suspend and resume it.
>Can you also kill a thread explicitely, like with processes?
Not currently, much to most everyone's chagrin. It seems very likely, though,
that, at some point before gerneral availability of 2.0, the IBM kernel
group will make it possible for one thread to raise an exception in another
thread. Then you will be able to kill off threads in a fairly orderly way.
-scott e. garfinkle
------------------------------------------------------------------------
Date: 12 Jun 91 16:40:45 GMT
From: seg@ingres.com (scott e garfinkle)
Subject: Re: Killing threads
>>... It seems very likely, though,
>>that, at some point before gerneral availability of 2.0, the IBM kernel
>>group will make it possible for one thread to raise an exception in another
>>thread. Then you will be able to kill off threads in a fairly orderly way.
>
>How will the threads be killed? Will there be a new system call, or
>what?
As I said, one way or another, you will be able to rais an excpetion in
another thread. My assumption would be something like DosRaiseException
with a second argument. By specifying the EH_NONCONTINUABLE flag and an
appropriate exception number, you could make sure that the target thread dies.
This way, you also give the target thread a chance to protect itself by
registering an excpetion handler. Of course, the whole excpetion mechanism
is not real intuitive, but it's better than nothing.
It bears pointing out that I am in no way affiliated with IBM, and that
any statements made here are sheer speculation.
-scott e. garfinkle
------------------------------------------------------------------------
Date: 12 Jun 91 16:49:27 GMT
From: seg@ingres.com (scott e garfinkle)
Subject: Re: VIO, KBD and MOU calls.
In article <1991Jun11.105427.8068@kingston.ac.uk> cs_b144@ux.kingston.ac.uk (Ian
Stickland) writes:
>
>From what I've heard and read about OS/2 2.0 it would appear that
>the VIO, KBD, and MOU calls have only been kept as 16bit calls.
>this true, and if so WHY?
Up front caveat: I am not a PM programmer. If the API doesn't start with
"Dos", I haven't used it.
It really doesn't make any difference that VIO, et al., are only available
as 16-bit calls. I think that, in general, only calls of a portable nature
were given 32 bit interfaces. By definition, calls such as VIO are fairly
PC-specific. In any case, it is pretty easy to write mixed 32/16 bit
interface programs. There is a new _far16 keyword to facilitate this,
and the Microsoft SDK documentation is unexpectedly lucid in this area.
The only penalty is, of course, that the calls may end up with some extra
address-mapping and segment-loading overhead. Since you already had the
segment overhead in the 16 bit world, and the address mapping consists
of about two instructions (a SHR and a MOV, as I recall), I can't get too
worked up.
I suspect that, in the long run, you will be better off for speed going
through PM. I dunno -- I still have no great desire to do user interfaces.
-scott e. garfinkle
------------------------------------------------------------------------
Date: 13 Jun 91 09:43:08 GMT
From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel)
Subject: Re: VIO, KBD and MOU calls.
I have found, that with correct programming, the ANSI sequences and
DosWrite() is quite sufficient to achieve very fast screen output.
You may have noticed the less-2, beav-2 and gnuinfo postings in
comp.binaries.os2. All three are ported Unix programs for which I have
used termcap and good buffering (1-2k) and binary mode for stdout to get
them running. The result is really fast. To achieve the same with VIO,
you need to write directly to the VIO screen buffer and this is *much*
more non-portable. I have done this with a MicroEMACS port and it was
much more work and looked ugly. So far for the VIO API. I have used only
a single VIO call to determine the screen or window size.
For KBD and MOU, there is no such easy substitute. But I don't need and
mouse interface at all in VIO programs. To use kbd and mou
simultaneously one has to use more than one thread and semaphores to
get programs that don't use too much of the CPU while waiting for an
event. I am not shure if this is worth the trouble. (It wasn't for me so
I have removed the mouse interface from the MicroEMACS version I use).
Kai Uwe Rommel
/* Kai Uwe Rommel, Munich ----- rommel@lan.informatik.tu-muenchen.dbp.de */
DOS ... is still a real mode only non-reentrant interrupt
handler, and always will be. -Russell Williams
------------------------------------------------------------------------
END OF OS/2 DISCUSSION FORUM 910603
***********************************