Richard Brooklyn said,
>> but I don't understand why you'd want to change
>> that setting dependent on the TCP stack you use.
> I'll tell you why, Because Miami HATES AT&F, it goes crazy man! I
> didn't make up that string anyhow, I just picked a modem (I can't
> remember which one) and I worked, so there!
Miami works fine with AT&F\r here.
>> &D2 drops carrier on loss of connection to the computer (i.e.
>> crash/reset), &D0 keeps the connection.
> Yep, sure does. It's better to have this setting that way when voyager
> runs out of memory and crashes (like it always does on my system!) you
> don't run up a bill after you forget about the modem.
So why do you use &D0 with Miami? Depending on the time of day and the
time it takes your Amiga to reboot, it's usually cheaper to leave the
connection up while rebooting.
An even better solution is to eliminate the cause of the crashes.
Neil
--
Neil Bothwick - New Media Editor, Amiga Active Magazine
Connected via Wirenet - http://www.wire.net.uk
The UK's first Amiga-only internet access provider
--
Procedure: (n.) a method of performing a program sub-task in an inefficient
way by extensively using the stack instead of a GOTO.