Who is making the Batch file based installer for FreeDOS 1.2?
I will be more than happy to answer any questions on V8Power Tools
implementation, theory and advanced techniques for
building the FreeDOS Installers User Interface.
If it is alright,I will make the installer.I haven't made any PHYSICAL
programs yet (besides making suggestions).So I will do it.
On Mon, Sep 7, 2015 at 4:51 AM, Jerome E. Shidel Jr.
wrote:
> Who is making the Batch file based installer for FreeDOS 1.2?
>
> I will be more
I don’t know if Jim had anyone specific in mind to write it. But, I don’t think
he does. So, I say “give it a shot”
Make sure you check out the EXAMPLES Batch files for V8Power Tools. They cover
may advanced V8PT
usages, vchoice selections and polling, drive scanning and etc.
The latest
Maybe, I should just write it.
> On Sep 7, 2015, at 1:33 PM, Jerome E. Shidel Jr. wrote:
>
> I just checked Jim’s FreeDOS blog posts. They currently only go back a little
> over 2 years. But, other than Jim’s desires for the batch based installer and
> information about my
I'm not 100% sure anymore, but I vaguely recall "Mercury Thirteen"
saying he's working on v1.2 (there was also an announcement on the FD
website at some point about that).
Mateusz
On 07/09/2015 13:51, Jerome E. Shidel Jr. wrote:
> Who is making the Batch file based installer for FreeDOS 1.2?
I just checked Jim’s FreeDOS blog posts. They currently only go back a little
over 2 years. But, other than Jim’s desires for the batch based installer and
information about my V8PT utilities, I don’t see that anyone was creating an
installer.
> On Sep 7, 2015, at 12:56 PM, Mateusz Viste
That's what I saw at some point on the freedos website:
http://sourceforge.net/p/freedos/news/2014/12/working-towards-freedos-12/
> Maybe, I should just write it.
That would probably be the most efficient solution, yes. :)
Note, that I already put together a whole bootable CD (all_cd.iso) with
I compiled the packages and verified the .lsm files and structured them
into a zip. Jim himself said there is an installer he's working on,
which is what's I've been waiting on. Since Jim doesn't seem to have
much free time (like many of us) I would say go for it.
On 9/7/2015 12:56 PM, Mateusz
On 9/7/2015 6:37 PM, Michael Brutman wrote:
...
I think that whether it is open source or not it is still a great
solution for DOS networking. If the lack of source code prevents you
from using mTCP I regret that and I encourage you to question your
assumption that without source code it
Hello all,
I just picked a random email, but thanks for all the answers. :p
Op 7 sep. 2015 22:37 schreef "Barry de Graaff" :
>
> > Why is it important to have it open source?
>
> Because:
>
> 1. I do read the source, and also compare between versions the changes so
I can
Hi,
Please don't panic. There are better things to worry about. Just to
clarify:
- The source for the 2013-05-23 version is available and always will be.
That particular release was probably near perfect because very few people
ever ask for more features or send bug reports.
- The source for
Sadly, it would mean that specific version of mTCP could not be included in FD.
On Mon, Sep 7, 2015 at 8:31 PM, Mercury Thirteen
wrote:
>
>
> On 9/7/2015 6:37 PM, Michael Brutman wrote:
>
> ...
> I think that whether it is open source or not it is still a great solution
No, I understand that. I mean nothing would prevent a user from manually
utilizing it in the future if they deem it necessary.
On 9/7/2015 11:33 PM, Louis Santillan wrote:
> Sadly, it would mean that specific version of mTCP could not be included in
> FD.
>
> On Mon, Sep 7, 2015 at 8:31 PM,
Hello Mike,
Thanks for your clarification, it makes things clear for me, and I imagine it
will also be read by a lot of people browsing thru the mail archive.
It's great to hear you also work towards ipv6! I was meaning to ask you about
that for some time.
For those not knowing mTCP is more
On 9/7/2015 1:36 PM, Barry de Graaff wrote:
> Why is it important to have it open source?
Because:
1. I do read the source, and also compare between versions the changes so I can
decide if I need/want the new changes.
2. I actually change software from time to time and also merge my changes
I've never been able to get a working DOS network.I can't even get my
FreeDOS laptop to 'talk' to my windows desktop.
On Mon, Sep 7, 2015 at 2:10 PM, Ralf Quint wrote:
> On 9/7/2015 1:36 PM, Barry de Graaff wrote:
>
> > Why is it important to have it open source?
>
>
After playing around with a making prototype installer this is a more or less
first part. It is extremely slow running from a floppy (even in vmware). It
might be a good idea for whoever makes the installer to first copy stuff to a
ram drive or enable disk caching or something to boost
On Mon, 7 Sep 2015, Maarten Vermeulen wrote:
Hi,
My question here is why do you want that. I don't want to be irritating
(which I probably am now).
Why is it important to have it open source?
It's FreeDOS, after all. Can't include stuff that isn't Free®™© ;)
However, it's my personal
> Why is it important to have it open source?Because:1. I do read the source,
> and also compare between versions the changes so I can decide if I need/want
> the new changes.2. I actually change software from time to time and also
> merge my changes upstream3. I prefer free-software out of
Hello, Maarten!
Em Mon, 7 Sep 2015 20:40:56 +0200
Maarten Vermeulen escreveu:
> Why is it important to have it open source?
Please, see "Why we must insist on Free Software"[0] and "Why 'Open
Source' misses the point of Free Software"[1].
Just my 2 cents.
Footnotes:
Hi Maarten, Barry, Bruno and of course Michael,
> Why is it important to have it open source?
While I have not read this code either, nor contributed
to it, I generally appreciate a possibility to read it.
In that sense, it is a pity that code currently is not
open. I am sure there would be
21 matches
Mail list logo