Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: EAC fatal error when accessing directories (Read 5961 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

EAC fatal error when accessing directories

EAC installs fine.  Finds the optical drive no issues.  When setting it up for FLAC, choosing the browse button to locate flac.exe caused EAC to completely fail.  No error messages, it just quits completely.

I can open it up again just fine but investigating further, all of the browse buttons cause the same failure.

Any ideas...??

Re: EAC fatal error when accessing directories

Reply #1 –
Do you mean the "browse" button in EAC > Compression Options > External Compression?

It seems to me that Windows is not actioning a system call to open a file manager window.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: EAC fatal error when accessing directories

Reply #2 –
Yes, but it actually happens at all of the browse button locations.  It also does it when I try to load a profile, or select the compression button.  It seems like anytime EAC goes to windows to do a window call.  I've re-installed EAC, of course rebooted, and Googled extensively.  Can't find a darn thing...

Re: EAC fatal error when accessing directories

Reply #3 –
It sounds like you've installed some other program that's incompatible with EAC.

Re: EAC fatal error when accessing directories

Reply #4 –
That sounds like the following problem with WinFSP, which I also had:

https://github.com/winfsp/winfsp/issues/162

WinFSP is installed with Cryptomator, for example, so it took me some time to find a (temporary) solution. Here someone has created a bat file with a workaround:

https://github.com/winfsp/winfsp/issues/162#issuecomment-816260571

Here are more threads about this problem:

https://hydrogenaud.io/index.php/topic,123769.0.html

https://www.reddit.com/r/musichoarder/comments/12e1bmc/eac_exact_audio_copy_crashes_upon_accessing/?show=original

https://community.cryptomator.org/t/exact-audio-copy-eac-crashes/9953

The problem has been known for several years, but unfortunately only the developer of EAC can fix it. It seems to be due to the fact that EAC was developed with “Stony Brook Modula-2” (a compiler for the Modula-2 language), which only supports 16-bit and 32-bit, as it dates back to the 90s.

Re: EAC fatal error when accessing directories

Reply #5 –
Quote from: d4k0 on
That sounds like the following problem with WinFSP...

If that's true...

Quote
only the developer of EAC can fix it

Really?  Surely it's WinFSP's fault for not emulating a Windows file system properly.  You can't expect EAC (or whatever) to account for that.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: EAC fatal error when accessing directories

Reply #6 –
Quote from: d4k0 on
That sounds like the following problem with WinFSP, which I also had:

https://github.com/winfsp/winfsp/issues/162

WinFSP is installed with Cryptomator, for example, so it took me some time to find a (temporary) solution. Here someone has created a bat file with a workaround:

https://github.com/winfsp/winfsp/issues/162#issuecomment-816260571

Here are more threads about this problem:

https://hydrogenaud.io/index.php/topic,123769.0.html

https://www.reddit.com/r/musichoarder/comments/12e1bmc/eac_exact_audio_copy_crashes_upon_accessing/?show=original

https://community.cryptomator.org/t/exact-audio-copy-eac-crashes/9953

The problem has been known for several years, but unfortunately only the developer of EAC can fix it. It seems to be due to the fact that EAC was developed with “Stony Brook Modula-2” (a compiler for the Modula-2 language), which only supports 16-bit and 32-bit, as it dates back to the 90s.


Thank you d4k0, the batch file worked like a charm.  I'm back to ripping with EAC.

Re: EAC fatal error when accessing directories

Reply #7 –
Quote from: fooball on
Really?  Surely it's WinFSP's fault for not emulating a Windows file system properly.  You can't expect EAC (or whatever) to account for that.

The cause is first of all the following:

Quote
The problem is that EAC is a 32-bit application and the WinFsp Network Provider is 64-bits on a 64-bit system and 32-bits on a 32-bit system. Thus (on a 64-bit OS) we have the unfortunate situation of a 32-bit program trying to load a 64-bit DLL. The result: CRASH!

https://github.com/winfsp/winfsp/issues/162#issuecomment-385555174

From a Dokany developer:

Quote
OK I see what is happening here.
EAC is listing the network provider and open dokannp1.dll that is on the list directly. It does not use the network provider interface, but directly a Loadlibrary. EAC is 32 bits and dokannp1.dll is 64 bits. EAC do not seem to check if Loadlibrary fail and crash. I have installed the 32 bits dokannp1.dll instead of the 64 bits to be sure it is this and I could save a profile without crash.

https://github.com/dokan-dev/dokany/issues/545#issuecomment-343761121

This does not only occur with WinFSP, but also with other virtual file systems such as Dokan and Dokany.

Problems in connection with 64-bit have also been reported in the EAC forum in the past, but there has been no response from the developer. One of the developers of WinFSP wanted to contact him in 2018, but he abandoned it because there was no activity in the forum either. They also didn't want to include a workaround for a single program that requires writing to system folders (System32 and Syswow64).

The problem only seems to occur with "very old" 32-bit applications (more details on GitHub), with “newer” 32-bit programs a compatibility mode of Windows may take effect (from Vista onwards there were some changes in the APIs). In my case, the problem only occurs with EAC, I don't have the problem with any other 32-bit programs. The batch file ensures that the registry links to the 32-bit file for 32-bit programs on a 64-bit operating system.

Since 2011, there has been a free successor to “Stony Brook Modula-2”, “ADW Modula-2”, which also supports 64-bit.

Quote from: elmn8r on
Thank you d4k0, the batch file worked like a charm.  I'm back to ripping with EAC.

I'm glad that I could help.