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

AGWPE's Suite of Companion Programs

George, SV2AGW, the AGWPE author, has written several packet programs that will work with AGWPE. You can download all of them from

These programs are perfect for testing or troubleshooting AGWPE, since they are practically guaranteed to work with AGWPE. Other than entering your personal info (e.g. callsign, etc), you don't need to make any special setting to interface with AGWPE; they should work 'as is' with AGWPE.

  • AGW MONITOR - a program that simply displays incoming packets; it doesn't transmit.(go to the AGW Programs page to download it).

    Hint 1: Even though this program doesn't transmit, it helps to enter your call sign. If you do, any packets with your call sign can be displayed in a different color (default is green)! That includes packets from any of your stations with a different SSID, any digipeated packets, etc.

  • AGW TERMINAL- is a terminal program you can use to receive and send packets. It lets you "connect" to other stations, including a bulletin board (BBS). This is a good program for troubleshooting and testing AGWPE problems since it both receives and transmits.

    There are two versions of AGWTerm. The older version uses the Windows' DDE link to programs. The newer, better version uses the TCP/IP Interface to AGWPE and can be run over a network, where the older version can't. The newer program is called AGWTermTCP   (go to the AGW Programs page to download it).

    You can also configure AGWTerm (TCP/IP version) to connect to an instance of AGWPE running on a different computer on your home network or any where on the internet. See the AGWPE Over a Network page.


  • AGW CLUSTERS - a program that collects and organizes incoming DX spots from a DX Packet Cluster frequency.  AGW Programs

  • AGW UIDIGI - one of the logic functions in a regular TNC is the ability to act as digipeater, i.e. relay packets for other stations. AGWPE does not have this function on its own -- and a TNC's ability to do this is lost when AGWPE puts the TNC in KISS mode. By running the AGWUIDigi APRS program, you can provide a digipeater function to your station while running other packet programs. In fact, AGWUIDigi has additional "smart" digipeating functions which are not found on most TNCs (go to the AGW Programs page to download it).


  • AGWTracker - an APRS program (  This program is currently a $49 shareware program with a free trial period.


AGWTerm Closes Unexpectedly

  •  I'm trying to run AGWTerm and I get several messages like "Can't start monitorm conversation. Try running first Packet Engine (AGW.EXE)" even though I have started AGWPE!

    You have not yet configured a radio port in AGWPE.
  • I had just made a connection with another station when AGWTerm suddenly closed and I got this error message:  AGWTERM caused an invalid page fault in module WINMM.DLL

    You probably have a Windows sound scheme in effect. When you connected to the other station, Windows played the DING.WAV file. To prevent this from happening, set the Windows' Sound scheme to No Sounds. See the Window Sound Settings page on this site for further advice.

  • I am trying to run AGWTerm and I keep getting a "GDI File Read Failure". It also happens when I try to run AGWBBS and AGWFWD.

    All of these programs need a corresponding *.SYS file in the directory. For example, to run AGWTerm.exe, you must have the AGWTRM.sys file (not AGWTerm.sys) in the same directory. For AGWBBS and AGWFWD you need the agwbbs.sys file. The *.sys file is included with the main program file in the program's *.zip file. If necessary, you can re-download the zip file at
  • I've got AGWPE running and I can view the received packets using agwmon and AGWTERM, but I can't get AGWTERM to connect to anything. It acts like it's going to connect but the radio never transmits a packet. However, it *does* transmit a packet when I hit the "Ask QRA" button in the toolbar of AGWTERM.

    There was a problem in some older versions of AGWPE. Make sure you are running the  latest version of AGWPE to fix the problem.
  • I can't enter a long PATH in AGWTermTCP.

    This is program bug. Long PATH setting can't be entered on screen and are altered. Same is true if you enter path in .*.ini file. For example, APRS,WIDE,WIDE goes out as "To APRS-9" in AGWTermTCP.
  • I'm seeing two report of every packet in AGWTerm; one preceded by a 1: and one by a 2:.

    You have AGWPE set for Dual Port mode. Change it to Single Port and delete the appropriate port.ini file; for example, if it's port 2 that you want to delete, delete port1.ini (in other words, a number one less than the port number).
  • My AGWTerm has been working fine, but for some reason now when I click Properties, I get "agwterminal.exe has generated errors and will be closed by windows. I have reloaded it and it does the same thing!

    Delete the agwterm.ini file, then restart and reconfigure AGWTerm.

Return to the "Compatible Programs" page

Last Updated:


Top of page