So, to summarize what I'm hearing, FreeDOS 2.0 could be made to detect the
CPU on which its running and branch accordingly. If it was a 386 or better,
we enter protected mode and use a V86 monitor to spawn multiple 16-bit app
spaces using the chip's built-in virtualization hardware. If it's a 286 or
lower, we stay in real mode and operate normally. Either way we obtain
maximum speed, efficiency and power and maintain *100%* hardware and
software compatibility. The user doesn't have to worry about anything or do
any kind of customization, as the kernel itself would decide how to act
appropriate in the proper situation.
Another thing to think of, *if* this route would be taken, is that we may
be the only group who could pull it off. The FreeDOS-32 project has been
going for how long now? And without a single release to show for it?
Meanwhile you guys here created a fully functional, bug free DOS
replacement / enhancement. Amazing. I agree with Mike here - I foresee
*zero* programmers stepping forth to fill this niche. Hey, if they pull it
off, more power to them! I wish them no ill will. But being realistic about
it... I don't see it going anywhere.
Heck, I've been registered on Freelancer for awhile now. I'll take the
$2500 and do it myself if they're that serious about it! lol :P
On Sat, Jan 3, 2015 at 3:15 PM, Aitor Santamaría <aitor...@gmail.com> wrote:
> Hello,
>
> 2015-01-03 19:14 GMT+01:00 Travis Siegel <tsie...@softcon.com>:
>
>>
>> On Jan 1, 2015, at 3:46 AM, Mercury Thirteen wrote:
>>
>> > I too would love to see a fully modern DOS.
>>
>> As would I, and I believe everything mentioned in the email would be
>> perfect for a 32-bit dos. I believe it can be done, and the whole give
>> each program it's own virtual 86 machine is one I've wondered about for
>> quite sometime. It shouldn't be difficult, and actually, I read somewhere
>> that the initial version of windows did this, but of course, I can't
>> confirm that, since the only version of windows 1.0 I ever had was on an xt
>> where such a scheme wouldn't have worked anyhow, not to mention, I haven't
>> a clue where that machine wound up at. :)
>> Otherwise, each program being spawned in it's own virtual 86 machine, and
>> leaving things in protected mode as much as possible makes perfect sense to
>> me, and it was what I'd figured would happen to dos eventually, but it
>> never did.
>>
>
> It actually did!
> This is exactly what I was trying to explain, this is the way Microsoft
> took, as this is what VMM32.VXD=DOS386.EXE does (a much overpowered
> EMM386.EXE).
> But Microsoft didn't sell this piece of software with MS-DOS, but with
> MS-Windows.
>
> Cheers,
> Aitor
>
>
>
>
>
>
>>
>> ------------------------------------------------------------------------------
>> 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
>
>
------------------------------------------------------------------------------
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
