ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º Inboard 386 Common Problems º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 101 KEY ENHANCED KEYBOARD PROBLEMS IBM PC AT Model 339 (8 MHz) computers are the only IBM computers that can use a 101 keyboard. The Shift or Ctrl keys may stick in an AT computer with an earlier BIOS. A newer version of the BIOS will fix the problem. BEEPS AT POWER UP ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ These sounds: ³ Indicate a problem with this: ³ ÆÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍØÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ͵ ³ CONTINUOUS BEEP ³ The power supply ³ ³ REPEATING SHORT BEEPS ³ The power supply ³ ³ 1 LONG AND 1 SHORT BEEP ³ System Board ³ ³ 1 LONG AND 2 SHORT BEEPS ³ Display ³ ³ 1 LONG AND 3 SHORT BEEPS ³ Enhanced Graphics Adapter ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ BOOT FAILURE DURING INSTALLATION Some 8-MHz COMPAQ DESKPROS (with memory on the system board) and PORTABLE IIs (with assembly numbers 324.XX and 328.XX), won't boot when you install an OS/2 compatible Inboard 386. If you have this problem, contact Intel customer support. COMPAQ DESKPRO 286 AND 164 AND 201 MESSAGES You must fill all system board sockets in the COMPAQ DESKPRO 286 before you can add additional memory to the computer. COMPUTER AUTOMATICALLY REBOOTS Adding an expansion board such as the Above Board can cause the COMPAQ 286 to reboot itself automatically. This is symptom of either a failing power supply or a bad connection between the power supply and the system board. First check the connection between the power supply and the system board. Vigorously reseat the connection, but be careful to not press so hard that you break the connector or system board. If the power supply is bad or too weak, you'll need to replace it. ILIM386 PRIVILEGED OPERATION EXCEPTION ERROR ILIM386 generates this error when an instruction is incompatible with the current CPU operation mode. An interaction between the application software, ILIM386, and the system BIOS can cause this error. Changing the system BIOS may solve the problem. This error can also be caused by the incorrect amount of Extended memory being set by the EXT= parameter on the ILIM386.SYS command line of the CONFIG.SYS. If the user wants to set aside some Extended memory, the EXT= parameter must specify the amount needed, plus 144K for ILIM386.SYS to load into. For example, if a user wanted to have 256K of Extended memory available for use by the ICACHE.COM disk caching utility, the ILIM386.SYS command line of the CONFIG.SYS would look like: DEVICE=ILIM386.SYS EXT=400 (256K for the ICACHE, and 144K for ILIM386.SYS) ILIM386 VERSION 4.07 AND SOFTWARE WARMBOOTS When you use ILIM386 version 4.07, a software generated warmboot will result in an error when INBRDPC.SYS tries to load. The error will state that 80386 control software has been loaded. This is because ILIM386 put the 386 CPU into "virtual 86" mode and this mode is not reset by the software warmboot. LOCKUPS WITH CAD PROGRAMS Some programs will recognize a math coprocessor even if the math coprocessor switch is set incorrectly. Other programs won't, so make sure the switch is set correctly. MEMORY BOARD FAILURE Installing the Inboard 386 and the faster crystal in 6-MHz IBM ATs can cause memory boards to fail. If the BIOS is dated Jan. 10, 1984 it's okay to leave the original 12-MHz crystal in the computer to avoid memory board failure. MONITOR BOOTS UP IN 40-COLUMN MODE This can happen with EGA boards. The solution is to use the EGASIZE= parameter in the INBRDAT.SYS device driver command. OUT OF ENVIRONMENT SPACE The environment may be up to 32K bytes long. During power on, COMMAND.COM receives a default environment size of 160 bytes. This can fill up quickly, in which case DOS displays the message "Out of environment space." If you use DOS 3.1 through 3.3, you can increase the environment size by including the following command in the CONFIG.SYS file: shell=[d:][path]command.com /p /e:xxxx In DOS 3.1, xxxx is the # of paragraphs (16 byte blocks) in the environment. The allowable range is from 10 to 2048. In DOS 3.2 and 3.3, xxxx is the actual # of bytes in the environment. The allowable range is from 160 to 32,768. SCO XENIX SERIAL PORT IDENTIFICATION PROBLEMS Xenix can have trouble identifying serial ports On any cached 386 machine, including those equipped with Inboard 386. This is a problem with Xenix, not the Inboard. It occurs only on fast cached machines. Xenix requests a status report from the serial ports then tries to read the results before the routine returns them. To fix this problem, edit the SIOCNF.C file in the /USR/SYS directory. Locate the table declaration containing many different types of serial ports. Put the declaration of the affected serial port at the top of the list and make at least 5 duplicate entries. This way Xenix will check the port several times and one of the requests will retrieve the results. Recompile the "siocnf.c" file, then do a "make libio" to make the I/O libraries. When you're done, link it into the kernel and reboot. Field reports indicate that this procedure has completely fixed the problem. SCO XENIX 386 AND ESDI HARD DISK CONTROLLERS (Field report) A customer reports intermittent VERY slow hard disk access using 3 brands of ESDI controllers in system with Inboard 386. No known solution. The same hardware works fine in different 386 systems. 301 KEYBOARD ERROR This error message may occur on boot up. So far it has not been related to any real problems. The solution is to hit (F1) to continue and ignore the message. The message should be intermittent, and seems to be related to having the "old"-style AT keyboard on an new 8 MHz AT. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ End of file Intel FaxBack # 2064 June 25,1992