|
|
HALIFAX AREA
PERSONAL COMPUTER SOCIETY NEWSLETTER MAY 1996
Meets 4th Sunday of each month, 7:00 pm
Note Change of Location
Veteran's Memorial Building, Room 1613A
Corner of Robie and Jubilee Road, Halifax, N.S.
26 MAY MEETING
Opening Topics - Windows Feature
- Question and Answer
Feature Event - Internet Routing and Addresses
- Speakers from the Society
IN THIS MONTH'S ISSUE:
Announcements
Next meeting, other groups
What Do We Need To Know About Computers?
One perspective
The Upgrade Corner
Internet Tools - Traceroute
What does this program do?
Where is this Coming From Anyway?
Internet Country codes
The Newsletter
A few notes about what goes into this document
Meeting Schedule 95/96
GENERAL INFORMATION
This document is mailed to all paid up members and to anyone
who has attended a meeting within the past three months. Yearly
membership dues are $15.00. The text of the newsletter is available on
Chebucto Community Net and local bulletin boards.
Society Mailing Address -
P.O. Box 185 Stn. Main, Dartmouth N.S., B2Y 3Y3
Executive
Chairperson - David Potter
Vice-Chair - Bill Marchant
Secretary/Treasurer/Newsletter Editor -
Colin Stuart
Disk Librarian - Thayne MacLean
and also Norman DeForest, Henry Hill, Arthur Layton, Rob MacCara,
Andy Cornwall, George Richards, and Diane Smith
ANNOUNCEMENTS
There are not much in the way of announcements this month. I have managed
to get the newsletter out closer to the normal time this month. The
holiday may delay the mail a bit though. Hope everyone gets their copy
on time.
Last Planning Meeting
The last planning meeting was held on Monday, 6 May at the Veterans Memorial
Building. There were only a few people in attendance, namely Thayne
MacLean, David Potter, Diane Smith, and Henry Hill.
Next General Meeting
The feature event for the next general meeting will consist of a
presentation on Internet addressing and routing. We are planning to do a
live demonstration on some aspects of this. There are a couple of
articles this month dealing with this subject.
Meeting Facilities
The regular monthly meetings of the Society are held in Room 1613A of
the Veteran's Memorial Building (VMB) at the corner of Robie Street and
Jubilee Road, Halifax. The planning meetings will be held in a
different room in the same building. These facilities are provided at no
cost to the Society.
There is underground parking available at the VMB at a cost of $1.10 /hour.
For anyone who wishes to use it, the elevator from the parking area takes
you directly to the lobby. The parking bill is paid to the commissioner
in the lobby when you go to return to your car. There is also parking
available on the nearby streets. Both Robie Street and Summer Street
have parking meters, and at our meeting time on Sunday evening they are
most likely to be uncontested by others.
Society Mailing Address
Please note the mailing address for the Society:
P.O. Box 185, Stn. Main
Dartmouth, N.S.
B2Y 3Y3
Membership Expiry Dates
The membership expiry dates are printed in the upper right corner of
your newsletter mailing label. If you wish to continue to receive this
newsletter and know what interesting meetings are coming up, you either
have to renew ($15 per year) or come to the meetings and put your name on
the list that is passed around at the meetings.
DELPHI
The Metro Halifax Delphi Developers Group meets on the first Tuesday of
each month at 7:00pm. The meetings are held at the CCL Group Building
2669 Dutch Village Road, Halifax.
Further information may be obtained from Dave Hackett at 835-3894,
CIS:71650,2646 or from Carey Rolfe at 462-4551 or e-mail rolfe@ra.isisnet.com.
OS/2 Users Group
This group meets sometimes on the second Wednesday of the month at Purdy's
Wharf Tower Two. For information contact Donovan Long at 422-1975 or by
e-mail at tsst@isisnet.com.
Advertising and Want Ads
We don't charge for small individual want ads. Any Society member or other
interested person with some computer related item that they wish to sell,
trade, or give away can contact the editor to place an ad in the
newsletter. We would expect that more commercially oriented advertising
provide the Society with some remuneration for carrying the ad.
An ad will normally only appear once but let me know if you need it
repeated. Ads can be given to me at meetings or give me a call two weeks
to ten days before the next general meeting (newsletter deadline).
WHAT DO WE NEED TO KNOW ABOUT COMPUTERS?
by Bill Marchant
The first IBM PC which I bought, (over ten years ago now) came with
enough books to keep me reading for most of a weekend. I understood
practically nothing of what I read, but by Monday morning I knew how to
put a disk in the A: drive, and boot the computer. (Of course there was
no hard drive).
CONFIG.SYS and AUTOEXEC.- BAT files were a complete mystery, and since
they were not necessary (they still aren't), I tried to ignore them.
This turned out to be impractical, since every time I wanted to do
something slightly different I would read a line like "Add the following
line to your AUTOEXEC.BAT file...". After a while I understood something
about DRIVERS, PATHs, TSRs, The DOS environment and such like. Computing
became easier while it also became more complicated.
The first version of DOS which I used was 2.1. IBM and MicroSoft kept
people like me on the edge of anticipation by bringing out new versions
of DOS just a little faster than we were capable of absorbing them,
there was always a new command, or a new way of using an old one. There
was an element of competition between me and my computing friends to
understand all this stuff more fully. We learned things like what
happens when a disk is formatted; how does DOS know where to put the data
when it writes to a disk; and what is the difference between expanded
memory and extended memory.
It sort of put things in perspective one day when someone described me
as a "power user". I knew that wasn't true, but at the same time I
realized that I was being asked to help a lot of other computer users
with problems. Someone would need a Macro Menu for Lotus 123, or someone
else lost a file that "was there yesterday, but now can't be found".
Over time I have come to believe that every computer user needs to know
something about the workings of the machine and its programs. At the
same time it is utterly impossible for any one person to know
everything. There is a basic level of knowledge however which everyone
can benefit from. Some knowledge will come from just using the machine
and its programs, and the rest must be learned from books or courses.
There is a strong tendency for groups like MicroSoft to down-play the
need for knowledge. WINDOWS 95 SECRETS is a 900 plus page book which
contains the following quote on page 1; "MicroSoft has decided that the
Windows 95 operating system should be 'discoverable' without a manual."
The remainder of the book is filled with things which most of us would
never discover even if we spent most of the rest of our lives trying to
discover them. A book like Windows 95 Secrets tells much more than most
users will ever need to know, but much of it is essential knowledge for
keeping out of trouble when programs act in a way which we did not expect.
The manual I got with Windows 95 is about 4 mm thick. The section on
DEFRAGGING contains one paragraph consisting of 50 words. It says the
computing equivalent of "If you need to oil your lawn mower you should
oil it." Windows 95 Secrets which is a full 50 mm thick, has a whole
chapter on disk storage, and spends four pages on defragging alone. Even
Secrets assumes some previous knowledge on the part of the user. If I
had not had previous DOS knowledge, some of the information given would
have seemed very strange.
Defragging is just one example of where current computer education for
users is lacking. What about Networking, Modems, Using DOS programs in
Windows (and why), and File compression on a disk. There are many more.
Knowing how to use a computer is something like knowing how to drive a
car, but it is still far more complicated. Car drivers used to have to
be able to change tires, clean spark plugs, tow another car out of the
ditch and start the engine with a hand crank. But cars have been under
development for over 100 years. Many new drivers know little more than
how to start the engine, press the gas and brake pedals and steer. The
rest of car care is left to the mechanic at the garage. The history of
personal computers as we know them is much shorter, and basic diagnostic
knowledge is still a valuable if not essential tool for every computer
user. We still need to know the computer equivalent of blowing out a
gas line, rotating tires and changing the oil.
Some day perhaps, there will be a computer which will have the
equivalent of "turn the key, press the gas pedal and steer", but I doubt
it. After all there are 12 Function keys on a keyboard, and then there
are up to three buttons on most mouses. Already that is more complicated
than a car. Thank goodness computers are not as dangerous to use.
THE UPGRADE CORNER
by Colin Stuart
I will have an article ready for next month about a recent upgrade that
I did one Saturday. In the meantime, Bill Marchant provided me a note
regarding PKZIP, which I have included below for those of you who have
not heard of this.
A file called PKZIP300 with various extensions is available for
downloading from some boards and web sites. DO NOT DOWNLOAD OR USE THIS
FILE UNDER ANY CIRCUMSTANCES. When this file is executed, it
WIPES THE HARD DRIVE CLEAN, AND AFFECTS MODEMS AT 14.4 & HIGHER.
PKZIP300 is a trojan horse. It is a fake version of what might be the
next version of the famous and well regarded PKZIP series of compression
programs. Its sole purpose is to destroy hard drives, which it
evidently does with great efficiency.
INTERNET TOOLS - TRACEROUTE
Edited by David Potter
Traceroute is normally considered to be a systems administrator tool
rather than a user application. Traceroute performs an analysis of the
route packets between two internet hosts. It is extremely useful for
isolating network problems / congestion.
Internet communications take place by routing packets on a step-by-step
transmission to a remote computer. Each computer receives packets,
interprets them for correctness and if the packet is not addressed to
the local machine will attempt to forward the packet to another internet
address that may be the ultimate destination or another step in this
stepwise transmission of packets of data.
Traceroute prints each step in the communication from a local system to a
remote internet system. It also prints the amount of time needed to
communicate with a particular component computer in the path to the
remote destination. If the time to communicate to a new step in the
route suddenly increases significantly or if packets are not routinely
return from a step in the route, a source of internet congestion or
error conditions has been isolated.
Traceroute in combination with Ping can be very useful in dissecting the
transmission path between two internet hosts. (Editors note: Ping which
is available as a Winsock application will report whether an Internet
site is 'alive' and responding to inquiries.)
Traceroute is executed by specifying a remote host name or host address.
It will list each hop and the amount of time necessary to transmit and
receive and "echo" packet from that host.
The Internet is a large and complex aggregation of network hardware,
connected together by gateways. Tracking the route one's packets follow
(or finding the miscreant gateway that's discarding your packets) can be
difficult. Traceroute utilizes the IP protocol `time to live' field and
attempts to elicit an ICMP TIME_EXCEEDED response from each gateway along
the path to some host.
The only mandatory parameter is the destination host name or IP number.
The default probe datagram length is 38 bytes, but this may be increased
by specifying a packet size (in bytes) after the destination host name.
Traceroute attempts to trace the route an IP packet would follow to some
internet host by launching UDP probe packets with a small ttl (time to
live) then listening for an ICMP "time exceeded" reply from a gateway.
We start our probes with a ttl of one and increase by one until we get an
ICMP "port unreachable" (which means we got to "host") or hit a max
(which defaults to 30 hops and can be changed with the -m flag).
Three probes are sent at each ttl setting and a line is printed showing
the ttl, address of the gateway and round trip time of each probe. If
the probe answers come from different gateways, the address of each
responding system will be printed. If there is no response within a 3
sec. timeout interval (changed with the -w flag), a "*" is printed for that
probe. We don't want the destination host to process the UDP probe
packets so the destination port is set to an unlikely value (if some clod
on the destination is using that value, it can be changed with the -p flag).
Sometimes traceroute returns two identical entries perhaps due to a buggy
kernel on the 2nd hop system that forwards packets with a zero ttl (a bug
in the distributed version of 4.3BSD).
In some cases you have to guess what path the packets are taking
cross-country since some networks don't supply address-to-name translations.
Ie. 131.119.2.5 (131.119.2.5) 59 ms 59 ms 39 ms
A interesting example is:
traceroute allspice.lcs.mit.edu. traceroute to
allspice.lcs.mit.edu (18.26.0.115), 30 hops max
1 helios.ee.lbl.gov (128.3.112.1) 0 ms 0 ms 0 ms
2 lilac-dmc.Berkeley.EDU (128.32.216.1) 19 ms 19 ms 19 ms
3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 19 ms 19 ms
4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 19 ms 39 ms 39 ms
5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 20 ms 39 ms 39 ms
6 128.32.197.4 (128.32.197.4) 59 ms 119 ms 39 ms
7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 39 ms
8 129.140.70.13 (129.140.70.13) 80 ms 79 ms 99 ms
9 129.140.71.6 (129.140.71.6) 139 ms 139 ms 159 ms
10 129.140.81.7 (129.140.81.7) 199 ms 180 ms 300 ms
11 129.140.72.17 (129.140.72.17) 300 ms 239 ms 239 ms
12 ***
13 128.121.54.72 (128.121.54.72) 259 ms 499 ms 279 ms
14 *** 15 *** 16 *** 17 ***
18 ALLSPICE.LCS.MIT.EDU (18.26.0.115) 339 ms 279 ms 279 ms
Note that the gateways 12, 14, 15, 16 & 17 hops away either don't send
ICMP "time exceeded" messages or send them with a ttl too small to reach
us. 14 - 17 are running the MIT C Gateway code that doesn't send "time
exceeded". The silent gateway 12 in the above may be the result of a
bug in the 4.[23]BSD network code (and its derivatives): 4.x (x <= 3)
sends an unreachable message using whatever ttl remains in the original
datagram. Since, for gateways, the remaining ttl is zero, the ICMP "time
exceeded" is guaranteed to not make it back to us.
The behavior of this bug is slightly more interesting when it appears on
the destination system:
1 helios.ee.lbl.gov (128.3.112.1) 0 ms 0 ms 0 ms
2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 19 ms 39 ms
3 lilac-dmc.Berkeley.EDU (128.32.216.1) 19 ms 39 ms 19 ms
4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 19 ms
5 ccn-nerif35.Berkeley.EDU (128.32.168.35) 39 ms 39 ms 39 ms
6 csgw.Berkeley.EDU (128.32.133.254) 39 ms 59 ms 39 ms
7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * *
13 rip.Berkeley.EDU (128.32.131.22) 59 ms ! 39 ms ! 39 ms !
Notice that there are 12 "gateways" (13 is the final destination) and
exactly the last half of them are "missing". What's really happening is
that rip (a Sun-3 running Sun OS3.5) is using the ttl from our arriving
datagram as the ttl in its ICMP reply. So, the reply will time out on
the return path (with no notice sent to anyone since ICMP's aren't sent
for ICMP's) until we probe with a ttl that's at least twice the path
length. I.e., rip is really only 7 hops away. A reply that returns with
a ttl of 1 is a clue this problem exists. Traceroute prints a "!" after
the time if the ttl is <= 1. Since vendors ship a lot of obsolete (DEC's
Ultrix, Sun 3.x) or non-standard (HPUX) software, expect to see this
problem frequently and/or take care picking the target host of your probes.
Other possible annotations after the time are !H, !N, !P (got a host,
network or protocol unreachable, respectively), !S or !F (source route
failed or fragmentation needed - neither of these should ever occur and
the associated gateway is busted if you see one). If almost all the
probes result in some kind of unreachable, traceroute will give up and
exit.
Traceroute is intended for use in network testing, measurement and
management. It should be used primarily for manual fault isolation
because of the load it could impose on the network. (Editors note: An
internet search found several sites that provide traceroute service
between that host and any other internet site... more for interest than
value. Trumpet's HopCheck is available for those with a Windows based
Internet connection.)
Author - Van Jacobson
WHERE IS THIS COMING FROM ANYWAY?
by Norman L. De Forest
You look at a web-site address such as http://www.xyz.foo.dk/junk/info.html
or get an e-mail message from johnsmith@ abc.def.ghi.au (imaginary addresses)
and you wonder where the origin is (Denmark and Australia in this case).
Maybe the following information can help.
The format of an e-mail address is: user@address
The format of a web link is: protocol://address[/directory]... /[file]
(approximately; in some cases the '://address/' part may be omitted and
the format may be different with protocols other than 'http').
MY e-mail address is: 'af380@chebucto.ns.ca'. So my user name is 'af380'
and I can be found at the address 'chebucto.ns.ca'. My web-site home page
link is http://www.chebucto.ns.ca/~af380/Profile.html. The protocol 'http'
shows that this is a link to an HTML web page. The site address is
www.chebucto.ns.ca. The directory is '/~af380' which is shorthand for
'the 'public_html' subdirectory below the home directory of the user 'af380''.
(The Chebucto Community Net is free to move my home directory around as
they see fit and the link never needs to be changed. Only the server at
CCN needs to have its tables updated so it can translate the '~af380'
into the correct path.) The file is 'Profile.html'. The last part of
the ADDRESS may provide a clue to (a) the type of organization providing
the internet connection for a site or person or (b) the location of the
site. If there are three or four letters after the last period in the
address, the organization type is specified. If there are two letters,
the country is specified. The '.ca' at the end of "chebucto.ns.ca"
indicates the country to be Canada, for example.
The following tables may help you determine the type or location of an
Internet address by looking up the four-, three-, or two-letter code at
the end of the address.
DISCLAIMER: this list is not guaranteed to be accurate. This document is
in NO WAY an official document. The information given should not be used
as a basis for routing tables but only as general end-user information.
Data valid as of December 13, 1993. Some changes may have occurred
since then but MOST of the domains should be unchanged. This is a
summary of a larger table (which included codes to indicate mail, ftp,
gopher, bitnet, and other access types for each domain) obtained from a
disk of public-domain data originally obtained from various
Internet sites.
Four- and Three-letter domains:
-------------------------------
.ARPA Old style Arpanet (alias still works)
.NATO Nato field (soon to be deleted)
.COM Commercial
.EDU Educational
.GOV Government
.INT International field (used by Nato)
.MIL US Military
.NET Network
.ORG Non-Profit Organization
The domains in this section are special in that some of them are used in
more than one country. However, this doesn't mean that all of those
domains have full internet access. For example, only a small proportion
of .mil sites have full internet access. The same is true for .com sites,
for example.
Two-letter Domains:
-------------------
DISCLAIMER: The information included in this document (enclosed - ed.)
implies no view whatsoever regarding questions of sovereignty or the
status of any place listed.
WARNING: The link to some countries is often an expensive telephone
dialup link. The people in those countries pay dearly for every byte of
information sent to them. It is therefore not advised to send an
electronic mail to a remote node in such a country asking "how's the
weather there". When it comes to money, people take things very
seriously, especially since funds are scarce. It is a matter of net
etiquette to keep this in mind. Junk mail sent to any node that has to
pay a lot for its telephone connection will clearly be dealt with
HARSHLY and evasive action may well be taken against those not respecting
this notice.
ISO 3166 Codes and Top level domains:
Code Country Code Country
---- ---------------------- ---- --------------------
.AD Andorra .BZ Belize
.AE United Arab Emirates .CA Canada
.AF Afghanistan (Islamic St.) .CC Cocos (Keeling) Isl.
.AG Antigua and Barbuda .CF Central African Rep.
.AI Anguilla .CG Congo
.AL Albania .CH Switzerland
.AM Armenia (Ex-USSR) .CI Ivory Coast
.AN Netherland Antilles .CK Cook Islands
.AO Angola (Republic of) .CL Chile
.AQ Antarctica .CM Cameroon
.AR Argentina .CN China
.AS American Samoa .CO Colombia
.AT Austria .CR Costa Rica
.AU Australia .CS Czechoslovakia (still works...)
.AW Aruba .CU Cuba
.AZ Azerbaidjan (Ex-USSR) .CV Cape Verde
.BA Bosnia-Herzegovina (Ex-Yugoslavia) .CX Christmas Island
.BB Barbados .CY Cyprus
.BD Bangladesh .CZ Czech Republic
.BE Belgium .DE Germany
.BF Burkina Faso .DJ Djibouti
.BG Bulgaria .DK Denmark
.BH Bahrain .DM Dominica
.BI Burundi .DO Dominican Republic
.BJ Benin .DZ Algeria
.BM Bermuda .EC Ecuador
.BN Brunei Darussalam .EE Estonia
.BO Bolivia .EG Egypt
.BR Brazil .EH Western Sahara
.BS Bahamas .ER Eritrea
.BT Bhutan .ES Spain
.BV Bouvet Island .ET Ethiopia
.BW Botswana .FI Finland
.BY Belarus (Ex-USSR) .FJ Fiji
.FK Falkland Isl.(Malvinas) .LK Sri Lanka
.FM Micronesia .LR Liberia
.FO Faroe Islands .LS Lesotho
.FR France .LT Lithuania (Ex-USSR)
.FX France (European Ter.) .LU Luxembourg
.GA Gabon .LV Latvia (Ex-USSR)
.GB Great Britain (UK) .LY Libya
.GD Grenada .MA Morocco
.GE Georgia (Ex-USSR) .MC Monaco
.GF Guyana (Fr.) .MD Moldavia (Ex-USSR)
.GH Ghana .MG Madagascar (Republic of)
.GI Gibraltar .MH Marshall Islands
.GL Greenland .MK Macedonia (former Yugo.)
.GM Gambia .ML Mali
.GN Guinea .MM Myanmar
.GP Guadeloupe (Fr.) .MN Mongolia
.GQ Equatorial Guinea .MO Macau
.GR Greece .MP Northern Mariana Isl.
.GS South Georgia and .MQ Martinique (Fr.)
South Sandwich Islands .MR Mauritania
.GT Guatemala .MS Montserrat
.GU Guam (US) .MT Malta
.GW Guinea Bissau .MU Mauritius
.GY Guyana .MV Maldives
.HK Hong Kong .MW Malawi
.HM Heard & McDonald Isl. .MX Mexico
.HN Honduras .MY Malaysia
.HR Croatia (Ex-Yugoslavia) .MZ Mozambique
.HT Haiti .NA Namibia
.HU Hungary .NC New Caledonia (Fr.)
.ID Indonesia .NE Niger
.IE Ireland .NF Norfolk Island
.IL Israel .NG Nigeria
.IN India .NI Nicaragua
.IO British Indian O. Terr. .NL Netherlands
.IQ Iraq .NO Norway
.IR Iran .NP Nepal
.IS Iceland .NR Nauru
.IT Italy .NU Niue
.JM Jamaica .NZ New Zealand
.JO Jordan .OM Oman
.JP Japan .PA Panama
.KE Kenya .PE Peru
.KG Kyrgyz Republic (Ex-USSR) .PF Polynesia (Fr.)
.KH Cambodia .PG Papua New Guinea
.KI Kiribati .PH Philippines
.KM Comoros .PK Pakistan
.KN St.Kitts Nevis Anguilla .PL Poland
.KP Korea (North) .PM St. Pierre & Miquelon
.KR Korea (South) .PN Pitcairn
.KW Kuwait .PR Puerto Rico (US)
.KY Cayman Islands .PT Portugal
.KZ Kazachstan (Ex-USSR) .PW Palau
.LA Laos .PY Paraguay
.LB Lebanon .QA Qatar
.LC Saint Lucia .RE Reunion (Fr.)
.LI Liechtenstein .RO Romania
.RU Russian Federation (Ex-USSR) .TO Tonga
.RW Rwanda .TP East Timor
.SA Saudi Arabia .TR Turkey
.SB Solomon Islands .TT Trinidad & Tobago
.SC Seychelles .TV Tuvalu
.SD Sudan .TW Taiwan
.SE Sweden .TZ Tanzania
.SG Singapore .UA Ukraine
.SH St. Helena .UG Uganda
.SI Slovenia (Ex-Yugoslavia) .UK United Kingdom (ISO 3166 is GB)
.SJ Svalbard & Jan Mayen Is .UM US Minor outlying Isl.
.SK Slovak Republic .US United States
.SL Sierra Leone .UY Uruguay
.SM San Marino .UZ Uzbekistan (Ex-USSR)
.SN Senegal .VA Vatican City State
.SO Somalia .VC St.Vincent & Grenadines
.SR Suriname .VE Venezuela
.ST St. Tome and Principe .VG Virgin Islands (British)
.SU Soviet Union (Still used.) .VI Virgin Islands (US)
.SV El Salvador .VN Vietnam
.SY Syria .VU Vanuatu
.SZ Swaziland .WF Wallis & Futuna Islands
.TC Turks & Caicos Islands .WS Samoa
.TD Chad .YE Yemen
.TF French Southern Terr. .YT Mayotte
.TG Togo .YU Yugoslavia
.TH Thailand .ZA South Africa
.TJ Tadjikistan (Ex-USSR) .ZM Zambia
.TK Tokelau .ZR Zaire
.TM Turkmenistan (Ex-USSR) .ZW Zimbabwe
.TN Tunisia
NOTE: UK and GB domains: There are two codes for United Kingdom, namely
UK and GB. While UK is used for addressing of most domains in DNS format,
the field GB is used mainly in the X.400 addressing of United Kingdom sites.
However, there is an increasing trend in some United Kingdom sites being
directly connected to Internet under the GB domain. The GB domain is hence a
perfectly suitable Internet top level domain. When looking for further
information, it is worth looking at both UK and GB for United
Kingdom.
Biblical Bits #28
-- Prediction fulfilled --
I will make thy window of agates Isaiah 54:12
ABOUT THE NEWSLETTER
Newsletter Articles
We are almost always in need of good articles. We tend to have many of the
same people producing articles which is fine, but sometimes we can run out of
ideas. It is always interesting to hear from some of the other members from
time to time. If anyone has something that they feel would make a good
article, an interesting story to tell, or even a good meeting topic, please
don't hesitate to pass it on.
You can submit articles in almost any format, ASCII text, AMI Pro, MS Word,
Windows Write, WordStar and of course WordPerfect. What is the best way to
get an article to me? Various ways are available. You can bring it to a
meeting or give me a call and upload it to me. If you are on the Chebucto
FreeNet, Internet, or any type of e-mail system that has a gateway to the
Internet, you can send something to me via the Internet to where I work -
stuartce@ednet.ns.ca.
or
hlfxtrad.educ.stuartce@gov.ns.ca
It does work, but if you are sending a file attachment to your message to me
at the gov.ns.ca address, it should be UUencoded and not a mime attachment.
The ednet email works fine with regular mime encoding and I think it is a bit
quicker than the gov.ns.ca address.
Newsletter Production Notes
For those who may be interested, the newsletter is formatted with WordPerfect
for Windows 6.1 running on either a Pentium 75 or 120. Both have 16 megs of
RAM.
Much of the clipart used is from Novell (formerly WordPerfect) Presentations
3.0 which comes as part of the Perfect Office Suite. The only problem is that
there isn't a printed list of the images so you have to root' around a bit.
The original was printed at 600 dots per inch resolution on a HP Laserjet 4
Plus. The main body of the newsletter is set in 10 point Palatino with the
article headings being 14 point bold. The title on the first page is ITC Zapf
Chancery Medium Italic 19.2 and 16 points.
There were 62 copies produced this month of which around 50 were mailed out.
Any extra copies from the previous few month's issues that I have will be
brought to the next meeting for those who are new to the group or may not be
in regular attendance.
I do have a complete set of all the previous newsletters and if someone wanted
to look through these, let me know and I can bring them to the next meeting.
MEETING SCHEDULE - 1996
The dates for the remaining meetings for this meeting year are listed below.
26 May
23 June
The planning meetings are normally held on the second Monday (8 days) after
the general meeting. They are also located at the Veteran's Memorial
Building. Anyone is welcome to assist in the planning of future meetings or
events.
Any changes to the scheduled dates will be announced where possible at the
regular monthly meetings and/or in this newsletter.
Forward to: June 1996 Newsletter
Back to: April 1996 Newsletter
Go to the: Newsletter Archive
