Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi again,

On Wed, Feb 15, 2023 at 6:30 PM Rugxulo  wrote:
>
> FreeBASIC started in 2004 written in VBDOS (I think??) until it was
> able to compile itself. The whole PDS suite was mainly about
> supporting both DOS and OS/2 (until IBM and MS parted ways). Visual
> BASIC never had any further DOS releases and focused more on Windows
> (and not OS/2 either). The famous "QBASIC" interpreter was originally
> included in MS-DOS 5 (and supposedly others like OS/2 and NT). I don't
> even know if modern Windows includes VBScript anymore.
>
> FreeBASIC does have support for "REM $lang qb", but it's incomplete.
> Having said that, I did write a few scripts that intentionally work
> (and were tested) under both. So that is okay, as long as it runs on
> both. The advantage would be that deploying a script is easy if
> everyone already has one or the other.

I had thought "OPTION EXPLICIT" debuted in VBDOS, but I could be
wrong. (The default improved FBC dialect makes everything explicit
anyways.)

* https://www.freebasic.net/wiki/KeyPgOptionexplicit

Another feature I thought was first in VBDOS was "REDIM PRESERVE", but
the FBC wiki says it debuted in PDS.

* https://www.freebasic.net/wiki/KeyPgPreserve

I would be curious to know definitively from someone with more
experience (e.g. Ralf Q. or Steve N.).


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Roni Rider]

Really amazing your email!

Could you send to us some screeenshoots of this system?

Do you have some problems with the database files or some limitations
because of this technology?

Tell me more, I work as developper here in Canada

I really like this kind of situation

Ps: Sorry about my bad english

Le jeu. 16 févr. 2023 à 12:43, Jürgen Wondzinski  a
écrit :

> Just to chime in: There's still software in use written in FoxPro/DOS from
> 1994 :)
>
> In fact, I'm just upgrading and enhancing such a package. It's running
> from an USB-Stick (with FreeDos of course), which is plugged into a
> smallsized HP ThinClient. That beast is used in Delivery-cars, which sell
> flowers to gas-stations all over Germany. It will get replaced by a WebApp
> on Ipads, but until then it is doing it's job now since 25 years :)
>
>
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Rugxulo 
> Gesendet: Donnerstag, 16. Februar 2023 01:31
> An: Discussion and general questions about FreeDOS. <
> freedos-user@lists.sourceforge.net>
> Betreff: Re: [Freedos-user] Anyone want to write an article about FreeDOS?
>
> Hi,
>
> From a practical standpoint, the only "Turbo Pascal for DOS" that is
> readily available anymore is "old 5.5" (freeware, non-redistributable). So
> it's not even the full TP 7 dialect. So you do get actual improvements and
> newer features in other compilers with their "turbo" dialect (e.g. FPC).
>
> Even ignoring FPC (which is wonderful), the "de facto" Pascal standard
> long ago was "turbo" in lieu of either of the "official" standards (ISO
> 7185, 10206). Even Niklaus Wirth himself (whose birthday is
> today!) long ago jumped ship to other languages (e.g. Oberon-07).
>
> Heck, Delphi is 28 years old as of yesterday! (Quoting Marco Cantu):
> "As a commenter wrote, Delphi was VB done right. With the original native
> VB long abandoned by Microsoft, and VB.NET 'nearly frozen', Delphi has
> kept more steam and has remained a viable option over the years." [FPC
> supports a large subset of Delphi.]
>
> So why use old dialects at all? Part of it is just a challenge to see if
> it can be done. Part of it is just minimalism or reducing complexity or
> avoiding unnecessary modern features. It's also just for strict
> compatibility (rarely needed but still valid).
>
> A newer language or toolset doesn't necessarily share all the advantages
> of the older one. There are advantages and disadvantages to each.
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
-- 
*Roni  Martins *
| Software Development and Research
| T: +1  418 2613965
| e-mail: roni.jose.mart...@gmail.com
| web site: http://www.ronimartins.com
| LinkedIn Profile: *https://br.linkedin.com/in/ronimartins
<https://br.linkedin.com/in/ronimartins>*
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Ralf Quint]

On 2/16/2023 5:59 AM, Jürgen Wondzinski wrote:

Just to chime in: There's still software in use written in FoxPro/DOS from 1994 
:)

In fact, I'm just upgrading and enhancing such a package. It's running from an 
USB-Stick (with FreeDos of course), which is plugged into a smallsized HP 
ThinClient. That beast is used in Delivery-cars, which sell flowers to 
gas-stations all over Germany. It will get replaced by a WebApp on Ipads, but 
until then it is doing it's job now since 25 years :)


Yeah, but that's not Open Source! :P


Ralf ;-)




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jürgen Wondzinski]

Just to chime in: There's still software in use written in FoxPro/DOS from 1994 
:) 

In fact, I'm just upgrading and enhancing such a package. It's running from an 
USB-Stick (with FreeDos of course), which is plugged into a smallsized HP 
ThinClient. That beast is used in Delivery-cars, which sell flowers to 
gas-stations all over Germany. It will get replaced by a WebApp on Ipads, but 
until then it is doing it's job now since 25 years :)




 

-Ursprüngliche Nachricht-
Von: Rugxulo  
Gesendet: Donnerstag, 16. Februar 2023 01:31
An: Discussion and general questions about FreeDOS. 

Betreff: Re: [Freedos-user] Anyone want to write an article about FreeDOS?

Hi,

>From a practical standpoint, the only "Turbo Pascal for DOS" that is readily 
>available anymore is "old 5.5" (freeware, non-redistributable). So it's not 
>even the full TP 7 dialect. So you do get actual improvements and newer 
>features in other compilers with their "turbo" dialect (e.g. FPC).

Even ignoring FPC (which is wonderful), the "de facto" Pascal standard long ago 
was "turbo" in lieu of either of the "official" standards (ISO 7185, 10206). 
Even Niklaus Wirth himself (whose birthday is
today!) long ago jumped ship to other languages (e.g. Oberon-07).

Heck, Delphi is 28 years old as of yesterday! (Quoting Marco Cantu):
"As a commenter wrote, Delphi was VB done right. With the original native VB 
long abandoned by Microsoft, and VB.NET 'nearly frozen', Delphi has kept more 
steam and has remained a viable option over the years." [FPC supports a large 
subset of Delphi.]

So why use old dialects at all? Part of it is just a challenge to see if it can 
be done. Part of it is just minimalism or reducing complexity or avoiding 
unnecessary modern features. It's also just for strict compatibility (rarely 
needed but still valid).

A newer language or toolset doesn't necessarily share all the advantages of the 
older one. There are advantages and disadvantages to each.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Tue, Feb 14, 2023 at 11:21 AM Jim Hall  wrote:
>
> > In other words, you probably can't talk about "Turbo Pascal" proper,
> > only the dialect as used in either GPC or FPC or p2c. They don't want
> > you promoting or pointing people to proprietary software.
>
> Correct, you shouldn't write about proprietary software for
> Opensource.com. One exception is if you're writing about "open source
> alternatives to proprietary software." So writing a "(Free)DOS
> programming with Pascal" article that uses FreePascal is great; a
> Pascal article that uses TurboPascal would probably get rejected.

>From a practical standpoint, the only "Turbo Pascal for DOS" that is
readily available anymore is "old 5.5" (freeware,
non-redistributable). So it's not even the full TP 7 dialect. So you
do get actual improvements and newer features in other compilers with
their "turbo" dialect (e.g. FPC).

Even ignoring FPC (which is wonderful), the "de facto" Pascal standard
long ago was "turbo" in lieu of either of the "official" standards
(ISO 7185, 10206). Even Niklaus Wirth himself (whose birthday is
today!) long ago jumped ship to other languages (e.g. Oberon-07).

Heck, Delphi is 28 years old as of yesterday! (Quoting Marco Cantu):
"As a commenter wrote, Delphi was VB done right. With the original
native VB long abandoned by Microsoft, and VB.NET 'nearly frozen',
Delphi has kept more steam and has remained a viable option over the
years." [FPC supports a large subset of Delphi.]

So why use old dialects at all? Part of it is just a challenge to see
if it can be done. Part of it is just minimalism or reducing
complexity or avoiding unnecessary modern features. It's also just for
strict compatibility (rarely needed but still valid).

A newer language or toolset doesn't necessarily share all the
advantages of the older one. There are advantages and disadvantages to
each.

> > I don't think they are sympathetic to the history of QB, PDS, VBDOS.
> > (Steve Nikolas is the resident BASIC expert around here.)
>
> "History of programming" articles can be okay, but I'd guess the
> editors would look for the article to turn to open source options.
> That's what I'd look for, if I read the article. For example, an
> article about the history of BASIC might highlight a few variants like
> AppleSoft BASIC, BASICA, GW-BASIC, QuickBASIC/QBASIC, and FreeBASIC.
> Most of those are proprietary; GW-BASIC was made open source a few
> years ago, and FreeBASIC is GNU GPL. As a suggestion: You might make
> the focus into something like "[most] programs written for an earlier
> BASIC should work fine on a later BASIC, and that's the cool thing
> about BASIC backwards compatibility .. it's just BASIC." Or something
> like that. I am not an editor on the site, but my guess is they would
> like that. You can always email the editors to ask them.

FreeBASIC started in 2004 written in VBDOS (I think??) until it was
able to compile itself. The whole PDS suite was mainly about
supporting both DOS and OS/2 (until IBM and MS parted ways). Visual
BASIC never had any further DOS releases and focused more on Windows
(and not OS/2 either). The famous "QBASIC" interpreter was originally
included in MS-DOS 5 (and supposedly others like OS/2 and NT). I don't
even know if modern Windows includes VBScript anymore.

FreeBASIC does have support for "REM $lang qb", but it's incomplete.
Having said that, I did write a few scripts that intentionally work
(and were tested) under both. So that is okay, as long as it runs on
both. The advantage would be that deploying a script is easy if
everyone already has one or the other.

Later versions of PC-DOS included REXX instead of QBASIC, also a cool
language. I've written some scripts that were adjusted to run on
various REXX interpreters too (not as easy as it sounds!). So, again,
as long as it (also) runs on Regina, it's okay.

This is the (hypothetical) advantage of "standards". But in reality it
takes modularity, preprocessor, patches, and other fixes due to bugs
or omissions or incompatible dialects. But non-portability can
(mostly) be mitigated with a little extra work. (But never assume it
works everywhere until you test it! Even AWK or Sed can have that
problem.)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

> > On 2/6/2023 5:40 PM, Rugxulo wrote:
> > > Would you prefer an article on Pascal? I know you (also) are a fan of
> > > it. An article from your experience there might be useful.

> On Mon, Feb 6, 2023 at 9:49 PM Ralf Quint  wrote:
> > No, kind of programming language agnostic, with examples in BASIC, Turbo
> > Pascal, C and assembler. As mentioned, it will be about programming in
> > DOS for DOS.

On Mon, Feb 13, 2023 at 8:34 PM Rugxulo  wrote:
> Just a caveat: I think they want only "open source" tools. And,
> although they list OSI approved licenses, I would be surprised if they
> were sympathetic to OpenWatcom (Sybase v1).

I've written a few articles for Opensource.com that use OpenWatcom on
FreeDOS. For example, the "conio" article used OpenWatcom.

That said, any other articles I write about conio will probably use TK
Chia's IA-16 libi86. But that's just because I love the work on IA-16
GCC.


[..]
> In other words, you probably can't talk about "Turbo Pascal" proper,
> only the dialect as used in either GPC or FPC or p2c. They don't want
> you promoting or pointing people to proprietary software.

Correct, you shouldn't write about proprietary software for
Opensource.com. One exception is if you're writing about "open source
alternatives to proprietary software." So writing a "(Free)DOS
programming with Pascal" article that uses FreePascal is great; a
Pascal article that uses TurboPascal would probably get rejected.

("Open source alternatives" is always a popular topic, by the way. If
anyone wants to write an article about "Open source alternatives to
proprietary DOS software that you can run on FreeDOS in 2023," I'm
pretty sure the editors would go for that. My example is a very long
title; the editors can help you with the title.)


[..]
> I don't think they are sympathetic to the history of QB, PDS, VBDOS.
> (Steve Nikolas is the resident BASIC expert around here.)

"History of programming" articles can be okay, but I'd guess the
editors would look for the article to turn to open source options.
That's what I'd look for, if I read the article. For example, an
article about the history of BASIC might highlight a few variants like
AppleSoft BASIC, BASICA, GW-BASIC, QuickBASIC/QBASIC, and FreeBASIC.
Most of those are proprietary; GW-BASIC was made open source a few
years ago, and FreeBASIC is GNU GPL. As a suggestion: You might make
the focus into something like "[most] programs written for an earlier
BASIC should work fine on a later BASIC, and that's the cool thing
about BASIC backwards compatibility .. it's just BASIC." Or something
like that. I am not an editor on the site, but my guess is they would
like that. You can always email the editors to ask them.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Mon, Feb 6, 2023 at 9:49 PM Ralf Quint  wrote:
>
> On 2/6/2023 5:40 PM, Rugxulo wrote:
> > Would you prefer an article on Pascal? I know you (also) are a fan of
> > it. An article from your experience there might be useful.
> No, kind of programming language agnostic, with examples in BASIC, Turbo
> Pascal, C and assembler. As mentioned, it will be about programming in
> DOS for DOS.

Just a caveat: I think they want only "open source" tools. And,
although they list OSI approved licenses, I would be surprised if they
were sympathetic to OpenWatcom (Sybase v1).

Jim says "Microsoft MASM is out", but while JWasm (MASM v6 clone) is
OSI approved (and derived from OW's WASM), I don't think they care.

NASM has various DOS builds, e.g. 0.98.39 (2005, LGPL) for 8086 host
or 2.16.01 (2022, BSD) for 386 DJGPP (DPMI). Even TinyAsm (2020, BSD)
can be built for 8086 with either DeSmet C (your favorite, Ralf) or
IA16-GCC. (Maybe Oscar Toledo himself should write an article. He
already wrote some books.)

In other words, you probably can't talk about "Turbo Pascal" proper,
only the dialect as used in either GPC or FPC or p2c. They don't want
you promoting or pointing people to proprietary software.

> > I built and tested P5 Pascal (ISO 7185) with GPC (and GNU Make) for
> > DOS, Windows, and Linux.
>
> ISO 7185 is the worst thing that could happen to Pascal. Utterly useless
> and outdated by the time it was released.

It had some flaws (and workarounds), but I still like it a lot. I've
built P5 for us (via GPC) and emailed Scott Franco many times. I could
definitely write an article about that (and Modula-2, Oberon successor
languages). I have at least four interesting (well, to me) example
programs.

> Same as the standards for "minimal" and "extended" BASIC. There is not
> one mainstream BASIC implementation that is really sticking to either one..

At one time you were writing your own GW-BASIC clone, right? In recent
years I have written a few QBASIC scripts (that work in actual QB and
FreeBASIC's "$lang qb"). So I'm vaguely more familiar with that
(structured, not line numbered). I found BWBASIC too buggy. I never
played too much with other BASICs. P2c had its own Chipmunk BASIC.
(Heck, even Scott wrote a BASIC in Pascal.)

I don't think they are sympathetic to the history of QB, PDS, VBDOS.
(Steve Nikolas is the resident BASIC expert around here.)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Michael Brutman]

I initially mis-read what Tom had written about programming on DOS being
painful.  He is not wrong. ;-0  I program "for" DOS for the challenge.  But
I don't program too much "on" DOS, because I'm not interested in
challenging myself that much.

I used to use Turbo C++ 3.0 for DOS on a DOS machine for DOS programming.
10+ years ago I moved to Open Watcom 1.8 on a Windows machine for my DOS
programming.  With Cygwin I have a Unix-like environment.  I have multiple
windows for editing, web browser windows for looking up strange interrupts,
a PDF viewer, etc.  The performance of the modern machine is great compared
to ye old DOS machine.

There are some exceptions.  Turbo C++ 3.0 for DOS has a useful IDE, but I
can't read PDF files or look up things online from a DOS machine running it.


-Mike
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Daniel Essin via Freedos-user]

I think we're all here out of interest. i have a neighbor who "needs" yo run a 
dos app for his nusiness. He's the only one I know who "needs" to run dos. 
Everyone else does it out of interest who still has an ibm-pc or xt as their 
only computer?

That said, if someone "wants" to write dos programs, why not? And if you're 
looking for a retro experience, why a 20meg hard drive (I have one in my compaq 
portable III), why not dual floppies?

And, does anyone remember when Microsoft Access was a program to go online with 
your 300 baud modem to make airline reservations? I have that too, on 5.25 
flop;y. Works great in the compaq except there is no one to call with it 
anymore.

On Tue, Feb 7, 2023, at 10:25 AM, tom ehlert wrote:
>>> programming *on* DOS in the year 2023 is like self flagellation. you
>>> are absolutely allowed to do it; it's just not recommended.
>> Why not? It worked just fine for all intends and purposes for two 
>> decades, so why would that not be "recommended" to do so in 2023?
>
> because programming can be MUCH more productive when you have multiple
> windows open, each much better then 25*80, can google stuff while editing,
> look at your source while debugging and much more.
>
> it worked - yes. like a hand drill, and hand saw, or other late 1800 stuff.
> whatever you do - you are probably using electric stuff these days.
> unless you are an archeologist, trying to rebuild a medivial castel
> with medivial tools only.
>
>
>> That is the part that I think is the true fallacy that too many people
>> perpetrate these days, when claiming to be interested in (Free)DOS.
>
> when 'interested' in DOS, you should use edlin and a XT machine with a
> big 20 MB disk for the real experience.
>
> Tom
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[tom ehlert]

>> programming *on* DOS in the year 2023 is like self flagellation. you
>> are absolutely allowed to do it; it's just not recommended.
> Why not? It worked just fine for all intends and purposes for two 
> decades, so why would that not be "recommended" to do so in 2023?

because programming can be MUCH more productive when you have multiple
windows open, each much better then 25*80, can google stuff while editing,
look at your source while debugging and much more.

it worked - yes. like a hand drill, and hand saw, or other late 1800 stuff.
whatever you do - you are probably using electric stuff these days.
unless you are an archeologist, trying to rebuild a medivial castel
with medivial tools only.


> That is the part that I think is the true fallacy that too many people
> perpetrate these days, when claiming to be interested in (Free)DOS.

when 'interested' in DOS, you should use edlin and a XT machine with a
big 20 MB disk for the real experience.

Tom



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Ralf Quint]

On 2/7/2023 3:40 AM, tom ehlert wrote:

The use of (n)curses for example is a typical Unix thing, that has
nothing to do with DOS and should not be shoehorned into a DOS
application...

add DEVICE=ANSI.SYS to your config.sys and you can easily 'port'
(=compile and fix C compiler discrepacies) your curses  programs to
DOS.
Well, if you want to "port" an existing program from Unix/Linux to DOS, 
this would be a quick option, with all the added bloat...


programming *on* DOS in the year 2023 is like self flagellation. you
are absolutely allowed to do it; it's just not recommended.
Why not? It worked just fine for all intends and purposes for two 
decades, so why would that not be "recommended" to do so in 2023?
That is the part that I think is the true fallacy that too many people 
perpetrate these days, when claiming to be interested in (Free)DOS.



Ralf




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[tom ehlert]

> The use of (n)curses for example is a typical Unix thing, that has 
> nothing to do with DOS and should not be shoehorned into a DOS 
> application...

add DEVICE=ANSI.SYS to your config.sys and you can easily 'port'
(=compile and fix C compiler discrepacies) your curses  programs to
DOS.


>>
>>> Some *ix utilities MIGHT be useful for the use on DOS,
>> MKS Toolkit? GNUish? EMX? DJGPP? Heck, even Simtel and Garbo had a few.
> I said "some" utilities. Not everything plus the kitchen sink.
>>
>>
>> "The Lessons of Unix Can Be Applied Elsewhere"
>>
> Nice statement, but I think that this is wrong. And just for the record,
> I used my first Unix system before I used my first DOS system...
> Unix was from the start to be an abstraction of the hardware underneath,
> running on different hardware, usable with minimal knowledge of the 
> hardware (specially, CPU wise).
> DOS (as in MS-DOS/PC-DOS) is directly tied to the Intel 8086 CPU, it's
> segmented memory models, it's access to an underlying BIOS (and various
> extensions) on the hardware level and out of necessity, much more 
> reliant on direct access to the hardware underneath.
>>
>>> And yes, an article, possibly a series of articles, about programming on
>>> DOS, for DOS, will be forthcoming...

programming *on* DOS in the year 2023 is like self flagellation. you
are absolutely allowed to do it; it's just not recommended.

>> I built and tested P5 Pascal (ISO 7185) with GPC (and GNU Make) for
>> DOS, Windows, and Linux.

> ISO 7185 is the worst thing that could happen to Pascal. Utterly useless
> and outdated by the time it was released.
> Same as the standards for "minimal" and "extended" BASIC. There is not
> one mainstream BASIC implementation that is really sticking to either one..
+1

Tom




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

*I'm going to ignore all the off topic stuff in this conversation and bring
it back to the original focus:*

>> And yes, an article, possibly a series of articles, about programming on
> >> DOS, for DOS, will be forthcoming...
> > Would you prefer an article on Pascal? I know you (also) are a fan of
> > it. An article from your experience there might be useful.
> No, kind of programming language agnostic, with examples in BASIC, Turbo
> Pascal, C and assembler. As mentioned, it will be about programming in
> DOS for DOS.
> >
> >
>


Yes, I think articles about DOS programming in any language would be very
interesting. As long as the language variant is open source (for example:
NASM is an open source assembler, Microsoft MASM is not) the editors and
readers at OpenSource have shown great interest all kinds of programming
articles. They've run programming articles about Algol68 and other lesser
known languages.

So yes, write an article about programming for FreeDOS with FreePascal. Or
programming for FreeDOS with NASM. Or programming for FreeDOS with ___.

If you'd like a simple program to start with, they often use the "guess the
number game" as a simple programming example. Pick a random number between
1-100, and loop ("too high" and "too low") until the user guesses correctly.

Comparisons between DOS programming and Unix/Linux programming would also
be good. Like how would you port a Linux ncurses program to DOS conio? Or
how would your approach differ if you were to write a program on DOS vs for
Linux? As an example, I loved Jerome's article about large number
arithmetic on DOS.

>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Ralf Quint]

On 2/6/2023 5:40 PM, Rugxulo wrote:

Hi,

On Mon, Feb 6, 2023 at 4:35 PM Ralf Quint  wrote:

On 2/6/2023 2:03 PM, Rugxulo wrote:

Do you not understand that I see a lot of similarities between the two
OSes? Certainly they share enough for various ports of useful tools to
be made. It doesn't mean they have much in common, but I still see a
lot to learn from classic UNIX and the philosophy of some of the
authors and tools (as evidenced by my quotes from them). DOS is
"simple" (keep it simple!) but still useful (with the right tools and
the right ideas).

No, there aren't really "a lot of similarities" between DOS and
Unix/Linux.

DOS v1 was more like CP/M, but DOS v2 added file handles and
redirection. C compilers for DOS were abundant. C came from UNIX.
Well, no. For one, part of the programming API of DOS 1.xx was similar 
to that of CP/M-80. But it had a totally different underlying file 
system, as Paterson used the FAT filesystem that originally was inspired 
by the 8 bit FAT system used by Microsoft's Standalone BASIC (which he 
helped to implement at SCP) as well as Microsoft's unreleased 8-bit OS 
MDOS/MIDAS, which he was shown by Marc McDonald (Microsoft employee #1).


And C was developed to have a higher level language to implement Unix 
quicker "cross-platform", but while it has some features that it 
inherited from that initial task, it is not a Unix specific programming 
language. That is what in the end has made it so popular over a long 
time. In case of DOS, this shows in the use of very DOS specific 
libraries The file I/O stuff is a bit Unix like, but that's about it. 
The use of (n)curses for example is a typical Unix thing, that has 
nothing to do with DOS and should not be shoehorned into a DOS 
application...



Some *ix utilities MIGHT be useful for the use on DOS,

MKS Toolkit? GNUish? EMX? DJGPP? Heck, even Simtel and Garbo had a few.

I said "some" utilities. Not everything plus the kitchen sink.



"The Lessons of Unix Can Be Applied Elsewhere"

Nice statement, but I think that this is wrong. And just for the record, 
I used my first Unix system before I used my first DOS system...
Unix was from the start to be an abstraction of the hardware underneath, 
running on different hardware, usable with minimal knowledge of the 
hardware (specially, CPU wise).
DOS (as in MS-DOS/PC-DOS) is directly tied to the Intel 8086 CPU, it's 
segmented memory models, it's access to an underlying BIOS (and various 
extensions) on the hardware level and out of necessity, much more 
reliant on direct access to the hardware underneath.



And yes, an article, possibly a series of articles, about programming on
DOS, for DOS, will be forthcoming...

Would you prefer an article on Pascal? I know you (also) are a fan of
it. An article from your experience there might be useful.
No, kind of programming language agnostic, with examples in BASIC, Turbo 
Pascal, C and assembler. As mentioned, it will be about programming in 
DOS for DOS.


I built and tested P5 Pascal (ISO 7185) with GPC (and GNU Make) for
DOS, Windows, and Linux.


ISO 7185 is the worst thing that could happen to Pascal. Utterly useless 
and outdated by the time it was released.
Same as the standards for "minimal" and "extended" BASIC. There is not 
one mainstream BASIC implementation that is really sticking to either one..



Ralf



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Mon, Feb 6, 2023 at 4:35 PM Ralf Quint  wrote:
>
> On 2/6/2023 2:03 PM, Rugxulo wrote:
> > Do you not understand that I see a lot of similarities between the two
> > OSes? Certainly they share enough for various ports of useful tools to
> > be made. It doesn't mean they have much in common, but I still see a
> > lot to learn from classic UNIX and the philosophy of some of the
> > authors and tools (as evidenced by my quotes from them). DOS is
> > "simple" (keep it simple!) but still useful (with the right tools and
> > the right ideas).
>
> No, there aren't really "a lot of similarities" between DOS and
> Unix/Linux.

DOS v1 was more like CP/M, but DOS v2 added file handles and
redirection. C compilers for DOS were abundant. C came from UNIX.

> Some *ix utilities MIGHT be useful for the use on DOS,

MKS Toolkit? GNUish? EMX? DJGPP? Heck, even Simtel and Garbo had a few.

> but that doesn't mean by any stretch that things like "The Art of Unix
> Programming" do make any sense on DOS. The main goal should still be to
> program for DOS, not for Unix...

The book is mostly historical and philosophical about the "UNIX
mindset", not so much about doing UNIX-specific coding. So their
overall philosophy (esp. "open source") still applies greatly to
FreeDOS (or others).

* http://www.catb.org/~esr/writings/taoup/html/pr01s01.html

[partial intended audience, but others welcome too]

"You should read this book if you are a non-Unix programmer who has
figured out that the Unix tradition might have something to teach you.
We believe you're right, and that the Unix philosophy can be exported
to other operating systems. So we will pay more attention to non-Unix
environments (especially Microsoft operating systems) than is usual in
a Unix book; and when tools and case studies are portable, we say so."

"The Lessons of Unix Can Be Applied Elsewhere"

* http://www.catb.org/~esr/writings/taoup/html/ch01s05.html#id2873180

> > Jim's topic list mentioned Awk, Bash, C, Curl, Emacs, GDB, Grep,
> > Python, Sed, SSH, Vim, wget. (We have versions of all of those.)
> >
> In case you missed it, this was the whole list of possible topics from
> the Open Source magazine, not a list of suggested topics in regards to
> FreeDOS, as that was what Jim was asking in the subject of this thread.

I have used most of these on FreeDOS host for FreeDOS target. That is
the advantage of "portable" or "standard". I'm not tied to "UNIX"
exclusively.

> And yes, an article, possibly a series of articles, about programming on
> DOS, for DOS, will be forthcoming...

Would you prefer an article on Pascal? I know you (also) are a fan of
it. An article from your experience there might be useful.

I built and tested P5 Pascal (ISO 7185) with GPC (and GNU Make) for
DOS, Windows, and Linux.
I built and tested P4 Pascal subset (via p2c) with GCC and OpenWatcom
for DOS, OS/2, Windows, and Linux.
p5c works with modern GCC (e.g. DJGPP) or Clang.
DJGPP still includes old GPC (ISO 7185, ISO 10206, BP 7).
FPC still supports Go32v2 host / target and i8086-msdos target (with
{$mode tp} or {$mode iso}, et al).

(For UNIX Pascals besides FPC, Berkeley, ACK, and GPC are all on Github.)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Ralf Quint]

On 2/6/2023 2:03 PM, Rugxulo wrote:

Do you not understand that I see a lot of similarities between the two
OSes? Certainly they share enough for various ports of useful tools to
be made. It doesn't mean they have much in common, but I still see a
lot to learn from classic UNIX and the philosophy of some of the
authors and tools (as evidenced by my quotes from them). DOS is
"simple" (keep it simple!) but still useful (with the right tools and
the right ideas).
No, there aren't really "a lot of similarities" between DOS and 
Unix/Linux. Some *ix utilities MIGHT be useful for the use on DOS, but 
that doesn't mean by any stretch that things like "The Art of Unix 
Programming" do make any sense on DOS. The main goal should still be to 
program for DOS, not for Unix...


Jim's topic list mentioned Awk, Bash, C, Curl, Emacs, GDB, Grep,
Python, Sed, SSH, Vim, wget. (We have versions of all of those.)

In case you missed it, this was the whole list of possible topics from 
the Open Source magazine, not a list of suggested topics in regards to 
FreeDOS, as that was what Jim was asking in the subject of this thread.


And yes, an article, possibly a series of articles, about programming on 
DOS, for DOS, will be forthcoming...



Ralf




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Mon, Feb 6, 2023 at 3:18 PM Ralf Quint  wrote:
>
> On 2/5/2023 12:06 AM, Rugxulo wrote:
> > The Art of Unix Programming attempts to capture the engineering wisdom
> > and philosophy of the Unix community as it's applied today — not
> > merely as it has been written down in the past, but as a living
> > "special transmission, outside the scriptures" passed from guru to
> > guru. Accordingly, the book doesn't focus so much on "what" as on
> > "why", showing the connection between Unix philosophy and practice
> > through case studies in widely available open-source software.
>
> And how does this pertain to FreeDOS? :?

Someone (Mart?) mentioned Sam, another successor to UNIX's Ed (after
Vi). You well know that we have many DJGPP tools ported from UNIX
(e.g. GCC or Make or Diff or Patch). Most of the Sed ports in DOS that
I have used (hhsed, sedmod, csed, minised) were derived from code
written by Eric Raymond. He co-founded the "Open Source Initiative"
(OSI) and has written a lot about "open source", including the above
book.

Do you not understand that I see a lot of similarities between the two
OSes? Certainly they share enough for various ports of useful tools to
be made. It doesn't mean they have much in common, but I still see a
lot to learn from classic UNIX and the philosophy of some of the
authors and tools (as evidenced by my quotes from them). DOS is
"simple" (keep it simple!) but still useful (with the right tools and
the right ideas).

Jim's topic list mentioned Awk, Bash, C, Curl, Emacs, GDB, Grep,
Python, Sed, SSH, Vim, wget. (We have versions of all of those.)

Where would you recommend I start (thinking or writing)? What topic
would be most instructive?


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Ralf Quint]

On 2/5/2023 12:06 AM, Rugxulo wrote:

The Art of Unix Programming attempts to capture the engineering wisdom
and philosophy of the Unix community as it's applied today — not
merely as it has been written down in the past, but as a living
"special transmission, outside the scriptures" passed from guru to
guru. Accordingly, the book doesn't focus so much on "what" as on
"why", showing the connection between Unix philosophy and practice
through case studies in widely available open-source software.

And how does this pertain to FreeDOS? :?


Ralf




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Sun, Jan 29, 2023 at 4:29 PM Rugxulo  wrote:
>
> On Sun, Jan 29, 2023 at 3:01 PM Mart Zirnask  wrote:
> >
> > I'm definitely more of an end user, but I like the simplicity of both
> > DOS and traditional Unix tools.
>
> * https://en.wikipedia.org/wiki/Unix_philosophy
> * https://en.wikipedia.org/wiki/Minimalism_(computing)

Although I only skimmed it, I stumbled upon Eric Raymond's _The Art of
UNIX Programming_ (2003). It has A LOT of good stuff in there!

* http://catb.org/~esr/writings/taoup/

The Art of Unix Programming attempts to capture the engineering wisdom
and philosophy of the Unix community as it's applied today — not
merely as it has been written down in the past, but as a living
"special transmission, outside the scriptures" passed from guru to
guru. Accordingly, the book doesn't focus so much on "what" as on
"why", showing the connection between Unix philosophy and practice
through case studies in widely available open-source software.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

On Mon, Jan 30, 2023 at 8:43 AM Liam Proven  wrote:
>[..]
> But I have a suggestion:
>
> How to install FreeDOS onto a USB key, so you can boot a BIOS-equipped
> PC into DOS from USB. I've done this myself and it works very well.
>
> You can create the key using VirtualBox, and then run it either in a
> VM or on bare metal. I described this (with respect to Linux) in my
> blog:
> https://liam-on-linux.livejournal.com/50416.html
>
> I've done this with FreeDOS 1.3 and it works very well. You can insert
> the key and just copy DOS apps and things onto it, then eject it, put
> it into another PC and boot it, and the new apps are right there.
>


I'll add this to my list of topics I might write about sometime.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

On Mon, Jan 30, 2023 at 3:01 PM Aitor Santamaría  wrote:
>
> Hello Jim,
>
> Is this list of topics available somewhere on the web? The list here
> looks far shorter and does NOT include FreeDOS:
>
> The A to Z list of writing topics for Opensource.com | Opensource.com
>

I think they need to update that page; it's out of date (2016).
Rugxulo asked the same question but I think my reply got buried in the
thread:

The list was shared on the "frequent writers" email list, not
a web page - or I would have just linked to a web page.



So no, that list I shared it not on a web page that I know of.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Aitor Santamaría]

Hello Jim,

Is this list of topics available somewhere on the web? The list here looks
far shorter and does NOT include FreeDOS:

The A to Z list of writing topics for Opensource.com | Opensource.com


Aitor



On Sun, 29 Jan 2023 at 19:40, Jim Hall  wrote:

> If anyone here is interested in writing articles about FreeDOS,
> Opensource.com is interested in running FreeDOS articles. I write
> articles for them sometimes, and the FreeDOS articles perform very
> well on the site. In fact, they recently listed FreeDOS among their
> list of "topics we're interested in for 2023." Also included in the
> list: conio and C programming.
>
> I can tell you the editors are very welcoming, which is why I continue
> to write articles for them. If English isn't your first language, and
> you aren't confident of your English writing skills, they can help
> with editing to make the final version really nice.
>
> Here's the list they shared, in case this inspires anyone to write an
> article:
>
> - accessibility
> - Ansible
> - apt
> - Awk
> - Bash scripting
> - Blender
> - C getopt
> - C Programming
> - Chaos Engineering for K8s
> - Compose Key
> - conio
> - Containers/Pods
> - cron
> - Curl
> - DevOps
> - DevSecOps
> - dnf
> - doxygen
> - Emacs
> - find command
> - Firewall
> - FreeDOS
> - GDB
> - GIMP
> - Git
> - GNOME
> - GNU Screen
> - Go Beginners
> - Grep
> - Home Automation
> - Inkscape
> - Intro Small Scale Scrum
> - Java
> - JavaScript
> - Jinja2
> - Jupyter
> - Kdenlive
> - Kubectl
> - Kubernetes
> - Kubernetes SRE
> - Linux Apps
> - Linux perms
> - Logrotate
> - Markdown
> - MySQL
> - Networking
> - Parted
> - Pygame eBook
> - PyPI
> - Python
> - Raspberry Pi
> - Running K8s on RPi
> - Rust
> - Sed
> - SELinux
> - SSH
> - sudo
> - sustainability
> - systemd
> - tmux
> - Vim
> - wget
>
> Email the editors at o...@opensource.com
>
> They have a "write for us" page at https://opensource.com/writers
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Liam Proven]

On Sun, 29 Jan 2023 at 19:41, Jim Hall  wrote:
>
> If anyone here is interested in writing articles about FreeDOS,
> Opensource.com is interested in running FreeDOS articles.

As I write full-time for a competing publication, I can't.

But I have a suggestion:

How to install FreeDOS onto a USB key, so you can boot a BIOS-equipped
PC into DOS from USB. I've done this myself and it works very well.

You can create the key using VirtualBox, and then run it either in a
VM or on bare metal. I described this (with respect to Linux) in my
blog:
https://liam-on-linux.livejournal.com/50416.html

I've done this with FreeDOS 1.3 and it works very well. You can insert
the key and just copy DOS apps and things onto it, then eject it, put
it into another PC and boot it, and the new apps are right there.


-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lpro...@cix.co.uk ~ gMail/gTalk/FB: lpro...@gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Mart Zirnask]

On 30/01/2023, Jim Hall  wrote:
> SAM is a window-based editor, so it uses graphics mode. To me, this
> looks a lot like the window editor on the Apollo/DOMAIN system - I
> managed a small Apollo/DOMAIN network in the mid 1990s. You can find a
> screenshot of SAM on Wikipedia:
> https://en.wikipedia.org/wiki/Sam_%28text_editor%29#/media/File:Sam_text_editor.png
>
> Compiling this for DOS would be an interesting exercise. Not sure if
> it's possible, but give it a shot and let us know.

SAM can actually be used in both ways -- via a graphical interface,
but also without it, in command-line-only mode, just like ED or EDLIN.
This can be accomplished with the "-d" flag (sam -d [filenames]).

I am aiming to compile only the command line backend for DOS, without
the GUI. A Plan9 contributor has reportedly accomplished this (with an
early version, back in the day [1]), so there is hope.

Best,
Mart

1: He thought this might be the Unix source that he ported:
https://netlib.org/research/sam.shar


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Karen Lewellen]

Travis,
While certainly such an article can exist, speaking personally, treating 
accessibility as if it must be built, one population at a time is 
frankly a disservice.
In fact, speaking personally, that is part of why accessibility has made 
such little progress, in part to be sure.
One does not build a brick & motor business with just a single wall. 
Instead you create an entire structure which, if done to serve the public, 
much of the time takes into consideration that different kinds of humans 
will be visiting that building.  I say much of the time,  historical 
places 
do not always have ramps or elevators.
Still, when building an operating system, and hoping to encourage 
inclusion, why break it up by population?

It is not how accessibility guidelines work for example.
Instead inclusion is based on interaction, and according to the w3c, is 
device browser and user agent agnostic to keep people from prioritizing 
one  group of humans who interact with technology over another.
My guess is that accessibility is a new concept to this opensource 
community.
why perpetuate the unfortunate idea that only those experiencing blindness 
have  paths to accessibility, or that such only applies to them?
Speaking personally of course, since I do not believe an actual blind 
community exists...realizing others feel differently.

Karen



On Sun, 29 Jan 2023, Travis Siegel wrote:

Yes, but if they want articles on accessibility, I see no reason why an 
article on visually impaired access with screen readers can't be an 
article.  If folks want to write articles for other accessibility features, 
then feel free to do so.  I can't write about what I don't know.



On 1/29/2023 9:01 PM, Karen Lewellen wrote:

 Well, unless he has left, He is still on list.
 He did, if memory serves, get permission from the creator of asap and asaw
 to include it in his project.
 I might be entirely wrong, or he has a different one for dosbox.
 However, as shared, access is not about screen readers alone, it is
 frankly disturbing the folks who feel otherwise, because they hear such
 all the time.



 On Sun, 29 Jan 2023, Travis Siegel wrote:

>  Possibly, but asap isn't opensource, so no article there.
>  I do have an opensource screen reader, but again, it requires a physical 
>  synth, so I need to work on that somehow.
> 
>  Plus I have to find where I stuffed the source, it's around here 
>  somewhere, but I haven't seen it in a while.
> 
>  On the other hand, I'd be interested to see how ASAP was made to work, 
>  that should be an interesting reveal.
> 
> 
>  On 1/29/2023 8:36 PM, Karen Lewellen wrote:
> >   does not Joseph have a working edition of freedos using asap, as a 
> >  screen

> >   reader?
> >   The journey  to getting accessibility, not just screen readers, but 
> >  voice

> >   tools for those needing that kind of inclusion,  might make for an
> >   interesting piece.
> >   Since opensource seeks well open source smiles, the article might
> >   encourage creativity towards coding solutions that benefit many
> >   populations.  After all, accessibility is not about blindness 
> >  alone.

> >   Kare
> > 
> > 
> > 
> >   On Sun, 29 Jan 2023, Travis Siegel wrote:
> > 
> > >   I suppose if they're interested in articles on accessibility, I 
> >  should >  probably write one on visually impaired access.  I tried 
> >  to get a >  screen reader included into the project several years 
> >  ago, and was > turned down, because of the license of the code, even 
> >  though it didn't >  have any restrictions on distribution, other than 
> >  the fact that whoever >  did so have a license for the a86 assembler, 
> >  (which I do have), but I've >  also not done a whole lot with it 
> >  since then, so perhaps it's time I did >  do something about that.  
> >  I need to figure out some way to tie that >  screen reader to a 
> >  software synthesizer of some sort, so folks don't >  need a physical 
> >  hardware synthesizer.  If that could be accomplished, >  then 
> >  freedos would truly be completely accessible.
> > > >   Of course, it is sort of accessible to visually impaired folks 
> >  now, >  since running it under dosemu on linux uses the linux screen 
> >  reader, and >  works just fine, though I've not tried running it on 
> >  something like > dosbox under windows, to see if the windows screen 
> >  reader works for it.
> > > >   I guess there's more work that needs done before I could truly 
> >  write an >  all inclusive article about it being accessible to 
> >  visually impaired >  users.
> > > >   On the other hand, because dos is so easy to use, it does make 
> >  it a lot >  more accessible than other operating systems like windows 
> >  though, so >  perhaps there's an article there.

> > > >   
> > > >   I'll think about it, and see if there's something I can come up 
> > with >   that seems publication worthy.
> > > >   Ideas are of course welcome, which is (mostly) why I went ahead 
> > and >   

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Travis Siegel]

Yes, but if they want articles on accessibility, I see no reason why an 
article on visually impaired access with screen readers can't be an 
article.  If folks want to write articles for other accessibility 
features, then feel free to do so.  I can't write about what I don't know.



On 1/29/2023 9:01 PM, Karen Lewellen wrote:

Well, unless he has left, He is still on list.
He did, if memory serves, get permission from the creator of asap and 
asaw to include it in his project.

I might be entirely wrong, or he has a different one for dosbox.
However, as shared, access is not about screen readers alone, it is 
frankly disturbing the folks who feel otherwise, because they hear 
such all the time.




On Sun, 29 Jan 2023, Travis Siegel wrote:


Possibly, but asap isn't opensource, so no article there.
I do have an opensource screen reader, but again, it requires a 
physical synth, so I need to work on that somehow.


Plus I have to find where I stuffed the source, it's around here 
somewhere, but I haven't seen it in a while.


On the other hand, I'd be interested to see how ASAP was made to 
work, that should be an interesting reveal.



On 1/29/2023 8:36 PM, Karen Lewellen wrote:
 does not Joseph have a working edition of freedos using asap, as a 
screen

 reader?
 The journey  to getting accessibility, not just screen readers, but 
voice

 tools for those needing that kind of inclusion,  might make for an
 interesting piece.
 Since opensource seeks well open source smiles, the article might
 encourage creativity towards coding solutions that benefit many
 populations.  After all, accessibility is not about blindness alone.
 Kare



 On Sun, 29 Jan 2023, Travis Siegel wrote:

>  I suppose if they're interested in articles on accessibility, I 
should >  probably write one on visually impaired access.  I tried 
to get a >  screen reader included into the project several years 
ago, and was > turned down, because of the license of the code, even 
though it didn't >  have any restrictions on distribution, other 
than the fact that whoever >  did so have a license for the a86 
assembler, (which I do have), but I've >  also not done a whole lot 
with it since then, so perhaps it's time I did >  do something about 
that.  I need to figure out some way to tie that >  screen reader to 
a software synthesizer of some sort, so folks don't >  need a 
physical hardware synthesizer.  If that could be accomplished, >  
then freedos would truly be completely accessible.
> >  Of course, it is sort of accessible to visually impaired folks 
now, >  since running it under dosemu on linux uses the linux screen 
reader, and >  works just fine, though I've not tried running it on 
something like > dosbox under windows, to see if the windows screen 
reader works for it.
> >  I guess there's more work that needs done before I could truly 
write an >  all inclusive article about it being accessible to 
visually impaired >  users.
> >  On the other hand, because dos is so easy to use, it does make 
it a lot >  more accessible than other operating systems like 
windows though, so >  perhaps there's an article there.

> >  
> >  I'll think about it, and see if there's something I can come up 
with >  that seems publication worthy.
> >  Ideas are of course welcome, which is (mostly) why I went ahead 
and >  posted this message.

> >  Thanks for listening.
> > >  On 1/29/2023 2:37 PM, Linvel Risner wrote:
> >   I’m by no means a FreeDOS expert, I’m just a user, but if 
anyone > >  would
> >   like help writing an article I’m here to help. I know our > >  
community is
> >   very diverse linguistically and as a result I’m more than 
happy to > >  lend
> >   a hand to an English as a second language speaker/writer. I 
would > >  take no
> >   credit, you’d have 100% ownership of the article, I’d just 
like > >  to

> >   help in some way. Reach out if y’all need anything :)
> > > >   On Sun, Jan 29, 2023 at 2:20 PM John Vella 
 > >  wrote:
> > > >   That sounds like the sort of thing I'd be interested 
in > >  doing, but

> >   what sort of article are they looking for? Are they after a
> >   "history of FreeDOS" type article, because that's been 
done > >  so
> >   many times it would be hard to write anything original, > 
>  wouldn't it?

> > > >   I look forward to hearing your thoughts.
> > > >   Cheers,
> > > >   John.
> > > >   On Sun, 29 Jan 2023, 18:41 Jim Hall, 
 > >  wrote:
> > > >   If anyone here is interested in writing articles > 
>  about FreeDOS,
> >   Opensource.com is interested in running FreeDOS > >  
articles. I write
> >   articles for them sometimes, and the FreeDOS articles 
> >  perform very
> >   well on the site. In fact, they recently listed > >  
FreeDOS among

> >   their
> >   list of "topics we're interested in for 2023." Also > 
>  included

> >   in the
> >   list: conio and C programming.
> > > >   

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Travis Siegel]

Yes, it still exists, but I doubt it handles anything relatively modern, 
with the exception of web pages, since that hasn't changed very much.



On 1/29/2023 8:39 PM, Karen Lewellen wrote:
does this package still exist, and if so, how does it manage more 
current authentication  needs?

Kare



On Sun, 29 Jan 2023, Travis Siegel wrote:

Actually, that reminds me of a package called ka9q, which provides a 
complete tcp/ip stack to dos, that allows all kinds of net access to 
ftp, smtp, telnet, and probably other things I don't remember.  
That's probably a really good article waiting to happen.


I actually used that package to run my softcon.com site for a few 
months when I first opened it in 1996, until I got my linux boxes up 
and running.


I'll probably take a crack at something like that first before doing 
an accessibility one.



On 1/29/2023 2:37 PM, Linvel Risner wrote:

 I’m by no means a FreeDOS expert, I’m just a user, but if anyone would
 like help writing an article I’m here to help. I know our community is
 very diverse linguistically and as a result I’m more than happy to 
lend
 a hand to an English as a second language speaker/writer. I would 
take no

 credit, you’d have 100% ownership of the article, I’d just like to
 help in some way. Reach out if y’all need anything :)

 On Sun, Jan 29, 2023 at 2:20 PM John Vella  
wrote:


 That sounds like the sort of thing I'd be interested in doing, but
 what sort of article are they looking for? Are they after a
 "history of FreeDOS" type article, because that's been done so
 many times it would be hard to write anything original, 
wouldn't it?


 I look forward to hearing your thoughts.

 Cheers,

 John.

 On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

 If anyone here is interested in writing articles about 
FreeDOS,
 Opensource.com is interested in running FreeDOS articles. I 
write
 articles for them sometimes, and the FreeDOS articles 
perform very

 well on the site. In fact, they recently listed FreeDOS among
 their
 list of "topics we're interested in for 2023." Also included
 in the
 list: conio and C programming.

 I can tell you the editors are very welcoming, which is why I
 continue
 to write articles for them. If English isn't your first
 language, and
 you aren't confident of your English writing skills, they 
can help

 with editing to make the final version really nice.

 Here's the list they shared, in case this inspires anyone to
 write an article:

 - accessibility
 - Ansible
 - apt
 - Awk
 - Bash scripting
 - Blender
 - C getopt
 - C Programming
 - Chaos Engineering for K8s
 - Compose Key
 - conio
 - Containers/Pods
 - cron
 - Curl
 - DevOps
 - DevSecOps
 - dnf
 - doxygen
 - Emacs
 - find command
 - Firewall
 - FreeDOS
 - GDB
 - GIMP
 - Git
 - GNOME
 - GNU Screen
 - Go Beginners
 - Grep
 - Home Automation
 - Inkscape
 - Intro Small Scale Scrum
 - Java
 - JavaScript
 - Jinja2
 - Jupyter
 - Kdenlive
 - Kubectl
 - Kubernetes
 - Kubernetes SRE
 - Linux Apps
 - Linux perms
 - Logrotate
 - Markdown
 - MySQL
 - Networking
 - Parted
 - Pygame eBook
 - PyPI
 - Python
 - Raspberry Pi
 - Running K8s on RPi
 - Rust
 - Sed
 - SELinux
 - SSH
 - sudo
 - sustainability
 - systemd
 - tmux
 - Vim
 - wget

 Email the editors at o...@opensource.com

 They have a "write for us" page at 
https://opensource.com/writers



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user





___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Karen Lewellen]

Well, unless he has left, He is still on list.
He did, if memory serves, get permission from the creator of asap and asaw 
to include it in his project.

I might be entirely wrong, or he has a different one for dosbox.
However, as shared, access is not about screen readers alone, it is frankly 
disturbing the folks who feel otherwise, because they hear such all the 
time.




On Sun, 29 Jan 2023, Travis Siegel wrote:


Possibly, but asap isn't opensource, so no article there.
I do have an opensource screen reader, but again, it requires a physical 
synth, so I need to work on that somehow.


Plus I have to find where I stuffed the source, it's around here somewhere, 
but I haven't seen it in a while.


On the other hand, I'd be interested to see how ASAP was made to work, that 
should be an interesting reveal.



On 1/29/2023 8:36 PM, Karen Lewellen wrote:

 does not Joseph have a working edition of freedos using asap, as a screen
 reader?
 The journey  to getting accessibility, not just screen readers, but voice
 tools for those needing that kind of inclusion,  might make for an
 interesting piece.
 Since opensource seeks well open source smiles, the article might
 encourage creativity towards coding solutions that benefit many
 populations.  After all, accessibility is not about blindness alone.
 Kare



 On Sun, 29 Jan 2023, Travis Siegel wrote:

>  I suppose if they're interested in articles on accessibility, I should 
>  probably write one on visually impaired access.  I tried to get a 
>  screen reader included into the project several years ago, and was 
>  turned down, because of the license of the code, even though it didn't 
>  have any restrictions on distribution, other than the fact that whoever 
>  did so have a license for the a86 assembler, (which I do have), but I've 
>  also not done a whole lot with it since then, so perhaps it's time I did 
>  do something about that.  I need to figure out some way to tie that 
>  screen reader to a software synthesizer of some sort, so folks don't 
>  need a physical hardware synthesizer.  If that could be accomplished, 
>  then freedos would truly be completely accessible.
> 
>  Of course, it is sort of accessible to visually impaired folks now, 
>  since running it under dosemu on linux uses the linux screen reader, and 
>  works just fine, though I've not tried running it on something like 
>  dosbox under windows, to see if the windows screen reader works for it.
> 
>  I guess there's more work that needs done before I could truly write an 
>  all inclusive article about it being accessible to visually impaired 
>  users.
> 
>  On the other hand, because dos is so easy to use, it does make it a lot 
>  more accessible than other operating systems like windows though, so 
>  perhaps there's an article there.
> 
>  
> 
>  I'll think about it, and see if there's something I can come up with 
>  that seems publication worthy.
> 
>  Ideas are of course welcome, which is (mostly) why I went ahead and 
>  posted this message.
> 
>  Thanks for listening.
> 
> 
>  On 1/29/2023 2:37 PM, Linvel Risner wrote:
> >   I’m by no means a FreeDOS expert, I’m just a user, but if anyone 
> >  would
> >   like help writing an article I’m here to help. I know our 
> >  community is
> >   very diverse linguistically and as a result I’m more than happy to 
> >  lend
> >   a hand to an English as a second language speaker/writer. I would 
> >  take no
> >   credit, you’d have 100% ownership of the article, I’d just like 
> >  to

> >   help in some way. Reach out if y’all need anything :)
> > 
> >   On Sun, Jan 29, 2023 at 2:20 PM John Vella  
> >  wrote:
> > 
> >   That sounds like the sort of thing I'd be interested in 
> >  doing, but

> >   what sort of article are they looking for? Are they after a
> >   "history of FreeDOS" type article, because that's been done 
> >  so
> >   many times it would be hard to write anything original, 
> >  wouldn't it?
> > 
> >   I look forward to hearing your thoughts.
> > 
> >   Cheers,
> > 
> >   John.
> > 
> >   On Sun, 29 Jan 2023, 18:41 Jim Hall,  
> >  wrote:
> > 
> >   If anyone here is interested in writing articles 
> >  about FreeDOS,
> >   Opensource.com is interested in running FreeDOS 
> >  articles. I write
> >   articles for them sometimes, and the FreeDOS articles 
> >  perform very
> >   well on the site. In fact, they recently listed 
> >  FreeDOS among

> >   their
> >   list of "topics we're interested in for 2023." Also 
> >  included

> >   in the
> >   list: conio and C programming.
> > 
> >   I can tell you the editors are very welcoming, which 
> >  is why I

> >   continue
> >   to write articles for them. If English isn't your 
> >  first

> >   language, and
> >   you aren't confident of your English writing skills, 
> >  they can help

> >   with editing to make 

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Travis Siegel]

Possibly, but asap isn't opensource, so no article there.

I do have an opensource screen reader, but again, it requires a physical 
synth, so I need to work on that somehow.


Plus I have to find where I stuffed the source, it's around here 
somewhere, but I haven't seen it in a while.


On the other hand, I'd be interested to see how ASAP was made to work, 
that should be an interesting reveal.



On 1/29/2023 8:36 PM, Karen Lewellen wrote:
does not Joseph have a working edition of freedos using asap, as a 
screen reader?
The journey  to getting accessibility, not just screen readers, but 
voice tools for those needing that kind of inclusion,  might make for 
an interesting piece.
Since opensource seeks well open source smiles, the article might 
encourage creativity towards coding solutions that benefit many 
populations.  After all, accessibility is not about blindness alone.

Kare



On Sun, 29 Jan 2023, Travis Siegel wrote:

I suppose if they're interested in articles on accessibility, I 
should probably write one on visually impaired access.  I tried to 
get a screen reader included into the project several years ago, and 
was turned down, because of the license of the code, even though it 
didn't have any restrictions on distribution, other than the fact 
that whoever did so have a license for the a86 assembler, (which I do 
have), but I've also not done a whole lot with it since then, so 
perhaps it's time I did do something about that.  I need to figure 
out some way to tie that screen reader to a software synthesizer of 
some sort, so folks don't need a physical hardware synthesizer.  If 
that could be accomplished, then freedos would truly be completely 
accessible.


Of course, it is sort of accessible to visually impaired folks now, 
since running it under dosemu on linux uses the linux screen reader, 
and works just fine, though I've not tried running it on something 
like dosbox under windows, to see if the windows screen reader works 
for it.


I guess there's more work that needs done before I could truly write 
an all inclusive article about it being accessible to visually 
impaired users.


On the other hand, because dos is so easy to use, it does make it a 
lot more accessible than other operating systems like windows though, 
so perhaps there's an article there.




I'll think about it, and see if there's something I can come up with 
that seems publication worthy.


Ideas are of course welcome, which is (mostly) why I went ahead and 
posted this message.


Thanks for listening.


On 1/29/2023 2:37 PM, Linvel Risner wrote:

 I’m by no means a FreeDOS expert, I’m just a user, but if anyone would
 like help writing an article I’m here to help. I know our community is
 very diverse linguistically and as a result I’m more than happy to 
lend
 a hand to an English as a second language speaker/writer. I would 
take no

 credit, you’d have 100% ownership of the article, I’d just like to
 help in some way. Reach out if y’all need anything :)

 On Sun, Jan 29, 2023 at 2:20 PM John Vella  
wrote:


 That sounds like the sort of thing I'd be interested in doing, but
 what sort of article are they looking for? Are they after a
 "history of FreeDOS" type article, because that's been done so
 many times it would be hard to write anything original, 
wouldn't it?


 I look forward to hearing your thoughts.

 Cheers,

 John.

 On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

 If anyone here is interested in writing articles about 
FreeDOS,
 Opensource.com is interested in running FreeDOS articles. I 
write
 articles for them sometimes, and the FreeDOS articles 
perform very

 well on the site. In fact, they recently listed FreeDOS among
 their
 list of "topics we're interested in for 2023." Also included
 in the
 list: conio and C programming.

 I can tell you the editors are very welcoming, which is why I
 continue
 to write articles for them. If English isn't your first
 language, and
 you aren't confident of your English writing skills, they 
can help

 with editing to make the final version really nice.

 Here's the list they shared, in case this inspires anyone to
 write an article:

 - accessibility
 - Ansible
 - apt
 - Awk
 - Bash scripting
 - Blender
 - C getopt
 - C Programming
 - Chaos Engineering for K8s
 - Compose Key
 - conio
 - Containers/Pods
 - cron
 - Curl
 - DevOps
 - DevSecOps
 - dnf
 - doxygen
 - Emacs
 - find command
 - Firewall
 - FreeDOS
 - GDB
 - GIMP
 - Git
 - GNOME
 - GNU Screen
 - Go Beginners
 - Grep
 - Home Automation
 - Inkscape
 - Intro Small Scale Scrum
 

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Karen Lewellen]

does this package still exist, and if so, how does it manage more current 
authentication  needs?

Kare



On Sun, 29 Jan 2023, Travis Siegel wrote:

Actually, that reminds me of a package called ka9q, which provides a complete 
tcp/ip stack to dos, that allows all kinds of net access to ftp, smtp, 
telnet, and probably other things I don't remember.?? That's probably a 
really good article waiting to happen.


I actually used that package to run my softcon.com site for a few months when 
I first opened it in 1996, until I got my linux boxes up and running.


I'll probably take a crack at something like that first before doing an 
accessibility one.



On 1/29/2023 2:37 PM, Linvel Risner wrote:

 I???m by no means a FreeDOS expert, I???m just a user, but if anyone would
 like help writing an article I???m here to help. I know our community is
 very diverse linguistically and as a result I???m more than happy to lend
 a hand to an English as a second language speaker/writer. I would take no
 credit, you???d have 100% ownership of the article, I???d just like to
 help in some way. Reach out if y???all need anything :)

 On Sun, Jan 29, 2023 at 2:20 PM John Vella  wrote:

 That sounds like the sort of thing I'd be interested in doing, but
 what sort of article are they looking for? Are they after a
 "history of FreeDOS" type article, because that's been done so
 many times it would be hard to write anything original, wouldn't it?

 I look forward to hearing your thoughts.

 Cheers,

 John.

 On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

 If anyone here is interested in writing articles about FreeDOS,
 Opensource.com is interested in running FreeDOS articles. I write
 articles for them sometimes, and the FreeDOS articles perform very
 well on the site. In fact, they recently listed FreeDOS among
 their
 list of "topics we're interested in for 2023." Also included
 in the
 list: conio and C programming.

 I can tell you the editors are very welcoming, which is why I
 continue
 to write articles for them. If English isn't your first
 language, and
 you aren't confident of your English writing skills, they can help
 with editing to make the final version really nice.

 Here's the list they shared, in case this inspires anyone to
 write an article:

 - accessibility
 - Ansible
 - apt
 - Awk
 - Bash scripting
 - Blender
 - C getopt
 - C Programming
 - Chaos Engineering for K8s
 - Compose Key
 - conio
 - Containers/Pods
 - cron
 - Curl
 - DevOps
 - DevSecOps
 - dnf
 - doxygen
 - Emacs
 - find command
 - Firewall
 - FreeDOS
 - GDB
 - GIMP
 - Git
 - GNOME
 - GNU Screen
 - Go Beginners
 - Grep
 - Home Automation
 - Inkscape
 - Intro Small Scale Scrum
 - Java
 - JavaScript
 - Jinja2
 - Jupyter
 - Kdenlive
 - Kubectl
 - Kubernetes
 - Kubernetes SRE
 - Linux Apps
 - Linux perms
 - Logrotate
 - Markdown
 - MySQL
 - Networking
 - Parted
 - Pygame eBook
 - PyPI
 - Python
 - Raspberry Pi
 - Running K8s on RPi
 - Rust
 - Sed
 - SELinux
 - SSH
 - sudo
 - sustainability
 - systemd
 - tmux
 - Vim
 - wget

 Email the editors at o...@opensource.com

 They have a "write for us" page at https://opensource.com/writers


 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user

 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user



 ___
 Freedos-user mailing list
 Freedos-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/freedos-user
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Karen Lewellen]

does not Joseph have a working edition of freedos using asap, as a screen 
reader?
The journey  to getting accessibility, not just screen readers, but voice 
tools for those needing that kind of inclusion,  might make for an 
interesting piece.
Since opensource seeks well open source smiles, the article might 
encourage creativity towards coding solutions that benefit many 
populations.  After all, accessibility is not about blindness alone.

Kare



On Sun, 29 Jan 2023, Travis Siegel wrote:

I suppose if they're interested in articles on accessibility, I should 
probably write one on visually impaired access.?? I tried to get a screen 
reader included into the project several years ago, and was turned down, 
because of the license of the code, even though it didn't have any 
restrictions on distribution, other than the fact that whoever did so have a 
license for the a86 assembler, (which I do have), but I've also not done a 
whole lot with it since then, so perhaps it's time I did do something about 
that.?? I need to figure out some way to tie that screen reader to a software 
synthesizer of some sort, so folks don't need a physical hardware 
synthesizer.?? If that could be accomplished, then freedos would truly be 
completely accessible.


Of course, it is sort of accessible to visually impaired folks now, since 
running it under dosemu on linux uses the linux screen reader, and works just 
fine, though I've not tried running it on something like dosbox under 
windows, to see if the windows screen reader works for it.


I guess there's more work that needs done before I could truly write an all 
inclusive article about it being accessible to visually impaired users.


On the other hand, because dos is so easy to use, it does make it a lot more 
accessible than other operating systems like windows though, so perhaps 
there's an article there.




I'll think about it, and see if there's something I can come up with that 
seems publication worthy.


Ideas are of course welcome, which is (mostly) why I went ahead and posted 
this message.


Thanks for listening.


On 1/29/2023 2:37 PM, Linvel Risner wrote:

 I???m by no means a FreeDOS expert, I???m just a user, but if anyone would
 like help writing an article I???m here to help. I know our community is
 very diverse linguistically and as a result I???m more than happy to lend
 a hand to an English as a second language speaker/writer. I would take no
 credit, you???d have 100% ownership of the article, I???d just like to
 help in some way. Reach out if y???all need anything :)

 On Sun, Jan 29, 2023 at 2:20 PM John Vella  wrote:

 That sounds like the sort of thing I'd be interested in doing, but
 what sort of article are they looking for? Are they after a
 "history of FreeDOS" type article, because that's been done so
 many times it would be hard to write anything original, wouldn't it?

 I look forward to hearing your thoughts.

 Cheers,

 John.

 On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

 If anyone here is interested in writing articles about FreeDOS,
 Opensource.com is interested in running FreeDOS articles. I write
 articles for them sometimes, and the FreeDOS articles perform very
 well on the site. In fact, they recently listed FreeDOS among
 their
 list of "topics we're interested in for 2023." Also included
 in the
 list: conio and C programming.

 I can tell you the editors are very welcoming, which is why I
 continue
 to write articles for them. If English isn't your first
 language, and
 you aren't confident of your English writing skills, they can help
 with editing to make the final version really nice.

 Here's the list they shared, in case this inspires anyone to
 write an article:

 - accessibility
 - Ansible
 - apt
 - Awk
 - Bash scripting
 - Blender
 - C getopt
 - C Programming
 - Chaos Engineering for K8s
 - Compose Key
 - conio
 - Containers/Pods
 - cron
 - Curl
 - DevOps
 - DevSecOps
 - dnf
 - doxygen
 - Emacs
 - find command
 - Firewall
 - FreeDOS
 - GDB
 - GIMP
 - Git
 - GNOME
 - GNU Screen
 - Go Beginners
 - Grep
 - Home Automation
 - Inkscape
 - Intro Small Scale Scrum
 - Java
 - JavaScript
 - Jinja2
 - Jupyter
 - Kdenlive
 - Kubectl
 - Kubernetes
 - Kubernetes SRE
 - Linux Apps
 - Linux perms
 - Logrotate
 - Markdown
 - MySQL
 - Networking
 - Parted
 - Pygame eBook
 - PyPI
 - Python
 - Raspberry Pi
 - Running K8s on RPi
 - Rust
 - Sed
 

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Travis Siegel]

Actually, that reminds me of a package called ka9q, which provides a 
complete tcp/ip stack to dos, that allows all kinds of net access to 
ftp, smtp, telnet, and probably other things I don't remember.  That's 
probably a really good article waiting to happen.


I actually used that package to run my softcon.com site for a few months 
when I first opened it in 1996, until I got my linux boxes up and running.


I'll probably take a crack at something like that first before doing an 
accessibility one.



On 1/29/2023 2:37 PM, Linvel Risner wrote:
I’m by no means a FreeDOS expert, I’m just a user, but if anyone would 
like help writing an article I’m here to help. I know our community is 
very diverse linguistically and as a result I’m more than happy to 
lend a hand to an English as a second language speaker/writer. I would 
take no credit, you’d have 100% ownership of the article, I’d just 
like to help in some way. Reach out if y’all need anything :)


On Sun, Jan 29, 2023 at 2:20 PM John Vella  wrote:

That sounds like the sort of thing I'd be interested in doing, but
what sort of article are they looking for? Are they after a
"history of FreeDOS" type article, because that's been done so
many times it would be hard to write anything original, wouldn't it?

I look forward to hearing your thoughts.

Cheers,

John.

On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

If anyone here is interested in writing articles about FreeDOS,
Opensource.com is interested in running FreeDOS articles. I write
articles for them sometimes, and the FreeDOS articles perform very
well on the site. In fact, they recently listed FreeDOS among
their
list of "topics we're interested in for 2023." Also included
in the
list: conio and C programming.

I can tell you the editors are very welcoming, which is why I
continue
to write articles for them. If English isn't your first
language, and
you aren't confident of your English writing skills, they can help
with editing to make the final version really nice.

Here's the list they shared, in case this inspires anyone to
write an article:

- accessibility
- Ansible
- apt
- Awk
- Bash scripting
- Blender
- C getopt
- C Programming
- Chaos Engineering for K8s
- Compose Key
- conio
- Containers/Pods
- cron
- Curl
- DevOps
- DevSecOps
- dnf
- doxygen
- Emacs
- find command
- Firewall
- FreeDOS
- GDB
- GIMP
- Git
- GNOME
- GNU Screen
- Go Beginners
- Grep
- Home Automation
- Inkscape
- Intro Small Scale Scrum
- Java
- JavaScript
- Jinja2
- Jupyter
- Kdenlive
- Kubectl
- Kubernetes
- Kubernetes SRE
- Linux Apps
- Linux perms
- Logrotate
- Markdown
- MySQL
- Networking
- Parted
- Pygame eBook
- PyPI
- Python
- Raspberry Pi
- Running K8s on RPi
- Rust
- Sed
- SELinux
- SSH
- sudo
- sustainability
- systemd
- tmux
- Vim
- wget

Email the editors at o...@opensource.com

They have a "write for us" page at https://opensource.com/writers


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Travis Siegel]

I suppose if they're interested in articles on accessibility, I should 
probably write one on visually impaired access.  I tried to get a screen 
reader included into the project several years ago, and was turned down, 
because of the license of the code, even though it didn't have any 
restrictions on distribution, other than the fact that whoever did so 
have a license for the a86 assembler, (which I do have), but I've also 
not done a whole lot with it since then, so perhaps it's time I did do 
something about that.  I need to figure out some way to tie that screen 
reader to a software synthesizer of some sort, so folks don't need a 
physical hardware synthesizer.  If that could be accomplished, then 
freedos would truly be completely accessible.


Of course, it is sort of accessible to visually impaired folks now, 
since running it under dosemu on linux uses the linux screen reader, and 
works just fine, though I've not tried running it on something like 
dosbox under windows, to see if the windows screen reader works for it.


I guess there's more work that needs done before I could truly write an 
all inclusive article about it being accessible to visually impaired users.


On the other hand, because dos is so easy to use, it does make it a lot 
more accessible than other operating systems like windows though, so 
perhaps there's an article there.




I'll think about it, and see if there's something I can come up with 
that seems publication worthy.


Ideas are of course welcome, which is (mostly) why I went ahead and 
posted this message.


Thanks for listening.


On 1/29/2023 2:37 PM, Linvel Risner wrote:
I’m by no means a FreeDOS expert, I’m just a user, but if anyone would 
like help writing an article I’m here to help. I know our community is 
very diverse linguistically and as a result I’m more than happy to 
lend a hand to an English as a second language speaker/writer. I would 
take no credit, you’d have 100% ownership of the article, I’d just 
like to help in some way. Reach out if y’all need anything :)


On Sun, Jan 29, 2023 at 2:20 PM John Vella  wrote:

That sounds like the sort of thing I'd be interested in doing, but
what sort of article are they looking for? Are they after a
"history of FreeDOS" type article, because that's been done so
many times it would be hard to write anything original, wouldn't it?

I look forward to hearing your thoughts.

Cheers,

John.

On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

If anyone here is interested in writing articles about FreeDOS,
Opensource.com is interested in running FreeDOS articles. I write
articles for them sometimes, and the FreeDOS articles perform very
well on the site. In fact, they recently listed FreeDOS among
their
list of "topics we're interested in for 2023." Also included
in the
list: conio and C programming.

I can tell you the editors are very welcoming, which is why I
continue
to write articles for them. If English isn't your first
language, and
you aren't confident of your English writing skills, they can help
with editing to make the final version really nice.

Here's the list they shared, in case this inspires anyone to
write an article:

- accessibility
- Ansible
- apt
- Awk
- Bash scripting
- Blender
- C getopt
- C Programming
- Chaos Engineering for K8s
- Compose Key
- conio
- Containers/Pods
- cron
- Curl
- DevOps
- DevSecOps
- dnf
- doxygen
- Emacs
- find command
- Firewall
- FreeDOS
- GDB
- GIMP
- Git
- GNOME
- GNU Screen
- Go Beginners
- Grep
- Home Automation
- Inkscape
- Intro Small Scale Scrum
- Java
- JavaScript
- Jinja2
- Jupyter
- Kdenlive
- Kubectl
- Kubernetes
- Kubernetes SRE
- Linux Apps
- Linux perms
- Logrotate
- Markdown
- MySQL
- Networking
- Parted
- Pygame eBook
- PyPI
- Python
- Raspberry Pi
- Running K8s on RPi
- Rust
- Sed
- SELinux
- SSH
- sudo
- sustainability
- systemd
- tmux
- Vim
- wget

Email the editors at o...@opensource.com

They have a "write for us" page at https://opensource.com/writers


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

On Sun, Jan 29, 2023 at 4:39 PM Karen Lewellen  wrote:
>
> What is their compensation rate?
>

Opensource.com is a volunteer-contributor site, so writing is
uncompensated. I get paid to write for other websites and magazines,
but I choose to volunteer on this one.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

> On Sun, Jan 29, 2023 at 3:01 PM Mart Zirnask  wrote:
> >
> > If I manage to build the command line mode of Rob Pike's sam editor
> > [1] for DOS, I could probably do a writeup on how to use it. Because
> > of the so-called structural regular expressions [2, 3], it is a really
> > interesting editor. Excellent for processing arbitrary strings that
> > spawn across multiple lines, since sam doesn't expect the input to be
> > full, terminated lines.

On Sun, Jan 29, 2023 at 4:30 PM Rugxulo  wrote:
> I've heard of it but never used it. It's very interesting. Plan9's
> successor to Ed, right? (Grep and Sed both came from Ed. Even AWK took
> the regex code from Egrep, I think.)

Brian Kernighan uses SAM, and I've interviewed Brian a few times.
Brian describes SAM as "ed" or "vi" on steroids. And that's how the
SAM website describes it, so I guess that's not a surprise.

SAM is a window-based editor, so it uses graphics mode. To me, this
looks a lot like the window editor on the Apollo/DOMAIN system - I
managed a small Apollo/DOMAIN network in the mid 1990s. You can find a
screenshot of SAM on Wikipedia:
https://en.wikipedia.org/wiki/Sam_%28text_editor%29#/media/File:Sam_text_editor.png

Compiling this for DOS would be an interesting exercise. Not sure if
it's possible, but give it a shot and let us know.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Karen Lewellen]

What is their compensation rate?



On Sun, 29 Jan 2023, Jim Hall wrote:


If anyone here is interested in writing articles about FreeDOS,
Opensource.com is interested in running FreeDOS articles. I write
articles for them sometimes, and the FreeDOS articles perform very
well on the site. In fact, they recently listed FreeDOS among their
list of "topics we're interested in for 2023." Also included in the
list: conio and C programming.

I can tell you the editors are very welcoming, which is why I continue
to write articles for them. If English isn't your first language, and
you aren't confident of your English writing skills, they can help
with editing to make the final version really nice.

Here's the list they shared, in case this inspires anyone to write an article:

- accessibility
- Ansible
- apt
- Awk
- Bash scripting
- Blender
- C getopt
- C Programming
- Chaos Engineering for K8s
- Compose Key
- conio
- Containers/Pods
- cron
- Curl
- DevOps
- DevSecOps
- dnf
- doxygen
- Emacs
- find command
- Firewall
- FreeDOS
- GDB
- GIMP
- Git
- GNOME
- GNU Screen
- Go Beginners
- Grep
- Home Automation
- Inkscape
- Intro Small Scale Scrum
- Java
- JavaScript
- Jinja2
- Jupyter
- Kdenlive
- Kubectl
- Kubernetes
- Kubernetes SRE
- Linux Apps
- Linux perms
- Logrotate
- Markdown
- MySQL
- Networking
- Parted
- Pygame eBook
- PyPI
- Python
- Raspberry Pi
- Running K8s on RPi
- Rust
- Sed
- SELinux
- SSH
- sudo
- sustainability
- systemd
- tmux
- Vim
- wget

Email the editors at o...@opensource.com

They have a "write for us" page at https://opensource.com/writers


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user




___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Sun, Jan 29, 2023 at 3:01 PM Mart Zirnask  wrote:
>
> If I manage to build the command line mode of Rob Pike's sam editor
> [1] for DOS, I could probably do a writeup on how to use it. Because
> of the so-called structural regular expressions [2, 3], it is a really
> interesting editor. Excellent for processing arbitrary strings that
> spawn across multiple lines, since sam doesn't expect the input to be
> full, terminated lines.

I've heard of it but never used it. It's very interesting. Plan9's
successor to Ed, right? (Grep and Sed both came from Ed. Even AWK took
the regex code from Egrep, I think.)

> I'm definitely more of an end user, but I like the simplicity of both
> DOS and traditional Unix tools.

* https://en.wikipedia.org/wiki/Unix_philosophy
* https://en.wikipedia.org/wiki/Minimalism_(computing)

"modularity", "reusability" (e.g. tools), easy to use and combine with
other programs (using plain text input and output)
"do one thing (only) and do it well"
"keep it simple", "you ain't gonna need it", "make everything a filter"

But some people *hate* simple (e.g. text) interfaces.

"UNIX is very simple, it just needs a genius to understand its
simplicity." -- Dennis M. Ritchie
"C is quirky, flawed, and an enormous success." -- Dennis M. Ritchie
"Everything should be made as simple as possible, but not simpler." --
Albert Einstein (also often quoted by Niklaus Wirth)

(Replace "UNIX" and "C in the above quotes with "DOS". That's how I feel.)

(In fairness, if a tool requires a genius, you've designed it wrong.
Most people aren't geniuses. It should be easy to use, but that
doesn't mean bloat and unnecessary complications and fancy
interfaces.)

"Everyone knows that debugging is twice as hard as writing a program
in the first place. So if you're as clever as you can be when you
write it, how will you ever debug it?" -- Brian Kernighan

> An article about "Ultra minimal minimal minimal FreeDOS" (which is how
> I sense SvarDOS) might be interesting to many curious (newbie-)
> readers, I suppose. How to stripe FreeDOS only to the most essential
> components.

Yes, definitely, but (for instance) my MetaDOS never caught on and few
ever used it. I greatly respect Mateusz's work, but I never found the
time to try out SvarDOS. (I see he's responding below already.)


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

On Sun, Jan 29, 2023 at 3:39 PM Eze B  wrote:
> I’d love a place to learn more about Freedos and a place with
> articles for a beginner/entry. My dad who passed away used a program
> named IMAGE to make programs for CNC machining on Freedos. I myself
> have 0 knowledge when it comes to Freedos, I just know how to find the
> programs but I have no idea how to print them or transfer them. Would
> love an article/tutorial on basic commands and how to navigate.

I wrote a bunch of articles about how to use FreeDOS, including how to
navigate and use the basic command line tools. You can find them
collected in a series of free ebooks. (These are the most popular
articles about FreeDOS from Opensource.com, collected as ebooks.)


Here they are:


A guide to using FreeDOS
https://opensource.com/downloads/guide-using-freedos

An advanced guide to FreeDOS internals
https://opensource.com/downloads/advanced-freedos

A guide to tips and tricks for C programming (on Linux and FreeDOS)
https://opensource.com/downloads/guide-c-programming


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

On Sun, Jan 29, 2023 at 3:42 PM Rugxulo  wrote:
>[..]
> I assume you meant we can (also) write open source articles about the
> above subjects, too. But, AFAIK, none of those directly relates or
> interacts with FreeDOS.
>

Correct. I shared the entire list (verbatim) that the editors shared,
so you could see that "FreeDOS" and "conio" and "C programming" were
there. (The list was shared on the "frequent writers" email list, not
a web page - or I would have just linked to a web page.)

I also shared the list of ideas to show that the site is pretty open
to a variety of article topics. For example, Jerome wrote a great
article about doing 64-bit math on 16-bit DOS:
https://opensource.com/article/22/10/64-bit-math


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Mateusz Viste]

On 29/01/2023 22:00, Mart Zirnask wrote:

Another article worth considering is an overview of SvarDOS, or is it
not ready for this yet? A comparison of SvarDOS versus FreeDOS -- or
am I currently in the wrong church with this? :)


Sounds great. I'd definitely welcome such write-up.


An article about "Ultra minimal minimal minimal FreeDOS" (which is how
I sense SvarDOS) might be interesting to many curious (newbie-)
readers, I suppose. How to stripe FreeDOS only to the most essential
components.


Indeed. Worth noting though, that SvarDOS is not as much about striping 
FreeDOS, than about building a minimalist yet functional DOS on top of 
the FreeDOS kernel. It is also about 8086 compatibility and a more 
accommodating approach to licenses of 3rd-party packages (four freedoms 
not required).


Mateusz


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Rugxulo]

Hi,

On Sun, Jan 29, 2023 at 12:40 PM Jim Hall  wrote:
>
> If anyone here is interested in writing articles about FreeDOS,
> Opensource.com is interested in running FreeDOS articles.
>
> Here's the list they shared, in case this inspires anyone to write an article:
>
> - apt
> - Chaos Engineering for K8s
> - dnf
> - GIMP
> - Git
> - GNOME
> - GNU Screen
> - Go Beginners
> - Home Automation
> - Inkscape
> - SELinux
> - systemd
> - tmux

I assume you meant we can (also) write open source articles about the
above subjects, too. But, AFAIK, none of those directly relates or
interacts with FreeDOS.

> - Awk
> - C Programming
> - Curl
> - Emacs
> - find command
> - GDB
> - Grep
> - Networking
> - Sed
> - Vim
> - wget

We do have:  awk gcc curl emacs find gdb grep (networking, e.g.
links2) sed vim wget

So these would be the ideal topics for us, IMHO. Sed, in particular, I
always say is my favorite tool. But I'm not sure what I would write
about using it (adapting PSR Invaders?? I used that as a testbed to
practice certain things).

Or I could write about P5 (pcom / pint ... or even P4, its weaker
predecessor). I used GNU Pascal and GNU Make to build and test that
under FreeDOS. That too can translate PSR Invaders to NASM syntax
(instead of proprietary TASM).

But I'm not sure PSR Invaders is valid since it's "sources available"
but not necessarily four freedoms "open source". (We never did get
clarification from the original author, did we? The code is very old
from 1995, so I have no idea how to contact him anyways. It's not
included in FreeDOS 1.3 but was in previous releases.)

I'm just saying, as useful as Sed is, I can't offhand think of any
"big" success story I had with it. (I also used it a bit when
rebuilding 16-bit NASM 0.98.39. But that was for TurboC. OpenWatcom
[OSI] could just build it "as is".)

I also wrote a Befunge-93 interpreter in ISO 7185 (e.g. P5) Pascal
(but it also compiled under "Turbo" dialect). That is a toy that is
not very useful.

I never learned C++, but I did adapt paq8o8 (archiver) to use CPUID to
select between upstream's NOASM, MMX, and SSE2 code. I used DJGPP and
NASM (since the default older MinGW .EXE was "MMX only" and used a
buggy tmpfile() that only worked when run as Admin on Vista). I also
bundled (and beta-tested) CWSDPMI r7 for better speed, to auto-enable
SSE, and to support swapping (virtual memory). That is GPLv2.

Networking (e.g. mTCP's FTP), curl, wget were all used in MetaDOS
(which is deprecated). It contained scripts to rebuild (almost always
with DJGPP) VILE (based upon MicroEmacs!), Ctags, BIEW/BEYE, PicoC,
xgrep [JWasm], NASM 0.98.39, AWK, JWasm.

I never did translate Charles Dye's LOCATE (from A86 to NASM). Maybe I
should do that? (I do rarely use GNU find, e.g. DJGPP, but not for
anything heavy.)

Feel free to ask E. C. Masloch to write an article on ldebug (instead
of GDB, although we have ports of that, too). I think that would make
more sense (vs. GDB).

Well, that's all I can think of right now.


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Eze B]

I’d love a place to learn more about Freedos and a place with articles for a 
beginner/entry. My dad who passed away used a program named IMAGE to make 
programs for CNC machining on Freedos. I myself have 0 knowledge when it comes 
to Freedos, I just know how to find the programs but I have no idea how to 
print them or transfer them. Would love an article/tutorial on basic commands 
and how to navigate. 

Thank you,

Eze Bommer 

> On Jan 29, 2023, at 1:02 PM, Mart Zirnask  wrote:
> 
> If I manage to build the command line mode of Rob Pike's sam editor
> [1] for DOS, I could probably do a writeup on how to use it. Because
> of the so-called structural regular expressions [2, 3], it is a really
> interesting editor. Excellent for processing arbitrary strings that
> spawn across multiple lines, since sam doesn't expect the input to be
> full, terminated lines.
> 
> I'm definitely more of an end user, but I like the simplicity of both
> DOS and traditional Unix tools. Not a native English speaker, but as a
> trained and experienced (albeit currently "former") journalist, I
> suppose I could try, especially when somebody would find the time to
> proofread my work. Provided I first manage to compile sam, somehow,
> some way, ha.
> 
> Another article worth considering is an overview of SvarDOS, or is it
> not ready for this yet? A comparison of SvarDOS versus FreeDOS -- or
> am I currently in the wrong church with this? :)
> 
> An article about "Ultra minimal minimal minimal FreeDOS" (which is how
> I sense SvarDOS) might be interesting to many curious (newbie-)
> readers, I suppose. How to stripe FreeDOS only to the most essential
> components.
> 
> I have really enjoyed Jim's articles on Opensource.com in the past,
> and the Youtube videos are really-really good! Thanks Jim!
> 
> Best,
> Mart,
> from Estonia
> 
> 1: http://http://sam.cat-v.org/
> 2: http://doc.cat-v.org/bell_labs/sam_lang_tutorial/sam_tut.pdf
> 3: http://doc.cat-v.org/bell_labs/structural_regexps/se.pdf
> 
>> On 29/01/2023, Jim Hall  wrote:
>>> On Sun, Jan 29, 2023 at 1:38 PM Linvel Risner 
>>> wrote:
>>> I’m by no means a FreeDOS expert, I’m just a user, but if anyone
>>> would like help writing an article I’m here to help. I know our
>>> community is very diverse linguistically and as a result I’m
>>> more than happy to lend a hand to an English as a second language
>>> speaker/writer. I would take no credit, you’d have 100% ownership of
>>> the article, I’d just like to help in some way. Reach out if y’all
>>> need anything :)
>>> 
>> 
>> The editors are very cool with multiple authors on
>> articles. So it's fine to buddy up with someone to write
>> an article. They will list both of you as the author.
>> 
>> And they don't pay for articles (it's a volunteer writing
>> site) so it's not like you have to split proceeds.
>> 
>> Opensource publishes articles under a Creative Commons
>> license. You still "own" the article, Opensource.com
>> doesn't claim it. You can even run the article somewhere
>> else if you want.
>> 
>> Jim
>> 
>> 
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Mart Zirnask]

If I manage to build the command line mode of Rob Pike's sam editor
[1] for DOS, I could probably do a writeup on how to use it. Because
of the so-called structural regular expressions [2, 3], it is a really
interesting editor. Excellent for processing arbitrary strings that
spawn across multiple lines, since sam doesn't expect the input to be
full, terminated lines.

I'm definitely more of an end user, but I like the simplicity of both
DOS and traditional Unix tools. Not a native English speaker, but as a
trained and experienced (albeit currently "former") journalist, I
suppose I could try, especially when somebody would find the time to
proofread my work. Provided I first manage to compile sam, somehow,
some way, ha.

Another article worth considering is an overview of SvarDOS, or is it
not ready for this yet? A comparison of SvarDOS versus FreeDOS -- or
am I currently in the wrong church with this? :)

An article about "Ultra minimal minimal minimal FreeDOS" (which is how
I sense SvarDOS) might be interesting to many curious (newbie-)
readers, I suppose. How to stripe FreeDOS only to the most essential
components.

I have really enjoyed Jim's articles on Opensource.com in the past,
and the Youtube videos are really-really good! Thanks Jim!

Best,
Mart,
from Estonia

1: http://http://sam.cat-v.org/
2: http://doc.cat-v.org/bell_labs/sam_lang_tutorial/sam_tut.pdf
3: http://doc.cat-v.org/bell_labs/structural_regexps/se.pdf

On 29/01/2023, Jim Hall  wrote:
> On Sun, Jan 29, 2023 at 1:38 PM Linvel Risner 
> wrote:
>> I’m by no means a FreeDOS expert, I’m just a user, but if anyone
>> would like help writing an article I’m here to help. I know our
>> community is very diverse linguistically and as a result I’m
>> more than happy to lend a hand to an English as a second language
>> speaker/writer. I would take no credit, you’d have 100% ownership of
>> the article, I’d just like to help in some way. Reach out if y’all
>> need anything :)
>>
>
> The editors are very cool with multiple authors on
> articles. So it's fine to buddy up with someone to write
> an article. They will list both of you as the author.
>
> And they don't pay for articles (it's a volunteer writing
> site) so it's not like you have to split proceeds.
>
> Opensource publishes articles under a Creative Commons
> license. You still "own" the article, Opensource.com
> doesn't claim it. You can even run the article somewhere
> else if you want.
>
> Jim
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

On Sun, Jan 29, 2023 at 1:38 PM Linvel Risner  wrote:
> I’m by no means a FreeDOS expert, I’m just a user, but if anyone
> would like help writing an article I’m here to help. I know our
> community is very diverse linguistically and as a result I’m
> more than happy to lend a hand to an English as a second language
> speaker/writer. I would take no credit, you’d have 100% ownership of
> the article, I’d just like to help in some way. Reach out if y’all
> need anything :)
>

The editors are very cool with multiple authors on
articles. So it's fine to buddy up with someone to write
an article. They will list both of you as the author.

And they don't pay for articles (it's a volunteer writing
site) so it's not like you have to split proceeds.

Opensource publishes articles under a Creative Commons
license. You still "own" the article, Opensource.com
doesn't claim it. You can even run the article somewhere
else if you want.

Jim


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

> On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:
>>
>> If anyone here is interested in writing articles about FreeDOS,
>> Opensource.com is interested in running FreeDOS articles. I write
>> articles for them sometimes, and the FreeDOS articles perform very
>> well on the site. In fact, they recently listed FreeDOS among their
>> list of "topics we're interested in for 2023." Also included in the
>> list: conio and C programming.
>>[..]

On Sun, Jan 29, 2023 at 1:19 PM John Vella  wrote:
> That sounds like the sort of thing I'd be interested in doing, but
> what sort of article are they looking for? Are they after a "history
> of FreeDOS" type article, because that's been done so many times it
> would be hard to write anything original, wouldn't it?


I think the editors would say they don't need another "history of
FreeDOS" article right now. The best time to write a "history of"
article is in June when our anniversary comes up again (June 29).

The best articles on Opensource.com are "how-to" articles, so you
could write an article about "how to use (command) on FreeDOS." Pick a
package in the FreeDOS distribution, and write about that. For
example, you might show how to use the E3 editor. Or you might show
how to use SORT to sort a file starting at column N (such as SORT /+2
to start sorting at column 2). Or you might demo how to use DOjS to do
some simple Javascript programming.

DOS programming articles are good too, such as the conio and C
programming articles that have done well. In my experience, the more
focused you can make these, the better. Don't write an article about
writing a full game from scratch. Write about a specific programming
topic instead. If you have a programming background, you could write
an article about "how to write a DOS version of __" such as "how to
read an arbitrary-length string in C on FreeDOS" [like Linux getline]
or "how to read keyboard input in C on FreeDOS" or "how to play sounds
on a SB16 in C on FreeDOS." Those are just some C programming
examples; Assembly or Pascal articles are good too.

Don't worry about overlap, if Opensource.com already has an article on
that topic. As long as the other article isn't too recent, they are
glad to run another perspective on the same topic. Especially if your
article is at a different difficulty level (maybe the other article
was "entry level" and yours is more "for the experienced DOS user").

Also don't worry about it being too "basic" or "entry level." As one
of the editors once commented to me (when I asked about "entry level"
articles): they have a variety of readers; some are more "expert"
folks, some are just getting started. They need articles at all skill
levels. (And these days, not a lot of readers had used DOS in the
1980s and 1990s, so it's all new to them anyway - but they are
interested to read about it.)

For Opensource.com, they only run articles about open source software.
So an article about "how to run Lotus 1-2-3 on FreeDOS" will get
rejected, because Lotus 1-2-3 is proprietary software. Even "how to
run As Easy As on FreeDOS" will get rejected; while As Easy As is free
(gratis) it is still proprietary (closed source). But "how to play
Freedoom on FreeDOS" is more likely to be accepted because Freedoom is
open source.

Jim


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[Linvel Risner]

I’m by no means a FreeDOS expert, I’m just a user, but if anyone would like
help writing an article I’m here to help. I know our community is very
diverse linguistically and as a result I’m more than happy to lend a hand
to an English as a second language speaker/writer. I would take no credit,
you’d have 100% ownership of the article, I’d just like to help in some
way. Reach out if y’all need anything :)

On Sun, Jan 29, 2023 at 2:20 PM John Vella  wrote:

> That sounds like the sort of thing I'd be interested in doing, but what
> sort of article are they looking for? Are they after a "history of FreeDOS"
> type article, because that's been done so many times it would be hard to
> write anything original, wouldn't it?
>
> I look forward to hearing your thoughts.
>
> Cheers,
>
> John.
>
> On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:
>
>> If anyone here is interested in writing articles about FreeDOS,
>> Opensource.com is interested in running FreeDOS articles. I write
>> articles for them sometimes, and the FreeDOS articles perform very
>> well on the site. In fact, they recently listed FreeDOS among their
>> list of "topics we're interested in for 2023." Also included in the
>> list: conio and C programming.
>>
>> I can tell you the editors are very welcoming, which is why I continue
>> to write articles for them. If English isn't your first language, and
>> you aren't confident of your English writing skills, they can help
>> with editing to make the final version really nice.
>>
>> Here's the list they shared, in case this inspires anyone to write an
>> article:
>>
>> - accessibility
>> - Ansible
>> - apt
>> - Awk
>> - Bash scripting
>> - Blender
>> - C getopt
>> - C Programming
>> - Chaos Engineering for K8s
>> - Compose Key
>> - conio
>> - Containers/Pods
>> - cron
>> - Curl
>> - DevOps
>> - DevSecOps
>> - dnf
>> - doxygen
>> - Emacs
>> - find command
>> - Firewall
>> - FreeDOS
>> - GDB
>> - GIMP
>> - Git
>> - GNOME
>> - GNU Screen
>> - Go Beginners
>> - Grep
>> - Home Automation
>> - Inkscape
>> - Intro Small Scale Scrum
>> - Java
>> - JavaScript
>> - Jinja2
>> - Jupyter
>> - Kdenlive
>> - Kubectl
>> - Kubernetes
>> - Kubernetes SRE
>> - Linux Apps
>> - Linux perms
>> - Logrotate
>> - Markdown
>> - MySQL
>> - Networking
>> - Parted
>> - Pygame eBook
>> - PyPI
>> - Python
>> - Raspberry Pi
>> - Running K8s on RPi
>> - Rust
>> - Sed
>> - SELinux
>> - SSH
>> - sudo
>> - sustainability
>> - systemd
>> - tmux
>> - Vim
>> - wget
>>
>> Email the editors at o...@opensource.com
>>
>> They have a "write for us" page at https://opensource.com/writers
>>
>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Anyone want to write an article about FreeDOS?

[John Vella]

That sounds like the sort of thing I'd be interested in doing, but what
sort of article are they looking for? Are they after a "history of FreeDOS"
type article, because that's been done so many times it would be hard to
write anything original, wouldn't it?

I look forward to hearing your thoughts.

Cheers,

John.

On Sun, 29 Jan 2023, 18:41 Jim Hall,  wrote:

> If anyone here is interested in writing articles about FreeDOS,
> Opensource.com is interested in running FreeDOS articles. I write
> articles for them sometimes, and the FreeDOS articles perform very
> well on the site. In fact, they recently listed FreeDOS among their
> list of "topics we're interested in for 2023." Also included in the
> list: conio and C programming.
>
> I can tell you the editors are very welcoming, which is why I continue
> to write articles for them. If English isn't your first language, and
> you aren't confident of your English writing skills, they can help
> with editing to make the final version really nice.
>
> Here's the list they shared, in case this inspires anyone to write an
> article:
>
> - accessibility
> - Ansible
> - apt
> - Awk
> - Bash scripting
> - Blender
> - C getopt
> - C Programming
> - Chaos Engineering for K8s
> - Compose Key
> - conio
> - Containers/Pods
> - cron
> - Curl
> - DevOps
> - DevSecOps
> - dnf
> - doxygen
> - Emacs
> - find command
> - Firewall
> - FreeDOS
> - GDB
> - GIMP
> - Git
> - GNOME
> - GNU Screen
> - Go Beginners
> - Grep
> - Home Automation
> - Inkscape
> - Intro Small Scale Scrum
> - Java
> - JavaScript
> - Jinja2
> - Jupyter
> - Kdenlive
> - Kubectl
> - Kubernetes
> - Kubernetes SRE
> - Linux Apps
> - Linux perms
> - Logrotate
> - Markdown
> - MySQL
> - Networking
> - Parted
> - Pygame eBook
> - PyPI
> - Python
> - Raspberry Pi
> - Running K8s on RPi
> - Rust
> - Sed
> - SELinux
> - SSH
> - sudo
> - sustainability
> - systemd
> - tmux
> - Vim
> - wget
>
> Email the editors at o...@opensource.com
>
> They have a "write for us" page at https://opensource.com/writers
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Anyone want to write an article about FreeDOS?

[Jim Hall]

If anyone here is interested in writing articles about FreeDOS,
Opensource.com is interested in running FreeDOS articles. I write
articles for them sometimes, and the FreeDOS articles perform very
well on the site. In fact, they recently listed FreeDOS among their
list of "topics we're interested in for 2023." Also included in the
list: conio and C programming.

I can tell you the editors are very welcoming, which is why I continue
to write articles for them. If English isn't your first language, and
you aren't confident of your English writing skills, they can help
with editing to make the final version really nice.

Here's the list they shared, in case this inspires anyone to write an article:

- accessibility
- Ansible
- apt
- Awk
- Bash scripting
- Blender
- C getopt
- C Programming
- Chaos Engineering for K8s
- Compose Key
- conio
- Containers/Pods
- cron
- Curl
- DevOps
- DevSecOps
- dnf
- doxygen
- Emacs
- find command
- Firewall
- FreeDOS
- GDB
- GIMP
- Git
- GNOME
- GNU Screen
- Go Beginners
- Grep
- Home Automation
- Inkscape
- Intro Small Scale Scrum
- Java
- JavaScript
- Jinja2
- Jupyter
- Kdenlive
- Kubectl
- Kubernetes
- Kubernetes SRE
- Linux Apps
- Linux perms
- Logrotate
- Markdown
- MySQL
- Networking
- Parted
- Pygame eBook
- PyPI
- Python
- Raspberry Pi
- Running K8s on RPi
- Rust
- Sed
- SELinux
- SSH
- sudo
- sustainability
- systemd
- tmux
- Vim
- wget

Email the editors at o...@opensource.com

They have a "write for us" page at https://opensource.com/writers


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user