1st Launch - this variable is the name of the first application that CP will launch when a Mail Session is initiated. (Located at <Menu> Edit -> Edit System Data -> System Paths...)
Events - This is a list of application that will run as the first application finishes its task. (This event chain, must follow tabby specifications and the applications listed in it must be tabby compatible). (Located at <Menu> Edit -> Edit System Data -> System Information...)
** Standard Cope Module Setup **
(See CP 2.1/Cope/Tabby Setup Doc for more information)
The following is a default setup if Copernicus Modules are being used with COUNTERPoint 2.1.
Make sure you rename 'TabbyNet' application to 'CALL'
(these are 10 variables are under the Systems Paths... dialog editor or hold down mouse button at launch).
Tabby Δí - :Tabby:
Gateway Δí - :Gateway:
CP Stuff Δí - :CP Stuff:
Mail Δí - :Mail:
UBA Δí - :UBA:
PKT's Δí - :Gateway:
Archive Δí - :Archive:
Home Path - :
1st Launch - ArcMail Compress
Home Appl - COUNTERPoint
the events variable is located under the System Info... dialog editor or
click on the keyboard icon in the Systems Paths... dialog editor).
Events: - CALL,ArcMail Extract,COUNTERPoint
Other Tabby Compatible that may be inserted into the 'Events' string, when using Tabby Modules include:
Zip Extract 1.2
Darwin 1.0
Frag Fighter 1.0
Plus many other, task specific, Tabby compatible utilities.
** Standard WhiteMailer Module Setup **
(See CP 2.1/Cope/Tabby Setup Doc for more information)
The following is a default setup if WhilteMailer/Microphone II Module is being used with COUNTERPoint 2.1 to replace the CALL or TabbyNet mailer module.
Be sure to place the MacWoof into the Gateway folder.
Configure Macwoof with your boss info.
Make sure you check 'disable automatic deARCing'
(these are 10 variables are under the Systems Paths... dialog editor
or hold down mouse button at launch).
Common/Tabby Δí - :Tabby: (if Cope modules are used change this to:)
:Common Folder:
Gateway Δí - :Gateway:
CP Stuff Δí - :CP Stuff:
Mail Δí - :Mail:
UBA Δí - :UBA:
PKT's Δí - :Gateway:
Archive Δí - :Archive:
Home Path - :
1st Launch - :Gateway:MacWoof
Home Appl - COUNTERPoint
(the events variable is located under the System Info... dialog editor or click on the keyboard icon in the Systems Paths... dialog editor).
Events: - COUNTERPoint
When using MacWoof with COUNTERPoint:
CP will automatically launch the MacWoof application. However, you will have to start the mail session by loading a 'Msg Area' and starting a connect to boss session under the MacWoof 'File' menu.
Once MacWoof has successfully connected and transfered and received its mail bundles perform a locate orphan bundles from within CP. Double click on all newly delivered mail bundles and click on process. CP will then launch AME or ZIP Extract, which ever you have listed in STR 836. When AME or ZIP Extract are complete do an Import messages.
Some Front Door systems place all NETMAIL into PKT's which are transmitted first during a mail session. Macwoof will intercept these .pkts before CP can get to them and will import them into Macwoof's NETMAIL area. Therefore, if you are using Woof as the mailer, inbound netmail may be delivered into woof not CP. Most Binkley and TabbyNet systems include the NETMAIL within the arc'ed or zip'ed bundles. This all depends on how your boss has his/her end setup.
** Standard QWK Mail Setup **
(See CP 2.1/QWK Setup Doc for more information)
The following is a default setup if QWK Mailers are being used with COUNTERPoint 2.1.
(these are 10 variables are under the Systems Paths... dialog editor or hold down mouse button at launch).
Common Δí - :Common Folder:
Gateway Δí - :Gateway:
CP Stuff Δí - :CP Stuff:
Mail Δí - :Mail:
UBA Δí - :UBA:
PKT's Δí - :Gateway:
Archive Δí - :Archive:
Home Path - :
1st Launch - LHarc 2.00
Home Appl - COUNTERPoint
(the events variable is located under the System Info... dialog editor or click on the keyboard icon in the Systems Paths... dialog editor).
System Name: - this is an 8 Character ID for the BBS you are calling. CP will extract this from the CONTROL.DATfile suppied with the .QWK Packets or ask your Sysop for the name.
