home *** CD-ROM | disk | FTP | other *** search
Wrap
Text File | 1993-12-31 | 171.0 KB | 4,573 lines
Mon, 1 Apr 91 04:30:10 PST From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #78 To: packet-radio Packet-Radio Digest Mon, 1 Apr 91 Volume 91 : Issue 78 Today's Topics: KE4ZV - Gary Coffman Looking for info on a specific freq. band (2 msgs) Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 31 Mar 91 10:28:53 GMT From: bionet!hayes.ims.alaska.edu!acad3.alaska.edu!ifjrs@ames.arpa Subject: KE4ZV - Gary Coffman To: packet-radio@ucsd.edu Hi. Tried to email a reply to some comments you made (I didn't save the reference), and for some reason our mailer didn't recognize ke4zv.uucp as a host. Wonder if you could email me at one of the addresses listed with an address, phone number, @bbs, ANYTHING, for GRAPES, and/or info about the DSY modem/rig. I've been trying, unsuccessfully, for several months to get some kind of contact from up here in the "bush." Thanks, John -- John Stannard ifjrs@acad3.fai.alaska.edu BITNET: IFJRS@ALASKA KL7JL@KL7JL.AK.USA.NA kl7jl.ampr.org [44.22.0.1] "God is the Answer!" "Oh?? ... er, ... What was the Question?" -- ------------------------------ Date: 30 Mar 91 15:16:55 GMT From: ogicse!emory!wa4mei!ke4zv!gary@ucsd.edu Subject: Looking for info on a specific freq. band To: packet-radio@ucsd.edu In article <2412@stsci.EDU> tullos@stsci.EDU (Calvin Tullos) writes: > >I'm looking for information on who might be broadcasting >between 174 MHZ and 199 MHZ..... TV broadcast channels 7 thru 11. Gary KE4ZV ------------------------------ Date: 1 Apr 91 08:30:24 GMT From: sdd.hp.com!usc!neuro.usc.edu!demikhov@ucsd.edu Subject: Looking for info on a specific freq. band To: packet-radio@ucsd.edu In article <2412@stsci.EDU> tullos@stsci.EDU (Calvin Tullos) writes: >I'm looking for information on who might be broadcasting >between 174 MHZ and 199 MHZ..... vs. wireless microphone. 174-216 MHz Television Channels 7-13 (6 Mhz of spectrum for each channel) ------------------------------ End of Packet-Radio Digest ****************************** Date: Tue, 2 Apr 91 04:30:05 PST From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #79 To: packet-radio Packet-Radio Digest Tue, 2 Apr 91 Volume 91 : Issue 79 Today's Topics: Mentor needed Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 1 Apr 91 23:59:54 GMT From: usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!milton!sumax!thebes!ole!ssave@ucsd.edu Subject: Mentor needed To: packet-radio@ucsd.edu I am interested in Amateur radio. I would like to get started and give the required exams. What I want to request from you pros out there is for someone to help and guide in this process. I need to practice and I need to learn from someone with experience. Would someone like to take on this task. I live in the Seattle area and have a degree in EE. Shailendra beaver.cs.washington.edu!sumax!ole.uucp.ssave ------------------------------ Date: 1 Apr 91 22:29:31 GMT From: epic!karn@bellcore.bellcore.com To: packet-radio@ucsd.edu References <skcm.670222049@ise>, <1991Mar29.223715.5564@bellcore.bellcore.com>, <skcm.670398101@ise> Reply-To : karn@thumper.bellcore.com Subject : Re: ? how to route with tcpip In article <skcm.670398101@ise>, skcm@echo.canberra.edu.au (Carl Makin) writes: |> In the case of a BBS forwarding traffic then the BBS is the "originating" |> station. In the case of someone navigating his way thru the network |> then HE remains the "originating station" despite how many links may |> be carrying his traffic. This STILL makes no sense. There is absolutely no fundamental difference between an autoforwarding BBS and an IP router. Both are store-and-forward packet switches. Both operate automatically, forwarding connectionless traffic from a source toward a destination on top of AX25 frames that reflect only the immediate transmitter and receiver. The only differences are the following: 1. (The BBS) generally uses magnetic disks for store-and-forward buffer storage while the other uses dynamic RAM. 2. The network layer protocols are a little different - one uses stream ASCII (the mail message format); the other uses formatted binary (the IP header). It is true that the network layer addresses in the BBS network are callsigns while IP addresses are not. But the three big uses of IP, mail, FTP and telnet, usually involve exchanging, in the TCP data stream, the names of the originating and destination station or user names as part of the application protocol. Since the amateur TCP/IP convention is to make the user's callsign part of the system name, you have a situation very similar to autoforwarding BBSes. In neither situation are the originating and ultimate destination stations identified in each packet, but they are identified in the data stream near the beginning of a connection. I hesitate to encourage you to use this argument with the DoTC because it could very well result in a proclamation that autoforwarding BBSes are illegal too... such is the nature of a bureaucrat, I'm afraid. Phil ------------------------------ End of Packet-Radio Digest ****************************** Date: Wed, 3 Apr 91 04:30:06 PST From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #80 To: packet-radio Packet-Radio Digest Wed, 3 Apr 91 Volume 91 : Issue 80 Today's Topics: Computer required for BBS Help: Why won't BAYCOM connect to this station/ UA ignored? KPC-2 Mentor Monthly On-Line Elmers Resource Directory Nintendo for sale TAPR tnc-2 upgrades UO-14 satellite sounded really weird tonight Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 2 Apr 91 22:04:24 GMT From: swrinde!elroy.jpl.nasa.gov!sdd.hp.com!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!miller@ucsd.edu Subject: Computer required for BBS To: packet-radio@ucsd.edu Where can I get hold of the software for a packet BBS system, and what is the preferred hardware to run on these days? I helped assemble a couple of Xerox 820's back in the good old days, but have lost touch with more recent developments. I am now presented with the possibility of getting involved with a BBS again, provided someone is willing to bring me up to speed. Thanks, Tim, N9DKI miller@ecn.purdue.edu ------------------------------ Date: 3 Apr 91 00:55:06 GMT From: comp.vuw.ac.nz!cc-server4.massey.ac.nz!G.Moretti@uunet.uu.net Subject: Help: Why won't BAYCOM connect to this station/ UA ignored? To: packet-radio@ucsd.edu I've been trying out BAYCOM and it seems to work really well, but only on ONE of the local BBS (there are two). On the second, I can request a connect (send a SABM), the BBS replies with a UA which is apparently ignored and BAYCOM retries, with the BBS repeatedly replying until BAYCOM gives up. Here's the copy of the monitor window (I'm ZL2BOI, ZL2TCX is the BBS): > T0 ZL2BOI>ZL2TCX>SABM,P > R0 ZL2TCX>ZL2BOI>UA > R0 ZL2TCX>ZL2BOI>I00,F0: > [MSYS-1.10-HM$] > R0 ZL2TCX>ZL2BOI>I10,F0: > Hello Giovanni, Welcome to ZL2TCX's MSYS BBS in Levin. > R0 ZL2TCX>ZL2BOI>I20,F0: > R0 ZL2TCX>ZL2BOI>I30,F0: > T0 ZL2BOI>ZL2TCX>SABM,P > R0 ZL2TCX>ZL2BOI>UA > T0 ZL2BOI>ZL2TCX>SABM,P > R0 ZL2TCX>ZL2BOI>I00,F0: > [MSYS-1.10-HM$] > R0 ZL2TCX>ZL2BOI>I10,F0: > Hello Giovanni, Welcome to ZL2TCX's MSYS BBS in Levin. > R0 ZL2TCX>ZL2BOI>I20,F0: > R0 ZL2TCX>ZL2BOI>I30,F0: > R0 ZL2TCX>ZL2BOI>UA > R0 ZL2TCX>ZL2BOI>I00,F0: > [MSYS-1.10-HM$] > R0 ZL2TCX>ZL2BOI>I10,F0: > Hello Giovanni, Welcome to ZL2TCX's MSYS BBS in Levin. > R0 ZL2TCX>ZL2BOI>I20,F0: > R0 ZL2TCX>ZL2BOI>I30,F0: > T0 ZL2BOI>ZL2TCX>DISC,P > R0 ZL2TCX>ZL2BOI>I00,F0: > [MSYS-1.10-HM$] > R0 ZL2TCX>ZL2BOI>I10,F0: > Hello Giovanni, Welcome to ZL2TCX's MSYS BBS in Levin. > R0 ZL2TCX>ZL2BOI>I20,F0: > R0 ZL2TCX>ZL2BOI>I30,F0: > R0 ZL2TCX>ZL2BOI>UA Below is a connect to a BBS that works. The only difference I can see is that on this BBS the "UA" packet has the FINAL bit set. > T0 ZL2BOI>ZL2TCA>SABM,P > R0 ZL2TCA>ZL2BOI>UA,F > R0 ZL2TPQ>ZL2TCX>RR0 > R0 ZL2TCA>ZL2BOI>I00,C,F0: > Hello Giovanni and welcome to the ZL2TCA BBS in Feilding! > T0 ZL2BOI>ZL2TCA>RR1,R Normal Info packets are fine as shown below: > R0 ZL2TCX>ZL2TPQ>I11,F0: > Decay rate: 2.89e-06 rev/day^2 > Epoch rev: 789 > Satellite: RS-12/13 > Catalog number: 21089 > Epoch time: 91083.72491363 Is this a known bug or is there something I can do to bypass the problem? Thanks Giovanni ZL2BOI -- ------------------------------------------------------------------------------ Giovanni Moretti, Consultant | G.Moretti@massey.ac.nz, Pkt-ZL2BOI@ZL2TCX Computer Centre, Massey University| Ph 64 63 69099 x8398, FAX 64 63 505607 Palmerston North, New Zealand | QUITTERS NEVER WIN, WINNERS NEVER QUIT ------------------------------------------------------------------------------ ------------------------------ Date: 2 Apr 91 21:43:49 GMT From: sdd.hp.com!caen!math.lsa.umich.edu!spsd4360a.erim.org!hideg@ucsd.edu Subject: KPC-2 To: packet-radio@ucsd.edu Hello. Is the Kantronics KPC-2 a tnc-2 clone? ____________________________________ Steve Hideg N8HSC hideg@spsd4360a.erim.org ------------------------------ Date: 2 Apr 91 16:39:43 GMT From: news-mail-gateway@ucsd.edu Subject: Mentor To: packet-radio@ucsd.edu To the party interested in Amateur Radio in the Seattle area: Amateur Radio Supply (in Seattle) publishes a catalog that includes Ham examination times, dates, sites and contact persons. Both ARS and their catalog can steer you where and to whom you might want to contact. 73;, ------------------------------ Date: 1 Apr 91 22:36:07 GMT From: tut.cis.ohio-state.edu!magnus.acs.ohio-state.edu!zaphod.mps.ohio-state.edu!caen!kuhub.cc.ukans.edu!zeus.unomaha.edu!acmnews@ucbvax.berkeley.edu Subject: Monthly On-Line Elmers Resource Directory To: packet-radio@ucsd.edu Greetings Netters, I am currently compiling a directory of On-Line Elmers. These are people who, by virtue of skill and knowledge in an area of expertise in ham radio, are willing to field E-mail by readers of the rec.radio.* groups. Volunteers need only send me their name, E-mail address, and area of expertise. As requested, here is a suggested list of areas of expertise that are needed: 1. Volunteer Examiners 2. Novice Instructors 3. DX'ers and Contesters 4. QRP 5. Homebrewers 6. Packet Ops (both AX.25 and TCP/IP) 7. VHF and Repeaters 8. OSCAR and other satellites 9. MARS (Military Affiliate Radio System) 10. CAP (Civil Air Patrol) 11. ARES (Amateur Radio Emergency Service) 12. RACES (Radio Amateur Civil Emergency Service) 13. Skywarn (Amateur Weather Spotters) 14. ARRL Field Organization (American Radio Relay League) "Generalist" or "Miscellaneous" Elmers are also quite welcome. Naturally, the more that volunteer, the more the work is distributed. If upon volunteering, you are unable to meet your obligations, simply write to me and I will remove your name from the list. I could also add that because of "personal committments" or "career broadening" you no longer are available to Elmer on a regular basis. I will be the point-of-contact for this project. I will maintain the list, post it to the groups at least monthly, and have the latest copy placed in the supplemental archives at ftp.cs.buffalo.edu in subdirectory pub/ham-radio. Here is the latest version of the list. If you sent me mail and are not on it, please resend as it may have been lost on the way or once it reached my host. 73, Paul, KD3FU ACMNEWS@zeus.unomaha.edu uunet!unocss!zeus!acmnews 137.48.1.1 ps67@umail.umd.edu uunet!mimsy!umail!ps67 128.8.10.28 ON-LINE Elmers Resource Directory (as of 04/01/91) ----------------------------------------------------- John Brewer WB5OAU brewer@anarky.enet.dec.com Miscellaneous, Wire antennas, ------------------------------------------------------ {ames!ncar!noao!asuvax,mcdphx}!anasaz!rusty anasaz!rusty\ 73 de Rusty Carruth, N7IKQ (602) 870-3330 anasaz.UUCP!rusty>@asuvax P.O. Box 27001, Tempe, AZ 85285 rusty%anasaz.UUCP/ \.eas.asu.edu Join the Usenet Un-Net on 10M, 1700-1900Z Saturdays, 28.410 or 28.390 MhZ The Ham Callsign Project-part 3 (the 1990 version) - its HERE! Email for info ------------------------------------------------------ Dan Halbert, KB1RT QTH is West Newton, MA, near Boston. halbert@crl.dec.com Building homebrew QRP gear, Advice on simple antennas ------------------------------------------------------ R.D. Keys Dept. of Crop Science NCSU Raleigh, NC 27695-7620 rdkeys@ccvr1.cc.ncsu.edu de NA4G, "Boat Anchor Bob", an ol' cw fart ..... If I can be of assistance in older equipment, junk-boxing your way to hamdom, the cheapskate's approach, let me know. 22 yrs a ham, extra class, mostly cw, mostly boat anchors and radio in the traditional sense. {Telegraphy has been in my family for almost 100 years!} ----------------------------------------------------- Alan Larson WA6AZP larson@snmp.sri.com My areas are fairly general, and I teach classes (Novice, with code, and upgrade sessions) at w6yx. My main audience is to the Stanford (University) community. ----------------------------------------------------- Joel Magid N1HZH/AA magid@esis.enet.com ARES/RACES Novice Instruction ------------------------------------------------------ Dave Potter, K1MBO potter@think.com electronics theory, regulations, antennas and transmission lines, operating practices. ------------------------------------------------------ Tony Reeves KK6XC QTH Beach Area of So. Los Angeles Torrance, Redondo Beach, Hermosa Beach, Manhattan beach tony@hacgate.scg.hac.com Novice training, local VE for Novice-Tech tests, General questions ------------------------------------------------------ Paul W. Schleck, KD3FU acmnews@zeus.unomaha.edu ps67@umail.umd.edu Miscellaneous, Internet, College Clubs ------------------------------------------------------ Tom Sefranek WA1RHP tcs@ll.mit.edu Elmering for the last 20 years. Almost all fields, Specializing in power supplies, micro-controllers, antennas ------------------------------------------------------ Marty Squicciarini NR3Z skitch@nadc.navy.mil DX and Contesting QSL'ing ------------------------------------------------------ Diana L. Syriac Leominster, MA dls@genrad.com KC1SP QSL Bureaus (how to use them) Volunteer Examiner Service (how to become one) Macintosh Hamstacks Civil Air Patrol ------------------------------------------------------ Robert Taylor K9ALD rtaylor@ux1.cso.uiuc.edu K9ALD RT 5, Box 70, Mahomet, IL 61853 217-586-4958 Help on antennas, MARS, components, Tube circuits, linear amplifiers, trouble shooting. ------------------------------------------------------ Mike Waters AA4MW/7 waters@nddsun1.sps.mot.com Miscellaneous ------------------------------------------------------ Bob Witte HP Colorado Springs Division bobw@col.hp.com P.O. Box 2197 Phone:(719) 590-3230 Colorado Springs, CO 80901 Radio: KB0CY "All Disclaimers Apply." Miscellaneous ------------------------------------------------------- End of Directory ------------------------------ Date: 3 Apr 91 06:30:09 GMT From: ogicse!milton!bigmouth@ucsd.edu Subject: Nintendo for sale To: packet-radio@ucsd.edu Nintendo base unit with 2 controllers, NES Advantage joystick, light gun games: Super Mario Bros/Duck Hunt, Punch Out and Ghosts & Goblins $135 obo bigmouth@milton.u.washington.edu ------------------------------ Date: 2 Apr 91 21:45:36 GMT From: sdd.hp.com!caen!math.lsa.umich.edu!spsd4360a.erim.org!hideg@ucsd.edu Subject: TAPR tnc-2 upgrades To: packet-radio@ucsd.edu Hello. Does TAPR still offer tnc-2 upgrades? I have two HD-4040s, I'd like to upgrade them. tnx. ____________________________________ Steve Hideg N8HSC hideg@spsd4360a.erim.org ------------------------------ Date: 3 Apr 91 04:18:53 GMT From: swrinde!zaphod.mps.ohio-state.edu!wuarchive!rex!rouge!pc.usl.edu!jpd@ucsd.edu Subject: UO-14 satellite sounded really weird tonight To: packet-radio@ucsd.edu I tried to copy UO-14's 0230 UTC 3 April 91 pass, and I heard this horrible buzz and high-pitched tone instead of the usual woosh of msk fm. I was surprised to see my NB96 modem showing DCD detected, but I printed nothing. Anyone know what's happened to uo-14? The next pass was similarly afflicted. 73, -- -- James Dugal, N5KNX Internet: jpd@usl.edu Associate Director Ham packet: n5knx@k5arh Computing Center US Mail: PO Box 42770 Lafayette, LA 70504 University of Southwestern LA. Tel. 318-231-6417 U.S.A. ------------------------------ End of Packet-Radio Digest ****************************** Date: Thu, 4 Apr 91 04:30:10 PST From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #81 To: packet-radio Packet-Radio Digest Thu, 4 Apr 91 Volume 91 : Issue 81 Today's Topics: FLEA at MIT 21 April 91 Cambridge MA Looking for info on a specific freq. band TAPR tnc-2 upgrades Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 4 Apr 91 07:21:10 GMT From: w1gsl@athena.mit.edu Subject: FLEA at MIT 21 April 91 Cambridge MA To: packet-radio@ucsd.edu Its just about time for this years first.... ***** 50 cent buyers discount with hardcopy of this notice ******** COMPUTERS - ELECTRONICS - HAM RADIO - COMPUTERS - ELECTRONICS FLEA all SUMMER at MIT Sunday, April 21, 1991 9AM-2PM Come to the city for a great flea - plenty of free parking. MIT's electronics and ham radio flea will take place on the third Sunday of each month this summer, April thru October. There is tailgate space for over 400 sellers and free, off-street parking for >1000 cars! Buyers admission is $1.50 (you get 50c off if you're lucky enough to have a copy of our add) and sellers spaces are $8.00-each at the gate or $5.00 if mailed by the preceding 5th. A sellers Season Pass for all 7 sundays is available for $28 if purchased by April 21st The flea will be held at the corner of Albany and Main streets in Cambridge; right in the Kendall Square area from 9AM to 2PM, with sellers set-up time starting at 7AM. !! RAIN or SHINE !! Have no fear of rain, a covered tailgate area is available for all sellers (6'8" clearance). Talk-in: 146.52 and W1XM/R-449.725/444.725 (PL 114.8/2A). Sponsors: MIT Electronics Research Society MIT UHF Repeater Association (W1XM) MIT Radio Society (W1MX) Harvard Wireless Club (W1AF) For more info / advanced reservations 617 253 3776 ******** 50 cent buyers discount with hard copy of this notice ************ ------------------------------ Date: 3 Apr 91 14:49:26 GMT From: swrinde!mips!apple!uokmax!d.cs.okstate.edu!unx2.ucc.okstate.edu!uccxmgm@ucsd.edu Subject: Looking for info on a specific freq. band To: packet-radio@ucsd.edu The frequency range is occupied by TV channels 7, 8, 9, and 10. If one of those channels in your area is not used, then frequencies in that range would be the safest to use. channel 7 174-180MHZ channel 8 180-186MHZ channel 9 186-192MHZ channel 10 192-198MHZ ------------------------------ Date: 3 Apr 91 04:08:28 GMT From: usc!cs.utexas.edu!solo.csci.unt.edu!vaxb.acs.unt.edu!greg@ucsd.edu Subject: TAPR tnc-2 upgrades To: packet-radio@ucsd.edu In article <1991Apr2.214536.7357@math.lsa.umich.edu>, hideg@spsd4360a.erim.org (Steve Hideg {Mr. Fabulous} ) writes: > Hello. > > Does TAPR still offer tnc-2 upgrades? > I have two HD-4040s, I'd like to upgrade them. > > tnx. > > ____________________________________ > Steve Hideg N8HSC > > hideg@spsd4360a.erim.org Hi Steve, Just call the TAPR office at (602) 749-9479 from Tuesday through Friday, 10am - 3pm MST. -- or if you have Fax capbility you can use the TAPR FAX line (602) 749-5636. I would suggest you drop a line, since we have a few of the TNC-1 upgrades left and there is no plan to order additional kits after we sell the current stock. Not many units like yours left that havn't been upgraded. I believe the price now is $60.00 for the TNC-1 upgrade. There was a slight price upgrade that will be published in the next PSR. 73 - Greg Jones, WD5IVD Sec/Trea TAPR ------------------------------ Date: 4 Apr 91 01:23:45 GMT From: sdd.hp.com!spool.mu.edu!munnari.oz.au!manuel!csc.canberra.edu.au!echo!skcm@ucsd.edu To: packet-radio@ucsd.edu References <1991Mar29.223715.5564@bellcore.bellcore.com>, <skcm.670398101@ise>, <1991Apr1.222931.755 Subject : Re: ? how to route with tcpip In <1991Apr1.222931.7557@bellcore.bellcore.com> karn@epic.bellcore.com (Phil R. Karn) writes: >In article <skcm.670398101@ise>, skcm@echo.canberra.edu.au (Carl Makin) writes: >|> In the case of a BBS forwarding traffic then the BBS is the "originating" >|> station. In the case of someone navigating his way thru the network >|> then HE remains the "originating station" despite how many links may >|> be carrying his traffic. >This STILL makes no sense. There is absolutely no fundamental >difference between an autoforwarding BBS and an IP router. Both are HOLD THE PRESSES. I've since had words with some people in the know and yes, BBSes as they currently exist in Australia are illegal. :-( The relevant people in DoTC however are not going to do anything yet however we have to do something to fix the regs problems we now have. Sigh. More work for the seminar this weekend. Thanks for pointing it out Phil. Carl. ------------------------------ End of Packet-Radio Digest ****************************** Date: Fri, 5 Apr 91 04:30:06 PST From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #82 To: packet-radio Packet-Radio Digest Fri, 5 Apr 91 Volume 91 : Issue 82 Today's Topics: UO-14 satellite sounded really weird tonight Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 4 Apr 91 18:20:36 GMT From: idacrd!mac@princeton.edu Subject: UO-14 satellite sounded really weird tonight To: packet-radio@ucsd.edu ------------------------------ Date: (null) From: (null) It sounds like it went back to AFSK and the bootloader. They are probably reloading code from scratch. Bob -- ____________________________________________________________________________ My opinions are my own no matter | Robert W. McGwier, N4HY who I work for! ;-) | CCR, AMSAT, etc. ---------------------------------------------------------------------------- ------------------------------ End of Packet-Radio Digest ****************************** Date: Sat, 6 Apr 91 04:30:04 PST From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #83 To: packet-radio Packet-Radio Digest Sat, 6 Apr 91 Volume 91 : Issue 83 Today's Topics: KPC-2 (2 msgs) UO-14 satellite sounded really weird tonight Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 5 Apr 91 02:10:03 GMT From: agate!apple!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!wa4mei!ke4zv!gary@ucbvax.berkeley.edu Subject: KPC-2 To: packet-radio@ucsd.edu In article <1991Apr2.214349.7268@math.lsa.umich.edu> hideg@spsd4360a.erim.org (Steve Hideg {Mr. Fabulous} ) writes: >Is the Kantronics KPC-2 a tnc-2 clone? No. Gary ------------------------------ Date: 4 Apr 91 20:29:54 GMT From: hpl-opus!hpnmdla!alanb@hplabs.hpl.hp.com Subject: KPC-2 To: packet-radio@ucsd.edu In rec.radio.amateur.packet, hideg@spsd4360a.erim.org (Steve Hideg {Mr. Fabulous} ) writes: >Hello. >Is the Kantronics KPC-2 a tnc-2 clone? No. AL N1AL ------------------------------ Date: 5 Apr 91 16:12:15 GMT From: usc!wuarchive!rex!rouge!pc.usl.edu!jpd@ucsd.edu Subject: UO-14 satellite sounded really weird tonight To: packet-radio@ucsd.edu UO-14 was back to normal by the following day. I was able to download a few msgs describing what was going on: Create-time: Mon Apr 01 06:19:37 1991 Source: g0k8ka Destination: all Title: Reloads and Outages. Harold Price (NK6K) is temporary hostage at UoS, and we have been doing some work on FTL0 and the other UO-14 software. A lot of changes have been made since January, when we last reloaded. Reloading and testing may start tonight (01/04/91) UTC, so expect some interruptions to service and perhaps loss of the file system. Sorry. JWW Create-time: Wed Apr 03 08:31:21 1991 Source: g0k8ka Destination: all Title: UO3 DOWNLINK SWITCHING Keywords: UO3 ** QUICK STATUS REPORT ** Do not be alarmed by the sudden "disappearances" of UO-14's downlink; it is actually switching onto another frequency to send a few packets. When the spacecraft is idle (no broadcasts or FTL0 connections), the switch will take place every 25 seconds and 5 seconds of packets will be transmitted on the other downlink frequency. A full report on the "how and why" of this switching will be forthcoming. JWW Create-time: Thu Apr 04 06:27:03 1991 Source: g0k8ka Destination: all Title: DOWNLINK CHANGES Keywords: UO-14 FTL0 UO-14 Downlink Changes >From 1400 UTC today, UoSAT-OSCAR-14 started switching its single downlink transmitter between its Amateur Satellite Service frequency (435.070 MHz), and an experimental UHF downlink frequency licensed outside of the Amateur Satellite Service. Amateur users will sometimes see the downlink "disappear" for as little as 250 msec or as long as 5 seconds. So long as the downlink eventually returns to 435.070 MHz, there is nothing wrong with the satellite. UO-14's can operate outside the amateur service to support experimental communications trials to and from stations in developing countries. Most of these trials will be conducted by The Volunteers In Technical Assistance (VITA). VITA is an international development organisation with long-standing ties to AMSAT and UoSAT. VITA funded the construction of the UO-11 Digital Communications Experiment (DCE) by AMSAT volunteers in the USA and Canada, and contributed to the development costs of the UO-14 PACSAT Communications Experiment (PCE) hardware and software. It was, in part, UoSAT's arrangement with VITA which allowed G0/K8KA time to write FTL0 and the file system software now running on UO-14, PACSAT and LUSAT. VITA will be using UO-14 to transfer technical information amongst a number of stations in developing countries. These stations will be in areas which are poorly served by existing data communications systems. VITA's UO-14 operations are an experimental pilot system which will allow VITA to pass traffic which might not be appropriate for amateur channels. The UO-14 pilot studies will help VITA determine whether or not to purchase its own dedicated satellite. This operations are licensed by the FCC in the USA and by individual national authorities in other countries. It has been common for the RS series amateur satellite transponders to ride on the satellite bus of a non-amateur transponder or instrument; VITA's "hitchhiking" on UO-14 is similar. On a microsatellite like UO-14, however, the distinction between amateur and non-amateur payloads is blurred, and unique resources such as the downlink transmitter, the RAM message store and the CPU are actually shared. This symbiosis benefits both the amateur satellite community and the non-amateur organisation. Through collaboration with non-amateur organisations, the amateur satellite service conclusively shows its value as a force for technology development and testing. This, in turn, should help to secure our frequencies against competitors. On a more basic level, transfer of technology to paying customers helps fund present and future amateur satellite missions. These commercial (if not profit-making) ventures keep organisations like UoSAT, AMSAT-NA and TAPR financially sound so that they can continue to pursue technical goals with benefits to the amateur community. This change in UO-14 operations was made possible after NK6K travelled to the United Kingdom as a volunteer courier - carrying solar panels for UoSAT-F. NK6K and G0/K8KA took advantage of this brief visit to add a new WB6YMH I/O driver and to change QAX.25 (the software TNC), the broadcast protocol, and FTL0. In orbit testing started on 2 April. As the testing dual-frequency operation on UO-14 continues, we will issue further technical and "administrative" updates. Jeff Ward, G0/K8KA, UoSAT -- -- James Dugal, N5KNX Internet: jpd@usl.edu Associate Director Ham packet: n5knx@k5arh Computing Center US Mail: PO Box 42770 Lafayette, LA 70504 University of Southwestern LA. Tel. 318-231-6417 U.S.A. ------------------------------ End of Packet-Radio Digest ****************************** Date: Sun, 7 Apr 91 04:30:04 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #84 To: packet-radio Packet-Radio Digest Sun, 7 Apr 91 Volume 91 : Issue 84 Today's Topics: Is there a packet gateway from Internet? NET for Mac Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 7 Apr 91 06:17:20 GMT From: usc!jarthur!nntp-server.caltech.edu!pjb@ucsd.edu Subject: Is there a packet gateway from Internet? To: packet-radio@ucsd.edu I am curious if there is a way to send messages out to a packet BBS in Tennessee from my QTH in california. The real trick is this: I don't have packet equipment. I would like to use some sort of gateway machine that is tied to the national INTERNET or BITNET. I will be pleasantly suprised if such a thing exists, since whoever allowed messages to travel from the INTERNET onto the airwaves would have to take some sort of steps to insure they came from a liscensced amateur... Paul Brewer pjb@coil.caltech.edu pjb@hss.caltech.edu KI6CQ ------------------------------ Date: 6 Apr 91 18:25:41 GMT From: news@rsch.wisc.edu Subject: NET for Mac To: packet-radio@ucsd.edu Where can I ftp a copy of NET or NOS for the Mac? Thanks, Matt -- Matt Zeidenberg zeiden@cs.wisc.edu 608-257-3933 608-262-5786 ------------------------------ End of Packet-Radio Digest ****************************** Date: Tue, 9 Apr 91 04:30:04 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #85 To: packet-radio Packet-Radio Digest Tue, 9 Apr 91 Volume 91 : Issue 85 Today's Topics: BAYCOM program Problem with TAPR 1.1.7b KISS. (2 msgs) PROXIM radios Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 8 Apr 91 15:31:30 GMT From: njin!njitgw.njit.edu!root@princeton.edu Subject: BAYCOM program To: packet-radio@ucsd.edu Hi! I have been hearing about a software called BAYCOM but I just could not get hold of it. Do anyone of you knows of a ftp site where I can get it. Thanks in advance! -Sam- scr2275@hertz.njit.edu scr2275@tesla.njit.edu ------------------------------ Date: 8 Apr 91 12:25:57 GMT From: sdd.hp.com!spool.mu.edu!munnari.oz.au!manuel!csc.canberra.edu.au!echo!skcm@ucsd.edu Subject: Problem with TAPR 1.1.7b KISS. To: packet-radio@ucsd.edu I grabbed 1.1.7b from TOMCAT a couple of weeks ago and installed it in a TNC-2. It seems like the old param ax0 255 0 command won't return you to cmd: mode. In one case it locked the TNC. Has anyone else come across this? Is there another way to return it to cmd: mode? Carl. ------------------------------ Date: 8 Apr 91 14:18:17 GMT From: munnari.oz.au!uniwa!cc.curtin.edu.au!nmurrayr@uunet.uu.net Subject: Problem with TAPR 1.1.7b KISS. To: packet-radio@ucsd.edu In article <skcm.671113557@ise>, skcm@echo.canberra.edu.au (Carl Makin) writes: > I grabbed 1.1.7b from TOMCAT a couple of weeks ago and installed it in > a TNC-2. It seems like the old param ax0 255 0 command won't return you > to cmd: mode. In one case it locked the TNC. > > Has anyone else come across this? Is there another way to return it to > cmd: mode? > > Carl. I haven't looked at the KISS code in 1.1.7b yet, but in the earlier versions of KISS the command should really be "param ax0 255 1". The second parameter should be non-zero. (Some earlier instructions would have us enter "param ax0 255", but whether this returns to AX25 mode or not depends on the first character sent after the "param ..." command). I have used 1.1.7b here for a couple of months (well, it seems that long), and it's not given me any problems. .....Ron -- =============================================================================== Internet: Murray_RJ@cc.curtin.edu.au | "You can lead a horse to ACSnet: Murray_RJ@cc.cut.oz.au | water, but if you can Bitnet: Murray_RJ%cc.curtin.edu.au@cunyvm.bitnet | get him to float on his UUCP : uunet!munnari.oz!cc.curtin.edu.au!Murray_RJ | back you've really got Amateur Packet Radio: VK6ZJM@VK6BBS.#WA.AUS.OC | something" TCP/IP: 44.136.204.14, 44.136.204.19 | -- Murphy's Law I =============================================================================== ------------------------------ Date: 8 Apr 91 13:47:21 GMT From: news-mail-gateway@ucsd.edu Subject: PROXIM radios To: packet-radio@ucsd.edu Does anyone have a telephone number or address for PROXIM who made those 900 Mhz spread spectrum radios whose specs were reported earlier? Roy, AA4RE ------------------------------ End of Packet-Radio Digest ****************************** Date: Wed, 10 Apr 91 04:30:04 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #86 To: packet-radio Packet-Radio Digest Wed, 10 Apr 91 Volume 91 : Issue 86 Today's Topics: BAYCOM program Frequency coordination for DSY modems Packet-Radio Digest V91 #85 packet transmitter hunts (2 msgs) TRF Receiver (2 msgs) Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 9 Apr 91 06:54:04 GMT From: bloom-beacon!eru!hagbard!sunic!news.funet.fi!kannel!huopio@ucbvax.berkeley.edu Subject: BAYCOM program To: packet-radio@ucsd.edu > Nntp-Posting-Host: hertz.njit.edu > Hi! > I have been hearing about a software called BAYCOM but I just could > not get hold of it. Do anyone of you knows of a ftp site where I > can get it. > Thanks in advance! > -Sam- archie> prog baycom # matches / % database searched: 2 / 97% Host csseq.tamu.edu (128.194.2.20) Last updated 21:46 29 Mar 1991 Location: /pub FILE r--r--r-- 142722 Feb 25 15:48 baycom.zip Host ipl.rpi.edu (128.113.14.50) Last updated 17:54 5 Apr 1991 Location: /pub/archive/archives/rec/radio DIRECTORY rwxr-xr-x 512 Mar 26 06:05 baycom archie> --Kauto -- ****************** Kauto Huopio (huopio@kannel.lut.fi) ********************** * Mail: Kauto Huopio, Punkkerikatu 1 A 10, SF-53850 Lappeenranta,Finland * ***************************************************************************** ------------------------------ Date: 9 Apr 91 16:16:15 GMT From: news-mail-gateway@ucsd.edu Subject: Frequency coordination for DSY modems To: packet-radio@ucsd.edu Help. Our Wisconsin Frequency Coordinator would like more input on what frequencies are being used for WA4DSY modems. I think it's important to plan the use of the spectrum while we CAN! So, anyone with input on the topic (especially the Ottawa folks), please post the frequencies allocated or proposed in YOUR area. Also please CC: pat@pgd.adp.wisc.edu 128.104.198.22, as I am WAY behind in my forum reading.... Try an list out freq's in at least 220/432/905 areas.. Tnx a million, Pat P.S., I need this YESTERDAY :-). pat@pgd.adp.wisc.edu 128.104.198.22 ------------------------------ Date: 9 Apr 91 14:14:04 GMT From: news-mail-gateway@ucsd.edu Subject: Packet-Radio Digest V91 #85 To: packet-radio@ucsd.edu Re: Proxim Address Proxim Inc, 295 North Bernado Ave Mountain View CA 94043 415-960-1630 According to my spec sheet, they sell 4 spread spectrum radios: RXA-100 Serial Intf 121Kbps 100mW output RXA-1000 " " 1W RDA-100 Serial/Parallel " 100mW RDA-100/2 " " 242Kbps 100mw Their evaluation kits go for $2000 which includes 2 radios, 2 Engr test boards (RS-232 intf, switches for channel selection etc) and 2 antennas. By channels they mean separate (1 of 4) spreading code selection. Geoff - N6LXA ------------------------------ Date: 9 Apr 91 16:40:25 GMT From: usc!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu!wdlee@ucsd.edu Subject: packet transmitter hunts To: packet-radio@ucsd.edu If you've got a moment, consider the following... Could the unique capabilities of packet be exploited to create an enhanced transmitter hunt? As Matt used to say, "I'm not sure what I mean, so I'll listen to what I say." So, forgive me if I ramble. - perhaps bearings (taken by some contestants) would be posted to a BBS (or something like DX net) to be shared by *all* players. In this manner, even those bound to their living rooms could play, with a Diet Coke in one hand, and their parallel rulers in the other... - points could be awarded at the end of play, not only for finding the transmitter (those lucky mobile guys!) but also for posting good bearings. - If we do a little pre-game work, and build a table of call and physical locations, then the fixed stations could just as easily contribute to play. - Should the transmitter being hunted just emit a beacon? Could the beacon packet contain hints? (or a goose chase?) - <your ideas here...> Gotta go, my girlfriend wants to go to lunch... David david@moe.ece.utexas.edu ------------------------------ Date: 9 Apr 91 18:22:29 GMT From: pa.dec.com!shlump.nac.dec.com!sousa.enet.dec.com!sndpit.enet.dec.com!smith@decwrl.dec.com Subject: packet transmitter hunts To: packet-radio@ucsd.edu In article <46925@ut-emx.uucp>, wdlee@ccwf.cc.utexas.edu (david lee) writes... >If you've got a moment, consider the following... >Could the unique capabilities of packet be exploited to create >an enhanced transmitter hunt? [...] Neat ideas! How about being able to 'ping' the fox with a high-speed packet radio and measuring the round-trip delay to get range and bearing? Yes, it requires both ends to have very quick turnaround (or split-band), but it can't be _that_ difficult... Willie Smith smith@sndpit.enet.dec.com smith%sndpit.enet.dec.com@decwrl.dec.com {Usenet!Backbone}!decwrl!sndpit.enet.dec.com!smith ------------------------------ Date: 9 Apr 91 12:41:18 GMT From: usc!samsung!rex!uflorida!mlb.semi.harris.com!sunman.mlb.semi.harris.com!rps@ucsd.edu Subject: TRF Receiver To: packet-radio@ucsd.edu Can anybody supply me with a schematic for a tube TRF receiver? Regards, Ray S rps@sunman.mlb.semi.harris.com ------------------------------ Date: 9 Apr 91 22:07:44 GMT From: swrinde!mips!cs.uoregon.edu!milton!whit@ucsd.edu Subject: TRF Receiver To: packet-radio@ucsd.edu In article <1991Apr9.124118.27031@mlb.semi.harris.com> rps@sunman.mlb.semi.harris.com (Ray Sumperyl) writes: > Can anybody supply me with a schematic for a tube TRF receiver? No such devices have been built by THAT name in most of a century. Any of the '60s vintage Radio Amateur Handbooks, though, will have 'grid-dip meter' construction articles, and a grid dip meter is exactly a TRF receiver (not terribly sensitive, though, as they usually leave out the preamplification). After mid-60's, the grid-dip meters used MOSFETs (what's a 'grid' in a MOSFET?). John Whitmore ------------------------------ End of Packet-Radio Digest ****************************** Date: Thu, 11 Apr 91 04:30:09 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #87 To: packet-radio Packet-Radio Digest Thu, 11 Apr 91 Volume 91 : Issue 87 Today's Topics: Network Development Update de n6gn/n6rce Packet-Radio Digest V91 #85 Sparcstation1 audio port for low-speed DSP modem? TheNET 1.16 TRF Receiver Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 9 Apr 91 23:35:16 GMT From: hpl-opus!hpnmdla!glenne@hplabs.hpl.hp.com Subject: Network Development Update de n6gn/n6rce To: packet-radio@ucsd.edu Spring 1991 Status Report of Hubmaster and Intermediate Speed Network Development in Northern California. This is an update of some of the recent moderate speed amateur radio network developments in Northern California already described in the 9th ARRL Computer Networking Conference proceedings, QEX Magazine and elsewhere. As previously stated, our efforts are not only toward providing faster hardware and link layer operation but to more efficiently use amateur radio resources to provide amateurs with network layer access at moderate speeds. We anticipate that this will greatly improve current amateur radio applications and also provide a platform for completely new ones over wide areas. We hope that many "non-digital" amateurs will find the services such a network can provide to be both interesting and personally useful. We also hope that "non-radio" individuals with computer and networking interests will discover amateur radio as a wonderful environment in which to pursue their interests. Doing all this requires new radio hardware and digital hardware to handle the .25 Mbps to approximately 2 Mbps data streams. Economical operation at this performance level requires line-of-sight radio links. Hardware and new protocols which effectively utilize it are being devised. We have developed an architecture which allows small groups of amateurs to share both the expense and performance in a manner similar to current NBFM repeaters. One of the goals of this moderate speed solution is to solve the hidden transmitter problem without requiring users to suffer the additional complexity and expense of full duplex radio hardware. We have found AX.25 not to be sufficient for these goals. Perhaps most importantly, new kinds of coordination and cooperation among amateurs are becoming necessary to successfully implement all of this. System Components At present the intermediate speed radio hardware includes 900 MHz, 256 kbps 10 watt radios along with 13 element yagi antennas and a commercial colinear antenna for use at the hub. See the Hubmaster paper in the 9th ARRL CNC and March 1990 QEX/Gateway for details. Interface hardware to connect the radio(s) to the digital i/o is also necessary. Some of the 256 kbps radios along with the previously described 2 Mbps microwave link hardware may be used on initial backbones. The digital interface, MIO ("Mundane" or "Multi-function" I/O), can plug into a user's personal computer or be run standalone (remotely) as a hubserver and multiport switch/router to the backbone and other clusters. MIO has up to 4 SCC ports capable of driving a great variety of radio or wireline hardware. It is capable of emulating a conventional AX.25 TNC on one port while it serves a 1Mbps microwave backbone connection and a cluster of users running Hubmaster protocol at 256 kbps on other ports. A "stripped down" version of MIO can be run as the interface between the user's computer and 256 kbps radio. In order for all this hardware to operate together considerable software is necessary. This includes a packet driver for KA9Q NOS, Hubmaster primary and secondary software along with a software development toolkit including debugger. Provision has been made so that software can be written in C++ and put into ROM or loaded into RAM either via over-the-air transfer for the remote case or through shared memory to the PC in the plug-in case. The toolkit will provide basic interface to the Hubmaster polling protocol allowing developers to port their own protocols into the environment. If Borland C is used, then S/W debugging can be done via the TD/TDREMOTE interface. Status of Individual Components Radio Hardware, N6GN For several months two 10 watt radios, a prototype and a "pilot" unit, have been complete. A bit error rate tester was designed and built and BER and multipath distortion measurements have been made on-bench as well as across a variety of real paths from 50 feet to 7 miles using the first two radios. A quantity of commercially fabricated printed circuit boards have been made. One radio using the commercial boards is now virtually complete and working. Major parts for building 12-15 units are on hand. The intent is to build approximately 6 more radios for immediate deployment by N6RCE in Hubmaster protocol development and by N6GN for inter-cluster backbone communications. 13 element 5' boomlength yagi antenna have been designed, built and measured. Performance is within a few tenths of a dB of expectations. A commercial omnidirectional colinear for hub use is being evaluated. Interface circuits which provide logic level conversion between the radios and MIO are completed. Additional interfaces with provision for external clock/data encoding and decoding are in progress. Digital Hardware, N6RCE The basic MIO PC card has been completed. Ten boards have been commercially fabricated. Two of these have been loaded and the hardware completely debugged. Software development is proceeding. Additional boards are being assembled. MIO is designed as a full length IBM PC plug-in adapter. The card sports a V40 microprocessor running at 8MHz, 768K DRAM, up to 256K EPROM, and a pair of ZILOG ESCCs. It is designed for 8MHz (ISA) 8-bit slot PC buses but will function in any AT slot. MIO can function in any of three ways; entirely standalone, only drawing power from the PC or it can interface with the host processor. Interface is via a shared memory window. The size can be either 8K or 64K. The shared memory window address and size are set by writing to a control I/O register. Possible base addresses for the window are C8000, CC000, D8000, DC000. This control register also allows the host PC to generate interrupts to the V40, and to program the IRQ line used by MIO to interrupt the host. The V40 is an integrated microcomputer containing an interrupt priortizer, four DMA channels, and three timer/counters. The DRAM refresh controller and external bus arbiter for sharing DRAM with the host PC are also utilized. Software, N6RCE A software toolkit supports development and debugging with Borland C++ V2.0. A complete operating shell is supplied including linking, relocating and loading of code written on a PC platform. A run-time kernel provides for TOD keeping, interrupt management, DMA management, buffering, protocol manipulation and easy access to the Zilog ESCC ( give us your buffer, we'll get it there ). The programmer will be able to write software on a PC platform, compile and link on the PC with Borland TC++, load it onto the adapter, and debug it with the remote debugger supplied with TC++. (TC++ has a facility (TDREMOTE) which allows the target program to be debugged to run on one PC and the debugger to run on another PC. The two debuggers communicate via a serial link). This feature provides the possibility of remotely developing software running on hardware located at distant sites such as Hubmaster hubs or hilltop backbones from the comfort of a home QTH. System Status, Timetable, Targets and Priorities All development is currently being performed and funded by N6RCE and N6GN. Limited personal resources have set the speed of progress. We hope as hardware and protocols come on-line in Northern California that others will step in to develop applications. Such applications are becoming increasingly important to the furtherance of the project. We also hope that hardware will become commercially available for use by others outside of Northern California to start developing and enjoying the benefits of higher speed user network access. Current emphasis is on getting a minimal hub and backbone operating in time for the next ARRL Computer Networking Conference at San Jose, CA in September. Deployment of one or two clusters along with an interconnecting 256 kbps backbone is planned. To accomplish this, Hubmaster protocol refinement and backbone hardware/software development are running in parallel at N6RCE and N6GN, respectively. Future Targets and Checkpoints Future directions all rest on the completion of a functioning hub and backbone. Once this is accomplished the number and variety of options is very large indeed. Additional radios on other 900 MHz and 1200 MHz channels will need to be deployed to allow multiple physically close clusters to coexist. N6GN anticipates first modifying 900 MHz radios for 1200 MHz operation and then building all future radios in the 1200 MHz band. A minimum-expense combination low power user radio/interface ("layer 3 tnc") is anticipated with the goal of further reducing the cost of user hardware. N6GN hopes to have an opportunity to apply some ideas to substantially improve the cost/performance of microwave backbone hardware. In Northern California we hope to add additional clusters and to extend the backbone so that the Bay Area, Santa Rosa, North Coast and Sacramento users all have higher performance connectivity. Clearly these directions and opportunities require the cooperation and efforts of many people with many different talents. We hope that as others see functioning hardware and protocols along with available development tools that they will join in building and extending the network both in expanse and services. Since the function of the network is to support new and improved amateur radio applications we hope that many new ones will emerge. Existing BBS traffic and possibly DXPSN traffic may be supported. We hope that wider area connectivity will evolve. The SF Bay Area to Southern California path is one early possibility. NNTP, "News" protocol, client and servers are already in use at lower speeds and this network should be much more able to support Usenet style distribution of dialogue and information to amateurs over a wide area. Many other applications including amateur FAX, voice mail, digital voice and a NBFM to IP gateway, to name a few, are being considered. Where to Find Out More Since this is just an update on our recent intermediate speed networking efforts we refer you to December 1989 Ham Radio Magazine, the 1991 ARRL Radio Amateurs Handbook, March 1990 QEX/Gateway and particularly to papers in the 8th and 9th ARRL Computer Networking Conference proceedings for details of our approach and what we are doing. de N6GN and N6RCE April 9, 1991 ------------------------------ Date: 10 Apr 91 17:35:14 GMT From: unix!snmp.sri.com!larson@husc6.harvard.edu Subject: Packet-Radio Digest V91 #85 To: packet-radio@ucsd.edu In article <9104091414.AA01115@ale.Eng.Sun.COM> geoffb@Eng.SUn.COM (Geoffrey Baehr) writes: > > Their evaluation kits go for $2000 which includes 2 radios, 2 Engr test > boards (RS-232 intf, switches for channel selection etc) and 2 antennas. > By channels they mean separate (1 of 4) spreading code selection. Actually, it is frequency, not code. There are 7 channels, 4 that claim to be non-overlapping, and 3 half-channel spaced ones between them. The frequencies are listed in one of the manuals, as I recall. Alan ------------------------------ Date: 10 Apr 91 16:58:44 GMT From: swrinde!zaphod.mps.ohio-state.edu!rpi!news-server.csri.toronto.edu!utgpu!cunews!bnrgate!bwdls61!bnr.ca!mleech@ucsd.edu Subject: Sparcstation1 audio port for low-speed DSP modem? To: packet-radio@ucsd.edu The Sparcstation1 has an 8-bit PCM audio port. Has anyone thought about using that port to implement some low-speed DSP modems? I suspect that the SPARC has enough guts to do this, but I'm not enough of a DSP-dweeb to know for sure. Has anyone made an attempt? -- Marcus Leech, 4Y11 Bell-Northern Research |opinions expressed mleech@bnr.ca P.O. Box 3511, Stn. C |are my own, and not VE3MDL@VE3JF.ON.CAN.NA Ottawa, ON, CAN K1Y 4H7 |necessarily BNRs ------------------------------ Date: 10 Apr 91 23:37:00 GMT From: news-mail-gateway@ucsd.edu Subject: TheNET 1.16 To: packet-radio@ucsd.edu Can anyone advise me where I can get a copy of TheNET 1.16? I got a copy of it off of TOMCAT, and the code acts weird, so I got a copy of Le NET2 which was on the K4NGC telephone system. It too is buggy. Is this code all bugs? If so are there any revisions or later versions? Had nice features like reconnect to the last connected node, a quit from far end, and was setable to either a open end user system or closed backbone tunk. TheNET Plus 2.06 isn't configurable as much as 1.16, but since it was buggy, went back to 1.0. 73 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Charles Layno BITnet: wb4wor@UNCG.BITNET P.O. Box 8252 Internet: wb4wor@steffi.acc.uncg.edu Greensboro, NC CompuServe: 71441,1562 27419-0252 Packet Radio Mail: WB4WOR @ WB4WOR.#GSO.NC.USA.NA "REALITY..................WHAT A CONCEPT!" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------ Date: 10 Apr 91 19:19:37 GMT From: usc!rpi!zaphod.mps.ohio-state.edu!caen!stealth@ucsd.edu Subject: TRF Receiver To: packet-radio@ucsd.edu In article <1991Apr9.220744.4049@milton.u.washington.edu> whit@milton.u.washington.edu (John Whitmore) writes: >In article <1991Apr9.124118.27031@mlb.semi.harris.com> rps@sunman.mlb.semi.harris.com (Ray Sumperyl) writes: > >> Can anybody supply me with a schematic for a tube TRF receiver? > > No such devices have been built by THAT name in most of [...] Could you, Mr. Whitmore, please refrain from crossposting your article to all of rec.radio, and could you, Mr. Sumperyl, take a look at what groups you`re following up to and modify them so that they're appropriate? I mean really, who in rec.radio.cb would have a schematic for a tube TRF reciever? And why in misc.forsale, let alone rec.radio.cb?? -- Mike Pelletier | The University of Michigan's | [this section intentionally] Computer Aided Engineering Network | [ left blank ] Usenet, UUCP, IRC and mail admin | ------------------------------ End of Packet-Radio Digest ****************************** Date: Fri, 12 Apr 91 04:30:07 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #88 To: packet-radio Packet-Radio Digest Fri, 12 Apr 91 Volume 91 : Issue 88 Today's Topics: NET for Mac TRF Receiver Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 11 Apr 91 09:38:40 GMT From: news-mail-gateway@ucsd.edu Subject: NET for Mac To: packet-radio@ucsd.edu Try apple.com in their directory /pub/ArchiveVol1/tcpip/ka9q Their are other sites which carry ka9q net, but I am not sure if it is for MAC. Hope this is of help. Greetings, Michel (ON6ML) ------------------------------ Date: 11 Apr 91 20:42:53 GMT From: world!ksr!jfw@decwrl.dec.com Subject: TRF Receiver To: packet-radio@ucsd.edu In <1991Apr9.220744.4049@milton.u.washington.edu> whit@milton.u.washington.edu (John Whitmore) writes: >In article <1991Apr9.124118.27031@mlb.semi.harris.com> rps@sunman.mlb.semi.harris.com (Ray Sumperyl) writes: >> Can anybody supply me with a schematic for a tube TRF receiver? > No such devices have been built by THAT name in most of a century. >Any of the '60s vintage Radio Amateur Handbooks, though, will have 'grid-dip >meter' construction articles, and a grid dip meter is exactly a TRF receiver >(not terribly sensitive, though, as they usually leave out the >preamplification). After mid-60's, the grid-dip meters used MOSFETs (what's >a 'grid' in a MOSFET?). Well, in fact the 1963 Radio Amateur's Handbook has schematics for single-stage tube TRF receivers; you would just build a detector stage (plate detector, infinite impedance detector, or grid-leak detector) and wire the antenna to the RF input. You could then add an RF amplifier, if you wanted, remembering not to cheat and do any conversion stages ;-). As for no one building a TRF receiver in most of a century, check out the Ferranti ZN414 AM Receiver chip (available from Circuit Specialists and a couple of other places). It's a 10 transistor TRF receiver (4 amplifier stages, detector, and AGC) built into a TO-92 transistor package; add two resistors, two bypass capacitors, an LC tank, and an audio amp, and you have a complete receiver. (The 1963 Handbook also has a 110 page advertisement section that will make you CRY -- MAYBE a quarter of the advertisers still exist) ------------------------------ End of Packet-Radio Digest ****************************** Date: Sat, 13 Apr 91 04:30:08 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #89 To: packet-radio Packet-Radio Digest Sat, 13 Apr 91 Volume 91 : Issue 89 Today's Topics: In reply to yesterday's message re: using SPARCstation as a modem packet transmitter hunts (2 msgs) Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 12 Apr 91 15:12:08 GMT From: news-mail-gateway@ucsd.edu Subject: In reply to yesterday's message re: using SPARCstation as a modem To: packet-radio@ucsd.edu A friend in SUN told me that one of his colleagues has written a modem for that audio port. Just a simple 300baud (V21) modem as far as I know. I've got no other details, although I can ask. Steve, GI8OYA ------------------------------ Date: 12 Apr 91 15:45:00 GMT From: swrinde!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!wuarchive!emory!wa4mei!ke4zv!gary@ucsd.edu Subject: packet transmitter hunts To: packet-radio@ucsd.edu In article <1059@sousa.enet.dec.com> smith@sndpit.enet.dec.com (Willie Smith) writes: > >In article <46925@ut-emx.uucp>, wdlee@ccwf.cc.utexas.edu (david lee) writes... >>If you've got a moment, consider the following... >>Could the unique capabilities of packet be exploited to create >>an enhanced transmitter hunt? >[...] > >Neat ideas! How about being able to 'ping' the fox with a high-speed >packet radio and measuring the round-trip delay to get range and bearing? >Yes, it requires both ends to have very quick turnaround (or split-band), >but it can't be _that_ difficult... Good idea for a GAME Willie, but the real use of T-hunting is to prepare the hunters for real situations like tracking down jammers and finding downed aircraft. The targets normally don't cooperate in this way. Using packet to coordinate the hunt is a very good idea and one that has been picked up locally. The bad guys have scanners and always seem to find your coordination frequency and come up to taunt you. Using packet on a busy LAN frequency totally frustrates them. While on the T hunt topic, does anyone have experience with using a doppler direction finder coupled with an in car Loran C unit and a laptop to do automatic triangulation on the move? Also, is anyone using a group of fixed stations linked in real time by packet to do automatic triangulation? Cooperation is the only way to nail these guys fast. Gary KE4ZV ------------------------------ Date: 12 Apr 91 22:46:56 GMT From: theory.tn.cornell.edu!payne@THEORY.TN.CORNELL.EDU Subject: packet transmitter hunts To: packet-radio@ucsd.edu In article <2728@ke4zv.UUCP> gary@ke4zv.UUCP (Gary Coffman) writes: >While on the T hunt topic, does anyone have experience with using a >doppler direction finder coupled with an in car Loran C unit and a >laptop to do automatic triangulation on the move? Also, is anyone using >a group of fixed stations linked in real time by packet to do automatic >triangulation? Cooperation is the only way to nail these guys fast. No experience, but the idea has been talked about a lot. We're working on building some of the DDF systems and one thing that came up was using packet to coordinate DFing efforts. We thought of using a DDF system, positioning box of some sort (Loran-C as you say, mainly because they are cheap), and some sort of electronic compass. As you drive around, the software would take the bearings, headings, and locations, and start building a probability density. Ah yes, digitized topo information might be useful, too. The next step would be to link all participating stations with packet. Doesn't really matter if they are fixed or mobile, as long as the data interchange is standardized. Again, none of this has been built. We have built a bunch of TDOA systems (ala Handy Tracker or Vector Finder) and are in the process of building a DDF system based on the DoppleScant article in QST (an aside, anyone have a *correct* schematic?). Another aside, anyone consider building their own Loran-C? It may not be worth it, since I've heard of inexpensive units for low $200s. -- = = = = = = = = = = = = = = = = = = = = = = = = = = = Andrew C. Payne, N8KEI UUCP: ...!cornell!batcomputer!payne INTERNET: payne@tcgould.tn.cornell.edu ------------------------------ Date: 12 Apr 91 02:05:38 GMT From: ogicse!milton!whit@ucsd.edu To: packet-radio@ucsd.edu References <1991Apr9.124118.27031@mlb.semi.harris.com>, <1991Apr9.220744.4049@milton.u.washington.edu>, <3106@ksr.com> Subject : Re: TRF Receiver In article <3106@ksr.com> jfw@ksr.com (John F. Woods) writes: >In <1991Apr9.220744.4049@milton.u.washington.edu> whit@milton.u.washington.edu (John Whitmore) writes: >>In article <1991Apr9.124118.27031@mlb.semi.harris.com> rps@sunman.mlb.semi.harris.com (Ray Sumperyl) writes: >>> Can anybody supply me with a schematic for a tube TRF receiver? >> No such devices have been built by THAT name in most of a century. >As for no one building a TRF receiver in most of a century, check out the >Ferranti ZN414 AM Receiver chip Okay, I guess I was a little strong on that statement; what I really meant was that TRF receivers usually show up as little glue components (like in a garage door opener) rather than as a 'receiver'. Yes, there IS a place for tuned RF receivers, but conversion is the norm nowadays (and has been for quite a few years). TRF works best at low frequency (where the Q of an LC circuit offers adequate selectivity), and its only real advantage (cost) has rather been taken away by the cheap ceramic IF filters in use nowadays. John Whitmore ------------------------------ End of Packet-Radio Digest ****************************** Date: Sun, 14 Apr 91 04:30:10 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #90 To: packet-radio Packet-Radio Digest Sun, 14 Apr 91 Volume 91 : Issue 90 Today's Topics: Buggy thenet plus 2.06? (Was TheNET 1.16) Driving to Dayton Hams from other countries Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 12 Apr 91 11:07:37 GMT From: deccrl!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!tcdcs!swift.cs.tcd.ie!phealy@decwrl.dec.com Subject: Buggy thenet plus 2.06? (Was TheNET 1.16) To: packet-radio@ucsd.edu In article <910C170D609F60E44B@uncg.bitnet>, WB4WOR%UNCG.BITNET@ncsuvm.ncsu.EDU (CHARLES LAYNO (WB4WOR)) writes: > user system or closed backbone tunk. TheNET Plus 2.06 isn't configurable as > much as 1.16, but since it was buggy, went back to 1.0. We were about to replace a working thenet v1.1 with thenet plus 2.06 locally (ie most of Ireland). Could somebody with experience of v2.06 and v1.0/v1.1 compare them for reliability in single and dual port configurations? -- Paul Healy, phealy@cs.tcd.ie, phealy@tcdcs.uucp, ei9gl.ampr.org, EI9GL@EI5CI Compter Vision Group, Department of Computer Science, Trinity College, Dublin 2. ------------------------------ Date: 13 Apr 91 22:50:37 GMT From: usc!sdd.hp.com!hp-col!winfree!bdale@ucsd.edu Subject: Driving to Dayton To: packet-radio@ucsd.edu Turns out I'm going to be driving to Dayton again this year, and at least part of the trip I'll be driving alone. I'd like to solicit suggestions for 2m and 70cm FM repeater freqs along the way, so that I can soak up a dose of real humanity in between CD's... :-) The route will be Colorado Springs to Aurora, IL, on the 19th and 20th of April, then Aurora to Dayton on Wednesday the 24th, and then Dayton to Colorado Springs on the 28th and 29th. I have a few repeater freqs scribbled in the margins of last year's AAA TripTik, particularly for central/eastern Kansas, but I've never driven I-80 before. Suggestions? If others want to jump in with queries about other routes, feel free! And if you're going to be at Dayton, wander by the Grace Communications booths at #570-571 and say hi! Bdale, N3EUA ------------------------------ Date: 13 Apr 91 22:12:41 GMT From: sdcc6!gchandra@ucsd.edu Subject: Hams from other countries To: packet-radio@ucsd.edu Hi I have a license from India. Could someone please let me know what do I have to do to start operating from here. I vaguely remember someone having told me that there is a reciprocal arrangement between the USA and India wherein operators from one country could operate in the other with the license obtained from the parent country. I doubt the validity of this but would like to know the rules. Thanks in advance Girish ------------------------------ End of Packet-Radio Digest ****************************** Date: Mon, 15 Apr 91 04:30:02 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #91 To: packet-radio Packet-Radio Digest Mon, 15 Apr 91 Volume 91 : Issue 91 Today's Topics: [ANS] Buggy thenet plus 2.06? (Was TheNET 1.16) [FWD] Buggy thenet plus 2.06? (TheNET 1.16) Buggy thenet plus 2.06? (Was TheNET 1.16) TAPR TNC-1 and upgrade Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 15 Apr 91 04:18:40 GMT From: news-mail-gateway@ucsd.edu Subject: [ANS] Buggy thenet plus 2.06? (Was TheNET 1.16) To: packet-radio@ucsd.edu In article <910C170D609F60E44B@uncg.bitnet>, WB4WOR%UNCG.BITNET@ncsuvm.ncsu.EDU (CHARLES LAYNO (WB4WOR)) writes: > user system or closed backbone tunk. TheNET Plus 2.06 isn't configurable as > much as 1.16, but since it was buggy, went back to 1.0. Paul Healy, phealy@cs.tcd.ie then asks: >We were about to replace a working thenet v1.1 with thenet plus 2.06 locally >(ie most of Ireland). Could somebody with experience of v2.06 and v1.0/v1.1 >compare them for reliability in single and dual port configurations? Let me make a few comments on this since Charles and I are friends and we were both looking at the same problems from two places in the same state. Version 1.16: Has lots of really GREAT features. A lot of things can be turned on and off with this version that are really helpful. However, there were some things that were unexplainable. 1. When a node with version 1.16 made a level 3 connect from the nodes list to a node running 1.0, the remote 1.0 node would show a LEVEL 2 UPLINK from the callsign and SSID of the 1.16 site connecting to it. This in ADDITION to the CIRCUIT being shown.... as normal. After the connection was broken, the remote node running 1.0 would STILL show the level 2 UPLINK from the 1.16 nodes callsign and ssid as being active. It only went away after the "no activity timer" on the parms setting deleted it. It also did some weird things when connecting to G8BPQ nodes. The 1.16 would initiate a level 3 connect, and the G8BPQ node would respond. Then the 1.16 would show the G8BPQ as a level 2 connect, would send it the list of available node commands (like a user that had made an incorrect command) and would THEN stop and would leave the user making the connect attempt right at the 1.16 node and NOT connect him through to the G8BPQ node. A SECOND attempt would go right through. If the false level 2 uplink was allowed to time out, this sequence would repeat all over again. All kinds of settings on parameter 30 were tried with no success at curing this problem. Comments are invited by users of 1.16 since it sure appears to be a neat version of TheNet and does a lot of things that are very helpful as Charles noted. Version 2.06: This version works perfectly and I have had no problems with it. I do not think that Charles has either, but I have only talked to him once today. It works over the RS-232 ports (back to back) perfectly, and I have had ZERO problems with it. Advantages are remote setting of Transmit Delay, among some other things... but not the choice to disable level-2 connects like ver. 1.16 had. It also adds the (H)eard command, which is like the MHeard feature in your basic TNC. Version 2.08: I think that this MIGHT have been the version that Charles was talking about. It has some great but rather dangerous features. First, it allows level 2 connects to be disabled as to make the node into a backbone only version. It ALSO has defined two dummy port assignments. This allows a sysop of the node to make a manual ROUTING entry that will dump a specific callsign with specific SSID, or a specific callsign with ANY SSID to a dummy port. I.E. You lock him out of the node. This is basically an administrative feature that allows a system manager to lock out completely a BBS or Node or ANYONE that thinks that the whole system is there to do anything he wants with it, no matter how damaging it is to everyone else. However... the PARMS settings are really whacko! I say that only because I have gotten used to PARM settings being in a certain order and being able to adjust certain things. With THIS version, you no longer have access to all PARM settings except when you initially burn the EPROM. The ones that remain are out of order from the usual sequence. It takes awhile to get used to this. Basically most of the Transport settings can only be changed by burning a new EPROM. Same with the password... burn it once, and that's it. You can't change it from the 232 port. Spaces can be included in this version (in the password) but in version 2.06 if you put a space in the password, it causes problems. I am running this version now and have had no problems with it at all and I have another TNC running 2.08 hooked back to back with it. Send me a message if you want more details. I just wish they at least had made all PARM settings available after sysop validation. One version of this code needs to go on a 2000 foot tower, and I do NOT want to go up the tower just to change a PARM setting carrying a new EPROM and a screwdriver. Mark Bitterlich wa3jpy@wb4uou.nc.usa.na mgb@tecnet1.jcte.jcs.mil ------------------------------ Date: 15 Apr 91 04:36:47 GMT From: news-mail-gateway@ucsd.edu Subject: [FWD] Buggy thenet plus 2.06? (TheNET 1.16) To: packet-radio@ucsd.edu >In article <910C170D609F60E44B@uncg.bitnet>, WB4WOR%UNCG.BITNET@ncsuvm.ncsu.EDU (CHARLES LAYNO (WB4WOR)) writes: >> user system or closed backbone tunk. TheNET Plus 2.06 isn't configurable as >> much as 1.16, but since it was buggy, went back to 1.0. > >We were about to replace a working thenet v1.1 with thenet plus 2.06 locally >(ie most of Ireland). Could somebody with experience of v2.06 and v1.0/v1.1 >compare them for reliability in single and dual port configurations? >-- >Paul Healy, phealy@cs.tcd.ie, phealy@tcdcs.uucp, ei9gl.ampr.org, EI9GL@EI5CI >Compter Vision Group, Department of Computer Science, Trinity College, Dublin 2. > Sorry for two messages on this, but in my last one I forgot to mention any description of version 1.0 and 1.1 and there is one very important thing to know about version 1.0 of TheNet! Version 1.0 has a very severe problem when running in a back to back configuration with another node. It develops routing loops between the two wired togeather nodes. It did this with another 1.0 node wired in, and also a Converse node. For this reason, 1.0 is NOT recommended for back to back use unless the second node is a Converse node with NO radio hooked to it, and you set the minimum quality for auto-update equal to the RS-232 quality. This will ensure that it will only update the other nodes callsign that is actually hooked to it and will not update any of the nodes that the 1.0 node actually hears on the HDLC port. This is a really kluged up way to get around the problem and it would be a lot better just to switch to 1.1-E 1.1-E is the entry node version and is sometimes just called: 1.1 It works in all configurations that could be tested, but you can not turn off level-2 connects, and you can not set TXD remotely. 1.1-I (or TN11-I) is the backbone version of 1.1 It allows no level 2 connects other than the sysops and up to four other callsigns which the SYSOPS adds. Two when you burn it, two later by uplink connect. This version was intended only for "node to node" level 3 connections in a backbone. And rambling on.... one other thing I forgot.... version 1.16 does not have a "host mode". All other version of TheNet do. Sorry for having to send two posts to cover all this.. my memory is slipping. :-) Mark Bitterlich wa3jpy@wb4uou.nc.usa.na mgb@tecnet1.jcte.jcs.mil ------------------------------ Date: 14 Apr 91 13:32:00 GMT From: news-mail-gateway@ucsd.edu Subject: Buggy thenet plus 2.06? (Was TheNET 1.16) To: packet-radio@ucsd.edu There appears to a missunderstanding in my last post. The buggy code refered to was 1.16 and NOT, I REPEAT, NOT 2.06. There are some things in 2.08 I REALLY DON'T LIKE, but it works too. Like in 2.08 it seems all the level 3 parms are hard coded in the eprom and are not remote changable. (REALLY HATE THAT! GO BACK THE OTHER WAY GENTS!). The call lockout feature for level 2 stations is a real abuser if it gets into the wrong hands. A good idea after the WA3QNS 900-number mess, but it opens the door for unscrupious persons to wreak havic in the network of your choice, TheNET, TCP-ip or (if you are unforunate to have a ROSE in you area). Hope this gets to the authors of TN PLUS 2.08. 73 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Charles Layno BITnet: wb4wor@UNCG.BITNET P.O. Box 8252 Internet: wb4wor@steffi.acc.uncg.edu Greensboro, NC CompuServe: 71441,1562 27419-0252 Packet Radio Mail: WB4WOR @ WB4WOR.#GSO.NC.USA.NA "REALITY..................WHAT A CONCEPT!" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------ Date: 13 Apr 91 09:09:34 GMT From: uhccux!uhcmtg.phys.hawaii.edu!tony@ames.arpa Subject: TAPR TNC-1 and upgrade To: packet-radio@ucsd.edu I have an original TAPR TNC-1 running in KISS mode with NOS. I have noticed that the TNC-1 has a tendency to drop packets from other stations. I have swapped out the TNC-1 with other-brand TNCs but using the same radio and found that the other TNCs do NOT lose packets like the TNC-1 did. After extensive monitoring, I've come to realize that the packets being dropped come from stations that use (relatively) short TXDELAYs. However, these same stations don't have trouble connecting to stations other than mine (probably because they're not running TNC-1s). I've recalibrated the TNC-1 and everything looks ok. The DCD light will come on properly anytime the radio hears a packet. But as I said, packets tend to get lost as NOS shows intermittent received packets from those stations (when full tracing is turned on). There is supposed to be an upgrade kit that turns the TNC-1 into a TNC-2 and I'm wondering if this upgrade might improve the TNCs performance. In other words, is the KISS code in the upgrade kit any better than the TNC-1 KISS code? Or perhaps the problem isn't in the KISS code but in the modem's PLL lockup speed? (And for that matter, does the upgrade kit come with KISS capability?) Anyone have experience with either the upgrade kit or using the higher clock speed in a TNC-1? I've also tried using the faster clock speed but it seems that EVERYTHING that's timed is reduced by one-half. So I'm guessing that some EPROM timing mods need to be made before I can run at the higher clock speed in the TNC-1. What kind of mods need to be made to the EPROMS? Antonio Querubin tony@uhcmtg.phys.hawaii.edu AH6BW ------------------------------ End of Packet-Radio Digest ****************************** Date: Tue, 16 Apr 91 04:30:07 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #92 To: packet-radio Packet-Radio Digest Tue, 16 Apr 91 Volume 91 : Issue 92 Today's Topics: FOR SALE: AIRLINE TICKETS HELP with MARS MCS PBBS Problems (long) Packet buzzwords Repeater maps in Europe Texas Packet Radio Society Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 16 Apr 91 03:40:07 GMT From: mvb.saic.com!ieee.org!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!toml@ucsd.edu Subject: FOR SALE: AIRLINE TICKETS To: packet-radio@ucsd.edu =========================================================================== FOR SALE: Two (2) Tickets ANYWHERE =========================================================================== Fly ROUND-TRIP to: South America Europe India United States - FLY ANY TIME - FLY FROM ANY CITY - FLY TO ANY DESTINATION CITY You choose the dates and times of travel !!!! NO RESTRICTIONS !!!!!!!!!! (Fly tomorrow if you like) ASKING: $1400/pair or Best Offer CALL: Tom at (212) 864-0089 E-MAIL: toml@columbia.edu ------------------------------ Date: 15 Apr 91 17:02:15 GMT From: elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!rpi!crdgw1!seattle!cornett@ames.arpa Subject: HELP with MARS MCS PBBS Problems (long) To: packet-radio@ucsd.edu I helped my uncle install MCS for his MARS packet bulletin board, but it doesn't work quite right when started. The version is 6.7.2 running on an AT clone; his TNC is a KAM, which MCS supports. PROBLEMS: 1. TNCSET does not work correctly - it cannot find the 1A5 entry in the tnc1a5.scr library. Using a utility to locate strings in the library revealed only 1a4 entries. tnc1a5.sqz was not on the disks. Is there a way to use vidpop to create the entries? Can the .sqz file(s) be obtained (there is one for mail600)? 2. After hand loading the information that TNCSET sets up, MCS is started. The window/port message appears, then the TNC's CMD: prompt. However, there is a heart on the screen to the left of CMD:, the prompt is followed by the letter 'C' (should be expected, it seems, per the documentation), and a message to the effect "LINK STATE: Disconnected" (again, should be expected). At that point the system loops with the heart CMD: prompt followed by the 'C' followed by the "LINK STATE:..." and so on. 3. Control E does not operate - it is in the config.mc file. It is necessary to reboot to kill MCS. 4. TNCBAUD is missing. We set things up by hand (port and TNC). Using 6.6.1 rather than 6.7.2 produces the same results. I suspect pilot error on my part. Can anyone give a hand, please? In addition to the immediate problem of getting him going, I have some questions that may help later: 1. Is there any doc on vidpop? 2. From where does MCS obtain the type of TNC connected - the setup program asks which TNC, but I cannot find the file that holds that information. Uncle Ray's MARS call sign is AAT5LC - I do not know his ham call sign. Thank You, Danny Cornett cornett@crd.ge.com ------------------------------ Date: 15 Apr 91 15:39:11 GMT From: news-mail-gateway@ucsd.edu Subject: Packet buzzwords To: packet-radio@ucsd.edu I figured that when at the end of a conversation about computers with a colleague one of our coworkers said ***I didn't understand a single word you guys said*** that I had reached the pinnacle of jargoneese. Now that I'm into packet radio, I find that I have to learn a whole new language again. Therefore I need some help with what the following packet buzzwords mean: 1. TheNet 2. NetRom 3. Net.Exe 4. NOS 5. KISS and 6. What's the difference between a TNC-1 and a TNC-2 I am already somewhat familiar with TCP/IP (read: I know what the acromyn stands for). If I've missed any **in** buzzwords please fill me in. If you don't want to fill up bandwith here with information that has been provided a million times already feel free to send it to my packet address below. Thanks for the help. Bob Taggart/K8RYA K8RYA@WA3ZNW.MD.USA.NA rtaggart@ddn-wms.ddn.mil ****************************************************************************** All standard disclaimers apply. ****************************************************************************** All flames returned to originator without action. ****************************************************************************** Remember Karnac sayeth: He who shall, so shall he who. ****************************************************************************** ~ ------------------------------ Date: 15 Apr 91 10:36:00 GMT From: news-mail-gateway@ucsd.edu Subject: Repeater maps in Europe To: packet-radio@ucsd.edu Has any of our European reader of this list got a list of European repeaters which are kept on most of the day ? I am particularly interested in VHF repeaters, along a route from Italy to UK. Please answer directly to me since I am not on this list anymore. Thanks - Olivier M.J. Crepin-Leblond, Networks Research, Imperial College of Science and Technology, Elec. Eng. Dept. , London, UK. <umeeb37@vaxa.cc.ic.ac.uk> - should work from anywhere - ------------------------------ Date: 15 Apr 91 02:04:15 GMT From: pacbell.com!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!solo.csci.unt.edu!vaxb.acs.unt.edu!greg@ucsd.edu Subject: Texas Packet Radio Society To: packet-radio@ucsd.edu Texas Packet Radio Society TPRS information and TexNet version 1.6 code is currently available on PONDER.CSCI.UNT.EDU by anonymous FTP. All files are located in the pub directory under TPRS. A NEW directory is available to allow Texas hams to drop off TCP/IP address listing and other information that you might want me to store away. Currently the South Texas TCP/IP address are available. If you do drop something in the NEW directory, please send me EMAIL so that I will look over at the information 73 - Greg Jones, WD5IVD, TPRS ------------------------------ End of Packet-Radio Digest ****************************** Date: Wed, 17 Apr 91 04:30:04 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #93 To: packet-radio Packet-Radio Digest Wed, 17 Apr 91 Volume 91 : Issue 93 Today's Topics: 9600 baud with G3RUH Packet buzzwords (2 msgs) packet transmitter hunts Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 16 Apr 91 23:58:00 GMT From: news-mail-gateway@ucsd.edu Subject: 9600 baud with G3RUH To: packet-radio@ucsd.edu Hi ! I have a TNC2 and i need to trasmit at 9600 baud (or faster) but i don't know where to find the G3RUH's card (or faster card). Thanks for any help ! -------------------------------------------------------------------------- Andrea Pizzolato, PALERMO (Sicily-ITALY) TCPIP : IW9BUX.ampr.org [44.134.112.46] AX25 : IW9BUX@IT9ZWS BITNET : GAGLIO@IPACRES.BITNET -------------------------------------------------------------------------- ------------------------------ Date: 16 Apr 91 17:05:06 GMT From: mnemosyne.cs.du.edu!isis.cs.du.edu!whester@uunet.uu.net Subject: Packet buzzwords To: packet-radio@ucsd.edu In article <XX.180.2118.671729948@XX.QMAIL> rtaggart@ddn-wms2.ddn-wms.ddn.MIL ( Robert Taggart) writes: *******stuff deleted for brievity******* >guys said*** that I had reached the pinnacle of jargoneese. Now that I'm into >packet radio, I find that I have to learn a whole new language again. >Therefore I need some help with what the following packet buzzwords mean: > >1. TheNet >2. NetRom >3. Net.Exe >4. NOS >5. KISS > *********stuff deleted******** >I am already somewhat familiar with TCP/IP (read: I know what the acromyn >stands for). If I've missed any **in** buzzwords please fill me in. *********more deletions********** Well, I too am a packet beginner and haven't found any of this in the books that are on the market...they just talk about AX.25. A while ago, I posted a request concerning what advantages changing from AX.25 to TCP/IP would have for me. Got no responses... Does anyone know of a good packet handbook that fills in the gap between beginner and packet technoid level? ...and please post your responses to the original questions above to this group...I'm sure there are others who have wandered into packet radio and want to learn more...but are not up to the 56KBaud stuff yet! :-). Thanks. -- Bill Hester, Ham Radio N0LAJ, Denver CO., USA | N0LAJ @ W0LJF.CO.USA.NA Please route replies to: whester@nyx.cs.du.edu or uunet!nyx!whester Public Access Unix @ University of Denver, Denver Colorado USA (no official affiliation with the above university) ------------------------------ Date: 16 Apr 91 20:17:44 GMT From: news-mail-gateway@ucsd.edu Subject: Packet buzzwords To: packet-radio@ucsd.edu >From rtaggart Tue Apr 16 12:16:13 1991 Date: Tue, 16 Apr 91 12:16:09 EDT From: rtaggart ( Robert Taggart) To: perley@easygoer.crd.ge.com (Donald P Perley) Cc: rtaggart Message-id: <XX.180.28734.671818557@XX.QMAIL> Subject: Reply to: Re: Packet buzzwords Type: External In-reply-to: Re: Packet buzzwords Priority: Regular Security: None Classification: 1stclass Don, Much appreciate the info. If I have it all right it means that: 1. TheNet or NetRom is needed to be a NetRom node. 2. Net.Exe or NOS is needed to run TCPIP with KISS in the TNC. Looks like my Kantronics KPC-2 is a TNC-2 type then as it has KISS and a mailbox. Now if I can just get it to transmit in converse mode after I connect I'll be doing good. Works great in command mode for a connect or disconnect command but is dead in conv mode after connecting. Looks to me then from what you say that there are three protocols in use: AX.25, NetRom and TCPIP. What are the advantages for you of running TCPIP under NOS as opposed to running AX.25 ? Thanks again for helping a new guy with all this stuff. 73s and CULater Bob taggart/K8RYA ~ PS. Looks like our host table couldn't handle your address so replying via the net here. Rt. ~ ------------------------------ Date: 14 Apr 91 13:32:17 GMT From: deccrl!news.crl.dec.com!shlump.nac.dec.com!sousa.ltn.dec.com!sndpit.enet.dec.com!smith@decwrl.dec.com Subject: packet transmitter hunts To: packet-radio@ucsd.edu In article <2728@ke4zv.UUCP>, gary@ke4zv.UUCP (Gary Coffman) writes... >In article <1059@sousa.enet.dec.com> smith@sndpit.enet.dec.com (Willie Smith) writes: >>In article <46925@ut-emx.uucp>, wdlee@ccwf.cc.utexas.edu (david lee) writes... >>>If you've got a moment, consider the following... >>>Could the unique capabilities of packet be exploited to create >>>an enhanced transmitter hunt? >>[...] >> >>Neat ideas! How about being able to 'ping' the fox with a high-speed >>packet radio and measuring the round-trip delay to get range and bearing? >Good idea for a GAME Willie, but the real use of T-hunting is to prepare >the hunters for real situations like tracking down jammers and finding >downed aircraft. The targets normally don't cooperate in this way. So prove it can be done, make it work reliably, and you have just done something _wonderful_ for EPIRBs and PELTs. If there's a proven advantage (one aircraft can find the hiker with a broken leg in a national park in half the time of two aircraft or whatever) you will start seeing this capability show up in PELTs and EPIRBs. Sure it doesn't help with the 'old style' gear or jammers, but maybe it's worthwhile anyway... Willie Smith smith@sndpit.enet.dec.com smith%sndpit.enet.dec.com@decwrl.dec.com {Usenet!Backbone}!decwrl!sndpit.enet.dec.com!smith ------------------------------ End of Packet-Radio Digest ****************************** Date: Thu, 18 Apr 91 04:30:10 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #94 To: packet-radio Packet-Radio Digest Thu, 18 Apr 91 Volume 91 : Issue 94 Today's Topics: 9600 baud with G3RUH Japan MSYS 1.11 available via FTP? NEDA, was: Packet buzzwords Northern Calif Packet Association Meeting Packet buzzwords Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 17 Apr 91 12:21:08 GMT From: deccrl!news.crl.dec.com!shlump.nac.dec.com!sousa.ltn.dec.com!sndpit.enet.dec.com!smith@decwrl.dec.com Subject: 9600 baud with G3RUH To: packet-radio@ucsd.edu In article <8C30A85D06DF203E35@IPACRES.BITNET>, GAGLIO%IPACRES.BITNET@icnucevm.cnuce.cnr.it (Led Zeppelin) writes... > I have a TNC2 and i need to trasmit at 9600 baud (or faster) but i don't >know where to find the G3RUH's card (or faster card). PacComm sells the G3RUH card in a couple of configurations, internal for TNC-2 and clones with modem disconnect header ($110) or external in it's own box ($160). I suspect it would be really easy to buy the internal version and put it in your own box. Ask for a catalog, they've got a bunch of neat stuff! PacComm Packet Radio Systems, Inc 3652 W. Cypress Street Tampa, FL 33607-4916 (813) 874-2980 Willie Smith smith@sndpit.enet.dec.com smith%sndpit.enet.dec.com@decwrl.dec.com {Usenet!Backbone}!decwrl!sndpit.enet.dec.com!smith ------------------------------ Date: 16 Apr 91 22:50:10 GMT From: usc!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!cs.umn.edu!uc!noc.MR.NET!ns!ns!hughes@ucsd.edu Subject: Japan To: packet-radio@ucsd.edu I will be going to Japan in a few weeks, I was wondering if anyone knows the names and addresses of good Amateur radio stores in Tokyo? One more question, What can I do to be able to packet over there on my US license. Who should I contact, and can I do it before I get there (i.e. via telephone). Please respond via email. I will summarize the store list to the net. Thanks jim ------------------------------ Date: 17 Apr 91 22:32:00 GMT From: news-mail-gateway@ucsd.edu Subject: MSYS 1.11 available via FTP? To: packet-radio@ucsd.edu Does anyone know of a machine that I can use to FTP MSYS 1.11? 73, Charles AA5AV ------------------------------ Date: 17 Apr 91 17:39:59 GMT From: sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!clarkson!clarkson-test!usenet@ucsd.edu Subject: NEDA, was: Packet buzzwords To: packet-radio@ucsd.edu ------------------------------ Date: 17 Apr 91 14:48:06 GMT From: news-mail-gateway@ucsd.edu Subject: Northern Calif Packet Association Meeting To: packet-radio@ucsd.edu ------------------------------ Date: 17 Apr 91 14:28:29 GMT From: olivea!oliveb!amdahl!greg@decwrl.dec.com Subject: Packet buzzwords To: packet-radio@ucsd.edu In article <1991Apr16.170506.14041@mnemosyne.cs.du.edu> whester@isis.UUCP (William R. Hester) writes: >In article <XX.180.2118.671729948@XX.QMAIL> rtaggart@ddn-wms2.ddn-wms.ddn.MIL ( Robert Taggart) writes: >*******stuff deleted for brievity******* > >>guys said*** that I had reached the pinnacle of jargoneese. Now that I'm into >>packet radio, I find that I have to learn a whole new language again. >>Therefore I need some help with what the following packet buzzwords mean: >> >>1. TheNet >>2. NetRom >>3. Net.Exe >>4. NOS >>5. KISS >> >*********stuff deleted******** > >>I am already somewhat familiar with TCP/IP (read: I know what the acromyn >>stands for). If I've missed any **in** buzzwords please fill me in. >*********more deletions********** > >Well, I too am a packet beginner and haven't found any of this in the books >that are on the market...they just talk about AX.25. > >A while ago, I posted a request concerning what advantages changing from >AX.25 to TCP/IP would have for me. > >Got no responses... > >Does anyone know of a good packet handbook that fills in the gap between >beginner and packet technoid level? > >...and please post your responses to the original questions above to this >group...I'm sure there are others who have wandered into packet radio and >want to learn more...but are not up to the 56KBaud stuff yet! :-). I have for a few years thought that with packet, amateur radio has truly come of age. Up to now, for almost every mode and method, their used to be an abundance and redundance of documentation at all levels. For the "new digital modes," I have noticed that it's a little, but not much, better than what one has come to expect in UNIX-biz; somebody grunts "read the man() page." Greg ------------------------------ Date: (null) From: (null) The annual general meeting of the Northern California Packet Association will be held on Saturday, April 27th at 10:00am in the board room of the Contra Costa County Water District, 1331 Concord Avenue, Concord. Talk-in will be on 147.735(-). The spring issue of the NCPA downlink will be available at the meeting for those who wish to join or renew their membership at that time. The agenda for the meeting will be: o Summary of board actions and plans o NARC 220MHz reallocation plan o Election of directors 73, eric NCPA President ------------------------------ Date: (null) From: (null) There are clubs that may be of benefit to people who want to learn more about packet radio. Here's some info. North East Digital Association (I'm editor for this one) Box 563 Manchester NH 03105 - NEDA runs a LARGE TheNET network of 35 multiport nodes over a 400mile range including Boston, Concord, Manchester, Springfield, Pittsfield Albany, Utica, Rochester, Binghamton, Buffalo. No phone lines, no tricks, just 150 radios/TNCs with dedicated point to point UHF, 220, 6m, 900, 1200mhz links and 2m and 220 user access ports. The club publishes about 180 pages /year of newsletters, new user help stuff, tech stuff etc. The Quarterly is about 35 pages/quarter. Membership is $15/year for US. Send a SASE to the POBox. Northern California Packet Association This is an education and coordination club that puts out a quarterly journal called the Downlink. The one I have here is 20 pages long and is chock full of packet stuff. THey are NCPA 6680 Alhambra Ave, Suite 111 Martinez CA 94553 Then there's a few magazines: New England TCPer - This journal comes out 6 times a month and $12/year NE TCPer 252 Stow Rd. Harvard, MA 01451 Digital Digest - TCP, AMTOR, RTTY, CW everything 6 times a year and is 30 to 40 pages long including commercial advertising. $16/year Digital Digest 4063 N. Goldenrod Rd Winter Park Florida 32792 Joining a club, even a non-local one is a good way to get into correspondance that will answer some of the harder questions. One of the items that I helped create recently for NEDA was a 13 page glossary of packet terms that the club will probably make available. It was created for a technical developement meeting in Scranton Pa a couple of weekends ago. Tadd, KA2DEW NEDA editor Box 330 Colton NY 13625 - 315-262-1123 (until 11PM EST) [ KA2DEW @ KA2JXI.#NNY.NY.USA.NA - Tadd Torborg ] [ torbortc@clutx.clarkson.edu - 26 Maple St - PO Box 330 ] [ NEDA (North East Digital Association) Editor - Colton, NY 13625 ] [ Clarkson University - 315-262-1123 ] ------------------------------ End of Packet-Radio Digest ****************************** Date: Fri, 19 Apr 91 04:30:08 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #95 To: packet-radio Packet-Radio Digest Fri, 19 Apr 91 Volume 91 : Issue 95 Today's Topics: [ANS] Buggy thenet plus 2.06? (Was TheNET 1.16) (2 msgs) AO-21 QUESTION Current Listing of Packet PBBS's FAQ list for packet? (was Re: Packet buzzwords) NEDA, was: Packet buzzwords Packet buzzwords (3 msgs) TheNET 1.16 & 2.06 Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 16 Apr 91 11:12:01 GMT From: gatech!bloom-beacon!eru!kth.se!sunic!mcsun!ukc!tcdcs!swift.cs.tcd.ie!phealy@ucsd.edu Subject: [ANS] Buggy thenet plus 2.06? (Was TheNET 1.16) To: packet-radio@ucsd.edu In article <9104150418.AA13584@tecnet1.jcte.jcs.mil>, mgb@tecnet1.jcte.jcs.mil writes: > Version 2.06: > This version works perfectly and I have had no problems with it. I do The only thing I have to add in regard to the information posted here already is that the thenet plus 2.06 eprom setup program is excellent. The original attraction to us of 2.06 was the (simple) mheard command. I now think that a switch to 2.06 is warranted simply by the setup program. Thanks to everyone to took the time to reply to my question (oh3nwq, wb4wor, wa3jpy). Does anyone know if there is likely to be anything after 2.08? (or 1.16?) 73, Paul, EI9GL ------------------------------ Date: 16 Apr 91 13:11:11 GMT From: gatech!bloom-beacon!eru!kth.se!sunic!mcsun!ukc!pyrltd!root44!praxis!praxis!mikec@ucsd.edu Subject: [ANS] Buggy thenet plus 2.06? (Was TheNET 1.16) To: packet-radio@ucsd.edu >>>>> Regarding [ANS] Buggy thenet plus 2.06? (Was TheNET 1.16); mgb@tecnet1.jcte.jcs.mil adds: mgb> In article <910C170D609F60E44B@uncg.bitnet>, WB4WOR%UNCG.BITNET@ncsuvm.ncsu.EDU mgb> (CHARLES LAYNO (WB4WOR)) writes: > user system or closed backbone tunk. TheNET Plus 2.06 isn't configurable as > much as 1.16, but since it was buggy, went back to 1.0. mgb> Paul Healy, phealy@cs.tcd.ie then asks: >We were about to replace a working thenet v1.1 with thenet plus 2.06 locally >(ie most of Ireland). Could somebody with experience of v2.06 and v1.0/v1.1 >compare them for reliability in single and dual port configurations? [bits about TheNet versions deleted] mgb> Let me make a few comments on this since Charles and I are friends and we mgb> were both looking at the same problems from two places in the same state. mgb> It also did some weird things when connecting to G8BPQ nodes. The 1.16 mgb> would initiate a level 3 connect, and the G8BPQ node would respond. Then mgb> the 1.16 would show the G8BPQ as a level 2 connect, would send it the list mgb> of available node commands (like a user that had made an incorrect command) mgb> and would THEN stop and would leave the user making the connect attempt mgb> right at the 1.16 node and NOT connect him through to the G8BPQ node. This may well be to do with the L4 timeout handshake that BPQ nodes send when making/accepting a circuit connection. If you were to watch a BPQ node setting up a circuit you would see one character of info (an 'x') being sent to the remote node. TheNet 1.0 and 1.1 don't seems to care about the extra data tacked on after the NET/ROM conn ack/conn req frame but other TheNets might be more fussy. Get someone with a decent monitor eg WA8DED or TCP/IP NOS or NET to watch the NET/ROM transactions for you. Hope that helps, 73 Mike **** ............................................................................. | | Michael Chace | | e-mail : mikec@praxis.co.uk | PraXis Systems | | | Manvers Street | | AMPRNET: g6dhu@g6dhu.ampr.org [44.131.20.3] | Bath, Avon | | AX.25 : G6DHU @ G6DHU-2 or G6DHU @ GB7IMB | BA1 1PX UK | | Phone : (44) [0]225 444700 | | ............................................................................. ------------------------------ Date: 14 Apr 91 07:20:20 GMT From: kb2ear!overlf!n2aam@RUTGERS.EDU Subject: AO-21 QUESTION To: packet-radio@ucsd.edu Does anyone in netland know what is the story with AO-21? When will the transponders be put on line? Any information would be appreciated. Dave Marthouse N2AAM Unix: n2aam@kb2ear.ampr.ORG Fido: dave marthouse 1:107/323 Packet: n2aam @ w2emu-4.nj.usa.na ------------------------------ Date: 18 Apr 91 12:38:49 GMT From: o.gp.cs.cmu.edu!andrew.cmu.edu!paul+@pt.cs.cmu.edu Subject: Current Listing of Packet PBBS's To: packet-radio@ucsd.edu Does anyone know if there is an ftp site that would have current listings for packet PBBS's by state. I'd also like to get some current maps for the PA/WV/OH tri state area. \paul WA3TLD ------------------------------ Date: 18 Apr 91 02:38:34 GMT From: casbah.acns.nwu.edu!zaphod.mps.ohio-state.edu!caen!kuhub.cc.ukans.edu!zeus.unomaha.edu!acmnews@ucsd.edu Subject: FAQ list for packet? (was Re: Packet buzzwords) To: packet-radio@ucsd.edu In article <1991Apr16.170506.14041@mnemosyne.cs.du.edu>, whester@isis.cs.du.edu (William R. Hester) writes: > > Does anyone know of a good packet handbook that fills in the gap between > beginner and packet technoid level? > > ....and please post your responses to the original questions above to this > group...I'm sure there are others who have wandered into packet radio and > want to learn more...but are not up to the 56KBaud stuff yet! :-). > > Thanks. > This kinda suggests the need for a Frequently Asked Questions list for rec.radio.amateur.packet similar to the wonderful lists that Diana Syriac (dls@genrad.com) puts together for rec.radio.amateur.misc. Any volunteers? I would, but I'm not what you would call a packet "expert" and I am busy maintaining the Elmer's list. 73, Paul Schleck, KD3FU ------------------------------ Date: 18 Apr 91 12:48:20 GMT From: pa.dec.com!shlump.nac.dec.com!ryn.mro4.dec.com!ultnix.enet.dec.com!taber@decwrl.dec.com Subject: NEDA, was: Packet buzzwords To: packet-radio@ucsd.edu In article <1991Apr17.173959.14115@clutx.clarkson.edu>, torbortc@clutx.clarkson.edu (Tadd,KA2DEW, ,3152621123) writes: |> |>New England TCPer - This journal comes out 6 times a month and |>$12/year |>NE TCPer 252 Stow Rd. Harvard, MA 01451 |> Just for the record, you mean 6 times a year, right? -- >>>==>PStJTT Patrick St. Joseph Teahan Taber, KC1TD "Nerd" is so demeaning, I prefer "fashion-impared." ------------------------------ Date: 18 Apr 91 00:15:00 GMT From: agate!bionet!uwm.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!wa4mei!ke4zv!gary@ucbvax.berkeley.edu Subject: Packet buzzwords To: packet-radio@ucsd.edu In article <XX.180.2118.671729948@XX.QMAIL> rtaggart@ddn-wms2.ddn-wms.ddn.MIL ( Robert Taggart) writes: > [What are these buzzwords?] >1. TheNet A clone of Netrom written by a group of German hams. Source available. Distribution free. >2. NetRom Proprietary code for the TNC2 that establishes a low level network capablity for level 2 users. Sold by Software 2000. It allows a user to "uplink" to it via AX25 connected mode and issue commands to establish a connection to another Netrom node then do a "downlink" to another level 2 user. The internal network protocol uses UI frame datagrams. Features semi-automatic routing. >3. Net.Exe A version of TCP/IP written by Phil Karn KA9Q for the IBM PC. It has been ported to the Mac and Amiga. Allows peer level connections with other stations using the IP protocol suite. Available commands include telnet, ftp (get and put files), and smtp, a mail delivery agent. The package will also do level 2 AX25 connections to users running ordinary TNCs. Requires a KISS TNC or a DRSI board or one of several other hardware cards to interface with a radio. Includes ethernet support. Supports multiple ports. Each peer station is capable of IP routing. >4. NOS Network Operating System, a version of TCP/IP written by Phil Karn that uses "lightweight multitasking". This is the current version of Net on the IBM PC. Many enhanced functions over the older Net.Exe. >5. KISS Keep It Simple Stupid, operational software for the TNC2, and others, that removes the AX25L2 protocol from the TNC and passes all packets to your computer for further processing. >6. What's the difference between a TNC-1 and a TNC-2 The TNC-1 is the original TAPR designed TNC. The TNC-2 is TAPR's second generation TNC. They use different processor families with the TNC-1 using the Motorola family and the TNC-2 using the Zilog family. The TNC-2 design is the most widely licensed and used design today. Gary KE4ZV ------------------------------ Date: 18 Apr 91 15:29:22 GMT From: agate!bionet!uwm.edu!cs.utexas.edu!ut-emx!mojo.ots.utexas.edu!jah@ucbvax.berkeley.edu Subject: Packet buzzwords To: packet-radio@ucsd.edu In article <2750@ke4zv.UUCP> gary@ke4zv.UUCP (Gary Coffman) writes: >In article <XX.180.2118.671729948@XX.QMAIL> rtaggart@ddn-wms2.ddn-wms.ddn.MIL ( Robert Taggart) writes: >> >[What are these buzzwords?] > >>1. TheNet > >A clone of Netrom written by a group of German hams. Source available. >Distribution free. Wrong. Folks should be aware that THEnet(sm) is a registered service mark of the Board of Regents of the University of Texas, and may not be used without permission. It also happens that TEXnet (tm) is a trade mark of the Texas Business Network, Inc. I don't know who they are; I'm only affiliated with UT. -- Jeff Hayward The University of Texas System +1 512 471 2444 Office of Telecommunication Services jeff@nic.the.net ------------------------------ Date: 18 Apr 91 18:23:40 GMT From: deccrl!news.crl.dec.com!shlump.nac.dec.com!delni.enet.dec.com!goldstein@decwrl.dec.com Subject: Packet buzzwords To: packet-radio@ucsd.edu In article <47403@ut-emx.uucp>, jah@mojo.ots.utexas.edu (Jeff Hayward) writes... >>>1. TheNet >>A clone of Netrom written by a group of German hams. Source available. >>Distribution free. >Wrong. > >Folks should be aware that THEnet(sm) is a registered service mark of >the Board of Regents of the University of Texas, and may not be used >without permission. I think that's a non-sequitur. THEnet (presumably) is Texas Higher Education network, perhaps? note the three uppercase letters. TheNet is a German freeware implementation of the same protocols as NETROM. Note the lower case "he". See? Different name. Not that I'm a lawyer. And I don't see how the two can be confused. Heck, Digital goes to great lengths to protect its ALL-IN-1 trademark, but you can buy All-in-One Steak Sauce. (I prefer Texas Best, myself.) --- Fred R. Goldstein k1io Digital Equipment Corp., Littleton MA goldstein@delni.enet.dec.com voice: +1 508 952 3274 Do you think anyone else on the planet would share my opinions, let alone a multi-billion dollar corporation? ------------------------------ Date: 18 Apr 91 09:45:25 GMT From: news-mail-gateway@ucsd.edu Subject: TheNET 1.16 & 2.06 To: packet-radio@ucsd.edu Hello friends ! Maybe I can help to clarify a little TheNET confusion. NORD><LINK made theNets (VERY strongly influenced by WA8DED work) available in source and binary forms a long time ago. A month or two ago I received a floppy with all compilers and tools needed to make own version. I got sources for TheNET 1.1 normal,interlink, user-access; as well as COVERSE and TF21d. So, this are official versions from NORD><LINK. There are two versions widely circulated, both based on TheNET 1.1. TheNET 1.16 is an intermin version toward 1.20 (I hope !) made by HAMs close to NORD><LINK (but not DF2AU himself); while 2.06 is made in USA. I saw several other versions which are definitely pached EPROM images... Just count number of characters ! Most versions just play with user commands processor - but nobody tried to make faster interrupt routines and better level 3 routing. 2.06 has very nice documentation, so it is worth FTPing from TOMCAT; but I do not beleive it is worth climbing to the mountains to replace EPROMs. Single usable function, not found at 1.1, is HEARD list of last few calls. This is not usable on our busy 2m channells - because node hears much more stations as can be connected. Routes list use IDENT instead of CALLS, what just add confusion. Another nice feature is NOT FOUND message answer to "N UNKNOWN" command. At least in our region 2.06 is used mainly by SysOps who collect versions (must get TheNET 3.13 for them !). 1.16 is really next step. They throw away useless code for user terminal, so RS-232 port is NET/ROM ASYNC protocol only. They got space in EPROM for few nice changes. Reasons, why we put 1.16 to work in YU3 network: - T 60 command puts TX to transmit 60 seconds of test signal. This was badly needed for antenna tuning on 23cm. - Remote adjustable TXDELAY - "N UNKNOWN" command is replayed by "Not found" - Several flags to set mode of level 3 beacons - RESTART commands clears links, but keeps routes and nodes Another features, liked by users - CTEXT message (QRM, as all CTEXTes - but HAMLETs like them !) - QUIT command, which RECONNECTS back - NODE ? gives nice sorted list of known nodes. - LED 0,1,2,3 instead of HI/LOW Now... BUGS: We run several TheNET nodes on 38400 bd radio speed/ 9600 bd RS-232. They are connected to other nodes via diode matrix or FKROM (EPROM with logic for 4 TNCs, using TTL level ASYNC TNC lines. I hate diodes ...). All tested versions have a bug in LEV3 or LEV4: With nodes going up/down memory become corrupted and node blocks. But, after I enforced stable network (NO nodes with 0 quality), keeping maximum number of nodes at 20, they are quite stable. Users know: To go to OE, call 4N3P. To go to Italy, call 4N3K. To south, call 4N2Z. 1.16 bugs User interface on RS-232 is out. SIO pin 22 is no more needed. But - take care with single node - it attemps to send routing beacons to RS-232, and they eat memory, waiting for port to be ready. So, FLAGS 5 1 is MUST for single nodes (AND remote reset). It works fine in company. 1.16 sends CTEXT for EVERY lev.2 link - and if you block CTEXT, blank INFO frame with PID F0 is send on any connection, G8BPQ hates this, and they like to exchange several QRM lev.2 frames with PID F0. There are also some minor bugs in output messages for SYSOPs, like entering INFO and reading it in same QSO. 1.1y is yu3fk version - I try to get better results on 38400 bd by lowering link number (25 is too much for interlink nodes) etc. Only few mods to 1.1 - I do not want to make big changes on old version ! Best 73 and happy networking ! Iztok, YU3FK@YT3A.YUG YU3FK@ijs.ac.mail.yu ------------------------------ Date: 18 Apr 91 17:42:25 GMT From: deccrl!news.crl.dec.com!shlump.nac.dec.com!ryn.mro4.dec.com!ultnix.enet.dec.com!taber@decwrl.dec.com To: packet-radio@ucsd.edu References <XX.180.2118.671729948@XX.QMAIL>, <2750@ke4zv.UUCP>, <47403@ut-emx.uucp>ws.crl.d Reply-To : taber@ultnix.enet.dec.com (Patrick St. Joseph Teahan Taber) Subject : Re: Packet buzzwords In article <47403@ut-emx.uucp>, jah@mojo.ots.utexas.edu (Jeff Hayward) writes: |> |>In article <2750@ke4zv.UUCP> gary@ke4zv.UUCP (Gary Coffman) writes: |>>In article <XX.180.2118.671729948@XX.QMAIL> |>rtaggart@ddn-wms2.ddn-wms.ddn.MIL ( Robert Taggart) writes: |>>> |>>[What are these buzzwords?] |>> |>>>1. TheNet |>> |>>A clone of Netrom written by a group of German hams. Source |>available. |>>Distribution free. |> |>Wrong. |> |>Folks should be aware that THEnet(sm) is a registered service mark of |>the Board of Regents of the University of Texas, and may not be used |>without permission. Good luck. I assume that you can prove "THEnet" predates "TheNet" and have figured out whom to charge with infringement. I think your best course is to give permission (if you can find someone to accept it.) -- >>>==>PStJTT Patrick St. Joseph Teahan Taber, KC1TD "Nerd" is so demeaning, I prefer "fashion-impared." ------------------------------ End of Packet-Radio Digest ****************************** Date: Sat, 20 Apr 91 04:30:05 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #96 To: packet-radio Packet-Radio Digest Sat, 20 Apr 91 Volume 91 : Issue 96 Today's Topics: How do I subscribe to TCP-GROUP? Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 19 Apr 91 13:47:14 GMT From: agate!bionet!uwm.edu!spool.mu.edu!munnari.oz.au!manuel!csc.canberra.edu.au!echo!skcm@ucbvax.berkeley.edu Subject: How do I subscribe to TCP-GROUP? To: packet-radio@ucsd.edu The subject line says it all really. How do I subscribe to tcp-group. Thanks Carl. ------------------------------ Date: 19 Apr 91 13:43:17 GMT From: ucselx!usc!cs.utexas.edu!ut-emx!margo.ots.utexas.edu!jah@ucsd.edu To: packet-radio@ucsd.edu References <47403@ut-emx.uucp>, <4441@ryn.mro4.dec.com>, <22166@shlump.nac.dec.com> Subject : Re: Packet buzzwords Fred R. Goldstein writes: >I think that's a non-sequitur. >THEnet (presumably) is Texas Higher Education network, perhaps? note >the three uppercase letters. >TheNet is a German freeware implementation of the same protocols as >NETROM. Note the lower case "he". >See? Different name. Not that I'm a lawyer. And I don't see how >the two can be confused. Heck, Digital goes to great lengths to >protect its ALL-IN-1 trademark, but you can buy All-in-One Steak Sauce. >(I prefer Texas Best, myself.) First, I should say that I'm not a lawyer myself, nor do I speak for the Regents. My prior posting (and this one) should be considered, I hope, just a friendly observation to some fellow networkers. That aside, it should be said that trade and service marks are not like patents. Prior use is not much of an issue. Punctuation and capitalization are not much of an issue. For-profit, not-for-profit, private individual or corporate use is not much of an issue. If, in the mind of the consumer, they can be confused there is probably a conflicting use. You can bet that if H.J. Heinz started marketing A-1 office automation, Digital would be on them like... well, you know. As to whether there's a real conflict in this case, let me give a just barely hypothetical example. The Texas Education Agency has been charged with the task of building an "Electronic Information Transfer System" (read network) to bring together all the public schools in Texas. In the course of deciding just what structure and technology the network should use, two of the proposals made stood out. Proposal A made use of the existing higher education networking facilities, in conjunction with university staff expertise to make dial-up (V.32) connections to internet-based information resources, like usenet news. Proposal B made use of existing packet radio technology already used in Texas to avoid telecommunication costs and provide a completely flexible infrastructure. Proposal A wins the day. (Begin hypothetical part) Some time later, when testifying before the Texas senate education committee, a senator whose ox has been gored grills the head of the agency. "Why didn't you use this network, this thenet stuff like we talked about? I thought that held great promise to bring networking to the schools at very little cost to the taxpayer. Well, Mr. director?" So, Fred, which thenet does the senator refer to? Would you say there's a service mark conflict here? In any case, this is probably not of much interest to the packet radio community at large. I'm sorry to have taken up so much bandwidth with these marginally topical postings. -Jeff -- Jeff Hayward The University of Texas System +1 512 471 2444 Office of Telecommunication Services jeff@nic.the.net ------------------------------ Date: 19 Apr 91 16:12:56 GMT From: stanford.edu!neon.Stanford.EDU!kaufman@icarus.riacs.edu To: packet-radio@ucsd.edu References <XX.180.2118.671729948@XX.QMAIL>, <2750@ke4zv.UUCP>, <47403@ut-emx.uucp> Subject : Re: Packet buzzwords In article <47403@ut-emx.uucp> jah@mojo.ots.utexas.edu (Jeff Hayward) writes: >Folks should be aware that THEnet(sm) is a registered service mark of >the Board of Regents of the University of Texas, and may not be used >without permission. Registered in the US, only, though. Remember, this is a German program. Good luck proving/enforcing infringement on a freely distributed program with no identifiable US importer or reseller. Besides, "the net" is a generic description of a network and is only registerable in a very specific form, such as "THEnet" with caps, etc. Even then, it might be considered too generic if it comes to a court test. Want to try? Marc Kaufman (kaufman@Neon.stanford.edu) ------------------------------ End of Packet-Radio Digest ****************************** Date: Sun, 21 Apr 91 04:30:05 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #97 To: packet-radio Packet-Radio Digest Sun, 21 Apr 91 Volume 91 : Issue 97 Today's Topics: AO-21 Question Packet buzzwords Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 21 Apr 91 06:11:01 GMT From: kb2ear!n2aam@RUTGERS.EDU Subject: AO-21 Question To: packet-radio@ucsd.edu Does anyone on the net know when the AO-21 transponders will be placed on line? All I've heard has been the cw beacon. Dave Marthouse n2aam@kb2ear.ampr.org Fido: dave marthouse 1:107/323 Packet: n2aam @ w2emu-4,nj.usa.na ------------------------------ Date: 20 Apr 91 00:41:04 GMT From: agate!apple!portal!cup.portal.com!Jeepster@ucbvax.berkeley.edu Subject: Packet buzzwords To: packet-radio@ucsd.edu Bill Hester asks for information which is better to run, tcp/ip or ax.25. This won't help the net here much, but connect to K0YUM on 145.01 (I have to go thru ARA4:W0LJF-4 to get to him) and ask Fred. He seems to be one of the more knowledgable people in the area. Personally, I find NOS pretty nice. It lets you have regular AX.25 connections as well as telnet, ftp, smtp and net/rom connections all going on at the same time. It also allows you to have a mail box that messages can be forwarded to. 73, John kf0ou@kf0ou.ampr.org / jeepster@cup.portal.com /kf0ou@w0ljf ------------------------------ End of Packet-Radio Digest ****************************** Date: Mon, 22 Apr 91 04:30:05 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #98 To: packet-radio Packet-Radio Digest Mon, 22 Apr 91 Volume 91 : Issue 98 Today's Topics: Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 21 Apr 91 14:26:37 GMT From: swrinde!mips!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!wa4mei!ke4zv!gary@ucsd.edu To: packet-radio@ucsd.edu References <XX.180.2118.671729948@XX.QMAIL>, <1991Apr16.170506.14041@mnemosyne.cs.du.edu>, <f0UW010l5bUE00@amdahl.uts.amdahl.com> Reply-To : gary@ke4zv.UUCP (Gary Coffman) Subject : Re: Packet buzzwords In article <f0UW010l5bUE00@amdahl.uts.amdahl.com> greg@amdahl.uts.amdahl.com (Greg Bullough) writes: >In article <1991Apr16.170506.14041@mnemosyne.cs.du.edu> whester@isis.UUCP (William R. Hester) writes: >> >> >>Does anyone know of a good packet handbook that fills in the gap between >>beginner and packet technoid level? >> >>...and please post your responses to the original questions above to this >>group...I'm sure there are others who have wandered into packet radio and >>want to learn more...but are not up to the 56KBaud stuff yet! :-). > >I have for a few years thought that with packet, amateur radio has >truly come of age. Up to now, for almost every mode and method, their >used to be an abundance and redundance of documentation at all levels. > >For the "new digital modes," I have noticed that it's a little, but >not much, better than what one has come to expect in UNIX-biz; >somebody grunts "read the man() page." > >Greg Well I think the keyword here is "new". I imagine that when CW was new there were few authoritative manuals for generating the newfangled continous waves either. And certainly the "spark forever" boys wouldn't want to talk about it. Packet really is new to the amateur world. Many of the operating techniques and hardware standards of two years ago are now obsolete. Things are changing too fast for an authoritative book to be meaningful. It would be largely obsolete before it saw print. The best sources of information are local groups and forums like this one. There is as yet no national or international standard way of doing everything with packet. Each local area is somewhat unique in the way it sets up LANS, MANS, WANS, how it handles store and forward traffic, what methods it uses for digital voice, what bands are used for digital video, etc. With Netrom, Rose, Texnet, IP switched networks, and plain old AX25 link level digipeating going on, often at the same time in the same area, packet is still a fun *experimental* zoo. By the time authoritive manuals and standards emerge, it will be time to move on to something more interesting. If you want to know how to setup a functioning distributed switched 56kb MAN, ask me. If you want to know about low speed simplex ROSE links, ask someone else, I don't have a clue. In addition, what I could tell you about 56kb MANs would probably differ dramatically from the answers you would get from the Ottawa crowd who are going in a somewhat different direction. The BBS crowd's view of packet is totally different from those of us working on distributed computing. The HF crowd is going in yet another, more traditional, DXing and traffic handling direction. Packet Cluster folks are in yet another world of DX spotting nets that happen to use packet radio. Others, the spark forever crowd, are stuck in the obsolete 1200 baud digipeater world of keyboard chats. These last are the only ones with a manual. Rather than grunting "read the manual" most of us are at the "read the source code, there is no manual" stage. Gary KE4ZV ------------------------------ End of Packet-Radio Digest ****************************** Date: Tue, 23 Apr 91 04:30:09 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #99 To: packet-radio Packet-Radio Digest Tue, 23 Apr 91 Volume 91 : Issue 99 Today's Topics: How to make electronic antenna switches at 70cm? HT with Packet Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 22 Apr 91 08:01:18 GMT From: swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!phigate!philica!geertj@ucsd.edu Subject: How to make electronic antenna switches at 70cm? To: packet-radio@ucsd.edu I'm building a transverter for 10m->70cm, to be used for the DSY-modems. Transmit and receive seem OK now - haven't checked with an analyser yet - but I have some problems getting the TX/RX antenna switch right. Because it is going to be used for packet, I'm reluctant to use a coax relay. So, I am looking into diode switches. The amateur literature I have hardly mentions this area: transmitters are described, receivers are described, but the integration of these boxes usually isn't covered. So, how to I keep my 25 Watts of RF out of the preamplifier stage? I have looked into commercial designs, but most of them uses striplines on PCB, which are hard to 'borrow'. Has anyone else struggled with this problem? Somebody made a 70cm switch for 25W with kitchentable technology? Tell me how you did it! Thanks in advance! 73, Geert Jan PE1HZG --8<--nip-nip--------------------------------------------------------------- "We trained hard - but it seemed that every time we were beginning to form up into teams, we would be reorganized. It was to learn later in life that we tend to meet any new situation by reorganizing, and a wonderful method it can be for creating the illusion of progress while producing confusion, inefficiency, and demoralisation." - Petronius, 100 BC Geert Jan de Groot, Philips ICA, Weisshausstrasse 1, 5100 Aachen, Germany Email: geertj@ica.philips.nl or ..!hp4nl!philica!geertj Phone: +49 241 6003 714 FAX: +49 241 6003 709 ------------------------------ Date: 22 Apr 91 15:29:25 GMT From: swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!ducvax.auburn.edu!eng.auburn.edu!bh@ucsd.edu Subject: HT with Packet To: packet-radio@ucsd.edu I have a Yaesu FT470 HT. My question is this Can I use that HT for packet work? Brian Hartsfield bh@eng.auburn.edu ------------------------------ Date: 22 Apr 91 13:47:19 GMT From: usc!sdd.hp.com!caen!sol.ctr.columbia.edu!emory!wa4mei!ke4zv!gary@ucsd.edu To: packet-radio@ucsd.edu References <XX.180.2118.671729948@XX.QMAIL>, <2750@ke4zv.UUCP>, <47403@ut-emx.uucp> Reply-To : gary@ke4zv.UUCP (Gary Coffman) Subject : Re: Packet buzzwords In article <47403@ut-emx.uucp> jah@mojo.ots.utexas.edu (Jeff Hayward) writes: > >In article <2750@ke4zv.UUCP> gary@ke4zv.UUCP (Gary Coffman) writes: >>In article <XX.180.2118.671729948@XX.QMAIL> rtaggart@ddn-wms2.ddn-wms.ddn.MIL ( Robert Taggart) writes: >>> >>[What are these buzzwords?] >> >>>1. TheNet >> >>A clone of Netrom written by a group of German hams. Source available. >>Distribution free. > >Wrong. No the information is correct. If you have a problem with trademark infringement, talk to them. Also the Texnet folks. They've been using those names for several years. They may have prior art on you. Or they may not, I'm not an attorney. Regardless, those are the names that they are using. >Folks should be aware that THEnet(sm) is a registered service mark of >the Board of Regents of the University of Texas, and may not be used >without permission. > >It also happens that TEXnet (tm) is a trade mark of the Texas Business >Network, Inc. I don't know who they are; I'm only affiliated with UT. > >-- >Jeff Hayward >The University of Texas System +1 512 471 2444 >Office of Telecommunication Services jeff@nic.the.net Gary KE4ZV ------------------------------ End of Packet-Radio Digest ****************************** Date: Wed, 24 Apr 91 04:30:04 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #100 To: packet-radio Packet-Radio Digest Wed, 24 Apr 91 Volume 91 : Issue 100 Today's Topics: *** RADAR DETECTOR **** Dayton PI How do I set a KISS mode TNC to another HDLC baudrate? How do I subscribe to TCP-GROUP? Internet access via packet TCP IP addresses Is W0RLI BBS S/W v12.00 available via FTP? New Toys at Dayton Zilog combo SCSI/SCC Z85C80 SCSCI Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 23 Apr 91 16:34:46 GMT From: usc!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!news.miami.edu!umiami!mmilicevic@ucsd.edu Subject: *** RADAR DETECTOR **** To: packet-radio@ucsd.edu Hi There, Does anyone know of battery powered radar detector for cars? I've read about it in the DELTA's SKY magazine when I flew last month but did not take it with me. If you know anything about this please let me know. Sincerely, MLADEN internet: MMilicevic@UMiami.IR.Miami.EDU bitnet: MMilicevic@Umiami ------------------------------ Date: 23 Apr 91 12:45:17 GMT From: news-mail-gateway@ucsd.edu Subject: Dayton PI To: packet-radio@ucsd.edu We have studiously avoided using the mailing lists/Usenet to advertise our wares, but I guess it's ok to let you know that the Ottawa gang will be at Dayton, and we should have some PI boards to sell. Looks like we will not be at a table, so you'll have to catch us on the hoof, as it were. Good possibilities would be at the packet forum on Friday, lurking in the vicinity of the TAPR, AMSAT, or Grace booths, or at the infamous Saturday night gathering at McNasty's. Watch for our, um, distinctive blue t-shirts. :-) de ve3jf ------------------------------ Date: 24 Apr 91 07:19:00 GMT From: news-mail-gateway@ucsd.edu Subject: How do I set a KISS mode TNC to another HDLC baudrate? To: packet-radio@ucsd.edu I have been using the NOS program on 144 Mhz for a while now and I would like to try to use it also on HF. The problem is that I don't know how to set the HDLC baudrate to 300 baud. I don't know how to set it to 1200 baud either but that must be the default. I think it must be a "param ax0 ..." command but which one? If there is a list of all the possible "param" commands I would like to receive a copy because I couldn't find any documentation about them. 73, Robert PA3AMO Internet: nieuwendijk@tfdl.agro.nl ------------------------------ Date: 23 Apr 91 16:42:00 GMT From: swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!cci632!cb@ucsd.edu Subject: How do I subscribe to TCP-GROUP? To: packet-radio@ucsd.edu In article <skcm.672068834@ise> skcm@echo.canberra.edu.au (Carl Makin) writes: >The subject line says it all really. > >How do I subscribe to tcp-group. > >Thanks >Carl. Sorry for wasting the bandwith But I too would like to know. thanks... -- email: cb@cci632.cci.com or cb@cci632 or !rochester!kodak!n2hkd!curtis Curtis Braun, N2HKD, Computronics, PO Box 1002 Fairport NY, 14450 ------------------------------ Date: 23 Apr 91 20:32:12 GMT From: uswnvg!cjackso@uunet.uu.net Subject: Internet access via packet TCP To: packet-radio@ucsd.edu I know this is a FAQ, but when it came up the last time around, I was unware that I might be interested in the future, so I didn't save the thread. Anyway, please reply via email and I'll summarize for the net.. I'm within a day or so of getting the KA9Q TCP software running on my Unix box (but that's another thread) and am interested in finding out if there's a packet connection to the "wire" internet that will allow things like anon ftp via packet radio. I'd also be interested in trading notes/comments/ideas/code with anyone else running the KA9Q stuff under Unix (specifically, in my case, SCO Unix SYS V). Thanks in advance! -- Clay Jackson - N7QNM US WEST NewVector Group, Inc clayj@cjsysv.wa.com | ...uunet!uswnvg!cjackso ------------------------------ Date: 24 Apr 91 08:36:14 GMT From: news-mail-gateway@ucsd.edu Subject: IP addresses To: packet-radio@ucsd.edu Does anyone know IP addresses of systems which hold free HAM software? We particulary look for radio-fax and packet software. pe1ntw & pa0rtg (Wim & Ge) ------------------------------ Date: 23 Apr 91 00:41:24 GMT From: swrinde!sdd.hp.com!spool.mu.edu!munnari.oz.au!yoyo.aarnet.edu.au!frodo.cc.flinders.edu.au!adelaide.edu.au!e2grwill@ucsd.edu Subject: Is W0RLI BBS S/W v12.00 available via FTP? To: packet-radio@ucsd.edu Hello there. Can anyone in netland please direct me to an FTP server that has the W0RLI BBS Software V11.17 or V12.00 on it? I am looking for these programs but cant find them on the internet and dont have a telephone modem so I cant dial the Phone BBS in the US that has them. Any help Appreciated. Thanks in Advance... Grant Willis (VK5ZWI) - Adelaide University, South Australia - ** 2nd/3rd Year Electrical Engineering Student ** Packet Radio: VK5ZWI@VK5TTY.#SA.AUS.OC AmPR TCP/IP: [44.136.171.11] AARNet/Internet1: e2grwill@snap.adelaide.edu.au ACSnet/Internet2: e2grwill@snap.ua.oz.au Disclaimer: What I write is mine. The Uni has nothing to do with it! ------------------------------ Date: 23 Apr 91 19:06:56 GMT From: swrinde!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!matt.ksu.ksu.edu!steve@ucsd.edu Subject: New Toys at Dayton To: packet-radio@ucsd.edu This years appears to be a banner year for packet radio at Dayton. I have seen more product announcements about new packet equipment this year than any other. (Especially, when it comes to DSP modems) Since I am going to be stuck in Kansas, could someone please post a short summary of some of the new toys, ideas, etc that happened at Dayton. Maybe someone will dial-in to usenet at Dayton and show some of the less-educated packeteers what a good messaging system is like. :-) Thanks from all the Dayton deprived. -Steve Schallehn, KB0AGD Kansas State University ------------------------------ Date: 24 Apr 91 04:18:43 GMT From: mejac!orchard.la.locus.com!fafnir.la.locus.com!dana@decwrl.dec.com Subject: Zilog combo SCSI/SCC Z85C80 SCSCI To: packet-radio@ucsd.edu Last year, I discussed the idea of a packet-assembler-disassembler on rec.ham-radio.packet (now rec.radio.amateur.packet) which uses a SCSI link to the host. This is a project I've had on the back burner since then, mostly 'cause I wasn't looking very hard for data on SCSI interface chips. Now, while perusing some Zilog literature, I discover they offer a chip which combines the Z85C30 SCC (ubiquitous in packet radio) and the Z53C80 SCSI. The Z85C30 SCC is a very well known quantity; however I know nearly nothing about the Z53C80. Are there any readers who have used either the Z85C80 SCSCI (the combo) or the Z53C80 SCSI? I'd like to know about this SCSI controller, particularly any difficulties with the part or availability. Thanks, Dana -- * Dana H. Myers KK6JQ | Views expressed here are * * (213) 337-5136 | mine and do not necessarily * * dana@locus.com | reflect those of my employer * ------------------------------ End of Packet-Radio Digest ****************************** Date: Thu, 25 Apr 91 04:30:04 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #101 To: packet-radio Packet-Radio Digest Thu, 25 Apr 91 Volume 91 : Issue 101 Today's Topics: *** RADAR DETECTOR **** KISS documentation? Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 24 Apr 91 14:22:15 GMT From: swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!trub@ucsd.edu Subject: *** RADAR DETECTOR **** To: packet-radio@ucsd.edu In article <1991Apr23.123446.9268@umiami.ir.miami.edu>, mmilicevic@umiami writes: >Does anyone know of battery powered radar detector for cars? > >I've read about it in the DELTA's SKY magazine when I flew last month but >did not take it with me. > >If you know anything about this please let me know. I suppose you could modify a battery powered radar detector to monitor packet radio on 10 or 24 ghz, but i don't think the components are beefy enough to handle transmitting as well. -- perley@trub.crd.ge.com ------------------------------ Date: 24 Apr 91 17:04:47 GMT From: sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsj!kb2glo@ucsd.edu Subject: KISS documentation? To: packet-radio@ucsd.edu I am sure this must be a FAQ but I don't remember the answer. Feel free to responsd via email... Is documentation of KISS available via anonymous ftp? Thanks and 73 DE KB2GLO, Tom. -- Tom Kenny, KB2GLO uucp: att!lzatt!tek internet: tek%lzlup@att.att.com packet: kb2glo@nn2z.nj.usa.na ampr: kb2glo@nn2z.ampr.org [44.64.0.10] ------------------------------ End of Packet-Radio Digest ****************************** Date: Fri, 26 Apr 91 04:30:06 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #102 To: packet-radio Packet-Radio Digest Fri, 26 Apr 91 Volume 91 : Issue 102 Today's Topics: *** RADAR DETECTOR **** NOAM versus NA in addresses Zilog combo SCSI/SCC Z85C80 SCSCI Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 25 Apr 91 15:34:45 GMT From: crdgw1!ge-dab!sunny9.DAB.GE.COM!tortajad@uunet.uu.net Subject: *** RADAR DETECTOR **** To: packet-radio@ucsd.edu In article <1991Apr23.123446.9268@umiami.ir.miami.edu>, mmilicevic@umiami.ir.miami.edu writes: |> Hi There, |> |> Does anyone know of battery powered radar detector for cars? |> The SOLO by Cinncinati (sp?) Microwave is an great Radar Detector that is batery powered. You can only get it through the company, so give them a call. Good Luck, Bob KA2RUU ------------------------------ Date: 25 Apr 91 22:52:28 GMT From: news-mail-gateway@ucsd.edu Subject: NOAM versus NA in addresses To: packet-radio@ucsd.edu Found the following bulletin on my BBS today: ----- Some time ago Tom Clark W3IWI gave a paper which recommended the use of 4 letters rather than 2 for the Hierarchical Continent Address Designator. Trying to cope with two sets of addresses does add to the sysop chores. So I reviewed the 1640 BBSes that have been accumulating in my Lookup file. This list is maintained by daily parsing of the headers. Here is what I found. All stations in my list used either AF AS EU OC SA or NA with the following exceptions. 6Y5EW.#KIN.JAM.CAR 6Y5RA.#KIN.JAM.CAR 5 BBSes in MD NOAM 1 BBS in NY NOAM 1 BBS in MI NOAM 1 BBS in TX NOAM 1 BBS in FL NOAM 1 BBS in NM NOAM 1 BBS in IN NOAM 1 BBS in VA NOAM 1 BBS in KY NOAM Thats it. 15 out of 1640 BBSes are using the 4 letter designator. ------------------------------ Date: 24 Apr 91 17:33:26 GMT From: adobe!fraktur!freed@decwrl.dec.com Subject: Zilog combo SCSI/SCC Z85C80 SCSCI To: packet-radio@ucsd.edu I'm almost sure (99.9%) that the Z53C80 is the same as a very well known NCR SCSI chip - 5380. It's a _standard_ SCSI device and quite well behaved. One thought - both chips come in 40 pin cases, so the combination might be hard to use: I mean PGA is not very nice for home projects. -- |--------------------------------------------------------------------------- | -Alex Freed (The opinions expressed are my own. | However everyone is entitled to them.) -- |--------------------------------------------------------------------------- | -Alex Freed (The opinions expressed are my own. | However everyone is entitled to them.) ------------------------------ End of Packet-Radio Digest ****************************** Date: Sat, 27 Apr 91 04:30:06 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #103 To: packet-radio Packet-Radio Digest Sat, 27 Apr 91 Volume 91 : Issue 103 Today's Topics: All-Mode RS232 Boxes Modify an RS232 A/B switch to a cross switch for TxD and RxD signals NOAM VERSE NA NOAM versus NA in addresses (2 msgs) Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 26 Apr 91 20:08:07 GMT From: news-mail-gateway@ucsd.edu Subject: All-Mode RS232 Boxes To: packet-radio@ucsd.edu ... What is the current wisdom on All-Mode RS-232 boxes for HF and/or VHF? I would like to acquire one but I don't know the pros and cons of various manufacturers. Are they all about the same? mfj, AEA, HeathKit ? I am looking for comments about your experience with such units. thanks & regards, Bill Moyer WRM01@ALBNYDH2 (Bitnet) WMOYER@ATTMAIL.COM (Internet) ------------------------------ Date: 26 Apr 91 22:06:11 GMT From: pacbell.com!att!cbfsb!cbnewsb.cb.att.com!wa2ise@ucsd.edu Subject: Modify an RS232 A/B switch to a cross switch for TxD and RxD signals To: packet-radio@ucsd.edu A/B switch to cross switch mod file Lately, in my packet/phone modem/8bit home computer (with modem software that can store and load from disk) system, I added a VT100 terminal I got at a hamfest. This will let me view stuff using 80 characters across the screen, instead of always having to use the 40 characters the home computer does. Before I got the terminal, I used an A/B RS232 switch that switched all 25 wires. Now, to accomodate the terminal, I need a switch that can select connections of 8bit to TNC, 8bit to modem, terminal to TNC, and terminal to modem. A cross connect switch. Which would cost something like $25. I decided to see if I could modify the A/B switch. I use software Xon/Xoff flow control, which needs only 2 active lines and a ground. So, I need only switch 2 lines. Looking at the '89 ARRL Handbook, page 19-28, table 15), it shows the functions of all 25 RS232 wires. The ones I use are pin 2, TxD, and pin 3 RxD. Also pin 1, protective ground, and pin 7, signal ground. But there is a secondary TxD, called STxD, pin 14, and a secondary RxD, called SRxD, pin 16. So, I figured, I would connect the TNC to the common of the A/B switch, to the primary TxD and RxD. And connect the phone modem to the secondary TxD and RxD. (I would need to make a special Y shaped cable to do that.) And connect the 8bit machine to the primary TxD and RxD of the A connector of the switch, and the VT100 to the primary signals of B. Here's the mod to make this work: Wire a jumper from the A connector pin 2 (TxD) to B's pin 14 (STxD). Another jumper from A pin 3 (RxD) to B pin 16 (SRxD). And another from B pin 2 (TxD) to A pin 14 (STxD). And a last jumper from B pin 3 (RxD) to A pin 16 (SRxD). I also shorted all pin 7's together, and shorted all pin 1's together. (This avoids switching spikes in the grounds that might glitch the equipment. Now make the Y cable: pins 2 and 3 of the "common" connector go to the TNC connector pins 2 and 3, respectively. Pins 14 and 16 of the "common" connector go to the phone modem connector pins 2 and 3, respectively. All pin 1's are connected, and all pin 7's are connected. Label the modified A/B switch to describe what you did, so you don't try to use this switch to switch printers or something years later. My switch was an Inmac, with all original wiring traces on a circuit board. All mods are added jumpers, and no cut traces. So, this switch could be restored later if I need to. ============================================================================ 73 de WA2ISE amateur radio packet: WA2ISE@KD6TH Note that I'm at Bell, and no longer at Philips. :-) ------------------------------ Date: 26 Apr 91 23:55:40 GMT From: news-mail-gateway@ucsd.edu Subject: NOAM VERSE NA To: packet-radio@ucsd.edu Just to add my 3 cents worth. After i arrived in Japan and got up on Packet, I had a friend of mine who use N8GTC in Indiana used NOAM so when i sent a return msg, i got a note from VK4BBS telling me in no uncertain terms that NOAM was not correct and to only use NA. So wwhat is correct ? Why would we want to use 4 characters instead of 2? I have a short memory HI HI. If we in the U.S. use 4 ltr and the rest of the world uses 2 it would sem to me that this would lead to even more confusion. There is enuf confusion in the world lets not add to it!!! de KA2RC@KJ6WO.SUBIC.PHL.OC ------------------------------ Date: 26 Apr 91 16:42:39 GMT From: deccrl!news.crl.dec.com!shlump.nac.dec.com!tsar.enet.dec.com!hitz@decwrl.dec.com Subject: NOAM versus NA in addresses To: packet-radio@ucsd.edu Can someone please explain why a set of six entities needs four letter encoding? George, W1DA hitz@tsar.enet.dec.com ------------------------------ Date: 26 Apr 91 18:08:24 GMT From: photon!kurt@ucsd.edu Subject: NOAM versus NA in addresses To: packet-radio@ucsd.edu In article <22357@shlump.nac.dec.com>, hitz@tsar.enet.dec.com (George Hitz) writes: |> |> Can someone please explain why a set of six entities needs four letter |> encoding? |> |> George, W1DA |> hitz@tsar.enet.dec.com Because? ;-} kf -- Kurt Freiberger, wb5bbw kurt@cs.tamu.edu 409/847-8706 Dept. of Computer Science, Texas A&M University *** Not an official document of Texas A&M University *** ------------------------------ End of Packet-Radio Digest ****************************** Date: Sun, 28 Apr 91 04:30:08 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #104 To: packet-radio Packet-Radio Digest Sun, 28 Apr 91 Volume 91 : Issue 104 Today's Topics: NOAM VERSE NA Programming MOTOROLA MX-360 Walkie-Talkie Un-attended HF operation and the FCC Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 27 Apr 91 10:19:18 GMT From: swrinde!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!manuel!csc.canberra.edu.au!echo!skcm@ucsd.edu Subject: NOAM VERSE NA To: packet-radio@ucsd.edu In <9104262355.AA29736@ucsd.edu> asqj-nbf@zama-emh1.army.mil (ASQJ-NBF) writes: >Just to add my 3 cents worth. After i arrived in Japan and got up >on Packet, I had a friend of mine who use N8GTC in Indiana used >NOAM so when i sent a return msg, i got a note from VK4BBS telling >me in no uncertain terms that NOAM was not correct and to only use NA. >So wwhat is correct ? Why would we want to use 4 characters instead of Oh dear... Brian strikes again. :-( Brian Beamish, VK4BBS, is the head of the "Asianet Sysops Organisation". This organisation is basically a loose group of HF sysops clustered around the pacific basin excluding the US and Canada. Unfortunately he is a major link in the Australia<->US/Canada/Japan/etc forwarding scene. He has a rather brusque manner. :-( He was also almost simgle handedly responsible for Australia (and New Zealand etc) using .OC instead of the proper continent designators. :-( Here in Australia, I've heard no no mention of the 4 character country designator. I might mention however that virtually no US bulletins make it down here. Anyone interested in making a US<-internet->Australia forwarding path? :-) Carl. vk1kcm@vk1kcm.act.aus.oc (Yuk... I hate it. .OC) skcm@echo.canberra.edu.au ------------------------------ Date: 26 Apr 91 19:19:57 GMT From: uupsi!nstn.ns.ca!@rice.edu Subject: Programming MOTOROLA MX-360 Walkie-Talkie To: packet-radio@ucsd.edu I need HELP programming the frequency ROM (part# NLN-5096B) in these MOTOROLA HT radios. I have the complete schematics, but have no info on the ROM or how the ROM data is related to the channel freq. Any or all info greatly appreciated ... Sonny / KF4VB Someone please help me .. sonny@sonny.ufnet.ufl.edu 1-904-392-2510 P.S. I would gladly pay $$$ for someone with access to the "PROGRAMMER" to write these ROMS for me .. ------------------------------ Date: 26 Apr 91 17:43:31 GMT From: ogicse!uwm.edu!src.honeywell.com!skyler.mavd.honeywell.com!estey@ucsd.edu Subject: Un-attended HF operation and the FCC To: packet-radio@ucsd.edu There is a 5-part message from Tom, W3IWI floating around concerning the latest FCC action regarding the January problem of automatic forwarding of a message apparently violating FCC rules. Since only 2 of the 5 parts have arrived here I sure would appreciate seeing it posted here in its entirety. In that I am one of the stations covered by the current STA for unattended HF operation (14.109 Mhz) I have a lot of interest in the subject. Judging from what I have seen in the 2 parts of Toms message the only options for those of us operating unattended may be to terminate operations. Putting all messages on hold for SYSOP review puts a tremendous burden on the local SYSOP and slows message distribution considerably. In the short term that solution (hold for review) may work but in the long-term is not workable. Comments from SYSOPs involved with the problem? 73 de Carl -- ______________________________________________________________________________ Carl Estey | Home Mail Address: 276 Walnut Lane Amateur Callsign: WA0CQG | Apple Valley, MN 55124 ARMY MARS Callsign: AAV5TO | Business Address: Honeywell Inc. Phone: Work (612) 541-5136 | Flight Systems & Test Operations M/S MN15-2370 FAX (612) 542-6003 | 1625 Zarthan Ave. S., St. Louis Park, MN 55416 Home (612) 432-0699 | Packet: WA0CQG @ WA0CQG.MN.USA.NA The nonsense here is of my own making - no one else would want credit! ------------------------------ End of Packet-Radio Digest ****************************** Date: Tue, 30 Apr 91 04:30:03 PDT From: Packet-Radio Mailing List and Newsgroup </dev/null@ucsd.edu> Reply-To: Packet-Radio@UCSD.Edu Subject: Packet-Radio Digest V91 #105 To: packet-radio Packet-Radio Digest Tue, 30 Apr 91 Volume 91 : Issue 105 Today's Topics: Cost Benefit Ratio How to get started in packet radio? PK232 COMMAND LIST Send Replies or notes for publication to: <Packet-Radio@UCSD.Edu> Send subscription requests to: <Packet-Radio-REQUEST@UCSD.Edu> Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Packet-Radio Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/packet-radio". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 29 Apr 91 04:24:30 GMT From: swrinde!cs.utexas.edu!helps!bongo!julian@ucsd.edu Subject: Cost Benefit Ratio To: packet-radio@ucsd.edu I've been ill in bed for the last few days and running short of light reading material. So, I picked up QST "devoted entirely to amateur radio". Despite pain, psycho-tropic drugs and boredom I made it to page 27. In the bottom half of the page is the "New Products" column. Ah! New DSP chips? a cheap dish? No such luck. Sitting there in a photo are two Morris Keys. These keys, a paddle type and a straight (up & down) type are hand crafted and made from modern materials like Bakelite, wood, aluminium and brass. The price of the keys is between $70 and $100. I wonder if that includes error-correction circuitry? But then, how do we measure pleasure? How do we evaluate the truth and veracity of religion? After a quick kip I made it through to page 163 (Not marked by QST for some reason). There I saw that MFJ had an electronic keyer/key combo for $134.95, PSU $12.95 extra. Page 165, (Still no damn number QST) has a 1200 Baud TNC for $139.95 - and PSU included. Error correction circuitry also included. And now back to the National Enquirer to see what Liz and Dolly are up to. -- Julian Macassey, n6are julian@bongo.info.com ucla-an!denwa!bongo!julian 742 1/2 North Hayworth Avenue Hollywood CA 90046-7142 voice (213) 653-4495 ------------------------------ Date: 30 Apr 91 03:13:56 GMT From: o.gp.cs.cmu.edu!andrew.cmu.edu!rh2y+@pt.cs.cmu.edu Subject: How to get started in packet radio? To: packet-radio@ucsd.edu Hello, all. I'm posting this for a moderately sizable group of people. Quite a few of us OS9 and Color Computer users are also (or want to be :-) ham operators. After a discussion on our network bulletin-board, we decided somebody should ask around, to get us all started in the right direction. We want to use packet-radio in conjunction with the Tandy Color Computer, running under the OS9 operating system, as well as other computers running this same operating system. It's very similar to Unix. Our question is thus: Does anyone know of already existing software for doing packet radio under the OS9 operating system (whether or not specifically for the Color Computer). If so, where can we get it? If not, is there Unix source available, as this would be most likely the easiest to port from. Also, as many of us are novices, we'd like to know basically what is necessary to get started in packet radio, and where to get information on the subject. I've heard that there are certain packet controllers that do most of the work themselves, and all you need is a terminal. Is this true? I know these are all FAQ, but i didn't see an FAQ list on this board. Thanks for any help! Russell Hoffman rh2y+@andrew.cmu.edu Carnegie Mellon University ------------------- ------------------------------ Date: 29 Apr 91 19:17:49 GMT From: fs7.ece.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!paul+@sei.cmu.edu Subject: PK232 COMMAND LIST To: packet-radio@ucsd.edu I have compiled an ASCII text file which contains all of the PK232MBX commands and options as of the MBX update. I wanted a file that could be searched from within a terminal program to get information about some particular PK232 command without having to drag out the manuals. Is it legal to post this file, considering that this information is Copyright by AEA? If it is legal, would anybody out there in netland be interested in having a copy? File is almost 100K and is plain ASCII text with no formatting or hidden control characters. \paul WA3TLD pauld@fs1.ece.cmu.edu or paul+@andrew.cmu.edu or WA3TLD @ NO3M.#WPA.PA.USA.NA ------------------------------ End of Packet-Radio Digest ******************************