Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Synchronet
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Main
Synchronet
Commits
f1ff4043
Commit
f1ff4043
authored
1 year ago
by
Deucе
Browse files
Options
Downloads
Patches
Plain Diff
This will be at least 1.2
Also, it's SyncTERM Cyan, not Syncterm.
parent
7290558b
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#6101
passed
1 year ago
Stage: build
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/syncterm/Manual.txt
+14
-14
14 additions, 14 deletions
src/syncterm/Manual.txt
with
14 additions
and
14 deletions
src/syncterm/Manual.txt
+
14
−
14
View file @
f1ff4043
SyncTERM v1.
0
SyncTERM v1.
2
SyncTERM is a terminal program written specifically for connecting to
Bulleten Board Systems (BBSs). Despite the name, SyncTERM is in no way
...
...
@@ -408,13 +408,13 @@ most of the options are the same or silimar.
MBBS GHost
"GHost" in Sync
term
refers to the "Galacticomm Host Program" (called Ghost)
"GHost" in Sync
TERM
refers to the "Galacticomm Host Program" (called Ghost)
that was included in Major BBS and Worldgroup (MBBS/WG) that allowed a Sysop
to connect another (DOS-based) PC to the BBS by use of a null modem cable.
This was a way for a MBBS/WG Sysop to offer DOS doors, something that wasn't
normally possible.
The functions of the Ghost software itself are beyond the scope of Sync
term
,
The functions of the Ghost software itself are beyond the scope of Sync
TERM
,
and you should consult the MBBS/WG Ghost documentation for operation details.
However, broadly speaking, it worked like this:
...
...
@@ -427,15 +427,15 @@ However, broadly speaking, it worked like this:
back once the door exited to wait for the next request.
While few people are connecting DOS-based PC's to anything by null modem
cables anymore, the Ghost protocol (as offered in Sync
term
) is still useful
cables anymore, the Ghost protocol (as offered in Sync
TERM
) is still useful
because it's a way to run DOS doors inside a virtual machine and expose them
outside of that virtual machine. The idea being that the VM would configure
a serial port as some kind of network passthrough, so when Sync
term
connects,
a serial port as some kind of network passthrough, so when Sync
TERM
connects,
it's passed through to the VM and then Ghost.
One use case for this is to offer DOS doors in environments where it would
normally be difficult or impossible. For example, a UNIX user could run
Sync
term
on a remote system in curses mode, where it would then connect to
Sync
TERM
on a remote system in curses mode, where it would then connect to
a VM and launch a DOS door via Ghost. This would all be presented to the
end UNIX user in a seamless way, so all they would see is the door startup.
...
...
@@ -444,24 +444,24 @@ terminated with \r\n, and contains five parameters:
MBBS: PROGRAM PROTOCOL 'USER' TIME GR
You don't need to worry about sending this since Sync
term
will format it
for you based on the Sync
term
configuration options. But it is helpful
to understand how various Sync
term
options will translate to the Ghost
You don't need to worry about sending this since Sync
TERM
will format it
for you based on the Sync
TERM
configuration options. But it is helpful
to understand how various Sync
TERM
options will translate to the Ghost
protocol parameters:
PROGRAM: The name of the DOS door/software to ask the Ghost side to run.
Configured in Sync
term
in the 'GHost Program' field of a directory entry,
Configured in Sync
TERM
in the 'GHost Program' field of a directory entry,
or after the final slash in a ghost:// style URL.
For example: ghost://user@203.0.113.64/program
PROTOCOL: Always set to 2. Not configurable in Sync
term
.
PROTOCOL: Always set to 2. Not configurable in Sync
TERM
.
USER: Username of the person connecting. Configured in Sync
term
in the
USER: Username of the person connecting. Configured in Sync
TERM
in the
'username' field of a directory entry, or before the '@' in a ghost://
style URL. For example: ghost://user@203.0.113.64/program
TIME: Amount of time the user has remaining. Always set to 999. Not
configurable in Sync
term
.
configurable in Sync
TERM
.
GR: Set to GR (for "GRaphics", meaning ANSI-BBS support) or NG
(for "No Graphics"). Always set to GR. Not configurable in Sync
term
.
(for "No Graphics"). Always set to GR. Not configurable in Sync
TERM
.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment