How to Shutdown Computer automatically Using Firefox Auto Shutdown Add-on

4222061665 632c48d187 o How to Shutdown Computer automatically Using Firefox Auto Shutdown Add onFirefox is the top most world widely used web browser. Because it is handy and have lots of features though its add-on and extension. Sometimes we download files using Firefox and on the same time we need to go for some work. So until we come back the computer waste the energy. In this situation we can use Firefox Auto shutdown the computer when downloads are completed and helps us to save electric power.

4222067729 241056e744 How to Shutdown Computer automatically Using Firefox Auto Shutdown Add on

Auto Shutdown is a cool Firefox add-on which controls your active download and shut down the computer when downloads are completed through is auto executing user script. Not only this but if Firefox is running idle it also shut downs the pc 4222074655 e22c0502ae o How to Shutdown Computer automatically Using Firefox Auto Shutdown Add onautomatically with pre defined shut down time.

If you are using Downthemall Firefox extension for downloading movies, video, music and images from web then you can easily integrate Auto shutdown Firefox extension with downthemall add-on.

Download Auto shutdown Firefox Add-on

The NIST Computer User’s Guide to the Protection of Information Resources

Computer User’s Guide to the Protection of Information

National Institute of Standards and Technology
The National Institute of Standards and Technology (NIST) is
responsible or developing standards, providing technical
assistance, and conducting research for computers and related
systems. These activities provide technical support to government
and industry in the effective, safe, and economical use of
computers. With the passage of the Computer Security
Act of 1987 (P.L. 100-235), NIST’s activities also include the
development of standards and guidelines needed to assure the
cost-effective security and privacy of sensitive information in
Federal computer systems. This guide is just one of three
brochures designed for a specific audience. The “Executive Guide
to the Protection of Information Resources,” and the “Managers
Guide to the Protection of Information Resources” complete the

This guide was written by Cheryl Helsing of Deloitte, Haskins &
Sells in conjunction with Marianne Swanson and Mary Anne Todd of
the National Institute of Standards and Technology.

Today’s computer technology, with microcomputers and on-line
access, has placed the power of the computer where it belongs, in
YOUR hands. YOU, the users, develop computer applications and
perform other data processing functions which previously were
only done by the computer operations personnel. These advances
have greatly improved our efficiency and effectiveness but, also
present a serious challenge in achieving adequate data security.

While excellent progress has been made in computer technology,
very little has been done to inform users of the vulnerability of
data and information to such threats as unauthorized
modification, disclosure, and destruction, either deliberate or
accidental. This guide will make you aware of some of the
undesirable things that can happen to data and will provide some
practical solutions for reducing your risks to these threats.

The statement that “security is everyone’s responsibility” is
absolutely true. Owners, developers, operators and users of
information systems each has a personal responsibility to protect
these resources. Functional managers have the responsibility to
provide appropriate security controls for any information
resources entrusted to them. These managers are personally
responsible for understanding the sensitivity and criticality of
their data and the extent of losses that could occur if the
resources are not protected. Managers must ensure that all users
of their data and systems are made aware of the practices and
procedures used to protect the information resources. When you
don’t know what your security responsibilities are, ASK YOUR
All data is sensitive to some degree; exactly how sensitive is
unique to each business environment. Within the Federal
Government, personal information is sensitive to unauthorized
disclosure under the Privacy Act of 1974. In some cases, data is
far more sensitive to accidental errors or omissions that
compromise accuracy, integrity, or availability. For example, in
a Management Information System, inaccurate, incomplete, or
obsolete information can result in erroneous management decisions
which could cause serious damage and require time and money to
rectify. Data and information which are critical to an agency’s
ability to perform its mission are sensitive to nonavailability.

Still other data are sensitive to fraudulent manipulation for
personal gain. Systems that process electronic funds transfers,
control inventories, issue checks, control accounts receivables
and payables, etc., can be fraudulently exploited resulting in
serious losses to an agency.
One way to determine the sensitivity of data is to ask the
questions “What will it cost if the data is wrong? Manipulated
for fraudulent purposes? Not available? Given to the wrong
person?” If the damage is more than you can tolerate, then the
data is sensitive and should have adequate security controls to
prevent or lessen the potential loss.

Over the past several decades, computers have taken over
virtually all of our major record-keeping functions. Recently,
personal computers have made it cost-effective to automate many
office functions. Computerization has many advantages and is here
to stay; however, automated systems introduce new risks, and we
should take steps to control those risks.
We should be concerned with the same risks that existed when
manual procedures were used, as well as some new risks created by
the unique nature of computers themselves. One risk introduced by
computers is the concentration of tremendous amounts of data in
one location. The greater the concentration, the greater the
consequences of loss or damage. Another example is that computer
users access information from remote terminals. We must be able
to positively identify the user, as well as ensure that the user
is only able to access information and functions that have been
authorized. Newspaper accounts of computer “hackers,” computer
virus attacks, and other types of intruders underscore the
reality of the threat to government and commercial computer

No matter how many controls or safeguards we use, we can never
achieve total security. We can, however, decrease the risk in
proportion to the strength of the protective measures. The degree
of protection is based on the value of the information; in other
words, how serious would be the consequences if a certain type of
information were to be wrongfully changed, disclosed, delayed, or

General Responsibilities
All Federal computer system users share certain general
responsibilities for information resource protection. The
following considerations should guide your actions.

Treat information as you would any valuable asset.
You would not walk away from your desk leaving cash or other
valuables unattended. You should take the same care to protect
information. If you are not sure of the value or sensitivity of
the various kinds of information you handle, ask your manager for

Use government computer systems only for lawful and authorized
The computer systems you use in your daily work should be used
only for authorized purposes and in a lawful manner. There are
computer crime laws that prescribe criminal penalties for those
who illegally access Federal computer systems or data.
Additionally, the unauthorized use of Federal computer systems or
use of authorized privileges for unauthorized purposes could
result in disciplinary action.

Observe policies and procedures established by agency
Specific requirements for the protection of information have been
established by your agency. These requirements may be found in
policy manuals, rules, or procedures. Ask your manager if you are
unsure about your own responsibilities for protection of

Recognize that you are accountable for your activities on
computer systems.
After you receive authorization to use any Federal computer
system, you become personally responsible and accountable for
your activity on the system. Accordingly, your use should be
restricted to those functions needed to carry out job

Report unusual occurrences to your manager.
Many losses would be avoided if computer users would report any
circumstances that seem unusual or irregular. Warning signals
could include such things as unexplainable system activity that
you did not perform, data that appears to be of questionable
accuracy, and unexpected or incorrect processing results. If you
should notice anything of a questionable nature, bring it to your
manager’s attention.

Security and Control Guidelines
Some common-sense protective measures can reduce the risk of
loss, damage, or disclosure of information. Following are the
most important areas of information systems controls that assure
that the system is properly used, resistant to disruptions, and

Make certain no one can impersonate you.
If a password is used to verify your identity, this is the key to
system security. Do not disclose your password to anyone, or
allow anyone to observe your password as you enter it during the
sign-on process. If you choose your own password, avoid selecting
a password with any personal associations, or one that is very
simple or short. The aim is to select a password that would be
difficult to guess or derive. “1REDDOG” would be a better
password than “DUKE.”
If your system allows you to change your own password, do so
regularly. Find out what your agency requires, and change
passwords at least that frequently. Periodic password changes
keep undetected intruders from continuously using the password of
a legitimate user.

After you are logged on, the computer will attribute all activity
to your user id. Therefore, never leave your terminal without
logging off — even for a few minutes. Always log off or
otherwise inactivate your terminal so no one could perform any
activity under your user id when you are away from the area.

Safeguard sensitive information from disclosure to others.
People often forget to lock up sensitive reports and computer
media containing sensitive data when they leave their work areas.
Information carelessly left on top of desks and in unlocked
storage can be casually observed, or deliberately stolen. Every
employee who works with sensitive information should have
lockable space available for storage when information is not in
use. If you aren’t sure what information should be locked up or
what locked storage is available, ask your manager.

While working, be aware of the visibility of data on your
personal computer or terminal display screen. You may need to
reposition equipment or furniture to eliminate over-the-shoulder
viewing. Be especially careful near windows and in public areas.
Label all sensitive diskettes and other computer media to alert
other employees of the need to be especially careful. When no
longer needed, sensitive information should be deleted or
discarded in such a way that unauthorized individuals cannot
recover the data. Printed reports should be finely shredded,
while data on magnetic media should be overwritten. Files that
are merely deleted are not really erased and can still be

Install physical security devices or software on personal
The value and popularity of personal computers make theft a big
problem, especially in low-security office areas. Relatively
inexpensive hardware devices greatly reduce the risk of equipment
loss. Such devices involve lock-down cables or enclosures that
attach equipment to furniture. Another approach is to place
equipment in lockable cabinets.
When data is stored on a hard disk, take some steps to keep
unauthorized individuals from accessing that data. A power lock
device only allows key-holders to turn on power to the personal
computer. Where there is a need to segregate information between
multiple authorized users of a personal computer, additional
security in the form of software is probably needed. Specific
files could be encrypted to make them unintelligible to
unauthorized staff, or access control software can divide storage
space among authorized users, restricting each user to their own

Avoid costly disruptions caused by data or hardware loss.
Disruptions and delays are expensive. No one enjoys working
frantically to re-enter work, do the same job twice, or fix
problems while new work piles up. Most disruptions can be
prevented, and the impact of disruptions can be minimized by
advance planning. Proper environmental conditions and power
supplies minimize equipment outages and information loss. Many
electrical circuits in office areas do not constitute an adequate
power source, so dedicated circuits for computer systems should
be considered. Make certain that your surroundings meet the
essential requirements for correct equipment operation. Cover
equipment when not in use to protect it from dust, water leaks,
and other hazards.

For protection from accidental or deliberate destruction of data,
regular data backups are essential. Complete system backups
should be taken at intervals determined by how quickly
information changes or by the volume of transactions. Backups
should be stored in another location, to guard against the
possibility of original and backup copies being destroyed by the
same fire or other disaster.

Maintain the authorized hardware/software configuration.
Some organizations have been affected by computer “viruses”
acquired through seemingly useful or innocent software obtained
from public access bulletin boards or other sources; others have
been liable for software illegally copied by employees. The
installation of unauthorized hardware can cause damage,
invalidate warranties, or have other negative consequences.
Install only hardware or software that has been acquired through
normal acquisition procedures and comply with all software
licensing agreement requirements.

Ultimately, computer security is the user’s responsibility. You,
the user, must be alert to possible breaches in security and
adhere to the security regulations that have been established
within your agency. The security practices listed are not
inclusive, but rather designed to remind you and raise your
awareness towards securing your information resources:

Keep it in a secure environment
Keep food, drink, and cigarettes AWAY from it
Know where the fire suppression equipment is located and know
how to use it

Keep unauthorized people AWAY from your equipment and data
Challenge strangers in your area

Never write it down or give it to anyone
Don’t use names, numbers or dates which are personally
identified with you
Change it often, but change it immediately if you think it has
been compromised

Don’t allow unauthorized access to your files and data
NEVER leave your equipment unattended with your password
activated – SIGN OFF!

Don’t use unauthorized software
Back up your files before implementing ANY new software

If the data or information is sensitive or critical to your
operation, lock it up!

Keep duplicates of your sensitive data in a safe place, out of
your immediate area
Back it up as often as necessary

Tell your manager if you see any unauthorized changes to your
Immediately report any loss of data or programs, whether
automated or hard copy

For Additional Information
National Institute of Standards and Technology
Computer Security Program Office
A-216 Technology
Gaithersburg, MD 20899
(301) 975-5200

For further information on the management of information
resources, NIST publishes Federal Information Processing
Standards Publications (FIBS PUBS). These publications deal with
many aspects of computer security, including password usage, data
encryption, ADP risk management and contingency planning, and
computer system security certification and accreditation. A list
of current publications is available from:

Standards Processing Coordinator (ADP)
National Computer Systems Laboratory
National Institute of Standards and Technology
Technology Building, B-64
Gaithersburg, MD 20899
Phone: (301) 975-2817

Satellite Control, by Ninja Squirrel & Logan-5

[ Hacker Supreme’s – Hacker Directory V#22 ]
[ Compiled & by: Ninja Squirrel & Logan-5 ]

This article will deal with Satellite hacking, CB info, and car phone systems.

Satellite Control

Companies try to build satellites to last for as long a time as possible.
Unfortunately, for the companies, things in space can happen unexpectantly and
suddently. Take that satellite released by the space shuttle. It’s orbit
carried it way off the correct altitude. The company’s only hope was to fire a
rocket on it in order to bring it to the correct place.
Now think…how does one on the ground fire a rocket in space? Radio!
Gee, if the company could change the orbit, maybe we can too. Sound
Of course we were not the first to think of this. The satellite companies
have worried about this for a long time. There are stories about top secret
codes, frequencies, and protocols required to ‘nudge’ one of those babies.
The only problem is that-there is little information about this out there.
If you have any info, make a text file, and let others know of your knowledge.
But let me tell you all I know about a simple satellite whose telemetry is
known well.
OSCAR 6 was a satellite sent up in order to take in amateur signals
between 145.9 and 146.0 MHz, and re-transmit them between 29.45 and 29.55 MHz
using a transponder. Early in 1976, OSCAR 6 began to have battery problems.
The telemetry allowed the ground command stations to shut the satellite off at
regular intervals to prolong the useful life of the satellite.
Now we know the satellite sent out telemetry reports at a certain
frequency (OSCAR 7 was 29.502 and 145.972 MHz). And it sent them out in the
form of Morse code at about 20 wpm. Information rate of spin, power use, and
temperature were sent out at 20 wpm. This seems to suggest that the control
might have also used morse code. Strangely enough, there was never any
information in the American Radio Relay League magazine about just how they
control the OSCAR satellites. (Hams know what’s safe and what’s crazy also)

Suggestions: Don’t overlook RTTY when trying to Satelhack (Satellite
hacking). Also, chances are the owners will figure out what you did, so
‘downing’, the ultimate for a satelhack, is pretty difficult.

[ Infinity-Cartel Network ]
[ The Cartel Adventure/AE/Hack BBS 5.5 meg — 206-825-6236, or 206-939-6162 ]
[ Infinity’s Edge Adventure/AE/Cat/Hack 10 meg BBS ———— 805-683-2725 ]

Review of Federal Agency Computer Security and Privacy Plans



Sensitive information and information resources have become
increasingly important to the functioning of the federal
government. The protection of such information is integral to
the government serving the public trust. Concern that federal
agencies were not protecting their information caused Congress to
enact Public Law 100-235, “Computer Security Act of 1987” (the
Act). The Act reaffirmed the National Institute of Standards and
Technology’s (NIST) computer security responsibilities. These
responsibilities include developing standards and guidelines to
protect sensitive unclassified information. Other
responsibilities include providing new governmentwide programs in
computer security awareness training and security planning.

The Act required federal agencies to conduct educational programs
to increase staff awareness of the need for computer security.
The first-year activity included agencies identifying their
computer systems containing sensitive information. These
agencies prepared and submitted security plans for those systems
to the NIST and National Security Agency (NSA) review team for
advice and comment. This document summarizes a report on the
review of the computer security and privacy plans that were
submitted by federal agencies.

How The Reviews Were Conducted

The Office of Management and Budget (OMB) issued OMB Bulletin 88-
16, “Guidance for Preparation and Submission of Security Plans
for Federal Computer Systems Containing Sensitive Information,”
to guide agencies on preparing and submitting computer security
plans. The bulletin specified the information that was to appear
in each plan. The bulletin further requested that agencies
identify systems as major application or general ADP support
systems. Finally, the bulletin provided the agency the option of
identifying any needs for guidance or technical support. This
option also included making any comments the agency thought
appropriate. Although a four-part format appeared, agencies were
able to use latitude as long as all pertinent information was
present. This permitted agencies with existing programs to
submit current related documents. Submission of an agency
overview was optional and most agencies chose not to provide one.

The joint NIST/NSA review team examined 1,583 plans for 63
federal civilian agencies and 27,992 plans from 441 Department of
Defense (DoD) organizations. Most DoD submissions consisted
mainly of accreditation documentation prepared for other computer
security planning purposes. During the review process, the
review team recorded data about the systems for analysis. The
conclusions made in this report stem principally, but not
exclusively, from the civilian agency submissions.

Major Findings

The review team arrived at a number of conclusions about the
plans and the plan review process, seeing both many positive
signs and some areas for improvement. These findings include:

o The civilian agency CSPPs basically conformed with the
guidance given by OMB Bulletin 88-16. Many controls to
protect sensitive systems were already in place or
planned. These controls appeared consistent with
identified system functions, environment, and security
needs. However, some respondents appeared to have just
“checked the boxes,” perhaps presenting a falsely
optimistic picture.

o Many agencies appeared to report on isolated systems
rather than all systems subject to the Computer
Security Act and OMB Bulletin 88-16.

o Agencywide guidance on how to prepare the plans was not
clear. There was also some question whether a high-
level official reviewed the plans. Also unclear is the
distribution of agency-level computer security policy
and guidance. Further, most plans did not reflect the
joint involvement of ADP, computer security, and
applications communities in computer security planning.

o Significantly, the plans rarely addressed the security
concerns on networking, interfaces with other systems,
and the use of contractors and their facilities. This
may reflect a general confusion about the boundaries
and limits of responsibility for a given system.

o Many plans equated sensitivity only with privacy or
confidentiality and did not fully address requirements
for integrity and availability.

o Most plans did not communicate an appreciation for the
role of risk management activities in computer security

o Although most agencies said they had computer security
awareness and training, many did not show that all
applicable employees received periodic training.

o Finally, the CSPP submission and review effort raised
the level of federal awareness regarding the need to
protect sensitive information and the importance of
computer security planning.

Recommendations for Agencies

Based on the needs that became apparent during the plan review,
the review team recommends the following:

o Agency management should ensure that computer security
has the highest level of management involvement. This
involvement is also important in the computer security
planning process. Computer security benefits from the
multiple perspectives of and input from agency
information resources management, computer security,
and functional, user, and applications personnel.

o Agency management should identify and describe the
security needs of their systems which contain sensitive

o Agency management should recognize the importance of
computer security and its required planning. This
recognition should be aggressively communicated to
their staffs, perhaps using their computer security and
awareness training programs as one of the vehicles.

o Agencies should incorporate computer security planning
with other information systems planning activities.

o Agencies should consider the protection requirements
for integrity and availability on an equal basis with
that of confidentiality.

o Agencies should assess risks, and select and implement
realistic controls throughout the system life cycle.
This involves awareness of technology changes with
regard to system hardware and software. This awareness
also requires a knowledge of new technology and new
methods for protecting and recovering from system
threats. In addition, agencies should fully document
in-place controls to ease periodic reevaluation,
internal audit, and oversight agency review.

o Agencies should implement certification and
accreditation programs. There is a lack of awareness
of guidance regarding certification and accreditation,
including FIPS PUB 102, “Guideline for Computer
Security Certification and Accreditation.” There is
also a lack of knowledge of the certification
requirements in OMB Circular A-130, “Management of
Federal Information Resources.” Agencies may use OMB
Circular A-130 as the basis for these programs.

o Agencies should clarify the boundaries and limits of
responsibility for each system, and should include, in
any planned risk assessment activity, full
consideration of the telecommunications and networking
environment and relationships with contractors and
other organizations.

o Agencies should stress security awareness and training
for their employees. This includes all employees
involved in the design, management, development,
operation, or use of federal computer systems
containing sensitive information.

o Agencies should develop computer security policy and
operative guidance. Such policy and guidance should
fully reflect and comprehensively address an
encompassing view of computer security. The Computer
Security Act, OMB Circular A-130, and OMB Bulletins 88-
16 and 89-17, “Federal Information Systems and
Technology Planning,” and their successors all contain
this view. The policy should directly address the full
scope of computer security planning and risk management
activities. It must incorporate an application system
perspective and give more detailed consideration to
confidentiality, integrity, and availability protection

What NIST is Doing

NIST is evolving a strategy for helping federal agencies in
identifying and protecting sensitive information systems. This
strategy shifts emphasis to the implementation of computer
security plans, particularly those developed under OMB Bulletin
88-16. It provides for visits by OMB, NIST, and NSA staff. This
group will provide direct comments, advice, and technical aid
focused on the agency’s implementation of the Act.

In addition to the agency visits described above, NIST has
initiated the following computer security projects to help
agencies more easily and effectively comply with the Computer
Security Act:

o NIST will develop standardized specifications and
language for federal government computer security
services contracts.

o NIST will develop a guidance document on computer
security in the ADP procurement cycle.

o NIST has recently published guidance on the use of
Trusted Systems.

o NIST will develop guidance on computer security

o NIST has developed, and will continue to operate, a
computer incident response center in order to address
viruses, worms, and other malicious software attacks.

o NIST will support and coordinate computer security
resource and response centers nationwide.

o NIST will enhance and operate the National Computer
Systems Laboratory (NCSL) Computer Security Bulletin
Board System.

o NIST will operate the NIST/NSA Risk Management
Laboratory and prepare further guidelines on risk

o NIST will develop guidance and recommendations on
assuring information integrity in computer systems.

In addition to the above plans, NIST has already developed a
number of guidelines and other resources to help federal managers
secure their computer systems.

Future Directions

Federal managers have computer security requirements that are
similar to their counterparts in the private sector. We believe
that private sector organizations can learn and benefit from the
federal experience in implementing the Computer Security Act. In
both environments, a vigorous computer security awareness program
is important at all levels in the organization. Also, in both
environments, the active involvement of user, management, ADP,
and computer security communities in computer security planning
could help end some of the existing and potential barriers to
effective computer security. Such collective involvement would
also help ensure cost-effective control measures commensurate
with system function, system sensitivity, security requirements,
and analyzed and considered risks.

Agencies need to be aware of developments taking place in the
national and international standards arena on system
interoperability and data interchange. These developments will
impact information system product availability, protection
requirements, and protection alternatives as agencies do their
near-, mid-, and long-term IRM and computer security planning.

Finally, because agency awareness of problems is fundamental to
the solution, this project has been valuable. Computer security
officers say that the CSPP preparation and review activity has
raised the level of awareness in all parts of their organizations
and has made it easier for them to promote computer security.
The CSPP review project significantly raised the level of federal
awareness about the protection of sensitive information and the
importance of computer security planning. In the final analysis,
this contribution may be among the most meaningful results of the

The complete report of the CSPP review project will be published
as an NIST Interagency Report (NISTIR), and will be available
from the National Technical Information Service (NTIS) U.S.
Department of Commerce, 5285 Port Royal Road, Springfield,
VA 22161. Telephone: (703) 487-4650 FTS 737-4650. For
information about the report findings, contact Dennis Gilbert,
National Institute of Standards and Technology, A216, Technology
Building, Gaithersburg, MD 20899. Telephone: (301) 975-3872.

Downloaded From P-80 International Information Systems 304-744-2253

The Milnet File by Brigadier General Swipe/Dispater

][ ][
][ Finally it’s here………. ][
][ /\/\ /\/\ ][
][ / \ / / ][
][ \/\/\/il\/\/et ][
][ by: ___ __ ______ ][
][ __) / _` / ____/ ][
][ __)rigadier \__eneral / /wipe ][
][ ______________________/ / ][
][ /_______________________/ ][
][ (aka: Dispater) ][
][ ][
][ Thanx to: no one! G.D.I. (God Damn Independant) ][
][ ][
First of all Milnet is a system used by the Air Force and the Pentagon for
communication use. You know you are on milnet when you see that infamous
TAC login xxx. Milnet is run out of the University of Southern California,
(this might give some of you some ideas who live around there).
Logon Info
The Milnet number is 1-800-368-2217.
The ISI MASTER DIAL UP IS 213-306-1366.
This is a more tricky logon procedure but if you got balls, you’re using a
trunk box, or you are just S-T-U-P-I-D here goes:
1> call 213-306-1366
2> when the phone stops ringing you are connected
3> enter location number (9 digits) + 1 or 0
4> hang up and it will call you
5> pick up the phone and hit the ‘*’ on your phone
6> hit a carriage return on the computer
7> at the ‘what class?’ prompt hit RETURN!!!
8> then a ‘go’ prompt will appear and log on as you would the 800 number.
If you have trouble connecting try 300 bauds instead of 1200. It’s a bite in
the ass but, sometime the connection will fuck up if you don’t.
When you first connect you will see:
CALL NIC 1-800-235-3155 FOR HELP
WRPAT TAC 113 #:36
(you type)
@o 1/103
YOU ALWAYS TYPE @o then other connections are:
ISIA 3/103
ISIB 10:3/52
ISID 10:0/27
ISIF 2/103
VAX A 10:2/27
Next you will see a ‘USER-ID’ promt. The first 4 characters vary but it is
is always followed by a ‘-‘ and what ever connection you choose.
User-Id: (example) CER5-ISIE or MRW1-ISIE
The first three letters are the initials of the user followed by a random
number (1-9).
Access Code: (example) 2285UNG6A or 22L8KK5CH
An access code will never contain a ( 1, 0, G, Z).
The first 3 letters will be SAC. This stands for Strategic Air
Followint that is a ‘.’ Then the squadron number and the prime mission.
In this case ‘305AREFW’, (305TH AIR REFULING WING). Then a ‘-‘ and the
a fancey name for the motor pool. I’ll try and get a list of these there are
tons of names.
The password will not be echoed back and should be entered after a
the username.
The new user password as a default is: NEW-UZER-ACNT
+————-+ and what they are for
copied direcly from the help manual
ADUTY aids in management of additional duty assignments.
(International help – use the ? and keys, HELP.)
ARCHIVE requests files to be stored on tape for later retreval.
CHAT Provides near real time communication between terminal users on the
same host computer.
(Use ? with CHAT.)
DAILY Executive appointment scheduleing program
DCOPY Handles output on DIABLO and XEROX printers
EMACS Powerful full-screen text editor
FOLLOW Suspense follow up program
FTP provides file transfer capabilites between host computers
FKEYS allows user to define function key (real spiffaruni)
HELP the command used by stupid generals or hackers that have never used
milnet before
NCPCALC spreadsheet program
PHOTO saves transcripts of sessions
REMIND sends user-created reminders
RIPSORT a sophisticated data sorting program
(Described in SAC’s User manual (sorry))
SCRIBE a powerful text formatter for preparing documents.
(ISI’s manual, SCRIBE manual – soon on MILNET V.2)
SPELL text file spelling checker.
(HELP at TOPS-20 and directory international help -?)
SUSCON allows the creating, sending, and clearing of suspenses.
(international help – ? and , HELP command)
TACOPY used for printing hard copies of files
(international help – ?)
TALK pretty much the same as chat.
TIPCOPY predecessor of TACOPY
TN Tel-Net provides multi-host access on MILNET.
(HELP at TOPS-20 and directory,
international help – use ? and )
XED line oriented text editor.
(HELP at TOPS-20 and directory)
The Milnet ID card If you should be trashing somewhere and find a card that
+——————+ looks like this, then save it. (it will be blue & white)
/ \ It’s also wallet sized so you may
HOST USC-ISIE wish to mug someone who you know
HOST ADMINISTRATOR GORDON,VICKI L. is in the air force..haha!
————————————— (just kidding!)
CARD 118445

How to Connect OMRON 3S4YR-HSR4 to your PC

How to Connect OMRON 3S4YR-HSR4 to your PC

Brown = RDT – LPT Pin 11
Red = RCP – LPT Pin 12
Orange = CLS – LPT Pin 13
Yellow = +5V – LPT Pin 2-9
Green = Ground – LPT Pin 25

Note that you can *not* just solder pins 2-9 together, because that would
most likely *damage* your printer port. Use 8 pieces of 1N4148 switch diodes
connected like this:

+–|<--o Pin 2 | +--|<--o Pin 3 . . +--|<--o Pin 9 | +-------------- +5V to Yellow cable of card reader. I think you get the picture..... After that you simply need three 10 kOhm resistors that are to be connected to the +5V supply as pull-ups for the datalines RDT, RCP and CLS. +---%%%---o Pin 11 - Brown | +---%%%---o Pin 12 - Red | +---%%%---o Pin 13 - Orange | +-------------> To yellow cable of the reader – +5V pull-up.

That should be all you need to know about connecting the card reader to
your PC. Now run the enclosed software, MAGCARD4.EXE and tell the program
what printer port the reader is attached to. LPT1, LPT2 or LPT3. LPT1 is the
one located at $3BC, LPT2=$378, LPT3=$278. If you enter the wrong port, the
program will hang and wait for a card forever, so make sure you select the
right one. If all goes well, the card data will be read and displayed on
screen in both binary and normal view. Card data will also be saved on disk
for you…..

Greetz, Zaphod Beeblebrox /// Beeblebrox Industries Unlimited.
Internet: /