Hello,
On Sun, 29 Jan 2023 at 22:59, Jim Hall wrote:
> I think Microsoft would have had to find a way around the obvious
> limitations in DOS, inherent in an operating system from 1981. With
> more powerful CPUs, more memory, and networking, you need a more
> powerful operating system. Let's
On Sun, 29 Jan 2023 at 22:59, Jim Hall wrote:
>
> The thought experiment starts with: What might have happened if
> Microsoft had decided to keep "DOS" and not go the "Windows" route? A
> command line operating system, but one that takes advantage of newer
> hardware features?
Microsoft *did.*
Replying to my own comment:
On Sun, Jan 29, 2023 at 3:28 PM Jim Hall wrote:
>[..]
> Sifting through the several conversation threads on this, I think the
> only project that would really be worth "Google Summer of Code" is a
> "loader" to boot FreeDOS on new machines.
[..]
This reminds me of a
On Fri, Jan 27, 2023 at 10:09 AM Wilhelm Spiegl wrote:
>
> While this discussion is miles away from my original proposal,
> I understand that my proposal with GSoC is buried. Thanks for this
> interesting discussion.
Sifting through the several conversation threads on this, I think the
only
On Sun, Jan 29, 2023 at 7:19 AM tom ehlert wrote:
[..]
> after all, an OS is not an end target:
> people need the OS to run their applications like
>
> 1. Play classic DOS games.
>
> 2. Run legacy software.
>
> 3. Develop embedded systems.
>
> none of this is open source.
Liam wrote: [response
On Sun, 29 Jan 2023, tom ehlert wrote:
but I think the black box with the command prompt in Windows is indead
often called the DOS VM or DosBox.
DOS Virtual Machine, yeah.
-uso.
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
>>> whatever EMM386 and friends was and is, it is definitively not what
>>> people think when they hear 'DOS VM'. you are abusing words to make a
>>> point. not good.
>> I don't really care. I am talking about how existing DOS 386 memory
>> managers have worked for 35+ years now.
>> The 80386
> I know. I am a professional in this field and have been since 1988.
> Please do me the courtesy of imagining that I know what I am talking
> about.
according to https://cz.linkedin.com/in/liamproven
FOSS and cloud reporter · Freelance writer and English teacher · Technical
writer/editor ·
>> 3. Develop embedded systems.
> Not sure that's important in 2023. Any citations?
http://wiki.freedos.org/wiki/index.php/Main_Page
>> whatever EMM386 and friends was and is, it is definitively not what
>> people think when they hear 'DOS VM'. you are abusing words to make a
>> point. not
On Fri, 27 Jan 2023 at 15:23, tom ehlert wrote:
>
> this argument is nonsense. many/most people don't care about the 'open source'
> part as long as it's free.
I disagree. I think it's perfectly fair to say "FreeDOS does not
support MS Windows" and end it there.
> most care more if this OS
On Fri, 27 Jan 2023, tom ehlert wrote:
this argument is nonsense. many/most people don't care about the 'open source'
part as long as it's free.
This.
most care more if this OS supports big disks or much memory.
after all, an OS is not an end target:
people need the OS to run their
n and questions for FreeDOS developers."
Subject: Re: [Freedos-devel] Google Summer of Code?
Hallo Herr Liam Proven,
> I suppose my first suggestion would be: sod Windows.
> A suggestion of a justification:
> If people want a FOSS DOS then they must use a FOSS GUI, and if
Hallo Herr Liam Proven,
> I suppose my first suggestion would be: sod Windows.
> A suggestion of a justification:
> If people want a FOSS DOS then they must use a FOSS GUI, and if they
> want a proprietary GUI then they must accept that also means a
> proprietary DOS underneath.
this argument
On Mon, 23 Jan 2023 at 18:55, Bret Johnson wrote:
Hi Bret. Thanks for the long and considered reply.
I do not know why you conflated 2 different people's emails into one
reply, though, also stripping out the identifying info, but I will
only attempt to reply to the part that addressed my email.
On Sat, Jan 21, 2023 at 4:08 PM Jim Hall wrote:
> So let's discuss:
>
> What core programs or components should we put into the application -
> if we apply and can get accepted?
For 386+ machines, what about an installer based on Linux that doesn’t need
to reboot multiple times to install to
On 1/22/2023 11:30 PM, Robert Riebisch wrote:
Hi Liam,
"All" it needs is a memory manager that can start as a 32-bit process,
set up a few interrupts -- INT 11 for the hard disk, for instance --
INT 11?
Hard disk is Int 13h.
Yup, INT 11h is getting BIOS equipment list. Give him the benefit
Hi Bret,
Yep! You said it all much better and in far greater detail than I went into.
Thanks. :-)
Jerome
> On Jan 23, 2023, at 1:54 PM, Bret Johnson wrote:
>
>
>>
>> by the way, the 2 programs are the setup stuff and edlin. hardly
>> rocket science.
>
> Even those two "simple"
> by the way, the 2 programs are the setup stuff and edlin. hardly
> rocket science.
Even those two "simple" programs would probably be considered "rocket science",
or at least akin to "learning a foreign language", by most students who are
only used to modern technology and web apps.
Hi,
> On Jan 22, 2023, at 4:37 PM, Liam Proven wrote:
>
> On Sun, 22 Jan 2023 at 22:11, Jerome Shidel wrote:
>>
>> Assuming Google does not scrap GSoC amidst the layoffs, I have a thought.
>>
>> Perhaps it could be used to solve one of the most frequent problems I hear.
>> Running FreeDOS
Hi Liam,
> "All" it needs is a memory manager that can start as a 32-bit process,
> set up a few interrupts -- INT 11 for the hard disk, for instance --
INT 11?
Hard disk is Int 13h.
Cheers,
Robert
--
BTTR Software https://www.bttr-software.de/
DOS ain't dead
On Sun, 22 Jan 2023 at 22:11, Jerome Shidel wrote:
>
> Assuming Google does not scrap GSoC amidst the layoffs, I have a thought.
>
> Perhaps it could be used to solve one of the most frequent problems I hear.
> Running FreeDOS on modern UEFI hardware.
>
> As we are all well aware, this cannot be
On Sun, 22 Jan 2023, Jerome Shidel wrote:
Assuming Google does not scrap GSoC amidst the layoffs, I have a
thought.
Perhaps it could be used to solve one of the most frequent problems I
hear. Running FreeDOS on modern UEFI hardware.
As we are all well aware, this cannot be directly
Assuming Google does not scrap GSoC amidst the layoffs, I have a thought.
Perhaps it could be used to solve one of the most frequent problems I hear.
Running FreeDOS on modern UEFI hardware.
As we are all well aware, this cannot be directly accomplished and would
require an abstraction layer
Hello,
It is a good idea to apply to GSoC; but I reckon there won’t be many students
to select it. It sounds like giving a toddler a broom to clean an attic, while
the rest of the family is chilling downstairs.
- There is no single code base, everything is scattered. Scary.
- There is no
> > What core programs or components should we put into the application -
> > if we apply and can get accepted?
On Sun, Jan 22, 2023 at 12:11 PM Robert Riebisch wrote:
> A mouse-driven GUI...
>
> SCNR :-D
Funny! :-)
Mouse-driven GUI is always at the top of the list for new DOS
developers,
On 1/22/2023 10:28 AM, Robert Riebisch wrote:
Hi Ralf,
So let's discuss:
What core programs or components should we put into the application -
if we apply and can get accepted?
A mouse-driven GUI...
SCNR :-D
No, PLEASE, NO!
Was just kidding...
You DID notice the smiley at the end,
Hi Ralf,
>>> So let's discuss:
>>>
>>> What core programs or components should we put into the application -
>>> if we apply and can get accepted?
>> A mouse-driven GUI...
>>
>> SCNR :-D
>>
> No, PLEASE, NO!
Was just kidding...
Cheers,
Robert
--
BTTR Software https://www.bttr-software.de/
On 1/22/2023 10:11 AM, Robert Riebisch wrote:
Hi Jim,
So let's discuss:
What core programs or components should we put into the application -
if we apply and can get accepted?
A mouse-driven GUI...
SCNR :-D
No, PLEASE, NO!
___
Freedos-devel
Hi Jim,
> So let's discuss:
>
> What core programs or components should we put into the application -
> if we apply and can get accepted?
A mouse-driven GUI...
SCNR :-D
Cheers,
Robert
--
BTTR Software https://www.bttr-software.de/
DOS ain't dead https://www.bttr-software.de/forum/
Chris DiBona, the Senior Director of Open Source at Google was caught in
the massive wave of lay-offs that Google executed this past Friday. His
group is responsible for the Summer of Code. The departure of specific
people might not have an impact, but I would still try to be realistic
about
> Am 22.01.2023 um 03:46 schrieb Michael Brutman :
>
> I don't think you are going to get too far with an application ... I hate to
> be so blunt here, but it takes more than just being open source. It has to
> be a project with significant impact, and I think that FreeDOS is way too
>
I don't think you are going to get too far with an application ... I hate
to be so blunt here, but it takes more than just being open source. It has
to be a project with significant impact, and I think that FreeDOS is way
too niche to be considered.
You're going to be competing against many
Willi mentioned the Google Summer of Code, and I wanted to start a new
thread here for us to discuss the program:
I'd love for FreeDOS to participate in Google Summer of Code. IIRC,
this program doesn't require the participating open source projects to
have funds to join? [website is
On Mon, Sep 5, 2022, 1:29 PM Wilhelm Spiegl wrote:
> Hi Paul,
> did you or Jim or somebody else think about Google summer of code for
> FreeDOS, e.g. 2023 as this summer is almost over? Just a (bad) idea.
>
> https://summerofcode.withgoogle.com/
>
GSoC is a good idea, we should think about
34 matches
Mail list logo
