PE> You don't actually know, since you've never tried Binkley 2.60. I
PE> bet I am right.
BG> Oh come on Paul, the modem dials, the remote answers, it hears the STD
BG> pips, it drops carrier and redials. Every time it does that, Telstra
BG> charges me a 12c connection fee. It soon adds up, too. That's with BTPE
PE> Read what I said. "You don't actually know, since you've never tried
PE> Binkley 2.60". You said above "it doesn't behave like
Binkley 2.60".
PE> I don't believe you. I bet I am right, and you will have the same
PE> problem with Binkley 2.60.
BG> Then it's about time you learned how to speak English, as far too much of
BG> your stuff is cryptic to the point of unintelligibility. I'm not a fucking
BG> mind reader, you know.
Bill, which bit of "since you've never tried Binkley 2.60" is not
proper English? Before you reply, just spend 15 seconds having a
think about whether it just MIGHT have a SLIGHT POSSIBILITY that
it is actually your English comprehension skills that need brushing
up on.
BG> 4.0, which I thought was your recompile of Binkley 2.60. If not, what is
BG> it?
PE> It is. And I bet it behaves identically. If you try out 2.60, and
PE> it does the same thing, can you ask the question in BINKLEY, as a
PE> problem with 2.60, so that you might get the proper answer.
BG> Couldn't be bothered. I don't have BINKLEY tagged, nor do I have any
BG> desire to do so. If 2.60 is fucked, I'll simply go back to an earlier
BG> version. No skin off my nose at all.
2.60 may not be fucked, it may have changed behaviour. I don't
actually know. All I know is that the code looks fine to me, but
the documentation says something I don't understand, and in either
case I don't know what the magic number is.
PE> Just disable busy-detect for all calls in the meantime anyway,
^^^^^^^^^^^^^^^
PE> why do you care? Binkley will redial anyway. BFN. Paul.
BG> But only after the modem times out, say 60 seconds. I want it to recognise
PE> Sounds like the end of the world to me.
BG> Funny, you're the first to complain if something doesn't work properly.
Yes, you are right. But you will notice that I haven't denied that
there is a problem with Modemtrans, all I've said is that I don't
know whether it is a bug or what. I DON'T KNOW. IN THE MEANTIME, I
suggested a WORKAROUND, which is quite acceptable. To solve the
original problem (if you are interested in solving the original
problem), I need to know the behaviour of 2.60, and the results of a
question in BINKLEY.
BG> BUSY and redial immediately, just like a decent modem should. Only hppens
PE> A decent modem would detect BUSY.
BG> It does. Trouble is, is also occasionally thinks the STD pips is a BUSY
BG> response as well. Not unusual on a US modem, USR or otherwise.
Pity you never mentioned this before, I thought the USR was perfect.
Rod's Supra presumably doesn't have the same problem. The problem
never happened to me though. Which may have been because I used
Optus. Different people experience different problems, you see,
because not everyone's use is identical. Most never even use their
modem to answer the phone.
BG> when dialling STD via your exchange too. Other STD calls work just fine.
PE> A decent mdoem would detect BUSY.
BG> So would a decent exchange.
Do you work for Maestro by any chance?
PE> Anyhow, I thought you were switching to Optus? Optus doesn't have pips.
BG> Optus is also slightly more expensive with my dialling habits.
I was surprised when you said you were moving to Optus.
PE> BTW, you were very lucky relying on the V32b. I sent in a message to my NC
PE> to get V34 added, which he seems to have done without disabling V32b. Very
PE> lucky indeed.
BG> No big deal, if worst came to worst, I'd perform the ModemTrans on your
BG> name instead of the flags. All I need is some difference between yours and
BG> Dave's flags, and I can use that anyway, regardless of what it is.
Why don't you do that then? It would seem my name is a far more
logical thing to do a match on than whether a system has "V32b"
as a flag?! BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|