Hi,
On Sun, Oct 14, 2012 at 9:57 AM, Michael B. Brutman
wrote:
>
> Regarding the makefile errors - I do not compile in DOS. My preferred
> DOS machine is an 80386DX-40 and compiling using OpenWatcom crushes that
> machine. It is far more productive to work in Windows or Linux and
> cross compil
Hi,
On Sun, Oct 14, 2012 at 6:26 AM, Mateusz Viste wrote:
>
>> I saw this, but I can already tell some of it needs updating, e.g.
>> FreeDoom.
>
> I'm not a big expert on Doom, and available ports or forks today.. I
> think that I simply took the FD 1.0 package on this one. :)
I'm far from a Doo
>is the WatTCP program doing something anti-social like calling exit and >
>>killing the program outright?
WATTCP programs generally start by calling sock_init() Sock_init() will exit
the program if a packet driver is not found. If your program might have some
useful purpose without TCP/IP
I noted that FDNPKG is using WatTCP - I don't see that as a problem.
While I prefer mTCP and I think it has many advantages (speed, size, bug
fixes, etc.) WatTCP works well enough and people are comfortable with
it. I also have a slight bias, so I am trying to be objective. ; - 0
The "offlin
Hello,
On 10/14/2012 12:22 PM, Bernd Blaauw wrote:
> From what I've noticed it's a big binary, likely due to including
> wattcp and perhaps also a decompressor.
Indeed, FDNPKG includes everything - a UNZIP decompressor, the WatTCP
stack, and a simple HTTP downloader.
> I've not experimented w
Hello,
On 10/14/2012 12:31 AM, Rugxulo wrote:
> I haven't looked closely yet, curious what it's written in (presumably C).
Yes, ANSI C89, compiled with DJGPP.
> Do you have packet driver emulation enabled in DOSEMU? I never did
> understand how to get that working (to say the least). Hence my on
Op 14-10-2012 0:31, Rugxulo schreef:
> There are some people who seriously wanted such a thing for FreeDOS,
> e.g. some random dude on OS News when FD 1.1 was announced. So I guess
> he'll finally be glad, heh.
From what I've noticed it's a big binary, likely due to including
wattcp and perhaps