JP> Thanks Russell. I knew you'd be the first to cheer when you

 JP> heard!



 RB>> I am very pleased that you could finally get a Courier. As

 RB>> you can see, they are a cut above the rest.



 JP> Certainly. However, a few people have had problems connecting

 JP> to it. Some are experiencing freezes and delays in drawing menus (I

 JP> did myself when I hooked up the M11F to the spare notebook), and



I would have thought that this problem is not YOUR modem. The Later

Sportsters and the 33600 Dynalinks (using the borrowed code of the

sportster in question) do have a freezing problem. Not Yours.



If it has happened to you personally, then I would suggest it has to be

software related, thought, I do faintly remember a problem that some

users had when using a Courier back in '94 with the first V.34 SDL,

with dialling into early Maestro VFc modems, where the modem would let

you connect and stay in for upto 4 minutes, then hang you up. It was

also very slow on redraws. The Sysop concerned was not cooperative at

all. He was using Remote Access for DOS in an OS/2 window, 3 x 28800

VFC nodes, while running 18 CD-Roms and a CD-Rom writer as well as 16

other sessions all a once.



 JP> more disturbing, one of my regular callers always loses

 JP> carrier whenever a message is displayed. He logs in, the system

 JP> checks his mail, and when he presses (Enter) to read his mail, he

 JP> is cut off. It's happened every time without fail. I'm at a loss to

 JP> understand why the displaying of a message would cause a sudden

 JP> disconnect.



Not running Remote Access for DOS in OS/2 are you;-)



 RB>> Have you had any 33600/33600 connects yet??



 JP> I have tested my Courier with a number of systems. I have a

 JP> downlink in Mudgee, a downlink in Melbourne and two points, one who

 JP> has a 33.6k modem (I'm not sure which brand -- not a Courier

 JP> though). So far all of my downlinks seem to be doing fine. I have

 JP> no way of knowing whether or not my connects were 33600 in both

 JP> directions.



Safe bet that if you get 33600 one way, then you are either on the

money, or within two steps of it...28800,31200.



 JP> David crashmailed me back the following morning and (according

 JP> to my mailer's log), he achieved 33600. He posted me the

 JP> diagnostics for that session. These report a different connect

 JP> speed altogether. I'll post the log snippet to you here if you like.



More often than not, your connect rates are different than the Diags.

This speed shifting seconds after a connect, is very useful.



 JP> Steven Andreson connected at 31200 yesterday, and from hat he

 JP> says, his phone line is shocking. He didnt experience any

 JP> difficulties while connected here.



 RB>> I would be interested in a dump of your best online stats

 RB>> when you are in the middle of your best connect. (To another

 RB>> Courier preferably)



 RB>> While online at 33600/33600, do +++



 JP> I called another BBS running a V.E the other day. Typing +++

 JP> had no effect at all. I did toggle the DIP switch to disable

 JP> carrier loss on +++.



The sysop at the other end has either changed his Escape character or

disabled the feature with either the dip switches or S2=225



 RB>> then ATi6i7i11y11 (with capture on of course) now ATO1 to

 RB>> return to

 JP> normal



 JP> I'll have to try that. Is there any other way to drop to

 JP> command mode?



Not that I know of.... the other end has to let you.



 RB>> I want to check your S/N, near & far echo and signal

 RB>> strengths. If you

 JP> are

 RB>> using the same lines as you used too ( with the Dynalink,

 RB>> Simplemodem,

 JP> and

 RB>> Netcomm ) this should tell us one way or the other if it was

 RB>> your lines that were not up to scratch or those modems. I don't

 RB>> want to start a war here...I just want to know that you can get

 RB>> the best out of your

 JP> Courier.



 JP> Fair enough. In terms of setting it up, all I did was enter a

 JP> terminal, issue AT&F1&K3&W and used ATZ from then on.
No problems

 JP> so far. Not having to fiddle with multiple settings is one feature

 JP> I was quite impressed with.



I use AT&F1&A3&K3 AT&W The &A3 is just cosmetic (Full
protocol result

codes)



 RB>> The only troubles you may have, are either you or your users

 RB>> connecting (with inferior modems...older VFC modems) at no higher

 RB>> than 26400. But this could be a thing of the past soon with near



In this case I add S27=48 on dialling out.



 JP> Hopefully. :-) The caller (who is having problems staying

 JP> connected) has a Lightfax 1414LC according to the answers he

 JP> submitted when he first logged in over a year ago. He hasn't had

 JP> any problems connecting and staying online to the M11F I was using

 JP> before, but it is disturbing that the same can't be said of the

 JP> Courier.



Could very well be V.42 Negotiation detection causing trouble.



 If the reason for disconnect is:



      XID Timeout:

                 The modems failed to negotiate the V.42 Detection

                            (XID Exchange) phase.





 Odd one here, Food for thought..



Russell



--- Terminate 4.00/Pro