On Sat, 04 Apr 2015 22:08:14 +0200, Rugxulo <[email protected]> wrote:

> Jim Hall will probably say, "That's what you get for not being
> free/libre in the first place". And he's probably right.

Not really. In case of the HX DOS extender, the problem is that the  
documentation does not say much about distribution (particularly source  
code).

 From HXRT.TXT:

"The HX DOS extender runtime is freeware and may be used for any purpose.  
Copyright Japheth 1996-2010. The HX runtime can be freely distributed with  
any application."

 From HXGUI.TXT:

"HXGUI is part of HX DOS extender. This extender is freeware and may be  
used for any purpose. The binaries found in HXGUI can be freely  
distributed with any application. Copyright Japheth 2005-2010.

The WSOCK32.DLL binary is written with the help of WatTCP/Watt-32. If you  
want to distribute WSOCK32.DLL, please read the copyright regarding WatTCP  
in Doc\WSOCK32.TXT."

 From HXSRC.TXT:

"The HX DOS extender is freeware. Copyright 1996-2010 Japheth."

On Sun, 05 Apr 2015 16:12:56 +0200, <[email protected]> wrote:

> Does anyone have a copy of the most (or nearly most) recent versions they
> could send me offline.  I would like to post a copy of the clearly
> redistributable files on my fdos site for others and update my copies.

I have a copy of the latest(?) work-in-progress source code of the HX DOS  
extender. I would like to mirror it on my site... what's the worst that  
could happen?

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to