mmunicating via the Access.bus, thus eliminating the memory-hogging platform-specific driver installation, DIP switches, jumpers, or terminators.
The Access.bus connection protocol was developed by Digital Equipment and Philips Semiconductors in 1985. Because of its simplicity, it is widely accepted as an industry standard. Many hardware peripheral vendors plan to provide this connection in future products. This connectivity can be provided on existing peripherals and software-controlled devices. NEC Technologies has a head start in this game by offering an Access.bus connector on its XP series of 17- and 21-inch monitors.
With the Access.bus connection, you can connect up to 125 devices to your system in daisy-chain fashion, without having to manually configure each device. For example, you can connect your system to the monitor via the Access.bus, connect the printer to your monitor, connect your modem to the printer, and so on. The order in which you connect is irrelevant. If you want to add another device into the chain, it can be plugged in anywhere, and the system will know what I/O to use to address that device.
The system comm
unicates with each of the connected devices via the Access.bus, and each device is intelligent enough to respond to the system calls. Because the device communicates via the Access.bus, the platform on which it is connected becomes irrelevant. The Access.bus can also be used to update the flash ROM on the peripheral.
Windows 95 provides a Plug and Play device featuring an automatic detection of the monitor. Here, the monitor identifies itself as a Plug and Play-compatible device easing the setup and configuration time. With Access.bus compatibility, peripheral manufacturers should make their products more intelligent to accept and send instructions back and forth to the system.
No Transfer Necessary
photo_link (22 Kbytes)
NEC's Multisync XE21 features an Access.bus connection for hassle-free installation.
Access.Bus Technology
