www.makemkv.com

As far as I know the program will no longer be free when the full version is released. In general there are 3 phases when it's about releasing a software: a alpha phase a beta phase a final phase In the alpha phase no versions are published to the outside world. This is the time when the developer(s...

I also noticed that the new version reads at 0.6 x. Not all discs but some. But I am not quite sure in which version it started. I haven't used 1.16.7, yet. So it must be 1.16.6 or earlier.

A few versions ago makemkv used the windows native "save file"-window. This window worked just fine. But now it's using a window from a GUI package which is full of bugs. I can't use this window at all, no matter in with level/subdirectory I am because it doesn't even show my drives, so I ...

The screenshot you posted says it all. Windows doesn't know the program and then it went in full alert mode to scare you. The message is ridiculous.

On old disks I have often found a thin film of some substance. Maybe it's the plasticizer of the package. But at an age of about 10 years they get harder to read.

And here is the modified makemkv.exe for the version 1.16.0.

I only tested whether the program starts (which it does). I had no time to do ripping.

Hurray, I got it running. A single bit was the cause. Setting the bit to 0 solves the problem. I just checked the function call and what makemkv.exe is feeding as input parameter values: call kernel32.dll/CreateNamedPipeW( Name = address_of_2_byte_per_character_string("\\.\pipe\LOCAL\makemkv-00...

If I remember correctly there are 4 different error messages you can get at this stage of the loading process. They all seem to be triggered by a failed pipe connection in one way or another. I tried to get version 1.16.0 running by either using makemkv.exe or makemkvcon.exe from the 1.15.4 package....

Thank you for this information. This saves me a lot of work because I thought it was a Windows XP specific problem.

My analysis so far is, that makemkv.exe calls kernel32.dll/CreateNamedPipeW to open a connection with writing access to a pipe which is supposed to be connected with makemkvcon.exe. But the function fails with ERROR_INVALID_PARAMETER. Then makemkv.exe shows the error message and terminates itself af...

Hello and welcome to the scene, as you probably noticed there is a new version out (1.16.0). This version has the same problem like the previous version (1.15.4), that it cannot be used in Windows XP anymore. The last known version which works out of the box in Windows XP is 1.15.3. We got the previ...

If you use a magnetic hard drive then don't forget that the read/write head will start to move around reducing the writing speed dramatically. When I copy a big file from A to B then my hard drive is so bussy that it isn't even fast enough anymore to store the data comming from 1 DVD drive (about 12...

If you wanted to similarly edit "libffm.dll" to zero out "bcrypt.dll", the import directory entry .... But unfortunately, there are entries for 2 more DLLs after it: "kernel32.dll" and "msvcrt.dll". If you were to remove the entry for bcrypt, you'd have to mo...

Wow, nowadays there are not much people who have such a deep knowledge about the PE32 file format like you have. I am really impressed. Yes, it's a quick and dirty hack. And your solution is much cleaner than mine. But many in here are pure consumers. They want an executable that works somehow. Not ...

qbm0000 wrote: ↑

Sat Dec 12, 2020 9:15 am

It seems like MakeMKV doesn't even call those functions

If this is true, we can simply throw out the import descriptor (attachment below). If this is not true, the application will crash somewhen.

But actually the developers should fix this instead of us providing hacks.