[comp.os.os2] CrossTalk and OS/2

joma@ashtate (Jon Marinello) (06/14/90)

Running Crosstalk XVI in the compatability box is giving me trouble.  When
I start crosstalk, I receive two messages from the system:

	SYS1927: A DOS mode program changed an interrupt vector that
	is owned by the system.  The program was ended.

If I ignore the errors and continue, crosstalk works fine.  The problem
arises when I return to PM.  The mouse does not respond.

I am using a microsoft serial mouse on a COMPAQ 386 16 running OS/2 1.2.  Has
anyone encounterred this problem and found a way around it?
-- 
Jon Marinello

---------------------
Wait until you see dBASE CXXXII

patrick@engrhub.ucsb.edu (Patrick Lindstrom) (06/14/90)

I wouldn't suggest using CrossTalk in the DOS box.  But you do have an
easy solution.  Purchase something like REXXTERM which is written for both
DOS and OS/2.  It probably works better too.

Chuck_M_Grandgent@cup.portal.com (06/17/90)

Don't know about Crosstalk in the DOS compatibility box, but
I run Procomm Plus in the DOS box just fine.  I suspect if you
tried OVER 2400 baud you'd have a problem, but at 2400, everything
works super.  Zmodem transfers typically are 205-225 cps, which
is about as good as you can expect at 2400.  Now I'm running IBM's
SE 1.2.  Very early (rev 1.0) OS/2 didn't behave as well.
You're not trying both the mouse and modem on the same Com port,
are you ?  That's certainly a no-no.
      chuck_m_grandgent@portal.com