Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: MS Windows 3.0
Message-ID: <2665.UUL1.3#5129@willett.pgh.pa.us>
Date: 24 Apr 91 03:10:39 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 28

Category 1,  Topic 57
Message 17        Tue Apr 23, 1991
G.LEFAVE [Gene]              at 08:31 CDT
 
Dennis,

I run my own comm program based on an old pf model, and it runs at 19.2K baud 
reliably.  Although, when running in a window the screen is updated
sporadically.   My experience is mixed.  Some comm programs have a problem and
some don't.  I have not found any problems at all when running "exclusive"
mode.  Polling (Crosstalk) tasks are affected a lot when running in
background.   I have not been able to figure out what windows is doing with
serial ports. But I have tried removing the COMM stuf from the .ini files with
apparently no change in behavior.   Could the problem be a mode switch?  The
DPMI mode switch takes a couple 100 us, which would prevent operation above
9.6 K baud.

My current problem is trying to trap the Break Interrupt.  What ought to be
trivial is turning into a real project.

Gene


-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp