FT1200 (Crinkle) Facts, Tips & Tricks (Rev 06)
Part 1 - Facts
Part 2 - Tips and Tricks
Crinkle is a new release of the FT1200 entry level server. It combines the Tyson Chassis with the Intel DK440LX motherboard. The DK440LX motherboard is based on the Intel 440LX chipset with Intels PIIX4 ISA bridge and peripheral controller. No video controller is on the motherboard. The motherboard also includes Pro/100B 10/100 Mbps Ethernet controller, Crystal 4236B audio device and LM79 management controller. The base motherboard is ATX form factor and contains 1 AGP (Half length) slot for Advanced Graphics Port video cards, 3 PCI (Full length) slots, 1 PCI (Full length) / ISA (Full length) shared slot and 1 ISA (Full length) slot. Power is supplied from the PSU to the motherboard via ATX and auxiliary power connectors.
This version of the product offers increased price performance over the existing FT1200 product. The performance baseline is at least 10% greater than the current baseline product but can be scaled to around 4 times the performance of the current product for very little incremental cost. This scalability is achieved through use of multiple Slot 1 Pentium II processors. Memory capacity has also increased to 512MB and the new system offers extensive I/O expandability by virtue of many on board I/O devices, thus freeing up the PCI and ISA slots in the system.
Ideally the specification of the chassis would be extended to include an optional Hot Plug RAID disk subsystem and redundant power, but due to the resource constraints placed on us at the moment, the chassis remains the same base specification as the current FT1200.
The system management software will be based on LDSM Version 3 and will enable servers and clients alike to be managed though a common "console". Wbem may be available on the product at first release, and this will permit management of the server through standard Web browsers. An emergency management card will be available as an option to permit out of band system management. Other software products may be bundled with the server in addition to optional operating system pre-installs. The software products will range from a bootable CD containing diagnostics; manuals and set up utilities, to Internet enabled products such as Insight Web services and remote system assistance.
This motherboard has a number of feature differences to the PCL6000 motherboard that it replaces and these differences are summarised as follows:
This means the slot utilisation is better (more ISA slots free) on an FT1200 Crinkle, than on a FT1200 PCL6000. The Video is now via the AGP port, SCSI is on board, along with LAN and hardware instrumentation.
System Management Application.
System Inventory reporting via:
System fault detection and reporting via:
Enhanced system security via:
System Power Management through:
Improved Server Uptime through:
Out Of Band Features - supplied via Intel SMM (Hobbes and/or Bonsai card).
Product Configurations (UK).
Accessories (To be shipped in system carton)
Figure 1. Motherboard Layout
Figure 2. Back Panel Connectors
J7E1 Maintenance Mode.
This mode is for normal computer booting and operations. Connect pins 1 and 2 with a jumper on the configuration header (J7E1) to enable the mode. The BIOS uses the current bus/processor frequency ratio, configuration information, and passwords to boot the computer. Access to the Set-up program can be restricted using an administrative or user password. In normal mode, the BIOS attempt an automatic recovery if the configuration information in flash memory is corrupted.
This mode is for configuring the processor speed and clearing passwords. Connect pins 2 and 3 with a jumper on the configuration header (J7E1) to enable the mode. In this mode, Set-up automatically executes after the POST runs, and no password is required. Set-up provides the Maintenance menu with options for setting the processor speed and clearing passwords. All other Set-up screens are available. Configure mode uses the default BIOS settings for booting, not the current user or administrative settings. The default settings include the lowest bus/processor frequency ratio the processor supports. When the computer is rebooted, Set-up uses the original user and administrative settings with the exception of the options that were changed. For the configuration changes to take effect after exiting the Set-up program, power down the computer, set the configuration jumper to normal mode (see Section 0), and boot the computer. In configure mode, the BIOS attempts an automatic recovery if the configuration information flash memory is corrupted.
This mode is for upgrading the BIOS or recovering BIOS data. Remove the jumper (no pins connected) from the configuration header (J7E1) to enable this mode. After the computer is powered-on, the BIOS attempts to upgrade or recover the BIOS data from a diskette in the floppy drive. If the recovery fails with a diskette in the boot drive, a beep code indicates that the recovery failed. If a diskette is not in the boot drive, the BIOS attempts to run the POST, does not boot the operating system, and displays a message that the jumper is not properly installed. For the configuration changes to take effect after a successful recovery, power down the computer, set the configuration jumper to normal mode (see Section 0), and boot the computer.
J11A1: LAN SLP Jumper.
This jumper controls the functionality of the onboard LAN adapters ability to bring the system out of standby mode, into full power-up.
By default, pins 1 & 2 should be fitted with a jumper to enable this feature. Please note that the jumper is numbered upside down.
Peripheral (LED / Switches etc) connections to motherboard.
Various front panel LED's, switches and other internal connections may need to be made to the DK440 motherboard. Below are tables containing the pin-out information for these connections.
J12E1 (Single row): Front Panel Connections).
J12D1: Sleep / Power LED connection (P/N 16219331).
J11B1: LED connections.
J1F1: Internal Audio In Line, no connect.
J12D1: Sleep / Power LED connection (P/N 16219331).
J1E1: Internal CD-ROM Audio In.
J0A1: Chassis Security Header.
MIDI / GAMES port J2E2
All fans follow the same pin out as indicated, position of fans is additional detailed in following table
Only one card is intended for use at first production, a modem that should be fitted in the first slot on the right (as viewed from the front).
Motherboard IRQs and DMA channels
Base Input/Output (I/O) Port Addresses
The following table lists addresses used by components on the motherboard. Any ports between 100h and 3FFh that are not listed may be used by an expansion card.
The base IRQ for the Adaptec and NetWare need to be determined and added to the table.
PCI IRQ Allocation.
This section describes interrupt sharing and how the interrupt signals are connected between the PCI expansion slots and onboard PCI devices. The PCI specification specifies how interrupts can be shared between devices attached to the PCI bus. In most cases, the small amount of latency added by interrupt sharing does not affect the operation or throughput of the devices. In some special cases where maximum performance is needed from a device, a PCI device should not share an interrupt with other PCI devices. Use the following information to avoid sharing an interrupt with a PCI add-in card.
PCI devices are categorised as follows to specify their interrupt grouping:
The PIIX4 PCI-to-ISA bridge has four programmable interrupt request (PIRQ) input signals. Any PCI interrupt source (either onboard or from a PCI add-in card) connects to one of these PIRQ signals. Because there are only four signals, some PCI interrupt sources are mechanically tied together on the motherboard and therefore share the same interrupt. The PCI Interrupt Routing Map table below lists the PIRQ signals and shows how the signals are connected to the PCI expansion slots and to onboard PCI interrupt sources.
The order of cards in the PCI bus should follow the following table:
Based on the above configuration, additional cards in slots 4 or 5 will be allocated IRQ 11 or 15.
PCI Interrupt Routing Map.
For example, assume an add-in card has one interrupt (group INTA) into the fourth PCI slot. In this slot, an interrupt source from group INTA connects to the PIRQ2 signal, which is already connected to the onboard video and USB PCI sources. The add-in card shares an interrupt with these onboard interrupt sources.
Now, however, plug an add-in card that has one interrupt (group INTA) into the first PCI slot. Plug a second add-in card that has two interrupts (groups INTA and INTB) into the second PCI slot. INTA in the first slot is connected to signal PIRQA. INTA in the second slot is connected to signal PIRQB, and INTB is connected to signal PIRQC. With no other cards added, the three interrupt sources on the first two cards each have a PIRQ signal to themselves. Typically, they will not share an interrupt.
To Erase the CMOS remove the 3-volt Lithium battery (CR2032) and leave out for approximately 60 seconds before replacing. The CMOS will then require reconfiguring.
Entering BIOS Set-up.
Press "F2" on Boot or when prompted to enter these configuration screens.
BIOS Beep Codes
Whenever a recoverable error occurs during Power-On Self Test (POST), the BIOS displays an error message describing the problem. The BIOS also issues a beep code (one long tone followed by two short tones) during POST if the video configuration fails (no card installed or faulty) or if an external ROM module does not properly checksum to zero. An external ROM module (e.g. video BIOS) can also issue audible errors, usually consisting of one long tone followed by a series of short tones. For more information on the beep codes issued, check the documentation for that external device. There are several POST routines that issue a POST Terminal Error and shut down the system if they fail. Before shutting down the system, the terminal-error handler issues a beep code signifying the test point error, writes the error to I/O port 80h, attempts to initialise the video and writes the error in the upper left corner of the screen (using both mono and colour adapters).
If POST completes normally, the BIOS issues one short beep before passing control to the operating system.
BIOS Beep Codes Table:
This section lists the SETUP settings for a standard product. These settings are liable to change during the development of the software pre-install.
PCI/PNP ISA IRQ Resource Exclusion.
Note: The above is for information only and will be tailored differently for each machine and Operating System.
Two options are available for SCSI control; the onboard Adaptec 7895 Dual Channel SCSI to PCI controller or the AMI i960 series 431 Ultra SCSI to PCI Raid card. The Adaptec configuration uses two separate cables, one from each port to the front and rear drive bays (Part Numbers 16198431 & 16298531 respectively). The first SCSI channel (Ch A) will control the front mounted hard drives and the optional tape drive (via a 50 to 68 pin converter), whilst the second SCSI channel (Ch B) controls the rear drive pair. When using an AMI431 RAID card, a single SCSI cable (Part Number 16246531), which will connect all four hard drives and the optional tape drive (again via a converter).
Hard Disk Types.
The hard disk sub-system will consist of up to four IBM Draco 4Gb & 9Gb or IBM Capricorn 2Gb & 4Gb 68 pin Ultra Wide SCSI drives. These drives are located in the 2 lower front removable drive bays on 3.5" to 5.25" conversion plates. Two further drives are located in a carrier above the Power Supply and in front of the processors. Power connections are supplied directly from the PSU. They are configured on two wide SCSI buses where the front is Channel A and the rear is Channel B. The last physical drive (default position on the cable) is fitted to the lower front drive bay. The last physical drive on each bus is configured to terminate the bus.
IBM Draco 4Gb & 9Gb (DDRS-39130) Hard Disk Drive Jumper Settings for Crinkle systems.
68 and 80 pin model SCSI ID (address) pins.
*Shipping default ID for 80 pin drive
**Shipping default ID for 68 pin drive
IBM Capricorn (DCAS 34330) 4Gb Hard Disk Drive Jumper Settings for Crinkle systems.
68 and 80 pin model SCSI ID (address) pins.
*Shipping default ID for 80 pin drive
**Shipping default ID for 68 pin drive
Disable auto spin up (JP5)
This jumper controls how the drive starts when power is applied. If the jumper is NOT installed then the file will spin up automatically after power-on reset. If the jumper IS installed the file will NOT spin up unless the host system issues a 'START UNIT' command to the file.
SCSI terminator on (JP6)
When this jumpers is installed, the on-card SCSI bus terminator is enabled. There is no terminator on the 80-pin model
Unit attention disable (JP7)
When this jumper is installed the drive will not generate a unit attention following a power on reset (POR) or SCSI bus reset. Any pending unit attention conditions will also be cleared at POR or SCSI bus reset.
Enable TI-SDTR/Enable TI-SDTR/WDTR (JP8)
When the jumper is installed the drive will initiate synchronous data transfer spped negotiation (50,68 & 80 pin) and initiate wide data transfer request (68 & 80 pin) following a SCSI bus reset or power on event.
Auto start delay and delay start (JP9,JP10)
The auto start delay and delay start pins control when and how the drive can spin up, with the combination of auto spin up option (JP5).
When in auto spin up and start delay mode the drive start will be delayed by a period of time multiplied by its own SCSI address. If auto spin up is disabled, these jumpers will be ignored.
Disable SCSI parity (JP11)
When this jumper is installed, the drive's SCSI parity checking is disabled.
External activity (LED) pins (JP12)
The LED pins can be used to drive an external light emitting diode. Up to 8mA of sink current capability is provided. The LED anode must be tied to the current limited +5V source provided on pin # 1 of the option jumper block. The LED cathode is then connected to the pin # 2 to complete the circuit.
The default jumper setting at shipment is as follows.
SCSI signal connector
The SCSI signal connector is a 50 pin connector meeting the ANSI SCSI specification. The SCSI SCA-80 pin connector conforms to SFF 8046.It is intended that the hard disk drive should only be in electrical contact with the chassis of the system at a designated set of mounting holes. Other electrical contact may degrade error rate performance. As a result of this it is recommended that there should be no metal contact to the hard disk drive except at the mounting holes or the side rails into which the mounting holes are tapped.
NOTE: IBM Capricorn 4Gb Hard Disk Drives will now be shipped instead of the IBM 4Gb Draco due to cost and the lack of supply.
IPR4192 Processor speed / type display,
During POST there is no display of the processor type or speed. Failures of processors or incorrect speed settings are therefore possible.
Solution: A future BIOS will have this feature. Note DMI entries exist for these functions and can be checked using LDSM.
Adapter Card Issues.
IPR4434and 4435 AMI 431 and Tagged Command Queues
We are aware of problems with the TCQ protocol between AMI and 4G / 9G HDDs. These may cause hangs or failures of drives.
Solution: The default setting for the TCQ is currently disabled. This should not be enabled in the field until a new firmware has been released for the AMI card.
Microsoft NT Issues.
IPR4128 Installation of NT 4.0
If an automatic detection of devices is carried out during the installation of Windows NT 4.0 (either by CD boot or floppy boot) , the detection process will put the Adaptec 7895 into a state that cannot install the correct 7895 driver.
Solution: CD ROM installation cannot be carried out , and floppy installation must "SKIP" detection of devices. Then the 7895 driver can be loaded correctly using the Adaptec FMS rev03.
SCO Unix & UnixWare Issues.
IPR4209 UnixWare Installation
Installation of the UnixWare O/S cannot be carried out on a fully hard disk configured system.
Solution: Install using only the boot disk , when the O/S is then installed add the rest of the disks and they will then be seen correctly. There will be a newer UnixWare driver to resolve this feature in the future.
SMS and LDSM releases.
The SMS software must be used in conjunction with a special release of Lan Desk server Manager 2.8 (which installs a DMI 2.0 compliant service layer). This is supplied as part of the FT2400 Server CD Part No. 16211631.
Workaround: Not applicable.
LDSM install on DK440LX hardware.
The LDSM installation process brings up a dialog box saying the hardware is not recognised (but it still "does the right thing". This is a cosmetic issue only.
Workaround: Not applicable.
IPR4109/4111 - LDCM Fan monitoring.
The DK440LX uses a multiplexor to monitor more than the basic 3 fan inputs of the LM78. LDCM is not currently written to support this feature and therefore will only monitor 3 fans.
Solution: Support under LDSM + Apricot SMS pack supports the product correctly.
IPR4445 Scheduled shutdown can cause LDSM failure.
A scheduled shutdown of the system whilst a remote DMI connection is alive can cause the service layer of LDSM to fail which brings in Dr Watson. Because the system is closing down Dr Watson also fails and the close down is halted.
Workaround: None known.
ECC Monitoring depends on other products.
The ECC monitor component of SMS depends on the DBProxy device driver which is installed by the DMI BIOS component (part No. 16245231). So this software must also be installed for the ECC monitor to function.
Workaround: Not applicable.
Solution: Ensure s/w install is correct.
IPR4596 & 4597 - Interface to Power management component.
When entering a date/time for a power event, only the day number is needed (because the PIIX4 RTC alarm can only be programmed within the next 31 days). However the month and year must be entered even though they are subsequently ignored. This is a limitation of the LDSM 2.8 GUI There is no way of entering just the required information.
Workaround: None known.
Solution: Use the Setup GUI provided rather than the LDSM console GUI.
DMI indications are ignored by LDSM.
The SMS software generates DMI indications under certain circumstances (chassis intrusion, voltage failure, temperature too hot etc.). None of these indications will be visible using LDSM 2.8 because of a limitation of that software. As a work around, entries are placed in the NT event log.
Workaround: None known.
Solution: Use a different component of LDSM which doesnt ignore indications (info from Intel received 10/12/97). A future release of the SMS will correct this problem.
IPR 4562 - No SMS Help.
No Help is provided.
Solution: The next release shall have a help file.
Some SMS Parameters cannot be altered by the Setup GUI.
The GUI does not allow the power off notice period (or the message displayed, or the type of power off) to be altered.
Workaround: Edit the registry by hand.
Solution: The next release will contain this functionality.
LDSM crashes if a component is stopped.
If any of the DMI components are stopped whilst LDSM is displaying values from that component, one of the internal services of LDSM (ntsm) crashes. A reboot is required. This is a limitation of LDSM.
Workaround: None known.
IPR 4578 & 4579 - Power up on LAN/Modem.
Power up on Modem doesnt work at all, power up on Lan works even if just power up(modem) is requested.
Workaround: Power up the system but dont boot NT, then Power off (The BIOS programs the PIIX4 correctly).
Solution: This will be fixed in a future release in combination with fixed BIOS.
IPR 4594 - SMS can consume 100% of the processor.
Under some conditions (It is the 1st of the month and the schedule of power events is empty) a component of SMS loops, consuming 100% of the processor. The system continues to run, albeit slowly.
Workaround: Create a dummy event in the power schedule (e.g. power on at 1pm every Wednesday).
Solution: This will be fixed in the next release.
IPR 4631 - Server Abended after 3 days of tests using NSTEST.
Configuration Details: 256Mb RAM, Dual Pentium II @ 300MHz, AMI MegaRAID 431 controller, 3 x IBM Draco 9Gb HDD, Intel Pro/100B LAN adapter, Netware 4.11 & Embedded Intel 82557 LAN controller.
The server had been running IntraNetware and had 8 workstations each running NSTEST against it. After just under three days the server had abended with the following cause: Garbage Collection combine detected corrupt memory nodes at 0x00FF00FF.
Solution: The system has been re-tested using the parameter SET ALLOC MEMORY CHECK FLAG = ON, this checks for corruption within Alloc memory nodes. This time there were no ABENDs after almost 4 days of continuous testing. According to Novell there is still a chance that the server will abend with this flag on however this is fixed by using IntraNetware Support Pack v3.0 or later.
1) The Hard Disk and CD CD-Drive cage can be difficult to remove. If ALL the power and data cables are disconnected and moved away from the drives, the cage can be eased back and up at an angle. The screws holding the cage in place only need to be loosened off and not removed totally.
2) When adding memory, cards or other items that need to be fitted internally, remove the mains cable after switching off. This ensures that there is no power supplied to the motherboard.
3) Due to the single voltage regulator design of the motherboard, you need to insure that the processors have the same voltage IDs, otherwise the system will not boot. In simpler terms, you cannot mix Klamath and Deschutes versions of Pentium II in a dual processor configuration. Furthermore, to insure stable operation in multiprocessing O/S environments, speed, L2 cache size, ECC or non-ECC L2 cache in Klamath version of Pentium II, and processor family ID must match in a dual processor configuration. Your field upgrades from single processor to dual processor configurations need to take into account above factors.
4) There may be possible system hangs when shutting down or restarting Windows NT 4.0 due to BIOS issues, which is currently under investigation.
5) NetWare Server 4.11 currently is not supported on the DK440LX platform. This is a known third party issue, as NetWare does not have drivers available to support the AIC-7895 on-board SCSI device. Attempting to install NetWare 4.11 using the on-board SCSI controller may hang the system, or cause errors. In addition, NetWare will not recognise the on-board SCSI AIC-7895 controller when using an off-board SCSI adapter (3940 UW and 2940 UW).
6) The DK440LX system recognises certain SCSI tape drives as hard drives which may be due to problems with the core BIOS which is currently under investigation. The following is a list of tape drives that have been tested so far to exhibit this problem: HP Sure Store 6000 (DDS2) & Conner Python (aka: Archive)
7) There have been some installation problems with Permedia II based OpenGL cards with Windows NT 4.0 because NT 4.0 does not assign interrupts to AGP port when enumerating. The solution is to get updated drivers from the vendor that doesn't require an interrupt assignment to the AGP port.
8) APM resume events such as Wakeup on LAN, Wake on Modem Ring and Power on AC loss is not functioning in the Beta 8 BIOS under Windows 95. In addition, USB legacy support is not supported in the current BIOS. The support for these features will available in the Beta 9 DK440LX BIOS release.
9) If installing an Adaptec AHA2940 card to run an external SCSI device, the following settings are recommended. Machine Bios is set to Default settings (Advanced/PCI Configuration/PCI Slot 1 where Option ROM Scan and Enable Master are both set to Enabled and Latency Timer is set to 0040h). The AHA2940 Configuration should be Host Adapter ID is 7, SCSI Parity Checking and Host Adapter SCSI Termination are set to Disabled. Also, the Reset SCSI Bus at IC Initialisation option in the Advanced Configuration Options is set to Disabled.
10) When replacing or fitting a second processor, you need to remove the second drive bay metalwork for ease of access.
11) If the machine has only one processor fitted, then a Processor Termination Board must be located in the second processor slot.
12) If you find the processor is getting hot, check the fan. If it is not working, check it is connected to the CPU fan and not the front fan connection. If the connections are correct, then the fan is probably faulty.
13) When replacing the motherboard, after removing all the screws, ease the board forward and it will be free to take out. The motherboard fixing screws are not the same ones as used for add on's etc. They have a longer shank so please ensure the correct ones are fitted. Also, due to the lack of space, ensure that the Power Supply connections are fitted before the processor.
14) After restarting Windows 95 from MS-DOS mode, the system BIOS does not configure the diskette parameter table correctly if an LS-120 drive is the only floppy drive in the system. Windows 95 will report the LS-120 drive as a hard drive instead of a floppy drive and will report a floppy drive available as Drive A. If drive A is subsequently accessed, the system will lock up. The problem does not occur if a 1.44 MB 3-1/2" floppy drive is also present as either drive A or drive B. This will be fixed in a future BIOS revision.
15) The system BIOS does not recognise activity from a serial mouse as an APM event. The system will not be restored from a power-managed state until keyboard activity occurs. The system BIOS does recognise activity from a PS/2 style mouse. This will be fixed in a future BIOS revision.
16) Stuck or depressed Key during POST May Cause System Hang. If a key is stuck or depressed during POST, the system BIOS will continue to read data from the keyboard, resulting in a system hang condition. The BIOS is unable to detect when a key on the keyboard is stuck or depressed during Power On Self Test (POST). This will be fixed in a future BIOS revision.
17) The system BIOS does not detect when a single or double bit ECC memory error is identified by the memory controller. For single bit errors, the error will be corrected based on the memory checkbits. The corrected data will be passed to the system by the controller, but the error will not be signaled to the system BIOS. For double-bit errors identified during run time, no error will be signaled to the system BIOS and the system will not be halted. The erroneous data will be passed to the system by the controller. Because these errors are not detected by the system BIOS, they will not be flagged in the DMI log stored in non-volatile flash memory and the user will not receive information from this log that could be useful in isolating a failing memory module. This will be fixed in a future BIOS revision.
18) If replacing the Power Supply, check that the smaller of the two Power connectors has the location lug removed.
19) There has been a problem reported where the HP820cxi printer prints blank paper. It appears to fail the coms test. If the BIOS is changed from ECP to any other option apart from Auto the printer works OK. It has been passed to R&D to investigate.
20) There appears to be a problem with Pentium II Processors being supplied without the Heatsink fitted. They are joined together using a special tool and so any items found not to have the heatsink already fitted MUST be returned and replaced with the correct item.
21) The following connections will show errors as listed below if connected wrong.
22) During testing it has been noted that it is not possible to get digital audio or MIDI sound to come out of the Crinkle's built-in PC speaker. Operation through external speakers is fine. This is because the specification of the base board is such that the PC speaker is not connected to the CrystalWare audio chipset and that external speakers are necessary for the reproduction of WAVs or MIDI files.
23) Latest information on Intel Motherboard releases are:
Currently acceptable revisions for new purchases:
Currently acceptable revisions for field and production:
1) Improper installation of SMC may corrupt CMOS. You must unplug the AC power cord from the rear of the Apricot FT1200 when installing the Server Management Card (SMC) upgrade. Failure to do so may corrupt the motherboards CMOS memory. See the instructions for fitting the card and your Apricot FT1200 Owners Handbook for more information.
2) It has been found that while installing Windows NT 3.51 or 4.0, the server must be powered directly from the AC power supply. Otherwise, the Windows NT installation program causes the American Power Conversion (APC) UPS to switch to battery back-up mode. The UPS should be attached after installing the operating system but before installing APC PowerChute Plus.
3) SNMP Agent requires DPT Storage Manager. The DPT SNMP Agent does not report changes in the RAID subsystem unless the DPT Storage Manager is loaded and running at the server. See your DPT documentation for more information.
4) Mail system must be running when health alerts are issued. Your mail system must be running during the periods when Apricot SMA+ is scheduled to issue "health alerts" by e-mail. Otherwise, Apricot SMA+ may fail. See the topic on "Setting up an e-mail alert target" in SMA+ Help.
5) DMI Control Panel requires Client Service for NetWare. In order to use the DMI Control Panel in Intel LanDesk Client Manager, both the workstation and the server must be running the IPX protocol, and also the Client Service for NetWare which is included with Windows 95 and Windows NT.
6) Installing NetWare 4.11 onto a Crinkle based machine with version V04 Bios fitted. It has been found that when partitioning using a Windows 95 OSR2 version 2.1 floppy Disk, the installation fails after the correct language is selected. To correctly install, either use the DOS Installation supplied by Novell or MS-DOS 6.22 and create a partition greater than 50mb.
7) When installing NetWare 4.11 ensure the latest NetWare Service Pack is loaded. It is also advised to use the latest drivers supplied via our BBS or Webb site.
8) There is a problem with NetWare 4.11 not recognising the LAN Drivers when a second processor is fitted. The LAN drivers work OK with NetWare SMP providing the NetWare service Pack is loaded. If the service pack is not load the driver will load for 1 frame type and bind a protocol but will not broadcast on the network. The following settings should noted and will be set as default (shown below):
9) We have identified an error in the User's Manual - chapter 4 page 5 - the reference to the connector in which the CPU fan should be connected is incorrect. The correct ref is J3F2. The connector has changed due to late info from Intel and we missed the change in the User Manual.
10) Subject: Intel ICU rel 1.45 - Attempts have been made to configure the ICU - ISA Configuration Utility - rel 1.45 on the FT1200 to see if the IRQ could be changed for the Pro100B network adapter in SCO-Unix. It does not look like it can use anything other than IRQ 9. The ICU Software is also used to add an ISA card and reserve resources for it. There are config files for many cards, and you can add you own card - giving it a name of you choice and setting irq / io / memory. However, when you go File-->Save, or Exit---Save it hangs. On reboot the new card / resources are not saved. It has been tried with a DOS 622 setup - nothing else in config.sys accept the two lines the ICU install created, and no autoexec file. You have to install the ICU (install.exe from the first floppy) onto a DOS hard disk as the executables alone are over 2Mb - it will not fit on a floppy. The mouse driver used was an old Logitech one, but the hang occurred with no mouse driver and driving it from the keyboard as well. The same disk was tried in an FT2400 (Plexus Pentium Pro) and as the ICU starts to load, on the initial screen with the mouse hour glass you get: Fatal error 286.3330: General protection fault detected followed by a diplay of the cpu registers. If fitted, the Adaptec AHA 1510 card will work, but it is not ideal as the 1510 (needs i/o 340-35f) card does not have a utility to reserve resources in the BIOS. Fit the add in cards and ensure that the PCI bios does not cause any clashes! Note: The crinkle product has a 50pin SCSI adapter as standard so an Adaptec 1510 ISA card will probably only be used in rare instances.
Please refer to the following statement regarding Intel's support of the ICU. "If Users wish to reserve the resources for a card, it is recommended that the user uses the ISA card vendor's own utility to do so". The ICU is no longer a "supported" product as it came from Intel's development labs and has not been taken up and maintained.
1. Megaspi.sys, AMI's ASPI manager for the MegaRAID under DOS, uses 6K of system memory once it is loaded.
2. At this time, copied CDs are not accessible from DOS even after loading Megaspi.sys & AMIcdrom.sys.
3. The items "Media Error" and "Other Error" are found in the Ctrl-M firmware utility(among others) under: 'Objects', 'Physical Drive', select the device in question, and hit 'F2'. A "Media Error" is an error which occurred while actually transferring data(reading and writing data). An "Other Error" is one which occurs at the hardware level due to a device failure, poor cabling, termination, signal loss, etc.
4. The firmware option "FlexRAID Virtual Sizing" is what enables RAID expansion within the various MegaRAID utilities. FlexRAID Virtual Sizing must be enabled to increase the size of a logical drive or add a physical drive to an existing logical drive. The option is located within the <Cntrl-M> boot utility in the following hierarchy:
5. AMI does not have a driver for BSDI UNIX and therefore it is not supported by the AMI MegaRAID controller.
6. The AMI MegaRAID controller supports 1 LUN per each target ID. No multiple LUN devices are supported.
7. The MAXIMUM MegaRAID power requirements are 15watts at 5v. = 3amps.
8.The ANSI specification dictates the following:
9. J13 Fault Bus Connector is a 26pin connector on the MegaRAID. It is reserved for use as an OEM only option to monitor enclosure items such as drive speeds, enclosure temperature & fan speeds, etc. and be able to report such information.
10. Installing NT3.51 using the NT3.51 upgrade CD without creating boot floppies causes NT to overwrite the installed MegaRAID drivers with generic SCSI drivers. AMI strongly recommends that boot floppies from the upgrade CD be created and used to install NT3.51 when upgrading to NT3.51.
11.Whenever the operating system is installed via a BOOTABLE CDROM, the devices on the MegaRAID will not be recognized until after the initial REBOOT process. The Microsoft documented workaround is listed in their SETUP.TXT file as shown below:
SETUP.TXT (located on diskette#2 or CDROM)
To install drivers when Setup recognizes one of the supported SCSI host adapters without making the devices attached to it available for use:
Windows NT will now recognize any devices attached to this adapter. Repeat this step for each host adapter not already recognized by Windows NT Setup.
1) The software must be used in conjunction with a special release of Lan Desk server Manager 2.8 (which installs a DMI 2.0 compliant service layer) Part No. 16255431.
2) Installation is stand-alone, after the installation of LDSM 2.8 (and a reboot) rather than as a "snap in" disk. This limitation will probably be removed when we adopt LDSM3.0.
3) The ECC monitor component of SMS depends on the DBProxy device driver which is installed by the DMI BIOS component (part No. 16245231). So this software must also be installed for the ECC monitor to function.
4) The IR receiver has been removed.
5) When entering a date/time for a power event, only the day number is needed (because the PIIX4 RTC alarm can only be programmed within the next 31 days). However the month and year must be entered even though they are subsequently ignored. This is a limitation of the LDSM 2.8 GUI. There is no way of entering just the required information. However, the existence of the new GUI means that this is no longer so serious.
6) The `Wake up on LAN and `Wake up on Ring in functionality of the power control subsystem has not yet been tested.
7) The SMS software generates DMI indications under certain circumstances (chassis intrusion, voltage failure, temperature too hot etc.). None of these indications will be visible using LDSM 2.8 because of a limitation of that software. As a work around, entries are placed in the NT event log
8) If any of the DMI components are stopped whilst LDSM is displaying values from that component, one of the internal services of LDSM (ntsm) crashes. A reboot is required. This is a limitation of LDSM.
9) Ideally the sms.exe program (which is the GUI for adjusting system parameters) should be a control panel applet, but we were not able to get that to work in time for this release. The GUI doesn't allow the power off notice period (or the message displayed) to be altered. The menu item "sms setup" is not removed when SMS is uninstalled.
10) A timed closure of the system whilst a remote DMI connection is alive can cause the service layer of LDSM to fail which brings in Dr Watson. Because the system is closing down Dr Watson also fails and the close down is halted (IPR 4445).
11) Disk Layout - Volume in drive A is SMS-REL1