maine@elxsi.dfrf.nasa.gov (Richard Maine) (05/10/90)
On 9 May 90 07:37:10 GMT, kirchner@uklirb.informatik.uni-kl.de (Reinhard Kirchner) said: Reinhard> your SYSID is really a great peace of software, we all have Reinhard> to say thanks. Me too. Reinhard> BUT there is a little problem, and this is why I send mail. Reinhard> I bought a AST Premium 386/33, Reinhard> that is a 33Mhz 386, with 32kB cache. Reinhard> Now SYSID can't determine this cpu, it simple hangs in the Reinhard> cpu detection and can only by reactivated by the reset Reinhard> button. I ran into simillar symptoms on a generic no-name 386 clone. Tracked it down to hanging in the code that tried to determine the co-processor type. (I don't (yet) have a co-processor in the system). I verified this by hacking around the call to the co-processor-determination code (Sure was nice to have the source so this was possible). I did not dig enough into the code, nor do I know the tricks well enough, to be sure of all the circumstances needed to cause the hang, but the omission of the co-processor seems like the crux of the problem. (It is concievable that this only comes up on 386 systems; the only XT clones convenient to me all have 8087 chips and I wasn't inclined to pull them out just to test this). My hack was to an older version of SYSID, and I haven't gotten around to doing it to the current version, though it really wasn't very hard. Would be better if somebody figured out how to do it "properly" instead of just hacking out the co-processor test, so I don't think my hack is worth posting. -- Richard Maine maine@elxsi.dfrf.nasa.gov [130.134.64.6]