Re: [Freedos-devel] FreeDOS floppy edition boot disk lacks an editor?

which would give you basic full screen editing if you wanted to copy one on > the disk yourself (and if there is space enough on it)... > > Ralf > > > > > _______ > Freedos-devel mailing list > Freedos-devel@lists.source

Re: [Freedos-devel] FreeDOS floppy edition boot disk lacks an editor?

On 12/2/2022 1:38 PM, Bernd Boeckmann via Freedos-devel wrote: Hi all, last time I installed FreeDOS from floppy disk set I was in need for an editor to edit some system filed but did not find one on the boot disk. Is that an oversight of mine or is this by intention? I found that very inconve

[Freedos-devel] FreeDOS floppy edition boot disk lacks an editor?

Hi all, last time I installed FreeDOS from floppy disk set I was in need for an editor to edit some system filed but did not find one on the boot disk. Is that an oversight of mine or is this by intention? I found that very inconvenient. Perhaps there is a way to include at least minimal editin

[Freedos-devel] FreeDOS Interim Build T2212

Hi all, FreeDOS Interim Build T2212 is now available at https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Mostly, this update consists of improvements to KEYB and 5 other package updates

[Freedos-devel] FreeDOS Archive CI/CD

Hi All, First, I want to apologize to everyone using the FreeDOS Archive on GitLab ( https://gitlab.com/FreeDOS ) that may have received a bunch of messages regarding failed and successful CI/CD pipelines over the last few days. This was the result of some work I wa

Re: [Freedos-devel] FreeDOS Interim Build T2210

Hi, On Mon, Oct 17, 2022 at 11:04 AM Jerome Shidel wrote: > > > On Oct 2, 2022, at 5:08 AM, tom ehlert wrote: > > [..] > > btw dowloading 900 MB .zip over a 4MB/s download link is a PITA; this > > alone should recommend a split. (Sorry, I'm horrible at trying to calculate such things, but I tr

Re: [Freedos-devel] FreeDOS Interim Build T2210

I started with a 1200 BAUD modem back in the early 90's. Even downloading a copy of DOS back then would have taken a real long time. Remember this commercial? https://www.youtube.com/watch?v=mbUbRHRuyfs ___ Freedos-devel mailing list Freedos-deve

Re: [Freedos-devel] FreeDOS Interim Build T2210

Hi, > On Oct 2, 2022, at 5:08 AM, tom ehlert wrote: > [..] > btw dowloading 900 MB .zip over a 4MB/s download link is a PITA; this > alone should recommend a split. > > Tom Imagine downloading it back when DOS was the main home user OS — over a fast 56k modem. If you somehow managed to downl

Re: [Freedos-devel] FreeDOS Interim Build T2210

-devel@lists.sourceforge.net <freedos-devel@lists.sourceforge.net> Fecha:        domingo, 16 de octubre de 2022, 20:45:02 Asunto:       [Freedos-devel] FreeDOS Interim Build T2210 Archivos:     --===-- Hi Joseph, On another

Re: [Freedos-devel] FreeDOS Interim Build T2210

Hi Joseph, > On another note, I just corresponded with Sammy Mitchell of Semware. > The Semware Editor (TSE) has gone into Freeware, and, he tells me that > the DOS version will also eventually be freeware and open-source. Oh, that would be cool. > Whether the license is compatible remains to

Re: [Freedos-devel] FreeDOS Interim Build T2210

remains to be seen, but, he’s going into a community-supported model. It’s great to see folks wanting to preserve this software, and, use it too. Cheers! Sent from Mail for Windows From: Jerome ShidelSent: Saturday, October 1, 2022 10:49 AMTo: developers FreeDOSSubject: [Freedos-devel] FreeDOS Interim

Re: [Freedos-devel] FreeDOS Interim Build T2210

formation see: https://sites.google.com/site/blairdude/fdav   Willi             Sent: Sunday, October 02, 2022 at 4:59 PM From: "Wilhelm Spiegl" To: freedos-devel@lists.sourceforge.net Subject: Re: [Freedos-devel] FreeDOS Interim Build T2210 Hi, a simple idea how to save 27 MB of

Re: [Freedos-devel] FreeDOS Interim Build T2210

" To: "Technical discussion and questions for FreeDOS developers." Subject: Re: [Freedos-devel] FreeDOS Interim Build T2210 > I’ve just uploaded this months Interim Build to ibiblio. To test > T2210, you can fetch it from > http://www.ibiblio.org/pub/micro/pc-stuff/freedo

Re: [Freedos-devel] FreeDOS Interim Build T2210

> I’ve just uploaded this months Interim Build to ibiblio. To test > T2210, you can fetch it from > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ > I’ve warned about this several times. But with the recent updates > and few additions to the DJGPP packages, the Bonus

Re: [Freedos-devel] FreeDOS Interim Build T2210

On Sat, 1 Oct 2022, 16:49 Jerome Shidel, wrote: > > As I see it, this leaves us with 3 choices: > > 1) Drop nearly 300mb of packages from the CD. > 2) Do nothing and call it a DVD > 3) Move all development related packages onto their own disc. Have DevelCD > and seperate BonusCD. > In my view, a

Re: [Freedos-devel] FreeDOS Interim Build T2210

Hello, On Sat, 1 Oct 2022 at 16:49, Jerome Shidel wrote: > As I see it, this leaves us with 3 choices: > > 1) Drop nearly 300mb of packages from the CD. > 2) Do nothing and call it a DVD > 3) Move all development related packages onto their own disc. Have DevelCD > and seperate BonusCD. > >From

[Freedos-devel] FreeDOS Interim Build T2210

Hello All, I’ve just uploaded this months Interim Build to ibiblio. To test T2210, you can fetch it from http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ I’ve warned about this several time

[Freedos-devel] Freedos is a great OS，I am a programmer，I love it！

从 Windows 版邮件发送 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FreeDOS get-together coming up on Sunday

Hi again! The get-together starts in a few minutes. Here's the URL: https://bluejeans.com/354199206/8001 I need to keep today's call to an hour, so we'll go until noon US/Central. On Tue, Sep 13, 2022 at 11:01 PM Jim Hall wrote: > > Hi everyone! > > Just sending a quick reminder of the get-

[Freedos-devel] FreeDOS get-together coming up on Sunday

Hi everyone! Just sending a quick reminder of the get-together happening on Sunday. Same as always, 11am US Central Time. I'll share the link here and on the website shortly before the meeting. This month's topic is social time. Join us and get to know everyone a bit better. __

Re: [Freedos-devel] FreeDOS T2209

Hi, > On Sep 1, 2022, at 11:08 PM, Jim Hall wrote: > >  > > >> On Thu, Sep 1, 2022, 6:59 AM Jerome Shidel wrote: >> (...) >> Since we have not made a final decision on how many or where to keep >> previous test builds, I simply placed the old T2208 under >> >> https://www.ibiblio.org/pub/

Re: [Freedos-devel] FreeDOS T2209

On Thu, Sep 1, 2022, 6:59 AM Jerome Shidel wrote: > (...) > Since we have not made a final decision on *how many *or *where to keep* > previous test builds, I simply placed the old T2208 under > > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/previous/T2208/ > > (.

[Freedos-devel] FreeDOS T2209

Hello all, The FreeDOS interim test build T2209 is now available for download at https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Primary changes since T2208: 2022-08-21 15:03:44 curl (sh

Re: [Freedos-devel] FreeDOS Edlin 2.21

For anyone who wants to test the 32-bit version, note this uses dos4gw.exe so standard dos4gw assumptions apply. For example, if Edlin can't find \dos4gw.exe then try running Edlin from the command line via dos4gw.exe, such as this: >dos4gw edlin32.exe Or if you don't have dos4gw.exe in your path

Re: [Freedos-devel] FreeDOS Edlin 2.21

Oops, I realized that I didn't compile this version of Edlin 2.21 with catgets support, so I've recompiled it. There's an OW.BAT file in there, contributed by Rugxulo, so I used that to compile it. Updated zip is here: https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.21/ And insi

[Freedos-devel] FreeDOS Edlin 2.21

I realized that we didn't have an exe version of Edlin, so I compiled a 16-bit version using OpenWatcom, and put it on the FreeDOS Files Archive at Ibiblio: https://ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/edlin/2.21/ This was compiled with: > COPY CONFIG‐H.OW CONFIG.H > WCL ‐q ‐os ‐DHA

Re: [Freedos-devel] FreeDOS Unstable - interim development builds

s://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test.old/ > > <https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test.old/> If we used the test/2208/ method, we can store as many as needed. Another alternative is use test/, then retire previous on

Re: [Freedos-devel] FreeDOS Unstable - interim development builds

le, > > the report includes in document links to change summaries. > > > > Just let me know what we need to change. > > > Summary: > > 1. Can we use > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/devel/ > or > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ > ? > > 2. Can we keep "current plus 1 previous"? For example, > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/devel.old/ > or > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test.old/ > > > And not to lose the original point: I love that this becomes a way to > test current changes. And I love that this could help accelerate new > releases; we might say "this release is pretty solid, if no issues > found in [n] weeks, we'll make this the 'FreeDOS 1.4 RC1' distro." And > so on until FreeDOS 1.4 (or 2.0, whatever we call it). > > > 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] FreeDOS Unstable - interim development builds

>>On Jun 22, 2022, at 1:05 PM, Jim Hall wrote: >> >>I like the idea of the interim development builds. This should be a >>great way to test new changes that everyone can experiment with! >>Thanks for doing this. >> >>I'm thinking about how people will (mis)interpret the "FreeDOS >>Unstable" name.

Re: [Freedos-devel] FreeDOS Edlin 2.21 is here!

Hi Gregory, > On Jun 26, 2022, at 9:22 PM, Gregory Pietsch wrote: > > 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

Re: [Freedos-devel] FreeDOS Edlin 2.21 is here!

On Sun, Jun 26, 2022 at 8:22 PM Gregory Pietsch wrote: > > 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 Free

[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_

Re: [Freedos-devel] FreeDOS interim development build

Hi, > On Jun 25, 2022, at 4:41 PM, Aitor Santamaría wrote: > > Hello, > > Thanks for the answers! Your Welcome. > On Sat, 25 Jun 2022 at 22:32, Jerome Shidel > wrote: > For example, if KEYB on the GitLab archive has a commit pushed with the > comment “Fixed double

Re: [Freedos-devel] FreeDOS interim development build

Hello, Thanks for the answers! On Sat, 25 Jun 2022 at 22:32, Jerome Shidel wrote: > For example, if KEYB on the GitLab archive has a commit pushed with the > comment “Fixed double keypress bug”. That comment would appear in the > CHANGES.LOG as something like “2022-06-29 04:52:11 keyb (Aitor S

Re: [Freedos-devel] FreeDOS interim development build

Hi Aitor, > On Jun 25, 2022, at 3:22 PM, Aitor Santamaría wrote: > [...] > How do these logs build up? (I am assuming logs in an user-readable format). > Every time someone updates a tool, do we need to fill in somewhere? > Ideally, the implemented bugs and enhancements from GitLab would go to t

Re: [Freedos-devel] FreeDOS interim development build

Hello Jerome, I'll give you my opinion on some of these. On Sat, 25 Jun 2022 at 15:02, Jerome Shidel wrote: > First, how will we Label and refer to these builds? I went with “Unstable” > with the short name would be “FreeDOS U2207” and long name as “FreeDOS > 2206-Unstable”. To me, it is a well

[Freedos-devel] FreeDOS interim development build

Hi Jim and all, Well, the work I wanted to do to the RBE and release media is finished. I’ve replaced the downloads on my server with the new versions. You can fetch them, or view the report information at https://fd.lod.bz/releases/unstable/ Mostly, the

[Freedos-devel] FreeDOS Unstable - CHANGES.LOG

Hi, > On Jun 22, 2022, at 6:26 PM, Eric Auer wrote: > > > Hi! > >> Changes since FreeDOS 1.3 release >> 2022-06-22 10:02:08 project_RBE (shidel): Adjust interim build file names >> 2022-06-22 09:13:23 project_RBE (shidel): Automatic Unstable Build Versioning >> 2022-06-21 09:21:37 project_FD-N

Re: [Freedos-devel] FreeDOS Unstable - interim development builds

black background to differentiate it a normal release (blue >> background). >> >> * Maybe… Add boot message noting/warning that it is not a release >> build. Maybe… >> >> “Warning: This is a FreeDOS development build and is for testing >> purposes. It may exhibit behavior vary

Re: [Freedos-devel] FreeDOS Unstable - interim development builds

I like the idea of the interim development builds. This should be a great way to test new changes that everyone can experiment with! Thanks for doing this. I'm thinking about how people will (mis)interpret the "FreeDOS Unstable" name. I wonder if "FreeDOS Test" might be a better name for this. The

[Freedos-devel] FreeDOS Unstable - interim development builds

Hi Jim and the Dev group, I’m in the process of wrapping up some minor improvements to the RBE (Release Build Environment) that I wanted to make for creating the interim development builds of FreeDOS. For example: * Automatic interim build versioning. That way we can easily verify th

Re: [Freedos-devel] Freedos EDIT

Hello, On Fri, 22 Apr 2022 at 22:28, Eric Auer wrote: > > Hi Tom, > > > I just noticed that the source to FreeDOS EDIT > > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/edit.zip > > is incomplete as it assumes an existing DFLAT library which is not > > i

Re: [Freedos-devel] Freedos EDIT

tom ehlert [22/04/2022 14.31]: Can you complete the build with this? https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/dflat/ no. this is linux stuff with unknown conversion status. won't touch. How is this Linux stuff? This is the _readme.txt_ file from that directory: ===

Re: [Freedos-devel] Freedos EDIT

Hi Tom, I just noticed that the source to FreeDOS EDIT https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/edit.zip is incomplete as it assumes an existing DFLAT library which is not included, and at least non-trivil to locate on the internet. Looking at my

Re: [Freedos-devel] Freedos EDIT

On Fri, Apr 22, 2022, 7:34 AM tom ehlert wrote: > > I think in the FreeDOS "beta" days, the distributions included > > programming libraries too, basically a copy of the "libs" tree from > > Ibiblio. > what "libs" tree? > This link, one level up from the DFLAT link I shared in my other email: >

Re: [Freedos-devel] Freedos EDIT

Hallo Herr Jim Hall, am Freitag, 22. April 2022 um 11:57 schrieben Sie: > On Fri, Apr 22, 2022, 4:22 AM tom ehlert wrote: > I just noticed that the source to FreeDOS EDIT > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/edit.zip > is incomplete as it

Re: [Freedos-devel] Freedos EDIT

On Fri, Apr 22, 2022, 4:22 AM tom ehlert wrote: > > I just noticed that the source to FreeDOS EDIT > > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/edit.zip > is incomplete as it assumes an existing DFLAT library which is not > included, and at least non-t

Re: [Freedos-devel] Freedos EDIT

I just noticed that the source to FreeDOS EDIT https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/base/edit.zip is incomplete as it assumes an existing DFLAT library which is not included, and at least non-trivil to locate on the internet. Tom ___

Re: [Freedos-devel] "FreeDOS Next" packages

If you want my personal opinion, just distribute what more or less reproduces MS-DOS/PC DOS/DR DOS functionality as part of the release proper. -uso. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/li

Re: [Freedos-devel] "FreeDOS Next" help files

On Sat, Apr 2, 2022, 8:07 AM Wilhelm Spiegl wrote: > Hi everyone, > there is a corresponding question from me. I tried to reach Jim several > times, but till now I got no satisfying response, so I put the question > here: > > You emailed me? If you sent an off-list email in reply to a FreeDOS em

[Freedos-devel] "FreeDOS Next" help files

Hi everyone, there is a corresponding question from me. I tried to reach Jim several times, but till now I got no satisfying response, so I put the question here:   In FreeDOS help there are a lot of outdated commands. See: http://home.mnet-online.de/willybilly/fdhelp-109/en/index.htm (my websit

Re: [Freedos-devel] "FreeDOS Next" packages

+1 100% Sent with [ProtonMail](https://protonmail.com/) secure email. --- Original Message --- On Saturday, April 2nd, 2022 at 3:41 AM, Maarten Vermeulen wrote: > I never really say anything here, but I feel like I should here. > > I do agree with Mike here. When I install a DOS, I ju

Re: [Freedos-devel] "FreeDOS Next" packages

I never really say anything here, but I feel like I should here. I do agree with Mike here. When I install a DOS, I just want it to be DOS, so I always install just the base option with FreeDOS. Having less packages also means you have more control over the software and the project. Yes, you have

Re: [Freedos-devel] "FreeDOS Next" packages

How about something very radical - cutting FreeDOS back to the bare operating system, and just offering the other software as user-installed downloads as it was originally packaged? In ye olde days people purchased DOS, installed it, and then installed their own software using the original install

[Freedos-devel] "FreeDOS Next" packages - Utilities (util)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Utilities (util) packages we included in FreeDOS 1.3. This list is pulled from the fir

[Freedos-devel] "FreeDOS Next" packages - Unix Like Tools (unix)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Unix Like Tools (unix) packages we included in FreeDOS 1.3. This list is pulled from t

[Freedos-devel] "FreeDOS Next" packages - Sound Tools (sound)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Sound Tools (sound) packages we included in FreeDOS 1.3. This list is pulled from the

[Freedos-devel] "FreeDOS Next" packages - Networking (net)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Networking (net) packages we included in FreeDOS 1.3. This list is pulled from the fir

[Freedos-devel] "FreeDOS Next" packages - Graphical Desktops (gui)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Graphical Desktops (gui) packages we included in FreeDOS 1.3. This list is pulled from

[Freedos-devel] "FreeDOS Next" packages - Games (games)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Games (games) packages we included in FreeDOS 1.3. This list is pulled from the first

[Freedos-devel] "FreeDOS Next" packages - Editors (edit)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Editors (edit) packages we included in FreeDOS 1.3. This list is pulled from the first

[Freedos-devel] "FreeDOS Next" packages - Device Drivers (drivers)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Device Drivers (drivers) packages we included in FreeDOS 1.3. This list is pulled from

[Freedos-devel] "FreeDOS Next" packages - Development (devel)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Development (devel) packages we included in FreeDOS 1.3. This list is pulled from the

[Freedos-devel] "FreeDOS Next" packages - Boot Tools (boot)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Boot Tools (boot) packages we included in FreeDOS 1.3. This list is pulled from the fi

[Freedos-devel] "FreeDOS Next" packages - Archivers (archiver)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Archivers (archiver) packages we included in FreeDOS 1.3. This list is pulled from the

[Freedos-devel] "FreeDOS Next" packages - Applications (apps)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the Applications (apps) packages we included in FreeDOS 1.3. This list is pulled from the

[Freedos-devel] "FreeDOS Next" packages - FreeDOS Base (base)

This is the discussion thread for what packages we might drop in the next distribution of FreeDOS. See the other "parent" discussion thread and the "Thinking about FreeDOS 2.0" thread for context. These are the FreeDOS Base (base) packages we included in FreeDOS 1.3. This list is pulled from the

[Freedos-devel] "FreeDOS Next" packages

I wanted to start a thread to discuss packages in the *next* FreeDOS distribution. For now, I'll call this "FreeDOS Next" for lack of a better label. This could be "FreeDOS 1.4" or "FreeDOS 2.0" but we'll save the "label" discussion for another time. To frame the discussion, in the "Thinking about

Re: [Freedos-devel] FreeDOS wins award from SourceForge

a big achievement, as your project has qualified for these > > > > awards out of over 500,000 open source projects on > > > > SourceForge. SourceForge sees nearly 30 million users per month > > > > looking for, and developin

Re: [Freedos-devel] FreeDOS wins award from SourceForge

If you'd like to download one of the SourceForge badges to add to your own site, you can find them here: https://www.freedos.org/images/sfbadges/ (Use right-click and "Save As" to download the image. These are SVG files, so will scale nicely to smaller or larger sizes.) On Tue, Mar 1, 2022 at

[Freedos-devel] FreeDOS wins award from SourceForge

Hi everyone I received this email from SourceForge and wanted to share it. I'd guess this is partially to recognize the recent FreeDOS 1.3 release. Either way, this really belongs to the community here. Grab a copy of the badges from our SF project page and put them in your own website. I'm away

Re: [Freedos-devel] freedos 1.3 at german magazine heise

On 2/26/2022 12:31 AM, Jerome Shidel wrote: On Feb 25, 2022, at 8:00 PM, Ralf Quint wrote: On 2/25/2022 4:02 AM, Jim Hall wrote: https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html Just had a quick read over that one and noticed one s

Re: [Freedos-devel] freedos 1.3 at german magazine heise

Hi Eric, >>> https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html >>> >> >> Just had a quick read over that one and noticed one strange thing >> mentioned. Apparently the CPU detection in the installer would only >> recognize an 80186 ev

Re: [Freedos-devel] freedos 1.3 at german magazine heise

Hi Ralf, https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html Just had a quick read over that one and noticed one strange thing mentioned. Apparently the CPU detection in the installer would only recognize an 80186 even though appare

Re: [Freedos-devel] freedos 1.3 at german magazine heise

s been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > > ___ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-d

Re: [Freedos-devel] freedos 1.3 at german magazine heise

On 2/25/2022 4:02 AM, Jim Hall wrote: https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html Just had a quick read over that one and noticed one strange thing mentioned. Apparently the CPU detection in the installer would only recognize an

Re: [Freedos-devel] freedos 1.3 at german magazine heise

On Fri, Feb 25, 2022, 5:16 AM Wilhelm Spiegl wrote: > sorry, german text only > > > https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html > > Thanks! I had that one already: https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mi

[Freedos-devel] freedos 1.3 at german magazine heise

sorry, german text onlyhttps://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html--Diese Nachricht wurde von meinem Android Mobiltelefon mit mail.com Mail gesendet. ___ Freedos-devel mailing list Freedos-

Re: [Freedos-devel] FreeDOS on JavaScript

On Wed, Feb 23, 2022 at 5:58 PM Aitor Santamaría wrote: > > Hi, > > Remember that in the sunday meeting I mentioned there were out there JS > emulators running FreeDOS? > > I've found one in my bookmarks. Running FD 1.2, but still nice to link it to > the main FreeDOS page, so that people can ev

[Freedos-devel] FreeDOS on JavaScript

Hi, Remember that in the sunday meeting I mentioned there were out there JS emulators running FreeDOS? I've found one in my bookmarks. Running FD 1.2, but still nice to link it to the main FreeDOS page, so that people can even see the OS in action: JSLinux (bellard.org)

Re: [Freedos-devel] FreeDOS 1.3 is now available!

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.) Let's keep the focus on FreeDOS 1.3 in this thread. ___ Freedos-devel mailing list Freedos-devel@lists.sour

[Freedos-devel] FreeDOS 1.3 is now available!

The new FreeDOS 1.3 is now available for download! https://www.freedos.org/download/ Or more directly at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/official/ This contains a bunch of great new features and improvements since the 1.2 release, including: new FreeC

Re: [Freedos-devel] FreeDOS virtual get-togethers in 2022

On Fri, 11 Feb 2022, Jim Hall wrote: ** In January, we used Zoom as a test. For February, we're back to using BlueJeans (I use them for my training/consulting business). The BlueJeans support folks have given me a few pointers to improve performance, so I'm hoping this session will work better.

[Freedos-devel] FreeDOS virtual get-togethers in 2022

Hi everyone! I'm looking ahead at the calendar to plan the virtual get-togethers for the rest of this year. Here's what I'm thinking about: We have virtual get-togethers on the third Sunday of each month at 11am US/Central. This works well for most folks (I know the Earth is round, so it's night

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

Thanks to everyone for joining today's FreeDOS virtual get-together! I really appreciate getting to know everyone as more than just a name behind an email. Folks dropped in and out as they had time. I think we had a dozen folks during the get-together. We do these monthly, so if you weren't able

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

On Sun, Jan 16, 2022 at 10:46 AM Ralf Quint wrote: > On 1/12/2022 12:58 PM, Jim Hall wrote: > > I'll share the meeting info here in the hour leading up to the meeting. > > Did you oversleep? ;-) > > No, but I completely forgot to share the invite an hour before the meeting. :-) Here's the invi

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

On 1/12/2022 12:58 PM, Jim Hall wrote: I'll share the meeting info here in the hour leading up to the meeting. Did you oversleep? ;-) Ralf -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _

[Freedos-devel] FreeDOS virtual get-together on Sunday

Hi everyone! Every month, we have a virtual get-together on video chat. It's another way for us to stay connected - and helps us put a face to the name, so we aren't just someone on the other end of an email. The next virtual get-together is THIS SUNDAY, January 16 at 11am US/Central. We'll be li

Re: [Freedos-devel] FreeDOS 1.3-RC5 questions and bug-testing

EM "EGA" to "EGA18", figure out from CPIDOS list > SET CPXPACK=EGA10 > > LH DISPLAY CON=(EGA,,1) /C > MODE CON CP PREP=((%CODEPAGE%) %DOSDIR%\CPI\%CPXPACK%.CPX) > MODE CON CP SEL=%CODEPAGE% > KEYB %LANG%,%CODEPAGE%,%DOSDIR%\BIN\KEYBOARD.SYS > > REM These are no longer required while the system is running > SET CODEPA

Re: [Freedos-devel] FreeDOS 1.3-RC5 questions and bug-testing

On 12/19/2021 11:58 AM, Radek Krzyśków wrote: Hello! Here are a few questions and notes (testing new FreeDOS release on VirtualBox 6.1.30) 1) How to use `FDIMPLES` with Bonus CD? Running `FDIMPLES` with "FD13BNS.ISO" shows "Packa

[Freedos-devel] FreeDOS 1.3-RC5 questions and bug-testing

Hello! Here are a few questions and notes (testing new FreeDOS release on VirtualBox 6.1.30) 1) How to use `FDIMPLES` with Bonus CD? Running `FDIMPLES` with "FD13BNS.ISO" shows "Package media not found!", so I install additional so

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

Thanks to everyone who joined today's FreeDOS virtual get-together! Folks dropped in and out as they had time, and I think we had a dozen folks total who joined. Great opportunity for live debugging and testing. We'll do it again in 2022! On Sun, Dec 19, 2021 at 10:46 AM Jim Hall wrote: > Hi

Re: [Freedos-devel] FreeDOS virtual get-together on Sunday

Hi everyone FYI that the virtual get-together starts in 15 minutes, at 11am US/Central. The URL will be https://bluejeans.com/770650103/2822 See you there! On Thu, Dec 16, 2021 at 9:49 AM Jim Hall wrote: > Hi everyone! > > Every month, we host an online meeting so we can get to know each othe

[Freedos-devel] FreeDOS virtual get-together on Sunday

Hi everyone! Every month, we host an online meeting so we can get to know each other as more than just email addresses. We do these on the third Sunday of each month. Our next virtual get-together is coming up THIS SUNDAY, 12/19. Please join us at 11am US/Central (use your favorite timezone conve

Re: [Freedos-devel] FreeDOS 1.3-RC5

On 10.12.2021 14:55, Jerome Shidel wrote: >> >> Ouch. PGM.BAT works just fine, I was looking for PGME.BAT, my bad. > > No problem.  > > When PGME is installed using it’s installer, it mentions the batch > loader PGM. But when installed via FreeDOS package, there isn’t a good > way to make thes

Re: [Freedos-devel] FreeDOS 1.3-RC5

2 /fGray/p /t %1 LINE.3 %1 LightGreen LINE.3=/b1/e This is /f%2 line /f15 3 /a7/p :start vecho /t %0 LINE.1 %0 Cyan Running TEST.BAT outputs three lines, with the “line” a different color and number with color attribute 15 (white on black). Also, the last line has a blue background the width of the display. (Grey and Gray are the same color) Anyhow, I hope that all makes sense. Looking forward to you pull request. :-) 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

Re: [Freedos-devel] FreeDOS 1.3-RC5

On 9.12.2021 18:35, Jerome Shidel wrote: > >> * When launching PGME, I couldn't find the PGME.BAT file. So I can't >> start FDIMPLES for instance. > > There is no such file as PGME.BAT. Ouch. PGM.BAT works just fine, I was looking for PGME.BAT, my bad. >> * Speaking of FDIMPLES, it doesn't

Re: [Freedos-devel] FreeDOS 1.3-RC5

uot; To: "Technical discussion and questions for FreeDOS developers." Subject: Re: [Freedos-devel] FreeDOS 1.3-RC5 Hallo Herr thraex, am Donnerstag, 9. Dezember 2021 um 14:55 schrieben Sie: > I gave it a quick try in VirtualBox thanks for testing > * In VirtualBox the network seems

Re: [Freedos-devel] FreeDOS 1.3-RC5

Hallo Herr thraex, am Donnerstag, 9. Dezember 2021 um 14:55 schrieben Sie: > I gave it a quick try in VirtualBox thanks for testing > * In VirtualBox the network seems to be automagically detected, which is > *great*. But when I try to use say FDNET, I get a packet driver error > and it can't est

Re: [Freedos-devel] FreeDOS 1.3-RC5

Hi, > On Dec 9, 2021, at 8:55 AM, thraex wrote: > > > > On 9.12.2021 01:15, Jerome Shidel wrote: >> Hello FreeDOS Community, >> >> The wait for 1.3-RC5 is over. It has arrived! > > Yay! Thank you! :-) > I gave it a quick try in VirtualBox after choosing French and Turkish in > the install

<    1   2   3   4   5   6   7   8   9   10   >