| |
PA2AGA > HDDIG 18.10.99 00:09l 213 Lines 7276 Bytes #-9715 (0) @ EU
BID : HD_99_262B
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/262B
Path: DB0AAB<DB0ZKA<DB0ABH<DB0BOX<DB0MAK<DB0ERF<DB0SHG<DB0SM<PI8DAZ<PI8GCB<
PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991017/1814Z @:PI8VNW.#ZH2.NLD.EU #:8519 [HvHolland] FBB7.00g $:HD_99_262
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21471 ; Sun, 17 Oct 99 18:01:05 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016466 ; Sun, 17 Oct 99 16:18:57 MET
Date: Sun, 17 Oct 99 16:07:25 MET
Message-Id: <hd_99_262B>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/262B
X-BBS-Msg-Type: B
> >idea to see what Linux had to offer. Within a day of installing Linux
onto
> >my network, the windows machines began to crash frequently. Once Linux
> >was removed from the network, windows again became very stable.
> >
> >> I intend to wait until this problem with LINUX boxes mysteriously
causing
> >> nearby Win95/98 machines to become crash-prone has been tracked down
and
> >> resolved.
> >
> >This seems a reasonable thing to do. Perhaps the Linux experts can
explain
> >why this problem occurs. For now it seems the best thing to do is to
avoid
> >Linux until the problem is cured.
>
>
> Hmm, I have seen weird stuff happen when multiple machines get the same IP
> on a lan.
Different ip, same subnet (44.116.1.*)
> That would be the first thing to check. Win98 has dhcp client
> installed by default --
dhcp is disabled on all my windows machines.
> and me, I found that, unbeknownest
> to myself, the IP router I installed had an dhcp server running.
The router did not have dhcp enabled.
Samba had dhcp disabled.
> So, what
> happened, is when one of the misconfigured Windows systems in the
> building got turned on, the dhcp server in the gateway which I didn't
> know about assigned it to the same ip addresses as the name server.
> And, then things acted really weird all over. I only found out about
this,
> when I tried to setup DHCP myself, on a different server, and found
> something else on the net was handing out addresses. Ooops.
Not what happened.
In fact, the problem continued even with the ethernet cable removed
from the Linux machine. But now that the Linux CD is back in it's box
on the shelf, and the hard drives reformatted and repartitioned, everything
is back to normal again.
> It's hard to figure out these things if you're system isn't up any more.
The system is up (with two ethernet cards and an ip router), just not
running Linux.
> Though I've seen the Win98 machines with unset ip addresses -- either
> with or without DHCP servers on the lan doing all sorts of weird stuff.
Usually
> they don't crash, but they lock up intermittantly for a bit. This might
be fixed
> with Win98 as upposed to Win95.
I'll play the game a bit here: don't forget to use the same netmask on all
your windows machines. If you do not, there will be intermittent network
problems between the machines as one or another votes itself master and
does it's "hi I'm here, anyone around" broadcasts.
> Possibly there's some other issue. If you install Linux and you just tell
it
> to turn on everything, not knowing what it all is, it might cause a
problem. Me,
> I only run what I need and don't turn on, for example, smbd, or Linux
netbios
> stuff unless I really want it.
> Though I also get all the patches and updates to Win98 pretty regularly.
So,
> maybe that's the obvious and easy thing to try. Me, I'm a little
> hacker paranoid, so if there's some packet of death that blows out
Windows,
> I'd rather know what it is and fix it. Since possibly someone can send in
> that same block from the internet onto your lan.
No, it was clearly the simple act of loading Linux onto the machine that
caused all the problems. They are over now, and everything is back to
normal: nice stable Windows, DOS and CP/M systems.
>.
------------------------------
Date: 15 Oct 1999 18:59:13 GMT
From: nielsen@primenet.com (Bob Nielsen)
Subject: The BBS network and tcp/ip.
If this is the same host mode (BLP) as in the recent 1270 firmware (and
I have no reason to believe it is different), you can find the host
mode documentation on the TAPR web site (the same host mode is in TAPR
firmware versions 1.1.8 and 1.1.9 as well). As far as I know, only
packet is supported by the host mode, not pactor or amtor.
See ftp://ftp.tapr.org/software_lib/tnc/hostmode.zip
There is finally a commercial implementation of host mode software
available for BLP, but nothing yet for Linux.
Bob
On Thu, 14 Oct 1999 21:24:17 -0700, Cathryn Mataga wrote:
>Speaking of drivers, I have a MFJ 1276 right here, and I asked MFJ
>via E-mail if there was host mode documentation for this thing, but they
>never responded. It mentions host mode in a single sentence in the
>manual and says there's docs for it, but so far I have seen no
>evidence of this. Maybe the only way to talk to this box is by
>massaging the ASCII commands, which I sort of dread.
>
>So, if anybody knows how to program this thing -- I could use a pointer
>for this.
>
>Actually, the MFJ 1276, is kind of nice otherwise. It can do 9600 with
>an add-on board, apparently, and is as cheap as you can go for Pactor.
>
>I wasn't so sure about whether the P38 was still a live product. Though
>checking out www.halcomm.com shows them still selling it. Actually
>compared to the SCS boxes, these look like they get pretty good
>throughput, for less money. It seems like we should be able to get
>as good using software only, with the floating point being so fast
>on the pentiums, nowadays -- so I'm not sure what kind of future these
>sort of boards have.
>
>I have also seen some messages on the Tapr board lately about how
>BPQ is apparently still being worked on for win32 by somebody
>out there, which was news to me as of a few days ago. So, maybe
>there still is some life left in the DOS/win ham radio stuff.
>
>
>Hank Oredson wrote in message <7u64ur$d8m$1@bgtnsc03.worldnet.att.net>...
>>
>>Demetre Ch. Valaris <sv1uy@nest.sv1uy.ampr.ORG> wrote in message
>>news:2325.sv1uy@nest.sv1uy.ampr.org...
>>> Hank Oredson <horedson@att.net> wrote:
>>>
>>> > Where is a HAL P38 / PCI400 driver?
>>> > Where is the server to gateway telnet <-> net/rom <-> CLOVER <-> PACTOR?
>>>
>>> Well here is your big opportunity to write them yourself i.e. a driver
>>> for a HAL P38 / PCI400, a driver for a PTC-II etc. This way you would do
>>the
>>> amateur community a favour Hank.
>>>
>>> Just an idea for you to create a solution!!! Isn't that what you are
>>looking
>>> for?
>>
>>Already done it ... long time ago.
>>They still work.
>>Others have done it as well, for DOS and Windows.
>>
>>But nobody does it for Linux.
>>I wonder why?
>>
>>--
>>
>> ... Hank
>>
>>http://horedson.home.att.net
>>
>
>
>http://ke6i.com
>
>
--
Bob Nielsen Internet: nielsen@primenet.com
Tucson, AZ AMPRnet: w6swe@w6swe.ampr.org
DM42nh http://www.primenet.com/~nielsen
>.
------------------------------
Date: Fri, 15 Oct 1999 12:14:45 -0700
From: "Cathryn Mataga" <cathryn@junglevision.com>
Subject: The BBS network and tcp/ip.
Yeah, thanks for the information to you and the other guy who responded.
My main interest right now is in the HF modes, so I guess the only way to
talk to the 1276 for Pactor is mushing around with ascii commands.
And, yes, it'd be nice to have a Linux driver that could talk to this
To be continued in digest: hd_99_262C
Read previous mail | Read next mail
| |
