# HamConnect-Amiga hardware profiles

HamConnect separates “recognized” from “physically validated.” A profile can
identify a driver and generate correct configuration without claiming that a
specific card revision has passed real-hardware testing.

## Bundled profiles

| Hardware | Driver | Transport | Installer behavior |
|---|---|---|---|
| PiStorm/Emu68 WiFiPi | `wifipi.device` | Wi-Fi | Bundled, configures WirelessManager |
| Prism2 PCMCIA | `prism2.device` | Wi-Fi | Bundled with firmware and PCMCIA library |
| NE2000-compatible PCMCIA | `cnet.device` | Ethernet | Bundled |
| 3Com 3C589 PCMCIA | `3c589.device` | Ethernet | Bundled |
| WinUAE/UAE | `uaenet.device` | Virtual Ethernet | Uses emulator-provided driver |

## Importable profiles

The installer checks `PROGDIR:Drivers`, validates the SANA-II device and unit,
and then copies a matching user-supplied driver to `DEVS:Networks`.

- X-Surf / X-Surf-100
- Ariadne / Ariadne II
- A2065
- Plipbox
- ZZ9000
- Hydra
- ENC624J600
- PiStorm SANA-II
- PicoWyfy

## Validation gates

Before a profile is advertised as validated it must pass:

1. Cold boot and driver open.
2. DHCP acquire, renew, release, and reboot recovery.
3. Manual IP, gateway, and DNS.
4. DNS, HTTP, HamNet, and HamChat reachability.
5. One-hour idle connection and reconnect after cable/AP interruption.
6. Install, reinstall, repair, rollback, and uninstall.
7. The 1 MB Chip plus 4 MB Fast memory profile.

Driver binaries that are not redistributable are never placed in the public
bundle.
