This topic was archived here:

https://web.archive.org/web/20230000000000fw_/https://www.zenhax.com/viewtopic.php?t=79

shekofte, posted Fri Aug 15, 2014 3:14 pm (175)

---

dear Administrator of zenhax

Quote:

QuickBMS wants to be THE EXTRACTION TOOL for almost everything so
"help it to help yourself"

I quoted a sentence from yourself .

I feel there must a forum section with the name "Quickbms beyond of" or "New language of Data Management" (as Stephen Wolfram invented such symbolic language that plug into human brain ) , and so on ...

a simple example that can i mention just now about such applications are :

Its usage in some text processing :
-splitting text file on conditions or intervals
-character encoding
-applying encryption from simple reversed strings , rot13 , other complex encryption methods
-compress/decompress text blocks
-programmatic tons of file manipulations
(that can do all of this in an integrated tool freely but you can't find all of these capability even in a commercial tool )

obviously it has many application in dealing with sound

maybe as a research tool in computer science

...if i can remember other criterions i will prompt them too ...

also i request from other members that have an experience for solving of a problem with power of Qbms regardless of game research please share it here ?

aluigi, posted Fri Aug 15, 2014 3:30 pm (176)

---

Everything is ok if the language doesn't grow too much and becomes too complex.
Some commands are already at their edge of complexity.

For example recently I introduced the multiple conditions that are useful but they kill the original simplicity of the language.
(the multiple conditions are: if VAR1 == 0 && VAR2 == 10 )

Working with the text strings is one of the problems of quickbms, the existing commands do their job but they are not flexible.
And they have even strange operators like >> or Anyway 99.9% of times there are no strings manipulation for extracting archives.

Character/Charset encoding may be possible, probably there is a Microsoft API to do that but then Linux would remain uncovered and it's not acceptable.
So I should rely on a library but that's not ok if the library is bigger than the whole quickbms source code.
Also in this case, 99.9% of times this is not needed for file extraction.

The encryptions you mention already exist and you can apply them also to strings:

Code:

encryption xor "\x11\x22\x33\x44"
String VAR e VAR2 # till end of variable
String VAR E VAR2 # NULL delimited

Also that thing of the text blocks is possible using comtype with a memory_file or:

Code:

comtype zlib
String VAR c VAR2 # till end of variable
String VAR C VAR2 # NULL delimited

"programmatic tons of file manipulations", changing some bytes is ok but making tons of manipulations seems out of the scope of the tool.

After all if someone wants the maximum freedom of doing anything on a file... well probably he will use a real programming language like Python or C and not a tool for extracting files

Hope to have clarified the scenario in which QuickBMS operates.

shekofte, posted Fri Aug 15, 2014 3:42 pm (179)

---

Quote:

Hope to have clarified the scenario in which QuickBMS operates.

yes sir and thanks