Re: [Freedos-devel] Kernel behavior on critical error return AX=0

Ah sorry forgot to report the kernel version: Using the VR command in DOG I get: |\_ | .\---. / ,__/ / /C:\DOG\SRC % vr Running under Dosemu, version 2.0.0.0 FreeDOS version 1.3 FreeDOS Kernel compatibility 7.10 FreeDOS kernel 2043 (build 2043 OEM:0xfd) [compiled May 14 2021] DOG version 0.

Re: [Freedos-devel] Kernel behavior on critical error return AX=0

Hi Bernd, I can confirm, I also get AH=38h in dosemu when I try to access a nonexistent drive a: e.g. by calling ls a: with DOG. Same thing happens with dir a: using FreeCom. Both of these report a similar error: DOG reports: Read error drive A: DOS area (Abort/Fail/Ignore/Retry)? FreeCom report

Re: [Freedos-devel] Kernel behavior on critical error return AX=0

Hmm, The code tries to ignore any non disk-related errors, and returns 0x00 (ignore). Ignore should become fail if it's not allowed. And when it detects a disk error it seems to set an internal flag to indicate a critical error which is then tested for in the TestCriticalError[1] function. I gues

Re: [Freedos-devel] [Freedos-user] Info on creating Freedos packages?

Hey, Okay I created a merge request. There wasn't actually a separate LSM page, but I included your description from your reply. https://gitlab.com/FreeDOS/docs/-/merge_requests/4 Please review and LMK if something needs a rewrite :) --Wolf -- |\_ | .\---. / ,__/ / /Wolf _ On Wed

Re: [Freedos-devel] Proposal: replace FreeDOS Edit with SvarDOS Edit

On Tue, Feb 18, 2025 at 11:18 PM Bernd Böckmann wrote: > > I took a look, and it's really cool! I was thinking I'd probably want > > to write something like this on my own, but wmincrt seems to do what > > I'd want, so I'd like to incorporate it in DOG. :D > > The header file seems to be under MI

Re: [Freedos-devel] Proposal: replace FreeDOS Edit with SvarDOS Edit

On Tue, Feb 18, 2025 at 6:02 PM Bernd Böckmann via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > the above mentioned SVED shows how to write *really* small programs in > WATCOM C. > > > > it provides a minimum ASM stub, which calls a C main() which does all > the hard work. > > T

Re: [Freedos-devel] Useful tool: stuffkey

Neat program, I guess, but... If Terje had even gone with an MIT or BSD license... I'd stay away from this since it's not released under a proper license. It's not open source, but rather "source available". This makes it problematic to include in FreeDOS. Rebuilding something like it should also

Re: [Freedos-devel] Building entire FreeDOS release from source within FreeDOS

On Thu, Feb 6, 2025 at 9:10 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Thu, Feb 6, 2025 at 1:48 PM Bruno Ribeiro via Freedos-devel > > Would Micro-C be considered for inclusion in FreeDOS? > > > It's a pretty good C compiler, and once upon a time I remember th

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

Hi Danilo, Last time(s) it was a Google Meet. Jim sends a link on Sunday. All you need is a modern browser like Firefox or Chrome and a google account (e.g. gmail etc). In theory Meet Supports also joining by phone 🤔 --Wolf -- |\_ | .\---. / ,__/ / /Wolf _ On Fri, Dec 6, 2024 at 11

Re: [Freedos-devel] FreeDOS Interim Build T2412

Hey Jerome, On Tue, Dec 3, 2024 at 1:19 AM Jerome Shidel via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > 0.8.3c would have been some changes made to the 0.8.3b version. It got a > version bump so it would not be confused with the existing 0.8.3b package > by any of the program

Re: [Freedos-devel] FreeDOS Interim Build T2412

Hey, Changelog says DOG was upgraded to 0.8.5b but https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/unstable/pkg-html/dog.html says 0.8.4b and on that page it also links to somthing called 0.8.3c?? --W -- |\_ | .\---. / ,__/ / /Wolf _ On Sun, Dec 1, 2024 at 6:0

Re: [Freedos-devel] New article for DOG

n Mon, Nov 25, 2024 at 5:45 AM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Sat, Nov 23, 2024 at 9:03 PM Wolf Bergenheim via Freedos-devel > wrote: > > > > I wrote an article on how DOG manages the environment (and alias) memory: > &

[Freedos-devel] New article for DOG

I wrote an article on how DOG manages the environment (and alias) memory: https://dog.zumppe.net/post/env/ --Wolf -- |\_ | .\---. / ,__/ / /Wolf _ ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net

[Freedos-devel] Shells (command interpreters) in FreeDOS

Hey all, In the last FreeDOS get-together we were talking about package groups, Jerome mentioned that he was moving things around, and I asked about a SHELLS group which we don't have. Jerome mentioned maybe these types of programs belong in the APPS group instead. They fit the description of the

Re: [Freedos-devel] FreeDOS 1.4

On Sun, Nov 17, 2024 at 4:54 AM Wolf Bergenheim wrote: > Hey, > > Thanks for putting this together. I finally got to test it, but I'm > wondering if there is a way to install all the packages which were not > installed (I have the Full USB)? > > Could there maybe be an option to also install them

Re: [Freedos-devel] FreeDOS 1.4

Hey, Thanks for putting this together. I finally got to test it, but I'm wondering if there is a way to install all the packages which were not installed (I have the Full USB)? Could there maybe be an option to also install them through the installer or provide a way through fdnpkg to install a w

Re: [Freedos-devel] Make make great again!

I managed to build this with a combination of running configure on linux like so: ./configure --prefix=/gmake CC=gcc CPP=cpp CXX=cxx DEPDIR=deps.tmp and then using DJGPP and a Makefile I built (attached) I managed to compile it with make -f makefile.dos make However the resulting make.exe progra

Re: [Freedos-devel] Make make great again!

On Thu, Oct 24, 2024 at 7:42 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Thu, Oct 24, 2024 at 12:17 PM Gregory Pietsch via Freedos-devel > wrote: > > > > I am sending a GPLed version of the Unix make utility in the hopes > > that other programmers can make it

Re: [Freedos-devel] SQLite 3.46.1 compiled for DOS

On Thu, Oct 24, 2024 at 7:04 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > I put out a call on my Fosstodon not long ago to encourage anyone who > might be working on open source DOS stuff to join our email list and > share the news on freedos-devel. > > And someone

Re: [Freedos-devel] Source code distribution

On Mon, Oct 21, 2024 at 7:50 AM Louis Santillan via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Sat, Sep 28, 2024 at 12:13 PM Michael Brutman via Freedos-devel < > freedos-devel@lists.sourceforge.net> wrote: > >> [SNIP] >> You are responsible for making that source code availa

Re: [Freedos-devel] GeoWorks

On Tue, Oct 1, 2024 at 11:59 AM Liam Proven via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > I want to make a live bootable USB with FreeDOS and a few word > processors and other writer's tools, such as an outliner, maybe a > spreadsheet, as a distraction-free writing tool. > >

Re: [Freedos-devel] FreeDOS gitlab ticket: Ctrl-C versus TAB freeze in freecom

Hmm interesting... I looked at freecom, and when it's beeping for a tab it calls the beep() function : void beep(void) { sound(900); delay(200); /* 400 */ nosound(); delay(100); } Which in turn uses the delay function. The dela

Re: [Freedos-devel] Packages on the FreeDOS distribution

Hey all, I don't really have a horse in this race since I don't really contribute to the FD distribution, but as a developer of a tool getting relegated to the "other" CD, does make me a bit sad... I was surprised and quite proud to see DOG still being part of the main CD! :D However, I do realize

Re: [Freedos-devel] Improved RBIL

Sweet, thanks for the explanations! I admit I took a very quick look... ;o_o Aah now I see all the missing interrupts I was looking at the DOS kernel list... Thanks for pointing me to the right place! :D I really like this list a lot, PLUS it doesn't break e.g. in INT 21h/AH=30h and INT21/AX=3306h

Re: [Freedos-devel] Improved RBIL

Wow, nice work! I really like the formatting of the Exec function, but looking at the site itself I find it hard to find the interrupt I'm looking for. Can you make the function number maybe a bit more prominent? I'm mostly looking up interrupts by number and if I'm looking for a function by name

[Freedos-devel] Initial Environment block

Hi, I'm working on an article about the environment, and found something which was new to me, namely that DOS (at least MS-DOS and FreeDOS, haven't checked with DR-DOS yet) actually doesn't give the primary shell an environment of h when CONFIG.SYS uses a MENU. This mini environment is used to

Re: [Freedos-devel] FreeDOS wiki is temporary offline

Hi, On Fri, Jul 5, 2024 at 8:07 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > I really like your suggestion of using GitHub and Markdown to make it > easier to write the docs, share the docs, and include the docs in the > FreeDOS distribution! That's more extensibl

Re: [Freedos-devel] problems with moving in a long history

I did some more digging... Found a wikipedia article discussing it [1] but maybe more interesting was a german text on 4dos tips[2] apparently Windows 95 only put the rest of the command line in CMDLINE. And it makes sense that it was introduced because of long file name support. With LFN 127 chara

Re: [Freedos-devel] problems with moving in a long history

On Sun, Jun 2, 2024 at 5:13 AM Jerome Shidel via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > FreeCOM copies the first 126 bytes to the new PSP terminated by 0xd. Then > it creates an environment variable “CMDLINE” with the entire command line. > > Ah I see! Thanks! :D So I supp

Re: [Freedos-devel] problems with moving in a long history

On Sat, Jun 1, 2024 at 8:57 PM Bernd Böckmann via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > On 15.05.2024 16:01, Wilhelm Spiegl via Freedos-devel wrote: > [...] > I hope that this behaviour is reproducable. > > Some details: cursor positioning algorithm is broken if scrolli

Re: [Freedos-devel] Back at it with DOG

On Fri, May 31, 2024 at 12:56 AM Eric Auer via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > Hi and welcome back, Wolf :-) > Thanks Eric, I remember you from ~20 years ago! :D > edit code on linux and then build and test in a QEMU box which is > > constantly running. :) > > Time

Re: [Freedos-devel] Back at it with DOG

On Thu, May 30, 2024 at 4:50 PM Steve Nickolas via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Thu, 30 May 2024, Wolf Bergenheim via Freedos-devel wrote: > > > I'm using Borland C++ 3.1 for now as that's the compiler I used 22 years > > a

Re: [Freedos-devel] Back at it with DOG

On Thu, May 30, 2024 at 4:25 PM Jim Hall via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Wed, May 29, 2024 at 9:53 PM Wolf Bergenheim via Freedos-devel > wrote: > > > > What do your dev environments look like? How do you make an efficient > &

Re: [Freedos-devel] Back at it with DOG

On Thu, May 30, 2024 at 11:52 AM Bernd Böckmann via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > Hi Wolf, > > welcome to the mailing list. Great to hear you started working again on > DOG. Putting it on Github (or some other publicly accessible repo) sounds > like a good idea :) >

[Freedos-devel] Back at it with DOG

Hi everyone, After ~22 years I got back into coding on DOG. I'm working my way towards a new release, 0.8.4b, in the ~soon timeframe. I'm also working on moving the source code to GitHub and fixing the website. It had apparently broken several years ago... So far I've been fixing the code and imp