Assuming the data (including directory structure) you want is all on 
the nike mod20, then, yes, it's probably easier to change system A's 
configuration to accommodate the nike mod20 devices than it is to 
change system B's configuration to syncronize with system A's dtc 
ldevs and npconfig network printers.

If that's true, then, yes, it makes sense to restore system A's 
config.sys onto system B (specifying ldev 1) and then modifying to 
define the mod20 luns prior to rebooting.

You may then also need to address any conflicts between the ldev 
configuration of system A associated with its single DTC - if any - 
and system B's DTC and NPCONFIG ldev realities.



At 05:52 PM 2005-12-14, Greg Terterian wrote:

>First of all thank you to all who responded.  One more question?
>Can Company B/should CompanyB also Restore @.CONFIG.SYS from  Company A?
>
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

-------------------------------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
email:  [log in to unmask]  web: http://www.gsainc.com
-------------------------------------------------------------------------------------------------

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *