Xerox 8400B User Guide

 

 

 

 

Each vendor section within the Mib.ini file follows the format shown in the sample 
text above. In this case the Xerox vendor has 5 valid MIB II System Object 
Identifiers (SysObjIDs) associated with it. Concatenated to the SysObjID is an 
integer value delimited by a colon (‘:’). Valid values for this integer value are 0, 1 
or 2. This integer value is used to indicate whether or not the printer with the 
specified SysObjID has a built in HTTP server. A value of 0 indicates that the 
printer does NOT have an HTTP server, a value of 1 indicates that it does have an 
HTTP server, and a value of 2 indicates PrinterMap is to determine whether the 
printer has a built in HTTP server.  

NOTE:   The Mib.ini file may contain comment lines shown in the previous 

sample. The first two characters of comment lines should be two 
forward slashes (“//”) for consistency.  

 
The Mib.ini file may be modified with any text editor.   Be careful not to damage 
the file structure or modify any default entries because PrinterMap may not 
function properly afterwards. To edit the Mib.ini file the user needs the vendor of 
the printer being added, the printer’s System Object Identifier, and whether the 
printer has a built in HTTP server. The printer’s System Object Identifier may be 
determined using any MIB browser to view the printer’s MIB II System values.  

Using a text editor, find the vendor portion of the Mib.ini file to be modified. Next, 
update the  number= entry under the vendor block identifier field with the total 
number of System Object Identifiers for this vendor following the modifications. 
Next append the new System Object Identifiers to the end of the vendor block by 
adding new  validN= entries for each new SysObjID:HTTP_flag combination. 
Save and exit the file after modifying.  

NOTE: The PrinterMap Topology window must be exited and restarted to 

register the new Mib.ini entries.    

Following changes to the Mib.ini file, the discover process may be run to find any 
new printers on the network which match the new Mib.ini file entries. However, 
Generic printers already discovered by PrinterMap prior to the Mib.ini file 
changes are unaffected. PrinterMap’s Update process may be used to convert any 
Generic printers now identified in the Mib.ini file to the appropriate vendor 
printer. 

Refer to “Update” in Chapter 4 for more information on PrinterMap’s Update 
process. 

The [xerox_models] section of PrinterMap’s Pmap.ini file contains entries which 
map Xerox printer models to model-specific icon files. PrinterMap Topology uses 
these entries to determine the icons to display for supported Xerox printers. If a 
Xerox printer is discovered but contains no entry in the Pmap.ini file associating it