informis/textfiles
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
textfiles/bbs/FIDONET/FIDONEWS/fido0102.nws

793 lines
34 KiB
Plaintext
Raw Permalink Normal View History

Initial commit
2021-04-15 13:31:59 -05:00
fidonews.man -- 11 Dec 84 00:58:31 Page 1
Volume 1, Number 2 10 Dec 84
+----------------------------------------------------------+
| _ |
| / \ |
| - FidoNews - /|oo \ |
| (_| /_) |
| Fido and FidoNet _`@/_ \ _ |
| Users Group | | \ \\ |
| Newsletter | (*) | \ )) |
| ______ |__U__| / \// |
| / FIDO \ _//|| _\ / |
| (________) (_/(_|(____/ |
| (jm) |
+----------------------------------------------------------+
Editor: Tom Jennings
Publisher: Fido #1
HOT NEWS
This is the second FidoNews newsletter. There isn't
much news this week, unfortunately. Please send some, and
there will be.
Last weeks article on security is included again,
with an update.
Fido version 10a has a bug, in entering download
filenames. There is a version 10a 1/2 that fixes it.
ARTICLE SUBMISSION
The format of this thing is totally ad hoc; please
make recomendations as to formats, sections needed, liked,
or hated, columns you'd like to see, or see removed,
anything at all. If you want to submit something regularly,
we can start a column for you.
You are ENCOURAGED to send things in for the
newsletter. ANYTHING is fit for the newsletter, such as a
description of your board, problems found, questions, jokes,
fixes, horror stories about wrong FidoNet numbers, things
for sale, etc etc etc.
SUBMITTING AN ARTICLE
An article should have your name, node number (if
applicable), followed by the text. Text can be any ASCII
derivative; WordStar, soft paragraphs, 8th bit set, etc are
all OK.
Articles can be uploaded at either Fido #1 or #51,
into the NEWS File Area, or by sending it by FidoNet. There
is a convention for naming the files, so that the newsletter
can be published automatically.
ARTICLE FILENAMES
file.ART For article type things
file.SAL Things for sale
file.NOT Notices
fidonews.man -- 11 Dec 84 00:58:38 Page 2
file.MSC Miscelaneous things
file.EDT an Editorial
file.NEW News items
file.WNT Wanted items
Make sure the name is unique, especially if you send
it by FidoNet, so you dont overwrite another article.
fidonews.man -- 11 Dec 84 00:58:41 Page 3
NEWS
HOW THIS IS PUBLISHED
This is a totally electronic newsletter; articles
are written of course by users and sysops, but all other
parts and proceedures are machine generated.
For each newsletter, the Editor (thats me folks)
does the date and volume of the title page (tough job), and
whatever editorial there may be.
Articles are checked out for being readable (ie.
more or less English language), and bum copies (bad uploads,
etc) are deleted.
The lists generated by FidoNet Admin (St. Louis)
such as the node list, Fido list, and the route list, come
in via FidoNet during the week.
On the day the newsletter is to be published, Fido
#1 runs the text formatter (as a schedule) to produce the
newsletter, using all the articles, the node and Fido lists.
The completed newsletter is then copied into the NEWS file
area. All of the article submissions are saved as last
week's news, and deleted to make room for next weeks.
Some canned messages are copied into Fido 1's mail
area, which file attaches the newsletter to the distribution
points. This completes the FidoNews Newsletter publication.
FIDO SECURITY - Tom Jennings
Last week I mentioned a way that a few systems have
had their security breached; it seems I left out the
simplest method of all. First, a summary of waht was said
last week:
Fido is pretty secure, but there have been a few
instances where callers gave them selves SYSOP priveleges,
and ran amok ... the cure is quite simple.
NEVER NEVER NEVER have your "main" Fido directory
available as a download or upload area. Always make sure
there is no path that can reach your .BBS files. It is OK to
have it as a SYSOP only area, never let it be accessed by
NORMAL users.
If it is available, all someone has to do is get a
copy of SYSOP.EXE, run it, and make a USER.BBS with them as
SYSOP privelege. After uploading this file, they call back
in, with the new name, and bingo! they are in control.
A nastier version of this is to download your
current user list, use SYSOP.EXE to upgrade them (or two, or
three ... in case you find one of them) the upload it.
If this happens to you, delete USER.BBS
*immediately*. Fix it so that the Fido area is not available
to users, and then you will be safe.
Better do it quick, now that it's all documented
here.
fidonews.man -- 11 Dec 84 00:58:48 Page 4
THIS WEEK'S UPDATE
It is not necessary for anyone to go through all
that rigamarole. All they have to do is download USER.BBS,
get a copy of SYSOP.EXE, and see what the sysop's password
is. And probably a few others' passwords as well. I will
repeat the solution:
NEVER! have your main Fido directory accessable for
downloading. Never, never.
If you suspect this has happened to you, DELETE your
user list. Better to have everyone sign in again, than to
have someone crash your board repeatedly.
TIPS
For some systems, you may need to have these areas
accessable to some users. One way is to make that file area
EXTRA or PRIVEL, and let only certain people get at it.
If you want to make things in that area available
for downloading, such as Fido or other programs, you will
have to put a seperate copy into another subdir or disk.
Fido does not filter filenames; it will let any
accptable name pass though. This is a two edged sword; you
have to be careful what you make accessable.
Note that just because a file is not in the file
list (FILES.BBS) doesn't mean it cant be downloaded. If it
is there, it can be downloaded, regardless of whether or not
it's in the list.
Fido does check for device names, such as CON, AUX,
LPT1, COM1, etc. It changes the second character into $, so
uploading COM1 would become C$M1, etc. It will not let these
names be downloaded either.
IMMMMMMMMM;
:VIEWPOINT:
HMMMMMMMMM<
* Note: The IBM Club of Portland, Oregon, and the sysop of this board
in no way assume responsibility or liability for the opinions
posted here. Any viewpoints or opinions expressed here in
the VIEWPOINT editorial section do not necessarily reflect the
opinions or thoughts of the IBM Club or its members.
Moral outrage
-------------
V. Bachulis
My weekly issue of INFOWORLD just arrived today, Thursday the 29th. It
seems that the subject of software copy-protection is getting to be hotter
and hotter day by day. And not without due cause. In the issue prior to
the one I got today, INFOWORLD did an article covering Vault Corporation's
NEW "Killer copy-protection". For those of you who are not schooled in
the ways and wiles of copy-protection schemes, what the article had to
say may be some food for thought.
Briefly, copy protection is basically of only two or three types. The
fidonews.man -- 11 Dec 84 00:58:55 Page 5
main forms are either bad crc's or extra-long or extra-short sectors,
which the PC can not read since it only uses 256k sectors on the average
floppy you use. There are other forms, some of which are more effective,
and others which basically amount to nothing. Symphony and MS WORD are
two of the more prominent packages that come to mind for "sophisticated"
copy-protection. On the low end, the INFOCOM series comes to mind. But
then again, it isn't a $500 dollar program, either.
Now, it seems, software publishers are getting to be more and more uptight
about people either A)Pirating their software (most of which isn't worth
the disk it was copied on) or B)Making honest, legitimate backups of their
valuable software. Towards that end, Vault Corp. has come out with the
ultimate in copy-protection. What they propose is a form of copy-protec-
tion that will, if an illegitimate (or legitimate) copy is made using some
other method than purchasing a back-up disk or using a supplied program
like those supplied with the PFS: series, literally, blow up your machine.
Some of the details that were announced about this "new killer copy-protec
tion" were that it would come up with a warning that the software was not
a legitimate copy of the software, and it would then give you a certain
time limit in which to shut off the machine or risk permanent damage to
your machine and/or hard-disk. The permanent damage you ask? It would
release a "worm", which is a small program designed with the intent of
doing some form of damage, into your PCs' ROM BIOS and all associated
firmware and it would then proceed to destroy your system. Completely.
Why do I take umbrage at this disgusting outrage? Stop and think about
it for a minute. The lost profits from pirated software are not as
outrageous as the industry would have us believe, and in many cases
are blown totally out of proportion. I am of the firm opinion that if
a package is worth a damn, then the person who pirated the software
will ultimately purchase the program legitimately. For a second, even
stronger reason, consider the following quote from INFOWORLD:
"Should we turn Vault's worm loose on medical records
stored in a database? What if one of Defendisk's ...
traps casually omits the fact that some 5-year old-
may have a fatal reaction to penicillin? I'm sure the
grieving parents would understand that software pirates
must be stopped. They should have been more careful when
selecting their doctor. Couldn't they tell that this guy
copies software? And who cares if the pension records
of several hundred employees are capriciously destroyed?
We can't have illegal copies of software floating around.
What Vault and Defendisk propose to implement, and in some cases already
have, amounts to nothing short of a total disregard for this nation's laws
and principles. This form of abuse of those who use and purchase software
should not be tolerated. Granted, software piracy must be stopped or at
least controlled. Until the industry takes a more rational, adult approach
to the problem, this isn't going to happen. What will happen is that when
the first copy, legitimate or not, of this software blows up someone's
PC and destroys all their critical data, be it patient data, or business
records, there will be absolute hell to pay on the part of the software
industry. I will hazard a guess that the introduction of this new pro-
tection will go so far as to put those companies out of business who
utilize this form of protection. Until we start to see companies like
Borland International, who put out QUALITY software at a REASONABLE
price, this little game of "bust the copy-protection" is going to continue
regardless of whether or not there are lethal forms of protection running
around. I applaud Borland for their outstanding product and can only
hope that the rest of the industry will follow suit. Granted, Lotus
or dBASE III may indeed be good programs, but they don't warrant the
fee of $500 bucks a crack. It is a long over-due for software companies
fidonews.man -- 11 Dec 84 00:59:06 Page 6
to wise up and realize that they can't pull the wool over the end-users'
eyes forever.
* EOF *
*******************************************************************************
To all readers of this editorial: Your replies/rebuttals are more than welcome.
If you feel so compelled, please reply to Fido 59, 1-503-629-5581, c/o Sysop.
I am very interested in hearing what other users think about the subject.
*Sysop* Fido 59, Washco Fidonet, Beaverton, Oregon
*******************************************************************************
FIDO TOOLS
There are now some handy programs that make using
Fido easier, and add some new functions. They are available
on Fido 1, probably others too, but I dont know where.
TWIX
TWIX has only one function; it prints out new
FidoNet mail message on a printer or to a disk file. You can
schedule it as an external event, and have it print out all
mail received that night, so that you just look at your
printer to see what came in.
This works by looking for messages that haven't been
read yet; if you read them first with Fido, TWIX will not
print them.
SOURCE for this program is available.
NODELIST.EXE
This program, by John Warren takes the NODELIST.XXX
from Fido 51 and makes you a NODELIST.BBS. It will remove
the 1 and area code for local (to you) systems, put in
sprint or other dialing prefixes, enter costs as you
specify, etc.
One time only you put the needed information into a
file used by the program, and after that just run it when
you get a new list. It makes customizing the nodelist from a
one hour chore to a 30 second simple task.
WATCHDOG
IBM PC and clones only: this program is used with
the 0 command, and monitors the Carrier Detect signal from
the modem. If carrier is lost while you are in DOS, it will
restart Fido, so that another caller wont end up in your
DOS. There are versions for COM1, COM2, etc, and source is
available. By John Reinders at the Sailboard. (61)
READMSG
This does some of the Fido type message read
functions, but from DOS, and lets you scan them, and
optionally print them. This one is from Kurt Reisler, The
Bears Den (74).
TOM TCIMPDIS' LA BUST
fidonews.man -- 11 Dec 84 00:59:12 Page 7
The LA BBS bust is far from over. There hasn't been
any news lately, apparently because they are going through
the usual legal maneuvering, of hearings, pre-hearings, etc
etc.
However it turns out, this is an important case, and
whether you believe it or not, it will affect you directly,
even if you are not in LA and even if you are not a sysop.
Tom's guilt or innocence is only a small part of the
importance of this, and since most of us were not regular
callers to his board, it is hard to comment on it.
The underlying issue here is one of control: who is
liable for the contents of a BBS? It was related to me (by
someone who had lawyers persue it) that the status of BBS's
is quite up in the air; are they common carriers (ie. the
phone co.) or are they publishers (ie. newspapers). Phone
companies have limited liability because they provide a
medium, and not the contents, and are generally not liable.
(If you arrange a sale for a stolen bicycle by phone,
Pacific Bell is not resonsible). Publishers control their
contents, and I think are liable for even the contents of
their classified ads, though that is obviously impossible to
ensure.
You really should voice your opinion on this issue.
It will not mark you as a political radical, and the FBI
will not harrass your neighbors. It is your right, and our
right to free communications.
Losing this case will be a large step towards
regulating BBSs. Regulation will mean the death of BBSs as
we know it. We are unregulated, and are quite responsible
and take care of our own problems. The trouble makers are
far and few between.
Take the time to think about all of the systems you
have ever called and patronized, and consider how they were
run, how they were handled and how problems were solved. I
think you will find that they take quite good care of
themselves on the whole, and problems are resolved between
the users and the sysops.
If you want to help keep it this way, where you have
a very large say in what BBSs do, what they are used for,
and how they are run, please write!
The sample letter below can be used if you want.
Please send a copy to both people listed below; Lindner is
defending Tom Tcimpidis, and is a BBS user himself.
TAKE THIS OUT, FILL IT IN, AND MAIL IT!
(your address and the date
goes into this space
3 lines )
Ira Reiner -- LA City Attorney Charles E. Lindner, Atty
Suite 1800 City Hall East The Bradbury Building
fidonews.man -- 11 Dec 84 00:59:19 Page 8
20 N. Main St. Los Angeles CA 304 S. Broadway, Suite 420
90012 Los Angeles CA 90013
Dear Sir,
I would like to take this oppurtunity to speak in
behalf of computer bulletin board sytems (BBSes). Bulletin
Boards are excellent ways to meet other computer users and
hold intelligent conversations with them. Bulletin boards
are a very convenient way to get any help you might need for
your computer, from advice on a game to programming
techniques and technical information.
The idea that all of these bulletin boards are used
solely for pirating of software and illegal telephone usage
is one that is ill-conceived, stemming from the occasional
"bad seed" of BBSes. In reality, these illegal BBSes are
few and far between, and are frowned upon by the general
BBS-using public.
I urge you to consider all the good of which BBSes are
capable, and not the bad side shown by several rare and
unacceptable examples.
Thank you in advance for your consideration in this
matter.
Sincerely,
(print and sign your name here)
REPRINTED FROM FIDO #36 - RAINBOW DATA - LOS ANGELES
#22 14 20 Nov 84 09:19:31
From: Doug Brantley To: All
Subject: Fast Console Under MS-DOS
According to the Nov. 84 issue of 'Digital Review'.......
'Ever notice how slow your Rainbow screen output is under
MS-DOS version 2.05? The people at the DEC-8000 hot line
in Atlanta told me to change the byte at address 40:19 from
03 (hex) to 13. To do this automaticalyy at boot-up time,
add the following line to your AUTOEXEC.BAT file:
-
DEBUG<FASTCON
Then create a file named FASTCON that contains the following
two lines:
E40:19 13
Q
Lo and behold, screen output now runs about twice as fast.'
-
I found this statement in the Tech Talk column on page 106.
It is too bad that more discussion was not given the
subject. Why that byte and how does it speed output to the
screen?
-
I did the patch and the screen output is much faster.
#18 1 27 Nov 84 20:43:04
To: William Roberts
Subject: fast console
The MSDOS BIOS has this feature called the "fast
fidonews.man -- 11 Dec 84 00:59:26 Page 9
device". It has two components: a bit in the device
descriptor table (the 03 -> 13 patch mentioned) and the
"fast device" code, pointed to by Interrupt #29h.
The idea is that if you have a device youd like to run
real fast, you can use this for output. There can be only
one fast device in the system, and it is almost always CON.
If MSDOS finds the FASTCON bit set, then it uses INT 29h
for all its console output, instead of the normal BIOS
call, which invokes a huge, slow, paacket process for each
byte displayed.
Note that there has to be INT 29 code installed; you can
write it yourself, then set the bit in the table.
This feature probably does not exist for MSDOS 3.xx.
NOTICES
FOR SALE
WANTED
fidonews.man -- 11 Dec 84 00:59:29 Page 10
FIDOLIST --- HUMAN READABLE NODE LIST
List of Fido Based Bulletin Board Systems
Updated 07 Dec 84 by Fido 51
Please send updates,corrections or other information to:
Fido #51.
All are 24 hrs 300/1200 baud except as noted
Times listed are in the BBS's local time zone
RE == restricted, or private or by request,etc.
WE == plus Weekends
SU == plus Sunday, etc
RT == route all mail to node as specified
1 Fido's-Board San Francisco, CA Tom Jennings(415)-864-1418
2. CLP-FIDO Pikesville, MD John Madill (301)-484-2831
3. FidoSouth Atlanta, GA Lane Fowler (404)-979-5105
4. Bulldog St. Louis, MO Tony Clark (314)-441-9297
5. Batie's Backyard Corvallis, OR Alan Batie -DOWN-
6. CastleNet Corvallis, OR Lee Damon (503)-754-5244 9p - 9a SU
7. Bob_Overlock Waimea, HI Bob Overlock (808)-338-1277
8. Demon New York, NY Danny Feinsmith -DOWN-
9. GDC_Connection Middlebury, CT Jim Ryan (203)-758-8081
10. MDC/RCC St. Louis, MO Ben Baker (314)-234-1462 5p - 8a
11. PRO-TECH Cypress, CA Sanford Zelkovitz (714)-898-8634
13. Vern's_Fido San Jose, CA Vern Crawford (408)-923-5565
14. WayStar Marlboro, MA Kevin Porter (617)-481-7147
16. Mikes_Board St. Louis, MO Mike Mellinger (314)-726-3448
17. DCA_BBS St. Louis, MO Jon Wichman (314)-962-0395
18. Steve_Hedlund Van Nuys, CA Steve Hedlund -DOWN-
21. Phoenix_Sfwr Norwood, MA Bob Vandette (617)-769-0850 RE
22. PCLUG St. Louis, MO Ken Kaplan (314)-576-2743
25. Take-A-Byte Anaheim, CA Robert Collins (714)-995-2428
26. MicroFonePC Fresno, CA Bob Robesky (209)-227-2083 5p - 9a WE
27. Daves_Fido Gardner, MA David Rene (617)-632-1861
28. World Control Baltimore, MD Rob White (301)-653-2074
31. HamRadioWest Riverside, CA John Warren (714)-681-0974
32. Artesia_BBS Artesia, CA George Gilbert (213)-402-6217
33. Rod_Smallwood England Rod Smallwood 01144-635-4680
*34. CrossFire Philadelphia, PA Todd Savar (215)-565-7639 New Phn #
35. ConsultNet Saratoga, CA Jim Turley -DOWN-
36. Rainbow_Data Los Angeles, CA Don Brauns (213)-204-2996
38. Bill1000Jr Madison, WI Bill Thousand,Jr. -DOWN-
39. KarlRegier Reedley, CA Karl Reiger -DOWN-
40. RonCrain Birmingham, MI Ron Crain (313)-646-5159 11p - 6a
42. MetChem New Haven, CT John Bauer (203)-281-7287 8p - 8a
43. Seequa_Computer Odenton, MD Bob Depelteau (301)-672-3627
44. NECS Arlington, MA Dave Mitton (617)-646-3610
45. Midnight_DEC Boston, MA David Strickler (617)-353-7528 12a - 5p
46. Joes_Rainbow St. Mary, FL Joe Clayton (305)-321-2369
*47. The_Workshop AnaheimHills,CA Brian Majewski(714)-974-6925
48. El_Dorado Houston, TX Paul Wells (713)-488-8771
49. NW-RBBS Portland, OR Doug Foreman (503)-233-6583
or (503)-666-8265
50. Crystal_Cavern Austin, TX Scott Ashcraft (512)-263-5805
51. DECUS_CENTRAL St. Louis, MO Sysops16,17,&22(314)-432-4129
52. TOPCC Thousand Oaks, CA Gary Vedvik (805)-499-8378 4p - 8a WE
53. SE_C-Board Woodstock, GA Ken Shackelton (404)-928-1876
54. CEL_Comm_1 Seattle, WA C.E. Langenberg (206)-725-9413
56. Denver_Fido Denver, CO Oscar Barlow (303)-973-9338
57. MCCPowers Northbrook, IL Russ French (312)-480-8730
58. PiCoSystems El Toro, CA Jim Baumgartner (714)-855-3282 RE
fidonews.man -- 11 Dec 84 00:59:40 Page 11
59. Washco_FidoNet Beaverton, OR Vic Bachulis (503)-629-5581
60. Artichoke Houston, TX Justin Marquez (713)-870-8803 6p - 8a WE
61. RAMS Rochester, MN John Pritchard (507)-289-8452
62. Data_Jockey Bellevue, WA Darrin Smith (206)-643-0909 7p - 8a SU
63. WCE Waterford, MI Bob Leffler (313)-623-1089
64. Graf_Spee Houston, TX Jay Maynard (713)-530-2334 Irregular
65. TWACS St. Louis, MO Tony Clark(See also #4)(314)-895-6471 RE
66. Info*Net Costa Mesa, CA Richard Hart (714)-642-4408
67. DEC_Domain Lubbock, TX Alan Minchew (806)-795-0102
69. Sailboard Highland, MI Jim Kovalski (313)-887-7429
71. Rosenburg_Express Rosenburg, TX Ken Collins(713)-342-9349
72. Harry_Chesley San Francisco, CA H. Chesley (415)-563-2491
73. Eagle-1 Ashland, MA Dave Hornbaker (617)-881-6495
74. The_Bears_Den Falls Church, VA Kurt Reisler(703)-671-0598 7a - 11p
75. ThumbTech Plano, TX Matt Legare (214)-985-7926
77. GMCC Boulder, CO Kent Leonard (303)-497-6968
78. Living_Sober San Carlos, CA Rick G. (415)-593-5583 Moving??
79. DEC-WARE New York, NY Matt Kanter (212)-535-8924
80. Eldon_Ziegler Columbia, MD Eldon Ziegler (301)-992-3835 RE
81. PC-WORLD Philadelphia, PA Sal Marandola (215)-465-2278 4p - ??
82. DEC-House Cherry Hill, NJ Brian Sietz (609)-429-6630 12a - 530p
83. Harmer's_Hut Philadelphia,PA Brian Harmer (215)-565-7639 No Inc FNet
84. SCI-Fido Oakland, CA Mike Farren (415)-834-3319
85. Allens_Board Cincinnati, OH Allen Miller (513)-579-2587
86. Grummons_Fido Bethpage, NY Don Daniels (516)-575-5838
87. Deus_Ex_Machina San Diego, CA Bruce Webster(619)-286-7838
88. Wizards_Tower Teterboro, NJ Karl Schinke (201)-288-9076 5p - 8a WE
89. Boondocks Rock Island, IL Jonathan Smith (309)-794-0289 5p - 8a WE
90. MidNet Middleton, WI Mike Mansfield (608)-233-8449
91. The_DEAD_END Round Rock, TX Steve Sparks (512)-255-1282 RE
92. PCUTILboard Detroit, MI Jon Tara (313)-393-0527
99. The_REAL_Fido San Francisco,CA Tom Jennings -UNPUBLISHED- RE,RT 1
104. Baby_BYTE/Net Peterborough, NH George Bond (603)-924-9820
108. Samson Rolling Meadows,IL Larry Miglore (312)-991-8304 5p - 8a WE
115. Arquimedes Washington,DC Sam Hegardine (202)-332-9512
#117.Jim_Filgo Jakarta, INDONESIA Jim Filgo 011062-21-77054
124. TimeLifeBks Alexandria, VA Eldon Ziegler (703)-833-7355 RE
125. Radar's_Node Fairfax, VA Joel O'Rourke (703)-978-0351 Irregular
130. Paul_Munson Costa_Mesa, CA Paul Munson (714)-650-6422
200. Grinnell_Fido Grinnell, IA Michael Strait (515)-236-2578 8p - 8a
201. Ham_Radio_Net Newington, CT Ed Raso (203)-665-1114
202. DEC-Line Boston, MA Bill McNeill (617)-721-1688
203. Dark_Planet Branford, CT Peter Sashka (203)-488-3440
204. Noble_House NYC, NY Jonathan Youngwood (212)-534-8557 10p - 4p
205. Alex's_DragonDom NYC, NY Alexander Morris (212)-496-7946
206. BlueStar Edmonds, WA Craig Derouen (206)-745-5368
207. Northern_Reaches New Haven, CT Geoff Hickey(203)-865-1794
208. Bruce's_Fido W. Hartford, CT Bruce Lomaski (203)-236-3761
300. WeyCoFidoByter Federal Way, WA Steve Butler(206)-924-2955 5p - 8a WE
301. Beyond_War Los Angeles, CA Andrew Kanter (213)-477-5706
302. Don Quixote Rochester, MN Pat George (507)-288-8901 8p - 8a WE
303. Strictly_Sfwr Honolulu, HI Mike Oya (808)-944-0562 7p - 10a
304. Westlake_BBS Austin, TX Albert Nurick (512)-327-7926 6p - 7a SU
305. The_Pacesetter Potomac, MD Brian Driscoll (301)-299-3228
306. Left_Cartridge Cincinnati, OH Paul Martin (513)-797-7040 RE
307. DalTex_FIDOnet Dallas, TX Chris Bradley (214)-991-7934
308. Software_PLUS Cincinnati, OH Dave Schleper (513)-621-9273 7p - 9a
309. Marc's_FIDO Portland, OR Marc Frajola -UNPUBLISHED- RE,RT 59
310. Daves_Annex Westminister, MA Dave Rene (617)-874-4325 4p - 7a WE
311. The_Lair Altamonte Springs, FL Robert Hupf (305)-830-8494 430p-8a WE
312. Cinci_Comm_Net Fairfield, OH Jeff Perrigo (513)-874-0226 9p - 7a
313. Mikes_Rainbow Garden Grove,CA Mike Hamilton(714)-537-7355
314. One_Paticular_Harbour Ft Worth,TX Cpt Utley(817)-294-7383
fidonews.man -- 11 Dec 84 00:59:52 Page 12
315. DD_Network Boston, MA Dana Long (617)-536-4670 12a - 5p
On Weekends 12a - 10a
*316.Miami's_1st_Fido Miami, FL Al de la Torre (305)-554-4602
317. DEC-WARE_II Iselen, NJ David Horowitz (201)-750-3748
318. PC_WeeK Needham, MA Garry Ray (617)-449-4727
319. Tribury_Fido Waterbury, CT Phil Mongelluzzo(203)-574-2449 7p - 11p
On Weekends 10a - 10p plus FNet Nat'l Mail
*320.Surprise_Pak Orange, CT David Hecht (203)-795-0339
321. CANADA_1 Willowdale, ONT Vic Kass (416)-226-9260
322. PTC_Net Mt Vernon, WA Arlen Fletcher (206)-757-5233 5p - 7a WE
323. PC-Exploration Garland, TX Gary J. Carter (214)-530-9143
324. UW_Hat Madison, WI Michael Mansfield (608)-262-4469 8p - 8a WE
325. Quantum_BBS Potomac, MD Mike Merrell (301)-340-2486
Interim Sched. 3p Fri - 8a Mon WE Only
*326.The_Barn_Board Cinncinati,OH Robert Emerson(513)-752-8248
327. Toronto_RCP/M_4 Toronto, ONT Jud Newell (416)-231-0538
328. Toronto_RCP/M_6 Toronto, ONT Jud Newell (416)-231-1262
#329.Computer_Aide Tulsa, OK Mike Johnson (918)-493-2137
#330.Buzzboard Cambridge, MA Buzz Moschetti (617)-577-8092
#331.MSFIDO Los Angeles, CA Brian Casey (213)-250-8085 5p - 830a WE
#332.American_Conn Houston, TX David Reinsel (713)-831-3768 5p - 7a WE
#333.Rainbow_BBS Phoenix, AZ Jim Kashner (602)-952-2146
12a - 4p;10p - 12a M thru F;12a - 8a on Weekends
#334.Micro_Broker Denver, CO Oscar Barlow (303)-534-5456
#335.Phil's_Fido Gaithersburg, MD Phil Kim (301)-921-0111
#336.Berkshire Anaheim, CA Harry Lee (714)-632-9117
* INDICATES CHANGED ON THIS UPDATE
# INDICATES ADDITIONS ON THIS UPDATE
Please send updates, corrections, additions to Fido #51.

Reference in New Issue Copy Permalink