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

ArticlesSniffing Out LAN Hardware


September 1995 / Reviews / Networking at Warp Speed / Sniffing Out LAN Hardware

When you want to know what kind of LAN adapter your computer uses, you remove the cover and inspect the adapter. But installation software that wants to identify your LAN adapter has to use machine instructions to detect and identify such hardware. Micro Channel and EISA adapters are relatively easy to detect; both architectures supply configuration data to programs. ISA-based PCs, on the other hand, present installation software with a minefield of problems.

Warp Connect's installation program invokes functions within a DLL to sniff out LAN hardware . This DLL contains code that identifies 250 to 300 different network adapters; two-thirds of this code is for ISA adapters. IBM programmers re gularly add new entries to the list. Each addition goes through regression tests to make sure the new code doesn't crash in the presence of the other listed adapters.

The DLL steps carefully through a series of adapter-signature tests to find out what LAN adapter you have. The tests first look through adapter ROM for patterns of bytes. Sometimes the software uses adapter-specific sequences of IN and OUT machine instructions to make the query. Because the same adapter can often use different I/O addresses and IRQs, the detection software often must make several attempts at identifying it.

The order of the tests is important. The same sequence of IN/OUT instructions that detects one kind of adapter might cause a different kind to freeze the computer. And the possibility of troublesome interactions between the detection software and adapters sensitive to certain machine instructions makes it important to figure out which adapters are examined first.

To run the detection code outside the inst allation procedure, open a Warp Connect OS/2 command-line session and run the OS2SNIFF program in the GRPWARE directory. OS2SNIFF will invoke the detection routines in NCD.DLL and display the results on-screen.


Better Than a Bloodhound

screen_link (58 Kbytes)

The installation program sniffs out network adapters, then gives you confirmation of those that are installed.


Up to the Reviews section contentsGo to previous article: The Networking DifferenceGo to next article: To Print a RainbowSearchSend 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