John: The way the telnet server within the Altair32 works is that it's activated upon the "first" access of a CPU I/O port by a running program. So, for example, if you are running a program that doesn't interact with any of the console I/O ports (0/1, 20/21 octal), the telnet server will not be activated and any telnet client will bomb out, complaining that no server is found. So, the sequence I use is to run HyperTerm and "disconnect" from the telnet port (UDP port 23 by the way -- the standard telnet port). Then, I run the emulator, attach disks and "boot" CP/M. I run ZoneAlarm, so I get a notification that a telnet server is starting (with a TCP address of 127.0.0.1), so I allow the access then "connect" HyperTerm. If you don't run ZoneAlarm, you just have to guess the timing when connecting. When booting CP/M, it's no more than a few seconds. If you look at the front panel address LEDs, you can "see" that it drops into an idle loop (the address LEDs appear to only reference a tight range of addresses). This is the signal that the CBIOS is waiting for a "live" connection. If you prefer, you can use the built-in Windows Console. That doesn't have the same connection problems as telnet. With telnet, however, you should be able to reach your Altair across a subnet (although I've never tried it). The disks are full with stuff, and there certainly should be more than 2-3 files. The CP/M 2.2 disk probably has 25 files on it. Rich