mgrinzPlayer

No need to compile. I just hex edit range "1-16" to something else e.g. "1-64". You can use OllyDbg, x64dbg, CheatEngine, .... to find the right spot.  Then you...

 

Yeah. Those " were misleading 🙃 As I wrote earlier, I changed one byte only at offset 0xEF3C8. I forgot to mention: windows binary.

We know offset for 32bit. So, example for 64bit 1.35.0 win build and x64dbg. launch x64dbg, press F3, open aria2c binary, be sure CPU tab is viewed, press Ctrl+G and...

yes, 64bit aria2c 1.36.0, it is at 0xDF773. For 32bit, it is at 0xC5261. > needs to be done a little differently. For me, algo is still the same ("current...

> weird build of aria2 Offset is the same for me and you - 0xDF773. Maybe your x64dbg version works different (May8 2021 versus Jan 21 2022). I will try...

Thank you for your reply. >Why not just call mingw32-make.exe directly? No need to ask users to create a mess in their installs I took this, not mandatory, step from...

Similar here, 4.0.0.0-march-2016-prev1 Fortunately, _sources_ folder is empty. log: ``` ********************** Windows PowerShell transcript start Start time: 20160319155524 Username: USER-WIN10\User RunAs User: USER-WIN10\User Machine: USER-WIN10 (Microsoft Windows NT 10.0.14279.0) Host...

I've narrowed it down to pullrequest/commit/summary: PR2107/5047e4a/"Do not close stdout and stderr" Reverting only this one from official 1.37.0 source code and recompiling it brings previous behavior back. PR #2107...

Did you read readme.txt? _The CD-ROM has two tracks, the second being an audio track which consists of the random bonus song file, LIKE55.WAV. Because of this structure, using different...