|
|
|
|
|
|
|
|
VM/COM, October - November 1986
1
-
OO OO OOO OOO // OOOOOOO OOOOOOO OOO OOO
OO OO OO OOO OO // OO OO OO OO OO OOO OO
OO OO OO O OO // OO OO OO OO O OO
oo oo oo oo // oo oo oo oo oo
oooo oo oo // oo oo oo oo oo oo
oo oo oo // ooooooo ooooooo oo oo
0 ------------------------------------------------------------
October/November 1986 Edition Volume 3 Number 5/6
- CsNews Network Newsletter
-
-
Staff:
0 Michele Robinson CSMICH at MAINE Editor
Andrew T. Robinson ANDY at MAINE CsNews Director
Prof. G. Markowsky MARKOV at MAINE Faculty Advisor
-
0 Ôçççççççççççççççççççççççççççççççççççççççççççççççççççççççä
³ Newsletter article contribution Userid: CSNEWS@MAINE ³
³ ³
³ Contributions from readers welcomed and encouraged! ³
¨ççççççççççççççççççççççççççççççççççççççççççççççççççççççç]
1
0 Vm-Com Issue 3.5
-
0 Table of Contents
+ _____ __ ________
- Introduction to Vm/Com 3.5 . . . . . . . . . . . . . . . 1
CSNEWS Notes . . . . . . . . . . . . . . . . . . . . . . 2
Letters to the Editor . . . . . . . . . . . . . . . . . . 3
Life in the Fast Lane: Column #3 . . . . . . . . . . . . 4
Publishing an Electronic Magazine: a gothic romance . . . 9
Don't you C? . . . . . . . . . . . . . . . . . . . . . . 12
How the Jack O' Lantern Got Its Name . . . . . . . . . . 15
OpCodes . . . . . . . . . . . . . . . . . . . . . . . . . 17
-
-
-
-
-
-
-
-
-
-
-
-
-
- 2
1
0 Vm-Com Issue 3.5
0 Introduction to Vm/Com 3.5
+ Introduction to Vm/Com 3.5
-
Yes you can believe your eyes.. another issue of Vm/Com
has finally made it. Better late than never right? This
may not be the longest issue of Vm/Com you have ever seen
but it is at least something to let you know that Vm/Com is
still struggling along. Again I am going to ask that
anybody out there who might be interested in writing
something let me know. We really do need the articles.
0 This issue contains a Letters to the Editor section,
part three of Life in the Fast Lane, an article about
electronic magazines, an article on the language C, and the
usual assortment of OpCodes. Also you will find an article
on Halloween, I realize this has nothing to do with
computers but its in the Holiday spirit.
0 Until next time, Keep reading and writing, and have a
Happy Halloween and a Happy Thanksgiving. See ya in V3-7.
0 Michele Robinson,
Editor
-
-
-
-
-
-
-
-
-
-
0 1
1
0 Vm-Com Issue 3.5
0 CSNEWS Notes
+ CSNEWS Notes
0 Andrew T. Robinson, (ANDY@MAINE)
-
0 Well, since I'm running out of clever original opening
lines, let me just say "Welcome to the next issue of CSNEWS
NOTES."
0 Many things have transpired since the last time you read
the hallowed column of Vm/Com... Not the least of which is
that University of Maine Computer Science department has
devoted an entire course (and possibly a series of courses,
if the pilot is successful) to the CSNEWS server software!
0 It would be spoiling the surprise(s) to let you know
exactly what we are engaged in this semester, but if all
goes well there will be at LEAST a few surprises for those
of you who are programming-oriented when our work is done.
0 Other than that, there isn't a whole lot new to talk
about. CSNEWS usage has never been better, and FLAME and
CSBB are as active as anyone could want. Oh well, maybe I
will have something more exciting next issue.
0 Keep Netting!
0 Andy Robinson
-
-
-
-
-
-
-
-
0 2
1
0 Vm-Com Issue 3.5
0 Letters to the Editor
+ Letters to the Editor
-
From: Bruce Pennypacker, (90_PENNYPAB@UNION)
- I just started using BITNET only three weeks ago, and am
totally surprised at what I can do just by sitting in this
room full of terminals and typing away at a bunch of keys in
front of me. A few days ago I found out about the VM/COM
newsletter and decided to take a look at it. I was amazed
to see a group of articles by people all over the world who
took a few minutes to write about what they find
interesting. Everybody should be encouraged to write
articles for VM/COM every once in a while. Look at me -
after reading my first copy of the newsletter I decided to
let everybody know how impressed I was. I had never used a
mainframe before I started college and didn't have the
slightest idea that there were hundreds of computers
connected together throughout the world that I could
communicate with. I am very glad that I learned of BITNET
and intend to use it as much as possible (at least until I
graduate!). I hope that there are a lot of people that take
advantage of BITNET's capabilities and help keep the network
and newsletters like VM/COM working smoothly for everybody,
especially the people like me who are just learning about
it. Keep up the good work!!!
-
-
-
-
-
-
-
-
-
3
1
0 Vm-Com Issue 3.5
0 Life in the Fast Lane: Column #3
+ Life in the Fast Lane: Column #3
0 Chris Condon BITLIB@YALEVMX
-
For the Fall 1986 semester I wrote a study for Sacred
Heart University, the school I attend. The study concerned
whether the University should link it's VAX 11/750 to
BITNET. It included descriptions of network services,
membership requirements, and the cost of the hardware and
software. Melded into all of that was an evaluation of the
network as a whole. Since my own Yale BITNET activities
wouldn't be affected by my conclusions I was able to stand
back and take a hard, dispassionate look at Our Beloved
Network. This article contains a condensation of those
thoughts.
0 The Use and Stability of BITNET Services
0 BITNET is still by and large a voluntary,
cooperative network that only exists to the extent
that people work together... - Daniel Oberst
0 The file servers, conference machines, list servers and
other BITNET services perform the vital network function of
dispersal of information in different and efficient ways.
Their use reflects both the type and importance of
information given. For instance, many file servers store
programs that are useful for present and future BITNET
users, while the digests and forums may contain information
that is of interest only during a particular week.
0 It should be noted, however, that while the BITNET
services are useful in many ways they are also fairly
unregulated. On some file servers it is easy to find listed
among programs such as AWAY EXEC and VNET EXEC files such as
NUDE PICTURE and OTHELLO EXEC. Depending upon your
sensibilities this may or may not be harmless. Those that
maintain the file servers store the files they see fit.
Those in authority over them may have something else to say
about it.
0 As recently as August 1985 there were seven non-Relay
conference machines, twice as many several months before
that. In pre-Relay days conference machines were maintained
most often by students who wrote their own code and ran it
on their own userids. These old chats lasted as long as no
one detected how much system resources they were gobbling
up. When the chat was uncovered it would mysteriously
dissaper. Often the code would be shipped off to another
node or userid to be run again.
-
4
1
0 Vm-Com Issue 3.5
0 Due to the span of the relatively less CPU-hungry Relay
system, there are no more old-style conference machines
remaining. The last, FORUM@TAMCBA, was pronounced inactive
in late April of this year.
0 There is no official registration for BITNET servers. If
administrators at a given node wish to write and run a
server it it their prerogative, but there exists no central
authority to inform that the server is available for use.
By convention, the BITLIST weekly electronic magazine has
become the accepted source for such announcements. That
magazine, however, is published on a voluntary basis.
Should the author/editor of the BITLIST choose to stop
writing the magazine the job may or may not be taken over by
somebody else. This is not, to say the least, a
tremendously efficient setup.
0 Not only magazines are maintained on a voluntary basis.
The resources for file servers such as CSNEWS@MAINE and
SERVER@TAMCBA are provided by their respective institutions
for BITNET use. There is no requirement that they provide
these services to BITNET, nor do these institutions receive
incentive to do so. However, the author has yet to see a
file server shut down permanently. These tend to be the
most stable of BITNET services.
0 Name servers are about as useful as the information
stored on them. There is no requirement to register oneself
in the user database at BITNIC, nor do most nodes maintain
local name servers. The real maintainance problem occurs
when people do not delete themselves from off node user
databases. Each semester the the author is sent a list of
Yale userids in the CSNEWS user database and asked to verify
their existence. This must be done for every node that has
a user listed in that database (a tedious process to say the
least).
0 BITNET, however is not a static network. Work is
constantly underway to study such problems and construct
solutions. That is the one function of the list servers,
digests, and electronic magazines. Change is a constant in
BITNET, but more often than not it is change for the better.
0 The institutions in BITNET and her sister networks offer
a wide variety of services to the users. Most of all,
BITNET allows quick and easy contact with knowledgeable
people in Computer Science and many other fields. The
interests of those in the networking community are not
restricted to computers, nor are the those interested in
computing solely concerned with networking. The various
services (file servers, list servers etc.) allow
communication with these people. People, after all, are the
basis for BITNET.
- 5
1
0 Vm-Com Issue 3.5
0 Communication with these people is both BITNET's strong
and weak point. The variety of services in BITNET is great.
They fill the various information niches in several easy to
use ways. These same services, however, are often unstable
and subject to the whims of those caring for them. This is
not a problem restricted to BITNET. The Digests and Forums
from Arpanet and other networks often die out to due to lack
of interest.
0 The instability of these services often makes the people
in BITNET difficult to contact. Eventually this becomes a
matter of knowing where to look for information. For
example, If one were trying to locate people knowledgeable
in software engineering he might search the CSNEWS Bitnauts
list. If he failed there he might try the NETSERV and
BITSERVE user databases, and then go on to the Soft-Eng
Digest. The less experienced user might not know of these
sources, or how to use them effectively.
0 The resolution to this problem is proper instruction in
the use of the network and its services. All too often
nodes are attached to BITNET and the staff does not have a
complete knowledge of what is available or how to use it.
The users may be left to their own devices. This breeds
intentional and unintentional network abuse. Proper
instruction prevents many of the pitfalls that the
uninformed user may fall into.
0 The people of BITNET themselves are not always the salt
of the Earth. There are hackers in BITNET, yes. There are
a few people who take advantage of the relative anonymity of
mainframe accounts and verbally abuse others via interactive
messages. For the most part, however, the people of the
network are a well mannered, educated group of people. For
the most part, that is... Those that abuse BITNET are
subject to disciplinary action at their own node, if and
when they can be tracked down. This depends on whether the
abused individual has the presence of mind to write down the
userid@node of the abuser.
0 BITNET also suffers from its "store-and-forward"
structure. System crashes or hardware problems at a given
node may cut nodes off from the rest of the network for days
at a time. For instance, when the CUNYVM-->YALEVM link is
down, those at Yale, University of Maine, Wesleyan
University, UCONN, SUNY-SB, Brookhaven, Brown University,
Northeast University, Boston University, Boston College,
Harvard, MIT, and Tufts University are unable to contact the
1000+ other nodes in the network. Nor are the users there
able to contact most of the file servers, list servers, etc.
Likewise, the people on the other side of the gap are unable
to contact CSNEWS@MAINE. This causes a buildup of mail
files at both YALEVM and CUNYVM.
- 6
1
0 Vm-Com Issue 3.5
0 Conversely, this same "store-and-forward" structure makes
BITNET easier to use than some other networks. For
instance, when sending mail files RSCS checks the routing
tables as there is only ONE way to get from Point A to Point
B in the network. Some other networks require a specified
pathway, such as:
0 mitpls!ubjade!yalecs!melkor!gandalf!kulpvm!shucc!
0 That can become quite a problem when sending mail from one
end of a network to another.
0 Obviously, BITNET has it's problems. This does not
diminish the fact that despite these problems the network is
still useful and still works. How useful it is and how well
it works depends on the individual institutions and how they
contribute to and maintain the network. This may be said for
any computer network.
0 The mystique behind BITNET is this: For a hacker or
someone who simply enjoys computing, the network is a source
of great enjoyment. It is on such a scale that it would
take many months, maybe years to thoroughly explore it's
resources (not to mention those available via other
networks). However, what may be a source of enjoyment for
the hacker may be simply annoying to someone who wishes to
use the services for a specific purpose. The jnet software
package is easy to use; it is BITNET that requires the user
to go through quite a bit of orientation.
0 That problem is partially surmountable, given experienced
people to guide new BITNET users through the services. A
consultant of sorts would be necessary to answer questions
or suggest where information might be found. This does not
help the consultant much, who must still keep track of the
services. Most of the BITNET services have been covered or
referred to in these pages. It is more than likely that
there will be someone who is running a conference machine
that doesn't come to his attention, or a digest that will be
phased out without notice.
0 BITNET may not be right for Sacred Heart University. It
may be too expensive or too disorganized or even too big
depending upon what one wants to put into and get out it.
That does not mean that networks as a whole are not for this
institution. On the contrary, computer networks offer a
range of services that would be useful to both students and
faculty. This is evident from the number of people and
services in a network as young as this one.
-
-
7
1
0 Vm-Com Issue 3.5
0 Networking can be a useful tool for the people of Sacred
Heart University. BITNET, however, may not be the network
of choice. It is therefore suggested that alternative
networks be studied before BITNET membership is decided
upon. This, in turn, will allow the proposed 1987
restructuring of BITNET to be studied and evaluated.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
0 8
1
0 Vm-Com Issue 3.5
0 Publishing an Electronic Magazine: a gothic romance
+ Publishing an Electronic Magazine: a gothic romance
0 David A. Liscomb, (CSDAVE@MAINE, LISCOMB@MAINE)
-
The following article was prepared with the cooperation
of the editors of several popular BITNET electronic
magazines. My thanks go to Chris Condon, editor of
NetMonth; Andy and Michele Robinson, editors of Vm/Com; and
Brent Britton, editor of Nutworks. I have tried to
incorporate their advice with my own experiences as editor
of the electronic magazine FSFnet.
0 This article is primarily intended for people interested
in editing an electronic magazine, and for those users who
wish to know just what it takes to make a BITNET magazine
succeed. I will deal with four specific areas of concern for
myself and other editors: how to start an electronic
magazine, how to increase the number of readers of your
magazine, the problems of soliciting submissions, and the
difficulties of distribution. In the final section the
editors of the above magazines discuss what hints they would
give to prospective editors of BITNET magazines.
0 The first step in establishing an electronic magazine
should ideally be planning out what need the magazine will
fill, how it will interest users, and the magazine's format
and contents. Of course, many BITNET magazines have simply
spontaneously generated. For example, NetMonth began simply
as a user maintaining a list of BITNET servers. For this
reason, many editors fail to anticipate the dimensions their
project will reach. Ideally, a magazine should fill a
noticeable void in the network. For example, before FSFnet,
there was no BITNET science fiction forum for authors or
readers, despite a very healthy interest. Any electronic
magazine, to be successful, must both fill a distinct need
by users as well as sparking their interest.
0 If your magazine fills such a need and is well-written,
the readership often takes care of itself. Many editors
will attribute their popularity to the "one user tells two,
and so on" theory. However, this is not always the case. In
addition to word of mouth, another method of gaining
exposure to potential readers is by advertising. Many file
servers are willing to maintain informational files about
electronic magazines, and there are several BITNET news
magazines (NetMonth, Vm/Com to name two) who are very
willing to spread the news of a new BITNET magazine. By
advertising in the proper places and by encouraging users to
spread the word about your magazine, you will be insured of
a healthy readership.
-
9
1
0 Vm-Com Issue 3.5
0 Perhaps the single most critical and pervasive problem
that BITNET electronic magazines face is a common inability
to obtain original submissions. In most cases, users seem
legitimately interested in writing articles, but with most
network users being either students or computing staff,
other priorities often get in the way. This is a serious and
permanent problem for some magazines, as editors cannot be
expected to write entire issues alone. I believe that the
secret to getting submissions is to motivate potential
writers. This might at first seem obvious, but it is very
difficult to put into practise. In FSFnet, I have organized
a special writing project, which has been particularly
productive. Unfortunately, this tactic is specific to
fantasy fiction, and is virtually useless to other types of
magazines. This remains the primary problem area for most
BITNET magazines, including well-established ones, who
still must face this issue daily.
0 Another difficulty which arises after a magazine has been
established is distribution. By their very nature, BITNET
magazines are very large files, and are sent in large
numbers. To avoid abuse of the network, editors must come up
with an efficient method of distribution. Oddly enough,
none of the above magazines are distributed in the same
manner. Nutworks is not distributed at all, but sent to a
number of file servers, where users may request them on
their own. Some magazines are sent through MAILERs, which
cuts down on network load. Many, like FSFnet, are simply
sent directly at odd hours. I would strongly suggest to
anyone thinking of starting a BITNET magazine to look into
the LISTSERV machines. They are the most efficient method
of distribution of large numbers of files, and they have the
added benefit of allowing inter-network mailing, which is a
concern of large, established magazines.
0 After discussing these questions with the above editors,
I asked them what suggestions they would give to prospective
editors. Their responses were not always complimentary,
although I think some insight may be gained from each. Brent
Britton stressed that the editor must be prepared to devote
a large quantity of time to his project, as he has taken the
responsibility of maintaining it, and should honor interest
expressed by the readership. Chris Condon said that the
editor should not simply fish for praise, but actively ask
for criticism from the readership, in order to improve the
magazine and better serve the interests of the readership.
There was some disagreement as to whether a magazine should
adhere to a strict publication schedule. While FSFnet,
Vm/Com, and Nutworks appear (very) irregularly, NetMonth
comes out right on schedule. It appears that whether the
magazine is published in a certain time period is wholly up
to the editor, but that if the magazine has a specified
publication schedule, that schedule should be followed if
possible.
0 10
1
0 Vm-Com Issue 3.5
0 These are, of course, only a few of the lessons the above
editors have learned in the publication of their magazines.
If you have any questions, feel free to address them to
myself. I'm sure that any of the other editors would be
happy to honor reasonable questions posed of them as well.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 11
1
0 Vm-Com Issue 3.5
0 Don't you C?
+ Don't you C?
0 Glenn Sixbury, (VMAQ5@KSUVM)
-
0 Once again, it's soap-box time. I never seem to run out
of opinions about this, that, or the other thing. Since
Michele is pleading again for articles, I have decided to
put my latest crusade in writing. This will probably be my
last article which I write for VM/Com, but then again, I'm
not making any promises.
0 Throughout my college career, I have noticed that people
at the university are not always in tune with the rest of
society. University life seems to be contained in a world
of its own, and for those of us who are eventually thrust
into the "real" world, it can sometimes come as quite a
shock. Supposedly, college is a way of preparing us;
teaching us what we will need to know in our chosen
profession, but sometimes, the training we receive comes up
short of what the business world expects. In particular,
here at Kansas State University, our average Computer
Science graduate goes out into the world armed mainly with
Pascal. Our average Engineering student emerges only
slightly familiar with the Fortran language. This is not to
say that we don't teach other programming languages. It
just means that Pascal and Fortran are the staples. IN MY
OPINION, this is not the way to go.
0 From what I've seen, the "real" world wants people who
know JCL, COBOL, and C. JCL is helpful no matter what kind
of programming work you do. There are still too many places
using some version of an IBM operating system, and knowing
JCL is indispensable. Of course, more and more, a thorough
understanding of the UNIX operating system can be
substituted. Also, it is still true that most of the
business software out there is written in COBOL. If you're
a Computer Science graduate bound for the business world,
forget about PASCAL and ADA (at least for now) and learn
COBOL. For the rest of the programmers, the engineers and
the scientifically-oriented computer science students,
those wishing to do something other than balance the books,
data base work, or write reports, the language to learn is
C. Some of you stated "Of course, I know that," after
reading the last sentence. This article is not aimed at
you. It is aimed at the people who let loose a woeful groan
of non-agreement. These people should read onward.
-
-
12
1
0 Vm-Com Issue 3.5
0 I have always liked C. Maybe I liked it so much because
I heard only good things about it for a long time before I
ever used it, or saw any programs written in it. The first
time I had a chance to work with it, I used it to write an
assembler. As such, it didn't take long for C to impress
me. After working with Fortran, Basic, and Pascal for
years, I was amazed about how many problems the other
languages have which C has overcome. The pure power of the
languages is exciting. One part of C's power comes from its
chameleon nature. It takes on the look of the person
programming it. Fortran programmers produce C code looking
much like Fortran code; Pascal people end up with very
Pascal-like programs. One of the main contributions to this
ability is C's define statement, which allows the programmer
to use a different symbol for C's default symbols, thus
altering the appearance of the code as desired. This
attribute allows more flexability than non-C programmers can
realize.
0 It is not C's flexability that entices the business world
into using the language, but rather, it is C's ability to
get the job done that convinces technical managers it's the
best language to use. By getting the job done, I refer to
the fact that C is not a strongly typed language (like
pascal), it retains structured flow-control constructions
(like While, For, etc.), and it produces extremely efficient
code. Of these qualities, the ability to produce very
efficient code is probably the most important. By efficient
code, I mean that programs written in C usually execute as
quickly as programs written in assembly language. In fact,
C is so efficient that almost all of the UNIX operating
system is written in C. For companies trying to minimize
computer time, this ability of C is indeed an important
quality.
0 I realize I haven't given an irrefutable argument in this
article as to why C is the language to learn, but few people
would enjoy seeing such a lengthy article in an electronic
magazine such as this one. Therefore, I ask you to take my
word that C programmers are in demand in today's technical
end of the business world, or if you'd rather, you could
check it out for yourself. You will find that C is not a
hard language to learn if one already knows Pascal, and it
is worth the effort. To aid in this learning effort, an
absolute necessity is what is commonly referred to as the C
Bible. This is a book entitled The C Programming Language
+ ___ _ ___________ ________
by Brian W. Kernighan and Dennis M. Ritchie. Every other
book about C I have ever read has referenced Kernighan's and
Ritchie's book in its bibliography. As such, it seems to me
that the C Bible is a good place to start learning about C.
-
- 13
1
0 Vm-Com Issue 3.5
0 So much for this month's sermon about the virtues of
learning the language of C. I've tried to point out the
fact that people in the business world want programmers who
can program in C, I tried to give a very short impression as
to why they feel the way they do, and I have encouraged that
the readers of this article who do not yet know the C
language should go out and learn it. I'm sure some of you
will learn C. For those who do, the next time someone asks
"Don't you C?", you can say, "Of course I do."
0 Good luck and good programming.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 14
1
0 Vm-Com Issue 3.5
0 How the Jack O' Lantern Got Its Name
+ How the Jack O' Lantern Got Its Name
0 An Irish Folk Tale
From: Roman Shi, (ROMAN@UCSFVM)
- There was once a very old, miserly man named Jack. He was
even more miserly and selfish than Scrooge. No one in the
town liked him at all, which just made him more bitter and
miserly.
0 Well, one day, Jack took a walk out to a nearby woods and
proceeded to take a nap under a tree. Suddenly, Jack awoke
to find the devil sitting next to him smiling evilly. The
devil had long been following Jack's selfish and greedy ways
and wanted to make a bargain for Jack's soul. Well, of
course Jack was terrified of this prospect, but you don't
get rich by not using your head, so Jack quickly formed a
plan.
0 Jack told the devil that he couldn't make deals on an empty
stomach, so would the devil please climb the tree and get
him a piece of fruit. The Devil agreed and climbed the
tree. Once up in the tree, Jack took out a knife and carved
a cross into the bark of the tree. Now as everyone knows,
the devil can't pass over the sign of the cross, so the
devil was stuck up in the tree indefinitely. The devil was
(needless to say) furious with Jack and threatened Jack ter-
ribly. Jack said that HE would offer the devil a deal: If
the Devil promised never, in anyway to try and take Jack's
soul, he would scratch out the cross so the devil could get
down. The Devil didn't like this at all, but neither did he
like the prospect of being up a tree forever, so the devil
grudgingly agreed to Jack's terms. So saying, Jack
scratched away the cross and let the devil down. The devil
then vanished.
0 Well, Jack died eventually, and his spirit went to heaven,
but upon reaching the Gates to Heaven, his way was barred by
Saint Peter. Saint Peter said that a man who had led such a
narrow and uncharitable life could not be permitted entrance
to Heaven. Jack was shocked, and he begged and pleaded with
Saint Peter to let him in, but still he was denied.
0 Accepting his fate, Jack turned and proceeded to the only
other place that his soul could go, so he proceeded to Hell.
Well, when he got to the Gates of Hell, the devil was there.
When Jack asked admittance, the Devil mockingly told him
that under different circumstances Jack could have entered,
but he reminded Jack of the deal they had made. So say-
ingly, Jack could not stay in Hell, either. Jack had no
place to go, and realized with horror that he must walk the
Earth (in purgatory) forever!
- 15
1
0 Vm-Com Issue 3.5
0 Well, since damned souls cannot be abroad during the light
of day, they must walk the Earth at night. So Jack's soul
wandered the Earth looking for a place to rest. Especially
on Halloween, which you know is slang for "All Hallow's
Eve," the night all souls of the dead roam the earth.
0 Jack wanted to light his way on his endless search, so he
dug up a large turnip, cut out holes in it, and he placed a
lighted candle inside of it, making it into a lantern. He
then went forth, into the night mists searching for a place
that his soul may rest.
0 And that is why we call it to this day, a Jack O' Lantern
(meaning: the Lantern of Jack), and why we see it every
Halloween.
0 It is also said that lighting the Jack O' Lantern, and plac-
ing it in your window, helps light the way for all the lost
and wandering souls on this particular night.
- Happy Halloween
-
-
-
-
-
-
-
-
-
-
-
16
1
0 Vm-Com Issue 3.5
0 OpCodes
+ OpCodes
0 Various and Assorted Creative Minds...
-
BAC Branch to Alpha Centauri
BAH Branch And Hang
BALC Branch And Link Cheeseburger
BB Branch on Bug
BBI Branch on Burned-out Indicator
BBL Branch on Burned-out Lamp
BBLB Branch on Blinking Light Bulb
BCF Branch on Chip box Full
BCIL Branch Creating Infinite Loop
BD Branch to Data
BE Branch Everywhere
BMI Branch on Missing Index
BNA Branch to Nonexistent Address
BNR Branch for No Reason
BOD Branch on Operator Desperate
BPB Branch on Program Bug
BPD Branch on Programmer Debugging
BPO Branch to Power Off
BRA BRanch Anywhere
BRA Branch to Random Address
BRO BRanch to Oblivion
BRT BRanch on Tuesdays
BSM Branch and Scramble Memory
BSO Branch on Sleeping Operator
BTJ Branch and Turn Japanese
BW Branch on When
BW Branch on Whim
CBNC Close, But No Cigar
CC Crappy Control ÕUNIXþ
CCD Choke, Cough and Die
CCR Change Channels Random
CCWR Change Color of Write Ring
CH Create Havoc
CIB Change Important Byte
CIMM Create Imaginary Memory Map
DAUF Delete All Useless Files
DBZ Divide By Zero
DMPE Decide to Major in Physical Education
HF Hide a File
IBR Insert Bugs at Random
ICSP Invert CRT Screen Picture
IDI Invoke Divine Intervention
IDPS Ignore Disk Protect Switch
IEOF Ignore End Of File
IF Invoke Force
-
0 17
1
0 Vm-Com Issue 3.5
0 MBH Memory Bank Hold-up
RAST Rewind And Stretch Tape
RBG Random Bug Generate
RCF Rewind Cabinet Fans
RCR Rewind Card Reader
RDA Refuse to Disclose Answer
RIC Rotate Illogical thru Carry
ROD ROtate Diagonally
ROT Rotate Disk Õfixes broken drivesþ
RST Rewind and Stretch Tape
SCST Switch Channel to Star Trek
SID Switch to Infinite Density
SRD Switch to Random Density
SZD Switch to Zero Density
UCK Unlock Console Keyswitch
-
-
-
-
-
-
-
-
-
-
-
-
-
0 18
|