Date: Mon, 16 Aug 93 04:30:05 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #210
To: tcp-group-digest
TCP-Group Digest Mon, 16 Aug 93 Volume 93 : Issue 210
Today's Topics:
Modifying radios for 9600baud
NOS-BBS down
PMNOS errata and misc
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
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: Mon, 16 Aug 93 01:36:20 PDT
From: tking@oes.ca.gov (Tom King)
Subject: Modifying radios for 9600baud
To: tcp-group@ucsd.edu
Clint KA7OEI writes:
>From: ka7oei@uugate.wa7slg.ampr.org
>Subject: Modifying IF's for 9600 baud...
>To: tcp-group@ucsd.edu
>
>I was wondering about the feasiblity of simply bypassing the 455 KHz filter
>and using the 10.7 MHz xtal filters in the first IF, or perhaps
>'beefing up' the filters in the first IF. After all, the 10.7 MHz
>filters *are* relatively inexpensive AND readily available (Digi-Key, etc.)
>
>A few those monolithic 2-pole xtal filters (and a few caps) would probably
>do the job, unless you had some very strong adjacent channel signals...
>Wouldn't they?
>
>Clint
455khz filters are even cheaper than the 10.7mhz Crystal types. Unless
you have unacceptable group delay through the ENTIRE IF chain it is
probably better to just widen out the 455khz filters and not extensively
modify the IF/Discriminator Circuits.
Also by eliminating the 2nd IF you increase the chances of an image or1/2
IF problem (especially a problem if your station is on a hilltop or near a high
power base in the commercial or public safety services)
Tom
Packet: KA6SOX@ K6TZ.#SOCAL.CA.USA.NA
Internet: tking@oes.ca.gov
------------------------------
Date: Sun, 15 Aug 1993 16:36:59 -0400 (EDT)
From: "Barry McLarnon" <barry@dgbt.doc.ca>
Subject: NOS-BBS down
To: tcp-group@ucsd.edu
> Does anyone know if the NOS-BBS server at Carleton is down? I haven't got
> any updates for a few days.
I just got back from a week out of town, and it looks like the ethernet
between hydra.carleton.ca and the rest of the world got broke sometime
last Wednesday. We'll try and get it restored in the next couple of
days.
Barry
--
Barry McLarnon | Internet: barry@dgbt.doc.ca
Communications Research Center | AMPRnet: barry@bbs.ve3jf.ampr.org
Ottawa, Canada K2H 8S2 | PBBSnet: ve3jf@ve3jf.#eon.on.can
------------------------------
Date: Sun, 15 Aug 93 15:25:54 GMT
From: kz1f@legent.com (Walt Corey [44.104.0.23])
Subject: PMNOS errata and misc
To: tcp-group@ucsd.edu
It has come to my attention that several people have run into problems with
PMNOS under OS/2 v2.1GA. I can assure you there is nothing inherent in PMNOS
that causes a problem with OS/2 2.1 GA, in fact, I am using it here. I
believe I know the problem and the cause. In the situations that have been
reported to me the common denominator has been they used it in the 2.1
betas. If the nos.ini file was created during the time when IBM changed the
format of the ini file then PMNOS running under GA would not be able to read
it properly. The solution, delete \spool\nos.ini and restart PMNOS. This
will lose your earlier fonts, screen size and position settings, but those
can be reset.
-------------
On the subject of PMNOS, just so y'all know. I am only waiting to try to
resolve the operator page problem before I release PMNOS 1.1. Of the
features I have added, BOOTP and BOOTPD and a really nice feature some of
you will particularly like, fault tolerance operation. PMNOS will
effectively be crash proof. That is to say, when hitting one of those nos
bugs that would make PMNOS 'disappear' (a user euphemism for crashing) PMNOS
now will disable the offending process and truck on as if nothing had
happened. The user will get a notification of the exception with the process
name and the address that took the exception.
If too much time elapses I will release 1.1 as is. Walt
*********************************
* kz1f@kz1f.ampr.org or *
* kz1f@legent.com *
* The home of OS/2 NOS and PMail*
*********************************
------------------------------
End of TCP-Group Digest V93 #210
******************************
******************************