People make yourselves useful.
I was away for 2 weeks and the only thing razor gets is people telling me the program does not work, CRC errors and etc.
I'm not a repacker guys, I'm just a programmer, I create programs for you guys, and the least you guys can do is upload the file that gives pzlib problems, nothing has been uploaded so far. Firstly I'm on capped net your attachments must be small, can't expect me to download some game so that I can figure out the bug myself yet I don't even use pzlib at all, I simply buy games or just keep them "DP" Direct play, I really don't have time for repacking at all, the effort of repacking can easily be converted to buying another hard drive, anyways. What I'm trying to say is, none of my games do raise any CRC errors, and I'm giving you guys a job to fix it.
Now it must be really difficult to figure out which small file can have bugs well it is simple like it is difficult for me to figure out a bug in several gigabytes of data.
For example. PES2017, game is like 6GB. When I first used pzlib v2, it was buggy and gave CRC errors everytime it comes across dt15_win.cpk, but when you use pzlib on that file alone, the error isn't there. pzlib works with chunks and it keeps its chunks constant so what I did was flush the bug out. Firstly, the game is 6.2GB or so, don't really remember. (Game was crap so I deleted it and only kept the buggy part of it)
Ok so from 6.2GB, I know that the problem lies in dt15_win.cpk, so all I did was remove all files that came after that file and kept everything else and I remained with 1.22 GB because everything after dt15_win.cpk was close to 5GB meaning I'm trapping the bug and making it easy to spot, also making it easy for you guys to upload.
From that 1.22 GB, there was dt00_win.cpk, dt10_win.cpk, dt11_win.cpk, dt12_win.cpk, dt13_win.cpk, all those files were 964 MB, now from what I remember, in the past I created dummy file creator, just make dummy files of those files meaning you'll still have 1.22GB but now the data will be compressible for upload for me to investigate. I ran pzlib on the data with the dummy files, since the bug only lies in dt15_win.cpk, the bug was kept which is good because now the bug is even more trapped.
Remember pzlib works with chunk sizes, by default it's 16mb, so to trap the bug even more, you can start by deleting data from position 0 of the data, keep removing 16mb until the bug is gone, I ended up with 16.8mb of data from 964MB, and the bug was gone, I then readded 16mb to make sure the bug is still there so that I can investigate and find out what was wrong, the final size was 32.8 MB. So from 6.2GB worth of data, I ended up with 32.8MB but the bug was maintained, I then figured out what the problem was, fixed via programming and then added a few touches then made pzlib v3 having thought all the bugs were gone but they weren't.
So in short, you guys should do something roughly like this for the bug to be fixed.
Anyways, I uploaded an example. In the attachment. This file is buggy when used in pzlib v2, but it works in v3 because I did have the game that made pzlib to be buggy and fixed it, I don't have game that makes pzlib v3 buggy which is why it is buggy.