From:	jdashiel AT eagle1 DOT eaglenet DOT com
Date:	Tue, 28 Jan 1997 16:51:30 -0500 (EST)
To:	MORRIS JP <jpmorris AT csm DOT uwe DOT ac DOT uk>
Cc:	geneb AT web DOT wa DOT net, opendos AT mail DOT tacoma DOT net
Subject:	Re: [opendos] EMM386 gets violent
In-Reply-To:	<199701281208.MAA08127@milly>
Message-Id:	<Pine.NXT.3.95.970128164333.938j-100000@eagle1>
Mime-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

In that case some software will need an alternative to emm386.
I have qemm 7.04 which is the last version I could get
to run on this system.  How to tell opendos in the midst of the
installation you don't want to use
its emm386.exe but an alternative is something else again.
The installation program didn't appear to allow that much flexibility.
Wheneer an OS is installed it should make log files documenting results
of all steps.  This way, if the package has to be uninstalled the user
can have
a record where the system crashed and burned.  This would also be
extremely helpful if all software
installs did this especially for those of us who do their installs and
don't have
the monitors turned on.  I turn the monitor on for sighted people when
they come over,
but that's not that often.  Have to also remember to turn on the lights
too.
On
Tue, 28
Jan 1997, MORRIS JP wrote:

> 
> AFter a slight accident with the install program, I was finally able to
> get OpenDOS working, but it seems to be quite buggy.
> 
> (Don't worry.. I always find bugs in OSes..)
> 
> The problem appears to lie in EMM386.  Everything works fine unless EMM386 is
> running.  In this case, most protected-mode programs (DOOM, DUKE3d, WINDOWS)
> reboot the system in an extremely messy fashion.
> 
> Currently I am using the EMM386 from my old DRDOS installation, but that nailed
> the multitasking, and conventional memory is critically low.
> 
> I have tried all permutations of EMM386's switches (I was afraid of bugs in the
> DPMI server.. Borland added features to Ergo286)
> 
> I do wonder if EMM386 is trying to do strange undocumented things: my CPU is
> an AMD K5 device, not Intel.
> 
> Has anyone else had problems like that?
> This might be the cause of the problems experienced by jdashiel..
> 


jude <jdashiel AT eagle1 DOT eaglenet DOT com>

- Raw text -