Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!olivea!apple!netcom!gandrews From: gandrews@netcom.COM (Greg Andrews) Newsgroups: comp.dcom.modems Subject: Re: T2500's and v.32bis -- rumors? Summary: Remote access in the T1600. Message-ID: <28578@netcom.COM> Date: 17 Mar 91 01:09:20 GMT References: <1991Mar14.061634.14390@shaman.com> <28407@netcom.COM> <7178@emory.mathcs.emory.edu> Organization: Netcom - Online Communication Services UNIX System {408 241-9760 guest} Lines: 43 In article <7178@emory.mathcs.emory.edu> km@mathcs.emory.edu (Ken Mandelberg) writes: >In article <28407@netcom.COM>, gandrews@netcom.COM (Greg Andrews) writes: >|> >|> Why no protocol spoofing in V.42? Simple - the CCITT wasn't registering >|> extensions to the V.42 protocol when Telebit wanted to add protocol support. > >I had been wondering why on the T1600 the "remote access" commands only work >in MNP mode and not V.42. I guess the reason may be the same as suggested >above for spoofing. > Exactly right. > >By the way, I think its obvious why the upgrade path from the T2500 to >V.32bis can't be just firmware or a new daughter board, and will >probably be just some sort of discount on a new modem. The serial side >of the T2500 (on the motherboard) is apparently stuck at 19.2K max. It >doesn't seem to make much sense to signal at 14.4K with typically 2 >fold and more compression, if you can't push it out of the back of the >modem at better than 19.2K. (If Telebit could have increased the serial >rate with firmware surely they would have already done that to be >competitive even with the current V.32/V.42BIS modems). > Even so, a replacement for the 68000 wouldn't help much if the DSP processor couldn't handle the modulation. Both the 68000 and the 32010 were changed (along with most of the support chips). > >I think the more interesting question is will the T1600 get V.32BIS >with new firmware. > I can't tell at this point. Nobody's made an announcement about the T1600 and V.32bis. Tech support usually hears about it the same time everyone else does to minimize leaks. -- .-------------------------------------------. | Greg Andrews | gandrews@netcom.COM | `-------------------------------------------'