Dec 132017
 
Fido Standards #22.
File FSC-0022.ZIP from The Programmer’s Corner in
Category BBS Files
Fido Standards #22.
File Name File Size Zip Size Zip Type
FSC-0022.TXT 4338 1260 deflated

Download File FSC-0022.ZIP Here

Contents of the FSC-0022.TXT file


FSC-0022 11 Jul 88 by Bob Hartman, Jim Long, and Randy Bush


Dear FidoNet Software Developer,

This is an application for a FidoNet Technical Standards Committee product
code. It should allow us to evaluate your product and needs accurately and
quickly, to the benefit of all involved.

If you have already been issued a product code, but have never filled out
this form, would you please do so now? Thanks.

Please answer the questions as accurately and completely as possible. We
need to know what will actually be used on the net, so please describe only
the current product, and leave future features for the comments section.

FidoNet mail the completed form to the chair of the FTSC at 1:1/20.

We hope that you will take the time to revise your answers by submitting
additional FSC-0022 forms as your product changes. We hope to provide a
publicly available file of this data, so please tell us if anything needs
to be kept private.

Thank you for your patience and cooperation.


---------------------------------------------------------------------------

1. What is the name of the product and the current version name or number?

_______________________________________________________________________

2. What is the name, FidoNet node, and postal address, and voice number of
the person(s) or organization responsible for the product? Where should
inquiries be directed and who should be contacted if the product is
thought to cause errors on the network?

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

3. What machines and operating environments does it presently run on?

_______________________________________________________________________

4. Does the product contain a 'packer'? E.g. the package packs mail
compatible with FSC-0001.

_______________________________________________________________________

5.a Does the product contain a 'mailer'? E.g. the package transmits mail
to other FidoNet systems and can fall back to FSC-0001, though it may
handle other protocols.

_______________________________________________________________________

5.b If 5.a is yes, what protocols other than FSC-0001 does the product
handle ( e.g. FSC-0006[n] (YooHoo), FSC-0019 (SEAlink), SLO, FSC-0010
(SEAlink Resync), etc.)?

_______________________________________________________________________

With what additions or restrictions?

_______________________________________________________________________

5.c If 5.a is yes, is the package capable of servicing file requests, and
if so, 'bark' style (FSC-0013) and/or .REQ (FSC-0006)?

_______________________________________________________________________

With what additions or restrictions?

_______________________________________________________________________

5.d Is your package capable of functioning as a Continuous Mail system?
I.e. nodes running it might be marked as such in the FidoNet nodelist?

_______________________________________________________________________

6. How is the product distributed?

Public Domain ____________ Shareware ____________

Commercial ____________ Other ____________

Object code ____________ Source code ____________

Comments: _____________________________________________________________

7. Please give additional comments to describe the product.

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________

_______________________________________________________________________


Again, thank you for your patience and cooperation.


 December 13, 2017  Add comments

Leave a Reply