home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!bonnie.concordia.ca!clyde.concordia.ca!altitude!elevia!alain
- From: alain@elevia.uniforum.qc.ca (W.A.Simon)
- Newsgroups: comp.dcom.modems
- Subject: Re: WorldBlazer - the movie
- Message-ID: <13987@elevia.UUCP>
- Date: 30 Jul 92 02:39:06 GMT
- References: <13985@uniforum.qc.ca>
- <9207272313.AA12022@america.TELEBIT.COM>
- <9207281505.AA03097@america.TELEBIT.COM>
- <9207280635.AA01222@resonex.com>
- <9207281512.AA22888@technix.technix.MN.ORG>
- <199207290101.AA26522@wsrcc.com>
- <9207282305.AA13672@jwt.UUCP>
- Lines: 65
-
- I had complained:
- > > a) When calling another WorldBlazer (from now on, I'll just write WB)
- > > the login sequence happens just like in a wet dream. Unfortunately
- > > the protocole negociation fails. The same pair of WB's, in v42 cum
- > > v42bis (from now on, I'll just write 42) mode, does just fine.
-
- and Telebit promptly e-mailed:
- > Telebit Technical support has found a problem when the ANSWERING system has
- > a WorldBlazer and is using a UUCP window size of greater then 3. It appears
- > that the WorldBlazer is not passing through the UUCP start-up sequence, there-
- > fore causing UUCP 'g' start-up failures when UUCP protocol support is used.
- > We are currently working on a resolution, but until then adjust your UUCP
- > window size to 3 (which is what the modem negotiates when UUCP spoofing is
- > used in either PEP, V.32bis or V.32 in MNP mode) or set S111=0 so the World-
- > Blazer does not use UUCP protocol support. You can also establish a V.32 or
- > V.32bis connection using V.42 error control when the calling modem is a T1600,
- > T3000, T2500, or WorldBlazer and your throughputs should not decrease that
- > much. For T1600's, T3000's and WorldBlazers use: S50=6 or S50=7 and S180=2
- > and on T2500's use: S50=6 S95=2 S97=1 S106=1 for calling the WorldBlazer.
-
- > > b) When calling some of my PEPy neighbours, yeach, NO GO... Some are
- > > PEPier than others, I guess... The more recent PEP's recognize my
- > > baby. And the xfer rates are quite good.
-
- A couple of good people quickly set me straight on this one:
- > There is a known problem connecting to old TB+ models (ROM 4.00 or earlier.)
- > There are ROM upgrades available for the older TB+, or you can wait about
- > a few weeks until Telebit releases the next version of the WB ROMs, which
- > will have a compatibility mode (similar to the S120 register in recent
- > TB+ models.)
-
- > > c) When I use my other modems to call into my WB, lo and behold, it
- > > simply will not answer the phone, lazy bastard. And - please -
- > > do not tell me about S0=1; believe me, it is beyond this... Any
- > > other modem in the same position (same serial port same phone
- > > line same cables) will answer the phone.
-
- I received no feedback on this one. However, I had a chance to swap
- my WB with another one that was known to answer correctly. Same shit.
- I placed a T3000 in the same place and it answered the phone. Any
- other modem I tried answered the phone. It looks like a serial port
- problem. I am still working on it.
-
- A couple of unamed nice guys reminded me of the basics, as in:
- > Try checking the setting of &D (DTR Interpretation), and see if the
- > DTR light is on on your modem. If &D is set to anything except 0,
- > and DTR is not present, the modem will not answer the phone.
- and I thank them.
-
- But, significantly, all the replies had something nice to say about
- Telebit's Tech Support. Here is a typical one:
- > In general, Telebit Tech Support is very good, you should call them.
- > You will likely be put on hold for a couple of minutes when you call,
- > then somebody will take contact information and put you in their queue.
- > You will generally be called back within two to four hours. At least,
- > that's been my experience. Once you're talking to a support person,
- > they are usually very helpful.
-
- Thank you all.
-
-
-
- --
- The Vacuum Cleaner Man (reality sucks)
- God made me a chauvinist, my woman made me clean the house
-