Since starting to use MorphOS 1.4.5 I managed to set up Miami
Deluxe and could get about 4000 cps from my dial up ISP through
AWeb.

It's not a perfect setup, I've had many strange hangs, AWeb not
finishing downloading some files, giving up on some. AWeb suddenly
decides it's not going to show any pictures sometimes. Some
problems with YAM too, very slow to connect etc; so in general
things were about usable but I really want to solve these problems.

Now I am regularly updating Ambient from CVS and over the last month or two I notice that online connections have got really bad.
Long pauses, Miami makes itself offline for no reason, etc.
It's unusable now. I also noticed that I can't start Miami sometimes,
I get an error window with "A TCP/IP stack is already running".

The only thing I have changed is Ambient. So now I am wondering,
how can I find the cause of the problem and fix it ? Possibly Ambient
is using memory expected by the virtual bsdsocket.library but I don't
know enough about these things.

What tools can I use to debug this situation ?

many thanks

koan

From Ambient menu select "Exchange..."

Thats a tool that can show you a few programs
that are running (commodities)
When Miami complains there is a stack running
that means exactly that.

Perhaps you run MOSNet, Genesi or old Miami
at the same time?

So have a look it there is MOSNet or Genesi
or Miami listed in Exchange-Window when the
complain comes up ...

I have the same config (MOS 1.4.5, MiamiDX, MUI4 alpha and CVS Ambient updated daily) and have no problems. Miami works upto 7MB/s without any troubles.

@koan

about the slowdown, seen that your using dialup, probably is the debug output of MOS/AmbientCVS out of the serial port.

"I get an error window with "A TCP/IP stack is already running"."

check to don't have MosNET assigned with its own miami.library that could bangs with MiamiDX.

Having two of the same mcc's in sys:classes/mui and sys:morphos/classes/mui can give very strange problems in MorphOS.

koan,

as previously said, your problem is probably due to serial debug caused by ambient. ambient cvs versions are compiled with debug enabled and output quite a lot, enough to prevent your dialup link from working properly. With such a link, you'd better use ramdebug option at boot.

framiga,

about this "stack already running"...
Listers use usergroup.library to display user/group columns. The problem is that amitcp/mosnet can't start if disk-based usergroup.library was already opened before. Same for miami. But if you only use miami and didn't install mosnet/amitcp, there is no problem, because usergroup.library is created on-the-fly (like bsdsocket.library) so ambient can't open it before the stack is running.

Anyway this behaviour can probably be modified a bit, by only trying to open usergroup.library if a stack is detected.

Hello Fab

interesting.. thanks

i didn't know that listers uses usergroup.library. (i'm using Scalos btw)

Are you speaking about the latest AmbientCVS?

Yes, ambient uses it since 5th april 2006. :)

@all

Thanks for your replies.

I am only running Miami, I definitely don't have another TCP/IP
stack running.

I will try Fab's suggestion: I will make sure ramdebug
option is selected.

koan