1. 4001897A.exe Driver
2. atphoust.txt File Contents

atphoust.txt Driver File Contents (4001897A.exe)

                          Houston Diagnostics Setup

Date:         23 October 1998
Revision:     B
Notes:        Includes WANLinks for NT driver in distribution
Requirements: NT 4.0 system, Service Pack 3 (Server or Workstation)
              Minimum of four free PCI slots
Limitations:  Daughter Board S/N does not work properly
              Reduced packet size for data transfer

***** Copy Program Files *****

1. Create Directory (i.e. HoustonTest)
2. Copy all files from root of CD directory
3. Copy DxbMgt.dll to %SystemRoot%\System32
4. From File Manager, create a shortcut for ProductionTest.exe
   - Name should be "Houston Test"
   - Working directory is that created in step 1
5. From Explorer, create a shortcut for FlashWriter.exe
   - Name should be "Flash Writer"
   - Working directory is that created in step 1

***** Procure Binary Files (boot and POST) *****

1. From Engineering Services, retrieve the following files:
   - 82000360_?.bin         - DigiBoot
   - 82000361_?.bin         - IbmBoot
   - 82000362_?.bin         - POST
   Where "?" is the latest revision
2. Copy bins to test directory (the one created in the "Copy Program Files" step)
3. Remove existing down rev bins
4. With Notepad.exe, edit the file: %SystemRoot%\FlashWriter.INI
5. Modify the filenames of the bins to reflect the proper revision
6. Save the file

NOTES: If installing for the first time, you will need to create the file FlashWriter.ini
You may use the following text (this is for revision A of the bins):

[FlashBins]
DigiBoot=82000360_A.bin
IbmBoot=82000361_A.bin
POST=82000362_A.bin

Note that these bins are under ECO control and may require periodic updates. See the related ECO for official disposition of these bins. This rev of the flash writing program defaults to revision A of the bins. It will be necessary to update the registry to use the new filename (since it includes a revision letter).

***** Driver Setup *****

1. Install Adapters
    - Houston + daughter
    - Four boards in host

2. Install Driver
    - Boot NT
    - Launch Control Panel
    - Network | Install Adapter | Have Disk
    - Run setup four times to install all four adapters

3. Disable ISDN and ASYN drivers
    - Control Panel | Devices
    - Set "Digi ASYN Driver" to Manual
    - Set "Digi ISDN Driver" to Manual
    - Ensure that "Digi DataFire RAS Driver" is set to Automatic

4. Disable Driver Config
    - Open Registry Editor
    - Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DigiDxbX\Parameters
        (Where X is the instance number for the first adapter)
    - Set the value: SkipConfig to 0x1
         If the value: SkipConfig is not present, add a DWORD value by this name
    - Repeat for the remaining adapter instances (DigiDxb2, 3, 4)

5. Verify Driver Install
    - Reboot NT
    - Ensure that the green LEDs are flashing for all ports
      (Note: It is OK to have the yellow LEDs flashing in addition to green)
    - Ensure that the event log reports no errors

***** Test Procedure *****

Program Flash

1. Install Houston adapters in the host PC
   - Note that the S/N bar code sticker must be applied
2. Boot NT
3. Invoke "Houston Flash Writer"
4. Select the "Program Both" radio button
5. Select the "Digi Channel" radio button
6. Click the button [Write Flash]
7. When prompted, scan serial number barcode from Houston main board
8. When prompted, scan serial number from Houston daughter board
9. When prompted, enter the board revision, click OK to accept the default
10. Repeat steps 7-9 for each adapter
11. Ensure that the flash procedure is successful (Success! is displayed)
   (Note that this is a 60+ second operation per board)
12. Shutdown the PC

NOTE: For IBM OEM product, select "IBM OEM" radio button in step 5. You will be prompted to scan additional labels (11S IBM label) for IBM OEM product. The Daughterboard will not be scanned in this case.


Verify Flash Programming

1. Run PAR-POST.EXE to verify that the boot and POST run correctly
2. Select 'V' from PAR-POST.EXE to verify that the VPD is correct
3. Press 'ESC' and repeat the 'V' selection for all adapters

Functional Test

1. Install one to four Houston adapters in the host PC
   - Note that the boards must be flashed and hard booted prior to testing
     (Do not flash and run a board during the same boot)
2. Boot NT
3. Ensure that the LEDs near the port connectors flash green during boot.
4. Invoke 'Houston Production Test'
5. Ensure 'Production Test' radio button is selected
6. Click 'Go' from the toolbar
7. Allow test to run to completion
8. Verify which boards have completed the test successfully
   - Pass fail information is tied to each board's serial number
9. Tag non-conforming product


***** Modifying Registry Entries *****

It may be necessary to modify Registry configuration settings for the test bed.

 - Test Bed Configuration Changes -

1. Run the Registry Editor
    - Launch regedt32.exe or regedit.exe
2. Open the following key:
    - HKEY_CURRENT_USER
        Software
        Digi Internaional Production Test Software
        Houston Test

 - If Fireberd firmware changes -
   Under the "Fireberd" key, open the value:
       IdnResponse
       Modify the string to reflect the current firmware revision
       Example: "Telecommunications Techniques Corporation,Fireberd 6000,0,R"
       (replace the 0,R in the string with the current firmware revision of the Fireberd)

 - If the Fireberd is connected to a different com port -
   Under the "Fireberd" key, open the value:
       FireberdComPort
       Modify the string to reflect the com port name the Fireberd is attached to.
       Example: "COM2"

 - If a different dumpfile name is desired -
   Under the "ErrorReporting" key, open the value:
       DumpFile
       Modify the string to reflect the name and path of the new dumpfile

 - If a different number of allowed burnin errors are desired -
   Under the "ErrorReporting" key, open the value:
       MaxFailures
       Modify the number to reflect the new failure limit (default is 5)

 - If the Switchbox is connected to a different parallel port -
   Under the "SwitchBox" key, open the value:
       SwitchBoxPort
       Modify the string to reflect the parallel port name the Switchbox is attached to
       Example: "LPT1"

NOTES:
This release contains a workaround for E1 Jitter testing:
If the Fireberd is incapable of performing Jitter analysis, modify the following;
   Under the "JitterTest" key, open the value:
   UseJitterMask
   Modify this to be 0 (zero) to inhibit the Jitter modulation, set to 1 (one) to enable
   (1 is the default setting)