[comp.os.msdos.apps] WAFFLE and Fosile drivers...

jmi@dac.mdcbbs.com (JM Ivler) (05/29/91)

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?

Thanks...

jmi@dac.mdcbbs.com
[hoping soon to become root@gadco.com :-) ]

DOUG@ysub.ysu.edu (Doug Sewell) (05/30/91)

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.

DOUG@ysub.ysu.edu (Doug Sewell) (05/30/91)

Sorry to follow my own posting up, but I should have mentioned:

If you don't have FTP access, check your local BBS systems - some of
the software-oriented ones may have one.  The sysop might have one
installed on his system and be able to direct you.

Odds are, there's one available wherever you picked up Waffle.

Doug
--
Doug Sewell, Tech Support, Computer Center,         doug@ysub.bitnet
Youngstown State University, Youngstown,  OH 44555  doug@ysub.ysu.edu
Life is difficult for the organizationally-impaired.