Am 01.09.2014 um 21:51 schrieb Michael Brutman :
> 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
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 arou
Hi,
> 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
>
On Mon, Sep 1, 2014 at 2:44 PM, Mateusz Viste wrote:
> DHCP separation can be nice, but it has also its downsides.
>
> It's definitely a nice choice because it makes programs a bit smaller.
> However, a problem might appear in the (unlikely?) situation where a
> user plays with a network-enabled p
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
DHCP separation can be nice, but it has also its downsides.
It's definitely a nice choice because it makes programs a bit smaller.
However, a problem might appear in the (unlikely?) situation where a
user plays with a network-enabled program while his lease expires.
Say, my DHCP router provides
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 be
> Am 01.09.2014 um 17:05 schrieb Ulrich :
>
> Mike, what do you think - would it be a good idea to ship it with your mTCP
> package?
If this is Ok with Dave, I should have written of course.
--
Slashdot TV.
Video for
Hi
Thanks a lot, Dave, for the program. I was eager to try it, so I downloaded
OpenWatcom and compiled my first DOS program :-))
Had some time, while my son listened to some audiobook called "Mama Muh". :-)
I copied the program lines to a file m2wat.c and used these settings:
wcc m2wat /ms
wli
On 8/31/2014 1:36 PM, Rugxulo wrote:
> Hi,
>
> On Sat, Aug 30, 2014 at 10:10 PM, Michael Brutman
> 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 file. There ar
>I suggest that somebody write a small program that takes the current
>>configuration parameters from the mTCP configuration file and updates a
>WATTCP >configuration file. It should not be a terribly complicated program -
>you just >have to do some light string processing.
Here' you go:
Hi,
On Sat, Aug 30, 2014 at 10:10 PM, Michael Brutman 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 file. There are 15 invocations of the
> mt.exe program in th
tuff in "otherwat.cfg" ...
Most (likely all) of that other stuff is not needed anyway.
Dave
-Original Message-
From: Ulrich
To: Discussion and general questions about FreeDOS.
Sent: Sun, Aug 31, 2014 12:15 pm
Subject: Re: [Freedos-user] VirtualBox and FTP
I am sorr
Am 31.08.2014 um 05:31 schrieb dmccunney :
> it looks like
>
> mt -b- -c -n wattcp.cfg #ipaddr = my_ip= #netmask = netmask= #gateway
> = gateway= #nameserver = nameserver= #hostname = hostname=
>
> would do the same thing.
Hmm. Doesn't. Scrambles wattcp.cfg. :-(
But was a good idea.
--
On Sat, Aug 30, 2014 at 11:10 PM, Michael Brutman 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 file. There are 15 invocations of the
> mt.exe program in that sc
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
I am sorry, there were some errors in my previous post:
The batchfile has to be called like this in AUTOEXEC.BAT, right after the line
DHCP:
DHCP
CALL C:\FDOS\M2WAT.BAT
Otherwise it wouldn't return to AUTOEXEC.BAT.
There were also errors in the batchfile itself. I made some changes, now it
se
Am 30.08.2014 um 23:56 schrieb Mateusz Viste :
> Thanks for sharing!
> I might have missed something, but why haven't you used the DHCP.COM tool
> from Dave Dunfield, instead of all the sed-like magic? Just curious.
The main reason is that (unfortunately) DHCP.COM doesn't seem to be free
softw
Hi Ulrich,
Thanks for sharing!
I might have missed something, but why haven't you used the DHCP.COM tool from
Dave Dunfield, instead of all the sed-like magic? Just curious.
Mateusz
On August 30, 2014 11:47:35 PM GMT+02:00, Ulrich wrote:
>
>I think I found a solution.
>
>The problem was:
I think I found a solution.
The problem was:
When I choose "NAT" as network type for a VirtualBox FreeDOS 1.1 guest, only
mTCP DHCP.EXE is able to get the correct IP addresses from the DHCP server
provided by VirtualBox. WATTCP applications fail to get their IPs from that
DHCP server.
The i
.cfg #netmask = netmask=
>> mt -b- -c -n wattcp.cfg #gateway = gateway=
>> mt -b- -c -n wattcp.cfg #nameserver = nameserver=
>> mt -b- -c -n wattcp.cfg #hostname = hostname=
>>
>>
>> Step 3 Run it after MTCP DHCP.
>>
>> Dave
>>
>>
>
Hello, Tom.
Previously, we use ODI stack (Novell) with NIC autodetection (net.bat):
https://github.com/ya-mouse/dos-net-odi/
It is already contains a few drivers. It's easy to add more.
I hope iPXE would have packet's driver support soon.
29.08.2014, 14:58, "Tom Ehlert" :
>> We use undipd
> We use undipd driver:
> http://www.shikadi.net/network/files/undi2pd/undipd.com
this is great - if and only if booted from PXE.
Tom
> It is widely tested on the newest hardware: notebooks, desktops and servers.
> 28.08.2014, 23:14, "Rugxulo" :
>> Hi,
>>
>> On Mon, Aug 25, 2014 at 10:59
Hello.
We use OpenWatcom compiled version of Watt32:
https://github.com/ya-mouse/dos-utils
This repo contains watt32-version of curl also.
We use undipd driver:
http://www.shikadi.net/network/files/undi2pd/undipd.com
It is widely tested on the newest hardware: notebooks, desktops and
Hi,
On Mon, Aug 25, 2014 at 10:59 PM, Mateusz Viste wrote:
>
> Might be that the DHCP implementation of VirtualBox is incompatible with
> the DHCP client embedded in Watt32... A PCAP capture might show more,
> although not sure if there is any point, since watt32 probably won't be
> updated/fixed
iginal Message-
> From: Michael Brutman
> To: Discussion and general questions about FreeDOS.
>
> Sent: Tue, Aug 26, 2014 10:53 am
> Subject: Re: [Freedos-user] VirtualBox and FTP
>
>
> David Dunfield has a utility called DHCP that will work with both mTCP
about FreeDOS.
Sent: Tue, Aug 26, 2014 10:53 am
Subject: Re: [Freedos-user] VirtualBox and FTP
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
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
--
>mTCP vs wattcp.cfg - I agree this would be awesome if mTCP could read/write
>>WatTCP config files for backward compatibility :)
Step 1: Install minitrue on your PC. mt.exe ... google it.
Step 2: Create a batch file called "M2WAT.BAT"
Put this stuff in the batch file:
@echo off
rem con
Hi,
Might be that the DHCP implementation of VirtualBox is incompatible with
the DHCP client embedded in Watt32... A PCAP capture might show more,
although not sure if there is any point, since watt32 probably won't be
updated/fixed any time soon.
About some programs needing a fixed IP: yes, t
Am 22.08.2014 um 00:47 schrieb Ulrich :
> As the guest is connected through NAT, he can also do network operations like
> "FDNPKG update".
I just tried that and "FDNPKG update" still doesn't work. This seems to be
caused by WATTCP. WATTCP.CFG has the line
my_ip = DHCP
so it should get the s
>Just use passive mode
>connections
>and you'll be fine.
It's exactly the other way around ;)
Ulrich has its server behind a masquerading PAT, not the client. So ACTIVE mode
is what should work, IF its ftp client is smart enough to ignore the IP
presented by the server in the control channel
Am 21.08.2014 um 22:47 schrieb Michael B. Brutman :
> I am a little late in responding; moving an entire house of belongings
> and children is not fun.
Wow, best wishes! We are looking for a new house at the moment, so this is
something that might happen to our family too, sooner or later.
>
I am a little late in responding; moving an entire house of belongings
and children is not fun.
Mateusz provided a good explanation - it is "active" vs. "passive" mode
connections. Back 15 years ago before NAT was in widespread use all FTP
connections were "active." The client would initiate
Hi Mateusz,
Am 20.08.2014 um 08:23 schrieb Mateusz Viste :
> If your client is behind NAT, the ACTIVE mode will not work without
> special hacks, because the server won't be able to reach the client.
> If your server is behind NAT, then it's PASSIVE mode that won't work,
> because your server w
Hi,
FTP is a nasty protocol, that never should have existed in the first
place... But once it's done, it's impossible to get rid of it,
unfortunatly. The problem is that FTP is an out-of-band protocol,
meaning it separates data and control in two different channels (aka
connections). There are
Hi
I just tested a bit more what is possible with DOS networking and VirtualBox.
I always wondered why I need to choose "Bridged Adapter" in the guest network
settings to establish a FTP connection between host and guest. Because that
means the connection needs the physical router in my LAN.
37 matches
Mail list logo
