Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcdchg!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: W3 Development Questions
Message-ID: <1990Aug02.152319.14530@chinet.chi.il.us>
Date: 2 Aug 90 15:23:19 GMT
Sender: patrickd@chinet.chi.il.us (Patrick Deupree)
Organization: The Whitewater Group, Evanston, IL
Lines: 32

In article <8409@b11.ingr.com> lhughes@b11.ingr.com (Lawrence Hughes) writes:
}1. You can determine the total amount of "memory" available easily enough, but
}   how do you determine total/available:
}   a. conventional memory (up to 640K)
}   b. LIM EMS banked memory (also whether banking is even supported*)
}   c. extended memory (286/386 linear above 640K)
}   d. virtual memory (386 enhanced mode only)

here's the trick.  If you're running in real mode, you'll have EMS memory
available.  If not, you'll pretty much be running in all extended memory.
In order to find out the things you want to know, I believe you'd have to make
the appropriate DOS/BIOS calls.  Basically, do the same thing that those
memory mapping programs do for DOS.

I'm pretty sure that, as far as Windows is concerned, there is no conventional
or extended memory.  Just memory.

}2. I can have a timer driven handler wake up from time to time and snarf any
}   data that has come in the comm port and process it, but does anyone know
}   of a way to have an incoming comm port character trigger an input event,
}   yea, like unto a character typed on the keyboard? Or equivalently, a
}   message that informs me that the comm port queue is no longer empty...

The last I knew, the only way to handle com ports was through the timer/polling
method.  There is no way to tell a comm port to post a certain message every
time a character comes in, or anytime it's full.

-- 
"Organized fandom is composed of a bunch of nitpickers with a thing for
 trivial pursuit."  -Harlan Ellison

Patrick Deupree ->	patrickd@chinet.chi.il.us