All original text and Annotations by Jim Hall.
Translation by Michael Schienke
James Hall @-sign freedos freedos.org
[Translated 30 August 1998]
Recently available is the ftp address, which is free to copy Free-DOS, namely sunsite.unc.edu / pub / micro / pc-stuff / freedos. For this purpose, please report to me at the address @-sign freedos sunsite.unc.edu (please write in English). [Sunsite ftp is still available, but now the FreeDOS has its own domain and website on www.freedos.org, address of the coordinator also has changed.]
Was open discussion group at comp.os.msdos.misc. This is where we intend to discuss our projects and our achievements. Please join these discussions. If you want to uczestniczy? in the discussion on the Free-DOS should add your email address to a group at www.freedos.org but many users and groups comp.os.msdos.misc ?comp.os.msdos.programmer also participate in the discussion on the FreeDOS .
Free-DOS program was presented under the name of ± PD-DOS in early July 1994 as a re-implementation of the popular DOS. A hyphen was later omitted, the current program called FreeDOS.
I would stworzy? group that planowałaby write in the future, other implementations of MS-DOS. DOS was a popular operating system, and there is a large amount of equipment to assist him. Microsoft has always accused the DOS, and you can not count on the continuation of the DOS by companies such as IBM or Digital. I believe that this task should fall to the Internet, where the fate of DOS (and now FreeDOS) is not neutral and I feel that there is strong support for this project.
Free-DOS should work flawlessly on all types of computers, also on the older ones - including a processor 8088, with such a small amount of memory, and 640K. Sam Pack installation should occupy less than 1.44M. [In the meantime was so many programs with FreeDOS, now that the installation takes a lot more than 1MB. However, the installation can easily by? made from floppy disks with a capacity of less than 1MB.]
Free-DOS should not be designed for a narrow group of users. This means that the final product should be something that entertains and teaches both developers and others.
I believe that there is no problem in adjusting Free-DOS system to the 80386 and higher processors ?universities. But it remains the task of programming for the kernel.
Now we can formulate this as follows: each program under FreeDOS should use a 386 or other possible extensionswhen it will be detected - but the program should continue to work for the good old XT-conditions.
I think the Free-DOS project would be best to run with the following division into three subgroups:
¶ If you see this project which bends the axis ± ¶ success, I urge the hot ± ¶ social choice among one of the higher setting above-mentioned three sub-groups, so that leaders are born each group. This person should be burdened with the responsibility by? ¶ ± keeping your code clean and transparency ¶ ¶, and coordinate axes of ± gnie? group. For example, the leader of the group U ?serviceability should be assured in the various programs, placement of command line arguments similar to those of DOS. The leader should also ?decydowa? of acceptable extensions. [Nast ± pi ? a change, if it is about this point, the decision on a format has been transferred in a ? a ¶ appropriate place: back to the user ?u!]
Many additional programs to DOS, there is a long time as freeware and steel products were in great ?largely written by the Free Software Foundation. “[Most ¶ ? programs with FreeDOS has been here written with the co-operation interested in this system.] In each time If expected, ?s group U ?serviceability will be the first ± group ± which axis ± bends these goals. Group Drivers completed its draft brief and J ± kernel after them, by reason of their ¶ cis ? ± co-operation. For each time wa ?NYM level work is expected to release a temporary which will be available via ftp.
Additional Attention: • ? wishes I would have to all add-ons by ? y written in C or in the language of DOS files (BAT) to be assured of their continuance. [The requirement that ? o ? As will be seen here, too restrictive. However, programs for FreeDOS actions should be written in C or Assembler.] Legalization
All efforts inserting submitted in FreeDOS project actions should be obviously ¶ photo available both in object code form, and ? ? this family. Therefore, developers are urged to give their programs in accordance with the regulations brings early ¶ ± ± license, so ± as the GNU GENERAL PUBLIC LICENSE, here ± g extract from the preamble English ? y:
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is Intended to guarantee your freedom to share and change free software - to make sure the software is free for all its users. This General Public License applies to, most of the Free Software Foundation’s software and to any other program Whose authors commit to using it. (Some other Free Software Foundation software is Covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are Referring to freedom, not price. Our General Public Licenses are designed to make sure That you have the freedom to distribute copies of free software (and charge for this service if you wish), That you receive source code or can get it if you want it, That you can change the software or use pieces of it in new free programs; And You Know That You Can Do These Things.
Copyright © 1994–1998 Jim Hall
Unless Otherwise stated, FD-DOC HOWTO documents, custom research papers, buy essays,www.bedbugbitesinfo.com, more info, more info are copyrighted by Their respective authors. FD-DOC HOWTO documents May be reproduced and distributed in whole or in part, in any medium physical or electronic, cloud point of sale system as long as this copyright notice is retained on all copies. Commercial Redistribution is allowed and Encouraged, however, the author would like to be Notified of any dry distributions.
All translations, derivative works, or aggregate works Incorporating any FD-DOC HOWTO documents must be Covered under this copyright notice. That is, you May not produce a derivative work from a HOWTO and additional Impose Restrictions on its distribution. These rules are Exceptions May Be Granted under Certain Conditions, please contact the FD-DOC HOWTO coordinator at the address given below.
In short, the wish to Promote thorough dissemination of this Custom Writing information through as many channels as possible. However, we do wish to retain copyright on the HOWTO documents, and would like to be Notified of any plans to redistribute the HOWTOs.
If you have any questions, please contact the FD-DOC coordinator at the email Mentioned at the bottom of every fd-doc wiki page.