The classic IRQ trap for packet radio on a vintage system revolves around the serial mouse. Since standard 90s systems typically run a serial mouse on COM1 (IRQ 4), attempting to install your Terminal Node Controller (TNC) on COM3 will trigger an immediate hardware lockup the moment the TNC transmits, because COM3 inherently shares IRQ 4.

To safely run a TNC alongside a serial mouse, you must isolate the TNC on COM2 (IRQ 3). Here is how to lock that configuration in at both the hardware and operating system levels, configure UI-View32 for Automatic Packet Reporting System (APRS) tracking, and integrate high-resolution maps.

Part 1: Hardware and OS Configuration

Prerequisite: Configure the Motherboard BIOS

Before booting into Windows, you must ensure the motherboard is explicitly assigning the correct resources to your physical serial port.

1. Restart the machine and press the designated key (usually DEL or F2 on mid-90s boards like the PD440FX) to enter the BIOS setup.
2. Navigate to the Integrated Peripherals or I/O Configuration menu.
3. Locate the Onboard Serial Port 2 setting and explicitly set it to address 2F8 and IRQ 3.
4. Save and exit the BIOS.

• Verification: The BIOS saves successfully and the system proceeds to boot without stalling at the POST screen.

Step 1: Establish the Physical Connection

1. With the computer powered off, connect a standard straight-through RS-232 serial cable (typically DB9 on the PC side to DB25 on the TNC side) to the physical COM2 port on the back of the computer.
2. Power on the TNC, then boot the computer.

• Verification: The power LED on the TNC illuminates, and the computer boots fully into the Windows 95 desktop.

Step 2: Lock COM2 Resources in Device Manager

Windows 95 Plug and Play can sometimes dynamically reassign resources. We need to lock COM2 down to our BIOS settings.

1. Right-click My Computer, select Properties, and open the Device Manager tab.
2. Expand Ports (COM & LPT), right-click Communications Port (COM2), and select Properties.
3. Under the Resources tab, uncheck “Use automatic settings”.
4. Ensure the Basic Configuration matches Input/Output Range 02F8-02FF and Interrupt Request 03.

• Verification: The Conflicting Device List at the bottom of the window explicitly reads “No conflicts.”

Step 3: Configure HyperTerminal for Serial Communication

Before setting up dedicated packet software, verify the raw serial connection using the built-in terminal emulator.

1. Navigate to Start -> Programs -> Accessories -> HyperTerminal.
2. Open Hypertrm.exe and name the new connection “Packet TNC”.
3. Under “Connect using”, select Direct to Com 2.
4. Set the port settings to match your specific TNC’s default serial baud rate (typically 9600 or 1200 for Kantronics, AEA, or MFJ units), 8 Data bits, None Parity, 1 Stop bit, and Hardware Flow Control.

• Verification: The HyperTerminal window opens with a blinking cursor, and the connection timer in the bottom left corner begins counting up.

Step 4: Initialize the TNC Command Prompt

1. Click inside the blank HyperTerminal window and press the Enter key one to three times. This allows the TNC’s autobaud routine to detect and lock onto your baud rate.
2. Note: If you see garbage characters, the baud rate in HyperTerminal is mismatched. Disconnect, change the baud rate in the port settings, and try again.

• Verification: The TNC responds by printing its firmware version header on the screen, followed by the standard cmd: prompt, indicating a successful two-way data link.

Part 2: UI-View32 APRS Setup

UI-View32 is the gold standard for 32-bit Windows APRS tracking, but it requires exclusive access to the COM port.

Step 5: Freeing the COM Port (Crucial)

Windows 95 does not allow multiple applications to share a COM port. If HyperTerminal is still holding the port open, UI-View32 will crash or throw an “Unable to open Com port” error.

1. Click the “Disconnect” icon in HyperTerminal (the phone hanging up).
2. Close the HyperTerminal application completely.

• Verification: HyperTerminal is no longer running in the Windows 95 taskbar.

Step 6: UI-View32 Comms Setup

1. Launch UI-View32. (Enter registration details if this is your first time booting).
2. On the top menu bar, click Setup -> Comms Setup.
3. Set the Port to COM 2.
4. Set the Baud Rate to match the successful rate you found in HyperTerminal (e.g., 9600).
5. Select your specific hardware in the TNC Type drop-down menu (e.g., Kantronics, TNC2, or CMD/CON for generic Hayes-compatible).
6. Click OK.

• Verification: Watch the “Terminal” window inside UI-View32. You should see the software automatically send the initialization strings to the TNC to put it into KISS or Converse mode.

Step 7: UI-View32 Station Setup

Now that the TNC is communicating, you must format your outgoing APRS beacons.

1. Click Setup -> Station Setup.
2. Callsign: Enter your callsign with an appropriate SSID (e.g., W4DXR-1 for a primary home station).
3. Latitude / Longitude: Enter your exact coordinates (e.g., 31.1023N and 085.5891W for the Slocomb area). UI-View32 requires the format DD.MM.SSN / DDD.MM.SSW depending on your settings, so check the input mask carefully.
4. Unproto port: Set to 1.
5. Unproto address: Use the modern New-N paradigm path: APRS,WIDE1-1,WIDE2-1.
6. Beacon text: Enter a brief description (e.g., Vintage Win95 Packet Node).
7. Select an appropriate UI-View Symbol (like a House or a PC).
8. Click OK.

• Verification: Click Action -> Send Beacon. The TNC’s PTT (Push-To-Talk) and TX LEDs should briefly illuminate, and your radio should transmit a short burst of packet data. As local stations beacon back, their icons will automatically populate on the UI-View32 map.

Part 3: Installing High-Resolution Local Maps

Out of the box, UI-View32 only includes very basic, zoomed-out continental maps. To see local stations around your area, you will need to add calibrated high-resolution maps. There are two primary ways to do this in a vintage Windows 95 environment.

Method 1: The Static Map Image & .inf File

UI-View32 reads standard image files (.gif, .bmp, or .jpg) and overlays GPS telemetry on them by referencing a companion text file (the .inf file). Inside the .inf file are the geographical coordinates of the upper left and lower right corners of the map.

1. Obtain a Map Image: Capture or download a local street-level map image of Houston County or the Slocomb area. Save it as slocomb.gif or slocomb.bmp.
2. Determine the Coordinates: You must know the exact latitude and longitude of the Top-Left corner and the Bottom-Right corner of the image. UI-View32 utilizes Degrees, Minutes, and Seconds for this.
3. The Drag-and-Drop Method:
   • Open UI-View32.
   • Open Windows Explorer and drag your slocomb.gif file directly onto the UI-View32 map window.
   • UI-View32 will automatically open the “Create An INF File” dialog.
   • Enter the Top-Left and Bottom-Right coordinates, give the map a title, and click Save.
4. Manual INF Method: Alternatively, place slocomb.gif in the C:\Program Files\UI-View32\MAPS folder. Open Notepad and create a file named slocomb.inf in the same folder with three lines:

   31.10.05N, 085.37.15W
   30.59.30N, 085.30.10W
   Slocomb Local Area
   

5. In UI-View32, click Map -> Refresh Map List, then go to Map -> Load a Map to select your new local map.

• Verification: The map image appears on screen with your station symbol correctly positioned relative to local roads and landmarks.

Method 2: Precision Mapping (The Vintage Power-User Solution)

If you want seamless, zoomable, street-level mapping of the entire USA without manually calibrating individual GIFs, the ultimate 1990s/2000s solution was Precision Mapping by UnderTow Software.

To support Precision Mapping, UI-View32 uses a plug-in map server-called PMapServer-that integrates seamlessly into the program.

• You must first install the base UI-View32 application.
• Next, install a retail copy of Precision Mapping Streets (V5, V6, or V7 were common for this era).
• Finally, install the matching PMapServer plugin. Precision Mapping Streets 5.0 requires PMapServer, while version 6.0 requires PMapServer6.

Once installed, PMapServer replaces the static image engine.

• Verification: The standard UI-View32 map window is replaced with the PMap interface, allowing dynamic panning, zooming, and street searches directly inside your vintage Windows 95 environment.