| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | FOSSILS |
Good Morning, Karl -
About that message on 11-14-1998 from Karl Schneider to All:
KS> Aside from the fact that I'm rapidly approaching 'fossil' status
KS> myself, I still haven't managed to figure out just what it means with
KS> respect to communications.
It's a standardized application program interface for DOS that
contains com port and screen drivers, freeing the mailer or BBS
from the necessity of handling interrupts and screen translations.
Think of it as an extension to DOS that probably should have been
there in the first place.
When the BBS wants to write to the screen, it doesn't have to
care whether the screen is the local memory-mapped video card
or a terminal emulator on the other end of the phone. Same with
the com ports - it doesn't need to worry about what interrupt
or IO address the caller is on.
OS/2 obviates the need for a fossil by providing a communications
layer between the device drivers and the application which does
exactly the above.
Best,
dave
rooter{at}nisa.net
--- FleetStreet 1.22+
* Origin: Aurora Exploratoria - Ladysmith, BC, Canada (1:351/206)SEEN-BY: 396/1 632/0 371 633/260 267 270 284 371 634/397 635/506 728 639/252 SEEN-BY: 670/218 @PATH: 351/206 300 1 170/400 396/1 633/260 635/506 728 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.