Normally you need to add the simInfo section in the CDF for the particular simulator in question (e.g. eldoD or hspiceD). If you don't want to permanently modify the CDF, you should be able to do this in the effective CDF (easiest to modify the effective CDF interactively via the Tools->CDF->Edit form, and then use the SKILL cdfDump() function to dump the User CDF - see the manuals for more details). Then you can load the user CDF during each session to overwrite it in memory.Originally posted in cdnusers.org by adbeckett
The second requirement is usually to create a stopping view with the same name as the simulator integration, for each component. However, it doesn't _have_ to be called eldoD. So, you can modify the Setup->Environment->View list to include a view that is already there (e.g. "spectre") - and also put this in the Stop List. Similarly, if you're using a config, put the existing view in the view and stop lists in the hierarchy editor.
Still, if you're doing this over and over again, it may just be best to bite the bullet and modify the PDK. With a bit of SKILL code, that could be automated, to make it easier to maintain.