@All

Get ezTCP 0.1 here:

https://morph.zone/modules/mydownloads/singlefile.php?lid=334

@Sonic
Thanx for making this early test release possible in such short time.

At least one test failed - Antibike reported that resolving names via DNS doesn't work.
This doesn't mean ezTCP is completely unusable, you can continue testing, bencharking, bughunting, etc. Also i would like to receive more reports.
Just one advice: for emergency cases, if DNS fails for you too, to be able to enter at least morph.zone and #MorphOS IRC add the following to your s:netdb/hosts file:
--- cut ---
38.99.64.210 irc.freenode.net
69.13.225.0 morph.zone
--- cut ---
After this you'll at least won't stay alone deaf and dumb on the network and will be able to tell us something.

http://nogfx.free.fr/morphos/google_eztcp.png :)

Leo.

Sonic! Wow great work, I got on the net with a MOS native stack. I can say I have to enter in the sirect IP for sites as well. Great work again though, its starting to look like we will have a nice working stack soon.

Want to tell good news. I found the resolver bug! It was improper linking and improper API calling with wrong library base. If you look carefully you'll likely note that every DNS query generates that "crit" message in the syslog which i asked not to pay attention to. But this is the clue.
Note for programmers: never omit function prototypes or at some point you'll get into hard-to-find trouble!

[ Edited by Sonic on 2005/9/14 16:32 ]

This is top-notch commitment! Amazing!
Now, time for a question: Are there any talented developers not living in eastern Europe?

Sonic you just keep giving us great news over and over! I cant wait for the final release. It seems eastern europe does have quite a few great ones doesnt it?

I can say the world would be a better place if we live together like all of us do on this site and in this communiety.

careful with eastern europe ! biggest paert of Russia is in Asia :)

nice work Sonic, nice ? not nice ! amazing ! astounding !
don't forget to rest !!!

Great, I look forward to checkign it really soon here day or two ill let you know how it works on a proxy network.

here it says it can't find "bsdsocket.library"! Isn't it a bit strange!?

I've uploaded the second release. Unfortunately not everything is fixed, several original problems were discovered, but there is a chance that DNS works now. Please report.
2 micky060: Yes, strange. Try running a kernel from the command prompt, i think it tells you about some error there. Startnet just sends the output to NIL:
Next fixes are expected on monday or tuesday, sorry, saturday is my wife's birthday, i need to do some preparations at home...

Hi Sonic, yesterday I reached to solve the problem (thx scf), editing the solv.conf file.. ezTCP went online! Obiosuly without DNS is few usable.
Now I would like to try the 0.2. Where is it? I can'it find the link.
Thx.

You can find ezTCP v0.2 under the original link (as of now )

I am online with it :)

But dns still does not work for me
everything resolves to 64.49.213.239


@micky060
when do you get the error? Maybe its because
the version of bsdsocket.library is 3.x and not 4.x.

If you just want to surf the web without dns use a proxy (you have to use its IP for the settings of course)

[ Edited by weiseb on 2005/9/15 11:02 ]

What better birthday gift then a MOS native
TCPIP stack with DHCP enabled ???! :P

Gr,
Felix.

We are already investigated the new DNS issue. The workaround is to remove (or comment out) all DOMAIN entries in the resolv.conf. Antibike discovered this effect. It will be definitely fixed soon, now i exactly know where to look for the bug.

@Sonic

it's great to read your progress reports here. lots of thanks

thanks for the effort!
Now I'm sufing with it.
everyting's quite fast, except for morphzone...

What speed can be expected in 100Mbit LAN?

There were requests to bump bsdsocket.library version to v4. I've studied Miami's and AmiTCP's SDKs and there is only one thing added - socket events.
v0.3's bsdsocket will have v4 then. It will report "Function not implemented" on this function call in order to avoid crashes. Also it will report on unknown SocketBaseTags and unknown IOCTLs. This will help to figure out what software need what.
Also i expect to clean up known bugs list at all.

it sounds so easy with you Sonic. Once this TCP/IP stack will be done, why not joining the amizilla team to speed up the whole stuff ? hehe

Quote:

Heh, may be... Or start something new like Firewire... BTW, anyone knows what is the status of AmiWire/MorphWire by DiscreetFX?

After some testing here is new, re-summarized buglist:
1. Samba doesn't work - will be investigated, not really clear problem
2. Applications utilizing file (socket) descriptor creation callback will crash because calling conventions are wrong - found, will be fixed.
3. Resolving via DNS works only if no DOMAIN lines are specified in the resolv.conf - will be investigated, unclear, but probably closely relates to (1) - netdb gets screwed up in memory.
4. Wrong Ctrl-C handling in the DNS resolver (see download description for details) - found, will be fixed.
5. Ping tool can leave bsdsocket.library opened preventing ezTCP from quitting - found, will be fixed.
6. bsdsocket.library has version number 3 so there are non-working applications which ask for v4 - will be updated to 4, but new features will not be implemented, errors will be generated if some application will attempt to use them and warnings will be printed in the log; so some applications will continue not to work.

Quote:

no idea but it should be quite easy to contact them.

Sonic: Great work again, your moving along at a great speed. I would think in two months you will have a fine application to give everyone.

About firewire, I've looked into it a lot and from what I have found its not an open standard. The stuff in linux isnt that great and is more or less hacks. The real SDK and docs you need cost a lot of money to get.