| 1 |
|
1 |
|
| 2 |
=== SVARCOM ===
|
2 |
=== SVARCOM ===
|
| 3 |
|
3 |
|
| 4 |
|
4 |
|
| 5 |
SvarCOM is the SvarDOS command line interpreter, known usually under the name
|
5 |
SvarCOM is the SvarDOS command line interpreter, known usually under the name
|
| 6 |
"COMMAND.COM". It is designed and maintained by Mateusz Viste, and distributed
|
6 |
"COMMAND.COM". It is designed and maintained by Mateusz Viste, and distributed
|
| 7 |
under the terms of the MIT license.
|
7 |
under the terms of the MIT license.
|
| 8 |
|
8 |
|
| 9 |
For the time being, it is an incomplete, "work in progress" project. The goal
|
9 |
For the time being, it is an incomplete, "work in progress" project. The goal
|
| 10 |
is to make SvarCOM the default SvarDOS shell, replacing FreeCOM.
|
10 |
is to make SvarCOM the default SvarDOS shell, replacing FreeCOM.
|
| 11 |
|
11 |
|
| 12 |
|
12 |
|
| 13 |
*** Why replacing FreeCOM, the FreeDOS COMMAND.COM? ***
|
13 |
*** Why replacing FreeCOM, the FreeDOS COMMAND.COM? ***
|
| 14 |
|
14 |
|
| 15 |
FreeCOM is an impressive piece of software, but there are a few things that I
|
15 |
FreeCOM is an impressive piece of software, but there are a few things that I
|
| 16 |
do not like about it. SvarCOM is my attempt at addressing these things.
|
16 |
do not like about it. SvarCOM is my attempt at addressing these things.
|
| 17 |
|
17 |
|
| 18 |
- FreeCOM is not suitable for low-memory machines. It takes about 55K of
|
18 |
- FreeCOM is not suitable for low-memory machines. It takes about 55K of
|
| 19 |
conventional memory when XMS is unavailable. XMS being a 386+ thing, FreeCOM
|
19 |
conventional memory when XMS is unavailable. XMS being a 386+ thing, FreeCOM
|
| 20 |
is a poor fit for pre-386 machines. There is the KSSF hack, but it is a
|
20 |
is a poor fit for pre-386 machines. There is the KSSF hack, but it is a
|
| 21 |
kludge with many limitations. As pointed out by one of the FreeCOM authors,
|
21 |
kludge with many limitations. As pointed out by one of the FreeCOM authors,
|
| 22 |
FreeCOM is designed with 21'st century machines in mind and not IBM PC
|
22 |
FreeCOM is designed with 21'st century machines in mind and not IBM PC
|
| 23 |
compatibles (or "museum computers", as they refer to them).
|
23 |
compatibles (or "museum computers", as they refer to them).
|
| 24 |
https://www.mail-archive.com/freedos-user@lists.sourceforge.net/msg23472.html
|
24 |
https://www.mail-archive.com/freedos-user@lists.sourceforge.net/msg23472.html
|
| 25 |
|
25 |
|
| 26 |
SvarDOS will not rely on XMS, and performs runtime swapping that works on
|
26 |
SvarDOS will not rely on XMS, and performs runtime swapping that works on
|
| 27 |
any IBM PC compatible machine.
|
27 |
any IBM PC compatible machine.
|
| 28 |
|
28 |
|
| 29 |
- FreeCOM requires custom NLS files. While the vast majority of FreeDOS
|
29 |
- FreeCOM requires custom NLS files. While the vast majority of FreeDOS
|
| 30 |
programs use a single "standard" (CATS/Kitten), FreeCOM uses a different
|
30 |
programs use a single "standard" (CATS/Kitten), FreeCOM uses a different
|
| 31 |
approach with pre-compiled NLS strings, which makes it necessary to
|
31 |
approach with pre-compiled NLS strings, which makes it necessary to
|
| 32 |
distribute as many binary blobs as there are supported languages. It also
|
32 |
distribute as many binary blobs as there are supported languages. It also
|
| 33 |
makes the translation process much more difficult.
|
33 |
makes the translation process much more difficult.
|
| 34 |
|
34 |
|
| 35 |
SvarDOS will use Kitten-style translations, like other applications.
|
35 |
SvarDOS will use Kitten-style translations, like other applications.
|
| 36 |
|
36 |
|
| 37 |
- FreeCOM is a complex beast: it aims for compatibility with multiple
|
37 |
- FreeCOM is a complex beast: it aims for compatibility with multiple
|
| 38 |
compilers and supports many embedded features. This makes the code uneasy to
|
38 |
compilers and supports many embedded features. This makes the code uneasy to
|
| 39 |
follow and changes require careful testing on all supported compilers and
|
39 |
follow and changes require careful testing on all supported compilers and
|
| 40 |
all possible build variants.
|
40 |
all possible build variants.
|
| 41 |
|
41 |
|
| 42 |
SvarDOS, on the other hand, is meant to be simple and universal. It is meant
|
42 |
SvarDOS, on the other hand, is meant to be simple and universal. It is meant
|
| 43 |
to be compiled with OpenWatcom only, which makes a ton of IFDEF's go away.
|
43 |
to be compiled with OpenWatcom only, which makes a ton of IFDEF's go away.
|
| 44 |
It also won't integrate features that can be reasonably implemented as
|
44 |
It also won't integrate features that can be reasonably implemented as
|
| 45 |
third-party tools (typically: DOSKEY). It strives to reimplement the
|
45 |
third-party tools (typically: DOSKEY). It strives to reimplement the
|
| 46 |
functionalities of MS-DOS 5.0.
|
46 |
functionalities of MS-DOS 5/6.
|
| 47 |
|
47 |
|
| 48 |
- FreeCOM code is released under the terms of a toxic (GPL) license that
|
48 |
- FreeCOM code is released under the terms of a toxic (GPL) license that
|
| 49 |
restrain the freedom of its users due to its virality.
|
49 |
restrain the freedom of its users due to its virality.
|
| 50 |
|
50 |
|
| 51 |
SvarCOM is released under the terms of a liberal and permissive (MIT)
|
51 |
SvarCOM is released under the terms of a liberal and permissive (MIT)
|
| 52 |
license that does not impose limitations on how users may or may not use it.
|
52 |
license that does not impose limitations on how users may or may not use it.
|
| 53 |
|
53 |
|