That attitude toward the MS-DOS source code seems rather limiting and
short-sighted.
My recent device driver worked well enough on later versions of DOS (and
FreeDOS) but I was having a devil of a time trying to figure out why DOS
2.x would not honor the device driver telling it that the media
You clearly don't use search engines too much ...
Try "FreeDOS" and "Networking" as your two words for the search.
On Tue, Apr 23, 2024 at 7:38 PM Brandon Taylor via Freedos-user <
freedos-user@lists.sourceforge.net> wrote:
> Since FreeDOS doesn't support physical network hardware (even if
I'm just kind of amazed at what I read here at times.
It is no secret that DOS is no longer a mainstream operating system. As a
result, support for it on physical hardware is minimal, if it is supported
at all. Modern machines are just not intended to be used with DOS as the
primary, "bare
FAT is finicky but FAT is not the issue here.
As long as the machine has sufficient time to complete its last writes and
you don't have any programs running using the disk, it should always be
safe to shut down - DOS doesn't buffer or delay writes unless you have some
sort of disk caching program
sort of proxy that meets the spirit of the requirement.
Anyway, I think the OP has been scared off so this is an academic
discussion now. ;-0
On Wed, Jan 10, 2024 at 3:02 AM Frantisek Rysanek
wrote:
> On 8 Jan 2024 at 10:29, Michael Brutman via Freedos-user wrote:
> ...
> >
&
That last post was impressive, but I think it makes things way too
complicated.
Obviously something that does real-time operations should not be burdened
with a TSR. But it should also not be burdened with running DOS on legacy
hardware either. Nobody in their right mind is running something
How much is it worth ($$$) to your supervisor?
SNMP runs over UDP. It is possible to write an SNMP agent that runs in the
background as a TSR, but such a thing doesn't exist today. If somebody is
willing to invest it can be done.
-Mike
On Sun, Jan 7, 2024 at 12:30 PM Anton Gustafsson via
It's difficult to follow all of the details of the discussion.
Have you ever looked at getting a shell account on sdf.org? It still
supports plain old Telnet I think it comes with an email address. They
support POP3 and IMAP access to the email too.
Links and Lynx are available there when
I added some limited Unicode support to mTCP Telnet and mTCP IRCjr in the
last release a few months ago.
- I used a text file to store the mapping. That lets people add code
points or make corrections if they don't like the choices I made.
- The code uses the text file both ways; to
On Mon, Apr 10, 2023 at 1:00 PM Jim Hall wrote:
>
> Impressive for a PCjr. :-)
>
>
One day we might even be able to boot FreeDOS on it ... (it has some
challenges.)
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
ted on the website. I'll also share it on Mastodon.
>
>
> Jim
>
> On Sat, Apr 1, 2023 at 11:38 AM Michael Brutman
> wrote:
> >
> > http://www.brutman.com/mTCP/mTCP.html
> >
> > From the release notes:
> >
> > Unicode support for Telnet and I
http://www.brutman.com/mTCP/mTCP.html
>From the release notes:
- Unicode support for Telnet and IRCjr
- RLE graphics support in Telnet (fun as a demonstration, but not very
practical)
- The web server gets a built-in SNTP client for keeping the server time
correct across many
I think it is pretty safe to assume that everybody using FreeDOS in the
last 10 to 20 years has access to another, more capable device that can
read PDFs. Even low end cell phones have had this capability for the past
5 years.
I started with pure TXT files, composed on the same DOS machine that
. Can we not do that in the
future? Nobody is going to want to wade through a 293KB text file.
-Mike
On Wed, Mar 15, 2023 at 5:59 PM Michael Brutman
wrote:
> What version of FreeDOS are you installing?
>
> If things are really borked then keep in mind that mTCP is a standalone
What version of FreeDOS are you installing?
If things are really borked then keep in mind that mTCP is a standalone
project and you can get all the original files at its website. See
http://www.brutman.com/mTCP/mTCP.html for the downloads and PDF
documentation.
Mike
On Wed, Mar 15, 2023,
I initially mis-read what Tom had written about programming on DOS being
painful. He is not wrong. ;-0 I program "for" DOS for the challenge. But
I don't program too much "on" DOS, because I'm not interested in
challenging myself that much.
I used to use Turbo C++ 3.0 for DOS on a DOS machine
what your keyboard can produce.
-Mike
On Thu, Jan 26, 2023 at 8:36 PM Michael Brutman
wrote:
> I've never wanted to support Unicode and UTF-8 because of the potential
> performance problems on slow machines and the problem of mapping Unicode to
> code pages. I solved one problem, but
I've never wanted to support Unicode and UTF-8 because of the potential
performance problems on slow machines and the problem of mapping Unicode to
code pages. I solved one problem, but not the other. ;-0
If you'd like to try it the instructions are at
Read the documentation for whatever networking software you are using.
mTCP in particular is not a "resident" program, so your FreeDOS machine
will not respond to ping requests unless an mTCP program is actively
running. WATTCP programs have the same behavior.
d, but lpr.exe can be found in
> <
> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/wattcp/wat2001b.zip
> >.
> Look in apps/apps.zip.
>
> Maybe Michael Brutman wishes to port it to his mTCP suite:
> http://www.brutman.com/mTCP/
>
> Cheers,
> Rober
This is an 8 year old email thread and you are expecting working links from
back then?
Regardless, archive.org is your friend:
https://web.archive.org/web/20130430233113/https://geek.com/chips/nasa-needs-8086-chips-549867/
Consider donating to them.
On Sat, Jul 23, 2022 at 6:52 AM Aitor
It would be swell, but it's never going to happen ... at least not from me.
- Computationally, SSH is not feasible on the 16 bit machines that I
target for this project.
- Even with enough compute power, you need to find DOS equivalents of
all of the libraries. Which includes the
Just for a little bit ... :)
Thanks!
Mike
On Fri, Jul 8, 2022, 4:59 PM Jim Hall wrote:
> >
> > On Fri, Jul 8, 2022 at 6:19 AM Eric Auer wrote:
> >>
> >>
> >> Hi! Forwarding from BTTR:
> >>
> >> A new mTCP is available (2022-07-
Hi - yes it is true, a new version is available.
Please hold off on mirroring it at ibiblio for a little bit ... I'm trying
to gauge how many users I have based on downloads, and that falls apart
once people start to mirror it.
Cheers,
Mike
On Fri, Jul 8, 2022 at 6:19 AM Eric Auer wrote:
>
This has all been terribly interesting, but I can't help but think:
- This product should have been ported to a more capable operating
system years ago.
- The inner workings of how the product was made to run under DOS seems
to have rotted away.
- This really isn't relevant to
I have that exact same card in a Pentium 133 system. It's a good card.
This sounds silly, but try removing and reseating the card in the slot.
Really ... I've had cards that have been installed for ages where the
electrical contact on the pins oxidizes and then the card becomes flakey,
and this
I hate to even suggest this, but are you using the /B option on the file
copy to indicate that a binary copy is needed? Otherwise, the first Ctrl-Z
in the file will end the file copy prematurely.
On Wed, Jun 16, 2021 at 3:37 PM Frantisek Rysanek
wrote:
> Dear gentlemen,
>
> on and off, with
Kelley: That version of mTCP is nearly 8 years old ... Please get the
current version and repeat the trace file steps. It might even just work
without debugging ... I've made a lot of reliability improvements in the
past 8 years. Also, please email me *directly* ... this is an mTCP
question,
Hi - I'm the author of mTCP. mTCP is shipped with FreeDOS but it is an
independent project.
Please check the PDF, specifically the section on debugging. I'd like to
see a trace from your system when you are using a bridged Ethernet
connection. Use PING (the one that comes with mTCP), but
Yes, it seems to be functioning normally now. The next time I see a 5xx
type error I'll know not to try to debug it. ;-0
If the wiki is generally fast enough I wouldn't change anything. My
opinion was formed last night after one long session with it when it was
clearly struggling. If that is
wrote:
> Hi Mike!
>
> I can create an account for you.
>
> I'll create your account today and send it to you.
>
>
> On Wed, May 5, 2021, 11:14 PM Michael Brutman
> wrote:
>
>> I've noticed some inaccuracies on the FreeDOS networking wiki pages. How
>> does on
I've noticed some inaccuracies on the FreeDOS networking wiki pages. How
does one get an account so that edits can be made?
-Mike
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
This is an old trick and I have it documented in the mTCP PDF
documentation. Here is a quick overview.
If you have a printer that is network enabled and it speaks Postscript,
PCL, Epson ESC P2, or plain text then you can "print to a file" under DOS
and then use Netcat to send the file to your
Jerome Shidel wrote:
> Hello Michael,
>
> On Apr 10, 2021, at 3:20 PM, Michael Brutman
> wrote:
>
> Gents (Jerome and Rugxulo in particular) ...
>
> As per
> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/fdnet.html
> FDNET
Gents (Jerome and Rugxulo in particular) ...
As per
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/fdnet.html
FDNET is being distributed under GPL V2. However, it includes mTCP source
code which is licensed under GPL V3. As per
One important note - buyer beware.
Most of these are open source projects. And in a lot of cases people are
taking the designs and not providing credit to the original designers, or
making design changes that the original designers have quality concerns
about. Monotech was one of those.
The retrocomputing crowd has a lot of these projects now, and they
generally work. Most are based on open source designs so the quality will
vary from vendor to vendor.
The 8 bit IDE cards for example are based on a project called XT-IDE that I
was part of back in 2008/2009. (See the genesis of
Thanks for the dictionary definition, but I think you missed the point
here. mTCP != WATTCP, and I have no interest in WATTCP. WATTCP is a
library and a set of programs from many contributors while mTCP is all my
work. Being compatible with something that I originally had no knowledge
of an no
"Exotic" is a strange word ... WATTCP uses its own configuration file,
mTCP uses its own configuration file. I knew about Trumpet when I started
mTCP but not WATTCP. After WATTCP came to my attentioned I looked at it
and determined that I would continue to do my own thing.
You did write
I have a real simple solution ... Test more or repackage things without
altering them so that more testing is not needed.
My UPXed binaries are almost the same size and don't have that horrible
side effect. That's because I recognize the value of testing on a variety
of targets and I accept
Rugxulo,
Your thickness amazes me at times.
I provided a UPXed version of all of the mTCP programs back in 2013. It
works just fine, even on the slowest 4.77 8088 machine that I own. I'm
objecting to your blindly re UPXing it in such a way that the executable
takes 21x longer to load on the
Disclaimer: I understand that once I release something into the wild, there
is not much I can do about it.
I see two problems with the two included mTCP programs:
1. I took great care to write user documentation for my programs and the
DHCP.TXT and FTP.TXT files should be included with the
fear mTCP will get no traction if it
> ignores the more interesting 32-bit projects. ;)
>
> cheers,
> Mateusz
>
>
>
>
> On 01/09/2015 17:45, Michael Brutman wrote:
> > The current memory requirement is a function of your design, which I
> > think could be im
The current memory requirement is a function of your design, which I think
could be improved. Disk based data structures are not that difficult to
implement.
I have a PCjr with a 20GB Maxtor drive on it, of which 600MB is in use.
There are lots of 8086 and 80286 class machines with larger than
Rugxulo - I'm pretty sure that John was using the FTP server on his
machine, not the FTP client. The FTP server has no shell to dos
capability - that is only really needed/useful in the client.
For the most part it is safe to do; just don't take too long. In general
FTP servers are not sending
There is Netcat for DOS ... http://www.freedos.org/wiki/index.php/Netcat
And it can easily be used for printers that listen for raw connections on
port 9100.
--
___
From the comments page:
Unfortunately the FreeDOS community wants nothing to do with this project
as the goals cannot not be mutually met i will be removing the project and
exiting the development. sorry.
As far as I can tell, the Kickstarter project was launched without any
consultation from
The conversation is getting silly.
Sony got hacked. Like many large corporations, they are very concerned
about threats from outside. But once an intruder is inside, every door in
the building was basically found to be unlocked. Good security is layered
security - getting in the front door
That approach is faking it but it works and it sidesteps the questions
about wireless drivers, encryption, etc.
On Oct 6, 2014 9:52 AM, Matej Horvat matej.hor...@guest.arnes.si wrote:
This might be a good solution for wireless networking in DOS:
I don't want to brag too much, but M2WAT shows the absolute brilliance
of separating the DHCP process from the programs. ;-0 The mTCP programs
do not know or care about DHCP; they behave the same whether they have a
static IP address or a DHCP obtained one. M2WAT helps the WATTCP
programs
The expiring lease problem is irritating. My answer to that is have
people choose reasonable lease times and to run DHCP before doing
something that might run a while. Reasonable generally means at least
8 hours ...
If 8 hours is too long a nice work around is to configure the DHCP
server
On 9/1/2014 12:30 PM, Tom Ehlert wrote:
any good reason mTCP and DHCP can't update/use WATTCP.directly ?
imho there should be a *single* network configuration file, used by
*all* network stuff on the machine.
changing mTCP to understand WATTCP.CFG is trivial. (WATTCP.CFG has
been around for
On 8/31/2014 1:36 PM, Rugxulo wrote:
Hi,
On Sat, Aug 30, 2014 at 10:10 PM, Michael Brutman mbbrut...@brutman.com
wrote:
It pains me to see this much effort going into what should be a small
utility that takes the relevant mTCP obtained network parameters and
writes them into the WATTCP
It pains me to see this much effort going into what should be a small
utility that takes the relevant mTCP obtained network parameters and
writes them into the WATTCP file. There are 15 invocations of the
mt.exe program in that script.
I suggest that somebody write a small program that takes
David Dunfield has a utility called DHCP that will work with both mTCP
and WATTCP. I've not tried it, but David is well known in
vintage-computer circles and his software is supposed to be pretty good.
http://www.classiccmp.org/dunfield/dos/index.htm
Mike
I'll have to install those clients and try them. But it is most likely to be
something specific about them.
Anonymous users can't delete what they (or anybody else) upload. So that was
expected behavior.
Mike
escape esc...@front.ru wrote:
Works with Filezilla/Linux, lukemftp, ncftp, but
It's DOS so the filename was in error, but it should have aborted the data
transfer fully. I'll look into that after work - for now stick to 8.3 style
filenames.
Single Stage to Orbit alex.bu...@munted.org.uk wrote:
On Thu, 2011-09-29 at 08:37 -0500, Michael B. Brutman wrote:
I have made a
Crisis averted. :-)
-Mike
Robert Riebisch r...@bttr-software.de wrote:
Dear all,
You have probably noticed, that I have received a lot of public feedback
(plus a few private mails) on my announcement to close this forum.
Thanks for that! I didn't know, that this forum is such an important
58 matches
Mail list logo
