Archives
 
 
 
  Special
 
 
 
  About Us
 
 
 

Newsletter
Free E-mail Newsletter from BYTE.com

 
    
           
Visit the home page Browse the four-year online archive Download platform-neutral CPU/FPU benchmarks Find information for advertisers, authors, vendors, subscribers Request free information on products written about or advertised in BYTE Submit a press release, or scan recent announcements Talk with BYTE's staff and readers about products and technologies

ArticlesThanks, But No Thanks


July 1996 / Inbox / Thanks, But No Thanks

Jeffrey Fritz's article "Marrying ISDN to the OS" (April) implies that by adding ISDN support to Windows 95, Microsoft has made ISDN easier to use and support. In fact, the contrary is true, at least in Europe, because Microsoft chose to ignore CAPI, the Common ISDN API that has been adopted by the European Telecommunications Standards Institute. Every PC ISDN card sold here comes with CAPI drivers for DOS and Windows, and many come with one for OS/2. Almost every ISDN application builds on the CAPI standard, from telephone-answering to fax to drivers for BBSes, packet or NDIS networking drivers, and on-line service access programs. Windows 95 is not only incapable of working with CAPI, it actually disrupts existing solutions by doing things its own way. Vendors, far from being able to "come to market faster and at lower cost," as you r article asserts, now have to supply drivers supporting Windows 95 and CAPI in order to give users the functionality they are used to.

Tilman Schmidt
Bonn, Germany
tilman@schmidt.bn.eunet.de

In North America, the integration of ISDN into Windows 95 has made it easier--and probably cheaper--to use ISDN. While we may not agree with all their decisions (such as no Multilink PPP and limited compression support), Microsoft is one of the few vendors with enough clout to lead the way in improving ISDN deployment. I can understand why Microsoft's decision not to support CAPI would be considered a serious oversight in Europe. Unfortunately, CAPI has no widely accepted equivalent in North America. Ours is a fragmented environment where even ISDN network products that are supposed to work together frequently do not. We need a mammoth effort to correct this. That won't come from the U.S. or Canadian governments or from the Regional Bell Operati ng Companies. Microsoft's ISDN implementation is far from perfect, and much more work needs to be done; still, someone has to start somewhere. Credit Microsoft for being willing to try.--Jeffrey Fritz


Up to the Inbox section contentsGo to previous article: Join Local #1Go to next article: ThinkPad RevisitedSearchSend a comment on this articleSubscribe to BYTE or BYTE on CD-ROM  
Flexible C++
Matthew Wilson
My approach to software engineering is far more pragmatic than it is theoretical--and no language better exemplifies this than C++.

more...

BYTE Digest

BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin, and dozens of other CMP publications—bringing you critical news and information about wireless communication, computer security, software development, embedded systems, and more!

Find out more

BYTE.com Store

BYTE CD-ROM
NOW, on one CD-ROM, you can instantly access more than 8 years of BYTE.
 
The Best of BYTE Volume 1: Programming Languages
The Best of BYTE
Volume 1: Programming Languages
In this issue of Best of BYTE, we bring together some of the leading programming language designers and implementors...

Copyright © 2005 CMP Media LLC, Privacy Policy, Your California Privacy rights, Terms of Service
Site comments: webmaster@byte.com
SDMG Web Sites: BYTE.com, C/C++ Users Journal, Dr. Dobb's Journal, MSDN Magazine, New Architect, SD Expo, SD Magazine, Sys Admin, The Perl Journal, UnixReview.com, Windows Developer Network