View Single Post
Old December 14th, 2017, 07:15 AM   #9
Mispeld
Member
United States

Mispeld is offline
 
Mispeld's Avatar
 
Join Date: Feb 2017
Location: VA
Posts: 301
If you are running out of ideas, consider checking where Logix 500 is activating from -- FTAM or a legacy "master disk" file. If the EVRSI is still on your machine, and Logix 500 is going there for activation, the CHECKDRIVES parameter may have in impact on startup time under various network configurations. If that activation file is on your C drive, you will want CHECKDRIVES=C in Rocksoft.ini as described in various Rockwell Technotes.
  Reply With Quote