Error message (0xc000007b)

[Marit Koks]

Hi, 

I have downloaded WINDOW as a new application on my laptop. 

THERM has been on my laptop for a longer time and works perfectly. 

I first got the error message dll. but i was able to fix that using this forum. 

However, now a new error message has popped up:

Can not start application (0xc000007b)

Anybody know how I can fix this?

[Robin Mitchell]

Make sure to install the 32 bit versions of both of the redistributables not the 64 bit versions. 

Because the main cause of that 0xc000007b error is installing the 64 bit versions instead of the 32 bit versions.  Even if the computer is 64 bit THERM still requires the 32 bit versions of the redistributables.

Robin

--
You can view the WINDOW forum online at:
https://groups.google.com/g/berkeley-lab-window
---
You received this message because you are subscribed to the Google Groups "Berkeley Lab WINDOW" group.
To unsubscribe from this group and stop receiving emails from it, send an email to berkeley-lab-wi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/berkeley-lab-window/62dbfcc0-0c9f-4ed7-845a-1d818700591bn%40googlegroups.com.

--

Robin Mitchell

Windows & Envelope Materials Group
Lawrence Berkeley National Laboratory

[Ben West]

Hi again,

I performed the stated approach below but the ia32 folder was empty and there is another folder ia32_win which has the dlls but is under a compiler folder and seems to not be linking to the startup. I tried putting the libefcormd file in each THERM and WINDOW folders but still get the same error message.

Thanks,

Ben

To view this discussion visit https://groups.google.com/d/msgid/berkeley-lab-window/CACF39SsAM48atQ%3DS%3DTCcA%3D8%2BUOp3sYzwA4WiwKQac3nen8mzfQ%40mail.gmail.com.

[Stephen Czarnecki]

Hi Ben

It is a little hard to follow this.  Are you the original poster on a new email?

In any case it sounds like you are trying to follow the "Troubleshooting" section from this page: https://windows.lbl.gov/redistributable-packages

Assuming that is correct from what you have said so far it seems like you are in this case: "For the Windows 10 Operating System, the files are probably here
    C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\compiler"

I'm not quite sure what you mean by "seems to not be linking to the startup". But my current best guess is that either that folder is not in your path or there is something else in your path with another version of those files that is ahead of that folder.

Since messing with the path can be a bit painful and potentially break other stuff I suggest trying to copy the files to the same directories as the WINDOW and THERM exes instead. Without going into too much detail as far as I know when Windows runs an exe if it needs to load any dlls it checks a list of places in order the first of which is where the exe is. Since the first place on the list is the same folder as the exe copying the required dlls to the exe folder should resolve the issue.

I know you said you already tried copying libifcoremd.dll but don't mention anything else. If you haven't already could you try copying all of the files and see what happens?

For reference here is what mine looks like:

So could you try copying all of those files to C:\Program Files (x86)\LBNL\WINDOW7.8 or the folder for whichever exe you want to check and see what happens?

If yours only has the libifcoremd.dll another thing to try is running the w_ifort_runtime_p_2023.1.0.46319.exe again and uncheck the "Remove temporarily extracted files after installation." Then when it finishes take a look at what files are in the extraction location and see if they show up there.

Let us know if anything works or, if not, what you are seeing.

Thanks and sorry for the trouble

Stephen