Opus-CBCS - Revision history

Dan Tobias: /* Sample files */

2020-02-11T14:11:04Z

‎Sample files

Jsummers at 18:12, 15 February 2016

2016-02-15T18:12:27Z

Dan Tobias at 21:23, 8 February 2014

2014-02-08T21:23:20Z

Dan Tobias: cat

2013-12-29T13:35:13Z

cat

Dan Tobias: /* BBS/GBS files (OEC) */

2013-12-15T05:49:53Z

‎BBS/GBS files (OEC)

Dan Tobias: /* See also */

2013-12-15T05:48:04Z

‎See also

Dan Tobias: /* Overview */

2013-10-04T04:01:34Z

‎Overview

Dan Tobias: /* Overview */

2013-10-04T03:47:25Z

‎Overview

Dan Tobias: /* Overview */

2013-10-04T03:43:59Z

‎Overview

Dan Tobias: /* Other links and references */

2013-10-04T03:42:07Z

‎Other links and references

@@ Line 389: / Line 389: @@
 == Sample files ==
-* [http://www.dan.info/sampledata/117.MSG Sample message file]
+* [https://www.dan.info/sampledata/117.MSG Sample message file]
 == Software and documentation ==

@@ Line 80: / Line 80: @@
 === BBS/GBS files (OEC) ===
-Various files with a '''.BBS''' extension are displayed in different situations. There can also be corresponding files with a '''.GBS''' extension which include [[ANSI Art|ANSI graphic codes]] and are displayed in place of the .BBS files for users whose terminals support such codes. However, by the time of Opus 1.70, Avatar commands were supported in the .BBS file (converted automatically to ANSI when that is what the user supports, or stripped if no special codes are supported), so there really isn't much need for the .GBS files. Both .BBS and .GBS files can include any of a set of Opus Embedded Commands/Codes (OECs), many of which are composed of control characters. The Opus Technical Manual (in one of the file areas below) documents these commands. Some of them were later standardized as the [[AVATAR]] control codes for general BBS use (in competition with [[ANSI Art|ANSI]]).
+Various files with a '''.BBS''' extension are displayed in different situations. There can also be corresponding files with a '''.GBS''' extension which include [[ANSI escape code|ANSI graphic codes]] and are displayed in place of the .BBS files for users whose terminals support such codes. However, by the time of Opus 1.70, Avatar commands were supported in the .BBS file (converted automatically to ANSI when that is what the user supports, or stripped if no special codes are supported), so there really isn't much need for the .GBS files. Both .BBS and .GBS files can include any of a set of Opus Embedded Commands/Codes (OECs), many of which are composed of control characters. The Opus Technical Manual (in one of the file areas below) documents these commands. Some of them were later standardized as the [[AVATAR]] control codes for general BBS use (in competition with [[ANSI escape code|ANSI]]).
 :See article: [[Opus Embedded Commands]]

@@ Line 4: / Line 4: @@
 |released=1985
 }}
-'''[[Opus-CBCS]]''' (Opus Computer Based Conversation System) is a bulletin board system (BBS) program that runs under MS-DOS. It was popular from the mid-1980s through the 1990s.
+'''Opus-CBCS''' (Opus Computer Based Conversation System) is a bulletin board system (BBS) program that runs under MS-DOS. It was popular from the mid-1980s through the 1990s.
 == Overview ==

@@ Line 4: / Line 4: @@
 |released=1985
 }}
+'''[[Opus-CBCS]]''' (Opus Computer Based Conversation System) is a bulletin board system (BBS) program that runs under MS-DOS. It was popular from the mid-1980s through the 1990s.
 '''Opus-CBCS''' (Opus Computer Based Conversation System) is a bulletin board system (BBS) program that runs under MS-DOS. It was popular from the mid-1980s through the 1990s.
 == Overview ==
@@ Line 403: / Line 402: @@
 * [[Wikipedia:Opus-CBCS|Wikipedia article]]
 * [http://www.textfiles.com/programming/FORMATS/fossil.txt Fundamentals of FOSSIL implementation and use]

@@ Line 81: / Line 81: @@
 === BBS/GBS files (OEC) ===
-Various files with a '''.BBS''' extension are displayed in different situations. There can also be corresponding files with a '''.GBS''' extension which include [[ANSI Art|ANSI graphic codes]] and are displayed in place of the .BBS files for users whose terminals support such codes. However, by the time of Opus 1.70, Avatar commands were supported in the .BBS file (converted automatically to ANSI when that is what the user supports, or stripped if no special codes are supported), so there really isn't much need for the .GBS files. Both .BBS and .GBS files can include any of a set of Opus Embedded Commands/Codes (OECs), many of which are composed of control characters. The Opus Technical Manual (in one of the file areas below) documents these commands.
+Various files with a '''.BBS''' extension are displayed in different situations. There can also be corresponding files with a '''.GBS''' extension which include [[ANSI Art|ANSI graphic codes]] and are displayed in place of the .BBS files for users whose terminals support such codes. However, by the time of Opus 1.70, Avatar commands were supported in the .BBS file (converted automatically to ANSI when that is what the user supports, or stripped if no special codes are supported), so there really isn't much need for the .GBS files. Both .BBS and .GBS files can include any of a set of Opus Embedded Commands/Codes (OECs), many of which are composed of control characters. The Opus Technical Manual (in one of the file areas below) documents these commands. Some of them were later standardized as the [[AVATAR]] control codes for general BBS use (in competition with [[ANSI Art|ANSI]]).
 :See article: [[Opus Embedded Commands]]

@@ Line 386: / Line 386: @@
 == See also ==
 * [[Opus Embedded Commands]]
 == Sample files ==

@@ Line 13: / Line 13: @@
 Opus rapidly gained popularity by supporting everything Fido did, plus some enhanced features such as the use of color in menus (for users with terminal programs supporting one of several protocols that supported this), and some new and improved data transmission protocols which made more efficient use of modems.
-Later on, though, it lost ground to other BBS software which had greater support for such things as online games and multi-user chatting. There was a long delay between the release of versions 1.20 and 1.70 (they skipped the version numbers in between), with the only word on possible release dates being "When It's Ready", and many people switched away during that time, leaving a few hard-core Opus fans sticking with it.
+Later on, though, it lost ground to other BBS software which had greater support for such things as online games and multi-user chatting. There was a long delay between the release of versions 1.20 and 1.70 (they skipped the version numbers in between) (or maybe the delay was before 1.20; the online history is a bit sketchy), with the only word on possible release dates being "When It's Ready", and many people switched away during that time, leaving a few hard-core Opus fans sticking with it.
 Opus was one of the few FidoNet-capable boards that supported built-in network mail (and Echomail, the FidoNet answer to forums or newsgroups); other BBS software generally required an add-on front-end to support these features. Many Opus sysops, however, still used front-ends on their boards to do netmail/echomail, since those programs had more features in this area.

@@ Line 19: / Line 19: @@
 Opus has always been free software, with the author requesting that those who like it enough to want to pay for it send money to an AIDS research charity instead of to the author. Its creators (some others joined Wagner later in developing it) sometimes pointed out that it's not really "free"; it has a requirement that its users be "lawful and friendly", which they say can be more costly than mere money.
-Opus has always tended to be a bit tongue-in-cheek, often aiming a spirit of frivolity at those elements of FidoNet that tended to get a bit over-serious at times. For instance, while a big political debate raged over whether to vest administrative control of FidoNet in an incorporated entity called the International FidoNet Association (IFNA), Opus introduced its own unincorporated, unorganized, leaderless group called the Worldwide Opus Consortium (WOC), encouraging sysops to use punnish references like "A WOC on the Wild Side" (which were often found in the tag-lines of BBSs inserted into echomail messages). Opus protocol elements had colorful names like "Wazoo" and "YooHoo/2U2". The FOSSIL protocol was also used (in common with many other FidoNet-related programs).
+Opus has always tended to be a bit tongue-in-cheek, often aiming a spirit of frivolity at those elements of FidoNet that tended to get a bit over-serious at times. For instance, while a big political debate raged over whether to vest administrative control of FidoNet in an incorporated entity called the International FidoNet Association (IFNA), Opus introduced its own unincorporated, unorganized, leaderless group called the Worldwide Opus Consortium (WOC), encouraging sysops to use punnish references like "A WOC on the Wild Side" (which were often found in the tag-lines of BBSs inserted into echomail messages). Opus protocol elements had colorful names like "[[Wazoo]]" and "[[YooHoo]]/2U2". The [[FOSSIL]] protocol was also used (in common with many other FidoNet-related programs).
 According to Wagner, Opus is not named after the cartoon penguin, but after the Latin word for "work". The plural of "opus" is "opera", but there is no apparent connection between Opus and the web browser Opera.

← Older revision		Revision as of 03:42, 4 October 2013
Line 401:		Line 401:
	* [http://software.bbsdocumentary.com/IBM/DOS/OPUS/opushist.html History of Opus-CBCS]		* [http://software.bbsdocumentary.com/IBM/DOS/OPUS/opushist.html History of Opus-CBCS]
	* [[Wikipedia:Opus-CBCS\|Wikipedia article]]		* [[Wikipedia:Opus-CBCS\|Wikipedia article]]
		+	* [http://www.textfiles.com/programming/FORMATS/fossil.txt Fundamentals of FOSSIL implementation and use]