| |
PA2AGA > HDDIG 31.05.00 02:15l 178 Lines 5448 Bytes #-9463 (0) @ EU
BID : HD_2000_151B
Read: GUEST
Subj: HamDigitalDigest 2000/151B
Path: DB0AAB<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0FBB<DB0GOS<DB0PKE<DB0OVN<PI8JOP<
PI8ZAA<PI8GCB<PI8HGL
Sent: 000530/1829Z @:PI8HGL.#ZH1.NLD.EU #:45633 [Den Haag] FBB $:HD_2000_151B
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Tue, 30 May 00 19:47:45 MET
Message-Id: <hd_2000_151B>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
sound card. This worked for me....
73,
Tom - KB2SMS
------------------------------
Date: Tue, 30 May 2000 02:17:35 GMT
From: Dick Hughes <ragoldhughes@worldwingnet.att.net>
Subject: DigiPan Receive Audio Hint Needed
On Tue, 30 May 2000 01:34:55 GMT, TomR@astro.net wrote:
>On Mon, 29 May 2000 23:10:29 GMT, Dick Hughes
><ragoldhughes@worldwingnet.att.net> wrote:
>
>>I am currently using DigiPan with a SoundBlaster soundcard and Icom
>>IC-736 radio. I am using the aux speaker output on the Icom driving
>>the line input on the SoundBlaster. I have experimented with
>>different audio settings on both the radio and the computer. I don't
>>see much difference in quality of printout. I basically look for lots
>>of blue dots in the background and leave it at that. Is there a way
>>to achieve a more optimized receive level with DigiPan, or does it
>>even matter? I see lots of signals that appear strong on the DigiPan
>>screen, yet yield poor printout. Maybe they are just poor to begin
>>with, but I would like to know it's not on my end.
>>
>>Dick Hughes - W6CCD
>
> Dick,
> Try plugging the audio cable from your rig to the mic input on the
>sound card. This worked for me....
>
>73,
>Tom - KB2SMS
Thanks Tom. I will try it tonight, but I didn't initially because I
seem to have more than enough drive from the Icom for the line input.
I have the audio gain set at about 1/3.
Dick Hughes - W6CCD
Remove Gold & Wing from address
------------------------------
Date: Tue, 30 May 2000 11:17:02 +0100
From: Roger Barker <roger@peaksys.co.uk>
Subject: Flexnet API Info?
Does anyone know where I can find information on the Flexnet 32 bit API?
I want to add support for it to a packet application, so I'm looking for
detailed docs, not just an overview.
--
Roger Barker, G4IDE - roger@peaksys.co.uk
For UI-View go to - http://www.packetradio.org.uk
For WinPack go to - http://www.peaksys.co.uk
------------------------------
Date: Tue, 30 May 2000 01:59:56 GMT
From: "Mike Pupeza" <michael.pupeza@sympatico.ca>
Subject: N0ZO no longer supports Keyboard inputs!
Well Gang;
I said it would happen! My favorite Pactor WinLink BBS N0ZO in Lady Lake,
Florida will no longer talk to me.
Reason! I don't run the AirMail 2000 program!
I want to, but CAN'T!
My TNC - a PacComm PacTOR CONTROLLER, which is totally PTC-1 Compliant - the
ORIGINAL and STARTER of the whole Pactor scene, is INCOMPATIBLE, and NOT
SUPPORTED by the AirMail 2000 program!
Guys, I bought this NEW in February of 1999 - it's not OLD!
Also, I have a Mac I-book, for which there is no support! And I know people
who run Linux!
So here I go again, bitching! But, c'mon!
I hope that there are some changes in PSK-31 that'll allow error checking
and correction that'll make these PTC-II and IIe controllers as useful as
Commodore 64's, in todays world!
Off my chest! Thanks!
--
Mike Pupeza VE3EQP
------------------------------
Date: Mon, 29 May 2000 21:23:08 -0500
From: Seth Miller <sethmiller73@email.com>
Subject: N0ZO no longer supports Keyboard inputs!
Mike,
It was not SCS that made the decision to support only binary mode transfers,
rather it was the WinLink 2000 authors.
It is unfortunate that PacComm didn't implement a binary transfer mode (which
is
the problem in your case, and not Pactor I vs. Pactor II issue). Other
manufacturer's Pactor I TNC's (Kantronics, AEA, etc.) are supported by
AirMail/WinLink. This issue has no relationship to SCS and/or the PTC-II
series
- if you want to be bitter at least aim it at the right manufacturer.
- Seth
Mike Pupeza wrote:
> Well Gang;
>
> I said it would happen! My favorite Pactor WinLink BBS N0ZO in Lady Lake,
> Florida will no longer talk to me.
> Reason! I don't run the AirMail 2000 program!
> I want to, but CAN'T!
> My TNC - a PacComm PacTOR CONTROLLER, which is totally PTC-1 Compliant - the
> ORIGINAL and STARTER of the whole Pactor scene, is INCOMPATIBLE, and NOT
> SUPPORTED by the AirMail 2000 program!
> Guys, I bought this NEW in February of 1999 - it's not OLD!
>
> Also, I have a Mac I-book, for which there is no support! And I know people
> who run Linux!
>
> So here I go again, bitching! But, c'mon!
>
> I hope that there are some changes in PSK-31 that'll allow error checking
> and correction that'll make these PTC-II and IIe controllers as useful as
> Commodore 64's, in todays world!
>
> Off my chest! Thanks!
> --
> Mike Pupeza VE3EQP
------------------------------
Date: Mon, 29 May 2000 21:56:50 -0500
From: "Steve Sampson" <ssampson@usa-site.net>
Subject: N0ZO no longer supports Keyboard inputs!
PSK31, to me, is like the microsat to the phase III type satellite.
In this case, the PSK31 mode is popular because people get to
communicate with other Hams, rather then send mail to some
anonymous machine.
If the C-64 had a sound card, it would be a killer-App today :-)
"Mike Pupeza" wrote
> I hope that there are some changes in PSK-31 that'll allow error checking
> and correction that'll make these PTC-II and IIe controllers as useful as
> Commodore 64's, in todays world!
>
> Off my chest! Thanks!
------------------------------
Date: Tue, 30 May 2000 03:46:02 GMT
From: jflanders2@home.com (Jerry Flanders)
To be continued in digest: hd_2000_151C
Read previous mail | Read next mail
| |
