Page
4-6
Chapter Four
Eagle TX Series AMOS Based Terminal Server Technical Manual, Rev. 01
the terminal server will probably not re-boot properly. You must perform a successful Flashcard update
to ensure future functionality of the terminal server.
Flashcard Recovery
In the unlikely event that the data programmed into the Flashcard becomes corrupted, the terminal server
will probably not start up properly when power is applied or the reset button is pressed. To avoid the
inconvenience of sending the terminal server in for service, the system is provided with three different
methods to get the terminal server into a bootable condition. These are:
1. Perform a cold boot with an XMODEM upload of the BOOT.EMG (emergency boot file),
which has been provided on floppy. Then update with a full system.
2. Download a 4MB image file backup of your current operating environment.
3. Replace the flashcard with a known good spare.
Option #1 - XMODEM Cold BOOT
An emergency boot file (BT100.EMG for Eagle 100TX; BT450.EMG for Eagle 450TX) file has been
provided on a floppy with your terminal server. This file needs to be put on a PC near the terminal server,
or loaded onto the hard disk of a local Alpha Micro host computer system. This file can then be
downloaded to the terminal server via port 0 at 19200 baud with XMODEM protocol. To use this feature
you must configure the CMOS set up for the alternate boot device to be XMODEM and save and exit
CMOS. Then use a modem package like VersiComm or AutoLog to send the emergency boot file to the
terminal server. This file can be downloaded from ftp.alphamicro.com if your floppy is not available. See
the terminal server CMOS set up information earlier in this chapter for details of the CMOS set up
procedure.
In order to download the emergency boot file to the terminal server, make sure the following
items have been taken into account:
1.
CMOS set up should be configured so that Xmodem has been selected as the Secondary boot
device type. Don’t forget to save the new CMOS settings.
2.
If the emergency boot file is on your local PC, make sure you connect port 0 of the terminal
server directly to the COM port on your local PC. See Appendix A for cabling details. From
your local PC, you can then use Windows HyperTerminal to transfer the file using Xmodem
protocol to the terminal server.
3.
If the emergency boot file is on your Alpha Micro host, make sure that you connect port 0 of
the terminal server directly to an available port on the host. See Appendix A for cabling
details. You can then use either VersiCOMM or AUTLOG to transfer the file directly to the
terminal server using Xmodem protocol.
Once the terminal server has finished downloading the emergency boot file, it will boot up in a minimal
operating environment. This configuration has a VDK RAM disk initialized. Additionally, TCP/IP is set
up with BOOTPC running. You now have two choices in order to fully restore the software to your
