Sound Card Packet  with AGWPE

Translations and PDF of this site
Most recent AGWPE version is:  2013.415  15 Apr 2013

Computer requirements
Packet Engine Pro

Configure AGWPE
Download and Install
Basic AGWPE Setup
2 Radio Setup
2 Card Setup

Sound Device Setup
Basic Device Settings
Rename Sound Device
Additional Settings
Using the Tuning Aid

Program Behavior

AGWPE Features
AGWPE on a Network
Baud Rates & Modes
Remote Control
TCP/IP Over Radio
Tips and Tricks
Traffic Parameters

Compatible Programs:
Setup Help

Radio Interface
Getting Started
Kits and Pre-assembled
USB SignaLink
Receive Audio Cable
Transmit Audio Cable
PTT (TX Control) Cable
2 Radio Modification

About Packet
Packet Overview
Exchange Modes
What To Do with Packet
Common Frequencies
Frame Headers
Further Reading

Enabling the TCP/IP Protocol in Older versions of Windows

This page applies to users running pre-Windows XP operating systems. In Windows XP and more recent versions, internet connectivity should be on by default. That means the TCP/IP protocol should be operational and no special steps need be taken to turn it on.

AGWPE can use either the DDE or the Window's Winsock TCP/IP Application Interface to communicate with client packet applications. Except for WinPack and a few other programs using the DDE link exclusively, most programs use the TCP/IP interface. 

For the TCP/IP interface to work, TCP/IP must be enabled in both Windows and AGWPE Here are the two steps:

1. Activating the TCP/IP protocol in Windows

If you can use the internet now, then the TCP/IP protocol has already been activated in your Windows installation, either through the installation of a network interface card or Windows' Dial-Up Networking (DUN). If you are not sure if it is installed, see the Testing the TCP/IP Setup in Windows box just below.

If the TCP/IP protocol is not installed, install Windows' Dial-Up Networking (DUN) component: from the Control Panel, select Add/Remove Programs. Then click on the Windows Setup tab and then select (one click) Communications. Now press the Details button and then click on/check mark Dial Up Networking. Press the OK button twice. (You then may be prompted for your original Windows installation disks for the required files.) 

Now, with the Dialup Adapter installed, install the TCP/IP protocol. Select Control Panel again, then Network. Now select Add, then double click on Protocol, then Microsoft, then TCP/IP, then OK.

2. Enabling TCP/IP in AGWPE

AGWPE's  TCP/IP Application Interface  should be "enabled" in AGWPE automatically; it's the default condition in a new AGWPE installation. But to check it open the AGWPE menu, click on Setup Interfaces, and then on Winsock Interface tab make sure there is a check mark in the box next to "Enable Winsock TCP/IP Application Interface".

Testing the TCP/IP Setup in Windows

This tests both the AGWPE IP address and the AGWPE port address.

You need to find either the Windows' TELNET.EXE or HyperTerminal program to run this test. I have Windows XP which has only a basic, hard-to-configure TELNET program, so I used HyperTerminal, which comes with versions of Windows before and including XP. HyperTerminal does not come with versions of Windows after XP, so you might find one of these free programs useful:

TerraTerm -

PuTTY -- or

First start AGWPE. Click on the Packet Engine icon on the system tray to bring up the AGWPE menu. On the menu, click on Setup Interfaces. Make sure Enable Winsock TCP/IP Application Interface is checked and the TCP port is 8000. Click OK to close the menu.

Then, click again on the AGWPE icon and then click on About. Notice that the last two lines should say "SocksAPIServer Active" and "SocksAPIConnections 0".

Now open HyperTerminal or TelNet.

Testing TCP/IP using HyperTerminal:

a. Start HyperTerminal. On some systems, it may be found by using the START menu: Programs: Accessories: Communication. Otherwise locate it by doing a Windows file search.

b. From the HyperTerminal menu bar, select File, then New Connection. For the New Connection Name, enter a name of your choice, such as LocalHost 8000

c. On the resulting configuration dialogue window titled "Connect To", go the bottom field labeled "Connect using" and use the drop down menu list to select "TCP/IP (WinSock)".

d. On the resulting dialogue window (also titled "Connect To:"):

For Host Address:  enter either localhost or , if AGWPE is located on the same computer; otherwise enter the network address of the computer where AGWPE is running.

For Port Number: enter the AGWPE default port number 8000 ,unless a different port was selected in the AGWPE menu (Setup Interfaces: WinSock Interface)
then press OK.

e. If HyperTerminal can connect to AGWPE, you will see "Connected" in the lower left of the HyperTerminal window. You can also confirm this in AGWPE: Click on the AGWPE icon for AGWPE menu, and select About. The About screen should now say "SocksAPIConnections 1".

If HyperTerminal can't connect to AGWPE, you will get an error message from HyperTerminal saying "Unable to connect to (IP Address Port Number)..."  This means you need to re-check the configuration steps at the top of this page.

Testing TCP/IP using TELNET

1. Start AGWPE. Click on the Packet Engine icon on the system tray. On the menu, click on Setup Interfaces. Make sure Enable Winsock TCP/IP Application Interface is checked and the TCP port is 8000. Click OK to close the menu.

2. Click again on the AGWPE icon and then click on About. The last two lines should say "SocksAPIServer Active" and "SocksAPIConnections 0".

For Windows XP users:

a.  from the Start button, select run and then enter "cmd" and press the OK button.

b. At the DOS command prompt, enter telnet  8000. If the connection is successful, the DOS box's title bar will change to Telnet  If the connection to that port was unsuccessful, the Telnet window would report the "Connect failed".

c. If the connection was successful, click the Packet Engine icon again, and select About. It should now say "SocksAPIConnections 1" indicating that the TCP/IP connection to AGWPE is working.

d.  Close the Telnet window and the About window should then say "SocksAPIConnections 0".

For Pre-XP Users

I'm not sure exactly how Telnet works on other versions of Windows, but this method was reported to me for Windows 95. This won't work for Windows XP:

a. Run the Win95 Telnet program, TELNET.EXE. It's usually in the main Windows folder (or perhaps Windows/System32).

b. From the menu, select Connect, Remote System; then Host Name: , Port: 8000 (type 8000 over the menu choices); Term Type: VT100 

c. If the program title bar changes from Telnet - [None] to Telnet -, then everything is fine. TCP/IP is working in Windows. If instead you get a message "Could not open a connection to",  then there's something wrong with your Windows TCP/IP set-up. Review the steps at the top of this page.

d. Click the Packet Engine icon again, and select About. It should now say "SocksAPIConnections 1". TCP/IP is working in AGWPE.

e. Go back to In Telnet. Select  Connect, then Disconnect, and close the program. Another check on SocksAPIConnections in AGWPE should show 0."

Last Updated:


Top of page