The Abekas A65, Abekas A66 with Ethernet option, and the Abekas Diskus can act as frame buffers because they can receive images digitally across the Ethernet. (If the Abekas is receiving a digital video signal through the D1 port, its frame buffer section is effectively being bypassed.) In order to use the Abekas completely across the Ethernet without sending a D1 video signal to it, two configuration entries must be defined: one for the video controller functionality and one for the frame buffer. For information on the Abekas video controller, see page 271.
If multiple workstations are connected to your network, you can access the Abekas from any of them provided that they have been updated to recognize the Abekas. Please refer to your workstation's network configuration manual for instructions.
If you have more than one A65 or Diskus on your network, you may want to create a configuration entry for each of them. Be careful to ensure that the video controller configuration entries refer to the corresponding frame buffer configuration entries for the same physical device.
device frame buffer name
server_name server
server_id socket
server_host host
defn
name ethernet_name
format format
enddefn
enddevice
device frame buffer name
The name is the name used by the Abekas A65 or Diskus video controller configuration entry to refer to this device. Since your Abekas also has an Ethernet name, you may want to use that same name here. This name can be the same as the name of the corresponding video controller device.
server_name server
The server is the name of the executable that controls the Abekas. It resides in the product_bin. The server should be fbda65 for either the Abekas A65 or Diskus. (If you relocate the server executable, or if the server is running on a different host than your application, you must specify the server as a full UNIX pathname.)
server_id socket
The socket is the socket number through which your application communicates with the Abekas A65 or Diskus server process. This number must be unique to your UNIX system for each defined device and (Alias|Wavefront and non-Alias|Wavefront) server process. If you are defining multiple Abekas A65 or Diskus configurations, you must use a different socket number for each Abekas. The socket numbers must be different for the video controller and frame buffer configuration entries for the same Abekas.
server_host host
The host is the name of the workstation on which the server executes. This is different than the Ethernet name of the Abekas A65 or Diskus. This can be any of the workstations on your Ethernet network, but you must ensure that your application has been installed on the server workstation as well. The same host should be specified in both the video controller and the frame buffer configuration entries for a given Abekas.
name ethernet_name
The ethernet_name is the name of the Abekas A65 or Diskus on the Ethernet network.
format format
The format indicates whether your Abekas A65 or Diskus recognizes NTSC or PAL-sized images. If this line is omitted, NTSC is used by default.