Anthon Lockwood

@ashishcompwiz compilation is way simpler on this [fork](https://github.com/anthwlock/untrunc).

Hi, you might want to try using my [fork](https://github.com/anthwlock/untrunc), as its much easier to build!

I simply use `make` on [this](https://github.com/anthwlock/untrunc) fork. I somehow really like that fork!

@Prakash19921206 iirc you have to choose the pthread threading model when installing cygwin.

I don't know about cygwin, but I was able to build untrunc on windows using mingw-w64. On install mingw-w64 asks your preferred threading model:  Eventually you will have more...

_Note:_ Automated builds are now available [here](https://github.com/anthwlock/untrunc/releases/tag/latest).

For windows, I have set up automated builds. You can find them [here](https://github.com/anthwlock/untrunc/releases/tag/latest). If something doesn't work, please report it [there](https://github.com/anthwlock/untrunc/issues), not here.

It's a fork! Look [here](https://github.com/anthwlock/untrunc#about-this-fork) for a list of differences.

from https://github.com/anthwlock/untrunc/issues/31#issuecomment-534185772: > I added some logic to dynamically (at runtime) detect and use some characteristics from the healthy file. If you want, you can see them all via `untrunc...

I made an [attemp](https://github.com/anthwlock/untrunc/commit/3a8cfa864905ec4bca9c012083a36b600396823f) to better support >2GB files on my branch. It also handles file_ok2GB, by replacing `stco` with `co64` if needed.