At 11:57 PM 7/7/2005 +0200, Bernd Blaauw wrote:
Hello Michael, nice to see you making EMM386 even more perfect.
I'm going to test AUGOS one more time because I know that as soon as I
put EMM386 2.04 out there, AUGOS is going to start breaking again,
starting with your system.
typical, isn't
Hello Michael, nice to see you making EMM386 even more perfect.
I'm going to test AUGOS one more time because I know that as soon as I
put EMM386 2.04 out there, AUGOS is going to start breaking again,
starting with your system.
typical, isn't it? :)
rather than AUGOS. But if nothing surfa
At 03:09 PM 7/7/2005 +0200, Eric Auer wrote:
> AUGOS crashes with low EMM values somewhere below 2M and it needs a
> slowdown program for any PC above approximately a 30Mhz 80486.
Disagreed. Runs okay on my 500 MHz K6-2, but the "music" (beeps which
indicate the computation progress, yuck) are
Hi!
> AUGOS crashes with low EMM values somewhere below 2M and it needs a
> slowdown program for any PC above approximately a 30Mhz 80486.
Disagreed. Runs okay on my 500 MHz K6-2, but the "music" (beeps which
indicate the computation progress, yuck) are shorter than intended.
But on the other h
Continuing the conversation with myself
At 09:52 PM 7/6/2005 -0500, I wrote:
AUGOS crashes with low EMM values somewhere below 2M and it needs a
slowdown program for any PC above approximately a 30Mhz 80486. I don't
see the memory requirement as a bug with EMM386 unless there is evidence
At 09:52 PM 7/6/2005 -0500, I wrote:
In the same fashion, a small percentage of users are affected by the HIMEM
fix, unless the /NUMHANDLES option is used. Then the fix is pretty much
mandatory.
There is no great need for most users to grab the forthcoming EMM386/HIMEM
update.
I take that
At 11:47 PM 7/6/2005 +0200, Eric Auer wrote:
For me it was usually hang / illegal instruction for small EMM= values
and spontaneous reboot (page fault??) for bigger values.
AUGOS crashes with low EMM values somewhere below 2M and it needs a
slowdown program for any PC above approximately a 30
Hi...
> >emm=1520 (0x660k EMS) / emm=1536 / emm=2048: all crash while playing Go
>
> I found the problem with EMS page count rounding errors of actual
> versus calculated, causing a problem with typically low EMM= option values
> under EMS.
For me it was usually hang / illegal instruction
At 03:32 PM 6/18/2005 +0200, Eric Auer wrote:
emm=1520 (0x660k EMS) / emm=1536 / emm=2048: all crash while playing
Go, in all three cases first showing an illegal instruction and
then stopping because the MCB at the end of the UMB area, for me at
dfdf:0, got overwritten. Or maybe some EMS
Hi!
> LOG probably hasn't worked in years.
> I've never used, tested, or modified it.
Then please remove it completely (from the code and from the help screen).
I had thought that LOG could help with debugging, and I think other people
could fall in the same hole unless LOG is removed...
> >EMM
10 matches
Mail list logo
