OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
M0PZT  > WINPAC   30.05.09 01:21l 45 Lines 1394 Bytes #999 (0) @ WW
BID : 955_M0PZT
Read: GUEST
Subj: Re: The laptop's problem
Path: IZ3LSV<IK2XDE<DB0RES<DK0WUE<7M3TJZ<ZL2BAU<GB7ESX<M0PZT
Sent: 090529/1439 @:M0PZT.GB7ESX.#31.GBR.EU $:955_M0PZT Sally 4.1.231 Essex

VK6BE wrote:

> until I have a chance to test manual connection.

You can invoke a manual connection by running the BBS.TXT script which will 
connect you via any nodes (or in your case the telnet login) and leave you 
at the BBS prompt.  Simple.

> to make a real test I need a bull from Ray VK2TV.

...and the others whose messages have been subject to the Great VK6BE 
Australian Revolution of 2009.  It's a growing list, 
innit.

> Turning to the laptop Winpack has a problem there too
> I get an error message "Can't find the packet engine AGWPE".
> I check AGWPE which is on the desktop
> I have "TCP 8000" which is the default value and "enable Winsock tcp/ip
> application interface" Are these right for Winpack? 

You do not need AGW for Telnet connects out of WinPack.  AGW is a driver 
program to control/access TNC hardware (and sound cards) from multiple 
programs.  WinPack does NOT use TCP/IP to talk to AGW - it uses DDE which 
means that AGW MUST run on the same PC as WinPack.

Don't run AGW.  Use WinPack in "Telnet" host-mode with "Enable Auto 
Telnet" in the Options menu ticked.

> Please don't ask for my .ini file. The problem is not there!!

I'm cutting-out that quote and pinning it to my shack wall.

> I know nothing about AGWPE.

At last, we're finally getting somewhere!


--
Charlie - M0PZT @ GB7ESX.#31.GBR.EU
http://www.m0pzt.net

Sent: 14:27 on 29 May 2009




Read previous mail | Read next mail


 29.09.2024 19:39:15lGo back Go up