Path: utzoo!attcan!uunet!mcsun!hp4nl!utrcu1!hania
From: hania@utrcu1.UUCP (Simon Hania)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Coherent, anybody?
Message-ID: <296@utrcu1.UUCP>
Date: 10 Jul 90 08:59:23 GMT
References: <10545@spool.cs.wisc.edu> <26840001@hpcvra.CV.HP.COM> <4815@milton.u.washington.edu> <1990Jul9.183442.22228@nucleus.mi.org>
Reply-To: hania@utrcu1.UUCP (Simon Hania)
Organization: Utwente, Enschede
Lines: 21

In article <1990Jul9.183442.22228@nucleus.mi.org> dar@nucleus.mi.org (Dario Alcocer) writes:
>
>I had the same problem with my 386 clone (AMI BIOS), but it was an
>intermitten problem for me.  It seemed to happen most after having
>run MS-DOS, then did a soft-reboot; maybe the GDT is using the garbage
>left in memory by the last DOS run...
>
I am running Coherent on a Morse 386SX motherboard, AMI BIOS, WD clone
hard disk controller and Seagate ST225 and ST251-1 drives.
Rebooting Coherent with CTRL-ALT-DEL hangs the machine, rebooting MS-DOS
this way and starting Coherent leads to kernel panic at start-up.
Under MS-DOS I'm using QEMM, which puts the 386 in V8086 mode. This
probably is the cause.
I have to do a hard-reboot to switch between Coherent and MS-DOS and
vv.

-- 
------------+-----------------------
Simon Hania |  Hania@UTwente.NL
            |  HANIA@HENUT5.BITNET
            |  hania@utrcu1.UUCP