> >> There is a difference between the �i� project and the UZIX TCP/IP: The
> 2nd works nicely nowadays... =)
> >You forgot to state that project 'i' has to be programmed from scratch.
> >For UZIX, only a few adaptions had to be made, but the sources were already
> >there.

        BULLSHIT!!!!!!!!!
        I had to read the entire chapters of Tannaunbaum's Network book, I
had to read all those RFCs, I had to program it from scratch, find ideas
and sources from the net for problems I couln't fix and things I couldn't
understand, understand the protocols and sources and ideas. Now you say
that "just a few adaptions had to be made"???? It took me three entire
weeks to write the entire stack (and it's not complete yet!) and get a
working alpha version. I lost two weekends, I lost lunchs and dinners, I
didn't sleep until I got finished it. Buggy? Beta? Incomplete? Well, at
least it works, and was the first serious (and working) TCP/IP project for
MSX I saw.
        Multitasking? Multitasking is not necessary. I could make a
monotask version of UZIX TCP/IP stack. But I don't want to do it. I think
it's more interesting a UNIX version of the stack than a DOS version. If
you want a DOS TCP/IP stack, finish yours.

> >I won't stop my project (not project 'i', btw) just because there is an
> > UZIX TCP/IP stack

        Nobody said that.

> for several reasons: - it doesn't support my Sunrise RS232

        As I said: send me the info I need and I'll make a driver for
Sunrise RS232 only for you... It's a stupid excuse.

> >it doesn't run under the entrusted Dos environment
> > - it can't use the HD, -

        Another stupid excuses.
        When your HD dies, you will stop using your MSX?

> >I think Unix programs like mail or telnet or ftp are a bit too simple, I
> >prefer to have a (G)UI.

        GUI is for those whose IQ is near to 0.

> What I made up in this discussion: A tcp/ip program for MSX exists. It was
> made by converting C code to a running UZIX-program.

        Wrong. It was created for running on UZIX.

> Some people don't like the use of uzix, because it doesn't support HD.

        ONE person doesn't like UZIX because it doesn't support HD YET.
        ^^^^^^^^^^                                                 ^^^

> And some RS232-interfaces are not supported.

        Any standard RS232 interface with BIOS works with UZIX TCP/IP.
        Just the Sunrise RS232 doesn't work, since it was designed to run
only with Erix Fossil Driver.
        If I put my hands on info about acessing Sunrise RS232, I will 
made a damn driver for this, so nobody will say "It doesn't work with
Sunrise RS232, so I will not use".

> Now I am wondering: Why can't the C-code be adapted to MSX-compatible
> C-sources so that it'll run under DOS(2) ?

        Because it's MY code, because I made it for UZIX, because it uses
UZIX multitasking facilities, because I will not waste time porting it to
a monotasking system such MSXDOS(2). When the source code be release,
anyone will be able to port it to any machine or OS, including HP48G,
MSXDOS1, ZX Spectrum, etc.
 
> When finished this, a (G)UI should be 'a piece of cake' for experienced
> MSX-coders i guess.

        It's also a 'piece of cake' also for U*IX. Just do it.


Adriano Camargo Rodrigues da Cunha               ([EMAIL PROTECTED])
Engenharia de Computacao - UNICAMP   
http://www.adrpage.cjb.net           http://if.you.dont.like.msx.usuck.com

* Windows9X, preemptive multitask: does nothing while doesn't work. *


****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
 The MSX faq: http://www.faq.msxnet.org/
 The MSX newsgroup: comp.sys.msx
 The MSX IRC channel: #MSX on Undernet
****

Reply via email to