freedos-user — FreeDOS general questions and other non-technical discussion

Re: [Freedos-user] DOS Networks

[<per...@gm...>]

Can you try the latest release:
https://github.com/FDOS/kernel/releases/tag/ke2045 and let me know if there
are still issues with Lantastic.  I doubt the updates help with the
Invisible Lan issue though.

(It took me a bit longer than expected because I got sidetracked looking at
the other Int 2F/12xx functions and creating some tests for them.)

Jeremy

On Fri, May 1, 2026 at 10:05 AM <dr...@cf...> wrote:

> Jemery,
>
>
>
> Any updates?
>
>
>
> Thanks…
>
>
>
>
>
>
>
> *From:* drohde--- via Freedos-user <fre...@li...>
> *Sent:* Wednesday, April 22, 2026 2:52 PM
> *To:* per...@gm...; 'Discussion and general questions about
> FreeDOS.' <fre...@li...>
> *Cc:* dr...@cf...
> *Subject:* Re: [Freedos-user] DOS Networks
>
>
>
> Thanks Jermey for looking into it.
>
>
>
> Freedos has loads more features than MSDOS.
>
>
>
> Doug
>
>
>
>
>
>
>
> *From:* per...@gm... <per...@gm...>
> *Sent:* Wednesday, April 22, 2026 11:32 AM
> *To:* dr...@cf...; Discussion and general questions about FreeDOS. <
> fre...@li...>
> *Subject:* Re: [Freedos-user] DOS Networks
>
>
>
>
>
> On Wed, Apr 22, 2026, 9:18 AM drohde--- via Freedos-user <
> fre...@li...> wrote:
>
> Ralf,
>
>
>
> Thanks for the response.
>
>
>
> Lantastic:   It installs fine and can trying to map a drive to a server
> but gets “unimplemented internal dos function INT 2F/121a”   Any thoughts
> on that one?   It can map a printer fine.
>
>
>
>
>
> int 2f/121a does look to be unimplemented, but also looks pretty simple to
> add.  I will see about adding it in next few days and let you know where
> you can get a kernel for further testing.
>
>
>
>
>
> Invisible Lan:  It installs but upon bootup, fails on “NETBIND failure”
>
>
>
>
>
> this will need further research but probably another unimplemented
> internal function or expected layout that isn't supported yet.
>
>
>
> Open to anything on these issues.    As mentioned,  they all work fine
> under DOS 6.22.    I would much rather use FREEDOS.
>
>
>
>
>
> ...
>
>
>
>
>
> Jeremy
>

Re: [Freedos-user] DOS Networks

[<dr...@cf...>]

Jemery,

 

Any updates?

 

Thanks…

 

 

 

From: drohde--- via Freedos-user <fre...@li...> 
Sent: Wednesday, April 22, 2026 2:52 PM
To: per...@gm...; 'Discussion and general questions about FreeDOS.' <fre...@li...>
Cc: dr...@cf...
Subject: Re: [Freedos-user] DOS Networks

 

Thanks Jermey for looking into it.

 

Freedos has loads more features than MSDOS.   

 

Doug

 

 

 

From: per...@gm... <mailto:per...@gm...>  <per...@gm... <mailto:per...@gm...> > 
Sent: Wednesday, April 22, 2026 11:32 AM
To: dr...@cf... <mailto:dr...@cf...> ; Discussion and general questions about FreeDOS. <fre...@li... <mailto:fre...@li...> >
Subject: Re: [Freedos-user] DOS Networks

 

 

On Wed, Apr 22, 2026, 9:18 AM drohde--- via Freedos-user <fre...@li... <mailto:fre...@li...> > wrote:

Ralf,  

 

Thanks for the response.

 

Lantastic:   It installs fine and can trying to map a drive to a server but gets “unimplemented internal dos function INT 2F/121a”   Any thoughts on that one?   It can map a printer fine.

 

 

int 2f/121a does look to be unimplemented, but also looks pretty simple to add.  I will see about adding it in next few days and let you know where you can get a kernel for further testing. 

 

 

Invisible Lan:  It installs but upon bootup, fails on “NETBIND failure”

 

 

this will need further research but probably another unimplemented internal function or expected layout that isn't supported yet.

 

Open to anything on these issues.    As mentioned,  they all work fine under DOS 6.22.    I would much rather use FREEDOS.

 

 

...

 

 

Jeremy

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[hollow-one <hol...@gm...>]

On 29/04/2026 17:00, Michael Brutman wrote:
> There should be no conflict between mTCP and other networking 
> programs.  The only exception is if NetDrive is loaded; WATTCP 
> programs probably don't like the fake packet driver that NetDrive 
> presents. (Fixing that is on the to-do list.)
>
> What exactly were you seeing that makes you think there is a conflict?

I haven't been playing with my 86box dos machine for a while, need to 
dbl check. I may not have the latest version of MTCP there too, so it 
can be as you say/suggest something more historic.

Good reminder to actually update my opinions.

-h1

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Louis S. <lps...@gm...>]

Good call out. I trust that Al will want to make this right with you.

-L

On Wed, Apr 29, 2026 at 9:51 AM Michael Brutman via Freedos-user <
fre...@li...> wrote:

> On a slightly related note ...
>
> I'm a little concerned about these changes to SSH2DOS
>
>    - My UTF-8 code is GPL3 in the mTCP project.  SSH2DOS is GPL2.  The
>    two licenses are incompatible.  Al just says "Original mTCP code is GPLv3.
>    This port maintains the same license", but you can't just hand-wave that
>    incompatible license problem away.  His fork now has at least a license
>    violation, possibly more depending on the Claude generated stuff.  That can
>    be fixed, but it's not completely legit as it is right now.
>    - Al stripped out the ability to define arbitrary mappings between
>    unicode code points and MSDOS code pages via text files, which is one of
>    the big features of the original code.  This is a regression.
>    - While the mTCP source is acknowledged, there is not a link to it
>    anywhere.  That's also a no-no when reusing open source.  It should mention
>    the original soure of the code in case somebody wants to try to keep it in
>    sync.
>    - I'm not thrilled about having the UTF-8 changes lumped into the same
>    change as Claude (AI) generated code.  They should have been committed
>    separately to make it clear what human/system generated what code.
>
> I'll try to bring these issues up with Al, but be aware that they exist.
>
>
> Mike
>
> On Wed, Apr 29, 2026 at 8:00 AM Michael Brutman <mbb...@br...>
> wrote:
>
>> There should be no conflict between mTCP and other networking programs.
>> The only exception is if NetDrive is loaded; WATTCP programs probably don't
>> like the fake packet driver that NetDrive presents. (Fixing that is on the
>> to-do list.)
>>
>> What exactly were you seeing that makes you think there is a conflict?
>>
>> Side note: The UTF-8 code for Al's was adapted from my mTCP code.
>>
>>
>>
>> On Wed, Apr 29, 2026, 04:05 hollow-one via Freedos-user <
>> fre...@li...> wrote:
>>
>>> That's very cool, does it work with MTCP?
>>>
>>> I found some programs using WatTCP/32 work and some colide with MTCP
>>> suite from Michael Brutman, thus asking.
>>>
>>> -h1
>>> On 28/04/2026 22:38, Vladimiro Burlak via Freedos-user wrote:
>>>
>>> Hi, is there a compiled version?
>>> The only file available for download is from 2021.
>>> At least I couldn't find the latest version.
>>>
>>> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
>>> fre...@li...) escribió:
>>>
>>>> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>>>> include (AI-generated) CP437/UTF-8 basic compatibility. It's based on
>>>> Toyoyo's fork (with AI-generated implementations of updated Ed25519,
>>>> Curve25519 encryption) of AnttiTakala's fork (which included updates for
>>>> DH, AES, and SHA256).
>>>>
>>>> https://github.com/ajrossnz/ssh2dos
>>>> https://github.com/Toyoyo/ssh2dos
>>>> https://github.com/AnttiTakala/SSH2DOS
>>>> https://sshdos.sourceforge.net/
>>>> _______________________________________________
>>>> Freedos-user mailing list
>>>> Fre...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>>
>>>
>>>
>>> _______________________________________________
>>> Freedos-user mailing lis...@li...://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>> _______________________________________________
>>> Freedos-user mailing list
>>> Fre...@li...
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Michael B. <mbb...@br...>]

On a slightly related note ...

I'm a little concerned about these changes to SSH2DOS

   - My UTF-8 code is GPL3 in the mTCP project.  SSH2DOS is GPL2.  The two
   licenses are incompatible.  Al just says "Original mTCP code is GPLv3. This
   port maintains the same license", but you can't just hand-wave that
   incompatible license problem away.  His fork now has at least a license
   violation, possibly more depending on the Claude generated stuff.  That can
   be fixed, but it's not completely legit as it is right now.
   - Al stripped out the ability to define arbitrary mappings between
   unicode code points and MSDOS code pages via text files, which is one of
   the big features of the original code.  This is a regression.
   - While the mTCP source is acknowledged, there is not a link to it
   anywhere.  That's also a no-no when reusing open source.  It should mention
   the original soure of the code in case somebody wants to try to keep it in
   sync.
   - I'm not thrilled about having the UTF-8 changes lumped into the same
   change as Claude (AI) generated code.  They should have been committed
   separately to make it clear what human/system generated what code.

I'll try to bring these issues up with Al, but be aware that they exist.


Mike

On Wed, Apr 29, 2026 at 8:00 AM Michael Brutman <mbb...@br...>
wrote:

> There should be no conflict between mTCP and other networking programs.
> The only exception is if NetDrive is loaded; WATTCP programs probably don't
> like the fake packet driver that NetDrive presents. (Fixing that is on the
> to-do list.)
>
> What exactly were you seeing that makes you think there is a conflict?
>
> Side note: The UTF-8 code for Al's was adapted from my mTCP code.
>
>
>
> On Wed, Apr 29, 2026, 04:05 hollow-one via Freedos-user <
> fre...@li...> wrote:
>
>> That's very cool, does it work with MTCP?
>>
>> I found some programs using WatTCP/32 work and some colide with MTCP
>> suite from Michael Brutman, thus asking.
>>
>> -h1
>> On 28/04/2026 22:38, Vladimiro Burlak via Freedos-user wrote:
>>
>> Hi, is there a compiled version?
>> The only file available for download is from 2021.
>> At least I couldn't find the latest version.
>>
>> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
>> fre...@li...) escribió:
>>
>>> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>>> include (AI-generated) CP437/UTF-8 basic compatibility. It's based on
>>> Toyoyo's fork (with AI-generated implementations of updated Ed25519,
>>> Curve25519 encryption) of AnttiTakala's fork (which included updates for
>>> DH, AES, and SHA256).
>>>
>>> https://github.com/ajrossnz/ssh2dos
>>> https://github.com/Toyoyo/ssh2dos
>>> https://github.com/AnttiTakala/SSH2DOS
>>> https://sshdos.sourceforge.net/
>>> _______________________________________________
>>> Freedos-user mailing list
>>> Fre...@li...
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>>
>>
>> _______________________________________________
>> Freedos-user mailing lis...@li...://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>> _______________________________________________
>> Freedos-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Michael B. <mbb...@br...>]

There should be no conflict between mTCP and other networking programs.
The only exception is if NetDrive is loaded; WATTCP programs probably don't
like the fake packet driver that NetDrive presents. (Fixing that is on the
to-do list.)

What exactly were you seeing that makes you think there is a conflict?

Side note: The UTF-8 code for Al's was adapted from my mTCP code.



On Wed, Apr 29, 2026, 04:05 hollow-one via Freedos-user <
fre...@li...> wrote:

> That's very cool, does it work with MTCP?
>
> I found some programs using WatTCP/32 work and some colide with MTCP suite
> from Michael Brutman, thus asking.
>
> -h1
> On 28/04/2026 22:38, Vladimiro Burlak via Freedos-user wrote:
>
> Hi, is there a compiled version?
> The only file available for download is from 2021.
> At least I couldn't find the latest version.
>
> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
> fre...@li...) escribió:
>
>> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>> include (AI-generated) CP437/UTF-8 basic compatibility. It's based on
>> Toyoyo's fork (with AI-generated implementations of updated Ed25519,
>> Curve25519 encryption) of AnttiTakala's fork (which included updates for
>> DH, AES, and SHA256).
>>
>> https://github.com/ajrossnz/ssh2dos
>> https://github.com/Toyoyo/ssh2dos
>> https://github.com/AnttiTakala/SSH2DOS
>> https://sshdos.sourceforge.net/
>> _______________________________________________
>> Freedos-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
> _______________________________________________
> Freedos-user mailing lis...@li...://lists.sourceforge.net/lists/listinfo/freedos-user
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Louis S. <lps...@gm...>]

Work with mTCP?  The code base is WatTCP based.  I’ve used ssh2dos in the
past and it worked with mTCP dhcp.

-L

On Wed, Apr 29, 2026 at 4:04 AM hollow-one via Freedos-user <
fre...@li...> wrote:

> That's very cool, does it work with MTCP?
>
> I found some programs using WatTCP/32 work and some colide with MTCP suite
> from Michael Brutman, thus asking.
>
> -h1
>

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[hollow-one <hol...@gm...>]

That's very cool, does it work with MTCP?

I found some programs using WatTCP/32 work and some colide with MTCP 
suite from Michael Brutman, thus asking.

-h1

On 28/04/2026 22:38, Vladimiro Burlak via Freedos-user wrote:
> Hi, is there a compiled version?
> The only file available for download is from 2021.
> At least I couldn't find the latest version.
>
> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via 
> Freedos-user (fre...@li...) escribió:
>
>     Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>     include (AI-generated) CP437/UTF-8 basic compatibility. It's based
>     on Toyoyo's fork (with AI-generated implementations of updated
>     Ed25519, Curve25519 encryption) of AnttiTakala's fork (which
>     included updates for DH, AES, and SHA256).
>
>     https://github.com/ajrossnz/ssh2dos
>     https://github.com/Toyoyo/ssh2dos
>     https://github.com/AnttiTakala/SSH2DOS
>     https://sshdos.sourceforge.net/
>     _______________________________________________
>     Freedos-user mailing list
>     Fre...@li...
>     https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Louis S. <lps...@gm...>]

>From <https://github.com/ajrossnz/SSH2DOS/releases/tag/v0.2.1%2BSHA256.1>,
download the "Source code" (zip).  Extract and there's a "bin/" folder.
Find the binaries in there.

On Tue, Apr 28, 2026 at 1:38 PM Vladimiro Burlak <vla...@gm...>
wrote:

> Hi, is there a compiled version?
> The only file available for download is from 2021.
> At least I couldn't find the latest version.
>
> El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
> fre...@li...) escribió:
>
>> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to
>> include (AI-generated) CP437/UTF-8 basic compatibility. It's based on
>> Toyoyo's fork (with AI-generated implementations of updated Ed25519,
>> Curve25519 encryption) of AnttiTakala's fork (which included updates for
>> DH, AES, and SHA256).
>>
>> https://github.com/ajrossnz/ssh2dos
>> https://github.com/Toyoyo/ssh2dos
>> https://github.com/AnttiTakala/SSH2DOS
>> https://sshdos.sourceforge.net/
>> _______________________________________________
>> Freedos-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>

Re: [Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Vladimiro B. <vla...@gm...>]

Hi, is there a compiled version?
The only file available for download is from 2021.
At least I couldn't find the latest version.

El mar, 28 abr 2026 a la(s) 2:15 p.m., Louis Santillan via Freedos-user (
fre...@li...) escribió:

> Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to include
> (AI-generated) CP437/UTF-8 basic compatibility. It's based on Toyoyo's fork
> (with AI-generated implementations of updated Ed25519, Curve25519
> encryption) of AnttiTakala's fork (which included updates for DH, AES, and
> SHA256).
>
> https://github.com/ajrossnz/ssh2dos
> https://github.com/Toyoyo/ssh2dos
> https://github.com/AnttiTakala/SSH2DOS
> https://sshdos.sourceforge.net/
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

[Freedos-user] New version of ssh2dos v0.2.1 with CP437/UTF-8 basic compatibility

[Louis S. <lps...@gm...>]

Al's Geek Lab (Alistair Ross) has forked/patched ssh2dos v0.2.1 to include
(AI-generated) CP437/UTF-8 basic compatibility. It's based on Toyoyo's fork
(with AI-generated implementations of updated Ed25519, Curve25519
encryption) of AnttiTakala's fork (which included updates for DH, AES, and
SHA256).

https://github.com/ajrossnz/ssh2dos
https://github.com/Toyoyo/ssh2dos
https://github.com/AnttiTakala/SSH2DOS
https://sshdos.sourceforge.net/

Re: [Freedos-user] FDNPKG16 PROBLEM

[victoria c. <sp...@jo...>]

LOL my server was down. dont mind me... false alarm!! ^^;;;;

On 4/25/26 3:04 PM, victoria crenshaw via Freedos-user wrote:
> I found a major problem with fdnpkg16 the curent version 0.99.8253d is 
> not working network wise so i will have to fix it
>
> give me a bit. please wait warmly
>
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDNPKG16 PROBLEM

[victoria c. <sp...@jo...>]

I found a major problem with fdnpkg16 the curent version 0.99.8253d is 
not working network wise so i will have to fix it

give me a bit. please wait warmly

Re: [Freedos-user] DOS Networks

[<dr...@cf...>]

Thanks Jermey for looking into it.

 

Freedos has loads more features than MSDOS.   

 

Doug

 

 

 

From: per...@gm... <per...@gm...> 
Sent: Wednesday, April 22, 2026 11:32 AM
To: dr...@cf...; Discussion and general questions about FreeDOS. <fre...@li...>
Subject: Re: [Freedos-user] DOS Networks

 

 

On Wed, Apr 22, 2026, 9:18 AM drohde--- via Freedos-user <fre...@li...> wrote:

Ralf,  

 

Thanks for the response.

 

Lantastic:   It installs fine and can trying to map a drive to a server but gets “unimplemented internal dos function INT 2F/121a”   Any thoughts on that one?   It can map a printer fine.

 

 

int 2f/121a does look to be unimplemented, but also looks pretty simple to add.  I will see about adding it in next few days and let you know where you can get a kernel for further testing. 

 

 

Invisible Lan:  It installs but upon bootup, fails on “NETBIND failure”

 

 

this will need further research but probably another unimplemented internal function or expected layout that isn't supported yet.

 

Open to anything on these issues.    As mentioned,  they all work fine under DOS 6.22.    I would much rather use FREEDOS.

 

 

...

 

 

Jeremy

Re: [Freedos-user] DOS Networks

[<per...@gm...>]

On Wed, Apr 22, 2026, 9:18 AM drohde--- via Freedos-user <
fre...@li...> wrote:

> Ralf,
>
>
>
> Thanks for the response.
>
>
>
> Lantastic:   It installs fine and can trying to map a drive to a server
> but gets “unimplemented internal dos function INT 2F/121a”   Any thoughts
> on that one?   It can map a printer fine.
>
>
>

int 2f/121a does look to be unimplemented, but also looks pretty simple to
add.  I will see about adding it in next few days and let you know where
you can get a kernel for further testing.


Invisible Lan:  It installs but upon bootup, fails on “NETBIND failure”
>
>
>

this will need further research but probably another unimplemented internal
function or expected layout that isn't supported yet.

Open to anything on these issues.    As mentioned,  they all work fine
> under DOS 6.22.    I would much rather use FREEDOS.
>
>
>
>
>
...


Jeremy

Re: [Freedos-user] DOS Networks

[<dr...@cf...>]

Ralf,  

 

Thanks for the response.

 

Lantastic:   It installs fine and can trying to map a drive to a server but gets “unimplemented internal dos function INT 2F/121a”   Any thoughts on that one?   It can map a printer fine.

 

Invisible Lan:  It installs but upon bootup, fails on “NETBIND failure”

 

Open to anything on these issues.    As mentioned,  they all work fine under DOS 6.22.    I would much rather use FREEDOS.

 

 

 

From: Ralf Quint via Freedos-user <fre...@li...> 
Sent: Monday, April 20, 2026 8:34 PM
To: fre...@li...
Cc: Ralf Quint <fre...@gm...>
Subject: Re: [Freedos-user] DOS Networks

 

On 4/19/2026 3:34 PM, drohde--- via Freedos-user wrote:

 

Is there a reason why FREEDOS would be incompatible with the DOS network software out there?

 

E.G Lantastic,  Invisible Lan,  PowerLan etc etc.

 

In general terms, no, FreeDOS should NOT be incompatible with DOS networking software out there. However, a lot of that software back in those days was VERY picky about the configuration, specially network drivers and specialized network redirectors.

I used to run even years ago, FreeDOS connected to a Novel Netware 3.12 network, as well as with Personal Netware and also used the Workgroup add-on for DOS.

 

Ralf

 

Re: [Freedos-user] DOS Networks

[Ralf Q. <fre...@gm...>]

On 4/19/2026 3:34 PM, drohde--- via Freedos-user wrote:
>
> Is there a reason why FREEDOS would be incompatible with the DOS 
> network software out there?
>
> E.G Lantastic,  Invisible Lan,  PowerLan etc etc.
>
>
In general terms, no, FreeDOS should NOT be incompatible with DOS 
networking software out there. However, a lot of that software back in 
those days was VERY picky about the configuration, specially network 
drivers and specialized network redirectors.

I used to run even years ago, FreeDOS connected to a Novel Netware 3.12 
network, as well as with Personal Netware and also used the Workgroup 
add-on for DOS.


Ralf

[Freedos-user] DOS Networks

[<dr...@cf...>]

 

Is there a reason why FREEDOS would be incompatible with the DOS network
software out there?

 

E.G Lantastic,  Invisible Lan,  PowerLan etc etc.

 

I have been comparing FREEDOS with MSDOS 6.22.    All the networks work
perfectly under MSDOS.

 

Thanks.

 

 

Re: [Freedos-user] FDNPKG16 feedback

[Roger <rog...@gm...>]

Still waiting for Javascript and Rust language porting/compiling back to DOS...

So we can purchase more DOS compatible products via Amazon.com and
other websites.

On Fri, Apr 17, 2026 at 5:54 PM victoria crenshaw via Freedos-user
<fre...@li...> wrote:
>
> It is too quiet.. please reach out to me if u have tried the latest
> FDNPKG16 version 0.99.8253d (NOT IN TEST BUILD THATS BROKEN FOR THE
> MONTH) [which was fixed shortly afterwards]
>
> Please reach of if u tried it. <3
>
> https://4ch.mooo.com/freedos/repos/1.4/net/fdnpkg16.zip
> here is the fixed package file.
>
> use fdinst to install it once it is on your system
>
> htget -o fdnpkg16.zip
> https://4ch.mooo.com/freedos/repos/1.4/net/fdnpkg16.zip
> fdinst install fdnpkg16.zip
>
>
> I would like to apologize for the repo problem. It was not clear to me
> that it's a RELEASE repository for the package. which i needed to update
> again to fix the document problem i forgot about in the current release.
>
> I updated documentation for 0.99.8253d for next test build.
>
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] FDNPKG16 feedback

[victoria c. <sp...@jo...>]

It is too quiet.. please reach out to me if u have tried the latest 
FDNPKG16 version 0.99.8253d (NOT IN TEST BUILD THATS BROKEN FOR THE 
MONTH) [which was fixed shortly afterwards]

Please reach of if u tried it. <3

https://4ch.mooo.com/freedos/repos/1.4/net/fdnpkg16.zip
here is the fixed package file.

use fdinst to install it once it is on your system

htget -o fdnpkg16.zip 
https://4ch.mooo.com/freedos/repos/1.4/net/fdnpkg16.zip
fdinst install fdnpkg16.zip


I would like to apologize for the repo problem. It was not clear to me 
that it's a RELEASE repository for the package. which i needed to update 
again to fix the document problem i forgot about in the current release.

I updated documentation for 0.99.8253d for next test build.

[Freedos-user] EtherSlip users: Updated EtherSlip with 2 bug fixes

[Michael B. <mbb...@br...>]

If you are using EtherSlip from the Crynwr packet driver collection, the
latest version (11.7) has one minor bug and one serious bug.  I have a new
version (11.8) posted that you can upgrade to.  The bugs are:

1. The incorrect MAC address was being set in the simulated Ethernet
header. This broke mTCP NetDrive.  (I patched the existing 11.7 version
last year for this.)

2. The code in EtherSlip that simulates ARP responses has a pointer bug in
it. This can cause data corruption or crash your program any time it tries
to send an ARP request.

I've updated the source code and I have rebuilt the packet driver from
scratch.  The new version can be found at
https://www.brutman.com/Device_Drivers/packet_drivers/EtherSlip_v11.8.zip
.  More details about the bugs are in the ZIP archive, which also includes
the updated source code.

Also, please spread the news around - the second bug affects all EtherSlip
users, not just mTCP users.


-Mike

[Freedos-user] Incorrect UK key mapping with MKEYB.

[G.W. H. <fr...@ju...>]

Hi there,

After a disc died recently, when I replaced it I installed a fresh
copy of FreeDOS 1.4.  Until now (for decades) on this machine I've
been using KEYB from MS-DOS for the keyboard map, but this time for
whatever reason I chose to use MKEYB.

Everything went fine until the user fired up the 'desk calculator'.
This is a little something of my own which emulates an old tally-roll
calculator.  It pops up when the user hits CTRL-C while running the
financial stuff.  Four-function arithmetic on floating-point numbers,
for which the users tend to use the numeric keypad (a lot).

Using the MKEYB UK layout, with 'NUM LOCK' set ON the 'del'/'.' key on
the numeric keypad was incorrectly configured.  It produced ',' (comma)
instead of '.' (dot).  On shutting down the calculator we found that
the problem wasn't unique to the calculator.  It affected everything.

Instead of 'MKEYB UK' I tried 'XKEYB UK'.  The user was happy again.

Just a heads up.

-- 

73,
Ged.

Re: [Freedos-user] Interesting DOS youtube video

[Joao S. <joa...@gm...>]

Hello.

I lie dos, i used pc-dos 7... today use for games.

Old games that use pc speaker on modern hardware is impossible... so i
stick to emulation.

On Thu, Apr 9, 2026 at 10:18 AM G.W. Haywood via Freedos-user <
fre...@li...> wrote:

> Hi there,
>
> On Thu, 9 Apr 2026, Michał Dec via Freedos-user wrote:
> > On Thu, 9 Apr 2026, Lyn Thomas via Freedos-user wrote:
> >
> > > https://www.youtube.com/watch?v=k7ykuZBtmS8 mentions that he was using
> > > Freedos
> >
> > ... I wonder why he's using 3 different ways of pronouncing DOS:
>
> For the technologically challenged amongst us (those like me, unable
> to watch YouTube videos) what is the video about - and what makes it
> interesting to us here?
>
> --
>
> 73,
> Ged._______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

Re: [Freedos-user] Interesting DOS youtube video

[G.W. H. <fr...@ju...>]

Hi there,

On Thu, 9 Apr 2026, Michał Dec wrote:

> I've checked this guy out and I'm calling this horse radish.
> ...

Confirmed my suspicions, thanks.

-- 

73,
Ged.

Re: [Freedos-user] Interesting DOS youtube video

[Michał D. <mo...@gm...>]

I've checked this guy out and I'm calling this horse radish.

His channel: https://www.youtube.com/@ramB-m2p

The oldest video is barely 2 weeks old. I'm not that confident anymore 
that he used FreeDOS for 30 days. In the meantime of last 30 days he's 
covered all kinds of topics:

- Windows settings that kill SSDs

- spyware settings in Windows

- random dunking on Windows again

- privacy concerns for Google backups

- endless Linux banter from gaming, to vulnerabilities and systemd

DOS sits only 3 days into his past, with 3 videos made after it, and 16 
videos made before it. That DOS bet either must've happened a long time 
ago or someone else's been making videos for him cause there's no way he 
could put together a video on DOS and upload it to YouTube. Unless this 
is where his phone exception comes in.

All videos have a consistent theme of clickbait and sensationalism in 
titles and thumbnails. It's really telling how his videos max out below 
700 views with 2 exceptions of 5k and 8k views. In the video that 
garnered 8k views there is completely 0 engagement from him with his 
audience in terms of comments which is also the state of affairs for the 
rest of his videos. My bet is that this is a guy who farms engagement 
and AdSense revenue from AI content generated for free. He doesn't even 
pay enough mind to proofwatch his own stuff because at 11:19 in the DOS 
video the audio and video feed of our hero just cuts off. Looks like 
mass produced content.

BR,

Michał

W dniu 9.04.2026 o 11:58, G.W. Haywood via Freedos-user pisze:
> Hi there,
>
> On Thu, 9 Apr 2026, Michał Dec wrote:
>> W dniu 9.04.2026 o 11:15, G.W. Haywood via Freedos-user pisze:
>>> On Thu, 9 Apr 2026, Michał Dec via Freedos-user wrote:
>>>> On Thu, 9 Apr 2026, Lyn Thomas via Freedos-user wrote:
>>>>
>>>> > https://www.youtube.com/watch?v=k7ykuZBtmS8 mentions that he was 
>>>> using
>>>> > Freedos
>>>> ...
>>>
>>> For the technologically challenged amongst us (those like me, unable
>>> to watch YouTube videos) what is the video about - and what makes it
>>> interesting to us here?
>>
>> A man accepts a bet that he'll be able to do his work on a DOS for 30 
>> days. ... he wins the bet in the end ...
>
> Thank you.  The summary reads very well.  Was it generated by AI?
>
>
>
> _______________________________________________
> Freedos-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freedos-user