If you have any problems with EMM386 2.05, try the unofficial release
emmflesh.zip at
ftp://ftp.devoresoftware.com/downloads/emm386 as it has a couple of
relatively minor fixes in the EMM386.EXE file that will affect some
users. Be aware that this unofficial version is not EXE compressed in siz
G'day Johnson,
From: Johnson Lam <[EMAIL PROTECTED]>
Date: Wed, 21 Sep 2005 09:52:24 +0800
[..]
I noticed lots of users (especially in China) still stick to 'PC
Tools
Memory Information v9 (MI)'. Is it too old to report correct
information from FreeDOS's memory managers or UMB information?
At 05:05 PM 9/19/2005 -0700, Brolin wrote:
Firstly, I have not tested this new release. That said, what is the status
with regards to having FastTracker II working on FreeDOS?
FastTracker 2.08 runs fine for me under latest HIMEM and EMM386.
PKUNZIP failing unless the NOEMS option is specified
At 05:01 PM 9/19/2005 -0500, I wrote:
This version of EMM386 has a number of compatibility changes to enhance
operability with a variety of DOS applications and environments without
the need for advanced option tweaking. As a result of the seven changes
to EMM386 and two changes to HIMEM, thi
Hi,
I noticed lots of users (especially in China) still stick to 'PC Tools
Memory Information v9 (MI)'. Is it too old to report correct
information from FreeDOS's memory managers or UMB information?
Since it's layout is neat and clean, I suggest to make a new layout of
MEM which similar to 'MI',
Bernd Blaauw wrote:
>
> MEM (1.6) itself is broken, get 1.7beta or 1.8alpha
> both available at: http://wiki.fdos.org/Main/mem
>
> Please report back if that solves your UMB Corruption error or not.
>
> Bernd
>
Thank you, MEM 1.7beta works fine. -Dan
---
Hi Eric,
On the other hand, SCSI does seem to have odd properties
which we should analyze some more. Remember that LBACACHE
requires the TUNS option for some SCSI systems when you
loadhigh LBACACHE: TUNS allocates stack space in low RAM,
as some unknown quirk makes SCSI BIOSes fail on int 13 cal
Hi Michael,
Nope, there are documented instances of SCSI drivers being incompatible
with VDS.
Sure, but as I understand it, this VDS problem will occurr even when
there's NO driver loaded (e.g. pure INT13)?
In those cases, they share the same interrupt and potentially
the same register val
Hi there,
I am using a freedos-based boot disk and now I encountered that on a
machine with quite a number of drives and partitions, the ramdisk driver
crashes with "Not enough DCBs". Is there a way to increase the number of
DCBs with a parameter in config.sys or similar? Or can I compile a
custo
Hi again, VDS question time... So the only reason why you have
to turn off VDS on some SCSI system is that the interfaces
overlap (use the same interrupt / register values)? If so, it
should be possible to autodetect that case. But I assume there
are other cases where VDS must be turned off to mak
10 matches
Mail list logo
