chip@ateng.ateng.com (Chip Salzenberg) (11/29/88)
We recently have had occasion to install Xenix/386 2.3.1 on a 386AT system based on a Monolithic System Corporation motherboard. Or to try, anyway. When booting the N1 floppy, everything works fine until the kernel is loaded. :-) Seriously: at the boot prompt the keyboard works, and during the kernel load from floppy the Caps Lock and Num Lock lights toggle correctly. But once the kernel load completes, Caps Lock and Num Lock -- along with the rest of the keyboard -- do nothing at all. The system has 1.5M of memory and an Adaptec ESDI disk controller; and it worked fine with Xenix/386 2.2.3. We've tried two keyboards -- one of which is a gen-u-ine IBM AT keyboard. We even got a replacement BIOS from Monolithic. Nothing has helped. Is there anyone who has Xenix 2.3 and a Monolithic motherboard living in harmony? What's the deal? Please, help us out. (Post replies if you like; other people may have Monolithics.) -- Chip Salzenberg <chip@ateng.com> or <uunet!ateng!chip> A T Engineering Me? Speak for my company? Surely you jest! Beware of programmers carrying screwdrivers.
jbayer@ispi.UUCP (Jonathan Bayer) (11/29/88)
In article <1988Nov28.184415.1424@ateng.ateng.com>, chip@ateng.ateng.com (Chip Salzenberg) writes:
. We recently have had occasion to install Xenix/386 2.3.1 on a 386AT system
. based on a Monolithic System Corporation motherboard.
.
. Or to try, anyway.
.
. When booting the N1 floppy, everything works fine until the kernel is
. loaded. :-) Seriously: at the boot prompt the keyboard works, and during the
. kernel load from floppy the Caps Lock and Num Lock lights toggle correctly.
. But once the kernel load completes, Caps Lock and Num Lock -- along with the
. rest of the keyboard -- do nothing at all.
Try slowing down the computer. If it works then I think there is a problem with
the keyboard io on the board.
Jonathan Bayer
Intelligent Software Products, Inc.