Hi,
Just to come back and add to this (in the vain hopes of being
constructive),
On Mon, Oct 19, 2015 at 7:02 PM, Bret Johnson wrote:
>> EMS is quite obsolete, even in DOS circles. I'm not saying it's "bad",
>> but there are "better" ways to do things (e.g. DPMI).
>
> Depends on what you're
C.J. van Delft wrote:
>
> No I am not a developer ( any more ! ) at 70 I am just relaxing and
> doing very little. My concern is/was that FreeDos purports to be a
> free MS/Dos replacement and is currently more and more being pushed in
> the direction of 32/64 bit support, apparently without reg
Hi, to join this discussion...
I agree that the best way to install DOS on a very old PC
is to use a floppy distro. If you ask me, one which users
can install using manual FDISK FORMAT SYS XCOPY steps as
needed depending on their wishes. No need to waste space
on a floppy for a complex installer
Mateusz Viste wrote:
Hi C.J,
Reading your message I couldn't help but wonder about a few things.
Exact questions below.
On 20/10/2015 10:51, C.J. van Delft wrote:
I, for one, would also point out that there are many museums and
individuals with VERY old machines, who would need FreeDos if ever
Hi C.J,
Reading your message I couldn't help but wonder about a few things.
Exact questions below.
On 20/10/2015 10:51, C.J. van Delft wrote:
> I, for one, would also point out that there are many museums and
> individuals with VERY old machines, who would need FreeDos if ever their
> MS/IBM flo
Michael Brutman wrote:
Ok. I give up. No more 16 bit talk and FreeDOS in the same
discussion every again. I promise.
Which is just plain wrong.
MS/Dos was ALWAYS first for the 8086/8088 architecture with 1MB
(640Kb)memory, Any improvement to those limits was kludged/bolted on. If
we no
> EMS is quite obsolete, even in DOS circles. I'm not saying it's "bad",> but
> there are "better" ways to do things (e.g. DPMI). Depends on what you're
> doing. DPMI is good for "regular" programs, but not necessarily for TSR's
> and device drivers. EMS is specifically designed to be compatib
I have machines that have hardware EMS.
What I just read above is that FreeDOS shouldn't bother with EMS support
because it is obsolete. And that there is only one user who uses EMS and
he doesn't use FreeDOS, so it really doesn't matter.
Ok. I give up. No more 16 bit talk and FreeDOS in the s
Hi,
On Mon, Oct 19, 2015 at 6:12 PM, Michael Brutman wrote:
>
> EMS can work on 8088 class machines, given the right add-on memory card.
> DPMI will never work on that kind of machine.
I thought that was obvious. Did I not imply that heavily enough? Did
anybody here not actually know that alread
EMS can work on 8088 class machines, given the right add-on memory card.
DPMI will never work on that kind of machine.
--
___
Freedos-devel mailing list
Freedos-devel@lists.source
Hi,
Disclaimer: I've never done any direct EMS programming. I wish I was
more help here, but alas
On Mon, Oct 19, 2015 at 12:08 PM, Bret Johnson wrote:
>
> If you read the EMS v4 spec carefully
> (http://www.phatcode.net/res/218/files/limems40.txt), it doesn't actually
> say that the EMMXXX
> AFAIK, the name EMM0 is part of the EMS> standard, meaning any EMS
> manager MUST use> use this device name. If you read the EMS v4 spec carefully
> (http://www.phatcode.net/res/218/files/limems40.txt), it doesn't actually say
> that the EMM0 name is required. It's mentioned in the ap
Bret Johnson said:
> it looks like your EMS detection routine is faulty.
> It depends on the presence of a device named
> EMM0, which doesn't apply to all EMM's.
AFAIK, the name EMM0 is part of the EMS
standard, meaning any EMS manager MUST use
use this device name.
I am not a p
Hi,
On Thu, Oct 15, 2015 at 5:43 PM, sparky4 wrote:
>
> I helped ported and improved a memory manager from a game~
>
> it is in project 16
>
> https://github.com/sparky4/16/blob/master/src/lib/16_mm.c
> https://github.com/sparky4/16/blob/master/src/lib/16_mm.h
>
> the more than 64kb data stuff is
how dose one code that?
--
View this message in context:
http://freedos.10956.n7.nabble.com/extending-chkdsk-to-fat32-tp23607p23612.html
Sent from the FreeDOS - Dev mailing list archive at Nabble.com.
--
__
!! ah!
--
View this message in context:
http://freedos.10956.n7.nabble.com/extending-chkdsk-to-fat32-tp23607p23611.html
Sent from the FreeDOS - Dev mailing list archive at Nabble.com.
--
___
Just took a quick glance at the first part of your code (comparing it to some
of mine), and it looks like your EMS detection routine is faulty. It
depends on the presence of a device named EMM0, which doesn't apply to
all EMM's.
In my code, I don't look for a specific device name to test for
I helped ported and improved a memory manager from a game~
it is in project 16
https://github.com/sparky4/16/blob/master/src/lib/16_mm.c
https://github.com/sparky4/16/blob/master/src/lib/16_mm.h
the more than 64kb data stuff is all that is left in making this work well
--
View this message in
Hi Sparky,
> is this [extending chkdsk to fat32] possible?
My answer is based on "CHKDSK works on all computers
where DOS works and behaves as in old MS DOS times":
Yes and no. To do proper checking, you want to have
more memory available, so you want a 32 bit memory
space. The DOS port of DOSF
is this possible?
--
View this message in context:
http://freedos.10956.n7.nabble.com/extending-chkdsk-to-fat32-tp23607.html
Sent from the FreeDOS - Dev mailing list archive at Nabble.com.
--
__
20 matches
Mail list logo
