Date: Wed, 23 Mar 94 04:30:37 PST From: Ham-Digital Mailing List and Newsgroup Errors-To: Ham-Digital-Errors@UCSD.Edu Reply-To: Ham-Digital@UCSD.Edu Precedence: Bulk Subject: Ham-Digital Digest V94 #79 To: Ham-Digital Ham-Digital Digest Wed, 23 Mar 94 Volume 94 : Issue 79 Today's Topics: [REPOST] NTS Traffic on Packet [REPOST] The # in PBBS addresses.... GUI mailgateway Packet Radio <--> Internet RS htx202/KPC-3 wiring question Send Replies or notes for publication to: Send subscription requests to: Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Ham-Digital Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital". 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: Wed, 23 Mar 94 05:53:25 GMT From: netcomsv!netcomsv!skyld!jangus@decwrl.dec.com Subject: [REPOST] NTS Traffic on Packet To: ham-digital@ucsd.edu In article yarbrda@moose.gdss.grumman.com writes: > For some more specific questions: > > 1) if I put a traffic message on a PBBS, how long is that message > likely to remain there for a human to pick up, before the PBBS > automatically tries to start forwarding it to a another system? If there are people that regularly check in and do an LT, it gets serviced in a reasonable amount of time. Sometimes traffic gets dumped off on a BBS that no one checks and the traffic languishes until the Sysop finally services it himself. > 2) Like 1, but applied to intermediate forwarding systems along the > way to the final destination PBBS. Traffic is forwarded along with the personal and bulletin mail. Most Sysops have ST mail prioritized over personal or bulletin mail. > 3) What determines if a particular PBBS will receive NTS traffic > destined for a particular area around that PBBS. That is an arrangement made between local Sysops. A given Sysop will aggree to service a given block of zip codes, then those zipcodes will be forwarded to that system. > Thanks for the enlightenment. The amount of traffic that could be handled by packet could be increased by at least an order of magnatude except for some of the more diehard brass pounders that feel that automatic means just isn't the "real man's way" of handling traffic. Amateur: WA6FWI@WA6FWI.#SOCA.CA.USA.NA | "You have a flair for adding Internet: jangus@skyld.grendel.com | a fanciful dimension to any US Mail: PO Box 4425 Carson, CA 90749 | story." Phone: 1 (310) 324-6080 | Peking Noodle Co. ------------------------------ Date: Wed, 23 Mar 94 06:00:57 GMT From: netcomsv!netcomsv!skyld!jangus@decwrl.dec.com Subject: [REPOST] The # in PBBS addresses.... To: ham-digital@ucsd.edu In article yarbrda@moose.gdss.grumman.com writes: > What's the significance of the # in certain PBBS addresses? I've seen > them used with some places and not in others. For example, my own is > > ke4dxa @n4lxi.#nova.va.us.noam. ^-- North America (Continental Code) ^----- United States (Country Code) ^-------- State or Province ^------------- State sub-divisor (Area) ^-------------------- Destination BBS ^---------------------------- User the # symbol is an area designator. This way nova is not confused with some other location. > (if memory serves :-). Yet I've seen others that would leave it off. > I've also seen various uses of us vs. usa, and na vs. noam. Which one > is correct (or are they all?). People are trying to get the amateurs to go along with what is recognized as "correct" by the rest of the communications world. NA is a country code for Namibia, NOAM is a Continent Code for North America. I saw a bulletin on Packet the other day from a Sysop complaining about people (notably aa4re) "Forcing him to use NOAM, when NA works fine." You really have to wonder where some of these people are coming from. Amateur: WA6FWI@WA6FWI.#SOCA.CA.USA.NA | "You have a flair for adding Internet: jangus@skyld.grendel.com | a fanciful dimension to any US Mail: PO Box 4425 Carson, CA 90749 | story." Phone: 1 (310) 324-6080 | Peking Noodle Co. ------------------------------ Date: 23 Mar 1994 04:20:29 GMT From: ihnp4.ucsd.edu!usc!sol.ctr.columbia.edu!howland.reston.ans.net!torn!hermes.acs.ryerson.ca!ee.ryerson.ca!jeff@network.ucsd.edu Subject: GUI To: ham-digital@ucsd.edu FREEMANR@dstos3.dsto.GOV.AU wrote: : I am trying to interface MS Windows/Windows for Workgroups with KA9Q : package of NOS. Has anybody done this before? Any assistance with this : little project of mine will be appreciated. Well, I don't have any MS Windoze experence, but I'd like to see a nice XWindow interface on it. Perhaps we could make some GUI hooks that will allow us to port GUINOS?? to other platforms, like UN*X and XWindow, or Mac. Hmmmm since XWindow is client server.... perhaps something really interesing could come out of that. : Thanks Roy Send me some E-Mail with info on what base code, where you want to go, that sort of stuff. Sounds great. 73! de Jeff / VE3DJF Jeff@EE.Ryerson.Ca VE3DJF@bbs.VE3RPI.ampr.org ------------------------------ Date: 23 Mar 1994 10:54:39 GMT From: ihnp4.ucsd.edu!usc!howland.reston.ans.net!EU.net!Germany.EU.net!netmbx.de!zrz.TU-Berlin.DE!cs.tu-berlin.de!math.fu-berlin.de!news.th-darmstadt.de!zib-berlin.de!tfh-berlin.de!sun21.@network Subject: mailgateway Packet Radio <--> Internet To: ham-digital@ucsd.edu Hi everybody, I have read in the newsgroup rec.radio... in Amerika you have a mailgateway between Packet-Radio and Internet.I have a friend living not far away from me to send him a email to his Packet-Radio MBOX. How I have to adress it if I want to mail him. Is the domain ampr.org o.k? His Packet-Radio-Adress is DH7TA@DB0GR.DEU.EU. Have I write to DH7TA@DB0GR.AMPR.ORG or to DH7TA@DB0GR.DEU.EU.AMPR.ORG ? Many thanks for your help regards & 73 Olaf P.S. Please send answer with a carbon copy to DH7TA@DB0GR.DEU.EU ------------------------------------------------------------------------- _/_/ O L A F M E N Z E L _/ _/ Petersburger-Str. 31 | Informatik-Student _/ |\/|/ D-10249 Berlin | student of computer sc. _/ | | GERMANY | Technische Fachhochschule Berlin _/ _/ tel: +49 30 4296240 | email: menzel@tfh-berlin.de ------------------------------ Date: 22 Mar 94 16:02:25 GMT From: galaxy.ucr.edu!library.ucla.edu!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!swrinde!sgiblab!cs.uoregon.edu!reuter.cse.ogi.edu!netnews.nwnet.net!bach.seattleu@ihnp4.ucsd.edu Subject: RS htx202/KPC-3 wiring question To: ham-digital@ucsd.edu In article , Mark Ellis wrote: > >UPS last nite dropped off my Kantronics KPC-3 (YAY!), so I'm soon >to be packet-positive. Got one question: > >Since my HT (htx202) is my only rig at the moment, are there >any special considerations while wiring up the mic plug for packet? > >The KPC-3 manual does not specifically mention this radio in the >wiring section, but since Icom speaker-mics (I think, working from >memory) work with the 202, that's a tiny hint to follow the Icom >wiring diagram. > >Any tips/suggestions/etc. will be appreciated. > > .... Mark E. Ellis N2WZB > > PA&TD Workplace Automation Group > SMCAR-QAH-P, Bldg 62N > Picatinny Arsenal, NJ Yep, the Icom info is what to use. One caution: look over the plug very carefully under a magnifying glass for loose connections. They are very small and fragile - mine developed a loose connection where the solder lug is rivited to the center conductor and drove me nuts trying to find the problem, since it was VERY intermittent. It wouldn't work when plugged into the radio, but when removed for continuity testing, of course it was ok. Just make sure it's solid. 73 de Bill, W7LZP wrt@eskimo.com ------------------------------ End of Ham-Digital Digest V94 #79 ****************************** ******************************