Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcdchg!ddsw1!andyross
From: andyross@ddsw1.MCS.COM (Andrew Rossmann)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Re: Missing INFOP100 part 3/3
Message-ID: <1990Aug21.221247.18176@ddsw1.MCS.COM>
Date: 21 Aug 90 22:12:47 GMT
References: <1990Aug13.152727.10634@IRO.UMontreal.CA> <2210019@hpausla.aso.hp.com> <1990Aug18.221135.21163@portia.Stanford.EDU>
Reply-To: andyross@ddsw1.MCS.COM (Andrew Rossmann)
Organization: ddsw1.MCS.COM Contributor, Wheeling, IL
Lines: 23

In article <1990Aug18.221135.21163@portia.Stanford.EDU> toye@sunrise.stanford.edu (George Toye) writes:
>I have found that all versions of this software derived from SYSID 4.4 on
>ward has similar problems on many 386 and 386sx machines without coprocessors.
>It is as DAK@hp describes ... the code which tries to determine the math
>coprocessor type causes these machines to hang.  (NOTE: SYSID 4.3 implements
>this part of the code differently and works just fine.)  Is there some
>common element to the systems that hang ... like all use AMI BIOS?  They do
>not safely return from a math coprocessor exception caused by a missing 387
>(uninitialized vector or hardware design)?
>The machines that I have encountered so far with this problem have in common
>the AMI BIOS.  Does everyone with AMI BIOS, no 387 have similar results?


  I'm continuing to look into the problem. I've made further changes for
the upcoming edition, primarily by looking at how other programs find out!!
 Considering how everyone thinks that the AMI BIOS is so fantastic, that it
has this one major bug!!
  If you are having problems, I'd probably be inclined to write a little
test program to see if my latest version works, without having to go
through a whole major upgrade of INFOPLUS.

  Andrew Rossmann
  andyross@ddsw1.MCS.COM