Subversion Repositories SvarDOS

AMB1index.amaöïwpkg.amaåD0.network.ama)¶lcontact.amaB
±°pkgfmt.amaEiIUpkgrules.ama®ÊXlicense.amaÈGmeaning.ama‡mUfreedos.ama–"M

AMB1
index.ama

[Âhistory.amaã,Þ¥Rtodo.amaÁ3X	]ütitle=!’§

k‡pkg.amaD0.network.amacàn
contact.amaC
±°pkgfmt.amaFiIUpkgrules.ama¯ÊXlicense.amaÉ#Gmeaning.ama'‡mUfreedos.ama—*M

                            %h*** SVARDOS HELP ***

[Âhistory.amaä4Þ¥Rtodo.amaÂ;X	]ü8086.amaE÷
ÝtitleS!Ç

                            %h*** SVARDOS HELP ***

This help documentation is a work-in-progress thing. For the time being it

provides only very limited content. (wanna help building it? get in touch with

This help documentation is a work-in-progress thing. For the time being it

us on the SvarDOS %lcontact.ama:mailing list%t!)

provides only very limited content. (wanna help building it? get in touch with

us on the SvarDOS %lcontact.ama:mailing list%t!)

=== Chapters =================================================================

=== Chapters =================================================================

 * %lpkg.ama:Packages management (install/remove/update software)

 * %lnetwork.ama:Networking

 * %lpkg.ama:Packages management (install/remove/update software)

 * %lnetwork.ama:Networking

 * %lfreedos.ama:SvarDOS vs FreeDOS: what is the story?

 * %ltodo.ama:The project's "TODO" list

 * %lfreedos.ama:SvarDOS vs FreeDOS: what is the story?

 * %lcontact.ama:How do I get in touch with the SvarDOS community?

 * %ltodo.ama:The project's "TODO" list

 * %lcontact.ama:How do I get in touch with the SvarDOS community?

 * %lhistory.ama:SvarDOS origins

 * %lmeaning.ama:What does "Svarog" mean?

 * %lhistory.ama:SvarDOS origins

 * %lmeaning.ama:What does "Svarog" mean?

==============================================================================

 * %l8086.ama:8086 compatibility list

%hSvarDOS packages management

==============================================================================

To install or remove software on your SvarDOS system, use the "pkg" command.

%hSvarDOS packages management

pkg is a package manager to allow installing new software from SvarDOS

packages and removing exising software from the system. To learn about exact

To install or remove software on your SvarDOS system, use the "pkg" command.

pkg usage, type pkg /? in the SvarDOS command line shell.

pkg is a package manager to allow installing new software from SvarDOS

packages and removing exising software from the system. To learn about exact

You may obtain many SvarDOS packages from the SvarDOS web homepage at

pkg usage, type pkg /? in the SvarDOS command line shell.

<http://svardos.osdn.io>. If your system is connected to the internet, then

you may also use the SvarDOS "pkgnet" command. pkgnet is a network tool that

You may obtain many SvarDOS packages from the SvarDOS web homepage at

makes it easy to search for SvarDOS packages in the SvarDOS repository and

<http://svardos.osdn.io>. If your system is connected to the internet, then

download them right away. Type pkgnet /? in the SvarDOS command line shell to

you may also use the SvarDOS "pkgnet" command. pkgnet is a network tool that

learn about exact pkgnet usage.

makes it easy to search for SvarDOS packages in the SvarDOS repository and

download them right away. Type pkgnet /? in the SvarDOS command line shell to

See also:

learn about exact pkgnet usage.

 * %lpkgfmt.ama:The technical format of a SvarDOS package

 * %lpkgrules.ama:Packages inclusion rules

See also:

 * %lpkgfmt.ama:The technical format of a SvarDOS package

%hNetworking

 * %lpkgrules.ama:Packages inclusion rules

WRITE ME!

%hNetworking

%hHow do I get in touch with the project's community?

For enabling network connectivity you first need to know what kind of network

adapter you have, and obtain a suitable packet driver for it. The "crynwr"

The recommended way to contact the SvarDOS community is through the project's

package contains lots of packet drivers for a variety of network adapters.

mailing list: <https://lists.osdn.me/mailman/listinfo/svardos-users>

There is also a packet driver for Intel Pro cards in the e1000pkt package, and

a driver for AMD PC-NET cards in the pcntpk package.

The project's web homepage is <http://svardos.osdn.io>

You need to get the packet driver for your card onto the machine, and load it.

Package files provide an easy way to manage software on SvarDOS. These

Then, you should be able to access the internet and get anything else you need

packages must adhere to a strict convention so they can be handled properly

using wget, htget, gopherus and other network-enabled applications.

by the SvarDOS package manager.

Note that packet drivers are mostly available for old-ish interfaces. If you

have some modern ethernet card, then there might not be a packet driver

%hPackage filenames

available for it.

Packages names must follow some basic rules. They shall be max. 8 letters long

%hFILE SHARING

(but should not be too short either, since a 1 or 2-letters package name might

be confusing), and must not be composed of characters other than a-b, 0-9 and

Perhaps these links could provide some pointers:

'_'. This for backward compatibility with short file names (8+3) and ISO 9660

<http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_MS_Client>

file systems (used on CDROMs). The package filename is always followed by the

<https://www.lazybrowndog.net/freedos/virtualbox/?page_id=374>

.ZIP extension.

There is also EtherDFS, which is a very lightweight and easy solution for

file-sharing between DOS and Linux (but it does require a Linux PC and some

%hPackage files

basic understanding of how Linux works):

<http://etherdfs.sourceforge.net/>

SvarDOS uses ZIP files as its package file format. This format has been chosen

because ZIP files under DOS have become the de facto way to distribute

%hVIRTUALBOX - PACKET DRIVER

collections of files. Also, the ZIP file format is well documented, well

supported, and in the public domain.

VirtualBox is able to emulate an AMD PC-NET NIC (you need to make sure of that

in the configuration of your VM, VirtualBox calls it "PCnet-FAST III" and it

Here below is the recommended command line that can be used to create a

should be set to "NAT"). Then, in SvarDOS you have to install the pcntpk.zip

package for a program named EXAMPLE using info-zip:

package - you don't even need to download it, it's already present on the

installation image so it should be as simple as that:

  zip -9rkDX EXAMPLE.ZIP subdir1 subdir2 ... subdirN

pkg install a:\pcntpk.zip

If you are using 7za to create your packages, then use this:

Finally, load it as such:

  7za a -mm=deflate -mx=9 -tzip EXAMPLE.ZIP subdir1 subdir2 ... subdirN

C:\DRIVERS\PCNTPK\PCNTPK INT=0x60

%hPackage directory structure

...and that's it. From now on, you should be able to search through the

available online packages and install extra software, for example:

The directory structure of a package depends on the type of packages.

For "core" packages, we have this:

pkgnet pull gopherus

pkg install gopherus.zip

  APPINFO            Put the program's LSM file here

  BIN                Binaries, such as exe and com files

(gopherus is a gopher browser)

  DOC\PKGNAME        Package documentation

  HELP               Used ONLY by the "help" package

To search through the list of available packages in the online repository, use

  NLS\PKGNAME        Localizations (NLS language files) of the package

that:

  SOURCE\PKGNAME     The source code (optional)

pkgnet search your_search_term

Non-core packages use a slightly different directory organization. For

example, if we were to consider a package FOO, we might end up with the

%hHow do I get in touch with the project's community?

following structure:

The recommended way to contact the SvarDOS community is through the project's

  APPINFO\FOO.LSM    Package meta file for the FOO program

mailing list: <https://lists.osdn.me/mailman/listinfo/svardos-users>

  PROGS\FOO\FOO.EXE  The program's executable

  PROGS\FOO\FOO.TXT  Some documentation

The project's web homepage is <http://svardos.osdn.io>

  PROGS\FOO\FILE.DAT Data file used by the FOO program

  SOURCE\FOO\*       here would be stored the foo's source code (optional)

Package files provide an easy way to manage software on SvarDOS. These

packages must adhere to a strict convention so they can be handled properly

Note the 'PROGS' directory above. This is a category to which the package

by the SvarDOS package manager.

belong. The package installer might change this directory at install time,

depending on the user's preferences. Possible categories are listed below:

%hPackage filenames

Category | Description

DEVEL    | Development tools (mostly compilers)

Packages names must follow some basic rules. They shall be max. 8 letters long

DRIVERS  | Drivers

(but should not be too short either, since a 1 or 2-letters package name might

GAMES    | Games

be confusing), and must not be composed of characters other than a-b, 0-9 and

PROGS    | User programs, tools...

'_'. This for backward compatibility with short file names (8+3) and ISO 9660

file systems (used on CDROMs). The package filename is always followed by the

Note: "DOC", "NLS", "BIN" and "HELP" directories are strictly reserved to

.ZIP extension.

      CORE packages.

%hLSM meta-data files

%hPackage files

Every package MUST contain an LSM file in its "APPINFO" directory. This LSM

SvarDOS uses ZIP files as its package file format. This format has been chosen

file is a text file that contains basic information about the package. Its

because ZIP files under DOS have become the de facto way to distribute

format is very simple, it must contain at least two lines:

collections of files. Also, the ZIP file format is well documented, well

supported, and in the public domain.

  version: x.y.z

  description: package description

Here below is the recommended command line that can be used to create a

package for a program named EXAMPLE using info-zip:

Any other lines are ignored by the SvarDOS package manager.

  zip -9rkDX EXAMPLE.ZIP subdir1 subdir2 ... subdirN

                     %h*** Packages inclusion rules ***

If you are using 7za to create your packages, then use this:

SvarDOS is a DOS distribution that comes with plenty of third-party packages.

With time, packages get updated and new packages are being added. However,

  7za a -mm=deflate -mx=9 -tzip EXAMPLE.ZIP subdir1 subdir2 ... subdirN

SvarDOS is not a shareware distribution CD, nor it is a "warez" production of

any kind. Every software that is distributed within SvarDOS must comply to a

few common sense rules, as listed below.

%hPackage directory structure

%hObjective usefulness

The directory structure of a package depends on the type of packages.

For "core" packages, we have this:

The distributed software must be useful. There is no point in distributing

hundreds of "Hello World" programs for example. The software must be useable

  APPINFO            Put the program's LSM file here

as a finished product and provide some features that are proven to be seeked

  BIN                Binaries, such as exe and com files

by at least a subset of the user base. Games are considered useful, as long as

  DOC\PKGNAME        Package documentation

they fulfill their goal of providing actual distraction.

  HELP               Used ONLY by the "help" package

  NLS\PKGNAME        Localizations (NLS language files) of the package

%hReasonable quality

  SOURCE\PKGNAME     The source code (optional)

The packaged program must exhibit traits of reasonable quality. This means

Non-core packages use a slightly different directory organization. For

that it should have a deterministic behavior, and be free of undesirable

example, if we were to consider a package FOO, we might end up with the

side-effects to the user's computer (not crashing, freezing, resulting in

following structure:

unexpected loss of data, etc). It should also provide clear, non-ambiguous

instructions to the user about how the program is meant to be used.

  APPINFO\FOO.LSM    Package meta file for the FOO program

  PROGS\FOO\FOO.EXE  The program's executable

%hFree (no cost)

  PROGS\FOO\FOO.TXT  Some documentation

  PROGS\FOO\FILE.DAT Data file used by the FOO program

The program must be free - that is, available at no financial cost. It doesn't

  SOURCE\FOO\*       here would be stored the foo's source code (optional)

have to comply to an OSI-approved license or be open-source (even if that

would be preferred), but at the very least it must be free for personal,

Note the 'PROGS' directory above. This is a category to which the package

non-commercial use.

belong. The package installer might change this directory at install time,

depending on the user's preferences. Possible categories are listed below:

%hDistribution allowed

Category | Description

The program must allow distribution without restrictions, and must not forbid

DEVEL    | Development tools (mostly compilers)

being redistributed in a re-packaged form.

DRIVERS  | Drivers

GAMES    | Games

PROGS    | User programs, tools...

%!CORE EXCEPTIONS

Note: "DOC", "NLS", "BIN" and "HELP" directories are strictly reserved to

Please note that, while the above rules are valid for all third-party packages

      CORE packages.

that may be distributed with SvarDOS, it does not apply to the 'core' packages

that contain the operating system itself. SvarDOS being a free (as in "libre")

%hLSM meta-data files

operating system, all "core" packages must comply to a libre-like license - be

it GPL, BSD, MIT, public domain, or anything that allows for unrestricted

Every package MUST contain an LSM file in its "APPINFO" directory. This LSM

distribution, provides source code and allows to modify it freely.

file is a text file that contains basic information about the package. Its

format is very simple, it must contain at least two lines:

%hSvarDOS licensing

  version: x.y.z

SvarDOS is a DOS distribution made of many different software bricks, hence a

  description: package description

single license can hardly be applied to all. However, the CORE system (that

is the SvarDOS installer, bootable floppy image and all core packages) is

Any other lines are ignored by the SvarDOS package manager.

carefully assembled from software that is "free" (as in "Freedom"), ie. that

grants the 3 basic FOSS liberties: freedom to use, modify, and redistribute.

                     %h*** Packages inclusion rules ***

This includes, but is not necessarily limited to, software released under

following licenses: GNU GPLv2, GNU GPLv3, BSD, MIT, EUPL and Public domain.

SvarDOS is a DOS distribution that comes with plenty of third-party packages.

With time, packages get updated and new packages are being added. However,

Note that, while the above applies to the core of the SvarDOS distribution, it

SvarDOS is not a shareware distribution CD, nor it is a "warez" production of

does not cover all extra packages. Additionnal software packages may or may

any kind. Every software that is distributed within SvarDOS must comply to a

not be FOSS, they are only guaranteed to be "gratis for non-commercial use".

few common sense rules, as listed below.

Read more: %lpkgrules.ama:Packages inclusion rules

%hObjective usefulness

%hWhat does "Svarog" mean?

The distributed software must be useful. There is no point in distributing

hundreds of "Hello World" programs for example. The software must be useable

The "Svar" in SvarDOS refers to "Svarog". SvarDOS is the successor of the

as a finished product and provide some features that are proven to be seeked

Svarog86 and Svarog386 distributions.

by at least a subset of the user base. Games are considered useful, as long as

they fulfill their goal of providing actual distraction.

Excerpt from Wikipedia, the free encyclopedia:

%hReasonable quality

 Svarog is a Slavic deity (...) identified with Hephaestus, the god of the

 blacksmith in ancient Greek religion (...), some researchers conclude that

The packaged program must exhibit traits of reasonable quality. This means

 Svarog is the Slavic god of celestial fire and of blacksmithing.

that it should have a deterministic behavior, and be free of undesirable

side-effects to the user's computer (not crashing, freezing, resulting in

 The only mention of Svarog comes from the Hypatian Codex, a 15th-century

unexpected loss of data, etc). It should also provide clear, non-ambiguous

 compilation of several much older documents from the Ipatiev Monastery in

instructions to the user about how the program is meant to be used.

 Russia. (...) The complete passage, reconstructed from several manuscripts,

 translates as follows:

%hFree (no cost)

 "(Then) began his reign Feosta (Hephaestus), whom the Egyptians called Svarog

The program must be free - that is, available at no financial cost. It doesn't

  ... during his rule, from the heavens fell the smith's prongs and weapons

have to comply to an OSI-approved license or be open-source (even if that

  were forged for the first time; before that, (people) fought with clubs and

would be preferred), but at the very least it must be free for personal,

  stones."

non-commercial use.

        %h*** Why would I want to use SvarDOS instead of FreeDOS? ***

%hDistribution allowed

The FreeDOS project is a free, open-source operating system that aims to be

The program must allow distribution without restrictions, and must not forbid

100%% compatible with MS-DOS. And it is awesome. So why would I want to use

being redistributed in a re-packaged form.

SvarDOS instead?

%hLong release cycles

%!CORE EXCEPTIONS

The FreeDOS project began 29 June 1994. Version 1.0 came around in 2006.

Please note that, while the above rules are valid for all third-party packages

Version 1.1 has been released in 2012, and the version 1.2 followed in

that may be distributed with SvarDOS, it does not apply to the 'core' packages

December 2016. This translates roughly to a 5-years release cycle. Granted,

that contain the operating system itself. SvarDOS being a free (as in "libre")

the DOS scene is not as active as it used to be, but still, many things happen

operating system, all "core" packages must comply to a libre-like license - be

during a few years. Such version-centric approach also requires users to

it GPL, BSD, MIT, public domain, or anything that allows for unrestricted

perform full-system upgrades every now and then.

distribution, provides source code and allows to modify it freely.

SvarDOS is very different in this regard: there are no versions at all.

%hSvarDOS licensing

Whenever a new program is included into or updated within the distribution, it

becomes immediately available through the SvarDOS reposoitory and may be

SvarDOS is a DOS distribution made of many different software bricks, hence a

pulled either through the SvarDOS website or SvarDOS' pkgnet tool. Already

single license can hardly be applied to all. However, the CORE system (that

installed systems can be easily kept up-to-date using the distribution's

is the SvarDOS installer, bootable floppy image and all core packages) is

package manager.

carefully assembled from software that is "free" (as in "Freedom"), ie. that

grants the 3 basic FOSS liberties: freedom to use, modify, and redistribute.

%hConstraints of legal nature

This includes, but is not necessarily limited to, software released under

following licenses: GNU GPLv2, GNU GPLv3, BSD, MIT, EUPL and Public domain.

The FreeDOS project mimicks a proprietary operating system, with all its APIs

and peculiarities. For this reason, the project always had to be extremely

Note that, while the above applies to the core of the SvarDOS distribution, it

careful about what can and what cannot be included within the FreeDOS

does not cover all extra packages. Additionnal software packages may or may

distribution. As a result, only "free software" (as in freedom, think GPL,

not be FOSS, they are only guaranteed to be "gratis for non-commercial use".

BSD, and so on) can make its way into the official distribution. While such

cautious approach is sane and legally safe, it is far from practical for

Read more: %lpkgrules.ama:Packages inclusion rules

users. Allowing exclusively free software means that a high number of useful

programs, tools and games are left behind. For example "freeware" tools (as in

%hWhat does "Svarog" mean?

"gratis but no source included") are a no-go. Even open-source programs can be

rejected, if they do not clearly state that they comply with an OSI-approved

The "Svar" in SvarDOS refers to "Svarog". SvarDOS is the successor of the

license.

Svarog86 and Svarog386 distributions.

SvarDOS, on the other hand, is much more liberal about including packages.

Excerpt from Wikipedia, the free encyclopedia:

Basically, anything that is objectively useful, of reasonable quality,

free/gratis and can be legally distributed in the form of a package, can be

 Svarog is a Slavic deity (...) identified with Hephaestus, the god of the

included in SvarDOS. The only exception is for the "core" system (ie. the

 blacksmith in ancient Greek religion (...), some researchers conclude that

operating system itself), which must be based exclusively on free/libre

 Svarog is the Slavic god of celestial fire and of blacksmithing.

software. Read more about %lpkgrules.ama:SvarDOS package inclusion rules%t.

 The only mention of Svarog comes from the Hypatian Codex, a 15th-century

%hFreeDOS included!

 compilation of several much older documents from the Ipatiev Monastery in

 Russia. (...) The complete passage, reconstructed from several manuscripts,

It must be noted, that altough the goals of SvarDOS and FreeDOS may be

 translates as follows:

slightly different, SvarDOS wouldn't exist without FreeDOS. Indeed, SvarDOS

uses the excellent FreeDOS kernel, as well as a few other utilities borrowed

 "(Then) began his reign Feosta (Hephaestus), whom the Egyptians called Svarog

from the FreeDOS ecosystem.

  ... during his rule, from the heavens fell the smith's prongs and weapons

  were forged for the first time; before that, (people) fought with clubs and

Read also: %lhistory.ama:SvarDOS history

  stones."

%hSvarDOS origins (history from the point of view of its creator)

        %h*** Why would I want to use SvarDOS instead of FreeDOS? ***

Mateusz Viste says:

The FreeDOS project is a free, open-source operating system that aims to be

100%% compatible with MS-DOS. And it is awesome. So why would I want to use

In the years 2005-2015 I used to perform packaging work for the FreeDOS

SvarDOS instead?

project. I wasn't pleased with the packaging tool that FreeDOS used back then

(FDPKG), so in 2012 I started working on a new package manager, with network

%hLong release cycles

support, automatic updates, etc - I named it FDNPKG. Later I also devised a

scripted way of generating an "always up to date" FreeDOS CD that I

The FreeDOS project began 29 June 1994. Version 1.0 came around in 2006.

unimaginatively called "all_cd.iso". This CD included FDNPKG and all the

Version 1.1 has been released in 2012, and the version 1.2 followed in

FreeDOS packages available at the given moment.

December 2016. This translates roughly to a 5-years release cycle. Granted,

the DOS scene is not as active as it used to be, but still, many things happen

I still wasn't satisfied with how FreeDOS clings to its notion of "releases"

during a few years. Such version-centric approach also requires users to

and that it cannot include some software because of licensing issues, so in

perform full-system upgrades every now and then.

2016 I decided to create my own distribution, that I called Svarog386 (there

was also a Svarog86 project that I had created a couple months earlier,

SvarDOS is very different in this regard: there are no versions at all.

dedicated to 8086 machines). Svarog386 naturally relied on the FreeDOS kernel

Whenever a new program is included into or updated within the distribution, it

and used the FDNPKG package manager.

becomes immediately available through the SvarDOS reposoitory and may be

pulled either through the SvarDOS website or SvarDOS' pkgnet tool. Already

Then, in 2021, I found it increasingly annoying to look after two separate

installed systems can be easily kept up-to-date using the distribution's

distributions. Over time, FDNPKG also became a huge piece of protected mode

package manager.

code, and although it was magnificent code, I was no longer happy with it: too

many features, too much data processing, too much memory required... In a

%hConstraints of legal nature

word: too much fluff. I longed for something simpler, that would do perhaps

less, but with more transparency towards the user - and something that would

The FreeDOS project mimicks a proprietary operating system, with all its APIs

work in real mode with not much RAM, so it could run even on ancient 8086

and peculiarities. For this reason, the project always had to be extremely

machines.

careful about what can and what cannot be included within the FreeDOS

distribution. As a result, only "free software" (as in freedom, think GPL,

The result of these thoughts was SvarDOS: a distribution that replaced both

BSD, and so on) can make its way into the official distribution. While such

Svarog86 and Svarog386, and that came with its own package manager - a much

cautious approach is sane and legally safe, it is far from practical for

simpler (and in my opinion much more elegant) tool than FDNPKG.

users. Allowing exclusively free software means that a high number of useful

programs, tools and games are left behind. For example "freeware" tools (as in

%hSvarDOS: The project's TODO list

"gratis but no source included") are a no-go. Even open-source programs can be

rejected, if they do not clearly state that they comply with an OSI-approved

* Replace the default (FreeDOS) edit with a smaller alternative (?) that is:

license.

  - TINY (a dozen of KiBs or so)

  - relatively simple: no need for advanced text editing features, just enough

SvarDOS, on the other hand, is much more liberal about including packages.

    to comfortably edit small (<64K) configuration files

Basically, anything that is objectively useful, of reasonable quality,

  - 8086-compatible and have modest memory requirements

free/gratis and can be legally distributed in the form of a package, can be

  - multi-lang (kitten library)

included in SvarDOS. The only exception is for the "core" system (ie. the

  - capable of (limited) copy/pasting between two files

operating system itself), which must be based exclusively on free/libre

software. Read more about %lpkgrules.ama:SvarDOS package inclusion rules%t.

* validate that CORE is 100%% 8086-compatible

%hFreeDOS included!

* replace FreeCOM by SvarCOM

It must be noted, that altough the goals of SvarDOS and FreeDOS may be

* improve installer so user can choose the target disk

slightly different, SvarDOS wouldn't exist without FreeDOS. Indeed, SvarDOS

uses the excellent FreeDOS kernel, as well as a few other utilities borrowed

* COUNTRY settings shall be configurable by localcfg (and user should be

from the FreeDOS ecosystem.

  able to define local preferences through an easy-to-use wizard during

  install time)

Read also: %lhistory.ama:SvarDOS history

* out-of-the box networking support:

%hSvarDOS origins (history from the point of view of its creator)

 - requires shipping lots of packet drivers with SvarDOS... Should CRYNWR be

   part of the install set? Or only selected, most popular drivers? Or maybe

Mateusz Viste says:

   this could be provided as a "supplemental" floppy disk?

 - user should be asked for its NIC model at install time

In the years 2005-2015 I used to perform packaging work for the FreeDOS

 - installer could also ask for a basic DHCP / static configuration

project. I wasn't pleased with the packaging tool that FreeDOS used back then

(FDPKG), so in 2012 I started working on a new package manager, with network

* add a "link" tool so users can easily create "links" to their favorite

support, automatic updates, etc - I named it FDNPKG. Later I also devised a

  programs (esp. things like zip/unzip, etc). Might be something integrated

scripted way of generating an "always up to date" FreeDOS CD that I

  within SvarCOM, or a third-party TSR.

unimaginatively called "all_cd.iso". This CD included FDNPKG and all the

FreeDOS packages available at the given moment.

* install.com - MBR changes could be done by the installer itself instead of

  system()-calling fdisk

I still wasn't satisfied with how FreeDOS clings to its notion of "releases"

and that it cannot include some software because of licensing issues, so in

* help - write more useful content!

2016 I decided to create my own distribution, that I called Svarog386 (there

  - basic DOS commands (directories, copy/rename/delete files, etc)

was also a Svarog86 project that I had created a couple months earlier,

  - common configuration files (autoexec, config.sys, pkg.cfg, wattcp.cfg..)

dedicated to 8086 machines). Svarog386 naturally relied on the FreeDOS kernel

  - networking guide

and used the FDNPKG package manager.

  - memory management basics

  - ...

Then, in 2021, I found it increasingly annoying to look after two separate

distributions. Over time, FDNPKG also became a huge piece of protected mode

* test new versions of software and update packages accordingly. special care

code, and although it was magnificent code, I was no longer happy with it: too

  must be taken for core things: kernel, freecom, fdisk, himemx...

many features, too much data processing, too much memory required... In a

word: too much fluff. I longed for something simpler, that would do perhaps

* add new, useful software to the SvarDOS repository (see the %lpkgrules.ama:rules%t)

less, but with more transparency towards the user - and something that would

work in real mode with not much RAM, so it could run even on ancient 8086

* further NLS support, improvements of existing translations and adding new

machines.

  languages -> would be nice to have some kind of web interface for submitting

  and reviewing translations

The result of these thoughts was SvarDOS: a distribution that replaced both

Svarog86 and Svarog386, and that came with its own package manager - a much

* all CORE packages should be NLS-aware (ie. translatable)

simpler (and in my opinion much more elegant) tool than FDNPKG.

* pkgnet.exe: implement the 'checkup' action for easy update checks

%hSvarDOS: The project's TODO list

* possibly plenty of other things

* Replace the default (FreeDOS) edit with a smaller alternative (?) that is:

  - TINY (a dozen of KiBs or so)

  - relatively simple: no need for advanced text editing features, just enough

                        =============================

    to comfortably edit small (<64K) configuration files

                          %hWanna help? %lcontact.ama:Get in touch!

  - 8086-compatible and have modest memory requirements

                        =============================

  - multi-lang (kitten library)

SVARDOS HELP SYSTEM ver 20220124

  - capable of (limited) copy/pasting between two files

* validate that CORE is 100%% 8086-compatible

* replace FreeCOM by SvarCOM

* improve installer so user can choose the target disk

* COUNTRY settings shall be configurable by localcfg (and user should be

  able to define local preferences through an easy-to-use wizard during

  install time)

* out-of-the box networking support:

 - requires shipping lots of packet drivers with SvarDOS... Should CRYNWR be

   part of the install set? Or only selected, most popular drivers? Or maybe

   this could be provided as a "supplemental" floppy disk?

 - user should be asked for its NIC model at install time

 - installer could also ask for a basic DHCP / static configuration

* add a "link" tool so users can easily create "links" to their favorite

  programs (esp. things like zip/unzip, etc). Might be something integrated

  within SvarCOM, or a third-party TSR.

* install.com - MBR changes could be done by the installer itself instead of

  system()-calling fdisk

* help - write more useful content!

  - basic DOS commands (directories, copy/rename/delete files, etc)

  - common configuration files (autoexec, config.sys, pkg.cfg, wattcp.cfg..)

  - networking guide

  - memory management basics

  - ...

* test new versions of software and update packages accordingly. special care

  must be taken for core things: kernel, freecom, fdisk, himemx...

* add new, useful software to the SvarDOS repository (see the %lpkgrules.ama:rules%t)

* further NLS support, improvements of existing translations and adding new

  languages -> would be nice to have some kind of web interface for submitting

  and reviewing translations

* all CORE packages should be NLS-aware (ie. translatable)

* pkgnet.exe: implement the 'checkup' action for easy update checks

* possibly plenty of other things

                        =============================

                          %hWanna help? %lcontact.ama:Get in touch!

                        =============================

%h8086 compatibility

This page presents the 8086-compatibility status of each SvarDOS "CORE"

package.

%bPACKAGE     VERSION   EXECUTABLE BSUM  8086 ok?*   Checked on

amb        20201223      amb.com A11A     yes      2022-01-30

attrib          2.1   attrib.com 2C15     yes      2022-01-30

chkdsk   0.9.2 beta   chkdsk.exe E2A9     yes      2022-01-30

choice          4.4   choice.exe 8311     yes      2022-01-30

command  0.84 pre 2  command.com E64E     yes      2022-01-30  01)

cpidos          3.0         none   -       -       2022-01-30

debug          1.25    debug.com 2E6B     yes      2022-01-31

debug          1.25   debugx.com EA59     yes      2022-01-31

deltree  1.02g.mrlg  deltree.com E20D      no      2022-01-30  02)

deltree       1.02g  deltree.com AB16     yes      2022-01-31  03)

devload        3.25  devload.com B91B     yes      2022-01-30

diskcopy  beta 0.95 diskcopy.exe 3558     yes      2022-01-30

display       0.13b  display.exe 5903     yes      2022-01-30

dosfsck       2.11c  dosfsck.exe 1CB8     yes      2022-01-30

edit           0.9a     edit.exe 8F1A     yes      2022-01-30

fc             3.03       fc.exe E718     yes      2022-01-30

fdapm     2009sep11    fdapm.com A74A     yes      2022-01-30

fdapm     2009sep11 idledpms.com C8BD     yes      2022-01-30

fdisk         1.3.4    fdisk.exe F098      no      2022-01-30  04)

fdisk         1.3.4    fdisk.exe 98BF     yes      2022-01-31  05)

find       3.0a LFN     find.com A9DA     yes      2022-01-30

format        0.91v   format.exe F11E     yes      2022-01-30

help       20220124         none   -       -       2022-01-30

himemx         3.34   himemx.exe C8E6     yes      2022-01-30  06)

kernel         2042      sys.com BF43     yes      2022-01-30

kernel         2042   kernel.sys A9B2     yes      2022-01-30

keyb           2.01     keyb.exe 945C     yes      2022-01-30

keyb_lay        3.1         none   -       -       2022-01-30

label       1.4b.ea    label.exe 1F5D     yes      2022-01-30

localcfg       0.90 localcfg.com E424     yes      2022-01-30

mem           1.11r      mem.exe 2BB8     yes      2022-01-30  07)

mode     2015-11-25     mode.com BA1E     yes      2022-01-30

more            4.3     more.exe 729B     yes      2022-01-30

move           3.3a     move.exe D3E4     yes      2022-01-30

pkg        20210212      pkg.exe 9FAB     yes      2022-01-30

pkgnet     20220119   pkgnet.exe 3D2F     yes      2022-01-30

shsucdx        3.05  shcdx86.com 0A74     yes      2022-01-30

shsucdx        3.05  shsucdx.com E5A5     yes      2022-01-30  08)

sort          1.5.1     sort.exe 21C2     yes      2022-01-30

tree          3.7.2     tree.com 2370     yes      2022-01-30

(pcntpk)      03.10   pcntpk.com 38C7     yes      2022-01-30

(udvd2)   30-Apr-13    udvd2.sys D3AB     yes      2022-01-30  09)

* Executable does its normal job or exits gracefully with a hint.

Notes:

01) also has localized versions from cmd-de.com (German) to cmd-tr.com

    (Turkish)

02) pce-ibmpc: undefined operation [C1 04] -> uncompressing with UPX

    made it work

03) replaced BSUM E20D file; used UPX --8086 option

04) pce-ibmpc: undefined operation [C1 e1] -> needed a full rebuild

05) replaced BSUM F098 file; no -1 option for TC++; used UPX --8086 option

06) exits with "At least a 80386 is required."

07) under pce-ibmpc reports 1,024K of conventional memory, but 0K free

08) exits with "Must have at least a 386."

09) exits with "No 386+ CPU; UDVD2 not loaded!"

------------------------------------------------------------------------------

Article by Robert Riebisch

SVARDOS HELP SYSTEM ver 20220201