Expounding a bit on all the options and variations which have been
presented in this 32- vs. 16-bit debate:
1 - Two separate kernels (one 16-bit and one 32-bit) with a mechanism which
auto-detects what CPU it's running on and launches the appropriate kernel
automatically. Maintains 100% hardware and software compatibility, and
would potentially cut down on bloat since the installer could alternately
detect the user's processor ahead of time and install only the most
well-suited kernel for the user's machine.
2 - A single kernel which contains provisions for both protected and real
modes, auto-detects what CPU it's running on and launches into protected
mode automatically if it's supported but stays in real mode if not.
Maintains 100% hardware and software compatibility at the expense of a
larger kernel.
3 - A single kernel which supports only 386 and newer processors and always
runs in protected mode. Loses hardware compatibility for computers with 286
or earlier processors but maintains 100% software compatibility.
4 - Keep the same great 16-bit kernel we all know and love. Maintains 100%
hardware and software compatibility.
Note that only options 1, 2 and 4 keep 100% compatibility with both DOS
applications and the full range of PC hardware. Option three would
modernize the kernel the most, but I think we all agree we cannot isolate
any members of our installed base like that. None of these options involve
any kind of emulation software, although options 1 and 2 would rely on the
processor's built-in virtual x86 mode which, despite it's name, is not
(strictly speaking) an emulator but simply real mode with the on-chip MMU -
normally deactivated in real mode - left activated.
Not meaning to keep the debate going, just summarizing as it winds to a
close. This has been a most interesting discussion. :)
Merc
On Mon, Jan 5, 2015 at 4:58 PM, Travis Siegel <tsie...@softcon.com> wrote:
> +1
> On Jan 4, 2015, at 11:27 PM, Jim Hall wrote:
>
> > I'm traveling, and likely won't be able to check email again or update
> the
> > roadmap on the wiki until Wednesday. With a few disagreements, it looks
> > like the consensus remains this:
> >
> >
> > *- "FreeDOS 1.2" should be an update/refresh from FreeDOS 1.1. No major
> > changes. Improved installer is a good idea.*
> >
> > *- "FreeDOS 2.0" should be 16-bit. Make FreeDOS feel more modern, but
> keep
> > it "DOS." We can improve the userspace. Keep supporting old PCs, but
> > support new hardware where we can. UEFI may be tricky (see SeaBIOS
> > discussion).*
> >
> > *- If FreeDOS-32 will break DOS application compatibility, it should not
> > use the "FreeDOS" name.*
> >
> >
> > This seems a clear direction.
> >
> > I'll admit that I'm curious what the kickstarter might achieve, but I'm
> not
> > hopeful. So while a FreeDOS-32 kernel that ran 16-bit apps while adding
> new
> > features would be very cool, it doesn't seem realistic. And it breaks
> > hardware compatibility anyway. So let's take it off the roadmap.
> >
> > If they can demonstrate feasibility of FreeDOS-32 running 16-bit programs
> > while adding new features, we can consider it and discuss it at that
> time.
> > But I don't think we want to forecast it for a release (that is, not 2.0
> or
> > 3.0 ... it's up to them to demonstrate feasibility, then we'll pick up
> the
> > topic again.)
> >
> > If no serious disagreements with the above, I think we can consider this
> > topic done, and I'll update the roadmap on the wiki later this week.
> >
> > If you agree, please reply with "+1".
> >
> > If you disagree, please share your thoughts by Tuesday.
> >
> > Sound fair?
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
