To download the latest version of EnergyPlus go to:
https://www.energyplus.net/downloads
or
https://github.com/NREL/EnergyPlus/releases
Passwords are no longer needed to use EnergyPlus, download the latest version at:
https://energyplus.net/downloads
If the older version is from the previous release, use the pull-down File menu in the EP-Launch and select "Transition Version". This will update the older file to the newer version.
If the older version is older than the previous release, then you must use the multiple transition program. You can download the transition programs from this site.
(That is http://energyplus.helpserve.com and go to the downloads area).
The Multiple Transition folder is set up on the EnergyPlus install.
Unzip the file into the MultipleTransition folder and use the IDF Converter GUI program to transition your older files.
QUESTION:
I am still having e+ installation problems of version 1.3 on windows vista. After double click on the exe file the installation routine starts normal, but then when "copying Visual Basic Runtime: C:\Windows\system32\oleaut32.dll" the little papers signaling the copying keep flying but there is no installation progress any more. I already switched out the firewall, but as I am new to vista I don't know what else I could try. Does anybody have an idea? I cannot use a newer e+ version for the time
being.
RESPONSES:
RESPONSE #1:
For another type of software, I had a problem getting the software to load on a Vista machine (very similar to what you are seeing). I don't recall exactly, but in the control panel there was an administrator area. In there the administrator control could be disabled and the software was then able to install. I then just enabled it again and everything worked as before. Hope this helps.
RESPONSE #2:
User Access Control of VISTA is causing the problem.
When using VISTA, you should treat it as a PC and server on the same machine, with an administrator sitting invisible. Your hard drive is like a networked drive. You must do as what the administrator allow you to do. When you right click a directory, you will see a 'share' option, select that and then security, you will see what your ID can do on that directory. If you do not have 'full access', use the ID which has full access, or make your ID has 'full access'. However, if you do not have the administrator right, you may not be able to do it.
So, you have to log in as an administrator to 'share' the disk with your ID. This is what you usually has to do in an intranet on the network disk.
If you can make your user account as an administrator type, many installation problem may not occur. You do not need to turn of the fire wall, etc. but to make sure your ID has the full control of the hard disk drive. If you do not have the full control, you cannot create file folder on the drive, and the installation will fail.
If you turn off the User Access Control, the machine cannot ask you for the administrator permission, and therefore appears to be stopped.
If you have tried installing the program using another account, make sure that the directory is removed, or shared with your new ID. Otherwise, any files in there cannot be replaced. That may result in what you saw, because the oleaut32.dll was not owned by you and the installer is searching for a solution, and this can take minutes. Eventually, a pop up may show to ask you what to do.
"copying Visual Basic Runtime: C:\Windows\system32\oleaut32.dll" will stay until some time out mechanism kicks in. If you are not an administrator, you normally cannot access the \system32\ directory.
When the files are copied from a CD_ROM during installation, the files will appear as 'Read only' on the hard disk. When you run the simmulation, some of the files must be modified. The read only attribute on the files may abort a simulation run. After the installation, you should verify that the .bat files are not all 'read only'. You should also choose 'run as administrator' whenever possible when you run a EPlus application, so that the simulation program can modify directories and files.
Hope this will help. Make yourself a standard user and administrator with a password, before you try to install again.
If you can switch off the fire wall, you should already have administration right, or administrator's permission. If you did it with the administrator pop up, you account may not be an administrator type.
I am still having e+ installation problems of version 1.3 on windows vista. After double click on the exe file the installation routine starts normal, but then when "copying Visual Basic Runtime: C:\Windows\system32\oleaut32.dll" the little papers signaling the copying keep flying but there is no installation progress any more. I already switched out the firewall, but as I am new to vista I don't know what else I could try. Does anybody have an idea? I cannot use a newer e+ version for the time
being.
RESPONSES:
RESPONSE #1:
For another type of software, I had a problem getting the software to load on a Vista machine (very similar to what you are seeing). I don't recall exactly, but in the control panel there was an administrator area. In there the administrator control could be disabled and the software was then able to install. I then just enabled it again and everything worked as before. Hope this helps.
RESPONSE #2:
User Access Control of VISTA is causing the problem.
When using VISTA, you should treat it as a PC and server on the same machine, with an administrator sitting invisible. Your hard drive is like a networked drive. You must do as what the administrator allow you to do. When you right click a directory, you will see a 'share' option, select that and then security, you will see what your ID can do on that directory. If you do not have 'full access', use the ID which has full access, or make your ID has 'full access'. However, if you do not have the administrator right, you may not be able to do it.
So, you have to log in as an administrator to 'share' the disk with your ID. This is what you usually has to do in an intranet on the network disk.
If you can make your user account as an administrator type, many installation problem may not occur. You do not need to turn of the fire wall, etc. but to make sure your ID has the full control of the hard disk drive. If you do not have the full control, you cannot create file folder on the drive, and the installation will fail.
If you turn off the User Access Control, the machine cannot ask you for the administrator permission, and therefore appears to be stopped.
If you have tried installing the program using another account, make sure that the directory is removed, or shared with your new ID. Otherwise, any files in there cannot be replaced. That may result in what you saw, because the oleaut32.dll was not owned by you and the installer is searching for a solution, and this can take minutes. Eventually, a pop up may show to ask you what to do.
"copying Visual Basic Runtime: C:\Windows\system32\oleaut32.dll" will stay until some time out mechanism kicks in. If you are not an administrator, you normally cannot access the \system32\ directory.
When the files are copied from a CD_ROM during installation, the files will appear as 'Read only' on the hard disk. When you run the simmulation, some of the files must be modified. The read only attribute on the files may abort a simulation run. After the installation, you should verify that the .bat files are not all 'read only'. You should also choose 'run as administrator' whenever possible when you run a EPlus application, so that the simulation program can modify directories and files.
Hope this will help. Make yourself a standard user and administrator with a password, before you try to install again.
If you can switch off the fire wall, you should already have administration right, or administrator's permission. If you did it with the administrator pop up, you account may not be an administrator type.
Question: We have upgraded to E+ V7 on most of our machines, but have to keep V6 for some older projects. Now the following question arose: is it possible to have multiple EnergyPlus versions installed on the same windows PC, or will they interfere somehow? Of course, they will be installed in different folders, but what about windows registry and other "common" resources?
Answer: Not a problem. You may install multiple versions of EnergyPlus on the same Windows machine as long as the folder names are different. The only common resource will be the Windows registry entries which all relate to EP-Launch and IDF Editor. These entries are shared by all of the installed versions, so if you change an EP-Launch option in v6, the same option will be set when you open v7 EP-Launch.
When installing EnergyPlus, there is an option to associate idf, imf, and epg files with EP-Launch. If you select this option during install, then that version of EP-Launch will open when any idf (or imf or epg) file is double-clicked in the file explorer, even if the file is for a different version. You can reset this association to a different version in EP-Launch --> Options --> File Association.
Hint 1: EP-Launch and IDF Editor display the current version in the lower left corner.
Hint 2: If you like to double-click files to open EP-Launch, and you are working with files from multiple versions, you can still use this feature with one extra step. Whenever EP-Launch is closed, it stores that current input file and weather file paths in the registry.
Let's say that the file association is set to v7, but you want to work with a v6 idf file. Double-click the v6 idf file in the file explorer. This will open v7 EP-Launch with the double-clicked file selected as the current input file. Close v7 EP-Launch (and this will store the input file path in the registry). Then open v6 EP-Launch and the same file will be selected. This can save time navigating across folders.
Hint 3: You can have multiple instances of EP-Launch open at the same time. These may be from different versions or you can even open multiple instances of EP-Launch from the same version. You can run simulations simultaneously from each instance of EP-Launch with one constraint: you cannot run simulations for idf files residing in the same folder from more than one EP-Launch at the same time.
Why? When a simulation is started, EP-Launch creates a temporary folder in the folder where the idf file resides. A given instance of EP-Launch can run multiple simulations in the same folder and will create temporary folders number 1, 2, 3, etc. But one instance of EP-Launch does not know about simulations in progress from a different instance. So, if two instances of EP-Launch run a simulation on files from the same folder, they will both try to work with the same temporary folder and one or both of the simulations will crash.
Hint 4: The recent file lists for input and weather are shared across versions, but the history file is specific to each version. This can help save time when opening outputs from previous simulations. The history is stored in a file named history.csv in the main install folder for each version. It may be edited or deleted to clear old entries.
Answer: Not a problem. You may install multiple versions of EnergyPlus on the same Windows machine as long as the folder names are different. The only common resource will be the Windows registry entries which all relate to EP-Launch and IDF Editor. These entries are shared by all of the installed versions, so if you change an EP-Launch option in v6, the same option will be set when you open v7 EP-Launch.
When installing EnergyPlus, there is an option to associate idf, imf, and epg files with EP-Launch. If you select this option during install, then that version of EP-Launch will open when any idf (or imf or epg) file is double-clicked in the file explorer, even if the file is for a different version. You can reset this association to a different version in EP-Launch --> Options --> File Association.
Hint 1: EP-Launch and IDF Editor display the current version in the lower left corner.
Hint 2: If you like to double-click files to open EP-Launch, and you are working with files from multiple versions, you can still use this feature with one extra step. Whenever EP-Launch is closed, it stores that current input file and weather file paths in the registry.
Let's say that the file association is set to v7, but you want to work with a v6 idf file. Double-click the v6 idf file in the file explorer. This will open v7 EP-Launch with the double-clicked file selected as the current input file. Close v7 EP-Launch (and this will store the input file path in the registry). Then open v6 EP-Launch and the same file will be selected. This can save time navigating across folders.
Hint 3: You can have multiple instances of EP-Launch open at the same time. These may be from different versions or you can even open multiple instances of EP-Launch from the same version. You can run simulations simultaneously from each instance of EP-Launch with one constraint: you cannot run simulations for idf files residing in the same folder from more than one EP-Launch at the same time.
Why? When a simulation is started, EP-Launch creates a temporary folder in the folder where the idf file resides. A given instance of EP-Launch can run multiple simulations in the same folder and will create temporary folders number 1, 2, 3, etc. But one instance of EP-Launch does not know about simulations in progress from a different instance. So, if two instances of EP-Launch run a simulation on files from the same folder, they will both try to work with the same temporary folder and one or both of the simulations will crash.
Hint 4: The recent file lists for input and weather are shared across versions, but the history file is specific to each version. This can help save time when opening outputs from previous simulations. The history is stored in a file named history.csv in the main install folder for each version. It may be edited or deleted to clear old entries.
Passwords are no longer needed to use EnergyPlus, download the latest version at:
https://energyplus.net/downloads
Help Desk Software by Kayako