Path: utzoo!mnetor!uunet!peregrine!ccicpg!turnkey!stanton!donegan From: donegan@stanton.TCC.COM (Steven P. Donegan) Newsgroups: comp.dcom.modems Subject: Re: hayes 9600 vs. trailblazer Message-ID: <17@stanton.TCC.COM> Date: 16 Apr 88 02:28:00 GMT References: <8804132344.AA25064@ucbvax.Berkeley.EDU> Organization: Stanton Public Domain Systems, Stanton, Ca. Lines: 46 Summary: When being quoted... In article <8804132344.AA25064@ucbvax.Berkeley.EDU>, RAF@NIHCU.BITNET ("Roger Fajman") writes: > > > ------------------------------ > > > V.32 modems are normally used for synchronous devices, such as IBM protocols > > and X.25 protocols. To use a V.32 modem with a terminal or pc will require a > > sync to async converter in most cases. The cost for a quality V.32 modem is > > still prohibitive when compared to a Trailblazer or Hayes 9600 ($500 to > > several > > $k more expensive). > > Asynchronous V.32 modems are made by several manufacturers, such as > AT&T, UDS, and Cermetek. The price is still higher than modems using > proprietary technology, but has been dropping rapidly lately. When being quoted, I would appreciate a note regarding the origin. On another note; QUALITY V.32 modems, in my experience, denotes modems manufactured by RACAL MILGO, CODEX, ANDERSON JACOBSON and other equally HIGH QUALITY manufacturers. I will probably get flamed for this, but UDS (Motorola) and Cermatek are not (again real-life experience with MANY modems) as well built, reliable (as in MTBF) or robust (as in line noise handling capability) as the above mentioned modems. ALL OF THESE MODEMS cost at least 2000$ each. I have yet to see/use an AT&T modem that is V.32 (rather surprising in that my employer is deeply in bed with AT&T). My total experience with AT&T modems has been with the older 4096 rack mounts etc. I do not believe these to be V.32. In the V.32 and other high speed modes, you get what you pay for. NEC FUJITSU and others are also high quality, reliable manufacturers. My company at my suggestion has used Trailblazers to support immediate need, error free async communications to nasty areas...such as dial-up to Singapore, Puerto Rico, Malaysia and other really bad (line noise environments) locations. I am the primary network architect for Western Digital and take matters such as these very seriously. If any/all of you have positive experiences with more cost effective solutions to remote site up-time and support, please pass them along. My disclaimer: My opinions are my own, my company pays me for them, but they don't own them or neccessarily support them. -- Steven P. Donegan Sr. Telecommunications Analyst Western Digital Corp. donegan@stanton.TCC.COM