Jack,
I love a good rant as much as anybody, but some context is needed.
PCI was desperately needed by server class hardware. The ISA bus and
the extensions to the ISA bus were failing for several reasons:
- Inability to share interrupt lines
- Three fragmented standards (ISA, VL, and EISA)
Jack,
There are so many inaccuracies and distortions in the reply that you
sent, I'm going to assume you are just irritated or in a bad mood.
The world moves on ... it doesn't make sense to support existing
standards forever. You can have eternal support, or affordable prices,
but not both.
Things have been quiet on the list lately, so I feel compelled to
generate some noise ...
A new version of mTCP is available at http://www.brutman.com/mTCP . The
notable changes are:
- IRCjr now supports multiple sessions using virtual windows.
- A high contrast screen mode for IRCjr; useful
My advice ...
Your problem reports are confusing. You say that something is not
working, but it had been working before. If that is the case, what are
you changing? If you can't remember what you changed then it is time to
slow down and take some notes.
The general method for getting a
I'm not a Lynx user so forgive my ignorance .. but are you using the
version supplied by Fred C. Macall? In the past he has been very good
about supporting DosLynx for other people.
The output from the mTCP DHCP client is probably not in a form directly
usable by the WATTCP apps. You are
The mTCP DHCP client writes output to STDOUT and to the MTCPCFG file,
which is pointed to by an environment variable. It's a simple matter of
programming/scripting to convert the output from either one into
something that looks like a static WATTCP configuration. I've tested my
DHCP client
I had seen the original suggestion to use CTTY to redirect the console
to a serial port but
I had seen the original question on how to redirect DOS to use the
serial port and I probably should have chipped in then, but now you know
the limitations of CTTY.
CTTY to a serial port only works
On 1/15/2011 10:23 AM, Ulrich Hansen wrote:
The new ftpsrv app from mTCP works, but at least on my system seems to
have problems with showing correct DOS paths. For instance it shows
c:\ as c:/\. So f.i. creating new directories in filezilla doesn't
work without manual correction.
regards
this problem.
Regards,
Mike
On 1/15/2011 4:33 PM, Ulrich Hansen wrote:
Am 15.01.2011 18:10, schrieb Michael B. Brutman:
On 1/15/2011 10:23 AM, Ulrich Hansen wrote:
The new ftpsrv app from mTCP works, but at least on my system seems to
have problems with showing correct DOS paths. For instance it shows
Are there any FreeDOS users using a PCjr?
I suspect that except for the weird memory hole that the video hardware
creates and the use of NMI for keyboard handling, everything else should
work pretty well. But I'd like to hear from somebody who knows.
Regards,
Mike
I have posted the latest and greatest code (again) at
http://www.brutman.com/mTCP . This version has some minor bug fixes and
a new FTP server application.
Besides downloading it from the link above, for a limited time you can
get it using FTP directly from the PCjr that I do my testing on.
On 12/21/2010 8:54 AM, dos386 wrote:
AFAIK the inline ASM is more painful in WATCOM than in Boreland C or
CC386 compilers (I ever tested the latter one only). The are also
pre-brewn int86() int386() and maybe more functions to fire the INT
instruction but don't ask me how they exactly work.
A new version of mTCP is available in the usual place:
http://www.brutman.com/mTCP .
If you are on an older clone machine and you have not been able to make
the larger apps run correctly, then you want this version. The Watcom
compiler runtime that I am using now was incorrectly flagging some
Geraldo Netto wrote:
Hi Michael/All,
Would be possible to release it as gpl or any other oss license?
(i guess someone already asked for it, but anyway...)
Kind Regards and Best Wishes,
Geraldo
Geraldo,
It is in the works. My employer has to review the code and bless it
first to protect
I just posted the latest and greatest code at
http://www.brutman.com/mTCP . This version supports IP fragments, which
might help with some of the stranger network and gateway setups out there.
Another neat feature that I should have done a while ago is command line
editing for FTP, including
Mateusz Viste wrote:
I believe you wanted to say frame instead of packet and 64 instead of
60? As far as I know, an IP packet can transport no payload, which gives a
20-bytes packet in result. :-P
The limitation is about the minimum size of the frame, which (on ethernet) is
of 64 bytes, to
Hi,
Just a quick note - I've posted a new version of mTCP at
http://www.brutman.com/mTCP .
The biggest change is a bug fix. Some packet drivers refuse to send
packets less than 60 bytes in size while many older packet drivers don't
care. Technically speaking, a packet less than 60 bytes in
dos386 wrote:
to me it's still unclear what it is supposed to do and whether it
works in (Free-)DOS at all, considering the shots you posted ;-
It is a LAN status monitor. It monitors the status of your LAN. ;-0
--
101 - 118 of 118 matches
Mail list logo
