E3D .bat vs .init

Hi E3D gurus,

I have training on PDMS administration, and I have done some project setup/configuration almost 10 years ago. After we did get a PDMS administrator and I have completly stoped to do setup/configuration.

Now I need to start doing Administration/Setup/Configuration again on E3D, but I have many things forgotten.

I have notice that we now have on E3D .bat and .init files "launch.bat, launch.init, evars.bat and evars.init".

My question is:

Whats the idea on using the .init or keep using the .bat?

  • we rarely touch aveva system file. btw, init for initialisation, .bat is just a windows-readable program, if u good with program, u can change a lot in these two file.

  • From what I can remember from the manuals you can do whichever way you want.

    But, our setup, in call-order, for starting model
    project specific bat-file (*)
    master model bat-file (**)
    mon.exe with master init file (which is a copy of Aveva with our own evars in the end) as argument (***)

    (*) a bit out of scope, but we have our own UI to search/start projects that generate the bat-files at demand for users

    (**) master model bat-file is because we cannot run robocopy or other shell-commands from init-file

    (***) the init file because that is Aveva's default new way and we hope by sticking to their way we will have less trouble in the future Slight smile