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.
especially since other
kernels behaves differently.
--Wolf
On Thu, May 29, 2025, 13:32 Bernd Böckmann via Freedos-devel <
[email protected]> wrote:
> Hi Wolf,
>
> > Am 28.05.2025 um 22:32 schrieb Wolf Bergenheim >:
> >
> > Are you running in a VM or
? So now I wonder why not?
Are you running in a VM or physical machine? What dos DR-DOS return?
--Wolf
[1]
https://github.com/boeckmann/edit/blob/cf4e4f6fb3dc346618318bd1475552fa51c6a4b7/source/message.c#L182
On Sun, May 25, 2025, 20:34 Bernd Böckmann via Freedos-devel <
[email protected]
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 _
things easier, but if it's a
bother I can also grab it from the svn, and save it in a separate directory.
> That would make incorporating it into other projects very
> easy. The .asm file compiles with the Watcom assembler WASM.
>
Cool, I
x27;d like to incorporate it in DOG. :D
The header file seems to be under MIT, does that mean that the whole thing
is released under MIT?
What's the best way to incorporate it into a project? I guess the tags
correspond to separate releases? Which release do you recommend, the newest
20250105?
something like it should also not be a very hard thing to do,
though. @Jim this could be your next video (hint, hint, nudge, nudge) ;).
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
On Tue, Feb 18, 2025 at 10:32 PM Julius Schwartzenberg via Freedos-devel <
[email protected]
pefully those bugs were fixed in the 25+ years since then.
--
|\_
| .\---.
/ ,__/
/ /Wolf _
___
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
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
o make everything
> better. FreeDOS is an open source community project.
>
100% Maybe if we write a package build guide we could have more help, I
feel packaging is something non-developers could definitely help with.
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
___
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
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
Huh didn't think it would be interesting enough for the new documentation
website. :D
Let me make a pull request to add it, we can test how external pull
requests work. We can then discuss the specifics of the article in the PR :)
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
O
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
[email protected]
https
OM
in the Gitlab repository, but not in the installer. It was added in July to
the repo. Is this an oversight or intention? What about 4DOS, should we
ship it as well? It's Open Source sort-of~ish
<https://4dos.info/sources.htm>...
--Wolf
--
|\_
| .\---.
/
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
all a whole group?
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
On Sat, Nov 16, 2024 at 8:00 AM Jerome Shidel via Freedos-devel <
[email protected]> wrote:
> Hi All,
>
> As we are most likely approaching the release of FreeDOS 1.4 in the very
> near f
0.0 happy. Some
example files would be nice and maybe more helpful error messages.
I tried looking at the code but gave up very quickly as it is basically
completely undocumented and uses a tonne of macros to do some macro magic.
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
On Sun, Nov 10,
nks for sharing. I'll definitely check and see if I can migrate over to
Gregory's Make for DOG! :D
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
___
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
-devel.
>
> And someone pointed me to this item on DOS Ain't Dead:
>
> > SQLite 3.46.1 compiled for DOS
> https://www.bttr-software.de/forum/forum_entry.php?id=22112
>
>
Nice! Glad to see someone cares to compile SQLite for DOS!
We should definitely include it in FreeDOS
ce, as one of my
projects I plan to install freeDOS/svarDOS on my HP Mini 210 which I have
lying around... I'd like to try optimizing for as high of a CPU as possible
and see how fast I could make DOS code 🤔
--Wolf
--
|\_
| .\---.
/ ,__/
/ /
oding too. So it would be cool to have a live USB FD distro for
both:
FD Writer and FD Coder :P So if you build the FD Writer I'm going to build
FD Coder from it, if you don't >:D
I'd also be interested in helping out, though I don't have a lot
instead of
printf to print the string, and see if that helps. I think it could
potentially help a lot, but with the side effect of the tab-completion not
being interruptible (unlessthat is also added in, but then it all becomes a
lot more complex...).
Oh boy, I almost lost myself in this rabbit hole
CD!
:D
However, I do realize that I'm working on a niche of a niche and no-one who
is installing
FreeDOS to play old games is going to even look at DOG.
It was cool to have it on the main CD, though! :D
Carry on, and keep up the good work!
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
21/AX=3306h,
like the other one did. Good job on that! I will link to your site from my
DOG site :)
I think this should be more prominently linked from on
https://freedos.org/about/devel/ instead of just (copy 2) of the RBIL box,
just my 2 cents...
--Wolf
PS +1 for JS
, they are easier
to read, and the time one also has problems with some of the tables.
Oh and one more thing it also has a nice interrupt jump table which I find
very handy:
https://www.ctyme.com/intr/int.htm
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
On Sat, Jul 27, 2024 at 10:12 PM J
know if anyone knows anything about MS-DOS and/or DR-DOS?
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
___
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
checkout to make contributions go live
faster.
> And if we do this for general documentation, we might consider moving
> the FreeDOS Help <https://home.mnet-online.de/willybilly/fdhelp-dos/>
> to be hosted in this GitHub project, so we can continue to manage it
p.htm
-Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
On Mon, Jun 3, 2024 at 10:58 PM Rugxulo via Freedos-devel <
[email protected]> wrote:
> Hi,
>
> On Sun, Jun 2, 2024 at 7:33 AM perditionc--- via Freedos-devel
> wrote:
> >
> > DJGPP is
make a note, I'll see what I can do once I start porting DOG to OW :)
Thanks again for the explanation and the resulting deep dive! :P
-Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
___
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
the
limit... I tried but get an ugly crash, but FreeCom doesn't crash, how does
it make the command tail > 127 bytes?
[1] https://github.com/FDOS/kernel/blob/master/hdr/process.h#L53
[2] https://github.com/FDOS/kernel/blob/master/hdr/tail.h#L43
-Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf
On Fri, May 31, 2024 at 12:56 AM Eric Auer via Freedos-devel <
[email protected]> 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
On Thu, May 30, 2024 at 4:50 PM Steve Nickolas via Freedos-devel <
[email protected]> 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
On Thu, May 30, 2024 at 4:25 PM Jim Hall via Freedos-devel <
[email protected]> 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
> &
On Thu, May 30, 2024 at 11:52 AM Bernd Böckmann via Freedos-devel <
[email protected]> 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
drive.
So now I'm looking at setting up Dosemu2 (I remember using doemu ~20 years
ago).
What do your dev environments look like? How do you make an efficient
edit-build-test cycle? Has anyone tried using watcom as a crosscompiler?
--Wolf
--
|\_
| .\---.
/ ,__/
/ /Wolf _
__
such urges, please send me a private email (to keep this
slight OT away from the list), and I'll be happy to answer any questions
you might have.
--Wolf Bergenheim
Wolf Bergenheim <[EMAIL PROTECTED]>
Boardmember, Linux-aktivaattori Ry [http://www.l
Hi!
I'm back from my hibernation. I see that thins seem to be progressing
nicely. I plan to continue working on DOG beginning next month (:
--W
--
|\ _ Maintainer of DOG - The New Shell!
| .\---. http://dog.sourceforge.net/index.php
/ ,/ http://sourceforge.net/projects/
37 matches
Mail list logo
