| |
PA2AGA > HDDIG 17.10.99 23:11l 201 Lines 7042 Bytes #-9715 (0) @ EU
BID : HD_99_261F
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/261F
Path: DB0AAB<DB0ZKA<DB0ABH<DB0SRS<DB0MW<DB0NHM<DB0EAM<DB0FC<DB0SHG<DB0SM<
PI8DAZ<PI8GCB<PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991017/1638Z @:PI8VNW.#ZH2.NLD.EU #:8445 [HvHolland] FBB7.00g $:HD_99_261
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21461 ; Sun, 17 Oct 99 16:24:15 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016457 ; Sun, 17 Oct 99 16:18:28 MET
Date: Sun, 17 Oct 99 16:07:16 MET
Message-Id: <hd_99_261F>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/261F
X-BBS-Msg-Type: B
1270 and 1276, but it doesn't include Pactor on the 1276. They are looking
at what to remove to put the BLP host code back into the 1270/1276 firmware.
BLP is an OSI based host protocol. Sample code (MTHOST and it's sources)
are on the TAPR site in a file called hostmode.exe. I'd like to see it
developed for Linux, as we have a Windows 32 bit version working now,
Multicomm Host. (and have been showing it at Hamfest's since Dayton this
year). Next stop, Lawrenceville in November.
The bad news about BLP is that we found two major showstoppers with the
current BLP release (which hasn't changed since 1991). The first is that if
you leave the TNC off for a day or so in BLP mode, the TNC has problems
connecting more than once. The second problem is that any host command that
has returned information greater than 300 byte gets truncated (the cstatus
and display commands are the two most notable). MFJ is working to get these
fixes in, but there is no timeframe for completion yet.
We're also working with HAL with the DXP38 and P38. Their 'api' is a numeric
based protocol. (I.e. 0x0813 N4GDO 0x8000 sets the mycall in the unit). Bill
Henry is very open with his programming interface, might want to give him a
call. Again, we have a Win 32 bit interface to it and have it working in 3
of the 6 modes it supports.
regards,
--
Rick Ruhl
President, Creative Services Software
http://www.cssincorp.com
Cathryn Mataga wrote in message ...
>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
>
>
>.
------------------------------
Date: Fri, 15 Oct 1999 09:12:31 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>> 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.
Samba is not related to DHCP.
>> 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.
So there you are. The problem is caused by the string "Linux" appearing
somewhere on a disconnected harddisk, and Bill Gates freaking out!
>> 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.
It will probably crash soon, now that you have mentioned Linux so often
the past week. This is the influence of the mighty imperium being so
close to you (as compared to us europeans).
Rob
--
+----------------------------------+--------------------------------------+
| Rob Janssen pe1chl@amsat.org | WWWhome: http://www.pe1chl.demon.nl/ |
| AMPRnet: rob@pe1chl.ampr.org | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
+----------------------------------+--------------------------------------+
>.
------------------------------
Date: Fri, 15 Oct 1999 09:30:08 GMT
From: nomail@pe1chl.demon.nl (Rob Janssen)
Subject: The BBS network and tcp/ip.
Hank Oredson <horedson@att.net> wrote:
>> 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?
When you would have been interested yourself, it would have been very easy
to write the driver. Probably you could even have ported it from your DOS
version when the code had been written in a modular fashion.
Driver writing for Linux is easy as you have many examples to look at, and
you can clearly see what is happening at all the system interfaces. No
guessing what is happening in a "black box" while you are debugging.
But you are not interested in writing for Linux yourself, and probably
nobody else is interested in the drivers for PACTOR as they have moved on
to TCP/IP over faster stuff these days.
To be continued in digest: hd_99_261G
Read previous mail | Read next mail
| |
