DOUG@ysub.ysu.edu (Doug Sewell) (06/10/91)
Archive-name: hardware/serial/fossil/0-- Archive-directory: wuarchive.wustl.edu:/mirrors/msdos/fossil/ [128.252.135.4] Original-posting-by: Doug Sewell <DOUG@ysub.ysu.edu> Original-subject: Re: WAFFLE and Fosile drivers... Reposted-by: emv@msen.com (Edward Vielmetti, MSEN) In article <1991May29.161140.1@dac.mdcbbs.com>, jmi@dac.mdcbbs.com (JM Ivler) says: > >I just picked up waffle and it keeps on talking about a "fossle driver". Well, >I went to my local PC stores, and no one know what the heck one is. So, before >I start up the software, I was wondering... > >1) What is it? >2) Do I really need it? >3) Where do I get it if #2 is YES? > A 'FOSSIL' driver is a device driver for the asynchronous comm port of an MSDOS system. I believe (and I'm having to think about it a bit) that it stands for Fido-Opus-Seadog System Interface Layer. I don't remember the history, but those names are all prominent BBS software programs. The standard async support for MSDOS on most IBM-type PCs is very primi- tive. The FOSSIL driver replaces it with interrupt-driven support and a standard set of interface calls that all FOSSILs are supposed to support. This way, a BBS system doesn't have to include its own interrupt-handler support. Some BBS systems require you to install a FOSSIL, since that's the only way they talk to the comm-port. A customized FOSSIL driver can also hide oddball async ports or MSDOS variants (the Tandy 2000, for example) from the software. BBS and comm package code becomes more portable this way. Last I looked at Waffle's doc's, a FOSSIL wasn't required, but if you're going to use high-speed modems (>2400 baud), plan on using one. There are two I know of right off-hand... BNU is a TSR implementation, and I believe it's unloadable. X00.SYS is a standard device driver you put into your config.sys file. Both are available via anon FTP from wuarchive.wustl.edu: /mirrors/msdos/fossil/bnu170.zip /mirrors/msdos/fossil/x00v124.zip I have no preference, as I've not actually used either... maybe some comp.dcom.modems, alt.bbs, or alt.bbs.waffle people can advise you. Also, if you get it - or can arrange to get it, check out newsgroup alt.bbs.waffle. Last time I hung out there, there was a bunch of really helpful people, including the author, Tom Dell. Doug -- Doug Sewell, Tech Support, Computer Center, doug@ysub.bitnet Youngstown State University, Youngstown, OH 44555 doug@ysub.ysu.edu The more things change, the more things stay insane. -- comp.archives file verification wuarchive.wustl.edu total 394 -rw-r--r-- 1 root 1264 May 26 19:00 00-index.txt -rw-r--r-- 1 20002 114161 Mar 18 18:00 x00v124.zip -rw-r--r-- 1 20002 3872 Sep 4 1990 vibm_110.zip -rw-r--r-- 1 20002 43124 Aug 22 1990 ocom_530.zip -rw-r--r-- 1 20002 74398 Apr 11 1990 bnu170.zip -rw-r--r-- 1 20002 10509 Dec 10 1989 fosil006.arc -rw-r--r-- 1 20002 25793 Feb 20 1989 fossilv5.arc -rw-r--r-- 1 20002 9973 Feb 20 1989 fossil.arc -rw-r--r-- 1 20002 15001 Feb 20 1989 hzcomm31.arc -rw-r--r-- 1 20002 9485 Feb 20 1989 foslaux.arc -rw-r--r-- 1 20002 2889 Feb 20 1989 t2000.arc -rw-r--r-- 1 20002 55239 Feb 20 1989 t2kcom52.arc -rw-r--r-- 1 20002 4274 Feb 20 1989 syocom50.arc -rw-r--r-- 1 20002 8408 Sep 6 1988 odec_501.arc -rw-r--r-- 1 20002 3040 Sep 6 1988 vdec_004.arc found fossil ok wuarchive.wustl.edu:/mirrors/msdos/fossil/