On Sat, 16 May 2015, Louis Santillan wrote:
On Sat, May 16, 2015 at 7:44 PM, JK Benedict xenfomat...@outlook.com wrote:
[SNIP]
- Base resources, such as file system options/changes
- Connectivity tools
* Modernized web browser (I am working on one now - a text based
prototype)
I think the original goal of FreeDOS has been met, based upon what I
remember from back in 2000 or so when I came across the project. I have
seen many posts back and forth about adding support for this and that
because Windows sucks and so forth and so on.
With that being said, here's what I see.
Completely agree as the web today reveals two things:
- How heavy it is
- How bloated it is
--jkbs
-Original Message-
From: Louis Santillan [mailto:lpsan...@gmail.com]
Sent: Sunday, May 17, 2015 1:52 AM
To: Technical discussion and questions for FreeDOS developers.
Subject: Re:
Excellent.
Daily builds was just an example and I agree, daily builds would be
overkill.
The angle I was coming from is when core changes start to be made. How
will this affect the 100 packages when core, resource, and drivers are
re-tooled? DOS is heavily classic, solid... but some of the
Hi Jesse,
Centralized documentation makes sense, but why
would you put 100 packages in a centralized
source code repository if 95 of them have not
a single source code change in a whole year?
And why do nightly builds of all 100 then? DOS
heavily relies on classic software that simply
is okay
There is WIFI drivers available,but they are often made for a specific
wireless card.Your best bet is to make a driver that can interpret ethernet
signals.Since information is coming from the internet to the ethernet
cables,you can get information/data from the internet using a parallel port
