Re: [Freedos-devel] FreeDOS Edlin 2.24 is out!
Okay. Fixed. -- Gregory > On 05/16/2024 3:02 PM EDT Jim Hall via Freedos-devel > wrote: > > > On Thu, May 16, 2024 at 1:49 PM Jim Hall wrote: > > > > On Thu, May 16, 2024 at 1:36 PM Gregory Pietsch via Freedos-devel > > wrote: > > > > > > FreeDOS Edlin 2.24 has been released to an unsuspecting world! Jim Hall > > > sent me some edits that moved the copyright to the help screen and > > > changed "Abort edit" to "Really quit". It's available on SourceForge > > > and Jim should mirror it very soon now! > > > > > > > > > Thanks! Unfortunately, this still advertises itself as 2.23. Can you > > fix it on SF and I can re-mirror that? > >[..] > > FYI: I've fixed the source files on my end and mirrored that version > to Ibiblio. It's at: > > https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.24/ > > > I've also uploaded a compiled version of EDLIN16.EXE (compiled using OW.BAT) > > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS Edlin 2.24 is out!
FreeDOS Edlin 2.24 has been released to an unsuspecting world! Jim Hall sent me some edits that moved the copyright to the help screen and changed "Abort edit" to "Really quit". It's available on SourceForge and Jim should mirror it very soon now! Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Edlin [was: libm-0.7 Released!]
Adding a /QUIET option would be extraneous, as it wasn't in the original Edlin and could easily be achieved by "edlin > NUL:". The copying message is important! The original Edlin had a /b option but I don't know how much of an improvement it is. Gregory > On 04/14/2024 12:43 PM EDT Jim Hall via Freedos-devel > wrote: > > > Tom Ehlert wrote: > > > btw: do you have a lot of communication about EDLIN? > > Gregory Pietsch wrote: > > > > I did have a lot of communication about Edlin when it was first released, > > but not as much anymore. > > > I actually use Edlin, and I do so without irony. It's great if you run > a command and want to make a quick BAT file out of it. I don't need > Edit for that, I can just as easily tap out a few lines in Edlin and > save it. > > One thing that would make that easier is a command line option to > suppress Edlin output. Something like /QUIET or /Q to not display the > "welcome" message (copyright & license). Because if I run a command > and want to make a BAT file out of it, the extra text might push some > interesting stuff off the top of the screen. > > Also, it would be nice if Edlin supported the /? option on DOS to > display the usage. Right now, it assumes any command line parameter is > a file: > > > C:\> edlin /? > > edlin 2.23, copyright (c) 2003 Gregory Pietsch > > This program comes with ABSOLUTELY NO WARRANTY. > > It is free software, and you are welcome to redistribute it > > under the terms of the GNU General Public License -- either > > version 2 of the license, or, at your option, any later > > version. > > > > /?: New file. > > * > > Here's an idea: if Edlin supported /? for usage, Edlin might only > display the "welcome" screen there and *not* display it during normal > program startup. That would remove my need for a /QUIET command line > option. > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] libm-0.7 Released!
I did have a lot of communication about Edlin when it was first released, but not as much anymore. -- Gregory > On 04/13/2024 2:53 PM EDT tom ehlert via Freedos-devel > wrote: > > > > Surprisingly, I have not received any communication whatsoever regarding > > libm. > > possibility 1) libm orks exactly as laid out in the documentation. > > poosibility 2) nobody cares about libm > > > btw: do you have a lot of communication about EDLIN? > > Tom > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.7 Released!
Submitted for your approval, the latest version of libm, FreeDOS's public domain math library, has been released! For this version, I have worked on edge cases regarding complex numbers and dug deep into the C99 Standard. Surprisingly, I have not received any communication whatsoever regarding libm. Where are the math nerds out there? Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
I don't keep track of whether changes had been made, but if someone wants to
hack it in, be my guest and send me an e-mail. I still have to check on what
hysterical historical behavior was for this, so I winged it.
Gregory
> On 02/05/2024 4:50 PM EST Jim Hall via Freedos-devel
> wrote:
>
>
> Not really about internationalization, so I'll make it a separate email:
>
>
> Whenever you quit Edlin, you always get this prompt:
>
> > *q
> > Abort edit (Y/n)? y
>
> I always find it a little concerning when I've already saved my file
> and Edlin asks if I want to "abort" my edit. It always makes me answer
> "n" and then write the file with "w" anyway before I use "q" again to
> quit. You get the same message with "e" ("end" : write and quit) which
> also makes me feel weird, which is why I prefer "w" then "q" to write
> then quit with individual steps so I know it's been saved.
>
> So this one is really a suggestion: can we not display "Abort edit
> (Y/n)?" if the file has been saved and no changes made? Or if that
> "change detection" would be too much to add, then maybe don't display
> that message with "e" because the program is supposed to write before
> quitting anyway.
>
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
> On 02/05/2024 4:48 PM EST Jim Hall via Freedos-devel > wrote: > > > Gregory Pietsch wrote: > > Believe me, I've had a few headaches over the years regarding NLS. This > > led to the myriad of ways to do NLS in Edlin. Anyway, all the strings > > that would need to be translated are #defines in msgs.h, and I included > > a simple filter program to generate msgs.h files from the NLS files. I > > don't know if NLS was done the right way from the start (POSIX sus4, > > anyone?) but you shouldn't have to put a hundred FreeDOS programmers > > into a room and get 101 ways of doing NLS in a program. > > > > Edlin is supposed to be TINY, and I've turned into the guardian of bloat. > [..] > > I suppose one option is to go the ed(1) route and minimize the output > it produces. But that starts to tilt dangerously into "user > aggressive" territory. > > That said, maybe Edlin uses a bit too much text. For example, when you > start Edlin, it produces this copyright message (which should be > translated) > > edlin 2.23, copyright (c) 2003 Gregory Pietsch > > This program comes with ABSOLUTELY NO WARRANTY. > > It is free software, and you are welcome to redistribute it > > under the terms of the GNU General Public License -- either > > version 2 of the license, or, at your option, any later > > version. > > > > * > > ..where "*" is the prompt. > > Does it need to produce that much text? Or could Edlin just start with > a "*" prompt? Normally, that kind of text is produced on a "show version" option. That's boilerplate for the GNU license. I wanted to have enough space for translations. > > When you ask for help with "?" Edlin produces this text: > > *? > > > > edlin has the following subcommands: > > > > # edit a single line[#],[#],#mmove > > a append[#][,#]p page > > [#],[#],#,[#]ccopy q quit > > [#][,#]d delete[#][,#][?]r$,$replace > > e<> end (write & quit)[#][,#][?]s$ search > > [#]i insert[#]t<>transfer > > [#][,#]l list [#]w<>write > > > > where $ above is a string, <> is a filename, > > # is a number (which may be .=current line, $=last line, > > or either number + or - another number). > > I don't know if the first "edlin has the following subcommands" line > needs to be there. That saves 1 line of translation, which isn't much. > But every little bit, right? I wanted the help text to be thorough! Gregory > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
Believe me, I've had a few headaches over the years regarding NLS. This led to the myriad of ways to do NLS in Edlin. Anyway, all the strings that would need to be translated are #defines in msgs.h, and I included a simple filter program to generate msgs.h files from the NLS files. I don't know if NLS was done the right way from the start (POSIX sus4, anyone?) but you shouldn't have to put a hundred FreeDOS programmers into a room and get 101 ways of doing NLS in a program. Edlin is supposed to be TINY, and I've turned into the guardian of bloat. I've tried to make it so that someone who is not in the priesthood could easily compile the thing with the right compiler, and I've tried to be broad about the compiler to use. Instead of tight 80x86 assembler, I made it portable as hell. It runs on Linux! It runs on Windows! It runs on Homer Simpson's brain! (Maybe...) Someone compiled it on a smartphone! Now I'm ranting Gregory > On 02/04/2024 2:55 PM EST Ralf Quint via Freedos-devel > wrote: > > > On 2/4/2024 11:32 AM, Jerome Shidel via Freedos-devel wrote: > > Hi, > > > >> On Feb 4, 2024, at 2:16 PM, Ralf Quint via Freedos-devel > >> wrote: > >> > >> On 2/4/2024 10:17 AM, Gregory Pietsch via Freedos-devel wrote: > >>> I made recompiling Edlin easy for non-programmers, so that shouldn't be a > >>> problem. You don't have to know a lick of C to recompile it. > >> Well, part of the problem is that in order to recompile, you need to have > >> the compiler (toolchain) installed, which isn't necessarily easy for a > >> non-programmer. > >> > >> > >> Ralf > > I have occasionally compiled edlin to provide an updated version for > > FreeDOS. > > > > As compile from source goes, EDLIN is not that bad. If I recall correctly, > > It just needs our Watcom-C to compile. Plus a little knowledge on options > > and such things. > > > > In general, it is extremely cumbersome to acquire all the exact required > > pieces to accomplish. An fairly often after spending a few hours on trying > > to get a successful compile, I will end up giving up. Therefore, I do that > > very rarely anymore for almost anything. > The problem with the whole NLS/i18n thing is that it is not only done > with just translating some text extruded from the sources. And > recompiling some programs which don't lend themselves well to the whole > "kitten" shebang. It would require a lot of testing, which needs to be > done by someone with those native language skills (plus some technical > knowledge what it is all about). A lot of command line tools might be > fairly easy to do, but for anything that is using a more formatted > screen output, this also requires to check where things are > "overflowing" (for lack of a better term right now)/misalignment... > And we have a very limited number of people that would have ALL the > required skills. > IMHO, before getting too much wound up with everything that is involved, > I think we need to make sure to have a proper English version, for > everything, > > > > As discussed in the online meeting, it would be nice to include dependency > > requirements in the package metadata. This makes me think we could possibly > > include the build-dependency requirements as well. Plus a per package > > universal build batch. That would be a lot of work and probably require > > frequent updating when packages change. > I see that there would be some effort initially to add that info, but > seriously, how much are dependencies as such changing for any given > program after that? > > > > But on the other hand, it would be very nice if all programs (excluding > > those made with commercial compilers like Turbo Pascal) could be built from > > source simply by installing the required build packages. > > > > This leads me to think, maybe we should go back to the old days when > > sources were in their own separate package and not included in the binaries > > package. > > > That was a move that I have never understood in the first place, as the > vast majority of people downloading FreeDOS are likely just interested > in getting it running, rather than doing any development. Specially if > things aren't as simple anymore as they (mostly) used to be in the days > of DOS, too many Linuxisms have crept in, which makes it so much harder > for people that are just trying to get back into DOS and haven't done > anything programming wise for the last 20-30 years, and then in things > like BASIC or Turbo Pascal, which are all "programma non grata" for a > lot of OSS license minded folks... > > > Ralf > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
I tried to make Edlin portable enough so that multiple toolchains would work on it. I normally use Cygwin with GCC and make to compile it, but FreeDOS is a DOS, so I tried to make it so that multiple compilers could compile it. Forgive my wording here... Anyway, tweaking config.h should take care of the differences in compilers. That file can also be generated through the configure script (as well as the makefile), but DOS wants things as simple as they can be. ;-) The files edlin.en and msgs-en.h in the distro are the English-language versions of the catalog and msgs.h, respectively. If I submitted a set of files for every language and compiler in existence, the politics of multiplication would come in, and I would be old and grey (or possibly dead from old age) before that project would be completed. Gregory > On 02/04/2024 1:32 PM EST Eric Auer wrote: > > > > I made recompiling Edlin easy for non-programmers, > > so that shouldn't be a problem. You don't have to > > know a lick of C to recompile it. > > One would still need the toolchain, so it would > be great if there could be somebody who already > has it (and does know C, just in case) who would > volunteer as the "send me your NLS updates for > EDLIN and I will make sure an updated EDLIN zip > will get published" person. Or, as said, a CI way. > > Eric > > PS: As mentioned on BTTR in the Book8088 compat thread > (which found out that SYS CONFIG GLOBALENABLELBASUPPORT=0 > can work around some crash in XT-IDE BIOS!) even seemingly > easy to use compiles fail in *unexpected* ways, e.g. OW > 2.0 compiles kernels in Linux, but only 1.9 does in DOS? ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] NLS in Edlin
I made recompiling Edlin easy for non-programmers, so that shouldn't be a problem. You don't have to know a lick of C to recompile it. Gregory > On 02/04/2024 12:59 PM EST Eric Auer via Freedos-devel > wrote: > > > Hi! > > > Willi Spiegl said in the meeting that there is no NLS in Edlin. I beg to > > differ! > > As with the HTMLHELP versus AMB issue, the problem, as far as > I have understood Willi, is the lack of a process, possibly > an automated pipeline, which will take updated translations > and spread them to the right places. As a non-programmer, he > would not recompile EDLIN to submit updated translations, so > we have to figure out whom and how to give the files so the > updates get published to the right, easy to use places :-) > > Eric > > PS: The same probably applies to CTMOUSE and similar tools > with compile time translations. Could be put into continuous > integration pipelines, but then updates are rather rare here. > > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] NLS in Edlin
Willi Spiegl said in the meeting that there is no NLS in Edlin. I beg to differ! There are two different ways of supporting NLS in Edlin. The first (easy) way is that in the source code, all the message strings are in a file called msgs.h, so by translating the strings, putting the translations in a msgs.h file, and recompiling, you have a version of Edlin with translated strings. When I discovered how the rest of FreeDOS was doing NLS, I put a small program in the Edlin distribution called kit2msgs that translated a message catalog into a msgs.h file with a minimum of fuss. So, to translate all the messages to German, just download edlin.de from Github, add the three new missing messages, use kit2msgs to translate that into a msgs.h file, and compile! WAY TOO EASY! The second way was to read the message catalogs in real time. There's a file called msgscats.h in the Edlin source that uses catgets to get the messages, so using that as msgs.h and compiling in catgets.c should also work. This is a bag on the side of Edlin, and to keep Edlin as small as possible, I don't recommend this way, but it's doable. This needs more debugging, though. I tried to write a version of catgets that follows the POSIX specifications and uses the same format of files as FreeDOS and fits in with the string functionality that the rest of Edlin uses, but I could use some feedback. Hopefully this clarifies things. Gregory (not George) Pietsch___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Virtual get-together?
Isn't there a virtual get-together happening now?___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Question about edlin
Of course, quotes can be escaped. -- Gregory
> On 01/22/2024 5:18 PM EST Bret Johnson via Freedos-devel
> wrote:
>
>
> That solves the problem with commas, but it looks like you may still have
> issues if there are quotes in the file.
>
> I know one thing I've done in the past with some of my programs is allow the
> use of either a double-quote ("), single-quote ('), or grave-quote (`) as
> string demarkers, which allows strings to contain any two of the three
> quote-types and still be able to identify them properly. Of course, it will
> still fail if a string contains all three quote types, but that is a rare
> situation.
>
> EDLIN's solution (at least for MS-DOS 7.1) solves all potential problems with
> Ctrl-Z since Ctrl-Z (end-of-file) should never appear in the middle of the
> kinds of files (plain text) that EDLIN works with.
>
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Question about edlin
I haven't shipped the NLS stuff since version 2.20 or so because I thought Jerome was handling that. -- Gregory > On 01/22/2024 2:11 PM EST Wilhelm Spiegl via Freedos-devel > wrote: > > > It would be great when edlin could support the 20 NLS files that are shipped > with it some day. > At least 1.24 till 1.29 of the NLS files are not supported. And I do not > speak about Chinese. > > Willi > > > > > Sent: Monday, January 22, 2024 at 6:23 PM > From: "Gregory Pietsch via Freedos-devel" > > To: "Technical discussion and questions for FreeDOS developers." > > Cc: "Gregory Pietsch" > Subject: Re: [Freedos-devel] Question about edlin > > FD edlin ignores a leading space. If you want the leading space to be > searched for, put the string in quotes; e.g. > > 1r"written"," written" > > The reason why I didn't stick a ^Z there is because I wanted to get away from > control characters in the commands, and a comma just looks better, IMHO. > > Gregory > > > On 01/22/2024 12:06 PM EST Bret Johnson via Freedos-devel > > wrote: > > > > > > > I'm using the "r" (replace) instruction correctly: 1rfrom,to will > > > start at line 1 and replace "from" with "to". > > > > > > But it looks like a leading space is ignored, so edlin treats my > > > "1rwritten, written" as just "1rwritten,written" and seems to ignore > > > it because the "from" and "to" strings are the same. > > > > > > FYI: I can add a space in the middle of a replaced word, such as: > > > > > > *1rtext,te xt > > > 1: This is a plain te xt file,written in edlin. > > > > > > Is "ignore leading spaces after the comma in the 'r' command" the > > > expected behavior from MS-DOS edlin? > > > > I haven't used EDLIN in a LONG time (decades), but just did an experiment > > with MS-DOS 7.1 EDLIN. Your problem doesn't seem to be unrecognized spaces, > > it seems to be that you're not using any sort of "escape" character to > > separate your input and output strings. I believe you think the comma > > should be the "escape" character and it isn't. There's a similar issue with > > programs like SED and AWK/GAWK. > > > > When I'm in EDLIN (at least the one with comes with MD-SOD 7.1) and I type > > "?" to get help, the syntax for the Replace command looks like this: > > > > Replace [startline][,endline][?]R[oldtest][CTRL+Znewtest] > > > > It expects you to use a Ctrl-Z (end-of-file character) as the "escape" > > character. > > If I use the Ctrl-Z "trick" I can replace things like you're wanting to do. > > > > I do not remember if earlier versions of EDLIN did this or not, nor do I > > know how FD-EDLIN works. > > > > > > ___ > > Freedos-devel mailing list > > Freedos-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-devel > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > > ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Question about edlin
FD edlin ignores a leading space. If you want the leading space to be searched for, put the string in quotes; e.g. 1r"written"," written" The reason why I didn't stick a ^Z there is because I wanted to get away from control characters in the commands, and a comma just looks better, IMHO. Gregory > On 01/22/2024 12:06 PM EST Bret Johnson via Freedos-devel > wrote: > > > > I'm using the "r" (replace) instruction correctly: 1rfrom,to will > > start at line 1 and replace "from" with "to". > > > > But it looks like a leading space is ignored, so edlin treats my > > "1rwritten, written" as just "1rwritten,written" and seems to ignore > > it because the "from" and "to" strings are the same. > > > > FYI: I can add a space in the middle of a replaced word, such as: > > > > *1rtext,te xt > > 1: This is a plain te xt file,written in edlin. > > > > Is "ignore leading spaces after the comma in the 'r' command" the > > expected behavior from MS-DOS edlin? > > I haven't used EDLIN in a LONG time (decades), but just did an experiment > with MS-DOS 7.1 EDLIN. Your problem doesn't seem to be unrecognized spaces, > it seems to be that you're not using any sort of "escape" character to > separate your input and output strings. I believe you think the comma should > be the "escape" character and it isn't. There's a similar issue with > programs like SED and AWK/GAWK. > > When I'm in EDLIN (at least the one with comes with MD-SOD 7.1) and I type > "?" to get help, the syntax for the Replace command looks like this: > > Replace [startline][,endline][?]R[oldtest][CTRL+Znewtest] > > It expects you to use a Ctrl-Z (end-of-file character) as the "escape" > character. > If I use the Ctrl-Z "trick" I can replace things like you're wanting to do. > > I do not remember if earlier versions of EDLIN did this or not, nor do I know > how FD-EDLIN works. > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Simplified Chinese Edlin?
While perusing Github, I noticed that the NLS project hasn't upgraded Edlin, which has three new messages to be translated. I also noticed that recently, many of the downloads of Edlin from SourceForge are from Hong Kong, which I found amusing. I also found a "fork" of Edlin in Github where the guy translated the messages into Simplified Chinese. This begs the question of what I should do to get Edlin to work with Simplified Chinese (I know very little about how an Asian language with 50,000 characters is used on a PC) and can we include it in NLS. I think searching for "edlin.zh-hans" on Github will find it. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDOS Edlin 2.23 is out on Sourceforge!
Oops! I keep forgetting to change the version numbers in the config.h and batch files. Fixed and re-uploaded the files to SourceForge. -- Gregory > On 11/12/2023 11:07 AM EST Jim Hall via Freedos-devel > wrote: > > > Thanks! I always love a new Edlin release. :-) > > I've mirrored it on the FreeDOS Files Archive at Ibiblio. Here's the link: > https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.23/ > > > For anyone interested, the video Gregory mentioned is here: > https://www.youtube.com/watch?v=yapAepxbaT4 > > The compile warning is at 2:47 (yes, this is confirmed fixed in Edlin > 2.23 using OpenWatcom C) > > > FYI that if you compile this on FreeDOS, Edlin 2.23 will actually > advertise itself as "2.22". To fix, you'll need to edit config-h.bc or > config-h.ow (depending on your compiler .. I used config-h.ow to > compile with OpenWatcom C) and change all occurrences of "2.22" to > "2.23" (3 occurrences in each file). > > > On Sun, Nov 12, 2023 at 9:50 AM Gregory Pietsch via Freedos-devel > wrote: > > > > When Jim compiled Edlin 2.22 for the video, I noticed that the > > OpenWatcom compiler emitted a warning. Of course, this caused a > > disturbance in the Force. The new version 2.23 cleans up that warning, > > and therefore FreeDOS Edlin can now be thrown into the gladiatorial > > arena and slay the software demons called Fear, Doubt, Uncertainty, > > and Proprietary. > > > > Gregory > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] New FreeDOS Edlin 2.23 is out on Sourceforge!
When Jim compiled Edlin 2.22 for the video, I noticed that the OpenWatcom compiler emitted a warning. Of course, this caused a disturbance in the Force. The new version 2.23 cleans up that warning, and therefore FreeDOS Edlin can now be thrown into the gladiatorial arena and slay the software demons called Fear, Doubt, Uncertainty, and Proprietary. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.6 and libmpi-0.2
In a world where mathematicians are the lowest of the low, I have sent Jim the latest versions of these low-level libraries. These versions contain mostly bug fixes. I am still wondering if someone out there can check the math. -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Meetup?
Isn't there a meet-up that's supposed to be happening now? -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Virtual get-together?
Wasn't a virtual get-together supposed to happen about now? -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.5
This is the latest version. I believe I have all the functions in libm implemented here, so please check my code and prove I do not suck. -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.4
I sent Jim libm-0.4, which includes new complex arctangent functions. -- Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.3
I just had to do it... MOSCOW, April 23, 2023 - The latest version of FreeDOS libm, version 0.3, has been released, and it is a triumph of Soviet engineering. The new version finally completes the library, adding the functions that were missing in previous versions. This is a major milestone for the FreeDOS project, and it is a testament to the hard work and dedication of the developers. The new version of FreeDOS libm is a powerful tool for developers, and it will help to advance the cause of Soviet technology. With this new library, developers will be able to create more powerful and sophisticated software, and they will be able to do so with greater ease and efficiency. The release of FreeDOS libm version 0.3 is a clear sign that the Soviet Union is once again a world leader in technology. We have always been at the forefront of innovation, and this latest release is proof of that. We are confident that this new library will be embraced by developers around the world, and that it will help to usher in a new era of Soviet technological dominance. We would like to congratulate the developers of FreeDOS libm on this remarkable achievement. They have worked tirelessly to create a library that is both powerful and easy to use, and they have succeeded beyond all expectations. We look forward to seeing what they will accomplish next, and we are proud to be a part of this great Soviet technological revolution.___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] libm-0.2
I'm attempting to fix some of my older things that got delayed because of mental burnout. Three years in the making, libm-0.2 has a few new functions in it, such as implementations of the Bessel functions, a new implementation of ctan and ctanh, and a couple of other things. I was hoping someone could help with testing and whatnot. I'll get the ZIP file to Jim in a few. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS Edlin 2.22 released!
Twenty years in the making, FreeDOS Edlin 2.22 is now released unto an unsuspecting world. The latest bug report/feature request that I have tried to tackle is one that backup files aren't created if the backup file already exists and is read-only. This is consistent with historical (hysterical) behavior. Gregory___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Editing the FreeDOS 28th Anniversary Ebook
Some one-line questions are more telling than others. -- Gregory > On 07/25/2022 5:31 PM Jim Hall wrote: > > > On Mon, Jul 25, 2022 at 2:01 PM Gregory Pietsch wrote: > > > > In mine, there's an answer where I answer a different question than > > the one that's given (I answered the "desert island" question with a > > question about why I'd want to go somewhere without electricity.) Could > > you please fix it? > > > > Gregory > > > > Fixed! I added the "desert island" question back in, so it makes > sense. (I shortened the questions when I dumped these to text files.) > > > What programs do you like to run on FreeDOS? Do you have a favorite app, > > or favorite game? If you could take only one DOS program with you to a > > desert island, what would it be? > > > Although I'll remove your reply to that question when I do the next > step of assembling the first draft. Several folks gave a 1-line > response or a non-response to one or more questions, and I won't > bother including those in the book. > > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Editing the FreeDOS 28th Anniversary Ebook
In mine, there's an answer where I answer a different question than the one that's given (I answered the "desert island" question with a question about why I'd want to go somewhere without electricity.) Could you please fix it? Gregory > On 07/25/2022 2:45 PM Jim Hall wrote: > > > Hi everyone > > I wanted to share an update on the FreeDOS 28th Anniversary Ebook. You > may remember this is the book of interviews with FreeDOS developers > and users. > > I've started a GitLab project for the ebook. You can find it here: > https://gitlab.com/freedosproject/freedos28/ > > I've uploaded plain text copies of the interviews I've received so > far. If you are interested in participating in the ebook, and > ESPECIALLY IF YOU ALREADY RESPONDED TO THE INTERVIEW, please take a > look at the project. If you responded to the interview, but you don't > see your interview listed, THAT MEANS I DON'T HAVE A COPY OF YOUR > INTERVIEW (I may have missed it in my Inbox, or it was caught by a > spam filter, etc.) If your interview isn't there, LET ME KNOW so I can > get your interview response added. > > If you want to contribute to the ebook, but haven't responded to the > interview, this is your last opportunity to do so. You can find the > list of questions in the GitLab project. > > I originally planned to have other technical editors help me with the > editing process, but that didn't work out due to timing. So I will do > the editing myself, with input from the community! I'll plan to edit > everything in the open on GitLab. > > The first phase was to get everyone's raw interview responses into > GitLab. The next phase is to organize the responses into a structure > or format. I'll do those edits in LibreOffice, which is how I'll > publish the ebook. Drafts will get posted as ODT and PDF files. > > The updated (expected) schedule is: > > July to early August - edit > early to mid August - first draft > community review opportunity > mid to late August - second draft > community review opportunity > late August - final (published) > > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS Edlin 2.21 is here!
After I released FreeDOS Edlin 2.20 onto an unsuspecting world, I noticed a couple of items I needed to address in the source code. In an effort to produce a more perfect FreeDOS Edlin, I have addressed those issues and released FreeDOS Edlin 2.21 to SourceForge! Please send me feedback___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] "Badges" for FreeDOS contributors
After thinking about this, FreeDOS Edlin will have its twentieth anniversary of the earliest date in the change log on March 3, 2023. Gregory > On 06/19/2022 7:41 PM Jim Hall wrote: > > > Hi everyone > > I thought about celebrating the FreeDOS 28th anniversary by sharing > some "badges" for FreeDOS contributors. Anyone who wants to can > download your own badge to use on your website, in your social media, > ... whatever. These will be similar to the "badges" that SourceForge > created when they recognized a bunch of projects (including FreeDOS) a > few months ago. You can find those SF badges at: > https://www.freedos.org/images/sfbadges/ > > I am thinking I'll create the badges listed below. WHAT BADGES AM I > MISSING? If I've missed a contribution area, let me know. > > Here's the initial list of "badges": > > 1. FreeDOS User (for anyone who uses FreeDOS) > > 2. FreeDOS Tester (for anyone who tests FreeDOS and submits bug reports) > > 3. FreeDOS Translator (for anyone who translates FreeDOS into other languages) > > 4. FreeDOS Documenter (for anyone who writes "Help" articles or > contributes to the wiki) > > 5. FreeDOS Developer (for anyone who writes/has written FreeDOS > programs ... I'll create this badge with a few variations so folks can > show how long they've been a FreeDOS developer: 5 years, 10 years, 15 > years, 20 years, 25 years) > > 6. FreeDOS Fan (a general-use badge to show your support for FreeDOS) > > > The badges will all have the same basic outline or layout, with > different decorations (such as color, etc) for each variation. > > I'll share them in SVG and PNG format on the website on June 29 (the > FreeDOS 28th anniversary). Folks can download the badge or badges that > they want to use. > > > Jim > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Historical vs. Hysterical Edlin Versions
If anyone finds any bugs or errors in my code, don't hesitate to tell me, as long as it's legitimate. I do not believe that I introduced new bugs in 2.20, but you never know. As far as I know, there are two giant missing pieces of Edlin that I can surmise from all I have read about it. One is the obsolete workings of M$ Edlin's 'a' command. The second is implementing the F-keys and others with regard to modifying lines. The former is truly an obsolete way of dealing with large files; the latter I am constantly thinking about how to do it portably without making it look like a bag on the side of Edlin. If anyone can help remedy this and other headaches, I'd be happy. Gregory On 5/17/2022 3:23 PM, Jim Hall wrote: I'm resharing an announcement from the website about Edlin 2.20: Thanks to Gregory Pietsch, there is a new version of the classic FreeDOS Edlin editor. If you haven't used Edlin, it's a text-mode "line editor" for DOS that's similar to the Unix "ed(1)" editor. Some of the more visible changes in this version of Edlin: + Added '#' as a synonym for "$+1" + Added "New file." for new filenames on command line + Added "Abort edit (Y/N)? " message. You can download the source code from Edlin at SourceForge <https://sourceforge.net/projects/freedos-edlin/>. We have also mirrored this release in the FreeDOS Files Archive at Ibiblio, under /files/dos/edlin <https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.20/> <<<< I've also compiled Edlin 2.20 for DOS (both 16-bit and 32-bit) and shared my executables here: https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.20/ edlin-220exe.zip *I did only light testing of these Edlin executables, but they compiled without error and they seem to run fine for me. Please test yourself before using. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Historical vs. Hysterical Edlin Versions
FreeDOS Mavens, I'm thinking of editing Edlin to match historical behavior after downloading a 1982 IBM DOS manual and a 1987 Microsoft OS/2 manual I found floating around the 'Net. I want to make Edlin still the small program it has always been without adding things that would make the executable super-huge, so I want to get some feedback from the list before I do anything. The things I am considering are below: 1. At the beginning of the program, when Edlin reads the file whose name is on the command line, the historical thing to do is output "End of input file" if the entire input file has been slurped in or "New file" if the file does not exist yet. FreeDOS Edlin just runs the same code as the T command to slurp the file in and give the output of that command, which is the number of lines read. 2. The IBM DOS manual adds "#" as the line number that's one beyond the last line. This should be an easy add that doesn't change existing behavior. 3. The historical behavior for the Q command is to always verify that the user wanted to quit the program with an "Abort edit (Y/N)?" message. 4. Historically, the E command erased any backup copy (i.e. the file with the .BAK extension) after writing and before quitting. I don't know if I want to emulate this behavior. I'll probably come up with some more. I am reluctant to add strings to Edlin, though, because it would make Jerome's i18n project more hairy. Nevertheless, part of the project's goals are to emulate historical behavior and eliminate hysterical behavior. There's a lot more there that I want to tackle just as soon as I figure it out, but I want to tackle the low-hanging fruit first. What do the list-subscribers say? Gregory ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Thinking about FreeDOS 2.0
EVERYBODY! -- Gregory On 3/31/2022 9:42 PM, Michael Brutman wrote: Please forgive me for getting lost on this thread, but what exactly is the problem that we are trying to solve? Are we trying to make things simpler for novice users? Advanced users? FreeDOS maintainers (Jerome in particular) ? -Mike ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Thinking about FreeDOS 2.0
We're still working on that telepathic user interface and all those things we've dreamed Microsoft put into MS-DOS. I'm still working on everything I have sent in, but it would be nice if I got some direction on things that can be improved. Gregory On 3/3/2022 5:28 PM, Deposite Pirate wrote: On Thu, 3 Mar 2022 00:13:32 -0600 Jim Hall wrote: On Sun, Feb 20, 2022 at 4:16 PM Jim Hall wrote: [..] I'm sure we'll want to discuss "1.4" or "2.0" or whatever version comes after 1.3. (I can start a new conversation next week to talk about that.) Now that FreeDOS 1.3 has been out for a little while, I wanted to start thinking about what comes next. Let's use this thread to discuss it. What would you like to see changed or added (or removed) in the next distribution? * Merge the kernel, FreeCOM as well as all the base utilities that haven't been updated in years (abandoned?) in one single repository with one single build system to lower the barrier to entry for newcomers to improve FreeDOS. Added bonus down the line, it may then be possible to directly generate various floppy images like ELKS does and have a stripped down build with binaries suitable for XTs. * In my testing, jemm386 isn't a compatible replacement for emm386. Most games that require EMS I've tried just crash while they work fine with PC-DOS and friends. It's also the last piece of the puzzle that prevents Windows 3.x from working in FreeDOS. Seems like solving these problems would be a major achievement. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] is there anyway i can contribute to freedos's development with C++?
It's possible, but all the core FreeDOS stuff is in C or 80x86 Assembler. Often, there's not a whole lot in C++ that you have to use or can use for things. I'm sure some of the games might be in C++. Gregory On 1/10/2022 11:16 PM, geff wrote: hey all, sorry for the noob question. is there anyway i can contribute to freedos's development with C++? Cheers! ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Let me count the ways
Not to mention that one can compile Edlin either using the msgs-*.h or something closer to the message catalogs. I am still waiting for Klingon, but I have close to 20 sets of language strings. Gregory On 12/25/2021 3:31 PM, Jerome Shidel wrote: Thank you for your help in testing RC5. So far, testing has gone very well. Regarding installation and the media, there have been a few minor issues that have been already corrected. A couple that still need fixed and a few things that need investigated further. This of course is not referring to bugs reported in things like the drivers, installed programs, kernel, etc. Just the two installers and release media. Most issues were regarding NLS. There are a multitude of ways to install FreeDOS 1.3-RC5. There are so many variations it is impractical for just a few people to test. Having the community root out edge case issues is a big help. How many variations for installation can occur? Let me count (most of) the ways… * boot LiveCD to Live Environment, run setup. (uses primary installer FDI, normal mode) * boot LiveCD to Live Environment, run setup adv (FDI in advanced mode) * boot LiveCD to Live Environment, change to FDI-x86 dir, run setup (uses FloppyEdition installer, FDI-x86 in normal mode from a subdir) * boot LiveCD to Live Environment, change to FDI-x86 dir, run setup adv (FDI-x86 in advanced mode from a subdir) * boot LiveCD to Install to Hard Disk. (FDI in normal mode) * boot LiveCD to Install to Hard Disk, exit and run setup adv (FDI in advanced mode) * boot LiveCD using Easter Egg, (FDI-x86 in advanced mode from a HD image) * boot LiveCD using Easter Egg, exit installer run setup (FDI-x86 in normal mode from a HD image) * boot LegacyCD (FDI in normal mode) * boot LegacyCD, exit and run setup adv (FDI in advanced mode) * boot LegacyCD, exit, change to FDI-x86, run setup (FDI-x86) * boot LegacyCD, exit, change to FDI-x86, run setup adv * boot LiteUSB (FDI in normal mode) * boot LiteUSB, exit and run setup adv * boot FullUSB * boot FullUSB, exit, run setup adv * boot FullUSB, exit, change to FDI-x86 dir, run setup (FDI-x86) * boot FullUSB, exit, change to FDI-x86 dir, run setup adv * boot FloppyEdition (any diskette version), (FDI-x86 normal mode) * boot FloppyEdition (any diskette version), exit, run setup adv (FDI-x86 in advanced mode) * xcopy FloppyEdition to some hard disk subdir and run setup. * xcopy FloppyEdition to some hard disk subdir and run setup adv. all the CD versions, boot from CD boot Floppy and repeat. all versions, preexisting OS installed or not, then with backup or not. all versions, BASE or FULL, with our without sources. all ADVANCED FDI installers, custom user package selection. all FDI versions, variations on user language and keyboard settings. Once that is done, repeat all steps on different virtual machines and different hardware. Perhaps if your good a math, you could figure out all the permutations. Don’t forget all those multipliers. :-) And this only covers the most likely scenarios. There are others. Only the config and boot process changes. The two installers and tools are the same. While many of the items mentioned effect the installers in subtle ways, some tests only verify no pieces went missing during media creation. It’s far to much for one or two people to fully test. Once again, thank you for your assistance. :-) Jerome ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] wc
I'm trying to get more of the low-hanging fruit of the GNUish 2.0 project done. This time, it's wc, the word-counting program. Gregory wc - print the number of bytes, words, and lines in files The wc program counts the number of bytes, whitespace-separated words, and newlines in a given file, or the standard input if none are given or when a file named '-' is given. It prints one line of counts for each file, and if the file was given as an argument, it prints the filename following the counts. If more than one filename is given, wc prints a final line containing the cumulative counts, with the filename 'total'. The counts are printed in the order: lines, words, characters (if specified), bytes, the maximum number of characters in a line. By default, wc prints all three counts. Options can specify that only certain counts be printed. Options do not undo others previously given, so wc --bytes --words prints both the byte counts and word counts. COMPILING: On a Cygwin installation, it's as easy as ./configure;make;make install Other systems may differ. One may have to modify config.h (provided), then individually compile wc.c and getopt.c. Then load them into an executable. OPTIONS: -c, --bytes Print only the byte counts. -l, --lines Print only the newline counts. -m, --chars Print only the character counts. -w, --words Print only the word counts. -L, --max-line-length Print only the maximum line width of a file. Tabs are considered to be moving the column to a multiple of 8; nonprintable characters have a width of zero. --files0-from=FILE Get the filenames from a file instead of the command line. Within the file, the names are delimited with null characters. This option is useful with the output of the find command with the -print0 option. --help Print a usage message and exit with a non-zero status. --version Print version information on standard output then exit. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] I resubscribed!
I resubscribed to the list to participate in Jim Hall's GNUish project. I realize that I haven't upgraded edlin since 2010. I have the sources for 2.15 but Sourceforge locked me out of the project for some reason and I haven't been able to log in there. Anyway, it is rated 5 stars out of 5. ;-) If anyone has anything they would like to contribute for edlin, send me your sources as I am the new (old) maintainer! I sent Jim Hall my version of the Unix command 'cat' for the GNUish project. The cat command concatenates files and prints them to standard output. OPTIONS: -b, --number-nonblank Number all nonblank output lines, starting with 1. -e Equivalent to -vE. -n, --number Number all output lines, starting with 1. -s, --squeeze-blankReplace multiple adjacent blank lines with a single blank line. -t Equivalent to -vT. -u Ignored; for Unix compatability. -v, --show-nonprinting Display control characters except for linefeed and tab using '^' notation and precede characters that have the high bit set with 'M-'. -A, --show-all Equivalent to -vET. -E, --show-endsDisplay a '$' after the end of each line. -T, --show-tabsDisplay tab characters as '^I'. --help Print a usage message and exit with a non-zero status. --version Print version information on standard output then exit. On systems like MS-DOS that distinguish between text and binary files, 'cat' normally reads and writes in binary mode. However, 'cat' reads in text mode if one of the options '-bensAE' is used or if 'cat' is reading from standard input and standard input is a terminal. Similarly, 'cat' writes in text mode if one of the options '-bensAE' is used or if standard output is a terminal. Gregory -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Edlin 2.15 is on Sourceforge!
Yes, a new version of Freedos Edlin is on SourceForge! The version is to fix bugs in the previous version. FreeDOS Edlin is the standard line editor in the FreeDOS operating system. Without it, the kernel developers would not have anything to use. Gregory Pietsch -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS Edlin 2.14 is out!
I haven't seen anything on the developer list recently, so I thought I'd give an update. Yes, FreeDOS Edlin 2.14 has been released to an unsuspecting world! I made a small change to the catgets routines, so I'd thought I'd make a new release. It's on Sourceforge at the usual location for this stuff, and should be mirrored along with versions 2.12, 2.12a, and 2.13 when someone wakes up at FreeDOS headquarters. FreeDOS Edlin is the lynch-pin of the FreeDOS operating system. Without it, none of the other programs in the Base group would work, including the kernel. Really. Gregory Pietsch -- Download new Adobe(R) Flash(R) Builder(TM) 4 The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly Flex(R) Builder(TM)) enable the development of rich applications that run across multiple browsers and platforms. Download your free trials today! http://p.sf.net/sfu/adobe-dev2dev ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] IDE-type code editor
FreeDOS Edlin! (Actually, I use the joe editor under Cygwin to do a lot of my programming, and then make sure it compiles under MSVC 6.0 and OpenWatcom with a DOS target before sending it out.) Gregory Pietsch Joe Emenaker wrote: Is there a particular code editor (ideally, with IDE-type features like: being able to bind the maker/compiler to a keystroke, capturing of compiler errors into a separate window, etc.) that people here are using to work on the packages they maintain? Given that there are some really nice features that we have available nowadays (like CVS/SVN) which probably aren't available in a true DOS-based editor, is it a better idea to use a Windows editor/IDE and just instruct the compiler to build for DOS? What is everyone else using to develop/debug their DOS apps here? - Joe -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] German Translation
Jonas Tröger wrote: Hello, I'm very interrested in the new FreeDos 1.1 release and i want to help by checking German Translations Jonas T. Eric Auer is the guy who has done a lot with German translations. As for Edlin, well, he did them and I let them into the program. Gregory Pietsch -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Edlin 2.12a is out!
It has been ages. They wondered if FreeDOS Edlin, the one project without which the FreeDOS project would never reach that all-important Version 1.1 milestone, was still being developed. Well, fret not, faithful FreeDOS lovers! Version 2.12a is out on SourceForge. Thanks to Rugxulo who found a few warnings with 2.12. Gregory Pietsch, the czar in charge of Edlin -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS Edlin 2.12 is out!
Yes, the lynchpin of the whole FreeDOS project, the FreeDOS Edlin line editor, without which the entire FreeDOS project would never reach Version 1.1, is now up to version 2.12! The latest version is on Sourceforge after I figured out how to upload it. This version corrects a perceived bug in 2.11. Gregory -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Help files in spanish
There were only two files in the ZIP file, so you might want to include everything else besides index.htm and help.htm. For the HTML, you should use mnemonic representations for non-ASCII characters instead of numerical representations. Gregory Pietsch Natan Saidon wrote: I translated the FreeDOS help files to Spanish. Just extract to %fdosdir%\help\ directory PLEASE TEST -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Volunteering
It's okay if you know vaguely about the internals of something, but when you write an imitation of it, chuck all that code aside and try to write yours along different lines. For example, if the original was written to conserve memory usage, go for speed instead, or go for generality. The code will look much different. If the original was in tightly-written assembler, rewrite it in C. As for compiling, I do not release binaries, so you can download the source to FreeDOS Edlin (latest version: 2.11) and try to compile that using whatever compiler you wish. You might have to tweak the config.h file; just read the comments there. Another thing you could do is download all the sources and see in your opinion what looks great, what looks like garbage, what could be reusable. The great stuff, leave alone; the garbage, write a better version; the reusable stuff goes into libraries. ;-) Gregory Pietsch usul wrote: Japheth, Politics of any sort are this way. It is always extremes that shout the loudest. In my opinion is aways in the middle the answer always is in the middle, the middle rarely if ever has an advocate. :P I like open source and free software. More the spirit of the law though then the law itself. I feel code should be shared so things become standard. So much effort is repeated from developer to developer. If the license provides for that it is good enough for me. The minor differences are merely semantics to me. As for which Assembly Compiler I will use, I probably end up using which ever is the official one, its easier to follow in the beginning than trying to rock the boat. Besides at this point I am more interested in programming and being part of the project than arguing with people. As for decompiled source, I don't mind reading books. If the book was published and the code writer didn't file a lawsuit then its like they gave their permission. But I wont decompile or look at code someone else stole. The person that fences stolen property is as guilty as thief. That being said I rarely have looked at code I didn't think I could write better (even my own LOL). We can do it better. Passion vs paycheck. :) -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.11.31/2028 - Release Date: 03/28/09 07:16:00 -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Edlin 2.11 released to a unsuspecting world ...
After a couple of years of hibernation, I have decided to release version 2.11 of FreeDOS Edlin, the one package without which the entire FreeDOS environment would be like the grains of sand in a fine wind. It's on SourceForge. Gregory Pietsch -- ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Getting rid of kitten
as a delimiter for rulesets, so to support the kitten
rulesets below, NLSPATH would have to be
c:\NLSPATH\%L\cat;c:\NLSPATH\cat.%L. The name parameter given to
catopen isn't used at all. Your application isn't playing nice with all
the other applications that are using the system.
In other words, if somebody's LANG parameter is en, then according to
the kitten rules, edlin's English-language catalog file would be called
c:\NLSPATH\en\cat or c:\NLSPATH\cat.en . The English-language catalogs
for other programs would have to have the same names as well, causing
headaches for whomever set up the system. It is possible to put the
catalogs for all the programs in the system into the same file, but that
would be a maintenance nightmare.
I am trying to fix this by doing it the right way: having a flexible
NLSPATH and LANG environment variables. I know we can make this work
without causing i18n headaches.
Gregory
Jim Hall wrote:
On Sat, Aug 23, 2008 at 8:40 PM, Gregory Pietsch [EMAIL PROTECTED] wrote:
FreeDOS maniacs,
I was playing around with the implementation of edlin as it has been
over a year since 2.10c, and was wondering if I could get rid of the
ancient kitten.c and kitten.h files in the implementation.
I am currently trying to tweak the catgets.c implementation so that it
will be more Posix-like: relying on the environment variables LANG and
NLSPATH for the information needed to find message catalogs.
I'm trying to make the edlin implementation be at the forefront of
innovation for FreeDOS. At the same time, Jim Hall might complain if I
killed kitten by replacing it with something better (the files
nl_types.h and catgets.c in edlin implement the catgets functionality)
and I don't want to hurt his feelings.
What does everyone think about this?
Gregory
I doubt Jim would mind very much. :-) He says on his page
http://www.freedos.org/jhall/ that Kitten is not currently
maintained, so he would probably be happy for someone to take this on
and provide some updates. But that's just a guess - you might try
emailing him. ;-)
However, what version of Kitten or Cats do you have? (Kitten replaced
Cats.) Was it a locally-written version for Edlin? (I've never looked
at Edlin's i18n code.) You mentioned catgets.c, so I think Edlin must
have an old version of Cats, although Cats didn't have its own
nl_types.h.
Kitten already uses LANG and NLSPATH to find the catalog files. The
latest version of Kitten is kitten-c'.
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/cats/kitten-c.zip
Like Catgets, when looking for a catalog, Kitten will scan the paths
provided in NLSPATH to look for the catalog file. In Kitten, this is a
very simple ruleset:
For each path in NLSPATH {
1. look for: NLSPATH\LANG\cat
2. look for: NLSPATH\cat.LANG
}
-jh
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Getting rid of kitten
I didn't write the spec, I just have to implement it. I thought it would be easier if I started from scratch because I had a lot of low-hanging fruit to throw in. Seeing that MS-DOS was vaguely Unix-like, it makes sense to implement as much of what was in the Posix standard unless what's written in there is conflicting or unreasonable. Otherwise, we'd have a half-assed implementation, and nobody wants that. Gregory Eric Auer wrote: Hi! Given your description it definitely makes sense to keep all those features in catgets - it is good that kitten is smaller than that :-) Of course for being portable to Unix, catgets can be useful. Yet I never saw any % escape in and i18n setting on a Linux yet, so most people would not even notice if this is not supported by a version of catgets... Eric - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Getting rid of kitten
FreeDOS maniacs, I was playing around with the implementation of edlin as it has been over a year since 2.10c, and was wondering if I could get rid of the ancient kitten.c and kitten.h files in the implementation. I am currently trying to tweak the catgets.c implementation so that it will be more Posix-like: relying on the environment variables LANG and NLSPATH for the information needed to find message catalogs. I'm trying to make the edlin implementation be at the forefront of innovation for FreeDOS. At the same time, Jim Hall might complain if I killed kitten by replacing it with something better (the files nl_types.h and catgets.c in edlin implement the catgets functionality) and I don't want to hurt his feelings. What does everyone think about this? Gregory - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] A call to action - FreeDOS 1.1
The back end of FreeDOS edlin can be used as the back end of any editor, and I purposefully tried to make it as tight as I possibly could without sacrificing robustness. -- Gregory Kevin O'Connor wrote: On Fri, Aug 01, 2008 at 06:40:31PM -0700, H. Peter Anvin wrote: If there is any DOS editor I miss, it's Qedit: http://www.umich.edu/~archive/msdos/editors/qedit/qedit300.zip I used to use sled: http://www.wilmott.ca/sled.html I don't know how he managed to build a fully functional editor in 17K. Unfortunately, I don't think the source code was ever released. -Kevin - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] (no subject)
The problem here is that we don't want Bill Gates suing us for copyright violations. There's no reason we can't do a reimplementation of MS-DOS; we just have to do it cleanly. Gregory Pietsch - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Edlin 2.9A is on SourceForge!
Jim Hall wrote: On Sun, 2006-11-26 at 17:16 -0500, Gregory Pietsch wrote: Although it's personally been a difficult month for me, I have triumphed once again with a new version of FreeDOS Edlin, the one project without which the entire FreeDOS project would be plunged into darkness. Version 2.9A reflects everything that I have received as improvements since the 2.9 release, including a new translation of the msgs.h file into Polish. I also threw in a kit2msgs filter program to make things easier for the i18n crowd. -- Gregory Pietsch What's the URL? http://sourceforge.net/projects/freedos-edlin/ -jh - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Edlin 2.9A is on SourceForge!
Although it's personally been a difficult month for me, I have triumphed once again with a new version of FreeDOS Edlin, the one project without which the entire FreeDOS project would be plunged into darkness. Version 2.9A reflects everything that I have received as improvements since the 2.9 release, including a new translation of the msgs.h file into Polish. I also threw in a kit2msgs filter program to make things easier for the i18n crowd. -- Gregory Pietsch - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] New FreeDOS Edlin 2.9 on SourceForge!
There's a new version of FreeDOS Edlin, and it's on SourceForge! I've been trying to get to Jim Hall for days to mirror this information on FreeDOS's homepage, but I haven't been able to reach him. Gregory Pietsch - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] 8086/XT compatibility issues for FreeDOS 1.0
Joris van Rantwijk wrote: Hello Gregory, Gregory Pietsch wrote: Hmmm... for some reason, edlin was not included in either list. So, does it work or not? The nature of a non-exhaustive list is that some things are not included. But I just tested EDLIN; it runs, but I don't understand how to work with it. I tried the following: EDLIN edlin 2.8 ... *a : Hello, this is the first file I write with edlin. : (just pressed Enter at the second : prompt) String position error ABNORMAL TERMINATION C:\ So, I'm not sure if it works ok. Joris. What happened was that you found a bug in edlin. I reproduced it, and patched the bug. It will be fixed in the next release. -- Gregory Pietsch - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] 8086/XT compatibility issues for FreeDOS 1.0
Joris van Rantwijk wrote: Aitor Santamaría wrote: What about the rest? Do we assume they work? By popular (ahem) request, a list of things that work correctly on my XT. This list is not exhaustive. My testing was not thorough; I only tested very basic functionality of each program. 8086/XT compatible components in FreeDOS 1.0: kernel.sys (version 2036, 8086, FAT-32) assign.com append.exe (but does not affect fc.exe, find.com) attrib.com choice.exe comp.com chkdsk.com diskcomp.com diskcopy.exe debug.com deltree.com edit.exe (but extremely slow) fc.exe format.exe find.com keyb.exe label.exe mem.exe more.exe move.exe print.com/printq.exe (seem to do something but I don't have a printer) replace.exe sort.com sys.com tree.com xcopy.exe pg.exe ctmouse.exe I used command.com 0.82pl3, which is not included in FreeDOS 1.0. Hmmm... for some reason, edlin was not included in either list. So, does it work or not? Gregory Pietsch I compiled KEYB with 8088 specific instructions, and it installs own handlers so that it works in XT, so I'm curious if it does work well. KEYB.EXE seems to work. That is: if I type KEYB NL, all the punctuation keys get messed up and the rest of the system continues to work. My XT keyboard has an enhanced 101-key layout (I think that's unusual) and even that is handled ok. For a PC/XT you'll probably have a CGA, for which DISPLAY provides GRAFTABL emulation, did it work for you too? Yes, it has CGA. I think I know what GRAFTABL is meant to do, but I never managed to understand the EGA.SYS, DISPLAY.EXE, MODE.COM circus. I can try something if you explain me the commands I should type. Joris. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] c99 preprocessor
I have a C99 preprocessor about half-done, the right way. If someone wants to help me with this as I plan to release it under the GPL and my brain is fried right now with everything I've been doing, please e-mail me off-list. -- Gregory Pietsch - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Compiler group?
Arkady V.Belousov wrote: Hi! 13-Сен-2006 18:53 [EMAIL PROTECTED] (Gregory Pietsch) wrote to freedos-devel@lists.sourceforge.net: GP I was wondering if anyone wanted to form a compiler-writing group with GP the purpose of coming up with a C99 compiler that runs under FreeDOS. I What about OpenWatcom? Do you sure, that your experience and patience is enough to develop and maintain new compiler, which will not worser, than tons of existing ones? OpenWatcom is huge. You'd need a committee to maintain that. And how do you know that a new compiler will be worse than the existing ones? After much looking around, I've seen two types of open-source C compilers. The first type are monstrosities such as OpenWatcom and gcc. The second type are old compilers such as PCC and DeSmet and toy compilers that do not support C89, much less C99. And I don't think I've ever seen a preprocessor written using lexyacc/flexbison, which I thought was the right way to do it. GP There are free preprocessors, assemblers, and linkers available, but it GP would be neat if we could write them from scratch. What neat in this? After all, biggest advantage of open sources is possibility to reuse existing code. I know there's a possibility of reusing existing code; I just thought it would be neat! If we can rig the code to something like NASM, FASM, Arrow ASM, or something like that, then we can just include that assembler project. The problem here is not technical but getting permissions. ACK has a table-driven assembler; I thought that was an interesting way to do it. Gregory Pietsch - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Translation status for FreeDOS components
Aitor Santamaría wrote: Hi all, I have slightly modified the Translation status page as follows: http://wiki.fdos.org/Main/Translations Now you have for each tool wether it is translatable, and the different translation status (latest version translated) for each language. May I ask: DEVELOPERS: Please have a look at your tools, to see if the versions are OK, and you really have the translated files listed there. TRANSLATORS: Could you please check if there's work pending? That happens whenever the version listed in the Last version (EN) column and your language column differ. You may also want to add a new column if your language is not in the list. BLAIR: As a matter of reference, could you help me (either fill in yourself or pass the information to me) with the versions that are going inside the last CD-ROM? Of course, the information has been taken from the old page mainly, and I could have made mistakes. I'd be grateful for any inaccuracy correction. Thanks! Aitor I don't have translations for Esparanto, Lojban, or Klingon yet. I also don't have any for Swahili, Hungarian, Russian, Latvian, or !Xhosa (that strange African language with the clicking sound). If anyone contributes anything to Edlin, just give me a buzz! Gregory Pietsch - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS 1.0 relase, was MS-DOS image
Alain M. wrote: Michael Devore escreveu: Personally? I want another week to clear my schedule of incoming (and hope there isn't a lot more) plus monitoring, and another week after that for follow-up. Currently I feel like I should get a release out the door today, and frankly I'd like more time than that. Then, maybe a couple weeks of full FreeDOS 1.0 test? May I offer a suggestion: we can have FreeDOS 1.0 alfa FreeDOS 1.0 beta 1 FreeDOS 1.0 beta 2 That would keep the schedule *and* allow time to test... Alain Boy, it seems like 1.0 is a perfection that no one can achieve around here. We have 1.0pre-1, 1.0pre-2, etc. It seems like it's more like 0.9, 0.99, 0.999, 0., etc., getting closer to 1 without actually achieving it. Gregory - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeBack - backup tool
Johan Fjeltvedt wrote: Hi I want to join the programming FreeDOS programming team, if I can help with something... I am currently working on a backup program for MS-DOS compatible systems, in QBasic (yes, I know it's bad, but I hate to learn new languages, such as C). So, I wondered if you would have any use for that in FreeDOS? Of course, if there are nobody working on it now. If I am going to write it for FreeDOS - are there anything I should look out for - something that don't work in FreeDOS as in MS-DOS, etc.)? (sorry for my bad english - I'm norwegian ...) Johan There's always things to do around here. Even if you have no desire to learn C, you can translate many programs' messages into Norwegian or fix existing broken translations (FreeDOS Edlin has a broken Norwegian translation, which was generated mechanically via computer. The files are msgs-no.h and kitten/edlin.no. Read them, laugh at the quite possibly horrendous Norwegian, and please send me a fixed translation.). Don't worry about your English. We can tolerate bad English from non-native speakers around here, as long as they get their points across. As far as a backup program is concerned, I think somebody's working on one, I just don't know who. Gregory Pietsch --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Official KITTEN
Blair Campbell wrote: I didn't know about that version. Can someone (Eric? Blair?) email me a zip file of this new improved Kitten, so I can post it on ibiblio update the web site? I'll send it to you, but it is good to keep the other version because this version does not accept characters like \245 but rather the characters must be directly inserted into the text. Also, this version uses more memory than the other version, though resulting in a smaller binary, afaik. I also wrote a version of catgets for Edlin, and put it in there with the kitten code for a bit of variety. -- Gregory Pietsch --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628alloc_id=16845op=click ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] New FreeDos Developer
K. Alekhine wrote: Hi all, I am an experienced (+10 years) software developer who would like to aid to the FreeDos community in some way. My background is C/C++, Java/J2EE, Microsoft/Unix environments, Oracle db and also a little Assembler. Some years ago I worked on my sparetime with some MSDOS-programming. Except for installing and getting familiar with FreeDos, can you give me any hints for how to get started, which books/tutorials to read and such things ?. Which development environment/language do you recommend ? /Christer The first hint is to download the source code for the kernel and the apps and utilities and marvel at the code. Most of it was written either in straight ANSI/ISO C89 or 80X86 Assembler, as those are the two languages we use around here. If you want to develop an app that replaces an MS-DOS app, don't refer to Microsoft's code (if you have it) or any other proprietary programs while developing it. If you have a vague recollection of the internals of a MS-utility, that doesn't mean that you can't write an imitation of it, but try to write the imitation internally along different lines. For example, some programs were written to optimize memory use; if you go for speed or simplicity or generality instead, the code will be very different. I found code for MS Edlin floating around the Web, but it was in 80X86 Assembler. I read the specs and notices that it had a limit of 253 characters/line, which suggested static strings to me. I never referred to the Assembler code when I wrote FreeDOS Edlin. Also, it's in straight C and uses a dynamically-allocated array of dynamically-allocated strings as its main data structure. Believe it or not, I use Cygwin and MS Visual C++ version 6 as my two development environments, with OpenWatcom as a third to make sure that the code is portable. Gregory Pietsch --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] [Fwd: freedos]
I got this today and decided to forward it -- Gregory Pietsch ---BeginMessage--- i have a few questions. i asume that freedos runs ms-dos programs, is that correct? I have fdbootcd.iso, if a burn a cd and want to install it on the pc it won't boot, can you help me (or somebody else), i use nero for bruning. is it possible to use a 8 gb hd with freedos (no other system on the pc) maarten ---End Message---
[Freedos-devel] [Fwd: freedos and networking]
I got this from Pierre-Richard Potgeiter. -- Gregory Pietsch ---BeginMessage--- Hi How are you? I have hit a brick wall with trying to get Lantastic to work on Freedos, We run a Point of sale on dos and now we have to switch to freedos, It's a very nice system, We use lantastic to communicate between the POS's, I can get the POS to run hundred percent on freedos but when i try to load lantastic it loads aslong as you have the correct drivers but when it reboots it complains about not loading in High Mem, we managed to work around that but now it just refuses to work, Do you know if lantastic will work on Freedos or is there another networking protocol that we can use to communicate to windows from a FREEDOS machine. Thanx very much I really appreciate your help Pierre Pierre-Richard PotgieterSoftware SupportHRK AFRICA (PTY) LTDTel: 31 2668861/2Fax : 31-2660102[EMAIL PROTECTED] or [EMAIL PROTECTED] Glacier Bkgrd.jpg---End Message---
Re: [Freedos-devel] Re: best free C++ compiler
Alain wrote: Arkady V.Belousov escreveu: A BTW: do you have information about memcpy() problems in BC 3.1 ? Last My BC bugs list contains: - Result of intrinsic-version of memcmp function undefined when third argument is zero. FIX: check size of compared memory blocks before memcmp. Probably, memcpy() contains same bug. Which one you mean? I mean mamcpy(), but I will check it it could possibly have the 3rd argument =0. thanks. Alain Wouldn't that be a library and not a compiler problem? ;-) Here's my free implementation of all the mem* functions. You can use it for comparison: /* bcmp, bcopy, bzero, memccpy, memchr, memcmp, memcpy, memmove, memset -- memory-manipulation functions AUTHOR: Gregory Pietsch NAME bcmp - memory operations (LEGACY) bcopy - memory operations (LEGACY) bzero - memory operations (LEGACY) memccpy - copy bytes in memory memchr - find byte in memory memcmp - compare bytes in memory memcpy - copy bytes in memory memmove - copy bytes in memory with overlapping areas memset - set bytes in memory SYNOPSIS #include strings.h int bcmp(const void *s1, const void *s2, size_t n); void bcopy(const void *s2, void *s1, size_t n); void bzero(void *s, size_t n); #include string.h void *memccpy(void *restrict s1, const void *restrict s2, int c, size_t n); void *memchr(const void *s, int c, size_t n); int memcmp(const void *s1, const void *s2, size_t n); void *memcpy(void * restrict s1, const void * restrict s2, size_t n); void *memmove(void *s1, const void *s2, size_t n); void *memset(void *s, int c, size_t n); DESCRIPTION The functionality described on this reference page is aligned with the ISO C standard. Any conflict between the requirements described here and the ISO C standard is unintentional. This volume of IEEE Std 1003.1-2001 defers to the ISO C standard. The bcmp() function shall compare the first n bytes of the area pointed to by s1 with the area pointed to by s2. The bcopy() function shall copy n bytes from the area pointed to by s1 to the area pointed to by s2. The bytes are copied correctly even if the area pointed to by s1 overlaps the area pointed to by s2. The bzero() function shall place n zero-valued bytes in the area pointed to by s. The memccpy() function shall copy bytes from memory area s2 into s1, stopping after the first occurrence of byte c (converted to an unsigned char) is copied, or after n bytes are copied, whichever comes first. If copying takes place between objects that overlap, the behavior is undefined. The memchr() function shall locate the first occurrence of c (converted to an unsigned char) in the initial n bytes (each interpreted as unsigned char) of the object pointed to by s. The memcmp() function shall compare the first n bytes (each interpreted as unsigned char) of the object pointed to by s1 to the first n bytes of the object pointed to by s2. The sign of a non-zero return value shall be determined by the sign of the difference between the values of the first pair of bytes (both interpreted as type unsigned char) that differ in the objects being compared. The memcpy() function shall copy n bytes from the object pointed to by s2 into the object pointed to by s1. If copying takes place between objects that overlap, the behavior is undefined. The memmove() function shall copy n bytes from the object pointed to by s2 into the object pointed to by s1. Copying takes place as if the n bytes from the object pointed to by s2 are first copied into a temporary array of n bytes that does not overlap the objects pointed to by s1 and s2, and then the n bytes from the temporary array are copied into the object pointed to by s1. The memset() function shall copy c (converted to an unsigned char) into each of the first n bytes of the object pointed to by s. RETURN VALUE The bcmp() function shall return 0 if s1 and s2 are identical; otherwise, it shall return non-zero. Both areas are assumed to be n bytes long. If the value of n is 0, bcmp() shall return 0. The bcopy() and bzero() functions shall not return a value. The memccpy() function shall return a pointer to the byte after the copy of c in s1, or a null pointer if c was not found in the first n bytes of s2. The memchr() function shall return a pointer to the located byte, or a null pointer if the byte does not occur in the object. The memcmp() function shall return an integer greater than, equal to, or less than 0, if the object pointed to by s1 is greater than, equal to, or less than the object pointed to by s2, respectively. The memcpy() function shall return s1; no return value is reserved to indicate an error. The memmove() function shall return s1; no return value is reserved to indicate an error. The memset() function shall return s
Re: [Freedos-devel] Re: best free C++ compiler
Alain wrote: Only TC 2.01 and TC++ 1.02 are free. And OpenWatcom! Quite big but seems to be quite powerful as well. ... And note: TC/TC++ are free as in beer (zero cost.) But they are not free as in speech - source code is not available. IMHO it is not free. it says only for Personal Use. This makes devellopment even of FreeDOS utilities theoreticaly forbidden ... Alain PS: FWIU the later Borland museum compiler is BC1 that was released _after_ TC2, but for mistirious reasons I posted this many-many times and I fell into a some void. Well, now we know for sure that information is not lost in black holes (see Stephen Hawkings :) Why would development of FreeDOS utilities be forbidden? Nobody is requiring that anyone actually use TC 2.01 or TC++ 1.02. As long as the written code is portable, it should work with any compiler. ;-) Gregory Pietsch --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] best free C++ compiler
Koder wrote: Hi, After a few years of being idle in the DOS-scene, I am looking to writing some new apps. I am using Borland's TC 2.01 because that has been released for free. Here are some questions for you dev's: 1) If I were to write a FreeDOS-targetted application on FreeDOS, which C++ compiler would be the most interesting? I have a copy of TC++ 3.0 lying around somewhere. Is that one freely available yet? I typically use djgpp or Cygwin/gcc and M$ Visual C++ in console app mode. I then try OpenWatcom and see if I can get everything working on all three with a minimum of fuss. Throw in an autoconf/automake-generated configure script, et voila! 2) Is anyone using lex/yacc in any project? Did you use it for the processing of .bat files? If not, then why not? Will lex/yacc work with TC 2.01? GNU flex/bison and Berkeley yacc (or byacc) are Free versions of lex/yacc. The code produced with them should be portable enough that you can use it. I know I could just look all of this up, but I guess you guys already know the answers... Thanks in advance! Gregory Pietsch --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] GRC and FreeDOS
I got this in an e-mail that was also sent to Steffen Kaiser. I haven't included Roland's e-mail address per the note -- Gregory: Hello, do you know that Steve Gibson(www.grc.com) is Considering spending $20,000 for DR DOS? There is a thread about this in news.grc.com/grc.spinrite.dev. He is still using FreeDos, and maybe he would be willing to invest some money into FreeDos if you would fix the problems he is is currently having with it. If you are interested go to the newsgroup and participate in the conversation. Also forward this email to other freedos developers if it's useful, but please remove my email address if you are going to post it in the mailing list, I don't want more spam. Roland -- Sie haben neue Mails! - Die GMX Toolbar informiert Sie beim Surfen! Jetzt aktivieren unter http://www.gmx.net/info --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: FreeDOS distro delayed
Bernd Blaauw wrote: What compiler and what language for the edlin-2.2 binary? OpenWatcom, I suppose, otherwise it won't work on 8086 (MS EDLIN is older than MS EDIT). I'll search for some clear instructions in your source package. Otherwise, please instruct me, i'm pretty new to compiling stuff and only a thing like the kernel is very automated. The only real source files that would need to be modified are msgs.h (obviously, for the languages) and config.h, which gets overwritten by the ./configure script. BTW, my reference compiler is gcc/cygwin, but I also use MS Visual C/C++ and OpenWatcom. OpenWatcom and gcc/cygwin are free, and the traditional ./configure;make;make install works nicely with gcc/cygwin. ;-) gcc/cygwin is the same as MSYS / MINGW ? confusing, all those compilers, linkers, languages and platforms. Bernd They're similar (both ports of gcc). I don't know if the ./configure script can detect mingw, but it should be able to. Cygwin is a port of the gcc/bash environment that runs under Windows using a DLL emulator. It's useful for porting Unix/Linux programs to Windows. Anyway, under cygwin, what the ./configure script does is produce a config.h file with various #defines #defined and a Makefile from Makefile.in. The make program compiles and builds everything and then make install puts the executable into /usr/local/bin. The Makefile has a few other neat targets in it such as distdir (makes a distribution directory), dist (makes a distribution tarball edlin-2.2.tar.gz), and others. I use make dist to throw a distro together. Isn't automation fun? BTW, I left in the .tgt files for OpenWatcom, so compiling with that shouldn't be hard. Gregory Pietsch --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] [Fwd: FreeDOS]
---BeginMessage--- Title: Message Hello. My companyprocesses (removes microsoft information)and resells 1,000 - 1,500 major-label PCs a month.The OEMwould like us to add FreeDOS licenses to these PCs. The requirement is that weput some sort of documentation into each box - either a FreeDOS license ora document that points the end-user to FreeDOS. What do you recommend. Regards, Grant * Grant Guilbeault CEO FastAsset, Inc. 170 West Road Portsmouth, NH 03801 603-559-9900 800-794-6065 603-559-9901 fax [EMAIL PROTECTED] ---End Message---
[Freedos-devel] [Fwd: On Deadline Today: Fact Check for PC World [08fpcmyths FreeDOS]]
---BeginMessage--- Hello All, Could one of you please verify these facts below ASAP? Deadline is today. Thanks! :) Kristina Please verify the following for publication in PC World, August issue. The text is a paraphrase of that which will be printed. Please make any changes in ALL CAPS (not in color or bold) within the body of the fact check. IMPORTANT: Please only notify us of changes that are strictly necessary for the factual accuracy, spelling or punctuation of the material. Please do not add text, only verify what is there. Thank you for your time, Kristina Saar Senior Research Editor, PC World phone: 415.974.7375 [EMAIL PROTECTED] Product Information and/or excerpts from article or list text: -- DOS most frequent use these days is in embedded applications where the computer does just one thing. -- Microsoft doesnt sell DOS at retail. The closest equivalent is to download the MS-DOS compatible FreeDOS at find.pcworld.com/42850. END ---End Message---
[Freedos-devel] [Fwd: your O/S]
I don't know all the answers to his questions, so I'll post it here. -- Gregory ---BeginMessage--- Hello,I was reading your site!! (FreeDos) Man it looks great. I'm not a coder, so I really don't know what it can do. Can it run on the internet? Is it fast? Will it find my hardware? I was reading about a different O/S written in assembler also, and small, will fit on floppy. it has a site too. I thnk it's called menuet.com. Is this based from your code? I have a extra hard drive, I was thinking about putting your O/S on it. Is it secure?I hate to be a Dum Dum but I just have to ask.thanksMarshall ---End Message---
Re: [Freedos-devel] FreeDOS 1.0 TODO list ready (but not yet posted)
Aitor Santamaría Merino wrote: Hi, Gregory Pietsch escribió: I don't see anything about edlin or code in there, so I guess they are okay, or am I just not getting any feedback? Oops, sorry! When the list was first posted, EDLIN didn't exist, so I'll add it (to MISC utilities, ok?). Could you report on the commands already implemented? Is there any MS-EDLIN command still to be implemented? Here are the differences between FreeDOS edlin and MS edlin, AFAIK: # (edit a single line) - implemented. Does not work the same as MS's because I wanted the implementation to be easy. The only difference is that the user has to type in the entire line instead of just using the - key. a (append) - MS edlin used this for a paged file where part of the file is in memory and part hadn't been read in. My implementation can handle larger files (making the paged file thing obsolete), so I changed this to append to the end of the buffer, which seems more natural. c (copy range of lines) - implemented. d (delete a block of lines) - implemented. e (save and quit) - implemented. i (insert mode) - implemented. I made the get-out-of-insert-mode character a period on an otherwise blank line instead of control-Z because the one thing I hated about MS edlin was the use of control characters in the syntax. (The period can be escaped if you really wanted just a period on a line.) l (list lines) - implemented. m (move block) - implemented. p (page) - implemented. q (quit) - implemented. r (replace) - implemented. I added to the string syntax. s (search and replace) - implemented. MS edlin had a control-Z between the two strings; I have a comma, which results in a cleaner syntax, IMNSHO. t (transfer file) - implemented. It slurps in a whole file instead of going the paging route. w (write file) - implemented. I added the optional filename because the one thing that isn't there that MS edlin has is automatic file backups. Having the filename there makes it easy to backup the file manually. I believe that's all of them. It will be a bit harder for me to recover one of those old MS-DOS versions to compare... Aside from the control-characters-on-the-command-line issue (which I got around by improving the syntax), the only thing I can see that MS edlin does that mine doesn't is make automatic backups of the file you're editing. I got around it by adding the optional filename to the w command, so that the user can make a backup if he/she/it wants.) I don't know much about CODE, but doesn't sound as one of the core MS-DOS utilities, and hence does not go into this list, sorry... Aitor --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeDOS people list
Johnson Lam wrote: On Sun, 29 Feb 2004 11:20:16 -0600, you wrote: Hi Jim, About a month or so ago, there was a discussion thread about creating a list of FreeDOS users, so people could get together and create FreeDOS User Groups in their areas. Did anyone assemble such a list? I think it would be good to add a link to that from the http://www.freedos.org/freedos/contact/ page. I've been working on a contributor's list (wow ... hard to do since some people have too little information, maybe they want to keep low-profile). Please take a look and comment, try my best to improve. http://johnson.tmfc.net/freedos P.S. The most headache is the geographic location. Rgds, Johnson. Gregory Pietsch (edlin, code) - USA/New Jersey. --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Microsoft source code
This is in regard to referring to leaked M$-DOS v6 source code. Richard Stallman wrote in the GNU Coding Standards: begin quote Don't in any circumstances refer to Unix source code for or during your work on GNU! (Or to any other proprietary programs.) If you have a vague recollection of the internals of a Unix program, this does not absolutely mean you can't write an imitation of it, but do try to organize the imitation internally along different lines, because this is likely to make the details of the Unix version irrelevant and dissimilar to your results. For example, Unix utilities were generally optimized to minimize memory use; if you go for speed instead, your program will be very different. You could keep the entire input file in core and scan it there instead of using stdio. Use a smarter algorithm discovered more recently than the Unix program. Eliminate use of temporary files. Do it in one pass instead of two (we did this in the assembler). Or, on the contrary, emphasize simplicity instead of speed. For some applications, the speed of today's computers makes simpler algorithms adequate. Or go for generality. For example, Unix programs often have static tables or fixed-size strings, which make for arbitrary limits; use dynamic allocation instead. Make sure your program handles NULs and other funny characters in the input files. Add a programming language for extensibility and write part of the program in that language. Or turn some parts of the program into independently usable libraries. Or use a simple garbage collector instead of tracking precisely when to free memory, or use a new GNU facility such as obstacks. end quote Much of this can be used with regard to the M$-DOS programs we seek to imitate. For example, MS edlin had a limit of 253 characters on a line; FreeDOS edlin uses dynamically allocated strings, which smashes that arbitrary barrier. I only referred to the documentation for MS edlin when I wrote FreeDOS edlin and not its source code, however it was leaked, and it was probably in 8086 Assembler anyway. The only thing I didn't try replicating were the automatic backup files, but I added an option to specify the filename on write so that it is easy to write the filename to a different file if you really wanted to. I thought that this ability was a Good Thing, so I added it. Gregory Pietsch --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
