Hi!
Your vision on DOS is somewhat, well, interesting ;-) So
there is a lot to chat about, although I am not sure if
the KERNEL list is the right place for this topic. DPMI:
I would expect performance gain to be minimal. Maybe there could be
Low/HMA/UMB memory savings with a different
Hi Louis,
sort of a long response - it seems hard to make a short point here:
FreeDOS Roadmap, as goals and stretch goals for the project. I read
(paraphrasing): built-in networking, built-in USB, integrated DPMI, 32-bit
The fd32 project works or worked on the DPMI aspect. As far as I
On 03/05/2013 15:55, Tom Ehlert wrote:
In the past, we compiled kernels for 8086, 186 and
386 separately afair. I guess we got lazy and have
dropped 186 because very few users have 186/286 as
their CPU? They either have modern or REALLY old.
this is not about 'lazy'
it's easier for the user
Haha...I'd be interested if you ever developed a 586 core at 1GHz that
could utilize DDR-3 upto 4GB.
On Sat, May 4, 2013 at 1:43 AM, ht-lab han...@ht-lab.com wrote:
On 03/05/2013 15:55, Tom Ehlert wrote:
In the past, we compiled kernels for 8086, 186 and
386 separately afair. I guess we
On Fri, May 3, 2013 at 4:02 AM, Eric Auer e.a...@jpberlin.de wrote:
Hi Louis,
if I understand your patch correctly, you only changed the
build configuration to check how it affects the size of
the compiled kernel before UPX compression, which also is
an indicator of RAM size of the kernel?
What's the difference between wcc wcc386? I noticed that wcc386 adds
-5s, -5r, -fp5 (-6 equivalents) for stack, register and fpu optimization.
Does wcc386 generate code that could be used in the kernel?
-L
On Fri, May 3, 2013 at 5:57 AM, Louis Santillan lpsan...@gmail.com wrote:
On Fri,
Kernels with FAT32:
086: 68358 bytes
186: 67180 bytes (286 same)
386: 66044 bytes
486: 65948 bytes (586 and 686 same)
It is interesting that even 186 instructions do make a
quite big difference and that there is a difference at
all between 386 and 486. With 186, you get pusha and
What's the difference between wcc wcc386?
code generation for 16 bit (DOS) or 32 bit (windows)
Does wcc386 generate code that could be used in the kernel?
no
Big wins could be had on 586 with FPU memcpy 64-bit versus the 16-bit asm
in the kernel now and possibly the string functions.
