The next mTCP is available, with HTGet now included:
http://code.google.com/p/mtcp/
There are two versions of the pre-compiled binaries to choose from -
standard and "-upx". The "-upx" version binaries are compressed with a
program called UPX that decompresses the programs at load time. You wi
On 7/26/2011 12:09 PM, Bernd Blaauw wrote:
> HTGET supporting common HTTP URL/URI syntax
> (http://server.domain.extension/path/file.ext) is good enough already.
> your -userpass seems to indicate no complete syntax is possible, and
> portnumbers either assumed 80 or not changeable.
>
> http://us
On 7/25/2011 7:46 PM, Mike Eriksen wrote:
> Maybe a stupid idea, but couldn't HTGet just call you FTP client in
> case of a FTP-URL and let that one handle the download and keep the
> rest inside HTGet?
>
> Mike
There is no simple "call" ... the FTP client is a stand-alone program.
In the event
On 7/25/2011 6:58 PM, Rugxulo wrote:
> I assume this would work? ;-)
> htget -o wgetx.zip
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/pkgs/wgetx.zip
>
Worked just fine ... Response code 200 from the server, 510347 bytes
received in a correct/verified ZIP file.
M
On 7/25/2011 6:52 PM, Bernd Blaauw wrote:
> Thanks for creating this. It means you're pretty close to a basic WGET,
> and also reminds me why I never liked HTGET: no support for FTP and
> REDIRECT/MOVED. URL parsing seems fine. Not sure if/how HTGET would
> respond to HTTPS://
>
> Example URL (resp
I have an early version of HTGet ready that I would like to get some
more testing on before it becomes part of mTCP. It is available here:
http://www.brutman.com/mTCP/htget.zip
HTGet lets you download a file (or whatever content) from an HTTP
server. Just put the URL on the command line
On 6/22/2011 8:10 PM, Mike Eriksen wrote:
> If SNTP works anyway like in Linux/UNIX then the computer takes its
> hardware clock as UTC. If the hardware clock is offset to local time
> it will be misinterpreted. The poor computer doesn't have any
> conception of UTC by itself, it only knows its har
On 6/22/2011 10:49 PM, Marcos Favero Florence de Barros wrote:
> Hi Mike,
>
> I shouldn't even have called this thing a bug. It is, at most, an
> issue of semantics. Because the SNTC screen message used the word
> "timezone", I thought it would write UTC+3.
>
> I'm probably right on that point (jus
On 6/22/2011 9:15 AM, Marcos Favero Florence de Barros wrote:
> Hi Mike,
>
> Thanks for mTCP!
>
> I experimented with it yesterday for the first time, and it took
> me just 15 minutes to get started, in spite of my near complete
> lack of internet experience (except of course web browsers and
> ema
On 6/2/2011 1:42 AM, Willi Wasser wrote:
>> Some developers may not be too happy
>> about the license choice, especially
>> those who would like to grab your code
>> and try to make money from it by making
>> it part of an unfree software.
> Let's be serious! Is there still a market for any kind of
On 6/1/2011 5:30 PM, Ulrich Hansen wrote:
> Actually this is not really news but just a wish from my side. The
> discussion what*s part of FreeDOS 1.1 takes place since some time at
> freedos-devel. I think the developers decide, while we users should
> publish our expectations and wishes.
>
> So I
On 5/31/2011 6:55 AM, Ulrich Hansen wrote:
> I think users will like that your server takes good care of the data
> and doesn't loose or damage them. This is an important thing. On the
> other hand, most people will connect to the FTP server from more
> popular operating systems than DOS. So
On 5/31/2011 2:23 AM, Marcos Favero Florence de Barros wrote:
> Hi Ulrich, Michael, others,
>> Now that mTCP is Free Software, I think the next version of
>> FreeDOS should focus on getting basic networking abilities.
> That's wonderful news :-)
>
> Are you also contemplating networks for sharing f
Ulrich,
Sorry about the delay here - my email stacks up way too quickly and I
miss some at times. Comments are inline:
On 5/25/2011 9:54 AM, Ulrich Hansen wrote:
> Hi Michael,
>
> thanks a lot! I tried the ftpsrv app with Filezilla and it works much
> better now (I missed the update before, so
On 5/28/2011 3:57 AM, Bernd Blaauw wrote:
> hi Michael, congratulations on possibly having the first GPL3 DOS program ^^
> I seem to recall you needing permission from your employer to do this so
> thanks go out to them as well.
I think that honor was claimed already. I solved the permission prob
On 5/27/2011 6:48 PM, Single Stage to Orbit wrote:
> On Fri, 2011-05-27 at 16:49 -0500, Michael B. Brutman wrote:
>
>> I released mTCP as open source today: http://code.google.com/p/mtcp/
> Congratulations on releasing the sources, just in time for a project I
> am considering
I released mTCP as open source today: http://code.google.com/p/mtcp/
Enjoy!
Mike
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you ge
Come and get it! http://www.brutman.com/mTCP/
In this version:
- CTCP support in IRCjr (you can do "/me" now!)
- DHCP client enhanced to do multiple retries and give better error messages
- Fixed a parsing error in the FTP server
- Telnet can now work with servers that do not accurately interpre
On 4/10/2011 11:35 PM, Jack wrote:
> Also, I do not know you and you do not know me, so WHO ARE YOU to assume
> I am "irritated or in a bad mood"?!! Are you in fact a COMMUNIST?? I
> seem to recall THEY used to "operate" via trying to beat-DOWN opposition
> with such unqualified INSULTS as you
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.
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)
-
On 4/10/2011 12:08 PM, escape wrote:
> Please get it right. I'm not arguing against support of new
> technologies. But now it's often when manufacturers trying to disguise
> cost cutting and marketing rubbish as prominent new technology.
>
> Look at monitors as an example. Getting 16:10 aspect alon
On 4/10/2011 5:20 AM, escape wrote:
> Vote with your wallet. I'm personally not buying any 4k drives nor for
> myself nor for companies I'm working for. When you need more than 2Tb of
> space you always can add another 2Tb drive instead of replacing old
> drive with bigger (3Tb) one.
I think that
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 DHC
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 f
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 for
On 2/23/2011 2:47 AM, teo gum wrote:
> Please explain me how to setup an IRC client under DOS.
> Supposed that an internet connection already run.
> A sample config should be the best (I'm a humanitarian a Slavic
> filologist :)
> - with an explanation where to put target server and where somethin
ing lftp) have
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 proble
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.
>
> reg
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.
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
---
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
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 a
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
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 si
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 - 140 of 140 matches
Mail list logo
