It's smart enough to always use binary mode for output files so it doesn't write bad ticket, tmd or cert files.icefireicefire said:like what can this do that BFGR cant?
(BFGR shares files under vista? WTF are you talking about?)
It's smart enough to always use binary mode for output files so it doesn't write bad ticket, tmd or cert files.icefireicefire said:like what can this do that BFGR cant?
icefireicefire said:Except this has already been made before. No offense, its a great looking app, but why reinvent the wheel?![]()
and BFGR's code is perfectly fine. The real reason is probably found in Cygwin.Knocks said:Don't blame it on the OS if the software is not compliant. When bfgr extracts a wad, it creates a new folder and throws the unpacked contents in it, and that folder for some reason is SHARED by default.
It's not fine. Whoever ripped off segher's code for zeventig changed the fopen calls for the .app files to "wb" mode but wasn't smart enough to do the same thing for the tmd and ticket (and trailer and cert). Hence it writes 0x0D 0x0A instead of just 0x0A because the output file is in text mode.icefireicefire said:and BFGR's code is perfectly fine. The real reason is probably found in Cygwin.

tueidj said:It's not fine. Whoever ripped off segher's code for zeventig changed the fopen calls for the .app files to "wb" mode but wasn't smart enough to do the same thing for the tmd and ticket (and trailer and cert). Hence it writes 0x0D 0x0A instead of just 0x0A because the output file is in text mode.icefireicefire said:and BFGR's code is perfectly fine. The real reason is probably found in Cygwin.


