[Prev][Next][Index][Thread]

Re: Big problems w/ 1.99n5 under Win/95



>>>>> "John" == JohnTClark  <JohnTClark@aol.com> writes:

    John> For some reason my installation of 1.99n5 from the Bleeding
    John> Edge over 1.99n seems to have totally died now under Windows
    John> 95 June Test Release.  Before that though there were
    John> problems that mystify me as well.  Using 1.99n I could run
    John> executor if it was the very first thing I did after booting
    John> into Windows 95 and could only run it once.  After that
    John> trying to run executor again causes the message "Executor
    John> has run out of memory try using a small -applzone" which
    John> seems odd.

It sounds like DPMI memory not being released after Executor quits.
You can find out how much DPMI memory Executor thinks you have by
running "executor -info".  Once you can run Executor 1.99n5 again,
please do so, then run Executor without the switch, quit, and then run
it again.  If the amount of DPMI memory has decreased, then there is a
bug somewhere, quite possibly in your Windows beta.

    John> ...
    John> I have noticed that trying
    John> to run cwsdpmi on its own says "Protected mode not
    John> available" and then produces a General Protection Fault of
    John> sorts.

Yes, Windows '95 already provides DPMI, so a second DPMI provider
can't be run.

    John> That at any rate is what it used to do.  Now it is worse.  I
    John> either get an abort with EIP tracebacks - a representative
    John> example is below - using either 1.99n or 1.99n5 with
    John> applzone 1024 (the only setting which seems not to
    John> immediately provoke the out of memory fail code) 1.99n or
    John> 1.99n5; or if I add -nosplash, an endless stream of the same
    John> messages saying "Make sure $MACDIR/.Rsrc/System is readable
    John> and writable and that it has 512 bytes added to the
    John> beginning of it".

Somehow your System file has been corrupted.  Reinstall 1.99n
somewhere other than where you normally install it, and then copy the
new exsystem.hfv from your reinstall on top of the exsystem.hfv that
you normally use.  This will allow you to run again.  I am trying to
figure out why System files seem to be getting corrupted fairly often
now.  I thought it was a bug in Executor that Desktop Textures was
hitting, but now I'm not so sure.

bugs fixed.  We're hoping to go beta in mid August.

	--Cliff
	ctm@ardi.com


References: