Otherwise you'll be getting lots and lots of invalid bug reports.įor example, this is the error message my EnigmaVB unpacker used to show (as reported by ho3ein at Tuts4You): If your tool is showing an error message, make sure even your grandma could understand it. I don't know.īut one thing I know for sure - you must make your tools foolproof.
Posted in General, Programming C#, delphi, Enigma Virtual Box, unpacker 6 Comments How about you? Would you be able to write some tools without using Google and StackOverflow? kao It doesn't mean I can't do those boring tasks - I just don't want to. Why should I spend 30 minutes remembering basic algorithms for converting string to hex, if Google query can solve it in 10 seconds? Why reinvent the wheel and write CRC calculation from scratch? I'll just open StackOverflow and have a solution that's already tried and tested. Reading both the post and the comments made me think a lot.ĭoes using Google to solve your programming tasks makes you less of a programmer? I don't think so. While researching all the Delphi limitations and possible workarounds, I ran into this great article by Scott Hanselman.
NET framework - my next version of EnigmaVB unpacker will be made in C#. I'd very much rather use this time breaking some code. I don't want to spend my time developing custom stream classes. I can either make a custom stream class in Delphi, or I can pick another framework and rewrite my tool to use that. TFileStream internally uses longint, so it doesn't properly support files larger than 2GB. TMemoryStream uses a continuous memory range, so it can never support anything larger than 2GB. They look like they've been written in 1990s and were never updated. So, what's causing the problem?ĮnigmaVB unpacker is a 32bit application written in Delphi. In all cases, the problem was caused by really large files, like 3.5GB in size. Recently, several people sent me bug reports where my EnigmaVB unpacker failed to extract files.
0 kommentar(er)
