Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!sarah!cs.albany.edu!crdgw1!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!think.com!mintaka!ogicse!ucsd!sdcc6!sdcc6.ucsd.edu!cg108w3 From: cg108w3@ucsd.edu (Steve - Happy Hacker) Newsgroups: comp.sys.ibm.pc.hardware Subject: Re: Diagnostics with AMI BIOS Message-ID: Date: 21 Jun 91 00:17:51 GMT References: <1991Jun18.170421.26077@cbnewsj.att.com> <1991Jun19.034826.6420@chinet.chi.il.us> Sender: news@sdcc6.ucsd.edu Distribution: usa Organization: /home/cg108w/cg108w3/.organization Lines: 34 In-reply-to: chaz@chinet.chi.il.us's message of 19 Jun 91 03:48:26 GMT Originator: cg108w3@icogsci1 --=}>> On 19 Jun 91 03:48:26 GMT, chaz@chinet.chi.il.us (Charlie Kestner) said: CK> In article <1991Jun18.170421.26077@cbnewsj.att.com> ker@cbnewsj.att.com (kenneth.roser) writes: >My 386-33 machine has an AMI bios dated 5/91. I thought that one of >the features of an AMI BIOS was built in diagnostics. How does one >invoke these diagnostics? It's not specified in my motherboard >documentation. > >On the other hand, is it possible my BIOS doesn't have this feature? CK> You can get to the diagnostics (provided your BIOS has them), by ^^^^^^^^^^^^^^^^^^^^^^^^^^^ CK> doing whatever is required to get to the CMOS setup program at CK> bootup. On my AMI BIOS (dated 4/90), I get there by hitting the CK> delete key at bootup. The BIOS then presents me with a choice of CK> "SETUP" or "DIAGS". I have seen several (including my own) AMI BIOS's that DO NOT have the diagnostics program in them. AMI offers the same diagnostics on disk, and I was able to find them on a local BBS. Although, it would be nicer to be able to use them when the computer won't boot at all. For the interested, I have an Amstrad 386/33 motherboard with the VLSI brand chip set. Hitting Del at boot time gives me the choice of RUN SETUP or REBOOT. Also, it has no extended BIOS configurations. Things like bus speed and wait states are all jumper controlled. Looks like there are different types of AMI BIOS's. -Steve -- }>> Steve Haehnichen <<{ shaehnichen@ucsd.edu Disclaimer: UCSD and I do not share any opinions.