Copyright: ® Ed Kushner


Help Contents
Contents

ALTServer Help

Monthly Update - April, 96

Product History

Errata

General Product Information

Technical Product Summary


Monthly Update - April, 96

Updated Product History

Updated Errata Section

Updated Qualified Memory Lists (DRAM & SRAM)

Updated Frequently Asked Question (FAQ) section


Product History

ECOs - Board - April, 96

ECOs - Software - April, 96

ECO's - Columbus System - April, 96

ECO's - MG5000 System - April, 96

Baseboard revision summary -  April, 96

Baseboard revision details  April, 96

System revision summary -April, 96


ECOs - Board - April, 96

ALTSERVER BOARD LEVEL CHANGES - Implemented and Projected April, 96

Related Topics:

New Pentium 133 Mhz Stepping - Class III

Riser Card Changes - Class II

New I/O riser card baseboard Connector - Class III

New PCEB Stepping - Class I

Cache module part number change - Class III

ALTServer Buffer Change - Class I

INCA Stepping Change - Class Il


New Pentium 133 Mhz Stepping - Class III

Current Implementation Date: 5/96

ECO# 5529143

New C-0 stepping of 133 Mhz Pentium CPU.  The new stepping fixes several errata.


Riser Card Changes - Class II

Date Implemented: 4/96

1.  Width of critical dimension increased by .006" to address worst case mechanical alignment with connector.

2.  Square corner was replaced with diagonal 'ramp' to cause board to self-align with connector as board is inserted.

ECO#  5525781


New I/O riser card baseboard Connector - Class III

Date Implemented: 4/96

ECO #5526204

The I/O riser card baseboard connector changed to one which is less tensile and has stronger retainers. No new compatibility issues are introduced using this connector. This new connector works with -002 and -003 riser cards.


New PCEB Stepping - Class I
New PCEB Stepping − Class I

Date Implemented: 1/96

ECO# 5525602

The PCEB changed from -A2 stepping to the -B1.  This enables the SMI if in 120 or 133Mhz Dual processing mode with BIOS 1.00.15 or greater.  This is reflected in a board PBA number ending in -302 or greater (e.g. 630958-302).


Cache module part number change - Class III
Cache module part number change − Class III

Date Implemented: 1/96

ECO# 5526581

Intel's internal part numbers for the second level cache modules changed.  This change was implemented in order to allow better internal tracking of what processor speeds each qualified cache module supports.


ALTServer Buffer Change - Class I
ALTServer Buffer Change − Class I

Date Implemented: 3/96

ECO# 5527592

The ALTServer PBA changed to the 74ALTS245 in replacement of the 74F245 buffers.


INCA Stepping Change - Class Il
INCA Stepping Change − Class Il

Date Implemented: 3/96

ECO# 5527592

New stepping on INCA. Added clamp diode to input lines to modify the diode kickback voltage, minimize signal reflections


ECOs - Software - April, 96

ALTSERVER SOFTWARE LEVEL CHANGES  - Implemented and Projected April, 96

Related Topics:

New Country Kit - Class II

New version of Testview Diagnostics - Class II

New Country Kit - Class II

New Country Kit - Class II

BIOS Fixes - Class I

SCU Plug and Play Fix - Class I


ALTServer Help - ECOs - Software - April, 96 - New Country Kit - Class II
New Country Kit − Class II

Current Implementation Date: 6/96

ECO# 5529446

A new country kit will be included with all systems.  The SCU included in the kit will change to version 3.4 OVL 1.3. the testview diagnostics program will change to version 3.37.

Old Part Number	New Part Number	Description
650430-003	650430-004	Country Kit Base #
652764-002	652764-002	SCU 3.4 / OVL 1.30
642279-004 / 642280-004	654852-001	LDSM, version 1.3
650504-001	TBD	EZ-SCSI LITE, New version
652411-001	657974-001	Diagnostics, version 3.37
652413-001	657977-001	Diagnostics, version 3.37, help files, disk 1
	657978-001	Diagnostics, version 3.37, help files, disk 2


New version of Testview Diagnostics - Class II

Current Implementation Date: 5/96

ECO# 5529446

New version of the Testview diagnostics software will be cut into the product. Early copies of these drivers and release notes are available now for customer evaluation.

Old Diagnostics: 3.31	New version: 3.37


ALTServer Help - ECOs - Software - April, 96 - New Country Kit - Class II
New Country Kit − Class II

Date Implemented: 1/96

ECO# 5526526

A new country kit included with all systems.  The Platform guide revision will change, SCSI drivers, LSC version and the SCU included in the kit will change to version 3.21 / OVL 1.01 (required by BIOS 1.00.15.BI0).

Old Part Number	New Part Number	Description
620324-008	650430-001	Country Kit Base #
644121-001	650513-001	SCU 3.21 / OVL 1.01
640814-001	642011-001	Adaptec 78xx Drvr - Netware v1.2s2
642279-002	642279-004	LSC v1.12 Disk 1/2
642280-002	642280-004	LSC v1.12 Disk 2/2
630547-004	630547-005	Platform Guide


ALTServer Help - ECOs - Software - April, 96 - New Country Kit - Class II
New Country Kit − Class II

Date Implemented: 3/96

A new country kit will be included with all systems.  The SCU included in the kit will change to version 3.3 / OVL 1.20 (required by Feb. BIOS release).


BIOS Fixes - Class I
BIOS Fixes − Class I

Date Implemented: 3/96

A new BIOS was cut in to fix the following errata.

Detect Fab 6 vs. 7 using A/D channel 6 (0-based) to control the following:

a. GAT Mode - If fab 7, cannot allow GAT mode because it's using  an external arbiter.

b. SMM - If fab 6, cannot allow SMIs to be enabled because SMI pullup is missing.

PnP ISA card fix to allow PnP ISA cards' resources to be changed in the SCU without causing an extra record in the ESCD to be created.  This fix requires new SCU 3.30/OVL 1.02 or greater also.

1MB Hole Fix

a. Fixed CMOS locations 34h-35h to report the correct amount  of extended memory based on enable status of 1MB hole.

b. Fixed INT 15 Function DA88 to report the correct amount of  extended memory by subtracting out the 1MB hole if it is enabled.


SCU Plug and Play Fix - Class I
SCU Plug and Play Fix − Class I

Date Implemented:  3/96

The SCU version 3.3, Overlay 1.20  fixed issues with Plug andf Play (PnP) ISA cards.  Changes since previous release:

1) PnP code updates to work with newest BIOSes.  Previously, BIOS would not honor PnP resource requests.  New BIOSes will honor requests but must have some fixes in SCU.  Unfortunately, this fix makes this particular SCU Beta not work with older BIOSes.

2) There is a warning when trying to restore a CMOS image image from an older BIOS than what is currently in the system.

3) A couple of references to the 'ECU' were removed

4) The global resource map uses a PnP card's name instead of a generic "Main Function" string when describing resources.

5) There is a warning if no resources are reserved for standard video BIOS.

6) The maximum amperage was increased according to the Hardware EPS.

7) There is a "Toggle Temperature" key in the Volt/Temp Limits window to allow the user to toggle between entering temperatures in Celcius and Kelvin.

8) The Password dialog box title is "New Password" when there is no valid password and "Change Password" when there is a valid password.


ECO's - Columbus System - April, 96

COLUMBUS SYSTEM / CHASSIS CHANGES - Implemented and Projected April, 96

Related Topics:

Fan Sense Jumper - Class I

Front Panel Board update - Class II

New Front Panel Switch buttons - Class III


Fan Sense Jumper - Class I
Fan Sense Jumper − Class I

Date Implemented: 1/96

ECO# 5526645B

   Some Columbus systems with Altair Fab 7 baseboards were shipped without the "fan sense jumper" installed.  The cooling fan in the system will not work properly without this jumper installed on the unused fan connector on the baseboad. Please contact your Intel field sales representative.


Front Panel Board update - Class II
Front Panel Board update − Class II

Date Implemented: 1/96

ECO# 5526078

New fab to bury blue wires and remove etch cut on existing Front Panel PBA.

Old PBA #	634425-101	New PBA #	634425-201


New Front Panel Switch buttons - Class III
New Front Panel Switch buttons − Class III

Date Implemented: 3/96

ECO# 5525301

New switch buttons are being implemented to remove requirement of the black switch caps on the front panel board that are underneath the existing buttons.  These buttons will be identical to the old in function and appearance and are attached to the bezel.


ECO's - MG5000 System - April, 96

MAGELLAN  SYSTEM / CHASSIS CHANGES - Projected April, 96

Related Topics:

None Planned


None Planned


Baseboard revision summary -  April, 96

Product	PBA	Rev.	BIOS Level	CPU	SCU	Suggested BIOS/SCU	Date	Release Notes
	622280	-001	0.01.01.BI0	90	3.03, 0.08	same	8/94	Unsupported, FAB 2
		-002	0.01.01.BI0	90	3.03, 0.08	same	9/94	Unsupported, FAB 2
		-003	0.01.01.BI0	90	3.03, 0.08	same	10/94	Unsupported, FAB 2
	630080	-005	0.00.01.BI0	90	3.03, 0.08	same	12/94	Unsupported, FAB 3A
B1F100A2M0	633100	-001	0.00.01.BI0	100	3.03, 0.08	1.00.17.BI0 / 3.3, 1.20	1/95	Unsupported, FAB 4
		-002	0.04.01.BI0	100	3.03, 0.08	1.00.17.BI0 / 3.3, 1.20	2/95	Unsupported, FAB 4
		-003	0.04.01.BI0	100	3.03, 0.08	1.00.17.BI0 / 3.3, 1.20	3/95	Unsupported, FAB 4
		-004	1.00.01.BI0	100	3.04, 0.18	1.00.17.BI0 / 3.3, 1.20	4/95	Production Release, FAB 4
		-005	1.00.07.BI0	100	3.08, 0.31	same	5/95	Add Parity Support, FAB 4
		-007	1.00.07.BI0	100	3.08, 0.31	same	6/95	Correct 75Mhz boot issue.
BRD1F90C0M0	634000	-001	0.04.01.BI0	90	3.03, 0.08	1.00.17.BI0 / 3.3, 1.20	3/95	Unsupported, FAB 4
	634335	-001	0.04.01.BI0	90	3.03, 0.08	1.00.17.BI0 / 3.3, 1.20	3/95	Unsupported, FAB 4
		-002	1.00.01.BI0	90	3.04, 0.18	1.00.17.BI0 / 3.3, 1.20	4/95	Production Release, FAB 4
		-003	1.00.07.BI0	90	3.08, 0.31	same	5/95	Add Parity Support, FAB 4
		-005	1.00.07.BI0	90	3.08, 0.31	same	6/95	Correct 75Mhz boot issue.
BRD1F90C0M0	630958	-001	0.04.01.BI0	N/A	3.03, 0.08	1.00.17.BI0 / 3.3, 1.20	3/95	Unsupported, FAB 4
B1F100A2M0		-002	1.00.01.BI0	N/A	3.04, 0.18	1.00.17.BI0 / 3.3, 1.20	4/95	Production Release, FAB 4
BRD1F100C0M0		-003	1.00.07.BI0	N/A	3.08, 0.31	1.00.17.BI0 / 3.3, 1.20	5/95	Add Parity Support, FAB 4
B1FNOC0M0		-005	1.00.07.BI0	N/A	3.08, 0.31	1.00.17.BI0 / 3.3, 1.20	6/95	Correct 75Mhz boot issue.
B1F100A2M16		-201	1.00.07.BI0	N/A	3.08, 0.31	1.00.17.BI0 / 3.3, 1.20	6/95	Production Release, FAB 6
		-202	1.00.07.BI0	N/A	3.08, 0.31	1.00.17.BI0 / 3.3, 1.20	6/95	Correct 75Mhz boot issue.
		-203	1.00.07.BI0	N/A	3.08, 0.31	1.00.17.BI0 / 3.3, 1.20	6/95	New keyboard controller
		-204	1.00.11.BI0	N/A	3.11, 0.39	1.00.17.BI0 / 3.3, 1.20	9/95	New BIOS
		-205	1.00.11.BI0	N/A	3.11, 0.39	1.00.17.BI0 / 3.3, 1.20	10/95	Rev. C SCSI controller.
		-206	1.00.11.BI0	N/A	3.11, 0.39	1.00.17.BI0 / 3.3, 1.20	11/95	Rev. D Cirrus Video
		-207	1.00.15.BI0	N/A	3.21,1.01	1.00.17.BI0 / 3.3, 1.20	12/95	New BIOS
		-208	1.00.17.BI0	N/A	3.3, 1.20	same	2/96	New BIOS
	641332	-201	1.00.07.BI0	N/A	3.08, 0.31	1.00.17.BI0 / 3.3, 1.20	7/95	Correct fan sense circuit, FAB 6 for MG5F*
		-202	1.00.11.BI0	N/A	3.11, 0.39	1.00.17.BI0 / 3.3, 1.20	10/95	New BIOS
		-203	1.00.15.BI0	N/A	3.21, 1.01	1.00.17.BI0 / 3.3, 1.20	12/95	New BIOS, Rev. C SCSI cont., Rev. D video cont.
		-204	1.00.17.BI0	N/A	3.3, 1.20	same	2/96	New BIOS
B1FNOC0M0B B1F133A2M0B	630958	-301	1.00.12.BI0	N/A	3.11, 0.39	1.00.17.BI0 / 3.3, 1.20	10/95	Production Release, FAB 7, A2 PCEB, Preprod. BIOS
B1F100A2M0B B1F75A2M0B		-302	1.00.15.BIO	N/A	3.21, 1.01	same	11/95	New BIOS, Rev. D Cirrus Video
		-303	1.00.15.BIO	N/A	3.21, 1.01	same	2/96	New I/O riser connector.
		-304	1.00.17.BI0	N/A	3.3, 1.20	same	2/96	New BIOS
	648428	-301	1.00.12.BI0	N/A	3.11, 0.39	1.00.17.BI0 / 3.3, 1.20	12/95	FAB 7, B1 PCEB stepping Preproduction BIOS
		-302	1.00.15.BIO	N/A	3.21, 1.01	same	12/95	New BIOS, Rev. D Cirrus Video
		-303	1.00.15.BIO	N/A	3.21, 1.01	same	2/96	New I/O riser connector.
		-304	1.00.17.BIO	N/A	3.3, 1.20	same	2/96	New BIOS
		-321	1.00.17.BI0	N/A	3.3, 1.20	same	3/96	74ALS245 Buffers


Baseboard revision details  April, 96

Fab 3
Date	PBA	PB	Feature/Problem desc	Rewk Summary	ECO #
11/14/94	630080-001	630078-001	Fab 3
			Disable pipelining	remove R383
			A/D converter fixes	change 24 resistors
			Dual processor fix	change five res, 1 wire
Fab 3'
11/28/94	630080-003	630078-002	Fab 3'
			enabled soft reset w/BIOS 14	remove R88 & R90
12/1/94	630080-003		PCMC errata fix	4 wire; 3 lifted legs
			ECO release
12/9/94	630080-004		A/D converter fixes (redo);	change	5520063
			Fix video hang at 100 Mhz	cutin 5430 C step Cirrus
12/23/94	630080-005		Bring performance of C2 Pentiums up to B-5 level	cut one trace
	630080-005C		enable pipelining for C2	add a 0 ohm resistor at R383
			Fix SCSI chip issue	change from 40 to 42 mhz osc
			move from 90 to 100 Mhz	move two jumpers for 100 Mhz operation
	630060-006		PCI scan rework		552059
Fab 4
		633513-001	fab4 90
1/16/95			90 Mhz
			bring C2 performance up to B-5 level	cut one trace
			changes for chassis intruder detection & fan sensor switch, and front panel switch; change to latched cache simm socket; new KB controller v1.22	one cut traces; one blue wire, change six res values,add one jumper	5520391
1/30/95	634335-001		PCI scan order rework	3 wires and two cuts	5520702
			fab4 100
1/16/95	633100-001		100 Mhz
			bring C2 performance up to B-5 level	cut one trace
			changes for chassis intruder detection & fab sensor switch; new KB controller	one cut trace; one blue wire, change six res values,add one jumper	5520391
1/30/95	633100-002		PCI scan order rework	3 wires and two cuts	5520702
2/15/95	633100-003		Front Panel fix; change to latched cache simm socket	changed caps	5520702A
3/31/95	632100-004		ECO in  BIOS rel 1.0
4/5/95	633100-005		DRAM parity fix	3 wires; 3 lifted legs	5522198
5/1/95	633100-006		Fixed floppy write protect error (field only)	add one resistor	5522198
5/19/95	633100-007		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
5/19/95	633100-008		Inca reset (field only)	1 wire; 2 lifted legs;1 pal chng	5522850
			Fab 4 std
2/25/95	630958-001		base release includes all changes from 90 and 100 mhz boards	(4 wires and 4 cut traces)
3/31/95	630958-002		BIOS 1.00.01
4/5/95	630958-003		DRAM parity fix	3 wires; 3 lifted legs	5521730
4/21/95	630958-003		BIOS 1.00.04
4/28/95	630958-003		BIOS 1.00.07
5/10/95	630958-004		Fixed floppy write protect error (field only)	add one resistor	5522198
5/19/95	630958-005		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
5/19/95	630958-006		Inca reset (field only)	1 wire; 2 lifted legs;1 pal chng	5522850
			Fab 4 (rev C SCSI)
4/7/95	637768-002		ECO release w/ BIOS  1.00.01
5/10/95	637768-002		change OSC from 42 to 40; c BIOS 1.00.07		5522523
5/10/95	637768-003		Fixed floppy write protect error (field only)	add one resistor	5522198
5/19/95	637768-004		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
5/19/95	637768-005		Inca reset (field only)	1 wire; 2 lifted legs;1 pal chng	5522850
Fab 5
		634449-001	Fab 5 std
3/1/95	634450-001		engr BOM release w/BIOS 1.00.07	cutin 629183-002 and 621981-002 riser cards
3/17/95	630958-101		correct cap values, reduce cap line items	ECO release
4/5/95	630958-102		DRAM parity fix	3 wires; 3 lifted legs	5521730
			Fab 5  (fused tant caps; gold simm skt;  Rev C SCSI)
5/11/95	635123-001		release to sherpa
5/19/95	635123-002		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
Fab 6
		637990-001	Fab 6 std
5/1/95	630958-201		res/cap changes
5/22/95	630958-202		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
6/28/95	630958-203		Cut in V 1.28 KB controller		5523274A
8/29/95	630958-204		BIOS 11		5524136B
10/24/95	630958-205		Rev C SCSI; Cirrus -505 as alt		5525602A
10/30/95	630958-206		Callout only TDK ferrite beads		5525934
12/13/95	630958-206	rev change	new simm connector as alternate		5526204
12/15/95	630958-207		BIOS 15		5526581
			Fab 6 (Rev C SCSI)
5/1/95	630778-201		res/cap changes
5/22/95	637768-202		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
6/28/95	637768-203		Cut in V 1.28 KB controller		5523274
8/29/95	630778-204		BIOS 11		5524136B
10/30/95	630778-205		Callout only TDK ferrite beads & Cirrus -503 rev D		5525934
12/13/95	630778-205	rev change	Add back in CPU warning label; new simm connector as alternate		5526204
12/15/95	630778-205	rev change	New simm connector as alternate		5526581
			Fab 6  (fused tant caps; gold simm skt;  Rev C SCSI)
			res/cap changes-see Brewster
5/22/95	635123-202		Inca reset	1 wire; 2 lifted legs;1 pal chng	5522850
6/28/95	635123-203		Cut in V 1.28 KB controller		5523274A
10/30/95	635123-204		Callout only TDK ferrite beads & Cirrus -503 rev D		5525934
12/13/95	635123-204	rev change	B0 PCEB only
12/15/95	630778-204	rev change	New simm connector as alternate		5526581
			Fab 6 base PBA for Magellan: Std +  fan sense rework
7/17/95	641332-201		new pba	1 wire; res value changes	5523439
8/29/95	641332-202		BIOS 11		5524136B
Fab 7		641325-003	fab 7  std w/ A2 PCEB
9/18/95	630958-301		new fab, rev C SCSI, A2 PCEB & ESC
10/30/95	630958-302		Cirrus -503 rev D; BIOS 15		5525934
12/13/95	630958-303		New Simm socket		5526204
		641325-003	Fab 7  (fused tant caps; gold simm skt;  Rev C SCSI)
9/18/95	635123-301		new fab,  A2 PCEB & ESC
10/24/95	635123-301		fab 7  std w/ B1 PCEB	rev change only	5525602A
10/30/95	635123-302		Cirrus -503 rev D; BIOS 15		5525934
12/13/95	635123-303		New Simm socket		5526204
		641325-003	fab 7  std w/ B1 PCEB
10/24/95	648428-301		created a fab 7 std with B1 PCEB		5525602A
10/30/95	648428-302		Cirrus -503 rev D; BIOS 15		5525934
12/13/95	648428-303		New Simm socket		5526204


System revision summary -April, 96

Product	TA	REV.	Date	Release Notes
C1F75A2M8	637480	-001	5/95	Production Release
		-002	6/95	New front panel PBA
		-003	6/95	New keyboard controller / Fab 6 PBA, adds 133Mhz capability.
		-004	10/95	New front panel PBA
C1F75A2M16	641118	-001	6/95	Production Release
		-002	6/95	New front panel PBA
		-003	6/95	New keyboard controller / Fab 6 PBA, adds 133Mhz capability.
		-004	10/95	New front panel PBA
C1F90A2M16	630253	-001	5/95	Production Release
		-002	6/95	New front panel PBA
		-003	6/95	New keyboard controller / Fab 6 PBA, adds 133Mhz capability.
		-004	10/95	New front panel PBA
C1F100A2M16	641893	-001	7/95	Production Release
		-002	10/95	New front panel PBA
C1F120A2M16	638645	-001	7/95	Production Release
		-002	7/95	New front panel PBA
		-003	7/95	New keyboard controller / Fab 6 PBA, adds 133Mhz capability.
		-004	10/95	New front panel PBA
C1F75A2M8A2	649677	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, A2 PCEB
C1F75A2M16A2	650335	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, A2 PCEB
C1F100A2M16A2	649679	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, A2 PCEB
C1F133A2M16A2	649680	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, A2 PCEB
C1F75A2M8B	646274	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB
C1F75A2M16B	647555	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB
C1F90A2M16B	646466	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB
C1F100A2M16B	646275	-001	12/95	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB
		-002	1/96	Fan Sense Jumper
C1F120A2M16B	645564	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB
C1F133A2M16B	645634	-001	1/96	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB
C1F166B2M16B	650548	-001	2/96	Production Release, FAB 7 PBA, 300W Power Supply, B1 PCEB, Burst cache
MG5F75A2M16	638817	-001	6/95	Production Release
		-002	7/95	Correct fan sense circuit
MG5F100A2M16	636048	-001	6/95	Production Release
		-002	7/95	Correct fan sense circuit
MG5F133A2M16B	646415	-001	1/96	Production Release
		-002	3/96	New BIOS, Country Kit
		-003	5/96	Pentium C-0 Stepping
	202123	-004	5/95	Power Supply - 230 Watt - Production release
		-005	8/95	Lengthened P1 & P2
	628699	-001	11/95	Power Supply - 300 Watt - Production release
	634425	-001	5/95	Front Panel Assembly - Unsupported pre-production
		-002	5/95	Production release
		-003	6/95	Modified to work with LSC software
		-101	10/95	Add power on circuitry
		-201	1/96	Bury blue wires & remove etch cut.


Errata

General

Common to All Operating Systems

Limitations in the BIOS and SCU

Windows NT* 3.5 / 3.51

Windows* 95

Novell* NetWare* 3.12, 4.1x

SCO UNIX

Banyan* Vines* 6.0

Novell UnixWare* 2.x

Solaris*

IBM* OS/2*

Processor Errata as they apply to ALTServer Summary

Processor Errata Details

Known Errata - System

Manual

Closed Errata


General

Board Flex - Rubber bumper under power connectors in non-Intel chassis

Rubber bumper under I/O riser in non-Intel chassis

Installing the Video Memory DRAM

Configuring Multiple EISA/PCI add-in cards

BIOS - Procedure for updating


Board Flex - Rubber bumper under power connectors in non-Intel chassis

CAUTION:  Baseboard damage can occur due to board flex between the power connectors and the corner mounting screw.  This was discovered when the mouse failed on some systems.  Care must be taken when inserting and removing the power connectors.  This same care is also recommended when applying any mechanical force to the baseboard (I/O riser, Adapters, Video DRAM, etc.)   If you are not installing this product in an Intel chassis, add a rubber bumper under the baseboard power connector to eliminate any possibility of flexing the baseboard while installing the power cables.  This stabilizer has been added to Intel Chassises.


Rubber bumper under I/O riser in non-Intel chassis

CAUTION:  If you are not installing this product in an Intel chassis, add a rubber bumper under the I/O riser card connector on the baseboard to eliminate any possibility of flexing the baseboard while installing the riser card.  Make sure you hear the riser card click into place; otherwise the baseboard may be damaged.  A new specification is in progress; all pre-production/evaluation parts will be replaced.


Installing the Video Memory DRAM

! WARNING: Installing the video memory DRAM chip incorrectly in the socket could produce an extremely high Case temperature and destroy the chip and possibly the system board. Do not touch the Video memory chip after such an occurrence until it has been determined the case is not at elevated temperature.


Configuring Multiple EISA/PCI add-in cards

CAUTION: There is a small probability that problems may be encountered when loading a combination of more than five EISA and/or PCI add-in cards in the ALTServer system.  This is due to configuration memory allocation requirements  of .cfg files of some add-in cards.  Unfortunately, it is not possible to predict the configuration memory usage pattern of most EISA add-in boards until the board is actually inserted in the system.  A two-part solution exists for these cases:

•	A "Memory Used" utility included with a special System Configuration Utility to help in determining the amount of memory available for configuring additional EISA add-in cards.

• Φορ τηε ραρε χασεσ ωηερε χονφιγυρατιον μεμορψ ισ εξηαυστεδ (ασ ινδιχατεδ βψ αν ∀Ουτ οφ  Μεμορψ∀ ερρορ μεσσαγε φρομ τηε ΣΧΥ), α σεπαρατε ΣΧΥ ηασ βεεν δεϖελοπεδ.  Τηισ ΣΧΥ, ∀ΟςΛ.λιτε∀, φρεεσ υπ αδδιτιοναλ μεμορψ, βυτ ρεθυιρεσ αν αδδιτιοναλ στεπ ιν χονφιγυρατιον. Ιν τηισ χασε,  α χυστομερ ωουλδ φιρστ ρυν τηε νορμαλ ΣΧΥ ανδ χονφιγυρε τηε βασεβοαρδ/σψστεμ.  Τηεν τηε ∀ΟςΛ.Λιτε∀ ΣΧΥ ωουλδ βε ρυν το χονφιγυρε τηε ΕΙΣΑ χαρδσ.  Α χοπψ οφ τηισ υτιλιτψ ανδ ιτσ ινστρυχτιονσ μαψ βε οβταινεδ φρομ τηε Ιντελ ΒΒΣ.For the rare cases where configuration memory is exhausted (as indicated by an "Out of  Memory" error message from the SCU), a separate SCU has been developed.  This SCU, "OVL.lite", frees up additional memory, but requires an additional step in configuration. In this case,  a customer would first run the normal SCU and configure the baseboard/system.  Then the "OVL.Lite" SCU would be run to configure the EISA cards.  A copy of this utility and its instructions may be obtained from the Intel BBS.


BIOS - Procedure for updating

CAUTION: Special instructions for updating may be required and instructions are noted in the "release.txt" file supplied with the BIOS.  Care must be taken to read this file and follow its directions to ensure proper operation and upgrading.

Get BIOS update from dealer or sales representative; unzip file and copy the FMUP files to a bootable diskette (formatted, DOS 6.22 or later).

To update the BIOS:

1.	Run SCU and save current configuration to a file.

2.	Run <F1> CMOS Setup and note differences from defaults listed in manual.

3.	Turn the server off.

4.	Removal of ISA adapters from system may be necessary if there is an IRQ or I/O conflict with a factory default setting of an embedded feature in the system (e.g. Video or SCSI).  Note slot location of each adapter.

5.	Insert in drive A the bootable diskette that you have just copied the BIOS updates files to.  Turn the server on.  The update process starts automatically following system boot.  Follow the system prompts.

6.	When the update process completes, turn the server off.

7.	Reset CMOS NVRAM.

To reset CMOS NVRAM to factory default values:

1.	Turn the server off.  Move CMOS Clear jumper (J1B) to pins 2-3.

2.	Turn the server on and wait for the message indicating "NVRAM Cleared by Jumper".  This automatically reprograms CMOS NVRAM to default settings.

3.	Turn the server off.  Move the CMOS Clear jumper to pins 1-2.

4.	Turn the server on.

5.	Run <F1> CMOS Setup and restore configuration as per your notes from step 2 of "Updating BIOS" above.

6.	Run SCU to reconfigure the server.  At this point you can use the file saved in step one of "Updating BIOS" above.  Be sure to save changes (SCU step #4) before exiting the SCU.

7.	If you removed ISA adapters during the Updating BIOS procedure, power down system and re-install the adapters in there original slots now.

These instructions are repeated in Resetting CMOS NVRAM to Factory Defaults in the manual shipped with the product.


Common to All Operating Systems

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

Mouse AutoDetect may/may not assign IRQ12 as usable  1929

Factory Default A/D values incorrect for baseboard monitoring 1580

DPT 2122 hangs system with no drives attached. 2043

Fails PCI SIG "P2P Bridge" Test; Can't handle VGA on bridge  2233

Failed using the Sound Blaster IDE configured at secondary IDE 2236

Fails the PCI SIG Expansion ROM test  2349

Custom EISA card not found; reports wrong EISA config  2412

Atapi IDE CD-ROM Drives failed to function   2413

Creative Labs AWE32 sound blaster does not function w/ EISA SCSI  2414

Fails when running the PCI expansion ROM test  2444

Fails Toshiba XM-3501 SCSI CD-ROM  2478

Failed to reserve DMA 5  2528


Mouse AutoDetect may/may not assign IRQ12 as usable  1929

Problem:  On mouse auto detect - if mouse is not present we are not releasing IRQ12. This was found with a DPT card which was auto assigned IRQ12 when mouse was not present and it would hang the adapter.

Resolution:  To be fixed with future release of BIOS.


Factory Default A/D values incorrect for baseboard monitoring 1580

Problem:  Factory default settings for Upper FATAL, UPPER WARNING, LW, LF has incorrect values .

Resolution:  Fixed in BIOS 17, will close when BIOS releases.


DPT 2122 hangs system with no drives attached. 2043

Problem:  Place DPT 2122 SCSI raid controller in any EISA slot. 1a) Clear CMOS 2) Run SCU and configure controller for IRQ 15, BIOS address C8000, disable WD1003, disable floppy 3) Reboot system 4) With a drive attached to the 2122, a floppy disk will boot in drive A With no drive attached to the 2122 the system will hang.

Resolution:  There seems to be a conflict between the dpt bios and the onboard adaptec scsi bios.   Will be fixed in future BIOS.


Fails PCI SIG "P2P Bridge" Test; Can't handle VGA on bridge  2233

Problem:  At PCI Workshop on 9/21/95, the PCI SIG group gave a fail on the P2P Bridge test.

Resolution:  Under investigation, will fix in future BIOS release.


Failed using the Sound Blaster IDE configured at secondary IDE 2236

Problem:  With the Sound Blaster IDE set at Port 170, the primary master drive is then moved to primary slave and a "Drive Not Ready Error" Insert BOOT diskette in A: is received on bootup.

Resolution:  Under investigation.


Fails the PCI SIG Expansion ROM test  2349

Problem:  During 3 card states (0E,0F and 10), the error message "Warning: Option ROM code for Device 0x07 Function 0 on Bus 0x01 was not executed."

Resolution:  Fixed in BIOS 17, will close when BIOS releases.


Custom EISA card not found; reports wrong EISA config  2412

Problem:  The card can be installed, but BIOS can not be "see" it. When the system is booted the system reports wrong EISA configuration; even though, card has been properly configured in SCU.  This custom made card has been designed using EISA specs 3.12.

Resolution:  Under investigation.


Atapi IDE CD-ROM Drives failed to function   2413

Problem:  The system would not boot up in this configuration. Rather than boot off the Micropolis hard drive on the primary IDE port, it would try to boot off the Teac CD-ROM drive connected to the secondary IDE port. Failing in this, it would then give a "Drive not ready" error message.

Resolution:  Fixed in BIOS 17, will close when BIOS releases.  Duplication of 2236.


Creative Labs AWE32 sound blaster does not function w/ EISA SCSI  2414

Problem:  The system would not boot up in this configuration with the Mitsumi CD-ROM attached. When the CT531 CD-ROM and adapter were used the system would boot but no sounds were reproduced when the Windows programs were run. When the tests were run with the CT531 attached to a Creative Labs Value 16 sound card all programs ran correctly.

Resolution:  Under investigation.


Fails when running the PCI expansion ROM test  2444

Problem:   The BIOS is placing an 8K ROM at memory address EA00 which interferes with the execution of a large option ROM during the test.

Resolution:  Under investigation.


Fails Toshiba XM-3501 SCSI CD-ROM  2478

Problem:  While attempting to install the Toshiba XM-3501 (Firmware Rev. HA51215), the onboard 7870 SCSI host adapter, with CQWA542 listed on the chip, failed to boot the XM-3501 attached, the following error message was seen "unexpected SCSI time-out during SCSI inquiry". This problem does not occur when an Adaptec AHA 2940 is used.  All other SCSI CD-ROMs tested with the onboard SCSI host adapter on the baseboard passed as expected including; Toshiba XM-3601, XM-3701, NEC CDR 600, 601, 502, Plextor PX-4CH, 6CH, and the Sony CDU-76S.

Resolution:  Under investigation.


Failed to reserve DMA 5  2528

Problem:  Using Creative Labs ViBRA in SLOT9: IRQ=5, I/O=220/300, DMA=1/5, CS=CT2501-TBQ, BIOS=1.01; or Media Vision Pro Audio Studio in SLOT9: IRQ=5, I/O=220/300, DMA=1/5, CS=MVA508.  The cards listed above would not work when the high DMA setting was at "5". The DOS program "Hexen" worked fine and had clear sound. The card's diagnostic programs allowed the selection of DMA "5". But, under Windows 3.11, the "Rack" program failed to play .WAV files. Instead, an audible squeaking noise was produced. Both the Media Vision and the Creative Labs allowed the selection of DMA "5". Although the Creative Labs Vibra diagnostic programs had passed the selection of DMA "5" for its high DMA, it could not produce the correct sounds when testing "16 Bit Testing " from the menu. The Media Vision diagnostic during install first allowed the selection of DMA "5", but later produced squeaking noises when trying to select the same.

Resolution:  Under investigation


Limitations in the BIOS and SCU

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

Setup screen indicates BIOS v1.00.17 not bootble from SCSI HD  2442

BIOS Setup & SCU differ on Inactivity Timout maximum 2039

SCU appears to allow setting of PCI device memory location.  2057

SCU will allocate C0000 ram buffer for SMC EISA card  2198

SCU: User can not add cards manually from OEM diskette  2414

DPT 2122 hangs system with no drives attached  2472

BIOS does not honor the lock bit for PCI/PnP devices 2890


Setup screen indicates BIOS v1.00.17 not bootble from SCSI HD  2442

Problem:  This BIOS v1.00.17 differ to previous versions. The setup screen shows the boot option from only A: or/and primary IDE.   Previous BIOS versions gave options for boot from A:, the C:; C: only etc.  System will still boot to SCSI if no IDE is attached (as designed), but setup screens are confusing.

Resolution:  Will be fixed in future BIOS release.


BIOS Setup & SCU differ on Inactivity Timout maximum 2039

Problem:  BIOS states  0-255 minutes. SCU states valid values to be 0-127 minutes.  These should be equal.

Resolution:  Actual maximum is 127 minutes.  Will be fixed in future BIOS release.


SCU appears to allow setting of PCI device memory location.  2057

Problem:  SCU resources such as PCI memory locations can be changed while in an SCU session, but this does not affect the location of the devices

Resolution:  Only PCI interrupts and I/O locations can be manually set within the SCU.  Memory locations are not allowed to be set manually under PCI.  The fact that the SCU makes it look like you can change PCI memory locations is a limitation of the SCU.  Plans are in place to have help added to the "resource editing" fields indicating that the BIOS does not honor PCI port/memory requests until this problem is fixed in the BIOS.


SCU will allocate C0000 ram buffer for SMC EISA card  2198

Problem:  SCU overlay 29 will allow the SMC EISA lan adapter to map it's ram buffer to C0000, on top of the video bios.  When the system is rebooted, video is blank. C0000 is the first choice in the SMC's config file.

Resolution: The AMISCU assigns ISA and EISA resources first.  If there is a PCI video card and an EISA adapter that requests C0000 as a resource the EISA card will get the resource because it is scanned by the AMISCU first. This is a problem with the core AMISCU code.  The long-term Resolution is to ""special case"" video cards and give precedence to cards requesting C0000 as video memory. When using the SCU, you must scan each defined device and make sure that is does not request C0000 unless it is a video card. This is ""manual conflict Resolution.""  If the video device is already displaced then CMOS must be cleared before attempting the above.


SCU: User can not add cards manually from OEM diskette  2414

Problem:  There is no way to add cards to the system if the .cfg / .ovl files are on a separate OEM diskette. If the SCU is run off diskette and .cfg / .ovl files are stored on a separate diskette, the SCU provides no means of retrieving those files fo4r a manual load of an adapter card.

Resoultion: All .cfg and .ovl files for use must be placed on the SCU diskette. We are paging memory and we could possibly run out of disk space if too much data is placed on the SCU disk.   Care must be taken to avoid this.


DPT 2122 hangs system with no drives attached  2472

Problem: Placing a DPT 2122 SCSI raid controller in any EISA slot of the ALTServer system seems to hang with no drives attached to the 2122.

Resolution:  Investigation into this matter has shown that the DPT BIOS and Adpatec BIOS is conflicting in their assignments of ROM shadowing.  This issue has been brought to the attention of Adaptec and they are currently working to resolve.


BIOS does not honor the lock bit for PCI/PnP devices 2890

Problem:  Currently the [F8] Lock Resources option in the SCU doesn't work. Each reboot of the system will clear the bits assigned to take care of this.  The only resource that is reliably selectable via the SCU is the device IRQ.

Solution: The plan of record is to  Will be fixed in future BIOS.


Windows NT* 3.5 / 3.51

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

WinNT3.51 shows resource conflict between AHA2940 and pro100b  2529

DPT PM3224W RAID card fails to install Win NT 3.51  2467

System can hang on the 10th of the month at 10:40 AM


WinNT3.51 shows resource conflict between AHA2940 and pro100b  2529

Problem:  WinNT3.51 SV shows resource conflict between AHA2940 and EEpro100B while SCU assigned the resource correctly.

Resolution:  Under investigation.


DPT PM3224W RAID card fails to install Win NT 3.51  2467

Problem:  Windows Nt installation is completed. However, when the system boots the OS LOADER to complete the final installation of Nt, it hangs (blue screen). Sometimes it will state an error message can not find a bootable device. DPT PART NUMBER: HA-0321-002-B WITH FIRMWARE UPDATE (-C EQUIVALENT) DPT BIOS ver. 003.C9 FAB 7 : 648428-302 SEAGATE BARRACUDA ST32550N

Resolution:  Under investigation.  Intel is working with DPT to resolve.


System can hang on the 10th of the month at 10:40 AM

Problem:  Windows NT fails to boot after displaying "OS loader v 3.51", or a currently running Windows NT system will hang. The problem only occurs at 10:40 AM on the 10th of the month. The anomaly is a consequence of Testview (Intel's manufacturing test and diagnostics software module) incorrectly initializing the reqisters of the real time clock. The error creats an interrupt that Windows NT cannot handle.

Resolution:  A special utility has been developed to properly initialize the real time clock. It is called RTC.EXE and is available from the Intel Application Support BBS. In addition, XDIAGNOSTICS which is supplied with Testview has been modified to disable the resister.


Windows* 95

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

Produced double mouse pointers @ 1280X1024 resolution w/Win95 2175

Win95 would not recognize CD-ROM drive  2375

Onboard CL GD5430-QC-B failed Windows95 video resolutions 2221


Produced double mouse pointers @ 1280X1024 resolution w/Win95 2175

Problem:  Using the Orchid Kelvin 64, when the 1280X1024 resolution was selected, the mouse pointer changed to a double pointer. The mouse pointer also had to be clicked below and to the right of a desired menu selection.

Resolution:  Fixed in BIOS 17, will close when BIOS releases.


Win95 would not recognize CD-ROM drive  2375

Problem:  Subsequent to Win95 installation using a CD-ROM the platform failed to recognize the same CD-ROM when attempting to install the HCT's.

Resolution:  Fixed in BIOS 17, will close when BIOS releases.


Onboard CL GD5430-QC-B failed Windows95 video resolutions 2221

Problem:  When changing resolutions, the pull down menu leaves behind bits of images.

Resolution:  Under investigation.


Novell* NetWare* 3.12, 4.1x

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

SMC EISA 10/100 card fails Netware 4.10 testing 2258

Thomas Conrad TC3045 ArcNet ISA fails to init w/ NW 4.1   2278

Cogent EM964 PCI Quartet LAN card fails NWtest 2300

DPT 2122 EISA controller fails lite load test  2307

3COM TokenLink III ISA card fails NWTEST; Spurious IRQ error  2400

Proteon P1392+ fails NWTEST in Netware 4.10  2404

Thomas Conrad TC6242 fails NWTEST in Netware 4.10  2406

IBM 16/4 II, 3COM TokeLinkIII, TC5045 fail NWTEST 2427

Intel Token Express32 failed NWTEST after 18hrs  2457


SMC EISA 10/100 card fails Netware 4.10 testing 2258

Problem:  SMC EISA 10/100 card fails Netware 4.10 testing. Network stations drop off of server.  When 4 NE3200 are installed in a FAB 7 baseboard, stations start dropping off. With only 3 NE3200 installed in a FAB 7 baseboard, there are no problems with stations dropping off.

Resolution:  Under investigation.


Thomas Conrad TC3045 ArcNet ISA fails to init w/ NW 4.1   2278

Problem:  The cards should initialize in the system under test, connect to each other, and an IPX route should be established between the two systems.  The Failure in this Case: The TCMSL lan driver could not initialize the card. It reported there was no reset signal from the card.

Resolution:  Under investigation


Cogent EM964 PCI Quartet LAN card fails NWtest 2300

Problem:  One of the clients rebooted itself at the same time the two other clients reported Network Read Errors. The server was unresponsive to keyboard commands, requiring a hard reset to regain control.

Resolution:  Under investigation.


DPT 2122 EISA controller fails lite load test  2307

Problem:  With the DPT card in the system, the system would lock after Starting MS-DOS and the floppy access light would remain on. This failure only occured with 2 SCSI drives in the system. With only 1 drive in the system the DPT would function correctly.

Resolution:  Under investigation, Deturbo has been reported to fix this issue.  This may be caused by the same issue as DCS 2043.


3COM TokenLink III ISA card fails NWTEST; Spurious IRQ error  2400

Problem:  The client would be unable to attach to the 3COM card. When the VLM was executed from the client, the server would report "Spurious Hardware Interrupt 5 Detected". The specific interrupt number would change according to the configuration used. If the 3COM card was configured at interrupt 3, the spurious interrupt would report "Spurious Hardware Interrupt 3 Detected".

Resolution:  Under Investigation.


Proteon P1392+ fails NWTEST in Netware 4.10  2404

Problem:  NWTEST would start reporting write errors immediately upon starting. The error count would increase until the maximum of 50 errors was reached. NWTEST would then stop.

Resolution:  Under investigation.


Thomas Conrad TC6242 fails NWTEST in Netware 4.10  2406

Problem:  The lan driver would load, immediately causing the Server to abend, reporting a "Page Fault Processor Exception Error". This occurs using either of the listed drivers for the card.

Resolution:  Under investigation


IBM 16/4 II, 3COM TokeLinkIII, TC5045 fail NWTEST 2427

Problem:  The IBM 16/4 II card failed when the lan driver for the card was installed. Netware reported "Error Allocating Memory For The Adapter Structure". The TokenBM lan driver would not load. The 3COM TokenLink III card failed after the client had attached and NWTEST had been started. The server would report Spurious Hardware Interrupt X Detected. The interrupt number reported would change according to the cards' configuration. After the server reported this error, the client would report a Network Read Error. At that point, the client had been disconnected from the network. If the client was re-attached to the server, and NWTEST was restarted, the server would abend. The Proteon P1392+ lan driver would load without difficulty. The card did not receive any requests for service. No received packets received were seen by the server. The Thomas Conrad TC4045 failed after the client had attached to the card. When LOGIN was executed from the client, the server would report Initialization Error = 1C - DMA Data Error. The client could not log in. The Thomas Conrad TC5045 failed when the client was requesting service. Everything would load at the client except the VLM, which would abend the server as soon as it requested service from the TC5045.

Resolution:  Under investigation


Intel Token Express32 failed NWTEST after 18hrs  2457

Problem:  NWTest gave a network read error on the Intel Token express 32 at 18hrs in to the overnight test.

Resolution:  Under investigation.


SCO UNIX

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

None known at this time


None known at this time


Banyan* Vines* 6.0

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

Fails certification tests with 1 MEG hole and SCSI enabled  2455


Fails certification tests with 1 MEG hole and SCSI enabled  2455

Problem:  Banyan 6.0 certification tests fail when the onboard SCSI controller and 1MB hole are both enabled. When IDE drives are used and the onboard SCSI controller is disabled, all tests run clean. Once the 1MB hole is enabled with drives attached to the onboard SCSI controller, the system will panic with core dumps. SCSI driver V.1.0L.

Resolution:  Under investigation.


Novell UnixWare* 2.x

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

Know that as of BIOS 15 (1.00.15.BI0), Multiprocessing requires release Unixware 2.03.


Know that as of BIOS 15 (1.00.15.BI0), Multiprocessing requires release Unixware 2.03.


Solaris*

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

None known at this time.


None known at this time.


IBM* OS/2*

(Errata present in BIOS 1.00.15.BI0 and SCU 3.21 overlay 1.01)

Related Topics:

OS/2 Stress test FSDEL322 would not pass 2420

Fails to install OS/2 SMP 2.11 successfully; OS2APIC.PSD failure 2438


OS/2 Stress test FSDEL322 would not pass 2420

Problem:  The test FSDEL322 did not complete during the PCMMED01, long stress test. Nor did it complete satisfactorily when run by itself.

Resolution:  Under investigation.  Conversations with IBM indicate this may be a video issue.


Fails to install OS/2 SMP 2.11 successfully; OS2APIC.PSD failure 2438

Problem:  SMP operating system fails to install. Failure is characterized by "freezing" during the final boot on the Fab 7 (PBA# ending in -30x) baseboard.

Resolution:  Under investigation


Processor Errata as they apply to ALTServer Summary

1, 2, 3, 4, 5, 6, 7, 9	Not An Issue
10, 11,13	Not An Issue/with Explanation
14	Not An Issue
15	Not An Issue/with Explanation
16	Not An Issue/with Explanation
17	Not An Issue/with Explanation
DP1, DP2, DP3, DP4, DP5, DP6, DP7	Not An Issue/with Explanations
AP1, AP2, AP5, AP6, AP7, AP8	Not An Issue/with Explanation
AP9	Affected and plans in place to resolve or document.
AP10	Work Around Exists
TCP2	Not An Issue


Processor Errata Details

Various signals and instructions   1- 9

STPCLK# deassertion not recognized for 5 CLKs after BRDY# returned  10

Future Pentium OverDrive® processor FERR# contention in two-socket systems  11

STPCLK# assertion during execution of the HALT instruction hangs system  13

Runbist restrictions when run through boundary scan circuitry  15

FCR mode miscompare due to uninitialized internal register  16

STPCLK# restrictions during EWBE#  17

For baseboards that employ B step dual processors  DP1, DP2, DP3, DP4, DP5, DP6, DP7

For baseboards that employ dual processors and use Pentium® processor APICthe   AP1, AP2, AP5, AP6, AP7, AP8

Spurious interrupt in APIC through local mode  AP9

Potential for lost interrupts while using APIC in through local mode  AP10

For only those systems that use TCP package  TCP2


Various signals and instructions   1- 9

Errata 1 through 9 deal with various levels of functionality or debugging situations.  Each has been fixed in the C2 step of the part.  All ALTServer products are shipping with the C2 parts, so this is not an issue.


STPCLK# deassertion not recognized for 5 CLKs after BRDY# returned  10

The BRDY# on the Intel Server platform ALTServer baseboard has been implemented in a manner such that STPCLK# is not used, so this is not an issue.


Future Pentium OverDrive® processor FERR# contention in two-socket systems  11

This erratum describes the situations that may exist when the Future Pentium OverDrive processor is plugged into Socket 5 of a two-socket 75-, 90-, or 100-MHz Pentium processor system.  On the ALTServer baseboard, this could occur and cause the OEM processor to shut down following RESET to allow the OverDrive processor to drive the bus.  In this case, the FERR# output of the 75-, 90-, and 100-MHz Pentium processor continues to be driven HIGH (inactive).

The chosen workaround for this errata is shown in the figure that follows.  External logic is used to connect the FERR# outputs from the two sockets (296-pin SPGA and 320-pin Socket 5) in a way that will resolve the signal contention. An external AND gate is used to combine the outputs of the FERR# signals from the two sockets.  A pull-up resistor (≥3KΩ) is required on the FERR# output from Socket 5 in order to allow proper operation of both the Dual Processor and the Future Pentium OverDrive processor.

ALTServer uses this workaround  to prevent bus contention and allow the processors to individually drive the bus when needed.


STPCLK# assertion during execution of the HALT instruction hangs system  13

The Intel Server platform baseboard APM code has been implemented in a manner such that STPCLK# is not used, so this is not an issue.


Runbist restrictions when run through boundary scan circuitry  15

The Intel Server platform baseboard has been implemented in a manner such that Runbist is not used, so this is not an issue.


FCR mode miscompare due to uninitialized internal register  16

This problem only has implications in dual processor fault tolerant machines that employ FRC (Functional Redundancy Checking) on a cycle by cycle basis. The Intel Server platform baseboard has been implemented in a manner such that the FRC Mode is not used, so this is not an issue.


STPCLK# restrictions during EWBE#  17

The Intel Server platform baseboard APM code has been implemented in a manner such that STPCLK# is not used, so this is not an issue.


For baseboards that employ B step dual processors  DP1, DP2, DP3, DP4, DP5, DP6, DP7

These errata are relevant only for baseboards that employ B step dual processors.  The Intel Server platform position has always and will continue to be that all ALTServer baseboards will not be DP-ready for pre-production products.  All DP errata are fixed in the C-step parts.  All ALTServer production products will be C step or later baseboards, so this is not an issue.


For baseboards that employ dual processors and use Pentium® processor APICthe   AP1, AP2, AP5, AP6, AP7, AP8

These errata are relevant only for baseboards that employ dual processors and use the Pentium APIC.  The only time the APIC is used is in the DP mode, and hence the Intel Server platform position has always and will continue to be that all ALTServer baseboards will not be DP-ready for pre-production products.  All DP errata are fixed in the C-step parts.  All Intel Server platform ALTServer production products will be C step or later baseboards, so this is not an issue.


Spurious interrupt in APIC through local mode  AP9

In a non-APIC system, interrupts are presented to the processor on the INTR pin. INTR is a level sensitive input, which means that WHENEVER INTERRUPTS ARE ENABLED, an interrupt acknowledge cycle will be run by the processor on the next instruction boundary after recognition of an active level on the pin.

When the INTR pin is routed through the APIC unit, a design error caused information on the INTR pin to be latched (edge sensitive) rather than flow through (level sensitive).  As a result, even when processor interrupts are disabled, an "extra"(spurious/"lost") interrupt occurs.  Most operating systems ignore spurious interrupts.  Novell logs them and reports them as lost interrupts--meaning that an interrupt occurred, it came from hardware, but the OS can no longer identify the source.  In this case, the source of the interrupt is the 9AP Pentium errata.

The only possible Resolution that we have is to disable the APIC whenever we are in uniprocessor mode.  A register is available in the Pentium processor which can be used to disable the APIC.  But this can only be done when we know that a uniprocessor OS is being used.  We have verified that this workaround fixes the problems that have been reported. We will offer our customers an executable program that will perform this function, and we can work with our OS vendors to also implement this function.  Starting with BIOS version 1.00.04, the APIC can be disabled from F1 Setup.


Potential for lost interrupts while using APIC in through local mode  AP10

Problem:  This erratum affects APIC in through local (virtual wire) mode. If a uniprocessing or dual processing system is using a 75-, 90- or 100-MHz Pentium processor with the APIC in through-local (virtual wire) mode, and the chipset is able to re-assert the INTR line prior to completion of the second Interrupt acknowledge cycle (from a prior assertion of the INTR line), then the processor will neither recognize nor service the second interrupt. The assertion edge of INTR has to occur after the completion of the second IntAck BRDY#, if there is a transition and this transition is held high during the restricted time period, this INTR will not be recognized. Software disabling of the APIC by clearing bit 8 of the SVR (spurious vector interrupt register) will not prevent this from occurring.

Implication:  If the conditions listed above are met, the system may hang up, because there would be an interrupt that would not get serviced.

Workaround:  A PAL has been added to the baseboard to modify the chipsets such that they cannot assert a second INTR for processing prior the completion of both Interrupt acknowledge cycles for the first INTR.


For only those systems that use TCP package  TCP2

This erratum applies to only those systems that use the TCP package.  No Intel Server platform baseboards use the TCP package, so this is not an issue.


Known Errata - System


Manual

Front panel connector pinout

Hotkeys for Turbo / Deturbo


Front panel connector pinout

Pin 16 should be Chassis Switch.


 Hotkeys for Turbo / Deturbo

Problem:  The ALTServer product manual states that the hotkey sequence incorrectly .

Resolution:  The correct hotkey sequence for Turbo Enabled is <Ctrl-Alt-+>(plus),

Turbo Disable is <Ctrl-Alt-->(minus).


Closed Errata

Chassis Label incorrectly displays PCI Slot Order - CLOSED

Front panel power down - CLOSED

OS/2 2.11 - server cannot remote boot with IBM TR  1236  - CLOSED

OS/2 displays phantom floppy drive B: icon 2154  - Closed

Screen blanked at  start  of network part of MP Stress Test 1835 - CLOSED

Mouse movement and button presses misinterpreted after reboot  1381 - CLOSED

NFS clients lose connections with ALTServer running UnixWare 2.01 2199 - CLOSED

Unixware data corruption  2203  - CLOSED

SCO rel 5.0 fails to install  2674  - CLOSED

ALTServer POST(BIOS) can not detect newly installed EISA card   2454 - CLOSED

Disabling the 2nd serial and the parallel port, OS/2 WARP locked up  1580 - CLOSED

ALTServer SCU hangs installing EtherExpress and TokenExpress EISA cards together  2116 - CLOSED

Server hangs during loading if a DPT EISA SCSI Controller is in the system  2118  - CLOSED

IBM token ring can't be installed with SCU, can without  2164 - CLOSED

BIOS Setup & SCU differ on IDE sectors per block  2231 - CLOSED

BIOS setup sometimes implies 2 onboard SCSI devices  2233 - CLOSED

SCU hangs at various times for memory issues  2360 - CLOSED

SCU does not copy required *.OVL file when copying *.CFG file  2398 - CLOSED

SCU references "Memory Above & Below 512M" system only supports 256M  2399 - CLOSED

SCU will not correctly configure 2 DPT 2122 SCSI RAID controllers  2473 - CLOSED

BIOS - EISA CFG errors don't give <F1> wait message  2392 - CLOSED

Adding EISA cards with the manual add in the AMISCU can cause defaults  2426 - CLOSED

Adaptec Driver not using config data in CMOS  2461 - CLOSED

IBM DFHS52F HDD makes loud noise at cold boot 2884  CLOSED

DPT configuration program fails to run w/ on-board SCSI drive attached  2471 - CLOSED

SCU - Second Processor Status=Pass w/out processor present  2390  - CLOSED

SCU-Internal PCI resources can be removed in Add/Remove boards  2405 - CLOSED

Restoring Configurations from Backup CMS does not restore baseboard  2519 -CLOSED

Fujitsu keyboard not detected with bios 1.00.07  2525 - CLOSED

System board configuration file erros  2561 - CLOSED

AMI SCU conflicting configuration  2562 - CLOSED

Automatic/Manual Configuration labels misleading  2563  - CLOSED

NetWare 3.12J abends after about 9 hours of LAN stress test   2059 - CLOSED

NetWare drops SCSI drive volumes with ST3390N drives  2488  - CLOSED

PCI bridge cannot be configured conveniently  2145 - CLOSED

Adobe* Acrobat* Reader fails on system without Adobe Type Manager  2149 - CLOSED

Problems with Password protection in CMOS Setup  2160  - CLOSED

System I/O Ports need defined in SCU  2196 - CLOSED

Secure mode enabled on bootup with keyboard controller ver. 1.22  2202 - CLOSED

FAST IDE PIO modes & DMA modes not functional  2241 - CLOSED

Unreliable XMS Memory Error with HIMEM.SYS  2484 - CLOSED

SCSI BIOS gives 2nd Data Drive > 1G Warning Message  2538 - CLOSED

SCU does not manage IDE IRQ properly  2555 - CLOSED

LCD Display comes up enabled after CMOS clear  2585 - CLOSED

SMIs occurring with SMP configuration creates system hangs  2619 - CLOSED

PCEB register 46h initialized with 64K hole at 1Meg  2624 - CLOSED

Orchid Kelvin EZ PCI video adapter incompatible on ALTServer 2737- CLOSED

ALTServer fails to recognize the #9GXE 64 or #9 FX Motion 531 video cards 2738 - CLOSED

Undetected data corruption in on-board SCSI  1625 - Closed

Customer-supplied soft reset program locks ALTServer  1632 - CLOSED

Windows* 3.1 with #9GXE, screen garbled  1739 - CLOSED

Some SCSI devices cannot support 10.5 MB/s transfer rate  573 -CLOSED

Onboard parallel port does not show up when external port installed  1054 -  CLOSED

Adaptec* 1532P resets to IRQ6 each time server is rebooted   1542 CLOSED

PCIDiag test reports Orphan Vendor and Device ID   1573 - CLOSED

Zynx 312 diagnostic prints nonsense on ALTServer  2040 - CLOSED

Test Time for Windows NT Tape Test takes a long time  1829 - CLOSED

SONY CDU55S CD-ROM hanging using UnixWare 1.02S driver  565  CLOSED

Adaptec 1542CP requesting wrong interrupt  1298 CLOSED

Network adapters using the PLX 9032D chip may fail  1371 CLOSED

NDIS driver causes Lantastic to lose connection during first 1 MB file transfer  1537 CLOSED

Intel SMM does not allow shared memory use, interrupts, and DMA  1614 CLOSED

DTC2290 EISA IDE controller causes an unresolvable resource conflict  1919 CLOSED

3-mode floppy failure when IDE not plugged in  2101 CLOSED

PCI bridge resource allocation problem above 1 gigabyte  2102   CLOSED

120 Mhz CPu speed reported incorrectly in setup  2138 CLOSED

ISA bus mastering to PCI video fails when using LANDesk® Server Monitor Module  2140 CLOSED

PCI arbitration problem   2446 CLOSED

ALTServer baseboard fails password selections portions of the BIOS test  2508 CLOSED

ALTServer Testview (CPU) Anomaly  2314 CLOSED

ECP parallel port needs selectable DMA  2250 CLOSED

ALTServer IBM TR II will not initialize (NDIS driver problem) 2287 CLOSED

SCU Can't Lock EISA Resources  2256 CLOSED

Cannot boot from Future Domain PnP 1630 SCSI  2345 CLOSED

SMI not active on ALTServer  2295 CLOSED

3COM TokenLink III will not initialize 2288 CLOSED

STB Velocity 64 PCI adapter fails at boot  2389 CLOSED

ECP Parallel option inoperable 2630 CLOSED

SCU and OVL may produce dead-lock when resolving conflicts 2768 CLOSED

PCI devices getting assigned pre-allocated memory 2875 CLOSED

Static Device Resource Conflicts 2883 CLOSED

Removing an EISA card may delete ISA entries  2427 CLOSED

Thomas Conrad TC4045 fails NWTEST in Netware 4.10  2407 CLOSED

Removing EISA video card causes system to hang  2248   CLOSED

Failed to recognize several video cards  2526  CLOSED


Chassis Label incorrectly displays PCI Slot Order - CLOSED

Problem:  PCI Slots are incorrectly labeled on the chassis configuration label

Resolution:  Correct order is Slot 1 closest to the EISA slot (Slot 3 on label), slot 2 in the middle (no change), Slot 3 closest to 3.3V connector (Slot 1 on label).  The label has been corrected.


Front panel power down - CLOSED

Problem:  This model of the Columbus chassis does not support power-down features.  Intel will make a field-replaceable front panel available to customers who wish to upgrade.

Resolution:  Front panel interface board has been redesigned and now operates properly with the baseboard powerdown feature.  This can be verified by front panel PBA #634425-003 or later


OS/2 2.11 - server cannot remote boot with IBM TR  1236	 - CLOSED

Problem:   The IBM Token-Ring II RPL card was configured, using the SCU utility, to:  IRQ 3; no DMA; 64K of reserved memory starting at d8000; and I/O port 0a2-0a3 (the field will not allow an entry without a leading zero and, since there are only 3 character positions, a20-a2f cannot be chosen).  The onboard IDE is disabled and the system is set to Deturbo mode for this test.  ISA ROM shadowing for d8000 and dc000 was enabled for the first attempt and disabled for the second with the same result.  When the system is booted, an error message appears, immediately following the installation of the floppy drives, which says: "PCI I/ O port conflict: BUS 00, DEVICE 0F, FUNCTION 00".  After this message appears, the system is locked and stays locked until CMOS (NVRAM) is cleared.  The device indicated is the onboard SCSI (Adaptec 7870).  A  check of resources using SCU shows no apparent conflicts with I/O ports, IRQ's, or memory locations.  When the onboard PCI SCSI is modified using SCU, the changes do not appear to be saved (SCU reports a save, but subsequent checks show values reset to prior settings).  A check using the PCI.EXE program also shows that the changes are not incorporated.  If the Token-Ring card is not installed using the SCU, the card attempts to perform the remote boot but fails with a trap error (000e) when trying to initialize the adapter.

Resolution:  By adding the line to the PROTOCOL.INI file specifying where the on-card RAM can be found the IBM TR II will remote boot. The line should lok something like this:

                                          RAM=0xD800


OS/2 displays phantom floppy drive B: icon 2154	 - Closed

Problem:  OS/2 2.11, 2.11 SMP, and Warp all display an icon for floppy drive B: in the Drives folder.  If invoked, the object accesses the A: floppy drive.

Resolution:  Closed: This is a feature, not a bug.  The BIOS allows access to the floppy via both A: and B:.  OS/2 simply provides icons for both available drives..


Screen blanked at  start  of network part of MP Stress Test 1835	- CLOSED

Problem:   Screen blanked and server went down after attempt to open another window and start   network part of MP Stress Test .  A portion of the Solaris 2.4 MP Stress test simultaneously reads from the CD-ROM and reads and writes from both floppies, tape, and parallel port while playing a sound file.  On the ALTServer system, this part of the MP Stress test started and initially ran successfully. When attempting to open another window and start the Network portion of the MP Stress Test, the screen blanked and the system went down.

Resolution: Test script issue.


Mouse movement and button presses misinterpreted after reboot  1381 - CLOSED

Problem:  With UnixWare 2.0 Beta 2 on a multiprocessor server, mouse movement and button presses are misinterpreted after reboot.  The mouse cursor does not follow mouse movement and moves erratically in the upper left quadrant of the screen.

Resolution:  This affects only the Logitec serial mouse configured as a Microsoft serial mouse.  The Mouse Systems serial mouse and the Microsoft serial mouse have been tested and work fine.  Workaround: Press <ALT><SYS REQ><H> to exit to the console window.  Log in as root and then exit.


NFS clients lose connections with ALTServer running UnixWare 2.01 2199 - CLOSED

Problem:  The ALTServer has displayed unreliable test results when certain test routines that required the ALTServer to start seven processes that copy 16K to 500K files to and from the ALTServer before comparing the results. After a few moments, an error message stating that the server is not responding is displayed.

Resolution: Novell has been notified of this problem and recognizes that only AMD (with special drivers from Novell) will run properly with UnixWare 2.0x.  Novell is working on this problem.  A delay in the test script and a new VM driver from Novell fixed this issue.


Unixware data corruption  2203	 - CLOSED

Problem:  Using a DPT 3224/90 PCI/SCSI card in the PCI bus as a boot device, data corruption occurs running the grind script.   HDW setup as follows:

   PCI0-2 DPT 3224/90 connected to ST31230W

   AIC-7870 SCSI-A connected to ST31230W

Grind was run on all three adapters and data corruption occurred on each.  One to five data corruption usually occur, and the data size is between 8 bytes and 3 K (although most are under 512 bytes).  Data corruption shows no consistent signature.  Both updated and original DPT firmware were tried with similar results.  Both UW 2.0 and 2.01 were tried with similar results.

Resolution:   A patch from Novell for the VM system fixed this issue.


SCO rel 5.0 fails to install  2674	 - CLOSED

Problem: Installation completes but when the system reboots to load the kernal, the HDD is corrupted.

Resolution:  This is due to a problem in the BIOS.  It has been fixed in BIOS 1.00.11.BI0 and later releases.


ALTServer POST(BIOS) can not detect newly installed EISA card   2454 - CLOSED

Problem:  ALTServer POST(BIOS) can not detect the new EISA card that is installed in the EISA slot 6 and does not shows the POST 0043 error.  Other EISA slot shows the ""0043: EISA Invalid configuration for slot"" POST error when new card is installed in the slot. However, If EISA card is removed from slot 6, POST can detect this change and shows the ""0043"" POST error

Resolution:  This problem has been proven to be a core BIOS issue and it has been tested using an alpha version of the new BIOS.  The results were positive and will be implemented in the next release of the BIOS.  Fixed in BIOS 1.00.11.BI0


Disabling the 2nd serial and the parallel port, OS/2 WARP locked up  1580 - CLOSED

Problem:  After running the SCU to disable the second onboard serial port and the onboard parallel port, OS/2 WARP locks up or crashes when entering a DOS or Windows Full Screen or Windowed session if OS/2 has filled all real memory and has expanded to the virtual swap file.

Resolution:  Load DOS and Windows sessions during startup, before the swap file is expanded. Problem only occurs with Adaptec AIC7870.ADD OS/2 driver. Problem does not occur with IBMINT13.INT driver. Problem does not occur with IDE drives. Determined this failure happens on system whether SCU is executed or not.  Problem no longer occurs on BIOS 1.00.11.BI0.


ALTServer SCU hangs installing EtherExpress and TokenExpress EISA cards together  2116 - CLOSED

Problem:  ALTServer SCU hangs installing EtherExpress and TokenExpress EISA cards together. When installing the TokenExpress 32 into the ALTServer system, with the Flash32 card already installed, the SCU (ver. 3.07 overlay 27) will request the TokenExpress 32's configuration file !INT1201. 10/08/93))).  The SCU should read this .CFG file and install the TokenExpress 32 card.  However, while reading the file, the system will hang. At this point the system requires a "warm- boot" key sequence to restart the system.  If the TokenExpress 32 card or the Flash32 is installed in the system alone, the installation functions normally.  If an attempt is made to install the Flash32 card !INT1010.CFG (4/19/95)) after the TokenExpress 32 is installed, the system will again hang when reading the !INT1201.CFG file.  The following configurations were also tested and found to be successful:

TokenExpress 32 and 3COM 3c579 & Flash 32 and Proteon 190

Flash32 chipset=PLX 9032

INT=10 SLOT=3

TokenExpress 32 chipset=j9312

INT=9 SLOT=5 DMA=6

 Resolution:  This is no longer an issue as of SCU 3.11 / 39, BIOS 1.00.11.BI0


Server hangs during loading if a DPT EISA SCSI Controller is in the system  2118 	- CLOSED

Problem:  ALTServer - SCU ovl 27 hangs with EISA DPT 2122 SCSI controller.  The previous version of the overlay, 00.26 does not hang, and the system can be configured properly.

Resolution:  The AMI SCU has a memory management bug that sometimes causes the SCU to hang.  You must run the SCU from the SCU diskette so that there is as much conventional RAM available as possible.  Intel is currently working with AMI on this memory allocation problem. SCU overlay 31 will allow this board to be configured, due to increased availability of memory resources.  One dcs entry will be created to consolidate the SCU memory allocation issue.  As is, the SCU will allow a maximum of 4 EISA cards to be configured without running out of memory. There is no work-around for this problem.  The best we can do is shrink the size of the baseboard overlay to free up more memory.  OVL 00.31 has been shrunk for ALTServer.  SCU 3.08 implements a paging system that may help alleviate this problem in certain scenarios.  Fixed in SCU 3.11 / 39.


IBM token ring can't be installed with SCU, can without  2164 - CLOSED

Problem:  The ALTServer board fails to configure an IBM Token Ring II card using the SCU program due to the inability to select the A20 I/O port.

Resolution:  This is an ISA card. The process is to not attempt any card configuration using the SCU and instead just install the card with the settings at IRQ 3, I/O A20, RAM at D800 and ROM at DC00 as per adapter card documentation.  Config file supplied by vendor works if user selects from the PCI directory.


BIOS Setup & SCU differ on IDE sectors per block  2231 - CLOSED

Problem:  BIOS offers: Auto / 4 / 8 sectors per block.  SCU offers: Auto / 8 /16 sectors per block.

Resolution: This problem has been verified with an alpha version of the next SCU release.  The results were positive and will be included in the new SCU that accompanies the next BIOS release.  Fixed in SCU 3.11/ 39 and BIOS 1.00.11.BI0


BIOS setup sometimes implies 2 onboard SCSI devices  2233 - CLOSED

Problem:  The BIOS setup displays two in peripheral setup: SCSI A BIOS Scan? SCSI B BIOS Scan?

Sometimes see it say just SCSI A, sometimes just SCSI B. This may also be seen as Channel B.

Resolution:  Fixed in  BIOS 1.00.11.BI0


SCU hangs at various times for memory issues  2360 - CLOSED

Problem: Error condition with SCU - requires reboot to clear. BIOS 1.00.7, SCU 3.08 ovl 31

ERROR An error occurred while processing the overlay file. hit ESC,( or F10 or RETURN)

says:

ERROR Out of memory. Must Abort configuration. hit ENTER,ESC or F10

says:

ERROR Out of memory. Must Abort configuration and the user can't get out of that condition.

Resolution:  Fixed in SCU 3.11 / 39.


SCU does not copy required *.OVL file when copying *.CFG file  2398	- CLOSED

Problem:  SCU does not copy required *.OVL file when copying *.CFG file.  Using BIOS 1.00.07.BI0 and SCU 3.08 OVL 31, an Adaptec 2740 EISA card was installed in the system.  Upon running the SCU the following error message was received:  'OVL file not found.'  An inspection of the SCU diskette showed that the CFG file had been copied, but the OVL file had not. The SCU now correctly handles the situation where it must copy a *.CFG file from a third-party disk to the SCU disk, but it does not also copy an accompanying *.OVL file and the configuration attempt later fails when that file cannot be found.  This was observed with an Adaptec 1740.

Resolution:  Fixed in SCU 3.11 / 39.


SCU references "Memory Above & Below 512M" system only supports 256M  2399 - CLOSED

Problem:  Confusion may exist but there are no functional difficulties with this.

Resolution:  Fixed in SCU 3.11 / 39./


SCU will not correctly configure 2 DPT 2122 SCSI RAID controllers  2473 - CLOSED

Problem:  To duplicate this problem:

1)  Place 2 DPT 2122 SCSI Raid controllers in any EISA slots.

2)  Clear CMOS.

3)  Configure one controller for IRQ15, BIOS address C8000, floppy disabled

     and WD1003 mode disabled

4)  Configure the other controller for IRQ15, BIOS disabled, floppy disabled,

    and WD1003 mode disabled,

SCU will report a conflict and place WD1003 mode to enabled.  This is incorrect.

The system will not boot. The same procedure performed with the MCS ECU will work painlessly.  In fact it will occur automatically.  The system will boot.

Resolution: Initial inspection leads to a core problem in the AMISCU that does not allow sharing of resources based upon adapter type.  Will work with AMI to resolve.


BIOS - EISA CFG errors don't give <F1> wait message  2392 - CLOSED

Problem:  Insert or remove an EISA card without manipulating SCU first.  System will display the ""EISA Config Error..."" message but no longer gives user the option to enter setup <F1> or <ESC> to continue, it just continues on booting.  Previous BIOS' would pause on this error.

Resolution:  Install the card in the SCU before physically installing card. This problem has been proven to be a core BIOS issue and it has been tested using an alpha version of the new BIOS.  The results were positive and will be implemented in the next release of the BIOS 1.00.11.BI0.


Adding EISA cards with the manual add in the AMISCU can cause defaults  2426 - CLOSED

Problem:  When the user adds an EISA card via the manual add feature of the AMISCU,  the selections for other cards may be set to defaults (all selections, not just resource oriented selections).

Resolution: Fixed in SCU 3.11 / 39.


Adaptec Driver not using config data in CMOS  2461 - CLOSED

Problem:  The UnixWare Driver, and maybe others, tries to get the configuration data from SEEPROM attached to AIC-7870, if there is no SEEPROM, the driver will use default values, ie Wide, Sync @ 10MB/s, Disconnect, no start unit, etc. which will cause some drives/configurations to break.  Additional problems will appear with devices that do not perform up to what the actually negotiate to.  Some drives may say they transfer at 10MB/s but cannot handle that for sustained periods.  On boards with REV B AIC-7870 parts, this is more of a problem, since 10MB/s setting has an actual rate of 10.5MB/s - several drives cannot handle that

Resolution:  New Adaptec Driver version 1.10s3 fixes this problem.


IBM DFHS52F HDD makes loud noise at cold boot 2884 	CLOSED

Problem:  Using an IBM DFHS52F Hard Disk Drive in an ALTServer system seems to make lots of noise.

Resolution:  IBM has supplied new firmware for the drive that corrected the problem


DPT configuration program fails to run w/ on-board SCSI drive attached  2471 - CLOSED

Problem:  To replicate this problem:

1)   Place DPT 2122 SCSI Raid controller in any EISA slot.

      Place a SCSI disk on the on-board 7870 SCSI interface.

2)  Clear CMOS

3)  Run SCU and configure DPT2122 for INT 15, BIOS C8000, disable

     WD1003 boot, disable floppy

4)  Save configuration and reboot

5)  Run vendor supplied DPTMGR from floppy  to configure controller.

6)  Software will report that ""SmartRom has not been detected,"" and cannot

     configure a controller in the system. This is the problem.

7) If the drive attached to the on-board controller is removed, DPTMGR will

    run correctly and can identify the 2122 controller.

Resolution:  The BIOS was looking at the shadowing default locations for option ROMs.  The default state was set incorrectly to not shadow which destroyed the DPT SCSI BIOS after bootup. The DPT BIOS and onboard SCSI BIOS appear to both hook int 13 and disable the onboard drive.  The Adaptec and SCSI BIOS do not appear to agree on how to hook int13. The new BIOS (1.00.11.BI0) will correctly shadow the area.


SCU - Second Processor Status=Pass w/out processor present  2390	 - CLOSED

Problem:  SCU 308 / 31, fab 4 -3 baseboard, bios 1.00.07.  Run the SCU, SCU indicates that 2nd processor is not present, further down it says the 2nd processor status  is a PASS.

Resolution: Fixed in SCU 3.11 / 39


SCU-Internal PCI resources can be removed in Add/Remove boards  2405 - CLOSED

Problem:  SCU allows you to think you've removed video in the add/remove section.  You can delete/save/exit.  Of course the device comes back when you reboot, but the ability to remove these devices is confusing.

Resolution:  Fixed in SCU 3.11 / 39.


Restoring Configurations from Backup CMS does not restore baseboard  2519 -CLOSED

Problem:  When using the ""Restore Configuration from Backup CMS File"", the restore option restores all configurations except for what is under the ""Baseboard Configuration"" including SCSI BIOS scan, serial ports, and IDE enable.  All of the baseboard options are left at the current value.

Resolution:  Fixed in SCU 3.11 / 39


Fujitsu keyboard not detected with bios 1.00.07  2525 - CLOSED

Problem:  Fujitsu 4700 and 4800 model keyboards not detected with either kbd controller

1.22 or 1.28 and BIOS 1.00.07.

Resolution:  Fixed in the next release of the BIOS.  1.00.11.BI0


System board configuration file erros  2561	- CLOSED

Problem:  The AMI SCU may indicate that the system board configuration file contains errors when attempting to add an EISA or ISA card to the system.  This message is a ""false"" message and will be changed to indicate that the SCU simply could not add an adapter card due to irresolvable conflicts.

Resolution:  Fixed in SCU 3.11 / 39


AMI SCU conflicting configuration  2562 - CLOSED

Problem:  The AMI SCU allowed a configuration that had conflicts.  When adding a card, the AMI SCU indicated that the card could not be added.  On a second try to add the card, the SCU allowed the addition but placed resources in conflict.

Resolution:  Fixed in SCU 3.11 / 39.


Automatic/Manual Configuration labels misleading  2563	 - CLOSED

Problem:  The ""Automatic"" and ""Manual"" labels for PCI and PnP devices are misleading.

Automatic --> Current Configuarion

Manual --> User/SCU supplied alternate configuration for next boot.

Resolution:  Next release of SCU has changed these labels to say:

""Current Configuration"" and ""Manual Configuration""".  In SCU 3.11 / 39


NetWare 3.12J abends after about 9 hours of LAN stress test   2059	- CLOSED

Problem:  NetWare3.12J abends after about 9 hours of the LAN stress test with following error message:

Abend: Partition object not found in Partition Mapping Table OS version: NOVELL NetWare v3.12(250 user) 8/12/93

Running Process: Interrupt Service Routine (nested count 1)
Interrupt Process: Polling Process

This problem happened twice with EE32 and once with Fujitsu's LAN card.  Intel's Network Products Division and PLX Technology says that this is a known bug with any Intel NIC card that uses PLX's EISA 9032D used in Intel's PRO/100 EISA and FLASH32 EISA bus master adapters.  This configuration will result in server malfunction or data compare errors in Intel's server-based PCI/EISA systems.  PLX is now revising the EISA 9032D to correct this problem.

Resolution:  This is a known problem with the PLX chip as implemented on many Intel network cards; use different network controllers.  Refer to #1371 in the "Common to All Operating Systems" section of this document.


 NetWare drops SCSI drive volumes with ST3390N drives  2488	 - CLOSED

Problem: This occurs on both NetWare 3.12 and 4.10.  Error has been narrowed down to occurring with Seagate ST3390N and Quantum narrow SCSI drives.  Does NOT fail using Seagate ST31230W drives in the same configuration.  The system also is NOT failing with the Seagate ST3390N drives when the transfer rate is set to 5 MB in the AIC-7870 configuration utility.

Resolution:  Using Seagate's ST31230W or ST3390N drives and setting the transfer rate to 5 MB,  the same configuration has been successfully accomplished.  Seagate is being contacted to check for firmware upgrades or drive limitations. This is an Adaptec Driver issue and has been verified at Adaptec.  Fixed in latest adaptec drivers.


PCI bridge cannot be configured conveniently  2145 - CLOSED

Problem:  To read server's video memory from LANDesk Server Monitor Module, using ISA bus mastering, requires setting bit 2 in the PCEB register 48h.

Resolution: Video memory is now accessable from EISA bus in BIOS 1.00.11.BI0 and later.


Adobe* Acrobat* Reader fails on system without Adobe Type Manager  2149 - CLOSED

Problem:  The ALTServer system does not ship with printed manuals.  The Adobe Reader utility is supplied to read both the SCSI and system manuals.  If you don't have Adobe Type Manager (ATM), you can't read the manual.

Resolution:  Hardcopy manuals being supplied.


Problems with Password protection in CMOS Setup  2160  - CLOSED

Problem:  The password protection in CMOS setup allows the user to backspace over the last character of a correctly typed password and still boot.  After entering a password via CMOS setup on the ALTServer baseboard, and subsequently rebooting, if the correct password is entered, then the [BACKSPACE] key is pressed once, then the [ENTER] key is pressed, the password is accepted.

Resolution:  Does not affect normal operation.  Fixed in relaese 1.00.11.BI0 and later.


System I/O Ports need defined in SCU  2196	- CLOSED

Problem:  All system baseboard I/O Ports need to be defined in the SCU base board CFG file.   In particular, video I/O Ports are not defined.  All ports should be verified.

Resolution:  Resolved in SCU 3.11 Overlay 39


Secure mode enabled on bootup with keyboard controller ver. 1.22  2202 - CLOSED

Problem:  With certain manufacturer's keyboards and version 1.22 of the keyboard controller, the system will come up automatically in secure mode.  This locks out the front panel power and reset switch until the system boots.  In secure mode, this also blanks the video immediately upon bootup if selected in CMOS.

Resolution:  This issue was fixed with the implementation of the 1.28 KB controller cut into the fab 6 baseboard.  Intel PBA number 630958-203 and later.  If you see a problem, swap the keyboard and mouse connectors.  A new keyboard controller will be available beginning June 1995.  You can also press the <ESC> key to continue booting up to DOS.  Here is the list of keyboards that have ben tested an their results:

•	NMB RT 101 INTEL

result;   detected but security is on until dos boots when plugged  in kbd port (bottom one). Security is off when plugged in mouse port. (top ps2 connector)

•	NCR H0-150-std RS3000

result;  fails to be detected except when plugged in alone on the mouse port (top connector)

•	Cherry AT European 102 key

result;  works fine in any port

•	Keytronics EP3435XTAT

result;  works fine in any port

•	NCR and Cherry keyboards violated reset timing specs


FAST IDE PIO modes & DMA modes not functional  2241	- CLOSED

Problem:  Customer reports only mode 0 works.

Resolution:  Default in SCU is CHS, if drive is LBA, system will not recognize full HDD capacity. FAST IDE PIO mode is not supported with our disk drive controller on the isa/eisa bus (AIP).  This feature will be removed from setup and the scu in the next Implemented BIOS/SCU.  BIOS 1.00.11.BI0 and SCU 3.11 / 39.


Unreliable XMS Memory Error with HIMEM.SYS  2484 - CLOSED

Problem:  The problem seen was caused by forcing a .CMS file with a larger memory config. over one with less memory actually available. Bios reported the actual memory size, but did not report a memory decrease (which it does with Rel 1.00.06). When Himem.sys was loaded, it produced an error message;

        ""Possible unreliable XMS Memory Location at 4100004h"" (68,157,444d).  No CMOS error was reported, and the Bios did not prompt the user to run setup due to a memory size decrease. Was only able to clear this by clearing CMOS. Running the SCU and flashing up the BIOS did not clear this problem.

Resolution:  Fixed in SCU 3.11 / 39.


SCSI BIOS gives 2nd Data Drive > 1G Warning Message  2538	- CLOSED

Problem:  SCSI BIOS v1.19s6 gives a Data Driver > 1GB Warning message with BANYAN 6.0 disk drives that are bigger than 1GB.

Resolution:  Fixed in BIOS 1.00.11.BI0.


SCU does not manage IDE IRQ properly  2555 - CLOSED

Problem:  When re-enabling IDE (after disabling IDE to test Server Monitor Module(SMM) IRQ14 usage), SCU does not indicate IDE and SMM are both assigned to IRQ14.  Allows configuration; does not appear to impair IDE operation when not using SMM interrupts.  SCU indicates IDE is still disabled, but system boots from IDE.  SCU does not allow automatic configuration.  Only changing SMM's interrupt allows SCU to use automatic peripheral configuration and (from user's viewpoint) re-enable IDE.

Resolution:  Fixed in SCU 3.11 / 39, make sure to disconnect drive from IDE cable to get IRQ released.


LCD Display comes up enabled after CMOS clear  2585	- CLOSED

Problem:  According to the SCU, the LCD Display comes up enabled after CMOS clear, should be disabled.

Resolution:  Fixed in BIOS 1.00.11.BI0.  LCD is now disabled by default (when cmos/nvram  is cleared).  You now must enable it with the SCU (ie for Magellan).


SMIs occurring with SMP configuration creates system hangs  2619	- CLOSED

Problem:  When an SMI occurs with 2 processors installed in the system, a hang condition may ossur.

Resolution:  Fixed in Fab 7 baseboard.


PCEB register 46h initialized with 64K hole at 1Meg  2624 - CLOSED

Problem:   Under inverstigation.

Resolution:  Fixed in BIOS 1.00.11.BI0.


Orchid Kelvin EZ PCI video adapter incompatible on ALTServer 2737- CLOSED

Problem:  This particular video adapter has known problems on numerous Intel platforms.

Resolution:  Intel has contacted the manufacturer for an analysis and upgrade. These cards are non-compliant and will not be supported.


ALTServer fails to recognize the #9GXE 64 or #9 FX Motion 531 video cards 2738 - CLOSED

Problem: When the #9GXE 64 or the #9 FX Motion 531 PCI video cards are installed in an ALTServer system, the system returns an audible error that indicates no video cards present.

Resolution: These video cards do not decode the address bus correctly whenever the video RAM and ROM are assigned 4xx0000h apart in physical memory.  These cards are non-compliant and will not be supported.


Undetected data corruption in on-board SCSI  1625 - Closed

Problem:  The "Disk grind" test ran 85 hours over the long weekend with a wide Seagate drive on each of two NCR 8251S PCI SCSI cards, one on each PCI bus, and a narrow drive on each of the on-board AIC-7870's.  The test loop consists of copying some files, then comparing them twice, repeated indefinitely.  One instance of this test ran between the two wide drives on the NCR cards, and another independent instance ran between the two narrow drives on the 7870's.  After about 60 hours, data corruption occurred during one of the compare operations between the 7870's.  One file was garbled starting at an offset of 32769 bytes from the start of the file (at a sector boundary) for a length of at least 20 bytes.  The immediately-preceding comparison of the same two files had correctly found them identical.  No OS or hardware error report appeared in the test log.

Resolution:  This was resolved with improvements in the testing S/W and new drivers from the vendor.


Customer-supplied soft reset program locks ALTServer  1632 - CLOSED

Problem:  Any customer-supplied routines that perform port 64 and port 92 soft resets will lock system when run.  When the system hangs, an interrupt is pending at the processor input but is never serviced.  It seems that the probable cause is the local APIC not being initialized correctly.

Resolution:  Investigation revealed the test program was not designed for MP systems.  They do not reprogram the processor apic before soft reset.  They also use the stack which cannot be used in soft reset.  Customer rewrote there code.


Windows* 3.1 with #9GXE, screen garbled  1739 - CLOSED

Problem:  When running in Windows 3.1 with #9GXE video card, on-screen characters and images are garbled and distorted.  Found in setups of  800x600x256 & 1152x870x256.

Resolution:  We will not fix


Some SCSI devices cannot support 10.5 MB/s transfer rate  573 -CLOSED

Problem:  Per Adaptec, this is a 7870 REV B part problem that will hang the SCSI bus.  A baseboard that uses a 42MHz crystal means that instead of 10MB/sec transfer rate, they're actually trying to run at 10.5MB/s (which most Quantum drives cannot handle).

Resolution:  REV C 7870 parts which require a 40MHz crystal will fix this problem. The ALTserver product rolled the REV. C part into Fab 7.  Prior to this Fab, the work around is to set transfer rate to 8MB/sec maximum.

Quantum 1080S does not work at 10MB/sec transfer rate, does work correctly at 8MB/sec transfer rate.

Additional SCSI Devices which have had problem at the 10 MB/s setting:

Quantum 1080S 1GB Hard Disk                                                BIOS fails

Fujitsu M2694ESA 1GB Hard Disk                                            Netware Fails

Some Maxtor XT4000 Series (5.25"" FF, depends on F/W)        BIOS fails

Some Maxtor XT8000 Series (5.25"" FF, depends on F/W)        BIOS fails

Seagate ST31200N 1GB Hard Disk                                             SCO fails

Some Conner CFP1060E drives may fail in fully configured systems.


Onboard parallel port does not show up when external port installed  1054	-
CLOSED

Problem: If the onboard parallel port is enabled in BIOS Setup (Auto or Manual), and an offboard parallel port card is installed to a different IRQ, address, etc., the off-board port shows up as LPT1 and the onboard one does not show up at all.

Resolution:  The AIP has a bug in it where it does not latch data sent to it.  The BIOS checks the status on bootup to see if the port is in use and puts the I/O address in the BIOS data area.  This checking has been removed so that if something is on the port while we are going through POST it does not fail the readback and remove it from the BIOS data area.  This resolution will be rolled into the release of the BIOS 1.00.11.BI0.


Adaptec* 1532P resets to IRQ6 each time server is rebooted   1542	CLOSED

Problem:  Errors occur when using Plug-and-Play Adaptec* 1532P SCSI controller card because it is reset to IRQ 6 each time the server is rebooted.

Resolution:  Closed: This turns out to be an ADAPTEC 1532P problem since the switch for disabling the floppy controller on the card does not free IRQ 6 and/or ports for floppy controller. After extensive discussions with Adaptec regarding the 1532P, a low cost ISA Plug-n-Play card.  This card fails to install properly on ALL Intel platforms.  Specifically, every time a system re-boots, the card resets itself to default values. Because of low volume shipment of this card, Adaptec would prefer not to spend time finding the problem nor implement a fix.  Therefore this card will not be supported on Intel platforms and we recommend the use of the Adaptec 1542CP card as a  replacement.


PCIDiag test reports Orphan Vendor and Device ID   1573 - CLOSED

Problem:  PCIDiag test reports an Orphan Vendor and Device ID when run on the server with a 100MHz Pentium® processor.

Resolution:  This is a Cirrus Logic*  video BIOS  problem. This BIOS  was designed to be used by several different Cirrus Logic devices, and responds with a device ID for one of the other devices in the family.  This is a functional consideration for this product and has no effect in any known operation.


Zynx 312 diagnostic prints nonsense on ALTServer  2040 - CLOSED

Resolution:  The Cirrus video BIOS ver 1.22 does not have enough space to fit the 8x16 font which vga mode 12h uses.  You must first load the tsrfont.com program from Cirrus to be able to see these fonts.  This file is on the Cirrus Driver diskettes (disk 2 of 2) shipped with the ALTServer systems.


Test Time for Windows NT Tape Test takes a long time  1829 - CLOSED

Problem:  The system passes the Windows NT 3.5 HCT suite on all three tape I/O tests, one each for QIC 117 (floppy controller), QIC SCSI, and SCSI DAT drives.  The test time takes 50% to 100% longer on ALTServer than on a 486-based system.

Resolution:  Bad test script.


SONY CDU55S CD-ROM hanging using UnixWare 1.02S driver  565  CLOSED

Problem:  This issue may be related to Adaptec UnixWare driver - driver does NOT use config data for device initialization, but uses chip default values - WIDE SCSI, Sync 10MB/s xfer, disconnect/reconnect.  Many CD-ROMs report at rates that they cannot support, i.e., 5MB/s when they can only do Async transfer, etc. Using version 1.02S of Adaptec's 7800 UnixWare driver, the driver was hanging in initialization while downloading the microcode, and after some fumbling, the problem was caused by the presence on the SCSI bus of a Sony CDU55S CD-ROM reader. Evidently something about the download is customized to the particular set of devices found on the bus, and this driver does not know how to handle this particular model of CD-ROM drive.  The hang occurred earlier with the Sony's SCSI ID set to 1 than when it was set to 5.

Resolution:  Re-installed using Adaptec driver 1.20s, installation proceeded to completion. System operated normally after installation


Adaptec 1542CP requesting wrong interrupt  1298	CLOSED

Problem:  Requesting IRQ5 for floppy, need to use IRQ6.

Resolution:  Currently the use of IRQ6 does permit the floppy drive to operate.  Adaptec has been notified.


Network adapters using the PLX 9032D chip may fail  1371 CLOSED

Problem: When an EtherExpress 32 card configured with netconfig to IRQ10, connector type BNC, and Flash Memory Range D000-D1FF was installed, UUT could not connect to a remote system with rlogin or ping commands, and remote systems did not recognize the UUT.  Intel's Network Products Division and PLX Technology says that this is a known bug with any Intel NIC card that uses PLX's EISA 9032D used in Intel's PRO/100 EISA and FLASH32 EISA bus master adapters.  This configuration will result in server malfunction or data compare errors in Intel's server-based PCI/EISA systems.

Resolution: Intel's Network Products Division and PLX Technology says that this is a known problem with any NIC card that uses PLX's EISA 9032D. Currently this devices is used in Intel's PRO/100 EISA and FLASH32 EISA bus master adapters.  This configuration may result in a server malfunction or data compare errors in Intel's server-based PCI/EISA systems. Do not use NICs that use this PLX device as their LAN controller.


NDIS driver causes Lantastic to lose connection during first 1 MB file transfer  1537 CLOSED

Problem:  With NDIS, Lantastic 6.0 (Peer To Peer) and Intel TokenExpress Pro ISA (tpro.dos,v1.01), the network loses connection during the first 1 MB file transfer, first iteration.

Resolution:  Intel's Network Product Division is aware of this problem and recommends use of Intel TokenExpress 16 ISA (olitok.dos,v4.0) and Intel TokenExpress Pro EISA (olitok32.dos,v4.01).


Intel SMM does not allow shared memory use, interrupts, and DMA  1614 CLOSED

Problem:  The current .cfg file for the Intel Server Monitor Module does not allow shared memory use, and interrupts and DMA are not working.

Resolution:  Fixed in BIOS 15, SMM software release 1.2


DTC2290 EISA IDE controller causes an unresolvable resource conflict  1919 CLOSED

Problem:  The DTC2290 EISA IDE controller causes a ""Static Device Resource Conflict"" at system startup.

Resolution:  Hardware not available.  Vendor no longer manufactures nor supports this card.


3-mode floppy failure when IDE not plugged in  2101	CLOSED

Problem:  If an IDE hard drive is not plugged in, then the 3 mode floppy fails.

Resolution:  Closed: Microsoft's 3-mode floppy driver, 1024FD.EXE, is broken.  A new driver, 1025FD.EXE, is now available which fixes the problem.


PCI bridge resource allocation problem above 1 gigabyte  2102	  CLOSED

Problem:   If a resource requires more than 1 gigabyte of memory on a PCI bridge, it will not get it.

Resolution:  Closed: Under investigation, currently we know of no cards with this requirement. Fixed in rev. 1.00.05 of the BIOS and passed our compatibility run on 4/28/95.


120 Mhz CPu speed reported incorrectly in setup  2138	CLOSED

Problem:  120 Mhz processors are identified as wrong speed in setup.

Resolution:  BIOS 1.00.15.BIO correctly reports processor speed up to 166MHz.


ISA bus mastering to PCI video fails when using LANDesk® Server Monitor Module  2140	CLOSED

Problem:  Using a LANDesk® Server Monitor Module board, when attempting to read the video memory on an ALTServer using ISA bus mastering, every even-numbered byte was read correctly but odd-numbered bytes were returned as FF.  LANDesk Server Monitor Module is an 8-bit ISA bus master.  When attempting to write to video memory, seemingly random bytes are written, others are not.

Resolution:  Use "View Console" rather than "Get DMA image" from SMM management console.


PCI arbitration problem   2446	CLOSED

Problem:  While running the Exchange test on NetWare3.12J, using a Toshiba PCI LAN card that's using AMD's PC net LAN controller, then results show Memory Error on ALTserver that's used as a client. ALTserver is used for both server and client. Exchange test is a test that's included in the LAN adapter certification test kit from Novell. The root cause of this problem was found to be to be the PCEB's PCI arbiter being set to fixed priority mode. It seems that the CPU has a priority in this mode. If the CPU accesses the CL5430 VGA chip and the LAN card asserts REQ, then the GNT signal is not asserted until about 53-55 usec.  If the PCEB's PCI arbiter is set to rotating priority mode, this delay reduces to about 500nsec.

Solution:  Investigation has shown that rotational priority doesn't have any negative side effects like errata or performance.  Therefore this priority change will be implemented in the next release of the BIOS. 1.00.15.BI0


ALTServer baseboard fails password selections portions of the BIOS test  2508 CLOSED

Problem:  The ALTServer baseboard fails the password selections portions of the Intel BIOS confidence test. After entering a password via CMOS setup on the ALTServer baseboard, and subsequently rebooting, if the correct password is entered, then the[BACKSPACE] key is pressed once, then the [ENTER] key is pressed, the password is accepted.  In CMOS setup, the password is entered and confirmed.  The system is re-booted, and the user is prompted for the password.  If the correct password is entered, and than the backspace key is pressed, one less ""*"" than the correct password is displayed. But, if the [ENTER] key is pressed at this point, the user will still be allowed to access the system.

Resolution:  Fixed in BIOS 1.00.11.BI0.


ALTServer Testview (CPU) Anomaly  2314 CLOSED

Problem:  Testview reports the 100 MHz CPU at 220+ MHz. This is a recurring error, but it does happen only 0.34% of the time. Note that this error has been seen only on one unit out of 30 units. The percentage value was computed  from 13 errors out of 3733 runs of the mentioned unit.

Resolution:  Fixed in BIOS 1.00.11.BI0.


ECP parallel port needs selectable DMA  2250 CLOSED

Problem:  At this time, ECP mode is not supported by our BIOS.  As soon as a fix is implemented for the BIOS we will provide the needed setup selections in the SCU

Resolution:  It will be in Fab 7, BIO 1.00.15.BI0


ALTServer IBM TR II will not initialize (NDIS driver problem) 2287 CLOSED

Problem:  Using LANtastic 6.0 (Peer To Peer) the IBM Token Ring II ISA will not initialize. This problem has also been seen in Net BIOS and Banyan.

Resolution:  Currently it has been discovered that additional configuration must be performed to resolve this conflict. Once you've installed Lantastic with the NDIS driver that comes with the TR II card, go in and edit the PROTOCOL.INI to modify the I/O base address. At boot time Lantastic sees the TR II card, configures without error, then sits waiting for the client to come on-line without attaching to the MAU itself. Since this card works with other drivers, the NDIS driver that ships with the card is suspect at this time.


SCU Can't Lock EISA Resources  2256 CLOSED

Problem:  The MCS configuration utility provided the ability to 'Lock' the resources of EISA devices.  The AMI SCU does not have this ability.  From EISA SPECIFICATION, Version 3.12, from BCPR Services "The EISA Configuration Utility allows users to lock boards so that the selected choices (and resources) of a board are not changed when new boards are added to the system. ....""

Resolution:  Fixed and verified Fab 7, SCU 3.11 / Overlay 39, BIOS 11


Cannot boot from Future Domain PnP 1630 SCSI  2345 CLOSED

Problem:  Also difficult to get the card recognized. Had to install it on another system just to get it's PnP software to recognize it. Future Domain PNP 1630 SCSI Controller. The Future Domain PNP 1630 SCSI Controller failed to work with the Intel ALTServer. At first we couldn't get the card to be recognize by the ALTServer. The server failed to boot up and hang out the server so we downloaded from Future Domain the utility ""PNPCFG.EXE"" The Future Domain PNP 1630 SCSI Controller card Default settings are as follows:

Base Memory Address: CA000H  ===> Alternative: C8000H, CE000H, DE000H. Interrupt: IRQ 5  ===> Alternative: IRQ 10, 11, 15.

Base I/O Address: 150H  ===> Alternative: 140H, 160H, 170H

Resolution:  Fixed and verified Fab 7, SCU 3.11 / Overlay 39, BIOS 11


SMI not active on ALTServer  2295 CLOSED

Problem:  System Management Interrupts caused by the system monitoring block in INCA are not enabled for Hobbes detection; SMI needs to be enabled in INCA and ESC.

Resolution: Fixed in Fab 7.


3COM TokenLink III will not initialize 2288 CLOSED

Problem: Using LANtastic 6.0 (Peer To Peer) the IBM Token Ring II ISA will not initialize. This problem has also been seen in Net BIOS and Banyan. Using AI-NDIS (AILANBIO to NDIS) driver V2.14 (C) Copyright...problems were seen during the reboot sequence just after the LANtastic configuration takes place.  The error message that appeared looked like this: ERROR: Unable to bind to module TLNK3_NIF

Resolution:  This is an NDIS driver problem.


STB Velocity 64 PCI adapter fails at boot  2389 CLOSED

Problem:  The adapter will hang the system immediately after POST is initiated. The system passes the initial 64k RAM test, before it hangs the system.  The STB Velocity 64 PCI adapter utilizes a S3 Vision 968 graphics chip. STB Powegraph works with no problems and utilizes a S3 Trio 64 graphics chip. The customer reported that The STB Horizon works with no problems.

Resolution:  Video solutions based on the S3 Vision 968 chip are not compatible with this system.


ECP Parallel option inoperable 2630 CLOSED

Problem:  Selecting the ECP Parallel port option in the BIOS setup has no effect.

Resolution:  Fixed in Fab 7 (PBA# -30x) BIOS 15.


SCU and OVL may produce dead-lock when resolving conflicts 2768	CLOSED

Problem:  In an attempt to resolve a add-in card resource conflict, the ALTServer system goes into a endless loop due to some unresolvable conflicts.  If an on-board devices request a resource in-use by another device the SCU will has trouble resolving the conflict.

Resolution: Fixed in SCU 3.21 / OVL 1.01


PCI devices getting assigned pre-allocated memory 2875 CLOSED

Problem:  It has been noted that the BIOS is inadvertently placing the VGA device in a conflict with the ESC/IOAPIC. This was discovered in a clearing of CMOS and an attempt to view the VGA's Current Configuration.

Resolution:  Fixed in BIOS 15.


Static Device Resource Conflicts 2883 CLOSED

Problem:  Using the ALTServer System Configuration Utility, 3.11.39,  to add a card that has RAM memory and ROM memory in the same 16K block, the BIOS will display a "static device resource conflict".  If the 16K memory block has shadow enabled, this is a valid error.

Resolution: Fixed in BIOS 15


Removing an EISA card may delete ISA entries  2427 CLOSED

Problem:  Removing an EISA card physically from the system may cause ISA cards previously added to be ignored.  The ESD data for the ISA card is still in the NVRAM but it appears that the AMISCU ignores it if it finds an invalid configuration for an EISA slot.

Resolution:  Fixed in SCU 3.21 / 1.01


Thomas Conrad TC4045 fails NWTEST in Netware 4.10  2407 CLOSED

Problem:  The LAN driver for the card would load and IPX would bind to the card. The client could attach to the TC4045 without difficulty. Upon starting NWTEST, Read errors would immediately appear during the Read/Write portion of NWTEST. The errors would continue until the maximum of 50 errors was reached. At that point, NWTEST would halt.. This occurs using either of the listed drivers for the card.

Resolution:  To fix this problem, the card's driver needs to be configured for under 16MB manually and it is not documented as seen in Compatibility Test.


Removing EISA video card causes system to hang  2248	  CLOSED

Problem:  Compaq Q-Vision card installed through SCU.  Remove card before removing via SCU and the system won't boot to on-boards video.

Resolution:  Fixed in BIOS 15


Failed to recognize several video cards  2526  CLOSED

Problem:  Using the following cards; #9 GXE 64 CS=S3 86C968-P. #9 Motion 531 CS=S3 86C868-P. STB PowerGraph 64V CS=S3 86C765-P.  Digital Bahama 64 CS=S3.  Theses cards listed above failed to be recognized by the system. An audible no video beep code was heard and no video was produced.

Resolution:  Video solutions based on the S3 Vision 968 chip are not compatible with this system.


General Product Information

Product Order Code List

Packing lists

Orderable Spare Parts

ALTServer Platforms User-Installable Upgrades

iPTL Tested Product List

Frequently Asked Questions (FAQ)

Configuration Tips

Setup information

Installation Instructions


Product Order Code List

C1F90A2M16      	-  Columbus chassis, ALTServer baseboard, 256k Async cache, 16MB memory, 1-90 Mhz processor, 230W Power Supply

C1F75A2M8   	-  Columbus chassis, ALTServer baseboard, 256k Async cache, 8MB memory, 1-75 Mhz processor, 230W Power Supply

C1F100A2M16	-  Columbus chassis, ALTServer baseboard, 256k Async cache, 16MB memory, 1-100 Mhz processor, 230W Power Supply

C1F120A2M16	-  Columbus chassis, ALTServer baseboard, 256k Async cache, 16MB memory, 1-120 Mhz processor, 230W Power Supply

C1F133A2M16B	-  Columbus chassis, ALTServer baseboard, 256k Async cache, 16MB memory, 1-133 Mhz processor, 300W Power supply

RISERWEXTBLK	- Wide external SCSI I/O connector card (10 pack)

RISERNEXTBLK	- Narrow external SCSI I/O connector card (10 pack)

RISERATBLK	- All headers except PS/2 Keyboard external & Narrow internal SCSI (10 pack), no cables

RISERWINTBLK	- Wide internal SCSI I/O connector card (10 pack)

ALTCPUKIT	- Second processor heatsink assembly upgrade kits (10 pack)

SERVERMON	- Server Monitor Module, Netware 3.1x, 4.1x agents and Workstation Monitoring Console

XXPCIRAID4	- 2 channel PCI RAID controller with battery backup, 4MB cache, fault and LED cable

OEMGLDA	- All software and manuals, electronic copies


Packing lists

Columbus System

Magellan System


Columbus System

Altair Baseboard with memory & CPU as per order code

3-1/2" Floppy Drive & Cable

Hard Drive Bay (6-1" HDD)

230W Power Supply

Accessory Kit - Columbus

Item	Qty	Intel Base P/N	Description
SCSI cable	1	620333	9 connector narrow for 8 devices
IDE cable	1	619993	3 connector for 2 devices
Drive Rails, Left Hand	3	616738
Drive Rails, Right Hand	3	616738
Ground Clips	7	516398	Used in 5-1/4" bays
Country Kit - Columbus

Item	Intel Base P/N	Description
Power Cord	108520	US = Gounded/125V
543x Video Drivers 1of2	635487	v.1.22c
543x Video Drivers 2of2	635488	v.1.22c
Adaptec EZSCSI LITE	636495	v3.11s
Adaptec SCO/UXWR	642009	v1.10s3
Adaptec NVL/OS2/NT	642011	v1.10s3
Adaptec UXWR	642010	v1.10s3
Server Diags	640936	v3.17
Server Diags Help	640938	v3.17
System Configuration Utility	644121	v3.11 /  Overlay 39
LANDesk Server Control	639896	v1.01
Product Guide	630547
SCSI Software Guide	627538
LSC Installation Guide	636069
Quick Installation Card	618728


Magellan System

Altair Baseboard with memory & CPU as per order code

3-1/2" Floppy Drive & Cable

Wide SCSI cable from I/O Riser to hot swap bay

Narrow SCSI cable from baseboard to upper peripheral bay

Plastic Hard Drive Carrier for Hot Swap Bay (6)

525W Power Supply

Accessory Kit - Magellan

Item	Qty	Intel Base P/N	Description
Drive Rails, Left Hand	4	616738	(-001)
Drive Rails, Right Hand	4	616738	(-002)
Ground Clips	8	516398	Used in 5-1/4" bays
Country Kit - Magellan

Item	Intel Base P/N	Description
Power Cord	108520	US = Gounded/125V
543x Video Drivers 1of2	635487	v.1.22c
543x Video Drivers 2of2	635488	v.1.22c
Adaptec EZSCSI LITE	636495	v3.11s
Adaptec SCO/UXWR	642009	v1.10s3
Adaptec NVL/OS2/NT	642011	v1.10s3
Adaptec UXWR	642010	v1.10s3
Server Diags	640936	v3.17
Server Diags Help	640938	v3.17
System Configuration Utility	644121	v3.11 /  Overlay 39
Flash Update Utility	633733
LANDesk Server Control	639896	v1.01
Product Guide	630547
SCSI Software Guide	627538
LSC Installation Guide	636069


Orderable Spare Parts

Spares - Columbus

Spares - Magellan


Spares - Columbus

P/N	Description

C1F616843      CHASSIS ASSY,INTEL - "Columbus"

C1F202123      230 WATT BABY AT Power Supply

C1F628699      300 WATT BABY AT Power Supply

C1F634425      PBA,SYS FRONT PANEL

C1F620311      Cable Assembly,FLOPPY

C1F629290      FAN,ASSY,VARSP,100CFM,RD

C1F621980      RISER CARD,I/O, WIDE SCSI EXTERNAL

C1F621981      RISER CARD, I/O, Narrow SCSI EXTERNAL

C1F621982      RISER CARD, I/O, AT F2 - Header connectors only except for Keyboard

C1F629183      RISER CARD,I/O,INTERNAL WIDE SCSI - Comes standard with sys.

C1F620323      OPT,ACCESSORY KIT,PRPHL - Drive rails, cables, etc

C1F620324      OPT,CNTRY KIT,COL/ALT - S/W Drivers & Manuals

C1F627164      PRPHL BAY ASSY,HDD,6 - Swing out Hard drive bay

C1F622730      ASSY,PLATE,I/O - Metal mounts to chassis


Spares - Magellan

P/N	Description

MG5F	611494	KEY & LOCK ASSEMBLY
MG5F	611494M	KEY & LOCK MASTER
MG5F	617604	525 W POWER SUPPLY
MG5F	620322	PERIPHERAL MOUNTING RAIL
MG5F	622732	CABLE, PWR SUP to BKPLN
MG5F	623979	ACCESSORY KIT (RAILS/CLIPS)
MG5F	624091	BASEBOARD MOUNTING PANEL
MG5F	624118	BASE FOOT
MG5F	624570	CHASSIS ASSEMBLY
MG5F	624797	CABLE, BASEBOARD to FRONT PNL
MG5F	624855	CABLE, BASEBD,CNT'L to BKPLN
MG5F	624856	CABLE, BKPLN to UPPER BAY
MG5F	624857	CABLE, BKPLN to FRONT PANEL
MG5F	624860	CABLE, JUMPER BKPLN to 6 DRIVES
MG5F	625114	CHASSIS INTRUSION SWITCH & CBL
MG5F	625634	DRIVE TRAY
MG5F	625651	UPPER FRONT BEZEL
MG5F	625652	LOWER FRONT BEZEL
MG5F	626357	DRIVE LED PANEL
MG5F	627199	CABLE, BASEBD to FLOPPY DRIVES
MG5F	628960	PERIPHERAL RAIL CLIP
MG5F	629290	FAN (100CFM)
MG5F	631574	SCSI BACKPLANE
MG5F	632397	CABLE, LCD
MG5F	635025	FRONT PANEL BOARD
MG5F	635528	COUNTRY KIT
MG5F	625719	SERIAL BOARD, Metal plate I/O panel
MG5F	629183	RISER BOARD
MG5F	631039	SCSI CABLE, WIDE


ALTServer Platforms User-Installable Upgrades

(FaxBACK document 4520)

Related Topics:

Processors

System Memory

Secondary (L2) Cache Memory

Graphics DRAM


Processors

Single-processor ALTServer platforms can be upgraded by using a processor with a faster clock speed. The baseboard is designed to operate with 75, 90, 100, 120*, 133* or 167* MHz Pentium(r)  processors.  Dual-processor configurations must always have Pentium processors with the same clock installed in the two Zero Insertion Force (ZIF) sockets.  When upgrading processors, it is also important to ensure the CPU Speed jumpers a set correctly.   The second proccessor will require a heatsink compatable with the socket on the ALTServer baseboard.  In addition, a conductive compound should be used between the processor and the heatsink.  This assembly can now be ordered in packs of ten from the factory, order code ALTCPUKIT.

The second processor upgrade on the ALTServer baseboard must match exactly the following characteristics of the primary processor:  External Clock Speed and  Internal Clock Speed.   Use the following table when contacting your service provider for the second processor.  To determine what processor to use in the secondary socket, use the table below to match the Product code and S-Spec number on your installed processor to the secondary processor.  The Product code / S-Spec number can be found on the under side of the processor.  Use the table below to determine the S-Spec level of your installed processor by matching the "ALTServer Processor Assembly Number" (labeled on the processor heatsink assembly) to the correlating product code.  Note on Overdrive(r) processor support:  Only the secondary CPU site on the ALTServer baseboard supports future Pentium(r) Overdrive Processor upgrades because this processor will not support the multiprocessing funtionality built into the baseboard.

The ALTServer ships with only the "C-2" stepping and above of the P54C Pentium Processor.  This stepping allows a STD voltage part to operate in a VRE system.  Therefore, as of  Fab 6 baseboards, all ALTServers will have only VRE voltage settings for the processor (J3A, pins 1-2).  Either a STD or a VRE specified part can be used as the second processor.  And...don't forget the heatsink!

ALTServer Dual-Processor Upgrade Matrix

Installed  & Secondary Processor  Product Code	ALTServer Processor Assembly Number (For indication only, this is not an orderable spare part)	Installed Processor Details Internal Speed, External Speed, Processor/Stepping,	Baseboard Clk Ratio* Jumper Settings	Baseboard Speed Jumper Settings
A8050250-75 SX969	634656-001	75Mhz W/50MHz ext. bus, P54C/C-2	J1A pin 1-2 J2A pin 1-2	J6B pin 2-3 J5B pin 1-2
A8050260-90 SX968	634657-001	90MHz W/60MHz ext. bus, P54C/C-2	J1A pin 1-2 J2A pin 1-2	J6B pin 1-2 J5B pin 1-2
A8050266-100 SX963	634658-001	100MHz W/66MHz ext. bus, P54C/C-2	J1A pin 1-2 J2A pin 1-2	J6B pin 2-3 J5B pin 2-3
A8050266-100 SX970	634658-001	100MHz W/66MHz ext. bus, P54C/C-2	J1A pin 1-2 J2A pin 1-2	J6B pin 2-3 J5B pin 2-3
A8050260-120 SK110*	638694-001	120MHz W/60MHz ext. bus,	J1A pin 1-2 J2A pin 2-3	J6B pin 1-2 J5B pin 1-2
A8050266-133 SK106*	639152-103	133MHz W/66MHz ext. bus, P54CS/B-1	J1A pin 1-2 J2A pin 2-3	J6B pin 2-3 J5B pin 2-3
A8050266-166 SY017*	647693-001	166MHz W/66MHz ext. bus, P54CS/C-0	J1A pin 2-3 J2A pin 2-3	J6B pin 2-3 J5B pin 2-3
*The 120MHz  & faster processors require a FAB 6 or newer baseboard, contact your service providor for details.


ALTServer Help - ALTServer Platforms User-Installable Upgrades - System Memory
System Memory

Eight 72-pin sockets on the baseboard will accept up to 256 MB of system memory using 70 ns fast page SIMMs of the following sizes: 1M x 36 (4 MB), 2M x 36 (8 MB), 4M x 36 (16 MB), and 8M x 36 (32 MB) SIMMs. The minimum memory size is 2 MB and the maximum memory size, using eight 32 MB SIMMs, is 256 MB.

The eight SIMM sockets are arranged as four banks (Bank 0, 1, 2, and 3) with each bank consisting of two sockets. Both SIMMs in a bank must be of the same memory size and type, although separate banks may have different sizes and types of memory installed. In some instances, for electrical reasons only, it may be essential to populate Bank 0 first.

System memory begins at address 0 and is contiguous (flat addressing) up to the maximum amount of system memory installed. The only places where system memory is non-contiguous is in the ranges from 00080000 - 000FFFFF (the DOS compatibility region) and 00F00000 - 00FFFFFF (the system BIOS region). Memory regions holes at any other location may result  in DRAM beyond that hole unusable.

Because of the constant changes in the memory market, Intel engineering continually analyzes SIMMs by comparing information in the SIMM vendor's data book with the required timings on the ALTServer baseboard. Memory also is tested by either Intel or by respected OEM customers. A list of compatible/qualified SIMMs and those known to be incompatible is maintained on the Intel FaxBack* service (1-800-628-2283).

The following tables list SIMMs that are known to be compatible with the specified Intel platforms. SIMMs that are not listed also should function properly as long as their specifications are compatible with the devices listed below. In general, SIMM devices that are faster than those specified for a given platform will work although no extra performance will be realized.  The SIMM devices shown are categorized according to three levels of qualification:

1.  Intel Tested and Approved:  The SIMM has been electrically tested by Intel engineering and is known to be compatible with the ALTServer server basebaord.  Rigerous envinronmental testing, voltage margin, shock, and vibration testing were conducted on these SIMM devices.  In addition, the vendor has met or exceeded Intel's product change, quality control, and availablity requirements.  The SIMM is on the Intel Approved Manufacturing  List.

2.  Intel Tested:  The SIMMs have been analyzed by the data sheet and have been electrically tested.  A small sample ( normally 12 SIMMs) have been tested by Intel engineering across voltage and temperature margins on the ALTServer baseboard and/or memory modules.  The SIMMs are not on the Apporved Manufacturing list, but  are considered appropriate for use in the ALTServer server system.

3.  Customer Tested:  The SMM has been electrically tested by an OEM customer and is reported to be compatible  with the ALTServer server platform system.

Intel recommends that SIMMs listed as (1) Intel Approved and Tested or (2) Intel Tested be used to ensure reliable system operation. SIMMs not listed or listed as (3) Customer Tested can be used; but, in the event of unreliable system operation, the SIMMs should be replaced with SIMMs tested by Intel (1 or 2) to determine whether the SIMMs are causing the problem.

IMPORTANT NOTE

SIMM devices with gold contacts should NOT be placed into SIMM sockets with tin-lead contacts or vice-versa. Mixing dissimilar metal contact types has been shown to result in unreliable memory operation. For more information, see FaxBack document 4229.

Vendor Contacts (phone numbers are provided for convenience and may change without notice. Current as of 1/95).

IDT          www.idt.com	1-800-345-7015	NEC	415-960-6000*
Fujitsu	408-922-9000*	Samsung	408-954-7000*
Cypress  www.cypress.com	408-943-2600	Simple Technologies	714-558-1120
Hyundai	408-473-9200	Smart Modular	510-623-1231
Micromodule  Systems	408-973-1043	Texas Instruments	214-644-5580
Micron	208-368-3900*	Toshiba	503-629-0818*
MPM	800-899-4676	Corsair Microsystems	503-643-8307
 SIMMS - 4MB, 8MB, 16MB, and 32MB, Parity, Tin-lead contacts

(These parts are not available directly from Intel, the Tracking number is for Internal purposes only)

Manufacturer	Part number	Intel Tracking #	SIMM Type	Size	Qual Lvl
Samsung	KMM5361003C-70	634001-570	1Mx36	4MB	1
Hyundai	HYM536100AM-70	"	1Mx36	4MB	1
T.I	TM124MBK36A-70	"	1Mx36	4MB	1
Toshiba	THM3610B0ASG-70	"	1Mx36	4MB	1
Samsung	KMM5361203AW-70	"	1Mx36	4MB	1
Smart Tech (ti&fu)	SM5361000-70	"	1Mx36	4MB	1
Smart Tech (fujitsu)	SM5361000-70	"	1Mx36	4MB	1
Micron Tech.	MT9D136M-70	"	1Mx36	4MB	1
Smart Tech (fujitsu)	1M1N360-70JS-IS	"	1Mx36	4MB	1
Samsung	KMM5361003C-60	635239-001	1Mx36	4MB	1
Samsung	KMM5362003C-70	634002-570	2Mx36	8MB	1
T.I.	TM248NBK36R-70	"	2Mx36	8MB	1
Smart Tech (m&h)	SMI5362000-70	"	2Mx36	8MB	1
Smart Tech(Sam)	SM5362000QC-70	"	2Mx36	8MB	1
Smart Tech (n&h)	SM5362000-70	"	2Mx36	8MB	1
Toshiba	THM3620C0AS-70	"	2Mx36	8MB	1
Samsung	KMM5362203AW-70	"	2Mx36	8MB	1
Micron Tech.	MT18D236M-70	"	2Mx36	8MB	1
Smart Tech (ti&fu)	SMI5362000-70	"	2Mx36	8MB	1
Smart Tech (fujitsu)	2M1N360-70JS-IS	"	2Mx36	8MB	1
Smart (NEC&fu)	SMI5362000-70		2Mx36	8MB	1
Samsung	KMM5362003C-60	635240-001	2Mx36	8MB	1
T.I.	TM497MBK36Q-70	634005-570	4Mx36	16MB	1
Samsung	KMM5364103AK-70	"	4Mx36	16MB	1
Samsung	KMM5364100A-70	"	4Mx36	16MB	1
NEC	MC424000A36BE-7	"	4Mx36	16MB	1
Hyundai	HYM536410AM-70	"	4Mx36	16MB	1
Micron Tech.	MT12D436DM-70	"	4Mx36	16MB	1
Vision Tek.	VT69145.A	"	4Mx36	16MB	1
Samsung	KMM5364103AK-60	635242-001	4Mx36	16MB	1
Micro Tech.	MT12D436M-60		4Mx36	16MB	1
T. I.	TM497MBK36Q-60	635242-001	4Mx36	16MB	1
Samsung	KMM5368100-70	634006-570	8Mx36	32MB	1
Samsung	KMM5368103AK-70	"	8Mx36	32MB	1
Mitsubishi	MH8M36AJ-70	"	8Mx36	32MB	1
Mitsubishi	MH8M36BNJ-70	"	8Mx36	32MB	1
Vision Tek	VT69181.A	"	8Mx36	32MB	1
Samsung	KMM5368103AK-60	635243-001	8Mx36	32MB	1
ECC SIMM Modules

(These parts are not available directly from Intel, the Tracking number is for Internal purposes only)

Manufacturer	Part Number	Intel Tacking #	SIMM Type	Size	Qual Lvl
IBM	IBM11D4480BA-70	634005-750	4Mx36	16MB	1
Known Incompatible SIMM Modules

Manufacturer	Part Number	SIMM Type	Size	Qual Lvl
Simple Tech	STI361000A-70TTG T&G	1Mx36	4MB	FAILED
TI	TM124MBK36R-60	1Mx36	4MB	FAILED
Hyundai	HYM536200AM-60	2Mx36	8MB	FAILED
Simple Tech.	STI362000A-70TTT Tosh	2Mx36	8MB	FAILED
Vision Tek	VT69123.A	2Mx36	8MB	FAILED
TI	TM248NBK36R-60	2Mx36	8MB	FAILED
Hyundai	HYM536410M-70	4Mx36	16MB	FAILED
Simple Tech	STI364000-70TGS G&S	4Mx36	16MB	WAITING
Simple Tech	STI368000-70TGN G&N	8Mx36	32MB	WAITING
Toshiba	THM3680G0BS-60	8Mx36	32MB	FAILED


Secondary (L2) Cache Memory

The ALTServer provides an upgradeable second level (L2) cache using cache modules. Qualified cache upgrade options are available, as shown in the table below:

 Cache SRAM Memory Modules

(These parts are not available directly from Intel, the Tracking number is for Internal purposes only)

Manufacturer	Manufacturer Part Number	Intel Tracking #'s	SRAM Type	Size	CPU speed
IDT	IDT7MPV6189S15M	790075-001 790090-001 790100-001 790120-001 790133-001	Async. 3.3V	256KB	75, 90, 100, 120 & 133MHz
Corsair Micro.	C586L256K15B2-I3I0	790075-001 790090-001 790100-001	Async. 3.3V	256KB	75,90 & 100MHz
1st Tech Corp	PDM4M6189S12M	790150-001 790166-001	Async.	256KB	150 & 166 MHz
Motorola	MCM72BF32SG66	790090-002	Burst	256KB	90MHz
Cypress	CYM74SP54PM-66C	790090-002 790100-002 790120-002 790166-002	Burst	256KB	75, 90,100, 120, 133 & 166MHz
Micromodule Sys	DM-72BH32-A01-66	790075-002 790090-002 790100-002 790120-002 790133-002	Burst	256KB	75, 90, 100, 120 & 133MHz
Micromodule Sys	DM-72BH64-A01-60	790075-003 790090-003 790120-003	Burst	512KB	75, 90 & 120MHz
Micromodule Sys	DM-72BH64-66	790100-003 790120-003 790166-003	Burst	512 KB	100, 120, &166 MHz
Micromodule Sys	DM-72BH64-B01-66	790133-003 790150-003 790166-003	Burst	512KB	133, 150, & 166MHz


Graphics DRAM

Video DRAM memory can be upgraded using one 256K x 16, 70 ns, SOJ component. While some DRAM parts rated at 60 ns will function in ALTServer platforms, Intel does not warrant the use of these 60 ns parts, or assume any liability concerning the use of these parts.   Unlike the SRAM and system DRAM, we do not qualify video DRAM vendors.  The examples below have been used and have no known issues with the ALTServer baseboard.

Vendor	DRAM Part Number

SAMSUNG	KM416C256AJ-7T

SAMSUNG	KM416C256BJ-7T

MICRON TECHNOLOGY       	MT4C16257DJ-7TR

TOSHIBA CORP            	TC514260BJ-70(EL)

FUJITSU LTD             	MB814260-70PJRD

HITACHI	HM514260AJ-7T

NEC 	UPD424260LE-70 ITR

MITSUBISHI              	M5M44260AJ-7-T10

SAMSUNG 	 	KM416C256BLJ-7T

OKI SEMICONDUCTOR	       	MSM514260A-70JSTR

HYUNDAI                 	HY514260BJC-70

SIEMENS CORP            	HYB514171BJ-70

Intel Corporation disclaims all warranties and liabilities for the use of this document and the information contained herein, and assumes no responsibility for any errors which may appear in this document. Intel makes no commitment to update the information contained herein, and may make changes at any time without notice. There are no express or implied licenses granted hereunder to any intellectual property rights of Intel Corporation or others to design or fabricate Intel integrated circuits or integrated circuits based on the information in this document.

Contact your local sales office to obtain the latest specifications before placing your order. *Other product and corporate names may be trademarks or registered trademarks of other companies, and are used only for explanation and to the owners' benefit, without intent to infringe.

© INTEL CORPORATION, 1995	FaxBack document 4520 (rev 3.0, 9/11/95)


iPTL Tested Product List

A complete "compatabilty" report is available on NOTES to Authorized Individuals.

This appendix lists all of the products with which the baseboard has been tested.  It includes products found to be compatible in earlier testing runs.

When products on the following lists are marked by an asterisk (*), it indicates they failed an iPTL compatibility test.  The indicated failure may be due to a third-party problem.

Related Topics:

VALIDATED IN HARDWARE INTEROPERABILITY TESTING

USED IN CONFIGURING TEST PLATFORMS (NOT RIGOROUSLY VALIDATED)

OPERATING SYSTEMS AND HARDWARE VALIDATED IN NETWORK TESTING

SOFTWARE INCLUDING OPERATING SYSTEMS


VALIDATED IN HARDWARE INTEROPERABILITY TESTING

 Products marked with this symbol were added to the test suite specifically for these testing runs.

CD-ROM DRIVES

Creative Labs CT-531 (external, proprietary)

Mitsumi FX-001 (internal, proprietary)

Mitsumi FX-001DE (internal, IDE)

NEC CDR 74-1 (external, SCSI)

NEC CDR 260 (internal, IDE)

NEC CDR 600 (internal, SCSI)

NEC CDR 601 (internal, SCSI)

Optics Storage 800X (internal, IDE)

Panasonic CR-563B (internal, proprietary)

Plextor PX-43CH (internal, SCSI)

TEAC SuperQuad 4X CD55 (internal, proprietary)

Toshiba XM-3301E1 (external, SCSI)

Toshiba XM-3401 (internal, SCSI)

Toshiba XM-3501B (internal, SCSI)

Toshiba XM-5201B (internal, SCSI)

DISK CONTROLLERS

Onboard Adaptec 7870 (SCSI)

Onboard Intel AIP (ISA/IDE)

*Adaptec 1532P (PnP/SCSI)

Adaptec 1542CF (ISA/SCSI)

Adaptec 2740T (EISA/SCSI)

*Adaptec 2940 (PCI/SCSI)

Adaptec 2940W (PCI/SCSI wide)

*Bus Logic BT747D (EISA/SCSI)

DPT 2022 (EISA/SCSI)

DPT 2122 (EISA/SCSI)

*DTC 2290B (EISA/IDE)

Future Domain 1630 (PnP/SCSI)

Future Domain 1680 (ISA/SCSI)

Future Domain 3260 (PCI/SCSI)

NCR 8250S (PCI SCSI)

QLogic FastSCSI IR (PCI/SCSI)

Ultrastor 15C Cache 2MB (ISA/IDE)

FAX/MODEMS & MODEMS

Hayes 9600 SmartModem

Intel 14.4/14.4 Faxmodem

Intel SatisFAXtion® 100

Intel SatisFAXtion® 400

SupraFAXModem 288i

U.S. Robotics Courier Modem (28.8)

FLOPPY DRIVES

*TEAC FD-235J (3.5-in. 2.88MB floppy)

TEAC FD-505 (dual 1.44/1.2MB floppy)

TEAC FD-55GFR (5.25-in. 1.2MB floppy)

HARD DRIVES

Digital DSP 1370L (SCSI)

Fujitsu M2694ESA (SCSI)

Maxtor MXT7131A (IDE)

Maxtor MXT7345A (IDE)

Maxtor MXT1240S (SCSI)

Micropolis 4110 (SCSI)

Quantum ELS 170A (IDE)

Quantum LPS 170S (SCSI)

Quantum LPS 240S (SCSI)

Quantum LPS 270A (IDE)

Quantum LPS 270S (SCSI)

Seagate ST12450W (SCSI wide)

Seagate ST11950N (SCSI)

Seagate ST3145A (IDE)

Seagate ST32550N (SCSI)

Seagate ST32550W (SCSI wide)

Western Digital AC3100 RTL (IDE)

Western Digital WD170A (IDE)

KEYBOARDS

BTC AT

Hi-Tek PS/2

KeyCat II

Microsoft Natural PS/2

Zenith SK-2000RE

MEMORY BOARDS

Above® Board ISA

AST Rampage

JRAM

MICE

Logitech Bus mouse

Logitech PS/2 Cordless mouse

Logitech PS/2 Ergo mouse

Logitech PS/2 Trackball

Microsoft Bus mouse

Microsoft Ergo PS/2 mouse

Microsoft Home Serial mouse

Mouse Systems Serial

MISCELLANEOUS

*Bernoulli Box II

DCP 286i Diagnostic v1.10

DCP/MUXi Diagnostic

*DEC PCI Bridge Chipset

Hardcard 85MB

Intel EtherExpress™ 16

*Intel EtherExpress™ Pro 100 PCI

IRMA 2

IRMA 3

ZNYX ZX312 EtherAction (PCI)

MONITORS

Nanao FlexScan F550i-W

NEC MultiSync 5FGp

PRINTER

Panasonic KX-P1124i

SOUND BOARDS

Cyber Audio

Diamond Sonic Sound

*Gravis UltraSound

Pro AudioStudio 16XL

Sonic Sound

Sound Blaster 16 ASP

Sound Blaster 16 ASP SCSI-2

Sound Blaster 16 Multi-CD

Sound Blaster 16 Value

Sound Blaster AWE 32

Turtle Beach MultiSound

Turtle Beach Monterey

TAPE DRIVES

Colorado Jumbo 250 (Floppy, Tape)

Colorado Trakker 250 (Parallel, Tape)

Conner 51250Q (Floppy, Tape)

Exabyte 8200T (SCSI, Tape)

Iomega Tape 250 (Floppy, Tape)

VIDEO ADAPTERS

Onboard Cirrus Logic 5430

#9 GXE PCI 2MB

*#9 GXE ISA 1MB

AT&T VDC 800

ATI Graphics Wonder 1MB (ISA)

ATI Pro Turbo 4MB (ISA)

*ATI Pro Turbo 4MB (PCI)

ATI UltraPro EISA 2MB

ATI UltraPro ISA 2MB

ATI UltraPro PCI 2MB

Cirrus Logic 5430

Diamond SpeedStar Pro 1MB (ISA)

Diamond Stealth 24 1MB (ISA)

Diamond Stealth 32 2MB (PCI)

Diamond Stealth 64 4MB (PCI)

Diamond Stealth 64 DRAM 2MB (PCI)

Matrox MGA II PCI

Orchid ProDesigner 2 1MB (ISA)

Paradise Windows Accelerator 1 MB (ISA)

VIDEO EXTENSIONS

ProShare VC200 v1.6

ISDN Adapter

Smart Video Capture

Win / TV


USED IN CONFIGURING TEST PLATFORMS (NOT RIGOROUSLY VALIDATED)

 Products marked with this symbol were added to the test suite specifically for these testing runs.

CD-ROM DRIVES

NEC CDR 74-1 (external, SCSI)

Toshiba XM-3401 (internal, SCSI)

DISK CONTROLLERS

Onboard Adaptec 7870 (SCSI)

Onboard Intel 82091 (ISA/IDE)

Adaptec 1542CF (ISA/SCSI)

*Adaptec 2940 (PCI/SCSI)

FLOPPY DRIVES

NEC FD-1138H (3.5-in. 1.44MB floppy)

NEC FD-1157C (5.25-in. 1.2MB floppy)

TEAC FD-235HF (3.5-in. 1.44MB floppy)

TEAC FD-505 (dual 1.44/1.2MB floppy)

TEAC FD-55GFR (5.25-in. 1.2MB floppy)

HARD DRIVES

Hewlett-Packard C2490A (SCSI)

Hewlett-Packard C3323E (SCSI)

Seagate ST3243ON (SCSI)

Seagate ST3390N (SCSI)

Seagate ST5660N (SCSI)

Western Digital AC1270 (IDE)

Western Digital AC2250A (IDE)

Western Digital AC2340 (IDE)

Western Digital AC2540 (IDE)

KEYBOARDS

Compaq RT101

Key Tronic PS/2

NMB RT-101

MICE

Logitech PS/2 Standard mouse

Microsoft Serial mouse

Mitsumi PS/2

MISCELLANEOUS

3Com Etherlink III

Intel EtherExpress™ 16

ZNYX ZX312 EtherAction (PCI)

MONITORS

AT&T AC 120VCTX 6468GM

MAG MX15H

NEC MultiSync 3D

NEC MultiSync 5FGP

Panasonic PanaSync C1381i

QUME QM835

Sony CPD 1320

ViewSonic 6E

PRINTERS

Hewlett-Packard LaserJet IIP

Panasonic KX-P1124i

Panasonic KX-P2123

Panasonic KX-P2124

Panasonic KX-P2130

SERVER MANAGEMENT CARDS

HP Remote Assistant (EISA)

SOUND BOARDS

Sound Blaster 16 Value

Sound Blaster Pro II

TAPE DRIVES

Archive Viper 2150S (SCSI, Tape)

HP C1533 DAT (SCSI, DAT)

VIDEO ADAPTERS

Onboard Cirrus Logic 5430

*ATI UltraPro PCI 2MB

Atron VGA

Paradise Windows Accelerator 1 MB (ISA)


OPERATING SYSTEMS AND HARDWARE VALIDATED IN NETWORK TESTING

 Products marked with this symbol were added to the test suite specifically for these testing runs.

BANYAN VINES

*v5.54(0), Server

Client Workstation

Network Adapters:

IBM Token Ring 16/4

Intel EtherExpress™ 16

Intel TokenExpress™ 32 (EISA)

IBM LAN SERVER

*v4.0, Advanced

OS/2 Requester

*IBM OS/2 Warp v3.0

Network Adapters:

*IBM Token Ring 16/4 II

IBM Token Ring 16/4 II w/ RPL

Intel EtherExpress™ 16

Intel EtherExpress™ Flash32 (EISA)

*Intel TokenExpress™ 16/4s

Intel TokenExpress™ 32 (EISA)

ZNYX ZX312 EtherAction (PCI)

MICROSOFT LAN MANAGER

v2.2, Server

DOS/Windows Client

Microsoft OS/2 v1.30.1

Network Adapters:

*IBM Token Ring 16/4 II

Intel EtherExpress™ 16

Intel TokenExpress™ 16/4s

ZNYX ZX312 EtherAction (PCI)

MICROSOFT WINDOWS NT

*v3.5 Advanced Server

Network Adapters:

*AMD PCnet (PCI)

3Com 3C509

Intel EtherExpress™ 16

ZNYX ZX312 EtherAction (PCI)

NOVELL NETWARE

*v4.10, Server

v3.12, Server

SFT III

Workstations

Network Adapters:

3Com 3C509

3Com 3C579 Etherlink III (EISA)

3Com Etherlink (PCI)

3Com Tokenlink III

AMD PCnet (PCI)

*Cogent eMaster+ EM964 PCI

DEC Etherworks (PCI)

DEFPA PCI/FDDI

IBM Token Ring 16/4 II (16-bit)

*IBM Token Ring 16/4 (16-bit)

Intel EtherExpress™ 16

*Intel EtherExpress™ Flash32 (EISA)

Intel EtherExpress™ Pro (ISA PnP)

Intel EtherExpress™ Pro 100 (EISA)

Intel EtherExpress™ Pro 100 (PCI)

*Intel TokenExpress™ 16/4s

*Intel TokenExpress™ 32 (EISA)

*Intel TokenExpress™ Pro (ISA)

*Madge Smart 16/4 AT Ringnode

Novell NE1000

Novell NE2000

Novell NE2000plus

Novell NTR2000

Olicom PC AT

Olicom PCI Token Ring

Olicom PCI 16/4

Proteon 1990 (EISA)

Racal Interlan PCI T2

SMC Elite16C Ultra

SMC EtherPower PCI

SMC PC600FS

SMC Token Elite

Thomas-Conrad TC3045

Thomas-Conrad TC4045

Thomas-Conrad TC5045

Thomas-Conrad TC5048-T/2 (PCI)

Thomas-Conrad TC6242

Xircom Pocket Adapter

*ZNYX ZX312 EtherAction (PCI)

PEER TO PEER NETWORKS

LANtastic v.6.0

*3Com Tokenlink III

*IBM Token Ring II

Intel EtherExpress™ Pro

*Intel TokenExpress™ Pro (ISA)

*Intel TokenExpress™ 32 (EISA)

Novell Personal NetWare v.1.0

Intel EtherExpress™ Pro

Intel TokenExpress™ Pro (ISA)

*Windows for Workgroups v.3.11

Intel EtherExpress™ Pro

Intel TokenExpress™ Pro (ISA)


SOFTWARE INCLUDING OPERATING SYSTEMS

BENCHMARKS & DIAGNOSTICS

DisplayMate Professional v1.1

Floating Point Sequencer v1

GST Diagnostic v1.01

Intel Manufacturing Diagnostics

Landmark Benchmarks v2.0

Performance Suite

*QAPlus v4.70

XTree Pro v1.1

COMMUNICATION SOFTWARE

Crosstalk v2.0

Crosstalk for Windows

Faxability Plus OCR

First Choice v3.00

Procomm Plus v2.01 (DOS)

Procomm Plus v1.02 (Windows)

ProShare Premiere v1.6

WinFax PRO v4.0

MEMORY & DRIVE MANAGERS

EMM386.sys v4.0

HIMEM.sys v2.04

Netroom

QEMM v7.0

Qualitas 386MAX v7.3

RAMdrive.sys v2.12

Smartdrive.sys v2.10

MISC. SOFTWARE

Aces of the Pacific

Flight Simulator v4.0

Wing Commander 2

MULTIMEDIA APPLICATIONS

Aces of the Pacific

Animotion MCS Stereo v.1.04

Battle Chess (1991) for Windows

Beethoven (1992) for Windows

Bookshelf (1992) for Windows

Critical Path for Windows

Mammals (1990 NGS)

SD Zoo Animals v.1 for Windows

Seventh Guest v1.1t

OPERATING SYSTEMS

*Banyan Vines V.5.54(0)

*IBM LAN Server 4.0 Advanced

*IBM OS/2 v2.11GA

*IBM OS/2 v2.11 SMP

*IBM OS/2 Warp v3.0

LANtastic 6.0

Microsoft DOS v5.00A

Microsoft DOS v6.22

*Microsoft LAN Manager 2.2

Microsoft OS/2 v1.30.1

Microsoft Windows v3.11

*MS Windows NT v3.5 Advanced Server

*MS Windows for Workgroups v3.11

*Novell NetWare v4.10

Novell NetWare v3.12

Novell NetWare SFT III

Novell Personal NetWare 1.0

*SCO UNIX Open Desktop v3.0

SCO UNIX Vr3.2

*SunSoft Solaris v2.4

*SunSoft Solaris v2.1

Sun OS Vr5.1

UnixWare v1.1

*UnixWare v2.0

Unix Vr4.2

SOFTWARE APPLICATIONSDOS

AutoCAD 11

AutoCAD 12

dBASE IV v1.1

Excel v3.0 for Windows

Excel v4.0 for Windows

Grammatik v2.0 for Windows

Grammatik v5.0 for Windows

Harvard Graphics v2.13

Harvard Graphics v2.3

Lotus 1-2-3 r1.0 for Windows

Lotus 1-2-3 r3.1

Lotus 1-2-3 r4.0

Mathematica v1.2

Mathematica v2.0

Minitab v7.2

Norton Utilities v8.0

PageMaker v4.0 for Windows

Paradox v3.5

PowerPoint v3.0 for Windows

PowerPoint v4.0 for Windows

Project v1.0 for Windows

Quattro Pro v3.0

Symphony v2.2

Word v2.0 for Windows

Word v6.0 for Windows

WordPerfect v5.1

WordPerfect v5.1 for Windows

SOFTWARE APPLICATIONSOS/2

CorelDRAW v2.5

Harvard Graphics v2.3

 Indicates that the latest version (at test time) of the diagnostics was used.


Frequently Asked Questions (FAQ)

Windows-NT Certifications, Where can I find them?

Windows*95 - Doesn't recognize my PCI devices?

Novell Certification numbers, what are they?

Cache 512K - What's the story with 512K?

Fab 7 - What's changing?

SCO - Does ALTServer on-board SCSI support SCO UNIX 3.2 rel 4.0?

SCO & RAID - How can I add drives to an existing installation?

RAID - How can I do it on ALTServer?

Dual Processing - What is the performance improvement?

Netware mirroring - How can I do it on ALTServer?

OS Certifications - What is the status?

BIOS - I've upgraded my Pre-Production board to latest BIOS and now it won't work?

Second processor - What sort of performance enhancement can I expect?

NT & RAID - My system fails to load Windows NT 3.5 on my RAID card with an NTFS boot drive.

I/O Riser - How do I remove the I/O Riser from the Columbus Chassis

SCU reports: PCI - Undefined Device, what's that?

120mhz - Will ALTServer support the 120 MHz processor?

Power - What are some power considerations on ALTServer  / Columbus 230W supply?

Video - How can I make the on-board video secondary and my adapter video primary?

ISA - What is the procedure for adding ISA cards to the SCU?

ISA/EISA/PCI - More on Adding ISA/EISA/PCI Cards

ISA Adapters - Shadow Add-in Card BIOS

Boot order - What's the boot order for the various disk drive types on Altair?

NT & RAID - Booting Windows NT from on-board SCSI and have my data on an EISA XRAID4 controller.

OS/2 & RAID - OS/2 Warp fails to install properly from CD-ROM on the  XRAID4.


Windows-NT Certifications, Where can I find them?

Intel was recently informed by Microsoft that Windows NT certifications will not be granted at the baseboard level. Microsoft's policy is that only systems which are commonly available to the marketplace can be certified, and they must be certified in an 'as shipped' configuration by the company that sells the product. This means that they will not certify our baseboard products, but are happy to certify eligible systems from OEM customers. They will not allow Intel to act as an agent for customers in obtaining certification.

OEM customers can contact Microsoft directly and obtain a test package so that they can perform the certification testing at their site and send in the results to Microsoft. Once the results are reviewed, Microsoft will send a letter to the company, informing them of the certification, as well as adding their product name to Microsoft's "Hardware Compatibility List" (HCL). Alternately, the customer may elect to send the system to Microsoft testing labs to have the certification testing performed there.


Windows*95 - Doesn't recognize my PCI devices?

Although Windows 95 is not tested or supported, it has been shown to work.  Here's a tip:

     When I installed the Windows 95 upgrade to my Altair subsystem, it had problems recognizing my SCSI attached CD-ROM without  config.sys and autoexec.bat drivers installed.  Windows 95 does not  need these drivers installed.   I noticed that the system did not have a  SCSI controller resource and only saw the IDE controller. My system did not have a drive attached to the IDE interface. My boot drive(Windows 95) was attached to the onboard SCSI controller. Windows  95 had installed O.K. on the SCSI drive, but device manager never picked up the onboard SCSI controller.

    I went into device manager and let the system automatically add  hardware. Windows 95 did not automatically find any PCI devices. When  I manually added the Intel Neptune Pentium processor to PCI bridge, and          ensured that the Intel PCI to EISA bridge had been selected, Windows 95 started adding the rest of my PCI devices.


Novell Certification numbers, what are they?

The ALTServer Pent 100 Novell Certification Bulletin is F-3981.

The ALTServer Pent 133 Novell Certification Bulletin is F-3979.

The ALTServer Pent 120 Novell Certification Bulletin is F-3980.

The ALTServer Pent 75  Novell Certification Bulletin is F-3982.

These can be accessed directly from Novell via their fax back service at 800-414-5227.


Cache 512K - What's the story with 512K?

Check out all the 512K cache we now have qualified, finally!  Qual'd cache list.


Fab 7 - What's changing?

Changes to ALTServer Fab 7

July 20, 1995

Several changes have been required on the current ALTServer product in order to fix current errata, upgrade to more robust system features, or meet specific component supply limitations.  This document helps to clarify, explain, or update customers to these changes and how they may positively/negatively affect the current product.  Below is a list of the changes and a little explanation of each change and why.

•	Add pull-up for floppy write protect: This was required in order to ensure that the floppy write protect signal is always in a valid state. This change will have a positive impact for the current product when running QAPlus, and int13 compatibility format tests.  These occurrences have been known to cause floppy write protect failures mainly on Teac 2.88 floppy drives.

•	Change Fan Sense circuit: This was required in order to correct for a worst case scenario. In the Magellan chassis with two fans, fan failure may not be detected under worst case conditions.  A resistor value change has been implemented in order to guarantee a more accurate A_to_D reading of the fan sense circuitry.

•	Add drivers to floppy select lines: This was required in order to increase the drive capability of the floppy drive select signals.  Some 5.25" floppy drives have 150 Ohm pull-up resistors attached to the two drive select lines. The AIP does not have the drive capability to pull these lines to a valid logic low. Because there were some spare gates already available this changed required no new components.

•	Route bus frequency signals into keyboard controller: This was required so that BIOS can detect the change in Bus Frequency. The P54C processor now has two jumper-selectable lines which determine the core bus divide ratio. BIOS needs to know what state these lines are in order to determine the processor's operating frequency. In the current product there is no way of detecting a 120MHz or greater processor.

•	Add pull-ups on parallel port signals: This was required so that we could add pull-up resistors to improve quality of Parallel port control signals. This was a specific customer request and has no apparent functional effects on the product.

•	Reroute PCI reqest and grant to use INCA arbiter instead of PCEB: Because of shortages in the supply of B0/B1 PCEB parts we are required to support the older A2 stepping of the PCEB.  This stepping of the PCEB has known errata in it's internal PCI arbiter which would cause either unreliable server operation, or require defeaturing of the ALTServer.  As an alternative, the PCI arbitration function has been switched to an arbiter available in the INCA ASIC. This arbiter provides equally fair round robin arbitration for all PCI bus masters, guaranteeing a robust PCI bus with maximum guaranteed grant latency for all bus mastering devices.  ALTServer functionality and overall performance will not be affected by this change.    Fab 7 with the -A2 level PCEB will not support  GAT mode.


SCO - Does ALTServer on-board SCSI support SCO UNIX 3.2 rel 4.0?

No, this SCO release does not support PCI, the ALTServer does support SCO UNIX 3.2 rel 4.2.


SCO & RAID - How can I add drives to an existing installation?

Adding Another Hard Disk to an Existing SCO Unix 3.2/4.2 Raid Configuration

To add a hard drive to an existing SCO Unix Raid configuration, do the following (more than one drive can be added, just configure all as a single system drive with DACCF):

1. Attach the hard drive to the XRAID SCSI bus. Insure that the bus is

terminated correctly and that the SCSI Drive ID is unique.

2. Run the DACCF utility, choose the "View/Update Configuration" option.

3. Create a new pack and add the new drive to the pack. Arrange the pack and

create a System Drive.

4. Once the System Drive is created, Initialize the system drive. Highlight

the new drive and initialize it. DON'T INITIALIZE THE OLD SYSTEM DRIVE!! If you had one system drive before, that will be drive 0, so you'd initialize drive 1. Whatever the system drive number is, that's the id you use in step 4 of the SCO instructions.

5. Exit the DACCF Utility and boot SCO Unix.

Follow these SCO instructions to add the new hard disk.

1.   login as root in maintenance mode.

2    type  "mkdev hd"

3.   Choose "mdac" for Mylex drivers when asked for the device name, and

0 for the controller number (if you only have one controller).

4.   SCO documentation says you need to provide the SCSI id and LUN of the

disk. Instead of the SCSI id of the disk, enter the number of the RAID system drive (1st drive is id 0, 2nd drive is id 1, ...). The LUN will still be 0.

5.   At this point either it will ask you to relink the kernel or show

you the partition table of the disk. If shows the partition table go to step 6 below.

If it asks for relinking, type "y" to relink the kernel and reboot

the system. Now follow from the step 1 again. In other words you need to perform "mkdev hd" one more time.

6.   You should choose `Entire disk for Unix' option.

7.   Now it should show you division table.

- type `c' to create a file system

- type `n' to name the filesystem (for ewxample usr1 or whatever

you wish)

- type `q' q to quit

- type `i' to install the division table.

8. Now type `mkdev fs' to make an entry in the mount table

- choose `1' to add a file system and answer other questions.

At this point, you can mount the second disk.


RAID - How can I do it on ALTServer?

Intel offers the XXPCIRAID4 adapter card that offers two separate RAID channels on a single card.


Dual Processing - What is the performance improvement?

ALTServer uses what is called a "shared cache" architecture.  This means that the maximum performance gained by adding a second processor is aproximately 30% over the single processor system.  Some multiprocessing systems use what is called "dedicated cache" and can achieve a performance boost of 80%-90% with the addition of a second processor AND it's L2 cache.  The "dedicated" solution is therefore more expensive to upgrade than the "shared" approach.


Netware mirroring - How can I do it on ALTServer?

I have successfully implemented mirroring on an Altair with nothing external except for two equal drives.  Using the onboard 7870 I loaded install, created a partition on drive 0, then created a partition on the second drive of equal size.  Then I went to the mirroring option and mirrored partition on disk one with one on disk 2.  I did this without the benefit of Novell documentation, so a customer should have no issue doing this using the book.   Mirror


OS Certifications - What is the status?

Altair OS Certification Status                          9/1/95	Uniprocessor testing
Complete as part of final compatibility testing	Tested with BIOS rel 1.00.07
OS	tested	submit for cert	cert rec	Notes
Windows for Work groups  V 3.11                    75/100/120	pass	yes	??	Need confirmation of letter
Windows for Work groups  V 3.11                    133	9/18	9/25	10/9
SCO ODT V 3.0 (pre cert only) 100	pass	see below	see below
IBM OS/2 V 2.11       100/120	pass	yes	8/25	Need BIOS .11 rel to get cert
IBM OS/2 V 2.11        75/90	pass	yes	8/25
IBM OS/2 V 2.11       133	9/18	9/25	10/9
Sunsoft/Solaris   V 2.4     90	pass	yes	yes
Sunsoft/Solaris   V 2.4     100	pass	9/5	9/20
Unixware  2.01	pass	see below	see below
Windows 95 (beta)	8/4	n/a	n/a	No test package for certification.
OS/2 Warp  3.0	pass	yes	8/25	Need BIOS .11 rel to get cert
Unixware V1.1  90	pass	n/a	n/a	Will not certify.
Separate  IPTL testing
	test done	submit for cert	cert rec
Novell: Netware 3.12/4.1  90 Mhz	done	done	done
Novell: Netware 3.12/4.1  75,100,120,133 Mhz	done	done	done
Banyan   rel 5.54  75,90,100,120   mhz	done	done	done
Banyan   rel 6.00 75,90,100,120  mhz	done	done	done
Separate testing:  OS vendor
Novell: Netware   stress test  MP V4.1; C2 config	8/25	n/a	n/a	client testing only
SCO ODT V 3.0; C1 config 75 & 90	pass	n/a	done
SCO ODT V 3.0; C1 config 100,120, & 133	9/30	9/30	10/15
Altair OS Certification Status	Multiprocessor testing
Complete as part of final compatibility testing	Tested with BIOS rel 1.00.07 (
OS	tested	submit for cert	cert rec	Notes
SCO 3.2 V4.2MPX  (pre cert only)	pass	see below	n/a
SCO 3.2 rel 5 (Everest)				Full support OS; Beta in eval.
IBM OS/2 V 2.11    100/120/133	pass	yes	8/25	Need letters.
IBM OS/2 V 2.11    90/75	pass	pass	8/31	Need letters.
Sunsoft/Solaris V 2.4 120;133	9/18	9/25	10/13
Unixware  v 2.0	fail	n/a	n/a
Note:  Windows for work groups V3.11and  Windows 95, are not MP OS's
Separate  IPTL testing			(needs latest BIOS and HW)
	test done	submit for cert	cert rec
Novell: Unixware 2.01; 90 mhz	Done	Done	Done	Need letters.
Novell: Unixware 2.01; 75,100 mhz	Done	Done	8/10/95	Need letters.
Novell: Unixware 2.01; 120/133	Done	Done	8/10/95	Need Letters.
Novell: Netware 4.1MP				Beta version tested; cert package not released.
Separate testing: OS vendor
SCO MPX   75,90	done	done	done
SCO MPX    100,120,133	9/30	9/30	10/15
Microsoft NT  3.51  75,90,100,120,133	9/15	9/15	9/30	need rel BIOS 1.00.11 & 133 CPU; ship sys to Microsoft for testing


BIOS - I've upgraded my Pre-Production board to latest BIOS and now it won't work?

BIOS at level 1.00.04.BIO or later implemented half of a parity memory fix, the baseboard was modified to complete the fix.  This BIOS expects the BIOS to support parity.  To get around this issue of a PP baseboard not supporting parity properly you can disable parity by moving Jumper J7B to position 2-3 to disable parity checking altogether.


Second processor - What sort of performance enhancement can I expect?

The ALTServer is based on a shared cache architecture.  What this means to multiprocessing performance is that there is a theoretical maximum benefit of approximately 30% over the single processor system.  That means that you get an effective performance on the dual processing system of 1.3 processors.  This is compared to a dedicated cache solution that can reach up to 1.9 in a dual processing (DP) solution.  All that cache and hardware to support dedicated cache DP does not come cheap, so for some applications the 30% boost is an attractive solution as all that is necessary is the second processor.


NT & RAID - My system fails to load Windows NT 3.5 on my RAID card with an NTFS boot drive.

The issue with the caching controller card is that when you select to have the boot drive on Windows NT to be NTFS it actually starts out life with the FAT file system and gets converted during the last stage of the installation process.

During this conversion process windows NT goes off and reboots the system.  Unfortunately it reboots before the Caching controller controller has had a chance to fully write the data in its cache back to disk, causing the disk to become corrupt.

We are still looking for a work-around for this problem, but for now the best thing to do is to use FAT as the file system for the boot device.


 I/O Riser - How do I remove the I/O Riser from the Columbus Chassis

You must remove the baseboard to safely remove the I/O riser from the ALTServer motherboard.  You must also release the metal locking tabs mounted to the chassis (rotate 90 degrees).  If you don't remove the baseboard to perform this task you may break the I/O riser connector on your baseboard.


SCU reports: PCI - Undefined Device, what's that?

The INCA chip is the undefined device.  There is no PCI sub-component definition for the features supplied by the INCA and until there is, it will remain an undefined device as reported to and from the SCU.  Click here to read more about the INCA chip.


120mhz - Will ALTServer support the 120 MHz processor?

Fab 4 no, Fab 5 and beyond yes.   Click here for PBA numbers.

There are 3 versions of the 120mhz part, OPSD Servers is still working what processors to support.  The main issue has to do with multi-processing support.  As I understand it

P54C-120 binned to 120, won't support MP, avail first

P54CQS-120 new .35u, won't support MP, avail second

P54CS-120 newer .35u, will support MP, avail last


Power - What are some power considerations on ALTServer  / Columbus 230W supply?

The values shown below are measured levels with the ALTServer systems executing an MS-DOS application. The maximum amperage shown below calculates the maximum current (worst case) of every component on that product.   Click here for more power data.

Product	+5 volts (typical)	+5 volts (maximum)

2 P54C-90 processors with 256 MB	8.85 amps	15.75 amps

ST31200N 1GB Hard Disk	3.7 amps

3.5-inch Floppy Drive	0.4 amps	1.2 amps

EISA Bus Slot	2.0 amps/slot	4.5 amps/slot

System (230W) total	30.0 amps	30.0 amps


Video - How can I make the on-board video secondary and my adapter video primary?

A: This is not allowed.   Cards set up as primary and secondary as was the case in ISA/EISA systems.  Any add in adapter will REPLACE the onboard video.  The on-board is disabled in this situation.


ISA - What is the procedure for adding ISA cards to the SCU?

A: Before ISA cards can be added they must be defined, either while in the SCU or the card must provide a .cfg file.  If a .cfg file is provided you must copy it to the SCU disk before adding the card.  Perform the following:

1)	Boot SCU disk

2)	Press <F9> for Utilities at the first SCU screen

3)	<F7> to Define ISA cards

4)	Define the ISA card

5)	Make sure to save via the <F10> key

6)	Go back to the main SCU menu

7)	Select add/remove cards

8)	Select <INS> insert key to add isa card , your newly defined card will be in the list

9)	Follow the screen directions from there.


ISA/EISA/PCI - More on Adding ISA/EISA/PCI Cards

When adding an ISA add-in card, the user must first run the SCU to configure the ISA card resources.  Once the ISA card resources (IRQ, DMA, and I/O address) are completely configured via the SCU, the user then adds the ISA card into one of the EISA slots.  In virutally all cases, the ISA card has jumpers designated for IRQ settings, DMA settings, and I/O address settings.  It is wise to double check the ISA card's documentation to get a full understanding of the capabilities and choices available before exectuing the SCU.  Since the ALTServer baseboard server adheres to the ISA Plug-n-Play standard, these steps are considered normal practice in a PCI based system.  The ALTServer default setting is to DISABLE ISA SHADOWING in the SCU.  Any ISA card which has ROM BIOS on it can have shadowing enabled and can then be seen (via the BIOS signature AA55) and if the card's ROM BIOS region is SHADOW ENABLED, the ALTServer BIOS will automatically shadow this code.  However, if the ISA card contains RAM in any location between C0000-DFFFF, the ENABLE ISA SHADOWING option for that particular address in the SCU must  be disabled.  Token Ring, Intel Server Management Card, and DigiBoard cards fit into this type of ISA card catagory.  Please note that any ISA card that contains a ROM BIOS can be completely disabled.  This may be useful when the user is trying to configure a very heavily loaded system and is looking for more memory space between C0000-DFFFF.

When adding an EISA add-in card, the user is able to add the card to the system and execute the SCU at the same time.  EISA cards do not grab system resources until the *.CFG file is loaded via the SCU.  Once configured, the IRQ, any DMA or I/O addriessing is automatically configured by the ALTServer system.  Like the ISA add-in cards, the ROM BIOS on the EISA card can be fully disabled to free up needed memory space between C0000-DFFFF.

When adding a PCI add-in card, the user is able to add the card to the system and execute the SCU at the same time.  PCI add-in cards do not have a *.CFG file, but instead utilize PCI BIOS calls to determine the available system resources and configure themselves around existing ISA/EISA/CPI devices already in the ALTServer system


ISA Adapters - Shadow Add-in Card BIOS

Specific memory regions are designed to be moved to fast 64-bit ALTServer memory and also cached by the primary/secondary cache architectures located on the CPU module. While these areas (C0000-CFFFF,  D0000-DFFFF, and E0000-E7FFF) are implemented to ensure video BIOS compatibility, Intel engineers have demonstrated that some disk controller and Ethernet add-in card BIOS can be moved to these areas. The shadowing of add-in card BIOS code to fast 64-bit ALTServer memory can increase performance of the add-in card by as much as 40%. Special care must be taken concerning the system memory map.

Instead of temporary files being stored on the floppy, they are now stored on the VDISK.  This greatly improves the speed of the SCU during loading and configuring of files.  Keep in mind that the VDISK routines swap the processor in and out of flat model mode during INT 21h calls that are made to the VDISK.  Therefore the main application must be running in real mode.  If protected/flat model access is required, put the processor in whatever mode is needed, do what needs to be done, and put the processor back into real model.  Be aware the INT 21h VDISK calls cannot be made if the processor is not in real mode.  All of the configuration/overlay files are stored on drive Z (the VDISK drive).  When the SCU is initialized, the configuration/overlay files are loaded from a compressed image stored in the SCU flash area and copied to the virtual disk drive under the root directly.  If a particular configuration file is missing from the flash are, the user is prompted for the diskette that contains the missing configuration file. Once the disk is inserted, the appropriate files are copied to the VDISK.  This leaves 101KB remaining for configuration files an overlays.  If there were with unique cards in the ALTServer server system, the space remaining should not be sufficient.  However, there  are only three types of EISA cards;  video, SCSI, and Ethernet.  PCI cards have very small (1-2K) configuration files and have no overlay files.  In the ALTServer, the baseboard is actually treated as an EISA device and requires a configuration file (4KB) and overlay (66KB).  Compressed, they take up around 30KB.  The AIC-7870 SCSI controller on the baseboard is treated as a PCI device.  The Video configuration is handled by the baseboard configuration file which allows the user to add a EISA or PCI video card and the baseboard will automatically disable the onboard Cirrus PCI video controller.  For a standard platform, that leaves 71KB worth of space of the configuration files.

See also SCU section.


Boot order - What's the boot order for the various disk drive types on Altair?

A: If you have an IDE drive connected, you must make the IDE drive the boot device. If you don't have an IDE drive, a bootable drive connected to an EISA controller will be the boot device if the SCSI BIOS is enabled on the EISA controller. If a bootable drive is connected to the on-board PCI SCSI controller and a  bootable device is connected to an EISA SCSI controller, but the EISA SCSI controller BIOS is disabled, the boot drive will be the one connected to the on-board pci controller.  As far as scan order of the PCI boot devices.  PCI slot 1 is scanned first, then the onboard SCSI controller, followed by PCI slots 2 and 3.  Click here to view baseboard diagram.


NT & RAID - Booting Windows NT from on-board SCSI and have my data on an EISA XRAID4 controller.

2. Q: I'm booting Windows NT from a drive connected to the on-board PCI  SCSI controller and have my data drives connected to an EISA XRAID4 controller but I can't access the drives from Windows NT. How can I do that?

A: First run the SCU and make sure the XRAID4 BIOS is disabled.  Next, from the "Main" screen in the Program Manager, go into "Windows NT Setup". From the "Options" menu, select the "Add/Remove SCSI Adapters..." option. Go to the bottom to the list of devices to "Other" and select that. Insert the driver diskette that came with the XRAID4. Add the driver. Shut down Windows NT and reboot. You should now be able to see the drives on the XRAID4 controller.


OS/2 & RAID - OS/2 Warp fails to install properly from CD-ROM on the  XRAID4.

During the installation of OS/2 Warp from CD-ROM on a Intel XRAID4 you will get a RED SCREEN displaying a CD-ROM error. Please use the following IBM supplied work around.

1. At the RED CD-ROM ERROR screen, hit ENTER, and you will get an OS/2

command line prompt.

2. Access the CD-ROM drive and change directory to OS2IMAGE\DISK_1

'd:'

'CD\OS2IMAGE\DISK_1'

3. Run SYSINST2.EXE with command line option specifying location of source file s

.

'd:\OS2IMAGE\DISK_1\SYSINST2.EXE d:\OS2IMAGE'

NOTE: d: indicates CD-ROM drive i.e.-'E:'

Installation will then proceed normally.

The following config.sys file shows proper configuration for OS/2 DISK 1 when installing from CD-ROM. Ensure that the DAC960.ADD is copied to the diskette. If insufficient disk space is left, file TEDIT.HLP can be deleted to provide adequate space for DAC960.ADD. '*' indicates changes to config.sys on DISK 1 for CD-ROM install.

buffers=32

iopl=yes

memman=swap,delayswap

protshell=sysinst1.exe

set os2_shell=sysinst2.exe

diskcache=D2,LW

protectonly=yes

libpath=.;\;\os2\dll;\os2\install;

rem ifs=hpfs.ifs /c:64

pauseonerror=no

codepage=850

devinfo=kbd,us,keyboard.dcp

devinfo=scr,ega,vtbl850.dcp

device=\dos.sys

device=\mouse.sys

set path=\;\os2;\os2\system;\os2\install set dpath=\;\os2;\os2\system;\os2\install set keys=on

basedev=print01.sys

basedev=ibmkbd.sys

basedev=ibm1flpy.add

basedev=ibm1s506.add

basedev=ibm2flpy.add

basedev=ibm2adsk.add

basedev=ibm2scsi.add

rem basedev=ibmint13.i13        *

basedev=dac960.add              *

basedev=os2dasd.dmd

device=\testcfg.sys

basedev=xdfloppy.flt

set os2_shell=cdinst.exe

set saveconnect=1

set cdrominst=1

ifs=cdfs.ifs /q

basedev=aha152x.add

basedev=aha154x.add

basedev=aha164x.add

basedev=aha174x.add

basedev=aic7770.add

basedev=aic7870.add

basedev=btscsi.add

basedev=fd16-700.add

basedev=fd8xx.add

basedev=fd7000ex.add

basedev=dpt20xx.add

basedev=chincds1.flt

basedev=hitcds1.flt

basedev=neccds1.flt

basedev=sonycds1.flt

basedev=toshcds1.flt

basedev=ibmidecd.flt

basedev=tmv1scsi.add

basedev=sony535.add

basedev=sony31a.add

basedev=lms206.add

basedev=mitfx001.add

basedev=sbcd2.add

basedev=os2scsi.dmd

basedev=os2cdrom.dmd

The following is the configuration for config.sys on the boot partition to support DAC960 and provide access to the CD-ROM. '*' indicates changes from generic config.sys that OS/2 will write to the partition. These changes must be incorporated to access the CD after system install. Also, insure all files are in the proper paths.

PROTSHELL=C:\OS2\PMSHELL.EXE

SET USER_INI=C:\OS2\OS2.INI

SET SYSTEM_INI=C:\OS2\OS2SYS.INI

SET OS2_SHELL=C:\OS2\CMD.EXE

SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE

SET COMSPEC=C:\OS2\CMD.EXE

LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\MMOS2\DLL;

SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;C:\MMO S

2;

SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;C:\ O

S2\APPS;C:\MMOS2;C:\MMOS2\INSTALL;

SET PROMPT=$i|$p|

SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;C:\MMOS2\HELP; SET GLOSSARY=C:\OS2\HELP\GLOSS;

SET IPF_KEYS=SBCS

PRIORITY_DISK_IO=YES

FILES=20

BASEDEV=IBMKBD.SYS

DEVICE=C:\OS2\BOOT\TESTCFG.SYS

DEVICE=C:\OS2\BOOT\DOS.SYS

DEVICE=C:\OS2\BOOT\PMDD.SYS

BUFFERS=90

IOPL=YES

DISKCACHE=D,LW,AC:C

MAXWAIT=3

MEMMAN=SWAP,PROTECT

SWAPPATH=C:\OS2\SYSTEM 2048 2048

BREAK=OFF

THREADS=256

PRINTMONBUFSIZE=134,134,134

COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS SET KEYS=ON

SET BOOKSHELF=C:\OS2\BOOK;C:\MMOS2;

SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR SET SOMDDIR=C:\OS2\ETC\DSOM

REM SET DELDIR=C:\DELETE,512;D:\DELETE,512; BASEDEV=PRINT01.SYS

BASEDEV=IBM1FLPY.ADD

BASEDEV=IBM2FLPY.ADD

BASEDEV=XDFLOPPY.FLT

BASEDEV=OS2DASD.DMD

BASEDEV=IBM2SCSI.ADD            *

IFS=C:\CDFS.IFS /Q              *

BASEDEV=DAC960.ADD              *

DEVICE=C:\OS2\OS2CDROM.DMD /Q   *

BASEDEV=OS2SCSI.DMD             *

SET EPMPATH=C:\OS2\APPS;

PROTECTONLY=NO

SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS FCBS=16,8

RMSIZE=640

DEVICE=C:\OS2\MDOS\VEMM.SYS

DOS=LOW,NOUMB

DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB

DEVICE=C:\OS2\MDOS\VDPMI.SYS

DEVICE=C:\OS2\MDOS\VDPX.SYS

rem BASEDEV=OS2SCSI.DMD         *

rem BASEDEV=AIC7770.ADD         *  DEVICE=C:\OS2\MDOS\VMOUSE.SYS

DEVICE=C:\OS2\BOOT\POINTDD.SYS

DEVICE=C:\OS2\BOOT\MOUSE.SYS

DEVICE=C:\OS2\BOOT\COM.SYS

DEVICE=C:\OS2\MDOS\VCOM.SYS

CODEPAGE=437,850

DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP

DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP SET VIDEO_DEVICES=VIO_SVGA

SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)

DEVICE=C:\OS2\MDOS\VSVGA.SYS

SET MMBASE=C:\MMOS2;

SET DSPPATH=C:\MMOS2\DSP;

SET NCDEBUG=4000

DEVICE=C:\MMOS2\SSMDD.SYS

DEVICE=C:\MMOS2\R0STUB.SYS


Configuration Tips

SCSI Termination

NOVELL V4.1 Installation Instructions

Windows NT V3.5 Installation Instructions

SCO Unix Installation Instructions

OS/2 Installation Instructions

VGA - Cirrus 5430

INCA / LANDeskâ Server Control  (LSC)


ALTServer Help - Configuration Tips - SCSI Termination
SCSI Termination

The ALTServer's on-board Adaptec 7870 SCSI-II wide controller is physically located in between the baseboard SCSI-II narrow connector and the I/O riser card's narrow or wide connector.  This posses a unique situation for termination.  If both the connectors are used, care must be taken to terminate the bus in the proper locations.  The main thing to remember is that the bus requires termination at the SCSI bus ENDS.  Click here to view diagram with terminator locations

EXAMPLE Configurations:

Terminator Locations:  	T1, T2, T3 at I/O riser connector on baseboard

T4, T5 at Narrow SCSI connector on baseboard

The termination of the SCSI bus on the ALTServer depends upon the SCSI configuration.

Configuration 1: All Wide SCSI Drives attached to the connector on the Riser Card J2.

Configuration 2: All Narrow SCSI Drives attached to the connector J19.

Configuration 3: Some Wide SCSI Drives attached to the connector on the Riser Card J2, some Narrow 	SCSI devices connected to the connector J19.

Configuration 4: All Narrow SCSI Drives attached to the connector on the Riser Card J2.

Configuration 5: All Narrow SCSI Drives attached to the connector on the Riser Card J2.

Configuration 6: Some Narrow SCSI Drives attached to theconnector on the Riser Card J2, some Narrow 	SCSI devices connected to the connector J19.

SCSI Configuration Table

Key: 	T1 .. T5	= Terminator Number from Figure

T1 = R3 on FAB5 baseboard

T2 = R4 on FAB5 baseboard

T3 = R5 on FAB5 baseboard

T4 = R337 on FAB5 baseboard

T5 = R374 on FAB5 baseboard

RCBE	= Riser Card Scsi Bus End (Last SCSI Device on SCSI BUS Connected to Riser Card)

BBBE	= Baseboard Narrow Scsi Bus End (Last SCSI Device on Narrow SCSI Bus on Connector J19)

	T1	T2	T3	T4	T5	RCBE	BBBE
Config 1				X	X	X
Config 2	X	X	X				X
Config 3						X	X
Config 4			X	X	X	X
Config 5			X	X	X	X
Config 6			X				X


NOVELL V4.1 Installation Instructions

These instructions are basic instructions. They assume you have a single network adapter, the server is the first one on the network, and that you don't want to install any optional packages. The instructions are meant as a guide for installation of the basic NetWare V4.1 package.

1. Make a small DOS partition and install the AIC-7870 drivers for DOS so that you'll have access to the CD-ROM for installation. Reboot the machine after you've installed the drivers and insure you can access the CD-ROM. Also, be sure you know the HEX address of your network adapter.

2. Make the current directory the root directory (C:\). Make a new directory called 7870 in the root directory and copy the following Novell drivers    and files for the AIC-7870 to C:\7870:

   AIC7870.DSK

   ASPITRAN.DSK

   AIC7870.DDI

   README.TXT

3. Make the current drive the CD-ROM and change directory to:

   \NW410\install\english. Type "INSTALL" and press <enter>.

4. Choose "NetWare 4.1" from the list of products to install.

5. Choose "Simple Installation" for the type of installation.

6. Choose a name for your server.

7. After the server part of the install comes up, press the <INS> key to

   install the Adaptec AIC-7870 drivers that you copied to the C:\7870

   directory in step 2.

8. Press <F3> to specify the path to the AIC-7870 driver files for NetWare.

   Enter C:\7870 to specify the new path.

9. Two drivers will be listed: AIC7870.DSK and ASPITRAN.DSK. Select AIC7870.DSK by pressing <enter>.

10. Repeat step 9 for ASPITRAN.DSK.

    If you get a prompt "save existing file C:\NWSERVER\AIC7870.DSK", choose

    "No". Choose "No" to respond to the questions

    "save existing file C:\NWSERVER\AIC7870.DDI" and

    "save existing file C:\NWSERVER\ASPITRAN.DSK".

11. Choose "No" when asked the question "Do you want to select an additional disk driver". Press <enter>.

12. Select your LAN card from the list of supported LAN cards and press  <enter>. If you have an unsupported LAN card, press <ins> and follow steps similar to steps 9 and 10 for the disk drivers.

13. Press <enter> to "Select/Modify driver parameters. Enter the slot number for your LAN card. Enter the Hex network address for your LAN card and press <enter>. Press <F10> to save the settings. Choose the selection

    "Save parameters and continue" and press <enter>. Repeat the process for additional LAN cards. After all LAN cards have been installed, choose  "No" to answer the question "Do you want to select an additional network driver" and press <enter>.

14. Select "Continue Installation" and press <enter>.

15. If your driver doesn't install in the allotted time, control will be

    switched to the Server screen. Make sure the driver is loaded and press  <enter> to continue. Repeat this process for all drivers that load.

16. Once all drivers are loaded, answer "Yes" to the prompt "Continue

    anyway". Netware will check the network for conflicts and then mount the "SYS" volume.

17. Insert the "LICENSE" diskette when prompted. Press <enter>. Install will start copying the NetWare files to the hard drive.

18. When asked the question "Is this the first NetWare 4 Server", answer "Yes".

19. Choose your local time zone and press <enter>.

20. Enter your Organization name and press <enter>.

21. Enter your admin password, press <enter>, verify it and press <enter>.    Press <enter> when prompted. Install will start copying the rest of the NetWare files to the hard drive.

22. At the "Other Installation Options" screen, choose "Continue Installation" and press <enter>.

23. Press <enter> to exit to the console screen. Type "Down" and press <enter>.

    Type "Exit" and press <enter>. You will be left in a the directory

    C:\NWSERVER. This is the directory where you'll invoke the server on subsequent boots. Type "Server" and press <enter> to bring up the server again. Your installation is finished.


 Windows NT V3.5 Installation Instructions

The installation of Windows NT V3.5 with the default Adaptec AIC-7870 drivers is straightforward. These installation instructions assume that you want to install Windows NT V3.5 using the latest Adaptec AIC-7870 drivers that you get from the BBS.

1. Put a blank floppy diskette into the a: drive.

2. Unzip the Adaptec AIC-78XX self extracting zip file using the command    format:

            filename -o -d a:

   This will unzip the Adaptec driver file and put the AIC-78XX drivers for each operating system into appropriate subdirectories.

3. Edit the file "TXTSETUP.OEM" in the root directory of the a: drive.

4. Find this line in the "[disks]" subsection near the top of the file.

     d1 = "Adaptec SCSI Controller Drivers Disk 1 of 1", \disk1, \winnt

   Modify "\winnt" to read "\winnt\nt35" so the Windows NT V3.5 driver will be found when you insert the diskette during setup. The line will look like this after modification:

     d1 = "Adaptec SCSI Controller Drivers Disk 1 of 1", \disk1, \winnt\nt35

5. Boot from the Windows NT V3.5 Setup diskette. Follow the installation instructions on the screen until you have a choice to do an "Express"  setup or "Custom" setup. Press "C" to choose "Custom" setup.

6. Press "S" to skip mass storage device detection.

7. Press "S" to specify an additional device.

8. Highlight "Other" from the list of mass storage devices. Press <enter>.

9. Insert the Adaptec AIC-7870 driver diskette and press <enter>.

10. Make sure the "Adaptec Driver for AIC-78XX SCSI Controller is highlighted and press <enter>.

11. For this installation, there are no other drivers to install.

    Press <enter>.

12. Insert Setup diskette #3 when prompted and continue the normal Windows NT installation as specified in the Windows NT V3.5 Installation Guide.


 SCO Unix Installation Instructions

These instructions are basic instructions for installing SCO Open Desktop on the ALTServer. They do not cover any specific installation options.

1. Be sure your SCSI hard drive ID is 0 and your CD-ROM SCSI id is 5. The tape ID should be 2 if you're installing from tape. Be sure the SCSI bus is terminated correctly.

2. Boot the SCU diskette, choose the "Change Configuration Settings", select  the PCI SCSI Device, choose "Enable Manual", press <F6> and set the   interrupt level to IRQ 11.

YOU MUST SET THE SCSI CONTROLLER IRQ TO 11 OR  SCO UNIX WILL NOT INSTALL!!!!

3. Boot the N1 diskette.

4. Type "link" at the boot prompt. Then type "alad" and press <enter>. Be sure you type "alad" in lower case.

5. Follow the screen instructions.  When you're asked for the installation  media type, press <F3> twice to get a list of installation devices if you're installing from CD-ROM.  Choose SCSI CD-ROM and press <enter>.  The installation media type defaults to SCSI tape. Press <enter> to continue.

6. Follow the on-screen instructions. The rest of the installation procedure is straightforward.


OS/2 Installation Instructions

To install OS/2 2.11 SMP on a SCSI drive using the AIC7870 drivers, the driver must be added to the installation diskette DISK1 and config.sys modified to load the driver.  After the OS is installed, the line loading AIC7870.ADD is missing from config.sys on the boot drive.  The user must boot the system once more from the installation diskettes, escape out of the installation script and use an editor to modify config.sys.

This is a limitiation of the OS/2 2.11 installation process.

Needed tools:

1.  DOS bootable floppy disk with an editor.

The problem for the user is that after escaping from the installation procedure, they are placed in an OS/2 command line.  There are no  non-graphical editors included with OS/2.  The workaround is to boot from a DOS and use a DOS editor.

If the user has a text-bsaed OS/2 editor such as TEDIT or T2 they can use that.

If the user installs the OS on an HPFS partition, normal DOS will not be able to read the files.  The user will need to add the driver FSFILTER.SYS included with OS/2 which translates HPFS for DOS sessions.

See also OS/2 Warp CD-ROM installation with XRAID4 in the FAQ section of this helpfile.


VGA - Cirrus 5430

The onboard video will never be active or available if an video adapter card is added into the system.


INCA / LANDeskâ Server Control  (LSC)
INCA / LANDesk® Server Control  (LSC)

See LSC TPS section


Setup information

BIOS / CMOS Setup - <F1> during boot

On-board SCSI Setup - SCSISelect* on SCU disk

System Configuration Utility - AMISCU on SCU disk


Installation Instructions

NOVELL V4.1 Installation Instructions

Windows NT V3.5 Installation Instructions

SCO Unix Installation Instructions

OS/2 Installation Instructions


Technical Product Summary

Introduction

Board Level Features

Peripheral Component Interconnect (PCI) Chip Set

Interrupt Control ASIC (INCA) Component

Connectors / Signal Locations

Performance Benchmarks

System BIOS

System Level Features - Columbus Chassis

Environmental & Reliability Standards

System Level Features - Magellan Chassis - MG5000

Intel XXPCIRAID4 Disk Array Controller

Software Drivers Supported

Customer Support

Legal Stuff

SIMM Qualification Specification

Asynchronous Cache Module Qualification Specification

BURST Cache Module Qualification Specification


ALTServer Help - Technical Product Summary - Introduction
Introduction

The ALTServer baseboard and platform have been clearly designed to meet the needs of the server marketplace, and continue a tradition of performance and reliability set by Intel's Xpress technology. In contrast with the Xpress modular architecture, ALTServer offers a 'flat' design with the processor and memory subsystems residing on the main baseboard. The ALTServer design uses members of the Intel 82430 Neptune PCIset to provide high performance and a highly integrated system at multiple price/performance levels.

Two Zero Insertion Force (ZIF) sockets for Pentium processors provide scalability using Symmetric MultiProcessing (SMP) operating systems, such as UnixWare*, SCO UNIX, Solaris*, OS/2*, and WindowsNT*. The ALTServer's multiprocessing capabilities comply with the Intel Multiprocessing Specification v1.1. Additional simple and cost-effective performance upgrades are available through a variety of plug-in cache module options.

The ALTServer's expansion capabilities meet the needs of file and application servers for high performance I/O by providing a combination of PCI local bus and EISA connectors. The baseboard offers two dedicated PCI slots, five dedicated EISA slots, and one shared PCI/EISA slot. The high-performance PCI local bus allows the adoption of newer networking technology, such as ATM and 100 MB/second Ethernet NICs, with a minimum of effort and without concern for I/O bottlenecks. The PCI local bus offers a 133 MB/second bandwidth and has been a proven high-speed solution on the desktop. The ALTServer's architecture, as shown in the diagram below, brings these benefits to servers:

This combination of PCI and EISA expansion offers continuing support for existing special function EISA add-in boards, such as X.25 Multiport Serial cards. All of the add-in slots are available to the user because the high-performance PCI fast SCSI-2 interface and a PCI graphics controller are integrated on the baseboard.

A number of security, reliability, and management features also have been incorporated into the ALTServer's design to meet vital server needs. These features can be further enhanced with accessory products like the Intel Server Monitor Module and either intelligent EISA or PCI RAID controllers.


Board Level Features

AT Form Factor

Component Location

Block Diagram

Pentium Processors

3.3 Volt regulation

Second Level (L2) Cache

System Memory

Graphics Subsystem

Graphics Drivers and Utilities

Graphics Resolutions and Frequencies

Memory Map

I/O Map

Interrupts & DMA Channels

PCI SCSI Interface

Standard I/O and Advanced Integrated Peripheral (AIP) Component

IDE Interface

Keyboard and Mouse Interface

Dallas DS12887 Real Time Clock, CMOS RAM and Battery

I/O Riser Board

Expansion Slots (PCI and EISA)


AT Form Factor

The ALTServer baseboard measures 12" by 13" and is designed to fit into a standard AT-style chassis. Maximum chassis flexibility is provided by a special baseboard header which allows the connection of a riser with any of the following configurations of standard external I/O connections (keyboard, mouse, serial ports, etc.):

1.	Wide SCSI internal to chasis

2.	Wide SCSI external to chasis

3.	Narrow SCSI external to chasis

4.	Standard AT form factor

The following diagram shows the dimensions and mounting hole locations.

Figure 2. ALTServer board dimensions


Component Location


Block Diagram


Pentium Processors

The ALTServer baseboard is designed to operate with 75 MHz, 90 MHz, 100 MHz, 120 MHz, 133MHz or 167 MHz Pentium processors and is shipped with a single processor installed in the main Zero Insertion Force (ZIF) socket. A second ZIF socket is provided to upgrade to a dual processor SMP configuration. When two processors are installed, both should be of the same frequency, stepping and voltage specifications to ensure correct operation.When upgrading to dual processing, care should be taken to ensure the second processor is correctly oriented in the ZIF socket next to the primary processor.

The Pentium processor has an internal speed of 75, 90, or 100 MHz and an external speed of 50, 60, or 66 MHz respectively and is backward-compatible with the Intel486 processor. The Pentium processor supports both read and write burst mode bus cycles and includes a 16 KB on-chip cache core (8 KB for code and 8 KB for data caches) employing a write-back policy. Also integrated into the Pentium processor is an advanced numeric coprocessor which significantly increases the speed of floating point operations, while maintaining backward compatibility with the i486DX math coprocessor and complying with ANSI/IEEE standard 754-1985. Based on 0.6 micron processes, the Pentium processor is powered by 3.3 volts and supports Intel's System Management Mode (SMM) power-management operation.


3.3 Volt regulation

A patented onboard voltage regulator circuit provides the required 3.3 volts to the processor from the 5 volts provided by a standard power supply. This allows the ALTServer baseboard to be used with a 'standard' PC supply, instead of more costly supplies with 3.3V outputs. It should be noted that the onboard 3.3 volt regulator provides power for the processor(s) and not the PCI slots. When 3.3V PCI cards are used, the baseboard's 3.3 volt connector for the PCI slots must be used with a separate 3.3 volt power supply or with an external voltage converter.


Second Level (L2) Cache

To provide a cost effective solution using standard chip set components, the ALTServer offers an upgradeable second level cache using a cache module containing the cache devices.  This provides four options and price/performance points: No cache, 256 KB asynchronous cache, 256 KB or 512 KB Burst Synchronous cache.

The performance of each option depends on many factors, such as operating system, number of processors, amount of system memory, and other variables. However, as a general rule, overall system performance increases with larger cache sizes. The use of a Burst Synchronous cache should provide even higher performance than the equivalent size Asynchronous cache device.

The second level cache may be Enabled or Disabled using the BIOS Configuration Utility. When Enabled, the caching policy is always write-back mode to support the internal (L1) 16 KB cache of the Pentium processor. With a burst cache device installed, the processor read and write clock latencies are 3-1-1-1. With the Asynchronous modules, the processor read latency is 4-2-2-2 and the write latency is 3-1-1-1.

The single cache resource is shared in SMP configurations where two Pentium processors are installed. Cache coherency and control is provided by the 82434NX PCI/Cache Memory Controller.

Qualified L2 cache part numbers Secondary (L2) Cache Memory


ALTServer Help - Board Level Features - System Memory
System Memory

The main system memory is provided by eight 72-pin SIMM sockets for up to 256 MB of memory expansion on the baseboard. The eight 90° angled sockets support 256K x 36 (1 MB), 512K x 36 (2 MB), 1M x 36 (4 MB), 2M x 36 (8 MB), 4M x 36 (16 MB), and 8M x 36 (32 MB) SIMMs. The minimum memory size is 2 MB and the maximum memory size, using eight 32 MB SIMMs, is 256 MB. Memory timing requires 70 ns fast page devices. Parity generation/checking is provided for each byte.

The eight SIMM sockets are arranged as four banks (Bank 0, 1, 2, and 3) with each bank consisting of two sockets and providing a 64-bit wide data path and 8 parity bits. The memory array is controlled by the Intel 82434NX PCMC and data buffering is provided by two Intel 82433NX Local Bus Extension devices. Both SIMMs in a bank must be of the same memory size and type, although separate banks may have different sizes and types of memory installed. Any (or all) banks may be populated to provide the required system memory. In some instances, for electrical reasons only, it may be essential to populate Bank 0 first.

System memory begins at address 0 and is contiguous (flat addressing) up to the maximum amount of system memory installed. The only places where system memory is non-contiguous is in the ranges from 00080000 - 000FFFFF (the DOS compatibility region) and 00F00000 - 00FFFFFF (the system BIOS region). Memory regions holes at any other location may result  in DRAM beyond that hole unusable.

Qualified memory part numbers (DRAM SIMMS)


Graphics Subsystem

The SVGA subsystem is based on the Cirrus Logic 5430 PCI graphics controller. The Cirrus 5430 supports backward software compatibility with MDA, CGA, Hercules Graphics, EGA, and VGA graphics standards.

The standard configuration includes 512 KB of graphics DRAM soldered on the ALTServer baseboard. Graphics memory can be upgraded to a total of 1 MB by adding a 256 KB x 16 fast page mode 70 ns DRAM to the SOIC socket on the baseboard. The upgrade will allow higher display resolutions and performance. The display ram is paged into 128 KB of RAM located between A0000H and BFFFFh. The 15-pin VGA Connector appears on the I/O riser board. Graphics VRAM vendors and the VGA connector pinout is listed in the Appendix.


Graphics Drivers and Utilities

Graphics drivers and utilities for Windows 3.1,  and MS-DOS software applications are shipped with the ALTServer platform. Additional drivers for other common applications may be available from the Intel Applications Support BBS. Drivers for SCO*, Windows* NT, OS/2* and Interactive UNIX* should be obtained from the respective UNIX vendor.


Graphics Resolutions and Frequencies

The Cirrus 5430 video controller provides all standard IBM VGA modes. With 512 KB of video memory, the standard ALTServer goes beyond standard VGA support. The following tables show all supported video modes using the standard 512 KB of video memory, as well as with a user-installable upgrade to 1 MB of video memory. The following tables show the standard and extended modes that the chip supports, including the number of colors and palette size (e.g., 16 colors out of 256K colors), resolution, pixel frequency, and scan frequencies. All modes are supported with 512KB of video memory unless otherwise specified.

Mode(s)[Hex]	Colors (number /palette size)	Resolution	Pixel Freq. (MHz)	Horiz. Freq. (KHz)	Vert. Freq. (Hz)
0, 1	16/256K	360 X 400	14	31.5	70
2, 3	16/256K	720 X 400	28	31.5	70
4, 5	4/256K	320 X 200	12.5	31.5	70
6	2/256K	640 X 200	25	31.5	70
7	Mono	720 X 400	28	31.5	70
D	16/256K	320 X 200	12.5	31.5	70
E	16/256K	640 X 200	25	31.5	70
F	Mono	640 X 350	25	31.5	70
10	16/256K	640 X 350	25	31.5	70
11	2/256K	640 X 480	25	31.5	60
12	16/256K	640 X 480	25	31.5	60
12+	16/256K	640 X 480	31.5	37.5	75
13	256/256K	320 X 200	12.5	31.5	70
14, 55	16/256K	1056 X 400	41.5	31.5	70
54	16/256K	1056 X 350	41.5	31.5	70
58, 6A	16/256K	800 X 600	40	37.8	60
58, 6A	16/256K	800 X 600	49.5	46.9	75
5C	256/256K	800 X 600	36	35.2	56
5C	256/256K	800 X 600	40	37.9	60
5C	256/256K	800 X 600	49.5	46.9	75
5D	16/256K (interlaced)	1024 X 768	44.9	35.5	87
5D	16/256K	1024 X 768	65	48.3	60
5D	16/256K	1024 X 768	75	56	70
5D	16/256K	1024 X 768	78.7	60	75
5F	256/256K	640 X 480	25	31.5	60
5F	256/256K	640 X 480	31.5	37.5	75
60*	256/256K (interlaced)	1024 X 768	44.9	35.5	87
60*	256/256K	1024 X 768	65	48.3	60
60*	256/256K	1024 X 768	75	56	70
60*	256/256K	1024 X 768	78.7	60	75
64*	64K	640 X 480	25	31.5	60
64*	64K	640 X 480	31.5	37.5	75
65*	64K	800 X 600	36	35.2	56
65*	64K	800 X 600	40	37.8	60
65*	64K	800 X 600	49.5	46.9	75
66*	32K Direct/256 Mixed	640 X 480	25	31.5	60
66*	32K Direct/256 Mixed	640 X 480	31.5	37.5	75
67*	32K Direct/256 Mixed	800 X 600	40	37.8	60
67*	32K Direct/256 Mixed	800 X 600	49.5	46.9	75
6C*	16/256K (interlaced)	1280 X 1024	75	48	87
* Requires 1MB video memory option


Memory Map

Address Range (in Hex)[Block Range]	Block Size	Resource	Notes
0000_0000 - 0003_FFFF	256 KB	System memory
0004_0000 - 0007_FFFF	256 KB	System memory
0008_0000 - 0009_FFFF  [512 KB - 640 KB]	(4) 32 KB blocks	System memory  or ISA memory	1. Configurable.  2. DRAM is lost if ISA Memory.
000A_0000 - 000B_FFFF  [640 KB - 768 KB]	(4) 32 KB  blocks	System memory  or ISA memory	1. ISA Video Data RAM  2. Supports SMM attribute.
000C_0000 - 000E_FFFF [768 KB - 960 KB]	(12) 16 KB blocks	System memory  or ISA memory	1. Configurable. 2. Can be shadowed/cached. 3. DRAM is lost if ISA Memory.
000F_0000 - 000F_FFFF  [960 KB - 1024 KB]	64 KB	ISA memory	1. System BIOS (Fixed). 2. Can be shadowed / cached. 3. DRAM is lost if not Shadowed.
0010_0000 - 00EF_FFFF [1 MB - 15 MB]	14 MB	System memory  or unused	1. Depends on installed DRAM.
00F0_0000 - 00FF_FFFF  [15 MB - 16 MB]	1 MB	System memory  or EISA/ISA memory	1. Depends on installed DRAM. 2. Can be configured for AT EPROM space*. 3. If AT EPROM enabled, DRAM is lost. 4. Supports SMM attribute
0100_0000 - 3FFF_FFFF [16 MB - 1 GB]	1008 MB	System memory  or Unused	1. Depends on installed DRAM
4000_0000 - BFFF_FFFF [2 GB - 3 GB]	1024 MB	EISA memory or Xpress I/O slave memory
C000_0000 - C1FF_FFFF  [3 GB - (3G + 32 MB)]	32 MB	Memory mapped math coprocessor (Weitek)
C200_0000 - FEBF_FFFF  [(3GB + 32 MB) - (3GB + 976 MB)]	944 MB	EISA memory
FEC0_0000 - FEC0_0FFF	4 KB	I/O APIC #1	Default for ESC
FEC0_1000 - FEC0_1FFF	4 KB	I/O APIC #2	Default for INCA
FEC0_2000 - FEC0_2FFF	4 KB	I/O APIC #3
FEC0_3000 - FEC0_3FFF	4 KB	I/O APIC #4
FEC0_4000 - FFDF_FFFF	32752 KB	EISA memory
FFE0_0000 - FFFF_FFFF  [(3GB + 1008 MB) - (3 G + 1024 MB)]	32 MB	EISA (BIOS/ECU)
*The top 128 KB of this area is used for EPROM. The remaining 896 KB is available for AT add-in cards.


I/O Map

Note:  ISA boards may only use the I/O region from 100H to 3FFH.

Hex Address(es)	Resource	Notes
0000 - 001F	DMA Controller 1	ESC
0020 - 0021	Interrupt Controller 1	ESC
0022 - 0023	ESC Configuration Space Access Ports
0024 - 0025	AIP Configuration Space Access Ports
0026 - 0027
0040 - 005F	Programmable Timer	ESC
0060 - 0064	Keyboard Controller	Keyboard chip select from ESC
0061	NMI Status & Control Register	ESC
0070	NMI Mask (bit 7) & RTC Address (bits 6:0)	Write Only.
0071	Real Time Clock (RTC)	RTC chip select from ESC
0080 - 0081	PCEB BIOS Timer
0080 - 008F	DMA Low Page Register	ESC
0092	System Control Port A ( PC-AT control Port)	INCA Register
0094	Video Display Controller	Cirrus 5430
00A0 - 00BF	Interrupt Controller 2	ESC; 82374EB
00C0 - 00DF	DMA Controller 2	ESC;82374EB
00F0	Clear NPX error	Resets IRQ13
00F8 - 00FF	x87 Numeric CoProcessor
0102	Video Display Controller
0170 - 0177	Secondary Fixed Disk Controller (IDE)
01F0 - 01F7	Primary Fixed Disk Controller (IDE)
0200 - 0207	Game I/O Port
0220 - 022F	Serial Port A
0238 - 023F	Serial Port A
0278 - 027F	Parallel Port 3
02E8 - 02EF	Serial Port B
02F8 - 02FF	Serial Port B
0338 - 033F	Serial Port B
0370 - 0375	Secondary Floppy
0376	Secondary IDE
0377	Secondary IDE/Floppy
0378 - 037F	Parallel Port 2
03B4 - 03BA	Monochrome Display Port
03BC - 03BF	Parallel Port 1
03C0 - 03CF	Video Display Controller
03D4 - 03DA	Color Graphics Controller
03E8 - 03EF	Serial Port A
03F0 - 03F5	Floppy Disk Controller
03F6 - 03F7	Primary IDE - Secondary. Floppy
03F8 - 03FF	Serial Port A (Primary)
0400 - 043F	DMA Controller 1, Extended Mode Registers.	ESC
0461	Extended NMI / Reset Control	ESC
0462	Software NMI	ESC
0464	Last EISA Bus master granted
0480 - 048F	DMA High Page Register.	ESC
04C0 - 04CF	DMA Controller 2, High Base Register.
04D0 - 04D1	Interrupt Controllers 1 and 2 Control Register.
04D4 - 04D7	DMA Controller 2, Extended Mode Register.
04D8 - 04DF	Reserved
04E0 - 04FF	DMA Channel Stop Registers
0678-067A	Parallel Port (ECP)
0778-077A	Parallel Port (ECP)
07BC-07BE	Parallel Port (ECP)
0800 - 08FF	NVRAM
0C80 - 0C83	EISA System Identifier Registers	ESC
0C84	Board Revision Register
0C85 - 0C86	BIOS Function Control
0CF8	PCI CONFIG_ADDRESS Register	PCMC
0CF9	PCMC Turbo and Reset control
0CFC	PCI CONFIG_DATA Register	PCMC
n000 - n0FF	EISA Slot n I/O Space	n = 1 to 15.
x100 - x3FF	ISA I/O slot alias address	alias of 100H - 3FFH.
n400 - n4FF	EISA Slot n I/O Space	n = 1 to 15.
x500 - x7FF	ISA I/O slot alias address	alias of 100H - 3FFH.
n800 - n8FF	EISA Slot n I/O Space	n = 1 to 15.
x900 - xBFF	ISA I/O slot alias address	alias of 100H - 3FFH.
nC00 - nCFF	EISA Slot n I/O Space	n = 1 to 15.
xD00 - xFFF	ISA I/O slot alias address	alias of 100H - 3FFH.
46E8	Video Display Controller
xx00 - xx1F*	SCSI registers	AIC-7870
*SCSI I/O base address is set using configuration registers.


Interrupts & DMA Channels

Source	PCI or ISA Interrupt	Device Input
PCI Conn. A	INTA#	INCA PCI 0
PCI Conn. B	INTA#	INCA PCI 1
PCI Conn. C	INTA#	INCA PCI 2
PCI Conns. A,B,C	INTB#	INCA PCI 5
PCI Conns. A,B,C	INTC#	INCA PCI 6
PCI Conns. A,B,C	INTD#	INCA PCI 7
Timer	IRQ00	ESC IRQ0
Keyboard	IRQ01	ESC IRQ1
Serial Port B	IRQ03 for COM2 (typ.)	INCA PCI 11
Serial Port A	IRQ04 for COM1 (typ.)	INCA PCI 10
SCSI IRQ		INCA SCSI 0
Parallel Port	IRQ05	INCA SCSI 1
Floppy	IRQ06	INCA XXINT 0
Parallel Port	IRQ07	INCA XXINT 1
Video	IRQ09	INCA PCI 8
	IRQ10	ESC IRQ10
	IRQ11	ESC IRQ11
Mouse	IRQ12	ESC IRQ12
Math error	IRQ13	ESC IRQ13
IDE	IRQ14	INCA PCI 9
	IRQ15	ESC IRQ15


PCI SCSI Interface

The ALTServer platform integrates an Adaptec AIC-7870 SCSI controller, which supports both narrow SCSI-2 (10 MB/s) and wide SCSI-2 (20 MB/s). The AIC-7870 supports processor-to-PCI and PCI-to-PCI transfers, with an embedded 8 MIPs processor and 256 byte FIFO. As a PCI bus master, the SCSI controller supports burst data transfer rates of up to 133 MB/second at a 66 MHz bus speed. Transfer rates are 120 MB/second at 60 MHz and 100 MB/second at 50 MHz bus speeds.

For best results when mixing wide & narrow devices reserve device IDs 0-7 for narrow devices and put all your wide devices on IDs 8-15.


Standard I/O and Advanced Integrated Peripheral (AIP) Component

The EISA bus on the ALTServer baseboard supports the Intel Advanced Integrated Peripheral (AIP) component for standard I/O devices. The AIP contains a floppy disk controller (FDC), two serial ports, a multi-function parallel port, an IDE interface, and a game port on a single chip. The high integration provides low-cost, low-power consumption, and minimal impact on board real estate. The FDC is an 82078 core with a data rate of up to 2 MB/second. The serial ports are 16550-compatible with 16-byte FIFOs. The parallel port supports the Enhanced Capabilities Port (ECP) protocol with DMA, EPP protocol, and IEEE-1284 protocol for PS/2 bi-directional compatibility. The IDE interface supports 8- or 16-bit I/O and 16-bit DMA. The AIP host interface is 8-bit ISA.


ALTServer Help - Board Level Features - IDE Interface
IDE Interface

IDE is an interface for intelligent disk drives with onboard AT disk controller electronics. The 16-bit IDE interface consists of address decode (provided by the AIP), address, command, and data buffers, 40-pin connector, and 4-pin hard disk activity LED connector. The AIP selects the IDE device and enables the data buffers between the IDE cable and the bus. When IDE is disabled via the BIOS configuration utility, the I/O address space and interrupt (IRQ14) are available for use by add-in cards. The system BIOS may disable the interface when it finds the registers of another hard disk controller. When IDE DMA is enabled by the AIP and INCA, the IDE hard disk is then accessible through the DMA channel configured in the INCA. The standard I/O logic accommodates both compatible and Type F DMA cycles to IDE. AC timing constraints allow support for only Type 2 IDE drives in the CAM specification (or faster).


Keyboard and Mouse Interface

An Intel 8242 surface mount microcontroller contains the Phoenix-based PS/2 compatible keyboard/mouse PE controller code. PS/2-style keyboard and mouse connectors are located on the I/O riser that connects at the back panel side of the baseboard. The 5V line on this connector is protected with a PolySwitch* circuit which acts much like a self-healing fuse, re-establishing the connection after an over-current condition is removed. While this device eliminates the possibility of having to replace a fuse, care should be taken to turn off the system power before installing or removing a keyboard.

The 8242 microcontroller code supports Power-On/Reset (POR) password protection. The POR password is set via the System Configuration Utility. The keyboard controller also provides for the following "hot key" sequences:

•	CTRL-ALT-DEL: System software reset. This sequence performs a software reset of the system by jumping to the beginning of the BIOS code and running the POST operation.

•	CTRL-ALT+ and CTRL-ALT-: Turbo mode selection. CTRL-ALT- sets the system for de-turbo mode and CTRL-ALT+ sets the system for turbo mode (normal operation). Changing the Turbo mode may be prohibited by an operating system or application software.

•	HOT Key X (Immediate Secure): Disables mouse and keyboard immediately. It also disables the power down timer, but it does not place the system into a powered down state. This hot key will work only if a password is enabled in the BIOS.


Dallas DS12887 Real Time Clock, CMOS RAM and Battery

The Real Time Clock (RTC) is implemented using a Dallas DS1587 device. The DS1587 is accurate to within 13 minutes/year and requires no external support. The oscillator and battery are integrated into the device and the estimated life-span of the battery is 10 years. The RTC can be set via the System Configuration Utility (SCU). CMOS memory supports the standard 128byte batterybacked RAM, fourteen bytes for clock and control registers, and 114 bytes of general purpose non-volatile CMOS RAM. All CMOS RAM is reserved for BIOS use. The CMOS RAM can be set to specific values or cleared to the system default values using the SCU. Also, the CMOS RAM values can be cleared to the system defaults by using a hardware jumper.


ALTServer Help - Board Level Features - I/O Riser Board
I/O Riser Board

I/O connectors appear on a riser, not on the ALTServer baseboard. This allows great flexibility in chassis design and external I/O connector types, whether the customer desires PS/2 style keyboard and mouse connectors or an AT-style DIN keyboard connector.

The I/O riser also can provide either a Wide or Narrow SCSI connection to the SCSI-2 controller on the baseboard. The SCSI connector may be on either side of the I/O Riser, allowing for cabling to external SCSI peripherals or internal peripherals. The use of an internal Wide SCSI connector is appropriate because the baseboard itself provides only a Narrow SCSI connector.

A number of I/O riser options are available. The following diagram is an example of a riser that provides PS/2 style keyboard/mouse connectors and an external Narrow SCSI connector.  The I/O riser uses a 144-pin connector that is mechanically similar to a 72-bit SIMM module connector, but has 144-pins. The appendix details the pin-out of this connector.

Figure. Example of I/O riser board


Expansion Slots (PCI and EISA)

The ALTServer baseboard allows the addition of up to eight I/O expansion cards, and provides interfaces to the the ISA bus, the EISA bus, and the PCI loca bus. There are six EISA bus expansion connectors and three PCI expansion connectors. One expansion slot is shared by connectors which will accommodate either an EISA or a PCI expansion card, but not both at the same time. All three PCI expansion slots accept PCI master cards and fully support the PCI 2.0 specification. The six EISA bus expansion connectors will accept either EISA or ISA add-in cards. All six slots will accept either EISA/ISA bus masters or EISA/ISA slave cards.

The PCI bus on the ALTServer runs at half the external bus speed of the installed processor. For example, the external bus speed of the 100 MHz processor is 66 MHz, and the PCI bus is clocked at 33MHz. By dividing the PCI bus clock by either 3 or 4, the EISA bus clock can be derived. The table below shows an example:

Processor Clock Speed	External Bus Speed	PCI Bus Speed	Divisor	EISA Clock
75 MHz	50 MHz	25 MHz	3	8.33 MHz
90 MHz	60 MHz	30 MHz	4	7.5 MHz
100 MHz	66 MHz	33 MHz	4	8.33 MHz
120 MHz	60 MHz	30 MHz	4	7.5 MHz
133 MHz	66 MHz	33 MHz	4	8.33 MHz
167 MHz	66 MHz	33 MHz	4	8.33 MHz
Table 2. ALTServer clock frequencies and bus speeds


Peripheral Component Interconnect (PCI) Chip Set

The baseboard's two dedicated PCI expansion slots and one PCI/EISA combination slot are controlled by the Intel Neptune PCIset. The ALTServer uses one 82434NX PCI/Cache/Memory Controller (PCMC) and two 82433NX Local Bus Extension (LBX) devices. Together they provide a PCI interface, as well as DRAM memory and cache controller functions, including:

• 	Processor reset control

• 	Processor L1 cache control

• 	Processor burst mode control

• 	Processor interface control

• 	Integrated second level write-back cache

controller with tag comparator

•	Fast Page-mode DRAM controller

• 	Burst memory read/write control logic

• 	Data bus conversion to PCI

• 	Parity generation/detection to memory

Related Topics:

82434NX PCI/Cache/Memory Controller (PCMC)

82433NX Local Bus eXtension (LBX)

Host-to-pci bridge

PCI/EISA BrIdge (PCEB) & EISA System Component (ESC)


82434NX PCI/Cache/Memory Controller (PCMC)

The 82434NX provides all control signals necessary to drive a second level cache and the DRAM array, including multiplexed address signals. It also controls system access to memory and generates snoop controls to maintain cache coherency. The PCMC integral memory controller manages up to 256 MB of SIMM DRAM and controls either a Burst or Asynchronous Cache of either 256 KB or 512 KB. It also maintains full cache coherency between the Cache and main memory when both processors are installed.


82433NX Local Bus eXtension (LBX)

There are two 82433NX components which provide data bus buffering and dual port buffering to the memory array, LBX-H and LBX-L. LBX-H decodes the 64-bit data lines (16:31) & data lines (48:63), while LBX-L decodes the other data lines (0:15) & (32:47). The use of two 82433NX components provides a 64-bit data path from the processors to main memory. Controlled by the 82434NX, the 82433NX devices add one load each to the PCI bus and perform all the necessary byte and word swapping required. Memory and I/O write buffers are included in these devices.


Host-to-pci bridge

The PCI control section of the PCMC and the two LBX components form a Host-to-PCI bridge subsystem. This subsystem provides the interface between the processors and the PCI bus, providing for a transfer rate of up to 132 MB/second and full concurrence between processor Host bus and PCI bus transactions. Five integral Write Posting and Read Prefetch buffers increase PCI Master add-in performance.

The PCMC/LBX Host-to-PCI bridge is designed to conform to the PCI Local Bus Specification 2.0, and guidelines in the PCI System Design Guide.


PCI/EISA BrIdge (PCEB) & EISA System Component (ESC)

The baseboard has five dedicated and one shared 32-bit EISA I/O expansion slots. The 82375EB PCI-EISA Bridge (PCEB) and 82374EB EISA System Component (ESC) provide a bridge between the PCI local bus and the EISA bus. The PCEB has the following features:

•	Address, data paths, and bus protocol translation for PCI-EISA transfers

•	Extensive data buffering in both directions that increases system performance and allows concurrence between the PCI bus and EISA bus

•	Bus parity checking and error reporting

The ESC provides support for an EISA-compatible I/O subsystem, including:

•	EISA (master and slave) interface

•	EISA bus controller and arbitration

•	Enhanced 7-channel DMA controller with scatter/gather support

•	14-channel interrupt controller, five programmable timer/counters, and NMI logic.

•	Support logic for Xbus buffer and devices, including chip selects for Flash BIOS, Real time Clock (RTC), NVRAM and keyboard/mouse controller.


Interrupt Control ASIC (INCA) Component

Feature description

Interrupt Handling

Error Interrupts

Dual Pentium Processor (SMP) Operation

Symmetric Multiprocessing (SMP) Software Considerations

SMP Operating System Requirements

Single Processor Operation

System Management Interrupt (SMI) Support

Critical Event Logging

Security and Server Monitoring Features


Feature description

The Interrupt Control ASIC (INCA) collects many functions into a single component to enhance functionality, reduce part count, and reduce system cost. The main functions include providing both PCI interrupt control and unique security and server management features.

The following INCA features are used on the ALTServer baseboard:

•	Interrupt control:

I/O Advanced Programmable Interrupt Controller (APIC)

Serial port interrupt steering to any ISA interrupt

IDE interrupt steering to any ISA interrupt

PCI interrupt steering for the PCI auto-configuration

•	Security and Server Monitoring features:

Watchdog timer (software start/reset) will reset system if it expires

Keyboard/mouse inactivity; if detected, blanks video and locks floppy, requires password to re-enable

Baseboard voltage (12V, -12V, 5V, -5V, 3.3V) monitoring.

Baseboard temperature monitoring for out of range

Chassis door switch or improper entry monitoring

•	PCI Clock generation - 14 PCI clock drivers

•	General purpose I/O bits, used for 3-mode (720KB, 1.44MB, 2.88MB) floppy control, and other functions

•	DMA steering for IDE and parallel port to one of four possible ISA DRQs/DACKs

•	Support for front panel interface and LCD display


Interrupt Handling

This important element of the ALTServer design provides great flexibility in interrupt routing. Interrupt sources come from the PCI and EISA/ISA slots and onboard devices and need to be routed to either a single or dual processor. The following diagram illustrates the interrupt structure on the ALTServer Baseboard.

Figure 4. ALTServer interrupt structure


Error Interrupts

The traditional server platform will typically generate a Non-Maskable Interrupt (NMI) whenever a memory or bus error occurs. Traditional sources for an NMI are memory system parity error, EISA bus master time-out, or IOCHK#. The PCI bus adds two new sources of error detection which must be managed: PCI bus parity and PCI system error (SERR).

PCI bus parity is performed by the PCI source of the transaction which generates the bus parity while the destination checks it. If a parity error occurs (PERR# asserted one clock after the offending bus cycle), the current PCI bus master manages the error. The master may retry the transfer or may pulse SERR#. An asserted SERR# causes the ESC to generate an NMI. The PCMC manages the SERR# assertion for various conditions.


Dual Pentium Processor (SMP) Operation

In the dual processor configuration, the interrupt routing is performed by the Advanced Programmable Interrupt Controller (APIC) bus. Each processor has an on-chip local APIC device that can receive interrupts driven onto the APIC bus by I/O APIC devices. Both the INCA and 82374EB EISA System Component (ESC) incorporate I/O APICs that drive individual interrupts onto the APIC bus. All of the EISA/ISA interrupts are routed to the ESC component and all PCI interrupts are routed to the INCA component. This allows any external interrupt to be routed to the processor. For further details, refer to the operating system documentation and the Intel 82489 APIC data sheet.


Symmetric Multiprocessing (SMP) Software Considerations

The ALTServer Baseboard and BIOS comply with the Intel MultiProcessor (MPS) Specification, revision 1.1. This standard defines a method of constructing systems in which two or more processors operate concurrently. These processors operate in a tightly coupled architecture in which each processor has the same 'view' of the system, and in which each processor can interrupt any other processor. This architecture has the following features:

•	Each processor sees the same memory and I/O space, requiring only one copy of the operating system.

•	Any task can run on any processor, reducing the chance that the failure of one or more processors will render the system unusable. Tasks can be written generically, without regard for which processor they will be executing on.

The use of an Advanced Programmable Interrupt Controller (APIC) is specified for interrupt detection and notification. This reduces the load on the system bus, since the APICs use a serial bus to transmit and receive interrupts.


SMP Operating System Requirements

To obtain the benefits from using a second processor on the ALTServer platform, it is essential to use an operating system that is capable of Symmetric MultiProcessing and which has driver support for the Intel MultiProcessor Specification, version 1.1. This allows the software load to be distributed across the processors and for the operating system and application process to be shared efficiently. Most server operating systems now have this functionality. However, DOS and Microsoft Windows 3.1, 3.11 and Windows '95 do not have this capability and will see no performance increase from adding a second processor.

The following table shows which server operating systems support Intel  MPS v1.1 and ALTServer:

Operating System	Version
Microsoft Windows NT	3.1, 3.5
Novell UnixWare	2. 0
Novell USL/USG	System V.4.2 MP
IBM OS/2*	2.11 SMP
SunSoft Solaris for x86	2.4
SCO OpenServer + MPX	3.1
Banyan Vines*	5.54
Table 1. MultiProcessing operating system support


Single Processor Operation

All EISA/ISA interrupts are routed to the ESC component and all PCI interrupts from onboard PCI devices and PCI slots are routed to the INCA component. Under software control, the PCI interrupts can be routed from the INCA inputs to any of the ESC interrupt inputs. This allows PCI interrupts to be 'patched' into the standard PC interrupt structure. This routing is done dynamically at power-on by the Plug and Play BIOS by examining each device, assigning an interrupt to it, and programming the INCA device accordingly.


System Management Interrupt (SMI) Support

The EISA System Component (ESC) has added an SMIin# (pin 185). This pin is under software control and if enabled, asserts SMI# to the Processor. SMI# is of higher priority than NMI or INTR to the Pentium Processor. Assertion of SMIin# causes an SMI# and the processor switches memory space and begins execution of the SMM handler. SMM creates a secure memory space that the processor can use for ALTServer fault management.


Critical Event Logging

During POST, the BIOS will initialize the SMI RAM with code to log errors into non-volatile memory. Each processor will have a private area of SMI RAM dedicated to it for SMI processing. The INCA and PCEB/ESC will be programmed to generate SMI for memory errors, bus parity errors, PCI SERR and PERR, EISA bus time-outs, EISA software generated NMI, I/O channel check, and EISA watchdog time-out. When these errors are detected, the SMI routines will log the error or event, and then will cause an NMI to be generated, so that operating systems can respond appropriately.

If the OS is using the INCA watchdog timer to detect software or hardware failures, and that timer expires, an Asynchronous System Reset (ASR) will be generated, which is equivalent to a hard reset, except that the watchdog timer status will not be reset. The POST portion of the BIOS will detect this event as the system reboots, and will log this event to the logging area.

The System Management Log Area will be a minimum of 8192 bytes of non-volatile memory space. The format of the System Management Log Area will be based on the Xpress Server Management Critical Event Logging area format. The event logs will be a superset of the Xpress event logs. For more detail, please refer contact your Intel sales representative for the BIOS Extrernal Product Specification.


Security and Server Monitoring Features

Incorporated into the ALTServer design are a number of features that enhance the reliability and security of the platform and meet the needs for high availability servers. Most of the hardware functionality is incorporated into the INCA device, which provides the following monitoring features:

•	Watchdog timer (software start/reset) will reset system if it expires

•	Keyboard/mouse inactivity; if detected, blanks video and locks floppy, requires password to re-enable

•	Baseboard voltage (12V, -12V, 5V, -5V, 3.3V); if out of range, generates System Management Interrupt

•	Baseboard temperature and chassis door switch monitoring for out of range or illegal entry

In addition the BIOS incorporates further security and monitoring functionality:

•	User password - when specified must be entered to allow system boot

•	Administrative password - when specified it must be entered to enter the System Configuration Utility (SCU) and change the configuration of the system

•	Inactivity timer - if there is no keyboard or mouse activity within a specified time then the screen blanks and the User password must be entered to resume operation

•	Hot key activation - allows the Inactivity timer to be activated by using a definable 'Hot Key' sequence


Connectors / Signal Locations

I/O Riser Board

PCI SCSI CONNECTORS

PS/2 Style Mouse/Keyboard

Serial Ports

Parallel Port

Graphics Monitor Port

Front Panel and LCD Display

Primary Power

12V Fan Power

IDE Interface

Server Monitor Module (SMM) Feature Connector

SCSI Termination

Jumpers

PCI Connectors


ALTServer Help - Connectors / Signal Locations - I/O Riser Board
I/O Riser Board

The following table shows the pinout of the I/O riser board connector on the motherboard, indicating corresponding I/O connector pins. This connector is similar to a standard 144-pin SIMM connector.

Pin	I/O Connector Pin	Pin	I/O Connector Pin	Pin	I/O Connector Pin	Pin	I/O Connector Pin
1	Mouse 4	37	SCSI 48	73	Ground	109	SCSI 39
2	Mouse 1	38	SCSI 47	74	Ground	110	SCSI 38
3	Mouse 5	39	SCSI 46	75	Ground	111	SCSI 37
4	Keyboard 4	40	SCSI 45	76	Ground	112	SCSI 36
5	Keyboard 1	41	Video 15	77	Ground	113	SCSI 35
6	Keyboard 5	42	Ground	78	Ground	114	Ground
7	Serial Port A 4	43	Video 14	79	Ground	115	Ground
8	Serial Port A 3	44	Video 13	80	Ground	116	Ground
9	Serial Port A 2	45	Ground	81	Ground	117	Ground
10	Serial Port A 1	46	Video 12	82	Ground	118	Ground
11	Serial Port A 6	47	Video 11	83	Ground	119	Ground
12	Serial Port A 7	48	Video 1	84	Ground	120	Ground
13	Serial Port A 8	49	Video 2	85	Ground	121	Ground
14	Serial Port A 9	50	Video 3	86	Ground	122	Ground
15	Serial Port B 4	51	Ground	87	Ground	123	Ground
16	Serial Port B 3	52	Video 4	88	Ground	124	Ground
17	Serial Port B 2	53	Parallel Port 13	89	Ground	125	Ground
18	Serial Port B 1	54	Parallel Port 12	90	Ground	126	Ground
19	Serial Port B 6	55	Parallel Port 11	91	Ground	127	Ground
20	Serial Port B 7	56	Ground	92	Ground	128	Ground
21	Serial Port B 8	57	Parallel Port 10	93	Ground	129	Ground
22	Serial Port B 9	58	Ground	94	Ground	130	Ground
23	SCSI 17	59	Parallel Port 9	95	Ground	131	Ground
24	SCSI 18	60	Parallel Port 8	96	Ground	132	Ground
25	SCSI 19	61	Parallel Port 7	97	Ground	133	Ground
26	SCSI 63	62	Parallel Port 6	98	SCSI 68	134	Ground
27	SCSI 62	63	Parallel Port 5	99	SCSI 67	135	Ground
28	SCSI 61	64	Parallel Port 17	100	SCSI 66	136	Ground
29	SCSI 60	65	Parallel Port 4	101	SCSI 65	137	Ground
30	SCSI 59	66	Parallel Port 16	102	SCSI 64	138	Ground
31	SCSI 58	67	Parallel Port 3	103	SCSI 16	139	Ground
32	SCSI 57	68	Parallel Port 15	104	SCSI 44	140	Ground
33	SCSI 55	69	Parallel Port 2	105	SCSI 43	141	Ground
34	SCSI 53	70	Parallel Port 14	106	SCSI 42	142	Ground
35	SCSI 52	71	Ground	107	SCSI 41	143	Ground
36	SCSI 51	72	Parallel Port 1	108	SCSI 40	144	Ground


PCI SCSI CONNECTORS

The baseboard contains a 50-pin Fast/Narrow SCSI-2 connector for narrow SCSI-2 peripherals such as disk drives, CD-ROMs, and tape drives that are installed within the system chassis. Signals for both narrow and wide SCSI interfaces are routed to the header for the I/O riser. A selection of I/O risers offers a variety of combinations of either narrow or wide SCSI connections.

For wide SCSI devices, I/O riser cards are available that provide either an internal or external SCSI connection. The internal I/O riser for wide SCSI has the connector on the opposite side of the video and serial port connectors. This allows wide SCSI cabling to wide SCSI disk drives mounted inside the system chassis. The external version is similar to the narrow SCSI riser and could be used, for example, to connect with an external disk drive unit.


PS/2 Style Mouse/Keyboard

The keyboard and mouse connectors are mounted on the I/O riser board. The mouse connector is normally stacked over the keyboard connector. I/O riser connector pin numbers are shown in parentheses.

Pin	Keyboard Signal	Description
1 (5)	KEYDAT	Keyboard Data
2	(NC)	Not connected
3	GND	Ground
4 (4)	FUSED_VCC	Supply voltage (via fuse, shared by mouse connector)
5 (6)	KEYCLK	Keyboard Clock
6	(NC)	Not connected
The mouse connector is PS/2 compatible, with pinout shown below:

1 (2)	MSEDAT	Mouse Data
2	(NC)	Not connected
3	GND	Ground
4 (1)	FUSED_VCC	Supply voltage
5 (3)	MSECLK	Mouse Clock
6	(NC)	Not connected


Serial Ports

Two 9-pin connectors are provided on the I/O riser board for Serial ports A and B. By default, port A is the top connector. Each port can be set to one of four different COMx ports (refer to the I/O address map), and can be enabled separately. When enabled, each port can be programmed to generate edge or level sensitive interrupts. When disabled, serial port interrupts are available to add-in cards. I/O riser connector pins for ports A and B respectively, are shown in parentheses.

Pin	Name	Description
1 (7, 18)	DCD	Data Carrier Detected
2 (8, 17)	RXD	Receive Data
3 (9, 16)	TXD	Transmit Data
4 (10, 15)	DTR	Data Terminal Ready
5	GND	Ground
6 (11, 19)	DSR	Data Set Ready
7 (12, 20)	RTS	Return to Send
8 (13, 21)	CTS	Clear to Send
9 (14, 22)	RIA	Ring Indication Active


Parallel Port

The AIP provides one PS/2-compatible, 25-pin bi-directional parallel port. BIOS programming of the AIP configuration registers enable the port, and determine the port address and interrupt. When disabled, the interrupt is available to add-in cards. The parallel port connector appears on the I/O riser board (pins shown in parentheses):

Pin	Name	Pin	Name
1 (72)	STROBE#	14 (70)	AUFDXT#
2 (69)	D0	15 (68)	ERROR#
3 (67)	D1	16 (66)	INIT#
4 (65)	D2	17 (64)	SLCTIN#
5 (63)	D3	18	GND
6 (62)	D4	19	GND
7 (61)	D5	20	GND
8 (60)	D6	21	GND
9 (59)	D7	22	GND
10 (57)	ACK#	23	GND
11 (55)	BUSY	24	GND
12 (54)	PE	25	GND
13 (53)	SLCT


Graphics Monitor Port

Pin	Signal	Pin	Signal
1 (48)	RED	9	GND
2 (49)	GREEN	10	GND
3 (50)	BLUE	11 (47)	Pull-up
4 (52)	Pull-up	12 (46)	Pull-up
5	GND	13 (44)	HSYNC
6	GND	14 (43)	VSYNC
7	GND	15 (41)	Pull-up
8	GND


Front Panel and LCD Display

The INCA component drives a front panel interface and LCD display. Additional required circuitry consists primarily of two ICs and one 34-pin connector. The electrical interface on the ALTServer is compatible with the Stanley (Intel P/N 632397-001) LCD Display. For complete information, refer to the data sheet for the Sharp component. The connector is for a 34-pin ribbon cable that connects to a distribution board for LEDs, key lock assembly and LCD display, with pinout shown below:

Pin	Signal	Function
1	SPKDAT	Speaker DATA
2	+5V
3	+5V STANDBY
4	PS-ON	Power Supply remote control through INCA and SMM card
5	FP-RESET#	Front Panel Reset
6	0V
7	LCD-VCC	LCD Voltage
8	0V
9	HD1 LED VCC	Internal Controller Drive LED
10	HD1 LED RTN	Internal Controller Drive LED RETURN
11	HD2 LED RTN	ADD-IN Controller Drive LED RETURN
12	HD2 LED VCC	ADD-IN Controller Drive LED
13	KEYBD KEYLOCK#	Front Panel Keylock Switch
14	0V
15	SECURE MODE	Secure Mode Status from Main Board
16	CHASSIS SWT	Chassis Door Switch
17	KEY
18	+5V
19	I2C-SDA	I2C Serial Data
20	CHASSIS SWT RET	Chassis Door Switch Return
21	LCD-SD	LCD Serial Data
22	KS#	Kick Start RTC
23	LCD-SCLK	LCD Serial Clock
24	I2C-SCL	I2C Clock
25	LCD-PCLK	LCD Parallel Clock
26	0V
27	EN	Reserved
28	0V
29	RW	LCD READ/WRITE
30	N/C
31	RS	Reserved
32	PWR#	Shut Down Power
33	LCD-VDD	LCD Enable
34	0V


Primary Power

The ALTServer uses a 12-pin standard AT power supply connector with the following pinout:

Pin	Signal	Pin	Signal
1	PWRGOOD	7	GND
2	+5V	8	GND
3	+12V	9	-5V
4	-12V	10	+5V
5	GND	11	+5V
6	GND	12	+5V


12V Fan Power

There are two fan connectors, both appropriately located for the placement of a fan. The connectors are 3-pin, single in-line, .025 in. square pin with the following pinout:

Pin	Signal
1	Fan Rotation Sense
2	+12V
3	GND


ALTServer Help - Connectors / Signal Locations - IDE Interface
IDE Interface

The 40 pin IDE connector is located on the baseboard. The IDE interface does not support the Enhanced IDE (E-IDE) specification so the maximum number of disk drives that may be connected is two.

Pin	Function	Pin	Function
1	IDERST*	21	IDEDRQ
2	GND	22	GND
3	ID7	23	IDEIOW*
4	ID8	24	GND
5	ID6	25	IDEIOR*
6	ID9	26	GND
7	ID5	27	CHRDY
8	ID10	28	SPSYNC
9	ID4	29	IDEDAK*
10	ID11	30	GND
11	ID3	31	IDEIRQ14
12	ID12	32	IDEIO16*
13	ID2	33	IDESA1
14	ID13	34	PDIAG*
15	ID1	35	IDESA0
16	ID14	36	IDESA2
17	ID0	37	IDECS0*
18	ID15	38	IDECS1*
19	GND	39	IDEHDACT*/DRVPRES*
20	Keyed	40	GND


Server Monitor Module (SMM) Feature Connector

When the Server Monitor Module is installed in an ALTServer system, several features are available which are not available in other systems.  In order to utilize these features, the Server Monitor Module (SMM)  feature connector must be installed.  Refer to the user's manual for installation instructions.

The Server Monitor Module (SMM)  feature connector is a standard 20-pin dual row BERG ("stake pin") connector with 0.025" square posts. The figure below illustrates the pin assignments for the Server Monitor Module (SMM)  feature connector.

Figure:  Server Monitor Module (SMM)  Feature Connector Pinout

Table :  Server Monitor Module (SMM) Feature Connector Signal Descriptions*

Name	Pin#	Type	Description
SMI#	1	Input	System Management Interrupt.  This signal indicates that the XXpress host System Management Interrupt (SMI) has been activated.  This signal is routed to a bit in the Host Interrupt Code register on the Server Monitor Module for detection by the Server Monitor Module Software. Used for informational purposes only.
I2CCLK	2	I/O	I2C Clock.  Serial communication clock driven by PCF8584 I2C bus controller.  Frequency is determined by a register in PCF8584, and is <100kHz.  Note:  This signal is normally not driven, as the PCF8584 is not part of the standard Server Monitor Module product.
GND	3	Power	Electrical Ground.
key	4		No Connection.
PWROFF#	5	Output	Power Supply (active low).  When activated, PWROFF# will force the host's power supply to shut down.  When activated, PWROFF# will allow the host's power supply to operate again.
I2CDATA	6	I/O	I2C Data signal.  Serial data from/to PCF8584 I2C bus controller. Note:  This signal is normally not driven, as the PCF8584 is not part of the standard Server Monitor Module product.
LPOK	7	Input	Line Power OK.  Indicates that the XXpress host's power cord is plugged in and AC power is available (usually connected to 5VSTNDBY on the XXpress baseboard).
KEYUNLK	8	Output	Keyboard Unlock.  When this signal is inactive, the XXpress host will lockout the keyboard, rendering it non-operative.  When HKEYUNLK is active, the XXpress host will not lock the keyboard out based on The Server Monitor Module's command (but the keyboard can be locked out by other devices).
NMI	9	Input	Non-Maskable Interrupt.  This signal indicates the XXpress baseboard has activated its NMI. This signal is routed to a bit in the Host Interrupt Code register on the Server Monitor Module for detection by the Server Monitor Module Software. Used for informational purposes only.
3.3V	10	Input	3.3V power.  This pin should be connected to the 3.3V power plane on the XXpress baseboard.  If 3.3V is not present on a baseboard, this pin should be connected to electrical ground.
HRESET#	11	Output	Reset server.  This signal is a hardware-controlled 17.36s pulse (active-low pulse) which should cause a hard-reset of the server.
GND	12	Power	Electrical Ground
GND	13	Power	Electrical Ground
key	14		No Connection
SECURE	15	Input	Host in Secure Mode.  Indicates that the keyboard controller on the XXpress host has entered the secure mode.  Used for informational purposes only.
GND	16	Power	Electrical Ground.
INTRUD	17	Input	Intruder. When active, this signal indicates that the host server's chassis is open.  When inactive, the chassis is secure. Used for informational purposes only.
SPARE	18		No Connection.  Reserved for future use.
key	19		No connection.
GND	20	Power	Electrical Ground.
* Signals with a "#" (pound symbol) are active-low signals

Table 1:  SMM Feature Connector DC Electrical Specifications

Name	Direction	Type	IIH	IIL	IOH	IOL
SMI#	Input	TTL	-1uA	1uA
I2CCLK	I/O	TTL
PWROFF#	Output	TTL			4mA	4mA
I2CDATA	I/O	TTL
LPOK	Input	CMOS	10uA	10uA
KEYUNLK	Output	TTL			4mA	4mA
NMI	Input	TTL	-1uA	1uA
HRESET#	Output	TTL			4mA	4mA
SECURE	Input	TTL	10uA	10uA
INTRUD#	Input	TTL	10uA	10uA
Table 2:  3.3V Electrical Specifications

Parameter	Conditions	Min	Typ	Max	Units
Input Voltage Range	0oC to 70oC	0	3.3	5.6	Volts
Input Current	0oC to 70oC	108	110	112	uA


ALTServer Help - Connectors / Signal Locations - SCSI Termination
SCSI Termination

Termination for all SCSI devices attached to the ALTServer baseboard must be done manually. The baseboard design includes passive termination at one end of the SCSI channel and passive termination at the device. If any SCSI devices are connected to the bus, the passive terminators for that end of the chain must be removed. Click here for  terminator settings of various narrow/wide devices.  Click here for more information.


Jumpers

Figure - Baseboard Jumpers

Purpose	Location	Selection	Description
CMOS Clear	J1B	*1-2, Protect 2-3, Clear	When set to 'Clear' the NVRAM settings will be set to their default values.
Option 2	J7B	*1-2, Option High  2-3, Option Low	Reserved for future feature enhancement options.
Host Bus Frequency 0	J1A	*1-2, Bus:Core=1:2/2:3  2-3,.Bus:Core=1:3/2:5	Used in combination with Jumper J2A to determine Bus Speed to CPU core Ratio. Use table below to set proper ratio. J1A                J2A               Bus:Core               Example CPU
Host Bus Frequency 1	J2A	*1-2, Bus:Core=1:3/2:3  2-3,.Bus:Core=1:2/2:5	1-2                  1-2                 2:3                        PP 75 / 90 / 100 1-2                  2-3                 1:2                        PP 120 / 133 2-3                  1-2                 1:3                        Reserved 2-3                  2-3                 2:5                        PP 150 / 166
Password Clear	J2B	*1-2, Protect  2-3, Clear	When set to 'Clear' the password stored in CMOS will be cleared
Voltage Set	J3A	*1-2, VRE  2-3, Reserved	All C-2 step processors will function under VRE setting.  Prior to Fab-6 of the baseboard this jumper was 1-2 for VR and 2-3 for VRE.
CPU Type	J3B	*1-2, CPU1=Primary  2-3, CPU2=Primary	When set to 'CPU1', the primary CPU is installed in ZIF socket U76
Color	J4A	*1-2, Color  2-3, Monochrome	When set to 'Color', the primary video display supports color graphics.
Reserved	J4B	*1-2, Disable & Ground  2-3, Enable Kick Start	Reserved for future feature enhancement options.
Boot Block	J5A	*1-2, Protect  2-3, Erase/Program	When set to 1-2, the FLASH BIOS region that contains the actual system booting code is protected and cannot be updated.
Speed	J5B J6B	*1-2, 60MHz  2-3, 66MHz  (1-2), 50MHz *1-2, 60MHz  2-3, 66MHz  (2-3), 50MHz	When set to 1-2, either the only CPU or both CPUs are 60/90 Mhz Pentium Processors. These jumpers select the speed of both CPUs and must always be adjusted as a set (J5B and J6B) and not individually.
Flash Code	J6A	*1-2, Erase/Program  2-3, Protected	When set to 2-3, the Flash BIOS is protected and cannot be updated. This setting also protects the BIOS setup and EISA configuration information and prevents the user from changing any system settings. Default jumper (1-2) allows the user to enter and modify selections in the System Config. Utility.
Boot Option	J7A	*1-2, Normal Boot  2-3, Recovery	When set to 'Normal Boot' the system will run from the normal section of the Flash BIOS. Move only when the Flash BIOS becomes corrupted and the system needs to boot from protected recovery BIOS section.


PCI Connectors

Following is a summary of PCI signal pins, including the signal mnemonic, electrical type, full name, and brief description. The electrical types are as follows:

Type	Description
in	Input is a standard input-only signal.
out	Totem Pole Output is a standard active driver.
t/s	Tri-State is a bi-directional, tri-state input/output pin.
s/t/s	Sustained Tri-State is an active low tri-state signal owned and driven by one and only one agent at a time, subject to specific timing restrictions.
o/d	Open Drain allows multiple devices to share signals as a wired-OR.
Signal(s)	Type	Name and Description
AD[31::00]	t/s	Address and Data are multiplexed; during the first clock of a transaction (address phase) they contain a 32-bit physical address; during subsequent clocks, data. As address bits, AD0 and AD1 have no significance; instead, they are encoded to indicate the burst type.
C/BE[3::0]#	t/s	Bus Command and Byte Enable are multiplexed; during the address phase of a transaction, they define the bus command; during the data phase they determine which byte lanes carry valid data.
DEVSEL#	s/t/s	Device Select, when actively driven, indicates the driving device has decoded its address as the target of the current access. As an input, it indicates whether any device on the bus has been selected.
FRAME#	s/t/s	Cycle Frame is driven by the current master to indicate the beginning and duration of an access.
GNT#	in	Grant indicates to the agent that the arbiter has granted access to the bus. This is a point to point signal. Every master has its own GNT#.
IDSEL	in	Initialization Device Select is used as a chip select instead of the upper 24 address lines during configuration read and write transactions.
IRDY#	s/t/s	Initiator Ready indicates the initiating agent's (bus master's) ability to complete the current data phase of the transaction. During a write, IRDY# indicates that valid data is present. During a read, it indicates the master is prepared to accept data.
INT[A-D]#	o/d	Interrupts are defined as "level sensitive" and asserted low using open drain output drivers. The assertion and deassertion of INT[A-D]# lines is asynchronous to CLK.
LOCK#	s/t/s	Lock indicates an atomic operation that may require multiple transactions to complete.
PAR	t/s	Indicates even parity across AD[31::00] and C/BE[3::0]#. Parity generation is required by all PCI agents.
PERR#	s/t/s	Parity Error reports a data parity error on all commands except Special Cycle.
PRSNT1# PRSNT2#	in	Present Lines indicate the presence of a PCI add-in board in the connector, and the power requirements of the add-in board.
REQ#	out	Request indicates to the arbiter that this agent desires use of the bus. This is a point to point signal. Every master has its own REQ#.
RST#	in	Reset forces the PCI sequencer of each device to a known state.
SBO#	in/out	Snoop Backoff indicates whether the current memory access may proceed or is required to be retried.
SDONE	in/out	Snoop Done indicates the status of the snoop for the current cache access.
SERR#	o/d	System Error reports address parity errors, data parity errors on Special Cycle commands, or any other system error where the result will be catastrophic.
STOP#	s/t/s	Stop indicates the current target is requesting the Master to stop the current transaction.
TCK	in	Test Clock clocks state information and data into and out of the device during boundary scan. All of the test related pins conform to the Test Access Port (TAP) and Boundary Scan Architecture defined by IEEE Standard 1149.1
TDI	in	Test Input shifts data and instructions into the TAP in a serial manner.
TDO	out	Test Output shifts data out of the device. If an add-in card does not implement a TAP, TDI and TDO should be tied together.
TMS	in	Test Mode Select controls the state of the TAP controller.
TRDY#	s/t/s	Target Ready indicates the target agent's (selected device's) ability to complete the current data phase of the transaction. During a read TRDY# indicates that valid data is present. During a write it indicates the target is prepared to accept data.
TRST#	in	Test Reset is used to force the TAP controller into a test logic reset state.


Performance Benchmarks

Introduction

Single and Dual CPU Considerations

Cache Considerations

iCOMP INDEX Ratings

NETbench Suite Version 3.0 results

ServerBench1

ServerBench 2.0 (133MHz)


ALTServer Help - Performance Benchmarks - Introduction
Introduction

When it is not practical to measure the performance of the computer using the actual application the computer user will use on the computer, the results of a variety of realistic benchmarks can give valuable insight into expected real performance.  This benchmark report documents the performance of the Intel ALTServer platform with each of the available processors.  This report includes performance measurements in the MS-DOS, Windows, SCO UNIX V.4, and UnixWare 1.1 operating environments.  The results are intended to give a standard measure that can be used to predict how well specific applications and system environments will execute in the Altair architecture.

The computer is at least a function of the Processor being used, the memory design, the disk performance, and the video performance. To test the system, a processor benchmark (e.g., PC Bench, SPECint, SPECfp) will not suffice.  You must use a variety of Server benchmarks.  The performance of any system often is a combination of the computer's architecture and many other system software and hardware constrants.  Certain operating systems, compilers, code libraries, memory/cache designs and I/O subsystem characteristics can dominate individual benchmark results and make comparisons difficult.

Benchmark comparisons continue to be an integral part of a buyer's decision, and most benchmarks actually will provide an approximate measure of a given system's performance in a real world environment. Customers must understand how benchmarks are devised, be able to select appropriate data, and use the benchmark in combination with pricing information.


Single and Dual CPU Considerations

In order to effectively measure the ALTServer platform's performance, care was taken to configure the system in all of its CPU variations.  Currently the system can accommodate three different CPUs, 75, 90 and 100 MHz Pentium Processors.  Each of these processors will give different performance measurements.  Depending on the environment established for the various speeds, the expected data will vary accordingly.  In order to give enough data that's useful in evaluating the system, each of these processors will be measured and similar or common environments used.


Cache Considerations

Cache memory systems  are usually designed at two levels First Level Caches and Second Level Caches. First Level Caches are the single layer high speed memory, are usually small (4KB to 64KB) and tend to be internal to the microprocessor.  The Second Level Cache is second layer high speed memory, usually larger (64KB to 1MB), and usually designed external to the microprocessor.  The second  level cache handles the more random memory request that the first level cache misses.  To make this handling of the missed request by the first level simplistic, the second level cache handles all the data of the first level and more.  The ALTServer can accommodate either asynchronous or synchronous second level cache sub-systems and in capacities of either 256 or 512KB.  This benchmark report will concentrate on only the 256KB asynchronous configuration.

Qualified L2 Cache


iCOMP INDEX Ratings

There are many processors  and comparing processor performance can become a tedious task.  Each processor comes in a variety of speeds.  Processors are used in several different operating systems and there are several benchmarks that one could use to help determine processor performance.  The job of testing all processor combinations is enormous.  The iCOMP index (Intel Comparative Microprocessor Performance) is a simple indicator allowing end-users to compare relative, best-case performance of Intel microprocessors--not a benchmark.  The iCOMP index is based on the results of realistic benchmarks.  Ninety-three percent of the iCOMP index is determined by the processor's performance on SPECint92 and PCBENCH*.  SPECint92 and PCBENCHtest suites of today, accurately represent the technical workstation and desktop computing markets. Currently an iCOMP rating for two (or more) processors operating either symmetrically or asymmetrically doesn't exist.  The iCOMP rating is based on four separate areas of both 16- and 32-bit processor performance; integer, floating-point, graphics, and video.  Each category is evaluated based on an estimate of the percentage of time it uses to perform the  processing task.  It is important to note that the iCOMP index relates only to processor performance, and not to overall system performance, so a 100 MHz Pentium processor has a rating of 815, regardless of the system it is in.

The iCOMP index is based on eight performance categories, each represented by a benchmark test suite:

CPU Category	Test Suite Used	iCOMP Weighting
16-bit Integer	PC Labs v7.01;  Processor	52%
32-bit Integer	SPECint92	15%
16-bit Graphics	PC Labs WinBench v3.11	10%
16-bit Video	PC Labs v7.01;  Video	5%
32-bit Floating Point	SPECfp92	5%
32-bit Graphics	SPECint92	5%
32-bit Video	SPECint92	5%
16-bit Floating Point	Power Meter v1.7;  Whetstone PC Labs v7.01; Math Coprocessor	2% 1%


NETbench Suite Version 3.0 results

Altair based servers must be able to transmit and receive data packets of all sizes.  Servers are often connected to multiple segments, bridges, and routers. The NETbench test was developed by Zif Davis Labs and consists of test suites which focus on CPU throughput and Network Interface Card (NIC) throughput. The CPU utilization percentage (critical to servers) is acquired by a Novell Loadable Module called STAT.NLM, which monitors the CPU activity at the server and provides polling data, bytes received/transmitted, number of packets routed, and number of active connections. The lower the CPU utilization the better, since this means the network is free to run other applications. However, CPU utilization is not nearly as critical in client PC systems since these machines have only one Ethernet adapter. The I/O throughput rate is the main concern in the client PCs. The Ethernet adapter will make heavy use of the Altair system memory resource, the hard drive resource, the PCI bus and the EISA bus. NETbench is able to detect when the CPU must intervene in these memory and I/O transfers, while also measuring the I/O throughput from the server to the client across the Ethernet bus.

Test configuration: one EtherExpress PCI 100 LAN card, 64 MB of system memory, and one Seagate (2.2 GB) 12ms hard drive in the ALTServer executing Novell Netware 3.12, six i486-based clients with EtherExpress16 LAN cards installed.   Results are not audited by ZD Labs and are intended for reference only.

Test configuration: one EtherExpress 100 EISA  LAN card, 64 MB of system memory, and one Seagate (2.2 GB) 12ms hard drive in the ALTServer executing Novell Netware 3.12, seven i486-based clients with EtherExpress16 LAN cards installed.   Results are not audited by ZD Labs and are intended for reference only.

NetBench 3.0 Results

Configuration:

Network Speed:	10mb/sec

ALTServer:	EtherExpress Pro PCI 100

O.S.	Novell 4.1

Processor Configuration	Total Throughput for 28 Clients (bytes/sec)	Percentage Performance Increase
Single Processor 75MHz	834,710.523	-----
Single Processor 90MHz	870,681.150	4.3%
Single Processor 100MHz	875,713.655	.58%
Single Processor 120MHz	881,246.533	.63%
Single Processor 133MHz	846,788.407	-3.9%
NetBench 3.0 Results

Configuration:

Network Speed:	100Mb/sec

ALTServer:	3COM 3C595

O.S.	Novell 4.1

Processor Speed	Total Throughput for 28 Clients (bytes/sec)
75Mhz	1,522,038.143
90Mhz	1,623,336.952
100Mhz	1,635,364.293
120Mhz	1,627,112.475
133Mhz	1,590,747.767
NetBench 3.0 Results (133MHz)

Configuration:

Network Speed:	10Mb/sec

ALTServer:	3COM 3C595

O.S.	Windows NT Server 3.51 / Multiprocessor function disabled

Processor Speed	Total Throughput for 28 Clients (bytes/sec)	Percentage Performance Increase
Single Processor 90MHz	764,316.920	-----
Single Processor 100MHz	787,477.045	3.03%
Single Processor 120Mhz	775,868.221	-1.47%
Single Processor 133MHz	791,695.675	2.04%


ServerBench1

The ServerBench benchmark was designed to run in an client/server environment and divide the server into three different subsystems: processor/memory, disk, and network.  ServerBench does not measure the performance of how fast data move through the network wire, it is only concerned with how long it takes a transaction to complete. This benchmark is designed to test a server in the way that you would use the server. The numbers you see in the ServerBench results provide a way for you to measure both the overall performance of a server and the performance of one of the specific server subsystems listed above. The results are intended to give the user three specific data points:

1.	Provide a relative measure to let you compare different servers.

2.	Indicate the speed of the basic server subsystems in a client/server environment.

3.	Allow you to analyse the effect of changing a single variable in a test.

The unit of measurement used is called transactions per second (TPS). Each client generates one TPS number for each test in a given mixture of test. A transaction is defined as a  request that a client makes of the server and the response the server returns. A single transaction can consist of more than one subsystem test.  To thoroughly test a network subsystem, each iteration of a sub-system test includes one client to server subsystem test that moves 500 bytes of data and eight server to client network subsystem tests, each of which moves 12.5 KB of data for a total of 100 KB.

As stated by its title, the network test suites target the network subsystem. There are actually two types of network test, one uses 1 to 28 clients while the other one uses 32 to 60 clients. Each iteration of each mix in the network test suites executes 32 server to client tests and 32 client to server tests. Each test moves 12.5 KB of data in increments of 512 bytes, 1 KB, 2 KB, or 4 KB.

The overall test suites roughly balance the amount of processor and disk subsystem load they place on a server, along with a modest amount of network work. The disk, network, and processor test suites isolate and gauge the peak performance of each of these subsystems. Below are some results of the ALTServer Platform obtained when run in various configurations.

Processor	Cache	Peak Disk Performance(TPS)	Peak Network Performance(TPS)	Peak Overall Performance(TPS)
75 MHz	256K Async.	6.630	117.824	7.269
90 MHz	256K Async.	6.867	122.438	8.258
100 MHz	256K Async.	6.598	126.207	8.350
120 MHz	256K Async.	6.749	123.055	8.170
Test configuration: one EtherExpress 100 EISA  LAN card, 64 MB of system memory, and one DEC DSP3107L (2.2 GB) 12ms hard drive in the ALTServer executing Novell Netware 3.12, seven i486-based clients with EtherExpress16 LAN cards installed.   Results are not audited by ZD Labs and are intended for reference only.

Processor	Cache	Peak Disk Performance(TPS)	Peak Network Performance(TPS)	Peak Overall Performance(TPS)
Dual 100 MHz	256K Async.	6.413	124.393	8.392
Dual 90 MHz	256K Async.	6.400	121.851	8.275
Test configuration: one EtherExpress 100 EISA  LAN card, 64 MB of system memory, and one DEC DSP3107L (2.2 GB) 12ms hard drive in the ALTServer executing Novell Netware 3.12, seven i486-based clients with EtherExpress16 LAN cards installed.   Results are not audited by ZD Labs and are intended for reference only.


ServerBench 2.0 (133MHz)

Description

The ServerBench program was designed to measure the performance of a server running applications in a client/server environment. ServerBench measures the server's performance by initiating a work request from the clients to an application on the server. The requests sent by the clients are called transactions. A record of the amount of time it takes for the server to respond, and the total number of transactions that the server replies to is recorded on each client. In this way ServerBench can get an accurate measurement of the number of  transactions per second (TPS) the server is capable of. The clients send three types of transactions to stress the following server subsystems:  processor/memory, disk, and network. An overall score is then obtained for the server and clients. The overall score is intended to provide three things:

1.)  Provide a relative measure to compare with different servers.

2.)  Indicate the overall speed of the server in a client/server environment.

3.)  Allow you to analyze the effect of changing the processor speeds.

ServerBench includes several different tests that can be run to examine the capabilities of the server. One network test uses 1 to 28 clients and another uses 32 to 60 clients. While only six clients were used to perform the benchmarking, ServerBench is capable of simulating the remaining clients. The exact configuration of the server and clients as well as the test run to benchmark the ALTServer platform will be explained in the next two sections.

Configuration

To test the ALTServer system with ServerBench, a 10Mb network was used.  A 10 base-T twisted pair 8 client hub was used. The following table shows the configuration of the server, controller, and the six clients.

	ALTServer	Controller	Clients (6)
OS	Windows Server NT 3.5	DOS/Windows 3.11	DOS/Windows 3.11
Processor	Pentium 75,90,100,120,133Mhz	Pentium 66Mhz	486DX-33
Memory	64 MB	8 MB	8 MB
Cache	256k Async	256k Async	None
Hard Drive	DEC DSP3107L	Maxtor 7345AT	Maxtor 7120AT
Network Card	PCI  10/100Mb	EISA 10/100Mb	EtherExpress 16 10Mb
The configuration shown above did not change with the exception of the processor speed on the ALTServer platform.

Results

Since the ALTServer platform was designed to be used as an entry level server, the 1 to 28 client test was used in ServerBench. Also since Windows NT 3.5 is capable of using multiple processors, several different dual processor configurations were tested. The table below shows the transactions per second that were recorded with ServerBench simulating all 28 clients. Different speed processors were tested in both the single and dual processor mode.

Processor Configuration	Overall Score for 28 Clients (TPS)	Percentage Performance Increase
Single Processor 75Mhz	22.239	------
Single Processor 90Mhz	26.588	19.6%
Single Processor 100Mhz	29.440	10.7%
Single Processor 120Mhz	30.850	4.8%
Single Processor 133Mhz	34.386	11.5%
Dual Processor 90Mhz	39.361	------
Dual Processor 100Mhz	45.123	14.6%
Dual Processor 120Mhz	43.468	-3.67%
Dual Processor 133Mhz	46.681	7.4%
Conclusion

From the table above it can be seen that the best performance increase occurs when going from the 75Mhz processor to the 90Mhz processor. However, since most network servers would start at 90Mhz the next best performance increase would occur between the 120Mhz and 133Mhz processors. Therefor for small networks, under 30 clients, the step-up from a 90Mhz to a 100Mhz processor would give the best performance results. For larger networks, over 30 clients, the step-up to a 133Mhz processor would give the best performance increase. There is no significant increase in the performance of the server when increasing the processor from 100Mhz to 120Mhz. For Windows NT servers running dual processors the performance increase from the 90Mhz to the 100Mhz processor would benefit both small a large networks.

ServerBench Summary

The ALTServer platform was tested using ServerBench version 2.0. The ServerBench program was designed to measure the performance of a server running applications in a client/server environment. ServerBench measures the server's performance by initiating a work request from the clients to an application on the server. A record of the amount of time it takes for the server to respond, and the total number of transactions that the server replies to is recorded on each client. In this way ServerBench can get an accurate measurement of the number of  transactions per second (TPS) the server is capable of.

To test the ALTServer system with ServerBench, a 10Mb network was used.  The network consisted of six clients connected through a 10Mb twisted pair hub. Microsoft Windows NT Server 3.5 was the operating system on the ALTServer platform, and the six clients and the controller used DOS/Windows 3.11 operating system. A 10/100 Mb PCI Ethernet LAN card was used in the ALTServer, and the controller used a EISA 10/100Mb LAN card. The clients used 10Mb EtherExpress 16 cards. For a more detailed list of the configuration used please see the Configuration section above.

Since the ALTServer platform was designed to be used as an entry level server, the 1 to 28 client test was used in ServerBench. The graph below shows the transactions per second that were recorded with ServerBench simulating all 28 clients. Different speed processors were tested in both the single and dual processor mode under Windows NT.

From the graph above it can be seen that the best performance increase occurs when going from the 75Mhz processor to the 90Mhz processor. However, since most network servers would start at 90Mhz the next best performance increase would occur between the 120Mhz and 133Mhz processors. Therefor for small networks, under 30 clients, the step-up from a 90Mhz to a 100Mhz processor would give the best performance results. For larger networks, over 30 clients, the step-up to a 133Mhz processor would give the best performance increase. There is no significant increase in the performance of the server when increasing the processor from 100Mhz to 120Mhz. For Windows NT servers running dual processors the performance increase from the 90Mhz to the 100Mhz processor would benefit both small a large networks.


System BIOS

Introductory description

FLASH Implementation

Error Messages / Beep Codes

Power-On Self Tests (POST)

POST Codes and Countdown Codes

CODES DISPLAYED DURING RECOVERY BOOT PROCESS

CODES DISPLAYED DURING NORMAL BOOT PROCESS

Update recovery code

Graphics and SCSI BIOS

The PCI auto-configuration Utility

ISA Plug & Play Capability

System Configuration Utility (SCU)

SCU "Overlay Lite" Configuration Tips

SCU-Configurable Features

Using the BIOS Setup Utility

BIOS Upgrades & Recovery

Using the SCSISelect* Utility

SCSISelect* Configuration Options

SCSISelect Screens

User Flash Area Scans

Secure Mode Operating Model


Introductory description

The ALTServer baseboard uses an American Megatrends Incorporated (AMI) ROM BIOS, which is stored in an Intel Flash memory device and can be easily upgraded using a floppy disk-based program. The baseboard has an Intel 28F004BX-T 4 Mb FLASH component organized as 512 KB (512kbit x 8). This Flash memory device contains the following software elements:

•	The AMI BIOS code

•	The System Configuration Utility (SCU)*

•	Power-On Self Tests (POST)

•	Update recovery code

•	On-board Video BIOS

•	On-board SCSI BIOS

•	The PCI auto-configuration utility*

•	ISA Plug-N-Play software*

* Asterisk/Italics indicates features currently implimented on SCU disk

The BIOS displays a sign-on message during POST identifying the type of BIOS and a five-digit revision code. This ASCII string has the following format:

ALTServer = x.yy.aa.BI0

BIOSVersionx.yy.aa.pphvv

-	indicates an ASCII space character.

X	-	The major revision as assigned by AMI (1). If this is an Alpha or Beta BIOS, this number will be '0'.

YY	-	The minor revision as assigned by Intel. The minor revision will be ZERO for all production and Alpha BIOS versions, and will be the level of Beta for all Beta BIOS versions.

AA	-	The release level of the BIOS.

PP	-	The product identifier ('AD')

H	-	The hardware revision level. This starts at 0 for the first fab and is revised each time a hardware change is made that requires a BIOS change.

Information on BIOS functions can be found in the IBM PS/2 and Personal Computer BIOS Technical Reference published by IBM, and the ISA and EISA Hi-Flex AMIBIOS Technical Reference published by AMI. Both manuals are available at most technical bookstores.


FLASH Implementation

Figure 6. Flash memory implementation


Error Messages / Beep Codes

The BIOS indicates failures with beep codes prior to the initialization of the video adapter. The beep code is a series of individual beeps, each equal in length. The following table describes the error conditions associated with each beep code:

Beep Count	Error Condition	Possible Reason
1	Refresh failure	Refresh memory circuitry error
2	Parity can't be reset	Parity error in the first 64 KB.
3	First 64KBmemory failure	Memory error in the first 64 KB
4	Timer not operational	Memory error in the first 64 KB or Timer 1 on baseboard is not functioning
5	Processor failure	The CPU generated an error
6	8042 gate a20 is off (v_mode)	The BIOS cannot switch to protected mode
7	Exception interrupt error	The CPU generated an exception interrupt
8	Display memory r/w error	The system video adapter is either missing or it's memory is faulty
9	ROM checksum error	The ROM checksum does not match the value encoded in BIOS
10	Shutdown reg. r/w error	The shutdown register for CMOS RAM failed
11	Cache Error / External Cache Bad	The external cache is faulty


Power-On Self Tests (POST)

The system BIOS performs a Power On Self Test (POST) to confirm the correct operation of the baseboard hardware. Error messages are displayed on the video screen after the video subsystem has been tested and initialized. Prior to video initialization, beep codes are used to inform the user of errors. The POST error codes are logged into NVRAM and the Extended BIOS data area, according to the IBM PS/2 standard and are displayed on the LCD display. Refer to the Appendix for POST error codes and messages, POST beep codes, and their definitions


POST Codes and Countdown Codes

The BIOS indicates the current stage of the Power-On Self Test (POST) after the video adapter has been successfully initialized. A two-digit hex code is sent to I/O location 80h. This code can be shown on an LED display if a Port 80h card is installed. The current countdown code will also be displayed on the LCD panel, once it is initialized.


CODES DISPLAYED DURING RECOVERY BOOT PROCESS

The following table contains the Port 80 codes and the POST countdown codes displayed during the recovery boot process. This process is enabled by moving the Flash jumper from the position marked Boot to the opposite position, and cold-booting the system. During this process the floppy disk in drive A is booted and a BIOS image is automatically installed.

CP	YY	Reason
02h		Disable internal cache
08h		Disable DMA controller #1, #2, disable interrupt cntlr #1, #2, reset video display.
13h		Init all chipset registers (Enable LCD display here)
*15h	900	Initialise system timer
*1Bh	800	Real mode base 64k test
*20h	700	16k base ram test
*23h	650	SDetup interrupt vectors
*40h	600	Test memory in virtual mode.
*65h	500	Initialise 8237 dma cntlr
*67h	400	8259 interrupt cntlr test
*80h	300	Unmask diskette, kb and timer interrupts
*88h	200	Floppy unit initialisation
*A0h	100	Cache enable
*00h	000	Boot OS.
CP= AMIBIOS check point (Port 80) code; YY= ALTServer BIOS countdown code


CODES DISPLAYED DURING NORMAL BOOT PROCESS

CP	XX	Reason
D0h		Returned from ResetInit
D1h		PowerOnInit
D2h		Return from PowerOnInit
D3h		SoftResetEntryPoint:
D4h		Test to see if we are in Protected mode (entered from POST.BIN not
D5h		Checksum only the LOADER.BIN
D6h		Loader.bin checksum good. (Enable LCD in InitBeforeKBCInit)
*D7h	900	Issue BAT command to KBD controller.
D8h		After waitForEmptyBuffer
D9h		After Empty8042InputBufferX
DAh		After Retrieve8042OutputBufferX
DBh	820	Keyboard Init Passed
DDh		After initAfterKBCInitEnd
DFh		2nd Empty8042InputBufferX
*E0h	780	Initialize Master/Slave PICs
E1h		Before ChipsetInitEnd (before chip set initialization ends)
E2h		After ChipsetInitEnd (after chip set initialization ends)
*E3h	760	Initialize timer channel 0 for system timer.
E4h		Before beginning memory test need to clear any pending parity errors.
E6h	740	Test RAM from 0-640KB
E7h		GetMinPartitionSizeX(get minimum partition size)
E8h		RAM failure, call RemapMemoryPartitionX(memory failure)
E9h		RAM test complete, passed.
EBh	730	Set up stack at 30:100
EBh		BIOS just shadowed
ECh		Make F000h DRAM R/W Enabled
EDh		Dispatch POST
*23h	700	Setup interrupt vectors
24h		Just after call to SetPostEnvironment(after a call to setup the POST environment)
0Dh		CustomCheckManufacturingMode and CheckDefaultJumper
0Eh	690	Check validity of CMOS
0Fh		Force CMOS defaults
10h		CMOS init complete
25h		After Initialize CMOS pointers in EBDA
*F0h	600	EISA slot initialization
F1h		Enable extended NMI sources
F2h		Test extended NMI sources
28h		Set monochrome mode
29h		Set color display
2Ah		Clear parity status if any
2Bh		Call ChipsetBeforeVideoInit
2Ch	580	Video option ROM search
2Dh		Call CustomAfterVideoInit (calls custom code aftyer video has initialized)
2Eh	570	After video init
2Fh	560	After mono display setup
30h		Before check for vertical retrace
31h		Test for color display memory
32h		Check for vertical retrace
34h		Video card detected
35h	520	Initialize Console Redirection
36h		InitializeMessagingServices and ClearScreen
37h	500	CustomDisplaySignon
F3h		EISA ErrorDisplay
80h	370	KB/mouse port check
81h		Keyboard error determination.
82h		Enable Keyboard Interrupts and initialize keyboard circular buffer
83h		Check if keyboard is locked
F5h	330	Initialize mouse
39h		CustomUpdateScreenPointers,CustomDisplaySetupMessage,CustomDisplayKeyboardSignon,CustomDisplayMouseSignon
3Bh		Jumps to 'StartMemoryTesting' in next module.
43h	290	call GetMinPartitionSizeX
4Fh		call DisableEnhancedPost
52h		call ChipsetAdjustMemorySize
*61h	250	DMA register tests
62h		DMA test OK
64h		DMA controller latch test
65h		Initialize 8237 DMA controller
66h		clear DMA write request reg and mask set/reset reg
*67h	220	8259 Interrupt cntlr test
F4h		Enable extended NMI sources
8Ch	140	Chipset@Devinit and ConfigurePeripheralController
8Fh	130	Floppy Initialization
91h	120	HD initialization
92h		Set printer, rs-232 time out
96h		Before Option ROM scan
97h	080	Option ROM scan C800h-E000h
98h		After Option Rom scan
9Ah		Soft reset (1234) --> (1200)
9Dh	070	Timer data area initialization
A0h		Printer setup
A1h		RS_232 setup
A2h		After KB circular buffer set up
ABh		Before NPX test and init
*ACh	060	NPX test and init
ADh		Update coProcessor info in cmos and recalculate checksum
AEh		Set typematic rate
*AFh	050	KBD read ID command
B0h		Wait for READ ID response
A3h		Display POST errors
A6h		Before Setup
*A7h	030	Call Setup
B1h		Enable Cache for boot
B3h		Setup display mode set
B4H		Jmp preos.asm (jump to program outside)
BBh	020	Start of PreOS
00h	000	Execute BOOT


Update recovery code

A Flash Memory Update (FMUP) Utility is supplied, allowing the system BIOS and the System Configuration Utility to be updated from a diskette and without the need to open the chassis or remove any hardware.


Graphics and SCSI BIOS

The System BIOS contains the video BIOS for the Cirrus PCI graphics subsystem and also the SCSI BIOS for the on-board Adaptec PCI SCSI subsystem.


The PCI auto-configuration Utility

The PCI auto-configuration utility operates in conjunction with the System Configuration Utility to allow the insertion and removal of PCI cards without user intervention. When the system is turned on after adding a PCI add-in card, the BIOS automatically configures interrupts, DMA channels, I/O space, and other parameters. The user does not have to configure jumpers or worry about potential resource conflicts. Since PCI cards use the same interrupt resources as ISA cards, the user must specify the interrupts used by ISA add-in cards in the BIOS configuration utility. The PCI Auto-Configuration function complies with version 2.0g of the PCI BIOS specification.


ISA Plug & Play Capability

The BIOS will incorporate ISA Plug and Play capabilities as delivered by Intel Architecture Labs Plug and Play Release 1.2. This will allow auto-configuration of Plug and Play ISA cards, and of older non Plug and Play ISA cards.


System Configuration Utility (SCU)

The System Configuration Utility (SCU) will be supplied on one 3.5" high density floppy.  The SCU combines the functionality previously contained in the EISA Configuration Utility (ECU) as well as PCI and Plug-n-Play information.

The SCU conforms to the version 3.12 of the EISA standard and version 1.1 of the ISA Plug and Play Specification. It can be used with any compliant CFG or OVL files that are supplied by an add-in peripheral device manufacturer. The ALTServer platform contains the PCI overlay (OVL) and PCI configuration (CFG) files for the embedded controllers on the system baseboard.

The SCU modifies the ISA CMOS and EISA NVRAM, under direction of the user. The actual hardware configuration is accomplished by the BIOS Power-On-Self-Test routines and the ISA Plug and Play Auto Configuration Manager.

The appendix lists the features that may be configured with the SCU and the defaults as shipped.

The CU modifies the ISA CMOS RAM and EISA non-volatile RAM, under direction of the user. The actual hardware configuration is accomplished by the BIOS Power-On-Self-Test routines and the ISA Plug-N-Play Auto Configuration Manager.

The CU always updates a checksum for both areas, so that any potential data corruption will be detectable by the BIOS, before the actual hardware configuration takes place. If the data has been corrupted, the BIOS will request that the user configure the system, before the system is booted.


SCU "Overlay Lite" Configuration Tips

The AMI SCU operates in Real Mode and is limited to using the 640KB memory space associated with DOS.  In some configurations, users of the PCI/EISA server systems may experience "Out of Memory" errors when attempting to configure certain combinations of adapter cards.

In the unlikely event of this error being seen, "Overlay Lite" has been developed.  By implementing a paging scheme in the AMI SCU 3.08 overlay 00.31, the available amount of memory for add-in card OVL/CFG files dramatically doubled.  However, even with 115K-130KB available for the add-in card's OVL/CFG files it is mathematically possible to produce system configurations to exceed this limit. The "Overlay Lite" program frees approximately 130KB of additional memory for use by ISA/EISA/PCI adapter card OVL/CFG files.  This additional memory is useable by the elimination of the very large server baseboard overlay file.  The consequences of eliminating the baseboard overlay is the effective "locking" of the baseboard's resources.  Locking the baseboard's resources does not produce any immediate problems, but it does prevent the user from changing any of the choices provided by the standard AMISCU overlay.  The use of "Overlay Lite" can reduce memory requirements for system configuration to an extent that virtually no EISA/ISA/PCI configuration will be affected by the 640KB memory limitation.

The AMI System Configuration Utility  3.11 Overlay 00.39 should be used on the following platforms:

ALTServer -- int31A0

AMI System Configuration Utility Overlay 00.39 should only be used with the following BIOS versions (or more recent BIOS versions):

    Platform	Compatible BIOS*

ALTServer	1.00.04 BK0, 1.00.07 BK0

*AMISCU 3.07 and OVL 00.26 should be used for earlier BIOS versions.

This document provides instructions, functional considerations, and some special features for the use with "Overlay Lite."  The special features related to the AMISCU 3.11 Overlay 00.39 are implemented to assist users to monitor available memory and determine when "Overlay Lite" should be used.

Main Menu for SCU 3.11, Overlay 00.39

Perform the following steps to obtain a working version of Overlay Lite:

1)	Format and 'sys' a new diskette with DOS 6.22.

2)	Copy the contents of the provided System Configuration Diskette onto the newly created bootable diskette.

3)	Place the associated EISACFG/OVL files onto the bootable diskette.

4)	Boot the server system using the diskette.

5)	When the system boots, the user will be presented a main menu with a number of choices:

1. Execute AMISCU

2. Execute AMISCU and load adapter cards manually

3. Execute AMISCU using the Overlay Lite

4. Execute SCSISelect (TM) Utility  (int31A0/ALTServer baseboard only)

The user has ten seconds to make a selection or menu item (1) will be automatically selected.

In order to help our customers determine when memory problems might occur the AMISCU 3.11 includes two new features:

•	Pressing <CTRL-M> at the main menu will display the largest free memory block (this value is effectively the amount of free memory in the system.)

•	Pressing <CTRL-F> at the main menu will toggle-on (or toggle-off) a dynamic memory meter that appears in the upper left-hand corner of the screen.  This "gas gauge" meter will be erased at every screen update by the AMISCU and is sometimes covered up.  Asking for "Help (F1)" will usually provide a menu that displays this meter without being "covered up" right away.

The <CTRL-M>  and <CTRL-F> features are only available at the SCU menu screen.

Execute AMISCU Selection

The majority of system configurations should work without incident.  By selecting this option, the AMISCU will automatically located all EISA/PCI devices and configure them into the system per the Plug-N-Play and PCI specifications. If this is the first time the system has been configured after shipment or after a "clear NVRAM" the user should choose either "Execute AMISCU" or "Execute AMISCU and load adapter cards manually".  A vast majority of OEMs are expected not to ever have a problem during configuration of ISA/EISA/PCI add-in cards when executing either of these selections.

Execute AMISCU and Load Adapter Cards Manually Selection

The user should configure the system as desired, save the configuration, exit the AMISCU, and reboot the system. If no errors were encountered during the configuration process the user may boot to the desired operating system and continue.  However, if "Out of Memory" errors occurred, the user should reboot using the System Configuration Utility and choose to load Adapter cards manually.  By selecting this option, the user is required to locate some (or all) interrupt, I/O memory space, and RAM memory space specific to each EISA/PCI add-in card.  This selection is useful when used in conjunction with the dynamic memory meter to help in determining "problem" card configurations.

Execute AMISCU Using the Overlay Lite Selection

If configuring the system through the automatic AMISCU selection is unsuccessful (i.e. "Out of Memory" errors), the user may with to execute "Overlay Lite". By selecting this option, all adapter cards are re-configured automatically.  The previous settings of the adapter cards in the server system will not be restored if executed earlier with the "Execute AMISCU" selection.   This option especially locks the system baseboard configuration getting additional memory by the eliminating the very large server baseboard overlay file.  Locking the baseboard's resources does not produce any immediate problems, but it does prevent the user from changing any of the choices provided by the standard AMISCU overlay.  Any  future system configuration changes/additions/deletions must be performed using this selection.  The total time to configure the system will be approximately 5 minutes in some cases.

Execute SCSISelect(TM) Utility Selection

This option is only for use on the ALTServer system platform.  This option was installed to select the onboard AIC-7870 fast/wide SCSI controller.  The SCSISelect utility enables and configures the AIC-7870 SCSI controller on the ALTServer platform.  By selecting this option on either Xtended Xpress system platforms, this action will either lock up the system or cause unpredictable results.  The SCSISelect configuration menu can be enabled on either Xtended Xpress system platforms by pressing <CTRL-A> during system initialization.


SCU-Configurable Features

ALTServer System Board

Configuration Feature	Selection Options	Notes
	Systems Group
System ID String	None	Configured by User or System Integrator, using the ROM-based or disk-based configuration utility.
Configuration and Overlay Version	N/A	Display only, the version of the SCU
Display BIOS version string	N/A	Display only
Display processor Type(s) and Max. Speed and Failed Status	N/A	Display only for CPU 1 and CPU 2
Power-On Speed	Fast / Slow	BIOS programs the SLOWH timer before boot.
Cache control	Disabled / Enabled - Write Back	BIOS will enable cache before booting OS.
	Memory Subsystem
Base Memory	512 / 640 KB
Total Memory		Display only.
Shadowing ISA ROM at C000
Shadowing at C000	Enable / Disable
Shadowing at C400	Enable / Disable
Shadowing at C800	Enable / Disable
Shadowing at CC00	Enable / Disable
Shadowing ISA ROM at D000
Shadowing at D000	Enable / Disable
Shadowing at D400	Enable / Disable
Shadowing at D800	Enable / Disable
Shadowing at DC00	Enable / Disable
Shadowing ISA ROM at E000
Shadowing at E000	Enable / Disable
Shadowing at E400	Enable / Disable
	Floppy Subsystem
Floppy Autodetect	Enable / Disable
Floppy Drive Type	*Auto / 360 / 1.2 / 1.44 / 2.88 / Disable
	IDE Subsystem
Onboard IDE Controller	Auto / Disable
IDE Auto Configuration Drive C
Menu	Auto / Customize / Not Detected
IDE Drive C Options
Multi-sector transfer selection	Auto / 8 sectors / 16 sectors / Disable
Translation Mode	CHS / LBA  / ExtCHS / Auto
Fast Programmed I/O Modes	Auto / Disable
ISA IDE DMA Transfers	Auto / Disable
IDE Auto Configuration Drive D
Menu	Auto / Customize / Not Detected
IDE Drive D Options
Multi-sector transfer selection	Auto / 8 sectors / 16 sectors / Disable
Translation Mode	CHS / LBA  / ExtCHS / Auto
Fast Programmed I/O Modes	Auto / Disable
ISA IDE DMA Transfers	Auto / Disable
IDE Auto Configuration Drive E
Menu	Auto / Customize / Not Detected
IDE Drive E Options
Multi-sector transfer selection	Auto / 8 sectors / 16 sectors / Disable
Translation Mode	CHS / LBA  / ExtCHS / Auto
Fast Programmed I/O Modes	Auto / Disable
ISA IDE DMA Transfers	Auto / Disable
IDE Auto Configuration Drive F
Menu	Auto / Customize / Not Detected
IDE Drive F Options
Multi-sector transfer selection	Auto / 8 sectors / 16 sectors / Disable
Translation Mode	CHS / LBA  / ExtCHS / Auto
Fast Programmed I/O Modes	Auto / Disable
ISA IDE DMA Transfers	Auto / Disable
	Language Support Group
		Reserved for future use
	KB/Mouse Subsystem
NumLock State at Boot	On / Off
Typematic Speed	Auto / Slow / Medium / Fast
Mouse	Auto detected	Using Phoenix Keyboard Controller
	Serial Subsystem
Serial Port 1 Configuration Address - Interrupt	Auto / 3F8h - IRQ4 / 2F8 h- IRQ 3 /  3E8h - IRQ4 / Disable	Serial-A = COM1(3F8), Serial-B = COM2 (2F8)
Serial Port 2 Configuration Address - Interrupt	Auto / 2F8h - IRQ3 / 2E8h - IRQ 3 /  3E8h - IRQ4 / Disable	Serial-A = COM1(3F8), Serial-B = COM2 (2F8)
Select Serial Port Redirection	Disable/ port 1/ port 2	2 ports
Redirection Port Baud Rate	19.2Kb/ 9600b/ 2400b
Redirection Port Terminal Type	Disable / VT100 -ANSI / IBM-PC
	Parallel Subsystem
Parallel Port Address and Interrupt	Auto / 378h - IRQ7  / 278h - IRQ5   / 3BCh - IRQ7 / Disable	1 port
Parallel Port Mode	ISA-compatible, PS/2, EPP/ECP
	Security Subsystem
Administrative Password	Set/Not Set
User Password	Set/Not Set
Secure Mode Hot-Key	Enable / Disable	Promted for key to combine with Ctrl-Alt-key.
Secure Boot Mode	Enable / Disable	Boot Without Keyboard, No error message will be displayed.
Video Blanking	Enable / Disable
Set Lockout Timer	Timeout, 1-127 (10 min), Disabled	Keyboard inactivity
Floppy Writes	Enable / Disable
	Boot Subsystems Group
Floppy Boot	A: then C:, C: then A:, C: only, A: only
	LCD Display
LCD	Enable / Disable
LCD Display String After Boot	(user defined string or default)	Default is "N x PID Speed System Ready " where N = number of processors, PID is processor ID string, and Speed is the processor in MHz.
	Management Subsystem
Speaker	Enable / Disable
Event Logging	Enable / Disable	Controls onboard event logging.
User Flash	Enable / Disable
ALTServer On-Board PCI SCSI Device

Configuration Feature	Selection Options	Notes
Enabled	Auto / Manual	Manual - Press <F6>
IRQ	3,4,5,7,9,10,11,15
Memory	4K	Display Only
Address	10F000h-FFFFF000h	Display Only
Memory	10K	Display Only
Address	108000h-FFFF8000h	Display Only
Port	1000h-10FFh to FF00h-FFFFh
ALTServer On-Board PCI VGA Device

Configuration Feature	Selection Options	Notes
Enabled	Auto / Manual	Manual - Press <F6>
IRQ	3,4,5,7,9,10,11, 12, 15
Memory	16384K	Display Only
Address	1000000h-FF000000h	Display Only
Memory	32K	Display Only
Address	100000h-FFFF0000h	Display Only
Memory	64K	Display Only
Address	100000h-FFFF0000h	Display Only
Memory	64K	Display Only
Address	100000h-FFFF0000h	Display Only
Port	1000h-1001h to FF00h-FF01h
Port	1002h-1002h to FF02h-FF02h
Port	100Bh-10015h to FF0Bh-FF15h
Port	1016h-1016h to FF16h-FF16h
Port	1018h-1019h to FF18h-FF19h
Port	101Ah-101Bh to FF1Ah-FF1Bh
Port	101Ch-101Ch to FF1Ch-FF1Ch
ALTServer On-Board PCI Undefined Device

Configuration Feature	Selection Options	Notes
Enabled	Auto / Manual	Manual - Press <F6>
Memory	1K	Display Only
Address	10EC00h-FFFFEC00h	Display Only


Using the BIOS Setup Utility

The BIOS Setup Utility has some unique options and some that are also present in the SCU.  The SCU setting will overwrite the BIOS Setup setting when you rerun the SCU.

CAUTION:  The system can fail following improper BIOS setup.  Always record current settings before making setup changes.

Operation	Action
Use Setup To	Configure the system when there is no operable diskette drive. Enable a diskette drive before running the SCU. Change a parameter temporarily. Correct a configuration error so the system will boot.  Setup recognizes PCI and ISA Plug-and-Play boards.
To Enter Setup	Press <F1> during the memory test.  The Main screen appears when you start Setup.  The screen names appear on the menu bar.
These are the screens available when you enter the BIOS Setup Utility.

Screen	Description
Main Screen	Sets basic parameters such as date, time and displays installed peripherals.
Advanced Screen	Sets processor type and speed, peripheral options, base memory, plug and play.
Security Screen	Sets/changes user and administrative password.
Exit Screen	Specifies exit options.
These keys operate the Setup program: .

Key	Action
<F1>	Displays online help for selected parameter.
<Arrows>	Up and down arrows move from one parameter to another within a screen.  Left and right arrows move from one screen to another.
<Enter>	Displays options for a configurable parameter.  Selects an option.
<Esc>	Moves back to previous screen or parameter.
<F5>	Restores factory defaults.
<F6>	Resets all Setup options to their previous values.
<F10>	Saves changes and exits Setup.
BIOS Setup Configuration Options

MAIN MENU PARAMETERS	Usage	Tips/Defaults
Date/Time	Enter current date (year, date, month) and time (hour, minutes, seconds on 24 hour clock).	Use on new system for correct file timestamping and after installing a new battery.
Floppy Options	Press <Enter> fordisplay of devices
Floppy Drive A Type	Select size of floppy drive, if installed.	Default = 1.44 MB, 3.5".  See hardware documentation.  Use disabled if drive not installed.
Floppy Drive B Type	Select size of floppy drive, if installed.	Default = Disabled.  See hardware documentation.  Use disabled if drive not installed.
Hard Disk C, D, E, F	Select configuration mode for IDE hard drive.	Auto-Config (default):  BIOS automatically senses IDE hard drive in the system and configures it appropriately. User Type enables explicit configuration of IDE hard drive if not supported by Auto_Config.
Hard Disk Type	Select if BIOS senses and configures IDE drives	Default = Auto Configured
Number of Cylinders	Set if not Auto Configured.	Default = 0
Number of Heads	Set if not Auto Configured.	Default = 0
Number of Sectors	Set if not Auto Configured.	Default = 0
Maximum Capacity	Set if not Auto Configured.	Default = 0
Initialization Timeout	Select how long system retries to initialize IDE drive.	Default = 10 seconds
IDE Translation Mode	Select translation mode.  Std. CHS = 1024 cylinders.  Ex. CHS = >1024 cylinders.	Default = Standard CHS. Autodetect queries disk and chooses correct method.
Multiple Sector Setting	Sets IDE programmed I/O cycles, so multiple sectors are transferred in a single interrupt.	Default = Auto Detected See drive documentation for optimum performance for drive.
Fast Programmed I/O     modes	Selects if BIOS queries and uses fastest I/O Protocol.	Default = Auto Detected
Language	Display only	English
Boot Options	Press <Enter> for Menu
Boot Sequence	Specify which drive the system checks first for boot sector. A, C C, A C only	Default = A, C Tries boot from diskette 1st. Tries boot from hard disk 1st. Boots from hard disk only.
System Cache	Enable/disable using secondary cache memory	Default = Enabled.  Disabled decreases performance.
Boot Speed	Select system boot speed.	Default =Turbo.  Turbo boots board full speed. Deturbo results in slower operation.
Num Lock	Set boot up state of keyboard Num Lock	Default = Off
Setup Prompt	Enable/disable message display  "Press <F1> key if you want to run Setup" during power-up sequence.	Default = Enabled
Hard Disk Pre-delay	Select delay time before first hard disk access.	Default = 3 seconds.  Some disks hang if accessed before they initialize.
Typematic Rate      Programming	Select if delay and rate options are programmable. Delay:  specify how many milliseconds system waits before repeating a key that is held down. Rate:  specify how many characters per second a character repeats when a key is held down.	Default = Default.  Delay is 250 ms and Rate is 15 characters per second.
Video Mode	Display only
Mouse	Display only
Base Memory	Display only	BIOS determines how much base memory is available and displays here.
Extended Memory	Display only	BIOS determines how much extended memory is available in RAM and displays here.  In >1Mb systems, BIOS reports 384K less RAM than detected because address space between 640Kb and 1024Kb is unavailable to DOS.
ADVANCED SCREEN PARAMETERS	Usage	Tips/Defaults
Processor Type	Display only	BIOS detects installed processor type and displays here.
Processor Speed	Display only	BIOS detects installed processor speed and displays here.
Cache Size	Display only	BIOS detects installed cache and displays here.
Peripheral Configuration	Press <Enter> for Menu
Configuration Mode	Select whether certain other parameters under Peripheral Configuration have any affect.	Default = Auto.  System peripherals are automatically configured during power up and some parameters are disabled.  If manual, these must be explicitly configured.
Standard IDE Interface		Default = Enabled
Floppy Interface		Default = Enabled
Serial Port 1 Address	Select address.	If Configuration Mode is Auto, the default address is 3F8H.
Serial Port 2 Address	Select address.	If Configuration Mode is Auto, the default address is 2F8H.
Parallel port Address	Select address.	If Configuration Mode is Auto, the default address is 378H.
Parallel Port Mode	Select compatible or extended. Extended means the parallel port operates in bidirectional PS/2-compatible mode.	Default = Compatible. Parallel port operates in AT-compatible mode. Not affected by Configuration Mode setting.
Serial Port 1 IRQ	Auto configured	Default = IRQ4
Serial Port 2 IRQ	Auto configured	Default = IRQ3
Parallel Port IRQ	Auto configured	Default = IRQ7
Advanced Chipset Configuration	Press <Enter> for menu
Base Memory Size	Select either 640 KB or 512 KB.	Default = 640 KB
Map PCI to IRQ10		Default = Disabled
Force BSP to Slot 2		Default = Disabled
Installed DRAM Speed	Select appropriate speed.	Default = 70ns
Guaranteed Access Time		Default = Enabled
Plug and Play Configuration	Press <Enter> for menu
Latency Timer (PCI Clocks)	Maximum number of PCI clocks for PCI board to access bus.	Default = 66
SECURITY SCREEN PARAMETERS	Usage	Tips
User Password is enabled/disabled	Display only.	Default = Disabled.  Enabled prevents system boot and Setup use.
Administrative Password is enabled/disabled	Display only.	Default = Disabled.  Enabled prevents system boot and Setup use.
Set User Password	Press <Enter> to enter password.	Enter a password that enables booting the system.
Set Administrative Password	Press <Enter> to enter password.	Enter a password that enables configuring the system.  Use to change, disable or delete a user password.  To delete or disable, specify the new password to be <CR>  If the password is unknown,  move the password jumper on the baseboard to the disable password position.
Keyboard Inactivity Timer	Enter number of minutes of inactivity before securing system.	Default = 20
Video Blanking		Default = Disabled
Floppy Writes		Default = Disabled
EXIT SCREEN PARAMETERS	Action
Exit Saving Changes	Writes changes to CMOS NVRAM, then exits.  Use to save new configuration.
Exit Discarding Changes	Does not write changes to CMOS or NVRAM.  Use to discard changes and exit.
Load Setup Defaults	Reloads CMOS RAM with default values from the ROM table.
Discard Changes	Does not write changes to CMOS or NVRAM.  Use to discard changes and remain in Setup.


BIOS Upgrades & Recovery

The ALTServer incorporates the AMIBIOS in a Flash memory component. Flash BIOS allows easy upgrades without the need to replace an EPROM. The upgrade utility fits on a floppy diskette and provides the capability to save, verify, and update the system BIOS. The upgrade utility can be run from a hard drive or a network drive, but no memory managers can be installed during upgrades. The latest upgrade utility and BIOS code are available to qualified customers on the Intel bulletin board. Once the utility is obtained, UNZIP the archive and copy the files to a bootable MS-DOS 5.0, or 6 diskette. Reboot the system with the upgrade diskette in the bootable floppy drive.  Click here for a complete procedure on upgrading BIOS.

In the unlikely event that a Flash upgrade is interrupted catastrophically, it is possible the BIOS may be left in an unusable state. Recovering from this condition requires the following steps (be sure a power supply and speaker have been attached to the board, and a floppy drive is connected as drive A:)

1.	Change Boot Option jumper (J7A) to the recovery mode position (2-3)

2.	Install the bootable upgrade diskette into drive A: and reboot the system

3.	Because of the small code in the non-erasable boot block area, no video is available to direct the procedure. It can be monitored using the speaker and the drive LED. When the system beeps and the drive LED is lit, the system is copying recovery code into the Flash device. When the LED goes off, recovery is complete.

4.	Turn the system off.

5.	Change the Boot Option jumper back to the default position (1-2)

6.	Leave the upgrade floppy in drive A:, turn the system on, and continue with the original upgrade.


Using the SCSISelect* Utility

Choose SCSISelect* to enter SCSISelect* from SCU disk menu option.

These are the options available when you enter the SCSISelect Utility.

Main Menu Options	Description
Configure/View Host Adapter Settings	Use to configure SCSI host adapter settings and start, format and verify the  device.
SCSI Disk Utilities	The utility scans the SCSI bus for SCSI devices, reports a description of each device.  Run the utilities before configuring the SCSI devices.
These keys operate the utility. .

Key	Action
<ESC>	Exits the utility.
<Enter>	Displays options.  Selects an option.  Displays a configuration.
<Arrows>	Moves from one option to the next.
<F5>	Switches between color and monochrome.
<F6>	Resets to host adapter defaults.


SCSISelect* Configuration Options

CONFIGURATION MENU	Default/Menu	Comment
SCSI Bus Interface Definitions
Host Adapter SCSI ID	7
SCSI Parity Checking	*Enabled
Host Adapter SCSI Termination	*Manual
Additional Options
SCSI Device Configuration	<Enter> for menu
Initiate Sync Negotiation	*yes
Maximum Sync Transfer Rate	*10.0
Enable Disconnection	*yes
Initiate Wide Negotiation	*no
Send Start Unit Command	*no	No effect if BIOS disabled.
Include in BIOS Scan	*yes	No effect if BIOS disabled.
Advanced Configuration Options	<Enter> for menu
Reset SCSI Bus IC Initialization	*Enabled
Host Adapter BIOS     (Configuration Utility     Reserves BIOS Space)	*Enabled	No effect if BIOS disabled.
Support Removable Disks     Under BIOS as Fixed Disks	*Boot Only	WARNING:  Do not remove media from a removable media drive if it is under BIOS control. No effect if BIOS disabled.
Extended BIOS Translation for     DOS Drives greater than     1 GByte	*Enabled	No effect if BIOS disabled.
BIOS Support for More Than 2     Drives (MS-DOS 5.0 and above)	*Enabled	No effect if BIOS disabled.
*  Factory default setting.

EXIT MENU	Options	Comment
Exit Utility	Yes/No	Yes configures the bus:device and reboots the server.


SCSISelect Screens

AIC7870 at Bus:Device 00:0Bh	Indicates SCSISelect found

1 onboard AIC7870 on PCI

Bus Zero at slot 11

Configure/View Host Adapter 	See "Configuration" below

SCSI Disk Utilities	See "SCSI Disk Utilities" below

Configuration Menu

Feature	Option	Comment
SCSI Bus Interface Definitions

  Host Adapter SCSI ID                   0-*7-15           7 allows recognition Wide/Narrow

                                                                             SCSI-2 Controller.

   SCSI Parity Checking                              *Enabled	           Enables parity checking on the SCSI bus if

           devices support it

Disabled

Host Adapter SCSI Termination 	See Hardware Manual.  The ALTServer has passive terminators at each SCSI connector on the baseboard.

ADDITIONAL OPTIONS

   SCSI Device Configuration                      Press <Enter>        See SCSI Device Configuration Menu.

   Advanced Configuration Options             Press <Enter>        See Advanced Configuration Options Menu.

_____________________________________________________________________________________

*Factory default Setting.

SCSI Device Configuration Menu

SCSI Device ID	0-15 Option	Comment
Initiate Sync Negotiation                          *yes	Sync allows for higher performance if the

          no	device supports it

Maximum Sync Transfer Rate                  *10                           If device does not respond to default,

                                                                   8.0                            the Transfer Rate must be tested at any of

                                                                   6.7                            these other settings; since, the SCSI may

                                                                   5.0                            require other than the default value setting.

                                                                                                    The highest setting is prefered.

Enable disconnection                                 *yes                        Printer and scanner like devices may or may

                                                                     no                          not be powered  all the time.

Initiate Wide Negotiation                           yes                          Devices 0-7 default "no", 8-15 default yes as

          *no	any Narrow device must be device 0-7.

Send Start Unit Command                          yes                          Enables controller to "Spin up" drives

           *no	sequntially.  This puts the minimum amount

of stress on the system power supply during

a cold boot.

Include in BIOS  Scan                                 *yes                         Allows the controller to detect a device at

                                                                      no                            that location when it during boot.

_____________________________________________________________________________________

*Factory default setting.

Configuration Options

Feature	Option	Comment

Reset SCSI Bus IC Initialization              *Enabled                     It allows SCSI bus to reset on a warm boot.

                                                                  Disabled

Host Adapter BIOS (Configuration          *Enabled                     Enables the controller to access other

Utility Reserve BIOS Space)                    Disabled                      drives without scanning the SCSI

                                                                                                       controller.

Support Removable Disks Under              *Boot only 	  No effect if the SCSI BIOS is diaabled

Extended BIOS translation for                   *Enabled                     Sets up DOS to identify hard drives

DOS Drives greater than 1 Gbyte                Disabled                     bigger than 1 Gbyte.

BIOS Support for more Than 2                  *Enabled                      Required to set up more than one drive.

Drives (MS-DOS(R) 5.0 and above)           Disabled                      DOS has to be at least 5.0.

___________________________________________________________________________________

*Factory default setting.

SCSI Disk Utilities Menu

                                        These utilities scan the SCSI bus for SCSI devices. After scanning the bus,

                                         they report a description of each device.  Below is a sample.

SCSI Device	Option	Comment
SCSI ID #0:   ST32550N                   Format Disk                          Select Option to format hard disk drive,

                                                                                                            Not necessary for brand new. Needed if

                                                                                                            used with another controller.

                                                           Verify Disk Media               Select this option to verify the hard

                                                                                                            disk media.

SCSI ID #1: 3140 CD-ROM	    None	    This section effects Hard Disks Only

SCSI ID #2 - #7:   No device

SCSI ID #7:     AIC-78XX 	    None                                  This is your SCSI host adapter by

                                                                                                             default.

SCSI ID #8 - #14:       No device

SCSI ID # 15:     ST32550W	    Format Disk	    See above

    Verify Disk Media


User Flash Area Scans

Description:

To accommodate a range of uses, Intel has extended the functionality of the "User Flash area ROM scan" (a feature that allows user binaries, placed in the system flash ROM to be detected and executed at the end of POST) so that scans occur at several points during POST.

This new functionality accommodates the following:

1. User binaries placed in flash are recognizable, to the planar BIOS so it can execute the code, and to applications (i.e. DOS memory managers) so that they will be protected after DOS boots.

2. The solution is backward compatible, user binaries that work correctly in User Flash today continue to do so.

3 The planar BIOS performs a scan of the flash area at a number of points during POST. It is necessary that the planar BIOS selectively executes a user binary based on which scan is being performed. It is possible that a particular user binary requires execution at more than one scan, these extensions accommodate this by providing the user binary information about which scan is being performed.

4. System state is defined for each scan point.

5. Some system resources (ram, CMOS, ...) are allocated to user binaries.

Implementation:

In this solution is we alter the code "header", all the above goals are accomplished by implementing user binaries with a header as described below:

db	55h,0AAh,10h	; 8K USER Area

MyCode	PROC	FAR	; MUST be a FAR procedure

RETF	; This byte (Byte 3, 4th in the 	; file) would be the transfer 	; address in a standard scanned 	; BIOS. We make it a Retf for 	; backward compat and as the flag to 	; distinguish this as a new type 	; BIOS

db	04h	; Bit map to define call points, a 	; one in any bit specifies that the 	; BIOS will be called at that scan 	; point in POST (scan points to be

; defined

JMP	ErrRet	; follows a list of 8 transfer 	JMP	ErrRet	; addresses, one for each bit in the 	JMP	Start 	; bitmap. In all likelihood, only 	JMP	ErrRet	; one of these will be used, earlier 	JMP	ErrRet	; entries must be present, later can 	JMP	ErrRet	; be omitted if desired.

JMP	ErrRet

At each scan point in POST, the planar BIOS "scan"s the User Flash area. When the "AA55" signature is discovered at any 2K boundary within the area, the planar BIOS examines byte 3. If byte 3 is not 0CBh (RETF), then this user binary is ignored (until the normal user scan just prior to boot), if byte 3 is determined to be 0CBh this user binary is the new type and we need to determine if this is the correct scan point to transfer control. This is accomplished by comparing the byte 4 bit map to the current mask bit (determined/defined by the scan point) if the bitmap contains the appropriate bit set, then the mask is placed in AL and execution is passed to the address computed by (ADR(Byte 5)+5*scan sequence #). In addition we provide the user binary access to 16 bytes of BIOS Data Area Ram 40:D0-40:DF and a single bit of CMOS (unchecksumed) Byte 33Bit 6. Coordination of these resources between user binaries is the responsibility of the developers.

Scan Points:

Description:

This scan occurs immediately after the point that video init occurs (or would have occurred if video is not present).

Mask: 04h

RAM/Stack/BDA: Yes

Video/Keyboard: Yes

Description:

This scan occurs immediately before the normal external ROM Scan, this is just before boot but prior to the scan for external ROM's and the scan for conventional BIOSs in user flash.

Mask: 40h

RAM/Stack/BDA: Yes

Video/Keyboard: Yes

Description:

This scan occurs immediately following the "normal" User Flash area scan.

Mask: 80h

RAM/Stack/BDA: Yes

Video/Keyboard: Yes

Description:

This is the final scan, it occurs immediately prior to the INT 19 for normal boot and allows the user to completely circumvent the normal INT 19 boot if desired.

Mask: 20h

RAM/Stack/BDA: Yes

Video/Keyboard: Yes

Description:

This scan occurs in SMM as a result of an SMI. It is the last SMM detection routine to run. If an earlier detection routine added a new log entry, the first of these will b pointed to by the segment:offset pointer stored at fixed address 0A900:0018.

Mask: 02h

RAM/Stack/BDA: A stack is assured, in addition, 128 bytes of SMRAM is available to the user binary 	    from SMRAM address 0A900:0080-0A900:00FF. Remember, this is SMRAM and 	    only accessible when in SMM.

Video/Keyboard: Video memory is "un-mapped", Keyboard is port addressable.


Secure Mode Operating Model

Mode	Entry Method/Event	Entry Criteria /Qualifer	Behavior	Exit Criteria	After Exit
Secure Mode	* KB Inactivity Timer *Prgm of KBC *Hot-Key	*User Password *KBC inactivity timer set in scu	*CRT will be blanked , if  enabled  in Setup *Floppy writes are    disabled,if selected in  setup *Power ON switch and   Reset switch in the   front Panel are disabled.  *No keyboard  input will be accepted. **No mouse input will be accepted.	User Password	*Video resoterd *Floppy- writes are    enabled *Power/Reset -switches  are enable. *Keyboard inputs will  be  accepted. ** Mouse  inputs will be accepted.
Secure boot mode	Power On/Reset	*User Password *Secure Boot Enb in scu	*Will boot if drv     drive A=Empty *will prompt for   Password ,if   Drive A= Not empty *Video will  be  blanked,if enabled   in setup.    *Floppy writes are  disabled,if selected in   setup *Power ON switch and  Reset switch in the  front Panel are disabled.  *No keyboard input will be accepted. ** Mouse inputs will not be accepted. **Mouse driver should  be allowed to    load sucessfully	User Password	*Floppy- writes are    enabled *Power/Reset -switches  are enabled at front   panel. *Keyboard  inputs will be  accepted ** Mouse inputs will be  accepted. *System will attempt  to boot from drive A
User Password boot mode (AT style)	Power On/Reset	*User Password *Secure Boot      Disabled in scu	*System will halt for   User Password before booting *Video will  be  blanked,if enabled  in setup.    *Floppy writes are allowed if in SCU/setup. *Power ON switch and  Reset switch in the  front Panel are disabled.  *Nokeyboard input will be accepted **No mouse input will be accepted	User Password	*Power/Reset -switches  are enabled.at front   panel. *Keyboard inputs will be accepted ** Mouse inputs will be accepted. *Boot seq A:,  C:


System Level Features - Columbus Chassis

The ALTServer offers the expansion capabilities required by server applications with ten peripheral bays, expansion slots for up to seven add-in cards, a 230 watt power supply and an additional fan to cool a fully-loaded server configuration. Four of the peripheral bays (including the standard 3.5" floppy drive) can be accessed from the front of the chassis. The ALTServer also meets stringent environmental requirements.

Related Topics:

Peripheral Bays

Fan

Expansion slots

Front Panel

Back panel

Power Supply - 230W

Power Supply - 300W

Power Consumption

Floppy Drive

Speaker

Chassis color

Dimensions - Columbus

System Reliability - MTBF


Peripheral Bays

Figure 7. ALTServer front panel

Ten expansion bays are available for peripherals, including hard drives, tape drives, CD-ROMs, and other devices. These include three 5¼" half-height bays and one 3½" one-inch bay accessible from the front panel (filled in system configurations with a floppy drive). Six internal 3½" one-inch bays are located in a peripheral carrier than is hinged and swings out from the chassis for easy access and integration.


Fan

The ALTServer has two fans to keep the system cool. One fan within the power supply provides 28 cfm of air movement. The second fan, located at he chassis front, provides up 500lfm across the add-in cards and the processor. The second fan receives 12 Vdc directly from the baseboard.


Expansion slots

The ALTServer has eight expansion card slots, all of which are intended for use with full-length cards. Five of the slots are dedicated for use with EISA or ISA cards and two of the slots are dedicated for use with PCI add-ins. One slot is shared by connectors for either an EISA/ISA or PCI card, but not both at the same time.


Front Panel

The ALTServer front panel consists of a power switch, reset switch, a power-on LED and a hard disk access LED. Four peripheral bays also can be accessed from the front panel, as shown in Figure 7.


Back panel

The back panel consists of access panels for the expansion slots (one location is unused), a 115/230 voltage switch, a power supply input, an auxiliary power output and the power supply fan. Access also is provided for any of the ALTServer riser boards, which provide connections to the baseboard I/O devices and interfaces, including the parallel port, serial ports, video, keyboard, mouse, and narrow or wide SCSI-2. The riser is available in several configurations, routing the SCSI signals to either external devices or into the chassis.

Figure 8. ALTServer angle view, showing slot locations and peripheral bays


Power Supply - 230W

The ALTServer integrates a 230 watt switchable power supply for all onboard resources, add-in cards, and peripherals. The Astec Corp. model SA230-3415 supports operating settings at 100-120 VAC (5 Amps AC) or 200-240 VAC (3 Amps AC). The input voltage is selected using a switch on the back of the system.

AC Power input Specifications

Input frequency 50/60 Hz
AC Voltage	Current
90-135	5.0 A
	4.0 A
Table 4. Power Supply Input Specifications.

DC output Specifications

DC Voltage	Max. Current Load	Minimum Current Load
+5V	30.0A	2.0A
-5V	0.5A	0A
+12V	8.0A	.25A
-12V	1.0A	0A
Table 5. Power Supply DC Output Specifications.


Power Supply - 300W

The ALTServer integrates a 300 watt switchable power supply for all onboard resources, add-in cards, and peripherals. The Astec Corp. model  SA301-3405 is 300W Baby AT form factor power supply supports operating settings at 100-120 VAC (6.3 Amps AC) or 200-240 VAC (3.15 Amps AC). The input voltage is selected using a switch on the back of the system.

AC Power input Specifications

Input frequency 50/60 Hz
AC Voltage	Current
115	6.3 A
230	3.15 A
DC output Specifications

OUTPUT	Max Current Load	Min Curent Load
+5V	32A	3A
+12V	12A	2A
-5V	0.5A	0A
-12V	1.0A	0A
+5V Standby	0.1A


Power Consumption

The following tables list the current and power consumed by system resources in a configuration which includes two Pentium processors and 8 SIMMs (two active and six standby). This information is preliminary and is provided as a guide for calculating approximate total system power usage with additional resources added.

Current

DC Voltage	Typical Current*	Max. Continuous Current
+5V	8.85 amps	15.75
-5V	Not required	Not required
+12V	38 milliamps	80 milliamps
-12V	18 milliamps	23 milliamps
Table 6. ALTServer current consumption (preliminary)

Watts

Resource	Max Power	Typical Power
Two 90 MHz processors with 32 MB SIMMs,  no add-in cards and no peripherals	80 Watts	45 Watts
Table 7. ALTServer wattage consumption (preliminary)


Floppy Drive

The ALTServer integrates a 3½" Teac Floppy drive Model FD-235HF into the external 3½" bay. This is the same proven floppy disk drive that has been used on many previous Intel systems.


Speaker

The standard system ships with an external speaker installed. The user may enable/disable the device using the System Configuration Utility or program the speaker via port 61H. The speaker provides error beep code information during POST if the system cannot use the video interface.


Chassis color

The chassis color is "Intel Pearl White."

•	Plastic: Standard Intel Pearl White, GE Plastics C2800 - #H86204

•	Paint: Standard Intel Pearl White, Sherwin Williams - Polane T #F99WX119

The bottom and back of the chassis are not painted.


Dimensions - Columbus

Height	19.3" (49.0 cm)

Width	8.3" (21 cm)

Depth	17.7" (45.0 cm)

Weight	33lbs (15 kg), without peripherals


System Reliability - MTBF

	RELIABILITY TEST METRICS
	MTBF 80% CONFIDENCE LIMITS:				15013.41	Hours at	40'C
	Calculations as of:		5/1/95 12:00


Environmental & Reliability Standards

The topics in this section specify the normal operating conditions for the ALTServer. Exposure to absolute maximum rating conditions for extended periods may affect system reliability.

Related Topics:

Absolute Maximum Ratings - Baseboard

Environmental - Baseboard

Electrical - Baseboard

Reliability Data - Baseboard


Absolute Maximum Ratings - Baseboard

Stresses beyond those shown in the following table may cause permanent damage (provided for stress testing only).

Operating Temperature	0°C to +55°C
Storage Temperature	-55°C to +150°C
Voltage on any signal with respect to VSS	-0.3 to VCC +0.3 V
Supply Voltage with Respect to VSS	-0.3 to +5.5 V


Environmental - Baseboard

The ALTServer is intended for use in a Class B environment (residential). It meets the Intel Board Environmental Specification 112000 Rev. G. The following table summarizes environmental limits for the ALTServer:

Parameter	Condition	Specification
Temperature	Non-Operating	-40oC to +70oC
	Operating	+0oC to +50oC
Airflow	300 LFM	40oC
	400LFM	45oC
	500LFM	50oC
Humidity	Non-Operating	92% Relative Humidity max. @ 36oC
	Operating	80% Relative Humidity max. @ 36°C
Altitude	Non-Operating	50,000 feet (15,240 meters)
	Operating	10,000 feet (3048 meters)
ESD	1.0kV	No Errors
	2.5kV	No Errors
	5.0kV	5% Soft Errors, 0% Hard Errors, No physical damage
	7.5kV	10% Soft Errors, 0% Hard Errors, No physical damage
	10.0kV	25% Soft Errors, 5% Hard Errors, No physical damage
	12.5kV	50% Soft, 10% Hard, No physical damage
	15.0kV	100% Soft, 25% Hard, No physical damage
	25.0kV	100% Soft, 100% Hard, No physical damage
Shock	Non-Operating	30.0G, 11ms, 1/2 sine


Electrical - Baseboard

ALTServer DC specifications are summarized here, for motherboard signaling environment, power connectors, and 5V power budget. Refer to PCI Local Bus Specification Rev. 2.0, and EISA Bus Specification for PCI and EISA/ISA DC and AC electrical specifications. Refer also to the documentation for ASIC devices used on the ALTServer. The following tables show the required DC specifications for 5V and 3.3V Altair bus signaling environments.

Symbol	Parameter	Condition	Min	Max	Units
Vcc	Supply Voltage		4.75	5.25	V
TA	Operating Temp.	Still Air	0	55	C
Vih	Input High Voltage		2.2	Vcc +1.2	V
Vil	Input Low Voltage		-1.2	0.8	V
Iih	Input High Current	Vin = 2.7		1.0	mA
Iil	Input Low Current	Vin = 0.5		-1.6	mA
Voh	Output High Voltage	Ioh, max    Vcc, min	2.4		V
Vol	Output Low Voltage	Iol,max     Vcc, min		0.55	V
ALTServer 5 Volt DC Specification

Symbol	Parameter	Condition	Min	Max	Units
Vcc3	Supply Voltage		3.0	3.6	V
Vih	Input High Voltage		0.475 x Vcc3	Vcc +0.5	V
Vil	Input Low Voltage		-0.5	0.325 x Vcc3	V
Iih	Input High Leakage Current	Vin = 2.7		10	A
Iil	Input Low Leakage Current	Vin = 0.5		10	A
Voh	Output High Voltage	Iout = -0.5 mA	0.9 x Vcc3		V
Vol	Output Low Voltage	Iout = -1.5 mA		0.1 x Vcc3	V
ALTServer 3.3 Volt DC Specification


Reliability Data - Baseboard

The Mean-Time-Between-Failures (MTBF) data is calculated from predicted data @ 55C.

MTBF	Temperature
73,189 Hours.	55C


System Level Features - Magellan Chassis	- MG5000

Introduction - Magellan

Drawing - Magellan

Power Supply - Magellan

SCA drive bays - Magellan

SCA Hot Swap BackPlane in MG5000 system

SCA Backplane Drawing

Front Panel Intelligence

"Blinky" Light Board

Dimensions - Magellan


Introduction - Magellan

The  MG5000 is specifically designed to take all the peripherals necessary create high performance servers.  The 29" high chassis houses eight I/O expansion slots, eleven peripheral bays, and a 525 watt auto-ranging power supply.  The chassis is fabricated using electrogalvanized (EG) metal to minimize EMI/RFI.  Easy access to the interior system baseboard, processor module(s), memory module(s) and any add-in cards is provided by two thumbscrews on the side panel.  A front door opens to access the six hot-swap drive array for easy replacement of the SCSI-2 hard drives.  A side cover lock loop is available to secure the side panel.

The six internal 3½" full-height bays provide over 54 GB of hard disk expansion.  The six bays have been designed to allow easy setup of Redundant Array of SCA-compatible Backplane.  Four external 5¼" half height bays are available for backup or removable media devices.  The standard MG5000 configuration incorporates a 3½" Teac FD235HF 217U floppy disk drive, which supports 720 KB, 1.44 MB, and 2.88 MB media, for a total of five external drive bays.  A Sharp LM16X21A LCD 32 character display is also included.

The front cover on the MG5000 Mid-Range server provides access to the four external peripheral bays, the 3½" floppy drive, system reset switch, and poweron/off.   Three LEDs display system activity:  a yellow LED for IDE or SCSI hard disk activity, a red LED for a SCSI failure, and a green LED for system poweron.  The MG5000 front panel is protected by a mechanically lockable front door. Unique keys are used for additional security. A master key option is available for both the front panel and side chassis locks.


Drawing - Magellan

Figure 6:

 MG5000 Chassis


Power Supply - Magellan

The Delta 525  auto-ranging power supply automatically switches between 110V and 220V AC inputs,  supporting use in all parts of the world without requiring a switch change. The power supply has three DC peripheral connectors for the accessible drive bays; two mini-output connectors for use with 3½" floppy drives and one TTL output connector for use with 5¼" peripherals or a 3½" hard drive. A separate connector provides power directly to the SCSI-2 SCA Backplane.

The power supply fan transfers air at a rate of 250-300 linear feet/minute (35 cfm) from the exhaust port to cool the baseboard and peripherals. In order to provide additional cooling with minimum noise, a variable speed fan (maximum 100 cfm) also helps cool the chassis interior. The fan speed is determined by the air temperature and the number of  hard drives in the bottom peripheral bays. This fan is monitored for a drop in RPM's based on an internal temperature increase.  If necessary, the fan can be "hot-swapped" without bringing down the server system. The MG5000 is pressurized internally to allow needed airflow across all drive bays.  Operating with the side cover or processor compartment panel removed disrupts the airflow and will affect long term reliability.


SCA drive bays - Magellan

The MG5000 Mid-Range Server system is designed for easy installation, upgradability and maintenance of the disk, processor, memory and I/O subsystems.  The SCSI-2 SCA Backplane minimizes cabling for power and control from disk controllers and the power supply to the drive bays and contains a SCSI-2 port for any external SCSI drives.  The Adaptec AIC-7870 SCSI-2 controllers integrated on the system baseboard eliminate the need to install SCSI controllers in the expansion slots.  The MG5000 server includes easy to recognize LEDs, a lockable front panel, Single Connector Attachment (SCA) support for SCSI disk drives, and even a security sensor for unauthorized entry into the hot-swap drive array compartment.

The SCSI-2 SCA-compatible Backplane allows the user to have one continuous fast/wide SCSI bus for access to all hot-swappable drive bays.  Users need only to set the SCSI device ID for the disk, tape or CD ROM drives and install the peripherals on the SCSI bus.  Because the SCA Backplane takes care of terminating the SCSI bus, all terminating resistors should be removed from SCSI devices.  This saves the system integrator from having to determine which devices are physically located at each end of the SCSI bus and removing the termination resistors from only those two devices, as required on virtually all other PC server systems. The SCSI-2 SCA Backplane allows either SCSI-1 (5 MB/sec.) or Fast/Narrow SCSI-2 (10 MB/sec.), or Fast/Wide SCSI-2 (20MB/sec.) data transfers to the 3½" hard drives.


SCA Hot Swap BackPlane in MG5000 system

The hot swap backplane supports up to six SCSI SCA (Single Connector Attach) drives.  The SCSI bus is configurable as;  one bus and six drives, or two buses and three drives per bus.  Associated "active" bus termination is provided on the backplane to support either configuration.  The backplane allows removal and replacement of drives during power on without causing electrical disturbance to adjacent drives or disruption data integrity of the SCSI bus.  The backplane uses a docking connector and special circuitry to make this possible.  The special circuitry consists of delay circuits.  The primary delay is approximately ¼ second and the secondary delay is a 250 microsecond ramp.  The secondary delay applies power gently to the drive, preventing inrush current surges that normally cause disruptive problems to adjacent drives.  Additional circuitry allows for "fault" signals to power down a drive and activate its corresponding fault LED.  It would indicate that the drive could now be removed and replaced.  Replacing the drive activates the two delay circuits powering up the drive and also activates the "reset" signal on the SCSI bus.  The reset signal is intended to be a signal to the controller to indicate the the drive has been replaced.  It is expected that the controller removes the fault signal at the time.

The reset signal is for controller communication only, and not necessary to prevent bus disturbance.  Additional circuitry also drives the "power" and "activity" LEDs.  The activity LED is driven by the drive itself.  The power LED is driven by the +5v applied to the drive.

The SCSI SCA backplane is responsible for guraranteeing that there is no data corruption to/from SCSI hard drives connected to the backplane whtn a device is inserted inot the backplane or when poer is enabled.  When a SCSI hard drive is to be removced from the backplane, the SCA-compatible hard drive circuitry removes power from the drive.  When the SCSI hard drive is inserted into the SCSI SCA backplane, power is enabled and the hard drive is locked into place.  The onboard AIC-7870 SCSI disk drive controller does not automatically send a START UNIT command, but instead must be enabled by the user.  Howerver, when the SCSI hard drive is used with the XXPCIRAID4 (or other RAID controllers) are used, typically a START UNIT command is automatically sent.

Hot-Plug:  The ablity to plug a SCSI device into an active backplae without stopping I/O's to other SCSI devices on the bus.

Hot-Add:  The ability to add a new device to a SCSI Bus, be recognized by the SCSI controller, and used without turning off the power to the SCSI backplane

Hot-Swap:  The ability to swap an existing device to a new device on the SCSI backplane with turning off the power.

The product contains six 3.5" hard drive bays which are accessible from the lower front bezel.   A Hot Plug capable backplane is part of the 3.5 inch drive bay assembly.   The backplane is designed for Wide/Fast SCSI II devices using the Industry Standard 80 pin SCA connector.   This backplane consists of 2 rows of three drives each.   These bays are numbered 6 through 11.

The hot plug backplane implementation requires the use of a drive carrier.   The drive carrier accommodates 3.5" wide peripherals that are 1.6 or 1.0 inch high.   The drives are mounted in the carrier via four (4) fasteners.   The carrier is retained in the chassis via a locking handle.   Integral to the drive carrier is a pair of EMI/ESD grounding clips which make contact to the drive through the fasteners.

The user can configure the backplane to be controlled by baseboard SCSI channel A or both A and B.   In addition the user can configure the SCSI bus ID address on the backplane.   The factory default is ID 0,1,3 in the upper row (Bays 6-8) and ID 4,5, & 6 in the lower row(Bays 9-11).   By moving 2 jumpers on the backplane the SCSI ID are changed to 8,9 ,11 in the upper row and 12, 13,14 in the lower row.

All termination on the SCSI hot plug backplane is active.    The user can terminate the backplane so it operates as two busses with narrow cable to the upper peripherals(factory default), one bus with narrow cable to the upper peripheral bay, two busses with no narrow cable to the upper peripheral bay, or one bus with no cable to the upper peripheral bay.

An indicator board located above each row of drives will display individual drive status.   The drives status' are power on, activity, and  fault.   A fault light on the front panel board will indicate fault on internal drives.

These hot swap drive bays are designed to accept peripherals that consume up to 15 Watts of power, with peripherals that are specified with a maximum ambient temperature of 50oC.


SCA Backplane Drawing

SCSI Bus options:

Upper & Lower SCA bays on SEPERATE SCSI channels

* Connect controller "A" to J7, connect controller "B" to J16

* Remove J19 & J20 and connect J6 to terminated SCSI device in 51/4"  bays

* Ensure J10, J11, & J12 are installed

Upper & Lower SCA on a SINGLE SCSI channel

* Connect controller to J16

* Remove J10, J11, & J12

* Connect Wide SCSI "Jumper" cable from J8 to J7

* Ensure J19 & J20 are installed when not using J6 as port to 51/4"  bays

Explanation of Drawing:

J1 - MG5 Front Panel	J8 - Wide SCSI for jumper from Lower to Upper SCA bay
J2 - Upper bay Drive Presence / Activity LEDs	J9 - Lower bay Drive Presence / Activity LEDs
J3, J4, J5 - Upper SCA bay connector	J10, J11, J12 - Terminating Resister Packs
J6 - Narrow SCSI connetor to MG5000 upper bay	J13, J14, J15 - Lower SCA bay connector
RP1, RP2 - Terminating Resister Packs	J16 - Wide SCSI connector for Lower SCA bay
J7 - Wide SCSI connector for Upper SCA bay	J17 - XXPCIRAID Fault indication
E83-E86 - SCSI ID Selection	J18 - Power
DDE_LINK1DDE_LINK3DDE_LINK4Drive Bay Connector	No Jumper*	E85-E86	E83-E84	E85-E86 and E83-E84
J3	SCSI ID = 0	SCSI ID = 0	SCSI ID = 8	SCSI ID = 8
J4	SCSI ID = 1	SCSI ID = 1	SCSI ID = 9	SCSI ID = 9
J5	SCSI ID = 3	SCSI ID = 3	SCSI ID = 11	SCSI ID = 11
J13	SCSI ID = 4	SCSI ID = 12	SCSI ID = 4	SCSI ID = 12
J14	SCSI ID = 5	SCSI ID = 13	SCSI ID = 5	SCSI ID = 13
J15	SCSI ID = 6	SCSI ID = 14	SCSI ID = 6	SCSI ID = 14
* Default configuration


Front Panel Intelligence

The system front panel board contains the following features: power switch, a reset switch, and the following indicators: power, two SCSI/IDE bus activity indicators and one SCSI fault indicators and system speaker.   The front panel board has been designed to be compatible with Hobbes and System Mangement Software.

The LEDs will consist of two drive activity(green),  one drive fault(yellow) and one power on (green) indicator.   Each of the SCSI channels on the baseboard will be able to independently display activity.    If a SCSI fault occurs the yellow LED will illuminate.

There are 6 connectors on the front panel.   A 34 pin connector will connect to a ribbon cable from the baseboard.    A four pin connector for the access alarm switches.   A 10 pin connector to the hot swap backplane fot the I2C bus and fault indicators.   A 14 pin connector supplies data lines to the LCD and a 3 pin connector provides LCD backlight power.   The speaker is connected to a 4 pin header.

LCD display

Speaker

Power on/off switch - always power system on but will only power system off if SECUR signal is low

System reset switch - causes 150 msec low pulse to system if SECUR signal is low - resets all devices on the motherbd

Keylock switch - low on signal cause keybd activity to be ignored

Hard drive activity LEDs (qty 2)  - LED 1 is active when onbd SCSI channel A or B is active or onbd IDE is active or pins J1J2 1 or 3 are low.  LED 2 is active if J1J2 pin 2 or 4 are low.

Constant 5V which is provided at all times when AC is applied to Pwr supply

Misc signals:

5V - indicator pwr supply is on (qty 2 lines)

3.3V - indicator baseboard has a 3.3V pwr source

SECUR - TTL signal when asserted locks out reset and Pwr off switch.  This signal is sourced from the motherbd and has two potential sources which are enabled by BIOS.  One is detection of keybd inactivity for a specified period of time.  The other is achieved by setting bit 7 of INCA general purpose register to a logic 1.  The keybd inactivity can be masked off to the front panel by setting bit 10 to a logic 0 of INCA general purpose register.

FPNMI# - Sourced from front panel  a TTL signal or'd in with other NMI sources to allow user to force an NMI to system processor

I2C-SDA - Serial data conforming to I2C specification

I2C-SCK - Serial clock conforming to I2C specification

Ground - logic ground ( qty 6 lines)

PWR# - TTL signal sourced from the motherbd when assert high will cause the system to power off.  The system maybe powered back on by pushing the front panel on/off switch or driving the PWR# signal low.

Power On—System power on can be initiated at any time by the front panel switch or via Server Management board through pulse on PWR#

Power Off—Front Panel switch when secure mode is not set (SECUR_MOD low), Server Management board via pulse on PWR#, Baseboard via pulse PWR#

Secure Mode—SECUR_MOD is high one of the following is true;  front panel reset switch is disabled, front panel power cannot power system off, Server management power down the system via pulse on PWR#, Baseboard can power down the system via a pulse on PWR#, regardless of previously activity on the front panel switches, releasing secure mode will not cause the system to power down.

Power Recovery—In the event of an AC power failure, when AC power is restored the system power will return to the state it was in prior to AC power being removed.  The function is controlled by the front panel without any intervention required by an operator or server management card.

PWR# requires a low going high transition for a minimum of 11 microseconds.

The PAL that controls interrupt routing contains an equation that causes front panel NMI to be disabled when SMI is enabled. Front panel NMI should not be disabled when SMI is enabled. Front panel NMI should be routed the same way mnmi (NMI from the ESC) is.

NOTE: there's some question about the utility of this feature since it doesn't set any status bit that would indicate the source of the NMI. It may be that to make this feature useful, Front Panel NMI would actually need to be OR'd into IOCHK to be detectable.

This is to clear up some questions on the front panel used with XXpress and Altair in the Magellan chassis.  The only front panels that should be used are assembly number 635025-001 or -002.  If you don't know which front panel you have and there is no label on it, look for the PB number etched on the back of the board.  It should be 635028-001.  This board uses mostly surface mount components and has a 28-pin PAL (NOT the 20-pin PAL) located just above the reset switch.  It also has a 2-pin jumper near the reset switch.  IMPORTANT!!!!

This jumper MUST be installed when used with 12" and 15" baseboards.  When used with Altair this jumper must be removed.  Failure to set the jumper properly will result in erratic behavior of the front panel.


"Blinky" Light Board

The Drive Power LED is driven from the "blinky" light board and is ON whenever a drive is being powered.

The Drive Activity LED is directly controlled by the drive via a signal on the SCA connector.

The Fault LED can be activated or deactivated by the XXPCIRAID4 cable.  When the Fault LED is first activated, the drive is powered off.  Since the drive is powered off, the Drive Power LED is off as well.  The drive will remain powered off until the drive is removed and plugged back in.  Installing a drive causes drive power to be reapplied.  Installing a drive does not cause the Fault LED to go off.  Clearing the Fault LED after a drive has been inserted is up to the XXPCIRAID4 driver software.

The onboard AIC-7870 drivers don't utilize the fault LED and currently does not support "hot-Swapping' of drives under any operating system.


Dimensions - Magellan

Dimensions	MG5000 Server System
Width	no feet:  9.5"  (24.13 cm) with feet:  15.33"  (38.94 cm)
Depth	26.75"  (67.95 cm)
Total Height	25.49"  (64.74 cm)
Weight (approx.)	65 lb. (29.48 kg.)


Intel XXPCIRAID4 Disk Array Controller

The Intel XXPCIRAID4 Disk Array Controller allows the Xtended Xpress system to operate with a high degree of fault tolerance, while maintaining a high performance peripheral interface. The XRAID4 supports data striping without parity (RAID 0), disk mirroring (RAID 1), data striping with parity distributed across all disks in the array (RAID 5) and mirrored striped disks (RAID 6). Use of RAID levels 1, 5, or 6 improves system data availability and provides full data fault resistance. For transaction processing environments, RAID level 0 will improve I/O rates and overall system performance, but full fault tolerance is not supported.

The 32-bit PCI bus master add-in card features two fast SCSI-2 channels, an Intel960 RISC processor, and ships with a 4 MB cache with upgrade support for 16 or 32 MB. The two independent SCSI channels each use an NCR 53C720 SCSI processor and each supports seven peripherals. Each channel conforms to the SCSI-2 specification and transfers data at up to 10 MB/second.

Other features of the high performance XXPCIRAID4 controller include:

Onboard cache memory up to 32 MB (default is 4 MB)

An i960 RISC processor to control SCSI and PCI bus transfers, drive rebuilding, error recovery, RAID processing and configuration. The i960 also handles configuration of the disk cache memory.

A PCI bus master interface, allowing the XRAID4 controller to achieve 32-bit master mode (Class C) transfers at rates up to 33 MB/sec.

Field-programmable Flash memory, providing redirection for all INT13 calls to the i960, easy BIOS and firmware upgrades from a floppy diskette, and the ability to store configuration and drive failure data.

Easy-to-use configuration software simplifies integration. The XXPCIRAID4 currently ships with three software support packages, XXPCIRAID4 Utilities for MS-DOS, Software Drivers for SCO UNIX V.3.2.4 and Software Drivers for Novell NetWare 3.12, Netware 4.01, and Netware 4.10.

Fault indication connector for use with MG5000 Chassis

26 Pin Male Connector

Pin 1

Pin #

05	-FAULT DRIVE ID0  	Output --- Channel 0 or Channel 1, ID 0

07	-FAULT DRIVE ID1  	Output --- Channel 0 or Channel 1, ID 1

09	-FAULT DRIVE ID3  	Output --- Channel 0 or Channel 1, ID 3

11	-FAULT DRIVE ID4  	Output --- Channel 0 or Channel 1, ID 4

13	-FAULT DRIVE ID5  	Output --- Channel 0 or Channel 1, ID 5

15	-FAULT DRIVE ID6  	Output --- Channel 0 or Channel 1, ID 6

17	-FAULT FTPNL	Output --- Front Panel Fault Light - if any drive at fault.

18	GND    	Ground

22	GND    	Ground

All other pins - Do not care

Requirements:

In the event of a SCSI drive failure, the controller will mark the drive DEAD and assert the corresponding fault output signal, -FAULT DRIVE  ID#.  When this signal is received, the disk drive back plane will power on the corresponding Drive Fault LED and will turn off both 5 and 12 volt power to the drive.  This signal should be held asserted by the controller until the drive has been replaced and put back on line by rebuilding or put into a stand-by mode, or the system has been powered off.  In the case the system has been powered off, when the system is powered on, the controller will regard the drive as dead, whether or not the drive has been replaced.  The controller should not assert the FAULT DRIVE ID# for a drive it regards as DEAD on power up.

At the same time any -FAULT DRIVE ID# is asserted, the -FAULT FTPNL signal is asserted.  The drive back plane will power the Front Panel Fault LED whenever the -FAULT FTPNL signal is asserted.  Whenever the system is powered up, and the controller has a drive marked DEAD, the -FAULT FTPNL signal should be asserted.

The dead drive can be removed from the SCA back plane without any effect on the SCSI bus, since the drive has been powered off.

When a drive is inserted into the SCA back plane, the back plane asserts RESET on the SCSI bus for ~ 250msec.  At the end of the RESET assertion, the 5 and 12 volt to the drive is ramped to the drive.  The power ramps up in 500 microseconds.   The controller  should adhere to the requirement that no SCSI command is issued before 250msec after the RESET signal is deasserted.  The drive will not spin up until the Controller issues a Start command.


Software Drivers Supported

Operating System	Cirrus 5430 Video Driver	AIC-7870 SCSI Driver	Dual Pentium	XXPCIRAID4 Driver
Novell 3.12, 4.01, 4.1	Ships with NetWare	Ships with ALTServer		Ships with XXPCIRAID4
Microsoft OS/2 1.3	Ships with OS/2	Not Supported		Not Supported
IBM OS/2 2.11	Ships with OS/2	Ships with ALTServer		Ships with XXPCIRAID4
SCO UNIX System V 4.2	Ships with UNIX	Ships with ALTServer		Ships with XXPCIRAID4
Banyan 5.53	Ships with Vines	Not Supported		Not Supported
Sunsoft Solaris 2.4	Ships with UNIX	Not Supported		Not Supported
Interactive/UNIX 3.2.4, Release 4	Ships with UNIX	Not Supported		Not Supported
Novell UnixWare 2.01	Ships with UNIX	Ships with ALTServer		Ships with XXPCIRAID4
NextStep Release 3.2	Ships with OS	Not Supported		Not Supported
Windows NT 3.5	Ships with NT	Ships with ALTServer		Ships with XXPCIRAID4
Windows 3.0	Not Supported	Not Supported		Not Available
Windows 3.11	Ships with ALTServer	Ships with ALTServer		Ships with XXPCIRAID4
Specific DOS Applications	Ships with ALTServer	Ships with ALTServer		Ships with XXPCIRAID4
Table . ALTServer Driver Support.


 Customer Support

The ALTServer is backed by Intel's industry-leading support groups in the OEM Products and Services Division (OPSD), including IntelTechDirect, which includes these major services:

Related Topics:

INTEL Applications Support

Intel Applications Support BBS

WINDOWS HELP FILES

FaxBack


INTEL Applications Support

A direct link to highly qualified and well trained technical personnel.

- Toll-free access to Intel support engineers for problem resolution

- Responses within 24 hours Monday-Friday

- Expert assistance geared to the special needs of OEMs and VARs

- 1-800-628-8686


Intel Applications Support BBS

A full service bulletin board with product information, demo software and more.

- Available worldwide through direct-dial

Americas	916-356-3600

Europe	44-793-496340

- Modem speeds up to 14.4k baud with standard software

- FLASH BIOS upgrade files

- Modem set at no parity, 8 data bits, 1 stop bit.

- Master BBS file list and FaxBack catalog available at 800-897-2536.


WINDOWS HELP FILES

- Monthly Product updates available to qualified users on the bulletin board

- Official notification of engineering changes and technical data

- Easy information retrieval using Windows Help file format

- Intel platform system, board, and BIOS revision histories

- Hardware and software compatibility notes

- Documentation updates, spare parts and order information


FaxBack

- Product descriptions and technical data sent to any fax machine from a touch-tone phone

- Information on End-of-Life products

- Available worldwide through direct dial

U.S. Toll Free	800-628-2283 (Americas: 916-356-3105)

Europe	44-793-496646


Legal Stuff

ALTServer

Windows* Helpfile

Intel Corporation disclaims all warranties and liabilities for the use of this document and the information contained herein, and assumes no responsibility for any errors which may appear in this document. Intel makes no commitment to update the information contained herein, and may make changes at any time without notice. There are no express or implied licenses granted hereunder to any intellectual property rights of Intel Corporation or others to design or fabricate Intel integrated circuits or integrated circuits based on the information in this document. Contact your local sales office to obtain the latest specifications before placing your order.

*All other brands and names are the property of their respective owners.

Intel Corporation makes no warranty for the use of its products and assumes no responsibility for any errors which may appear in this document nor does it make a commitment to update the information contained herein.

Intel Corporation retains the right to make changes to these specifications at any time, without notice.

Contact your local sales office to obtain the latest specifications before placing your order.

The following are trademarks of Intel Corporation and may only be used to identify Intel products:

376	i750	MAPNET

Above	i860	Matched

ActionMedia	i960	MCS

BITBUS	Intel287	Media Mail

Code Builder	Intel386	NetPort

DeskWare	Intel387	NetSentry

Digital Studio	Intel486	OpenNET

DVI	Intel487	OverDrive

EtherExpress	Intel	Paragon

ETOX	intel inside.	Pentium

ExCA	Intellec	ProSolver

Exchange and Go	iPSC	READY-LAN

FaxBACK	iRMX	Reference Point

FlashFile	iSBC	RMX/80

Grand Challenge	iSBX	RxServer

i	iWARP	SatisFAXtion

ICE	LANDesk	SnapIn 386

iLBX	LANPrint	Storage Broker

Inboard	LANProtect	SuperTuned

i287	LANSelect	The Computer Inside.

i386	LANShell	TokenExpress

i387	LANSight	Visual Edge

i486	LANSpace	WYPIWYF

i487	LANSpool	IntelTechDirect

MDS is an ordering code only and is not used as a product name or trademark. MDS is a registered trademark of Mohawk Data Sciences Corporation.

CHMOS and HMOS are patented processes of Intel Corp.

Intel Corporation and Intel's FASTPATH are not affiliated with Kinetics, a division of Excelan, Inc. or its FASTPATH trademark or products.

TRADEMARK ACKNOWLEDGMENTS

TwinChannel is a trademark of Adaptec Corp.

Centronics is a trademark of Centronics Data Computer Corp.

Hercules is a trademark of Hercules Technology Corp.

MDA, CGA, EGA, VGA, PS/2 and PC/AT are trademarks of International Business Machines Corp.

MS-DOS, OS/2, Windows and Microsoft are trademarks of Microsoft Corp.

BurstRAM is a trademark of Motorola, Inc.

Novell is a trademark for Novell Corp.

UNIX is a trademark of AT&T Bell Laboratories

USL is a trademark of UNIX System Laboratories

Western Digital and Caviar are trademarks of Western Digital Corp

*All other trademarks are the property of their respective owners.

© INTEL CORPORATION, 1994


SIMM Qualification Specification

Revision 01

March 10,1995

Intel Document Number:  634104

Related Topics:

1.0 SCOPE:

2.0 APPLICABLE DOCUMENTS:

3.0 MECHANICAL REQUIREMENTS:

4.0 ELECTRICAL REQUIREMENTS:

5.0 ENVIRONMENTAL REQUIREMENTS:

6.0  SPECIAL REQUIREMENTS:

7.0 REFERENCE DATA:


ALTServer Help - SIMM Qualification Specification - 1.0 SCOPE:
1.0	SCOPE:

This document establishes the detailed requirements which the manufacturer must guarantee for a SIMM, single-in line memory module, for use in ALTAIR platforms.


ALTServer Help - SIMM Qualification Specification - 2.0 APPLICABLE DOCUMENTS:
2.0	APPLICABLE DOCUMENTS:

The latest revision in effect of the following document:

Technical Product Summary -- ALTAIR Platforms:  Order No. 634116


ALTServer Help - SIMM Qualification Specification - 3.0 MECHANICAL REQUIREMENTS:
3.0	MECHANICAL REQUIREMENTS:

3.1	PC Board

3.1.1	Substrate - FR4 Epoxy glass laminate clad with minimum 1 ounce copper for internal and external 	layers.

3.1.2	Etch Line and Card Edge Contact:  Tin/Lead only.

3.1.3	Plated Through Holes:  After plating, holes shall have a minimum arithmetic average of .001 inch of 	copper with a minimum of .0006 inch.

3.2	Safety

3.2.1	UL Rating:  Printed wiring board to have a flammability rating of 94V-0.  Markings to include UL traceability requirements per UL Recognized Component Directory.

3.3 Outline Diagram with Pinouts


ALTServer Help - SIMM Qualification Specification - 4.0 ELECTRICAL REQUIREMENTS:
4.0	ELECTRICAL REQUIREMENTS:

4.1	SIMM Configuration Definitions

This section refers to ALTAIR SIMM configurations.  The ALTAIR platform supports either 1M x 36, 2M x  36, 4M x 36, or 8M x 36 SIMMs.

4.1.1	Support Features

The ALTAIR architecture uses the 82434NX (PCMC) PCI Cache and Memory Controller which support symmetric addressing and Fast Page Mode operation.

4.1.2    DRAM Address Translation

The MA[11:0] lines are translated from the host address lines A[26:3] for all memory accesses, except those targeted to memory that has been remapped as a result of the creation of memory space gap in the lower extended memory area. In the case of a cycle targeting remapped memory, the least significant bits come directly from the host address, while the more significant bits depend on the memory space gap start address, gap size, and the size of main memory. The MA[11:0] bits are derived from the host address bus as defined by Table 1.

          TABLE 1. DRAM Address Translation

Mem. Add. MA[11:0]	11	10	9	8	7	6	5	4	3	2	1	0
Row Address	A26	A24	A22	A20	A19	A18	A17	A16	A15	A14	A13	A12
Column Address	A25	A23	A21	A11	A10	A9	A8	A7	A6	A5	A4	A3
4.1.3    Refresh

The DRAM controller contains an internal refresh timer which periodically requests the refresh control logic to perform either a single refresh or burst of four refreshes. The single refresh interval is 15.6s. The interval for a burst of four refreshes is four times the single refresh interval, or 62.4s. The PCMC is configured for either single or burst of four RAS#-only refresh cycles via the DRAM Control Register at offset 57h.

To minimize the performance impact, refresh cycles are partially deferred until the DRAM interface is idle. Refresh cycles are initiated such that the RAS# maximum active time is never violated.

4.1.4	TABLE 2.  Pin Connection

Pin	Sig	Pin	Sig	Pin	Sig	Pin	Sig	Pin	Sig	Pin	Sig

 1	VSS	13	A1	25	DQ24	37	DQ17	49	DQ9	61	DQ14

 2	DQ0	14	A2	26	DQ7	38	DQ35	50	DQ27	62	DQ33

 3	DQ18	15	A3	27	DQ25	39	VSS	51	DQ10	63	DQ15

 4	DQ1	16	A4	28	A7	40	CAS#0	52	DQ28	64	DQ34

 5	DQ19	17	A5	29	A11	41	CAS#2	53	DQ11	65	DQ16

 6	DQ2	18	A6	30	VCC	42	CAS#3	54	DQ29	66	NC

 7	DQ20	19	A10	31	A8	43	CAS#1	55	DQ12	67	PD0

 8	DQ3	20	DQ4	32	A9	44	RAS#0	56	DQ30	68	PD1

 9	DQ21	21	DQ22	33	RAS#3	45	RAS#1	57	DQ13	69	PD2

10	VCC	22	DQ5	34	RAS#2	46	NC	58	DQ31	70	PD3

11	NC	23	DQ23	35	DQ26	47	W	59	VCC	71	NC

12	A0	24	DQ6	36	DQ8	48	NC	60	DQ32	72	VSS

 Note: Address pin A9 is used for up to 2M x 36 SIMMs and A10 support addressing up to 8M x 36.

 4.1.5	TABLE 3.  Pin Names

SYM	PARAMETER

A0 to A11	12 ADDRESS INPUTS

DQ0 to DQ35	36 DATA INPUT/OUTPUTS

CAS#0 - CAS#3	4 COLUMN ADDRESS STROBE

RAS#0 - RAS#3	4 ROW ADDRESS STROBE

W	READ/WRITE INPUT

VCC	POWER (+5V)

VSS	GROUND

NC	NO CONNECTION

Note: The ALTAIR architecture has 12 (MA[0:11]) addresses to support 12 x 12 symmetrical addressing.

4.1.6	TABLE 4.  Absolute Maximum Ratings

SYM	PARAMETER	RATINGS

Standard

Vcc	SUPPLY VOLTAGE	-1V to 7V

VIN	INPUT VOLTAGE	-1V to 7V

Vo	OUTPUT VOLTAGE	-1V to 7V

Io	SHORT CIRCUIT CURRENT	 50mA

Pd	POWER DISSIPATION	 20.8 Watts

Tstg	STORAGE TEMPERATURE	-55 to 125°C

Notes: 	1. Vcc, VIN and Vo are with respect to ground (Vss).

2. Power dissipation value is referenced @ 25°C ambient temperature.

4.1.7       TABLE 5.  Recommended Operating Conditions, Ta = 0°C to +70°C.

SYM	                PARAMETER	MIN	MAX

Vcc	SUPPLY VOLTAGE	4.75V	5.25V

VIH	HIGH LEVEL INPUT VOLTAGE, (ALL INPUTS)	2.4V	VCC + 1

VIL	LOW LEVEL INPUT VOLTAGE, (ALL INPUTS)	-1.0V	0.8V

4.1.8	TABLE 6.  DC Electrical Characteristics, Ta = 0°C to +70°C, Vcc=5V±5%,Vss=0V.

SYM	PARAMETER	TEST CONDITIONS	STANDARD - 60ns	STANDARD - 70ns
			MIN	MAX	MIN	MAX
VOH	HIGH LEVEL OUTPUT VOLTAGE	IOH=-5mA	2.4V	__	2.4V	__
VOL	LOW LEVEL OUTPUT VOLTAGE	IOL=4.2mA	__	0.4	__	0.4
IOL	OUTPUT LEAKAGE CURRENT	Q FLOATING 0V<VOUT<Vcc	-20µA	20µA	-20µA	20µA
IIL	INPUT LEAKAGE CURRENT	0V<VIH<Vcc + 0.5, OTHER INPUT PINS=0V	-240A	240µA	-240A	240µA
Icc1	OPERATING CURRENT	RAS#, CAS# CYCLING		1200mA		1200mA
Icc2	STANDBY CURRENT	RAS#=CAS#=VIH OUTPUT OPEN		48mA		48mA
Icc3	RAS# ONLY REFRESH CURRENT	tRC-tWC=MIN, OUTPUT OPEN		1200mA		1200mA
Icc4	FAST PAGE MODE CURRENT	RAS#=VIL,CAS#=CYCLING tPC=MIN,OUTPUT OPEN		800mA		850 mA
Note:  1. Icc1, Icc2, Icc3 and Icc4 are dependent on output loading and cycle rates.  Specified

               values are obtained with the output open.  Icc is specified as an average current.

4.1.9	TABLE 7.  Capacitance.  Ta=0°C to +70°C, Vcc=5V ±5%, f =1MHz,

unless otherwise noted.

SYM	PARAMETER	STANDARD 60ns	STANDARD  70ns
		MAX	MAX
CI(A)	Input Capacitance, (A0-A10) Address Inputs	88pF	155pF
C(DQ)	I/O Output Capacitance, (DQ0 to DQ35) Data Outputs	22pF	39pF
CI (W)	Input Capacitance, Write Control Input	94pF	185pF
CI(RAS#)	Input Capacitance,  RAS#0 - RAS#3	60pF	80pF
CI(CAS#)	Input Capacitance,  CAS#0 - CAS#3	42pF	80pF
4.1.10	TABLE 8.  Timing Requirements.  Ta=0°C to +70°C, Vcc=5V  ±5%. All units in 	nanoseconds unless otherwise noted.

SYM	PARAMETER	STANDARD  60ns	STANDARD 70ns	NOTE
		MIN	MAX	MIN	MAX
tRC	Random read or write cycle	110		130
tPC	Fast page mode cycle time	40		45
tRAC	Access time from RAS#		60		70	4,9
tCAC	Access time from CAS#		15		20	4,9
tAA	Access time from column address		30		35	4,10
tCPA	Access time from CAS# precharge		35		40	4
tCLZ	Output Low-Impedance time from CAS# low	0		0		4
tOFF	Output buffer turn-off delay	0	15	0	20	5
tT	Transition time	3	50	3	50	3
tRP	RAS# precharge time	40		50
tRAS	RAS# low pulse width	60	10K	70	10K
tRASP	RAS# low pulse width (Fast-Page Mode)	60	200K	70	200K
tRSH	RAS# hold time after CAS# low	10		20
tCSH	CAS# hold time after RAS# low	60		70
tCAS	CAS# low pulse width	15	10K	20	10K
tRCD	Delay time, RAS# low to CAS# low	20	45	20	50	9
tRAD	Column  address delay time from RAS# low	15	30	15	35	10
tCRP	CAS# to RAS# precharge time	5		5
tCP	CAS# precharge time (Fast-Page Mode)	10		10
tASR	Row address setup time before RAS# low	0		0
tRAH	Row address hold time after RAS# low	10		10
tASC	Column address setup time before CAS# low	0		0
tCAH	Column address hold time after CAS# low	10		15
tAR	Column address hold time referenced to RAS# low	45		55
tRAL	Column address to RAS# lead time	30		35
tRCS	Read command setup time before CAS# low	0		0
tRCH	Read command hold time after CAS# high	0		0		6
tRRH	Read command hold time after RAS# high	0		0		6
tWCS	Write command setup time before CAS# low	0		0		8
tWCH	Write command hold time after CAS# low	10		15
tWCR	Write command hold time referenced to RAS# low	45		55
tWP	Write command pulse width	10		15
tRWL	Write command to RAS# low lead time	15		20
tCWL	Write command to CAS# low lead time	15		20
tDS	Data setup time before CAS#	0		0		7
tDH	Data hold time after CAS# low	10		15		7
tDHR	Data hold referenced to RAS#	45		55
tCSR	CAS# setup time (CAS# before RAS# refresh)	10		10
tCHR	CAS# hold time  (CAS# before RAS# refresh)	10		15
tRPC	RAS# to CAS# precharge time	5		5
tWRP	Write Command setup time	10		10
tWRH	Write Command hold time	10		10
Notes below are for Table 8.

Notes:

  1.	An initial pause of 200µs is required after power-up followed by 8 RAS# only refresh 	cycles before proper device operation is achieved.  In case of using internal refresh 	counter, a minimum of 8 CAS# before RAS# refresh cycles instead of 8 RAS# only 	refresh cycles are required.

2.	AC measurements assume tT  = 5 ns

3.	VIH(min) and VIL(max) are reference levels for measuring timing of input signals.  	Also,  transitions times are measured between VIH(min) and VIL(max).

4.	Measured with a load circuit equivalent to 2 TTL loads and 100pF.

5.	tOFF(max) defines the time at which the output achieves the open circuit condition 	and is not referenced to VOH or VOL.

6.	Either tRCH or tRRH must be satisfied for read cycle.

7.	These parameters are referenced to CAS# leading edge in early write cycles and to 	WRITE leading edge in Read-Modify-Write cycles.

8.	tWCS is not a restrictive operating parameter.  It is included in this specification as an 	electrical characteristic only.  If  tWCS ≥ tWCS (min.), the cycle is an early write cycle and  	the data out pin will remain open circuit (high impedance) through the entire cycle.

9.	Operation within tRCD(max) insures tRAC(max) can be met.  tRCD(max) is	 	specified as a reference point only.  If tRCD is greater than specified tRCD(max), 	access time is controlled by tCAC.

10.	Operation within tRAD(max) insures tRAC(max) can be met.  tRAD(max) is specified as a 	reference point only.  If tRAD is greater than tRAD(max), access time is controlled by tAA.


ALTServer Help - SIMM Qualification Specification - 5.0 ENVIRONMENTAL REQUIREMENTS:
5.0	ENVIRONMENTAL REQUIREMENTS:

5.1	Operating Temperature Range:  0°C  to +70°C.

5.2	Storage Temperature:  -55°C  to  +125°C.


ALTServer Help - SIMM Qualification Specification - 6.0  SPECIAL REQUIREMENTS:
6.0 	SPECIAL REQUIREMENTS:

6.1	Packaging

All SIMMs are to be packed for shipping to prevent ESD and mechanical damage.

6.2	Marking

All SIMMs are to have the manufacturers P/N and UL Recognition markings visible on production level product.


ALTServer Help - SIMM Qualification Specification - 7.0 REFERENCE DATA:
7.0	REFERENCE DATA:

7.1	Waveforms.

7.1.1	FIGURE 2.  Read Cycle.

7.1.2	FIGURE 3.  Early Write Cycle.

7.1.3	FIGURE 4.  Fast Page Mode Read Cycle.

7.1.4	FIGURE 5.  Fast Page Mode Write Cycle (Early Write).

7.1.5	FIGURE 6.  RAS-Only Refresh Cycle.


Asynchronous Cache Module Qualification Specification

Revision 02

April 19,1995

Intel Document Number:  635058

Related Topics:

1.0 SCOPE:

2.0 APPLICABLE DOCUMENTS:

3.0 MECHANICAL REQUIREMENTS:

4.0 ELECTRICAL REQUIREMENTS:

5.0 ENVIRONMENTAL REQUIREMENTS:

6.0  SPECIAL REQUIREMENTS:

7.0 REFERENCE DATA: 7.1 Waveforms


ALTServer Help - Asynchronous Cache Module Qualification Specification - 1.0 SCOPE:
1.0	SCOPE:

This document establishes the detailed requirements which the manufacturer must guarantee for a SRAM (static random access memory) module, for use in ALTSERVER platforms.


ALTServer Help - Asynchronous Cache Module Qualification Specification - 2.0 APPLICABLE DOCUMENTS:
2.0	APPLICABLE DOCUMENTS:

The latest revision in effect of the following document:

Technical Product Summary -- ALTSERVER Platforms:  Order No. 634116


ALTServer Help - Asynchronous Cache Module Qualification Specification - 3.0 MECHANICAL REQUIREMENTS:
3.0	MECHANICAL REQUIREMENTS:

3.1	SRAM Module

3.1.1	Substrate - FR4 Epoxy laminate clad with minimum 1 ounce copper for internal and external layers.

3.1.2	Etch Line and Card Edge Contact:  Tin/Lead only.

3.1.3	Plated Through Holes:  After plating, holes shall have a minimum arithmetic average of .001 inch of copper with a minimum of .0006 inch.

3.1.4	Clock -all clock lines should drive only one load and should have a trace length of 3.9 inches

0.1 inches.

3.1.5	Data -all data and parity lines should be routed as short as possible, with a maximum net length of

1.5 inches.

3.1.6	Address -all address lines should be routed as short as possible, with a maximum length from

connector pin to IC input of 3.8 inches.

All other lines should be routed as short as possible.

3.2	Safety

3.2.1	UL Rating:  Printed wiring board to have a flammability rating of 94V-0.  Markings to include UL traceability requirements per UL Recognized Component Directory.


ALTServer Help - Asynchronous Cache Module Qualification Specification - 4.0 ELECTRICAL REQUIREMENTS:
4.0	ELECTRICAL REQUIREMENTS:

4.1	SRAM Configuration Definitions

This section refers to ALTSERVER SRAM configurations.  The ALTServer L2 cache can supports 256KByte configuration using  standard asynchronous SRAM modules. The cache uses a write-back write policy. Write-through mode is not supported.

4.1.1	Support Features

The ALTSERVER architecture uses the 82434NX (PCMC) PCI Cache and Memory Controller which supports a direct mapped secondary cache. The PCMC contains 4096 tags. Each tag represents a sector in the cache. If the cache is 256KByte, each sector contains two cache lines. Valid and Modified bits are kept on a per line basis.

4.1.2    SRAM Address Translation

Host address lines HA[18:7] are driven through an external latch to form the upper SRAM address lines, 	CA[18:7]. CA[6:3] are driven from  the PCMC. For further information please refer to the 82434NX  PCMC 	databook (order number: 290478-003).

4.1.3    Cycle Latency Summary

 Table 1  Summarize clock latencies for CPU memory cycles which hit in the secondary cache.

TABLE 1. Secondary Cache Latencies with Standard Asynchronous SRAM

Cycle Type	60 and  66 MHz	50 MHz           (1 Wait-State)
Burst Read	3-2-2-2	3-2-2-2
Burst Write	4-2-2-2	4-2-2-2
Single Read	3	3
Single Write	4	4
Pipelined Back-to-back Burst Reads	3-2-2-2-3-2-2-2	3-2-2-2-3-2-2-2
Burst Read Followed by Pipelined Write	3-2-2-2-4	3-2-2-2-4
Note: The 60 and 66 Mhz asynchronous SRAM latencies require 17 and 15ns SRAM modules, respectively. The 82434NX PCMC supports two sets of  timings with asynchronous SRAM @ 50MHz. The 50MHz  (1 wait-state) timings require 20ns SRAM modules.

4.1.4   Standard SRAM Cache Cycles

At 60 and 66 MHz, the timing of the second level cache (L2) interface with standard asynchronous SRAMs is identical to the timing in the 82430 PCIset. When programmed for 3-2-2-2 reads and 4-2-2-2 writes, the cycles are the same as in the 82430 PCIset. For further information, please refer to Table 1.

4.1.4   Second Level Cache Stand-By

With  standard SRAM secondary caches, a halt or stop grant special cycle from the CPU causes the PCMC to negate CCS[1:0]#, deselecting the SRAMs and placing them in a low power stand-by mode. When the cache is in stand-by mode, the first bus cycle from the CPU brings the cache out of stand-by and into active mode, enabling the SRAMs  to service the cycle in the case of a hit to the cache. The PCMC asserts CCS[1:0]# after a propagation delay from the falling edge of ADS#. CCS[1:0]# are then left asserted until the next halt or stop grant  special cycle occurs. When exiting the powerdown state, the PCMC ignores the Secondary Cache Lead-off Wait States bit and executes a 3-2-2-2 read and 4-2-2-2  write in order to allow the SRAMs time to power up. In the case of a read cycle, COE[1:0]# are asserted in clock two as in the case of ordinary read cycles.

4.1.4	TABLE 3.  Pin Connection

1	GND	28	D26	55	A6-0	82	D63	109	D25	136	A7
2	D62	29	D24	56	A8	83	Vcc5	110	GND	137	GND
3	Vcc3	30	GND	57	GND	84	D61	111	DP3	138	A9
4	D60	31	DP2	58	A10	85	Vcc5	112	D23	139	A11
5	Vcc3	32	D22	59	A12	86	D59	113	D21	140	A13
6	D58	33	D20	60	A14	87	D57	114	Vcc5	141	A15
7	D56	34	Vcc3	61	A16	88	GND	115	D19	142	A17
8	GND	35	D18	62	A18	89	DP7	116	GND	143	GND
9	DP6	36	GND	63	GND	90	D55	117	D17	144	ALE
10	D54	37	D16	64	PD0	91	D53	118	VCC5	145	PD1
11	D52	38	Vcc3	65	PD2	92	D51	119	D15	146	CLK0
12	D50	39	D14	66	CLK1	93	GND	120	D13	147	CLK2
13	GND	40	D12	67	CLK3	94	D49	121	GND	148	GND
14	D48	41	GND	68	GND	95	D47	122	D11	149	WE7#
15	D46	42	D10	69	WE6#	96	D45	123	Vcc5	150	WE5#
16	D44	43	VCC3	70	WE4#	97	D43	124	D9	151	WE3#
17	D42	44	D8	71	WE2#	98	GND	125	DP1	152	WE1#
18	GND	45	DP0	72	WE0#	99	D41	126	Vcc5	153	GND
19	D40	46	Vcc3	73	GND	100	DP5	127	D7	154	ADSC1#
20	DP4	47	D6	74	ADSC0#	101	D39	128	D5	155	CE1#
21	D38	48	D4	75	CE0#	102	D37	129	D3	156	ADV1#
22	D36	49	D2	76	ADV0#	103	D35	130	D1	157	OE1#
23	D34	50	D0	77	OE0#	104	GND	131	GND	158	Vcc5
24	GND	51	GND	78	Vcc3	105	D33	132	A3-1	159	ADSP1#
25	D32	52	A3-0	79	ADSP0#	106	D31	133	A4-1	160	GND
26	D30	53	A4-0	80	GND	107	D29	134	A5-1
27	D28	54	A5-0	81	GND	108	D27	135	A6-1
4.1.5	TABLE 4.  Pin Names

SYM	PARAMETER
CA3 to CA18	CACHE ADDRESS INPUTS
ALE	ADDRESS LATCH ENABLE INPUT
D0 to D63	DATA INPUTS/OUTPUTS
DP0-DP7	PARITY INPUTS/OUTPUTS
CE0#-CE1#	CHIP ENABLE INPUTS
WE0#-WE7#	BYTE WRITE ENABLE INPUTS
OE0#-OE1#	OUTPUT ENABLE INPUTS
ADSP0#-ADSP1#	ADDRESS STATUS PROCESSOR INPUTS
ADSC0#-ADSC1#	ADDRESS STATUS CACHE CONTROLLER INPUTS
ADV0#-ADV1#	BURST ADDRESS ADVANCE INPUTS
CLK0-CLK3	CLOCK INPUTS
PD0-PD2	PRESENCE DETECT PINS
GND	GROUND
Vcc3	POWER SUPPLY FOR ASYNCHRONOUS SRAMs ONLY
Vcc5	POWER SUPPLY FOR BURST CACHE SRAMs ONLY
NC	NO CONNECTION
4.1.6       TABLE 5.  Present Detect Pins

PD2	PD1	PD0	Type	Size
N.C.	N.C.	N.C.	-	-
N.C.	N.C.	GND	-	-
N.C.	GND	N.C.	Asynch	256KB
N.C.	GND	GND	-	-
GND	N.C.	N.C.	-	-
GND	N.C.	GND	-	-
GND	GND	N.C.	Burst	256KB
GND	GND	GND	Burst	512KB
4.1.7	TABLE 6.  Absolute Maximum Ratings

SYM	PARAMETER	RATINGS
Vterm	Terminal Voltage with Respect to GND	-0.5V to Vcc + 0.5
Io	DC Output Current	50mA
Ta	Operation Temperature	0 to +70C
Tstg	Storage Temperature	-55 to 125°C
4.1.8       TABLE 7.  Recommended Operating Conditions

SYM	PARAMETER	MIN	MAX
Vcc3	SUPPLY VOLTAGE	3.0 V	3.6V
Vih	INPUT HIGH VOLTAGE	2.2V	Vcc + 0.3V
Vil	INPUT LOW VOLTAGE	-0.5V	0.8V
GND	SUPPLY VOLTAGE	0 V	0 V
4.1.9	TABLE 8.  DC Electrical Characteristics, Ta = 0°C to +70°C, Vcc3=3.3V10%

SYM	PARAMETER	TEST CONDITIONS	STANDARD
			MIN	MAX
VOH	HIGH LEVEL OUTPUT VOLTAGE	IOH=-4mA , Vcc = Min	2.4V	__
VOL	LOW LEVEL OUTPUT VOLTAGE	IOL=8mA , Vcc = Min	__	0.4V
|ILO|	OUTPUT LEAKAGE CURRENT	Vout = 0V to Vcc, Vcc = Max	__	5µA
|ILI|	INPUT LEAKAGE CURRENT  (ADDRESS)	Vcc = Max,                            Vin = GND to Vcc	__	20µA
|ILI|	INPUT LEAKAGE CURRENT (CE#, OE#, CONTROL)	Vcc = Max,                            Vin = GND to Vcc	__	10µA
|ILI|	INPUT LEAKAGE CURRENT (WE#, CLK)	Vcc = Max,                            Vin = GND to Vcc	__	5µA
Icc	OPERATION POWER SUPPLY CURRENT	Vcc = Max, CE#  Vil, f = fMax, Outputs Open	__	850 mA
ISB	STANDBY POWER SUPPLY CURRENT	Vcc = Max, CE#  Vih, f = fMax *, Outputs Open	__	120 mA
ISB1	FULL STANDBY POWER SUPPLY CURRENT	Vcc = Max, CE#  Vcc - 0.2V f = 0, Vin  0.2V or Vin  Vcc - 0.2V, Outputs Open	__	10 mA
4.1.10	TABLE 9.  Capacitance   Ta= +25°C, f =1mhz, unless otherwise noted.

SYM	PARAMETER	STANDARD
		MAX
Cin	Input Capacitance,  Address Inputs	45/10pF
Cin	Input Capacitance, (CE#, OE# , and Control)	25pF
Cin	Input Capacitance (WE#, Clk)	8pF
Ci/o	Input/output Capacitance	10pF
 4.1.11	TABLE 10.  Timing Requirements.  Ta=0°C to +70°C, Vcc= 3.3V 0.3V.  All units in nanoseconds unless otherwise noted.

SYM	PARAMETER	STANDARD 66ns	STANDARD 60ns	STANDARD 50ns
		MIN	MAX	MIN	MAX	MIN	MAX
tRC	READ CYCLE TIME	15		17		20
tAA	ADDRESS ACCESS TIME		15				20
tACS	CHIP SELECT ACCESS TIME		15				20
tCLZ	CHIP SELECT TO OUTPUT IN LOW-Z	5				5
tCHZ	CHIP SELECT TO OUTPUT IN HIGH-Z	0	9			0	10
tOE	OUTPUT ENABLE TO OUTPUT VALID		7				8
tOLZ	OUTPUT ENABLE TO OUTPUT IN LOW-Z	3				3
tOHZ	OUTPUT DISABLE TO OUTPUT IN HIGH-Z	2	7			2	8
tOH	OUTPUT HOLD FROM ADDRESS CHANGE	3				3
tWC	WRITE CYCLE TIME	15				20
tAW	ADDRESS VALID TO END-OF-WRITE	10				15
tCW	CHIP SELECT TO END-OF-WRITE	10				15
tAS	ADDRESS SET-UP TIME	0				0
tWP	WRITE PULSE WIDTH	10				15
tWR	WRITE RECOVERY TIME	0				0
tDW	DATA TO WRITE TIME OVERLAP	7				8
tDH	DATA HOLD FROM WRITE TIME	0				0
tOW	OUTPUT ACTIVE FROM END-OF-WRITE	4				4
tWHZ	WRITE ENABLE TO OUTPUT IN HIGH-Z	1	9			1	10


ALTServer Help - Asynchronous Cache Module Qualification Specification - 5.0 ENVIRONMENTAL REQUIREMENTS:
5.0	ENVIRONMENTAL REQUIREMENTS:

5.1	Operating Temperature Range:  0°C  to +70°C.

5.2	Storage Temperature:  -55°C  to  +125°C.


ALTServer Help - Asynchronous Cache Module Qualification Specification - 6.0  SPECIAL REQUIREMENTS:
6.0 	SPECIAL REQUIREMENTS:

6.1	Packaging

All SRAMs are to be packed for shipping to prevent ESD and mechanical damage.

6.2	Marking

All SRAMs are to have the manufacturers P/N and UL Recognition markings visible on production level product.


7.0	REFERENCE DATA: 7.1	Waveforms


BURST Cache Module Qualification Specification

Revision 02

April 19,1995

Intel Document Number:  635057

Related Topics:

1.0 SCOPE:

2.0 APPLICABLE DOCUMENTS:

3.0 MECHANICAL REQUIREMENTS:

4.0 ELECTRICAL REQUIREMENTS:

5.0 ENVIRONMENTAL REQUIREMENTS:

6.0  SPECIAL REQUIREMENTS:

7.0 REFERENCE DATA:


ALTServer Help - BURST Cache Module Qualification Specification - 1.0 SCOPE:
1.0	SCOPE:

This document establishes the detailed requirements which the manufacturer must guarantee for a SRAM (static random access memory) module, for use in ALTSERVER platforms.


ALTServer Help - BURST Cache Module Qualification Specification - 2.0 APPLICABLE DOCUMENTS:
2.0	APPLICABLE DOCUMENTS:

The latest revision in effect of the following document:

Technical Product Summary -- ALTSERVER Platforms:  Order No. 634116


ALTServer Help - BURST Cache Module Qualification Specification - 3.0 MECHANICAL REQUIREMENTS:
3.0	MECHANICAL REQUIREMENTS:

3.1	SRAM module

3.1.1	Substrate - FR4 Epoxy laminate clad with minimum 1 ounce copper for internal and external layers.

3.1.2	Etch Line and Card Edge Contact:  Tin/Lead only.

3.1.3	Plated Through Holes:  After plating, holes shall have a minimum arithmetic average of .001 inch of copper with a minimum of .0006 inch.

3.1.4	Clock -all clock lines should drive only one load and should have a trace length of 3.9 inches   0.1 inches.

3.1.5	Data -all data and parity lines should be routed as short as possible, with a maximum net length of 1.5 inches.

3.1.6	Address -all address lines should be routed as short as possible, with a maximum length from connector pin to IC input of 3.8 inches.

All other lines should be routed as short as possible.

3.2	Safety

3.2.1	UL Rating:  Printed wiring board to have a flammability rating of 94V-0.  Markings to include UL traceability requirements per UL Recognized Component Directory.


ALTServer Help - BURST Cache Module Qualification Specification - 4.0 ELECTRICAL REQUIREMENTS:
4.0	ELECTRICAL REQUIREMENTS:

4.1	SRAM Configuration Definitions

This section refers to ALTSERVER SRAM configurations.  The ALTServer L2 cache can support either  256KByte or 512kbyte configuration using synchronous burst SRAM modules. The cache uses a write-back write policy. Write-through mode is not supported.

4.1.1	Support Features

The ALTSERVER architecture uses the 82434NX (PCMC) PCI Cache and Memory Controller which supports a direct mapped secondary cache. The PCMC contains 4096 tags. Each tag represents a sector in the cache. If the cache is 512KBytes, each sector contains four cache lines. If the cache is 256KBytes, each sector contains two cache lines. Valid and Modified bits are kept on a per line basis.

4.1.2    SRAM Address Translation

Host address lines HA[18:3] are connected directly to the SRAM module address lines, A[15:0]. ADS# from the CPU is connected to ADSP# on the SRAMs. For further information, please refer to the 82434NX  PCMC databook (order number: 290478-003).

4.1.3    Cycle Latency Summary

 Table 1 Summarize clock latencies for CPU memory cycles which hit in the secondary cache.

TABLE 1.  Secondary Cache Latencies with Synchronous Burst SRAM

Cycle Type	60 and  66 MHz
Burst Read	3-1-1-1
Burst Write	3-1-1-1
Single Read	3
Single Write	3
Pipelined Back-to-back Burst Reads	3-1-1-1-1-1-1-1
Burst Read Followed by Pipelined Write	3-1-1-1-2

Note: The burst SRAMs speeds for 66, 60 and 50MHz operation are 8, 10, and 13ns clock-to-output valid into          a 0pF test load.

4.1.4    Burst SRAM Cache Cycle

During cache line fills, the CCS1# signal is negated by the PCMC to block any pipeline ADS#s from the CPU before the line fill is completed. On a cache miss, CCS1# is negated after NA# is asserted to prevent the SRAMs from latching a new pipelined address during a line fill. CCS1# is asserted after the last BRDY# of the burst line fill is completed.

4.1.5    Burst SRAM Write-Back Cycles

Since the CAA[6:3] and CAB[6:3] lines are not used, the write-back address must be driven on the host address lines. The PCMC asserts AHOLD  clock three, causing the CPU to tri-state the host address lines. The PCMC then drives the cache address of the de-allocated line onto the host address lines. The PCMC asserts CADS[1:0]# causing the SRAMs to latch the write back address. The PCMC posts the line from the SRAMs to the LBX CPU-to-Memory Write Buffer. In this case, only one line in the addressed sector is modified and is written back. The PCMC negates AHOLD, allowing the CPU to drive the original address on the address lines. The PCMC then asserts CADS[1:0]# causing the SRAMs to latch the original cycle address. The PCMC changes the HIG[4:0] lines from PCMCWQ to CMR allowing the read data from DRAM to be driven onto the host data lines. For further information, please refer to the 82434NX  PCMC databook (order number: 290478-003).

4.1.6    Second level Caches Stand-By

When the PCMC detects a halt or stop grant special cycle from the CPU, it first places the second level caches into the low power stand-by mode by deselecting the SRAMs and then generates a halt or stop grant special cycle on PCI.

With Burst SRAM secondary cache, a halt or stop grant special cycle from the CPU causes the PCMC to negate CCS# and assert CADS[1:0]#, deselecting the SRAMs, placing them in a low power stand-by mode. CSS# is then asserted and is left asserted by the PCMC. Thus, when the first cycle is  driven from the CPU, the SRAMs sample ADSP# and CS# active, placing them in active mode and initiating the first access.

4.1.7	TABLE 2.  Pin Connection

1	GND	28	D26	55	A6-0	82	D63	109	D25	136	A7
2	D62	29	D24	56	A8	83	Vcc5	110	GND	137	GND
3	Vcc3	30	GND	57	GND	84	D61	111	DP3	138	A9
4	D60	31	DP2	58	A10	85	Vcc5	112	D23	139	A11
5	Vcc3	32	D22	59	A12	86	D59	113	D21	140	A13
6	D58	33	D20	60	A14	87	D57	114	Vcc5	141	A15
7	D56	34	Vcc3	61	A16	88	GND	115	D19	142	A17
8	GND	35	D18	62	A18	89	DP7	116	GND	143	GND
9	DP6	36	GND	63	GND	90	D55	117	D17	144	ALE
10	D54	37	D16	64	PD0	91	D53	118	Vcc5	145	PD1
11	D52	38	Vcc3	65	PD2	92	D51	119	D15	146	CLK0
12	D50	39	D14	66	CLK1	93	GND	120	D13	147	CLK2
13	GND	40	D12	67	CLK3	94	D49	121	GND	148	GND
14	D48	41	GND	68	GND	95	D47	122	D11	149	WE7#
15	D46	42	D10	69	WE6#	96	D45	123	Vcc5	150	WE5#
16	D44	43	Vcc3	70	WE4#	97	D43	124	D9	151	WE3#
17	D42	44	D8	71	WE2#	98	GND	125	DP1	152	WE1#
18	GND	45	DP0	72	WE0#	99	D41	126	Vcc5	153	GND
19	D40	46	Vcc3	73	GND	100	DP5	127	D7	154	ADSC1#
20	DP4	47	D6	74	ADSC0#	101	D39	128	D5	155	CE1#
21	D38	48	D4	75	CE0#	102	D37	129	D3	156	ADV1#
22	D36	49	D2	76	ADV0#	103	D35	130	D1	157	OE1#
23	D34	50	D0	77	OE0#	104	GND	131	GND	158	Vcc5
24	GND	51	GND	78	Vcc3	105	D33	132	A3-1	159	ADSP1#
25	D32	52	A3-0	79	ADSP0#	106	D31	133	A4-1	160	GND
26	D30	53	A4-0	80	GND	107	D29	134	A5-1
27	D28	54	A5-0	81	GND	108	D27	135	A6-1
4.1.8	TABLE 3.  Pin Names

SYM	PARAMETER
CA3 to CA18	CACHE ADDRESS INPUTS
ALE	ADDRESS LATCH ENABLE INPUT
D0 to D63	DATA INPUTS/OUTPUTS
DP0-DP7	PARITY INPUTS/OUTPUTS
CE0#-CE1#	CHIP ENABLE INPUTS
WE0#-WE7#	BYTE WRITE ENABLE INPUTS
OE0#-OE1#	OUTPUT ENABLE INPUTS
ADSP0#-ADSP1#	ADDRESS STATUS PROCESSOR INPUTS
ADSC0#-ADSC1#	ADDRESS STATUS CACHE CONTROLLER INPUTS
ADV0#-ADV1#	BURST ADDRESS ADVANCE INPUTS
CLK0-CLK3	CLOCK INPUTS
PD0-PD2	PRESENCE DETECT PINS
GND	GROUND
Vcc3	POWER SUPPLY FOR ASYNCHRONOUS SRAMs ONLY
Vcc5	POWER SUPPLY FOR BURST CACHE SRAMs ONLY
NC	NO CONNECTION
4.1.9       TABLE 4.  Present Detect Pins

PD2	PD1	PD0	Type	Size
N.C.	N.C.	N.C.	-	-
N.C.	N.C.	GND	-	-
N.C.	GND	N.C.	Asynch	256KB
N.C.	GND	GND	-	-
GND	N.C.	N.C.	-	-
GND	N.C.	GND	-	-
GND	GND	N.C.	Burst	256KB
GND	GND	GND	Burst	512KB
4.1.10	TABLE 5.  Absolute Maximum Ratings

SYM	PARAMETER	RATINGS
Vterm	Terminal Voltage with Respect to GND	-0.5V to 7V
Io	DC Output Current	50mA
Ta	Operation Temperature	0 to +70C
Tstg	Storage Temperature	-55 to 125°C
4.1.11       TABLE 6.  Recommended Operating Conditions, Ta = 0°C to +70°C

SYM	PARAMETER	MIN	MAX
Vcc5	SUPPLY VOLTAGE	4.75V	5.25V
Vcc3	SUPPLY VOLTAGE	3.0 V	3.6 V
GND	SUPPLY VOLTAGE	0 V	0 V
VIH	HIGH LEVEL INPUT VOLTAGE	2.2V	Vcc + 0.3
VIL	LOW LEVEL INPUT VOLTAGE	-0.5V *	0.8V
Note: Vil = -1.0 V for pulse width less than 5ns, once per cycle.

4.1.12	TABLE 7.  DC Electrical Characteristics, Ta = 0°C to +70°C,

Vcc5=5V±5%

SYM	PARAMETER	TEST CONDITIONS	STANDARD
			MIN	MAX
VOH	HIGH LEVEL OUTPUT VOLTAGE	IOH=-4mA , Vcc = Min	2.4V	__
VOL	LOW LEVEL OUTPUT VOLTAGE	IOL=8mA , Vcc = Min	__	0.4V
ILO	OUTPUT LEAKAGE CURRENT	Vout = 0V to Vcc, Vcc = Max	__	5µA
|ILI|	INPUT LEAKAGE CURRENT  (ADDRESS)	Vcc = Max,                            Vin = GND to Vcc	__	40µA
|ILI|	INPUT LEAKAGE CURRENT (CE#,OE#, CONTROL)	Vcc = Max,                                         Vin = GND to Vcc	__	20A
|ILI|	INPUT LEAKAGE CURRENT (WE# , CLK)	Vcc = Max, Vin = GND to Vcc	__	5A
Icc	OPERATION POWER SUPPLY CURRENT	Vcc = Max, CE#  Vil, f = fMax, Outputs Open	__	1000 mA
ISB	STANDBY POWER SUPPLY CURRENT	Vcc = Max, CE#  Vih, f = fMax, Outputs Open	__	400  mA
ISB1	FULL STANDBY POWER SUPPLY CURRENT	Vcc = Max, CE#  Vcc - 0.2V f = 0, Vin  0.2V or Vin  Vcc - 0.2V, Outputs Open	__	180 mA
4.1.13	TABLE 8.  Capacitance   Ta= +25°C,  f =1MHz,

unless otherwise noted.

SYM	PARAMETER	STANDARD
		MAX
Cin	Input Capacitance,  Address Inputs	25pF
Cin	Input Capacitance, (CE#, OE# , and Control)	15pF
Cin	Input Capacitance (WE#, Clk)	8pF
Ci/o	Input/output Capacitance	10pF
4.1.14	TABLE 9.  Timing Requirements (1,2,3,6).  Ta=0°C to +70°C, Vcc=5V ±5%.                    	All units in nanoseconds unless otherwise noted.

   4.1.15       TABLE 10.  AC Test Conditions.

INPUT PULSE LEVELS	GND to 3.0V
INPUT RISE/FALL TIMES	3ns
INPUT TIMING REFERENCE LEVELS	1.5V
OUTPUT TIMING REFERENCE LEVELS	1.5V
AC TEST LOAD	See Figure 5


ALTServer Help - BURST Cache Module Qualification Specification - 5.0 ENVIRONMENTAL REQUIREMENTS:
5.0	ENVIRONMENTAL REQUIREMENTS:

   5.1	Operating Temperature Range:  0°C  to +70°C.

  5.2	Storage Temperature:  -55°C  to  +125°C.


ALTServer Help - BURST Cache Module Qualification Specification - 6.0  SPECIAL REQUIREMENTS:
6.0 	SPECIAL REQUIREMENTS:

    6.1	Packaging

     All SRAMs are to be packed for shipping to prevent ESD and mechanical damage.

    6.2	Marking

     All SRAMs are to have the manufacturers P/N and UL Recognition markings visible on production level 	     product.


ALTServer Help - BURST Cache Module Qualification Specification - 7.0 REFERENCE DATA:
7.0	REFERENCE DATA:

    7.1	Waveforms.