uhmmm the bms language doesn't implement this possibility, although would cost me nothing to implement a solution in quickbms (maybe the same I adopted for findloc).
so a 0.4.2a version? :)

uhmmm so they get identified as wma files. indeed they don't look like xma1 or xma2 files because xmaencode can't decode them. they could be msadpcm but I doubt because this adpcm needs a particular value located in the xwb archive and after a scanning I have found no value good to hear a clean soun...

why don't you use unxwb?
it tells any information found about the file and automatically builds the needed headers to play/convert it in a second moment.

that one is a script for quickbms that extracts all the files contained in the DAT archives used in the first Transformer game,

do you mean this one?
blog/?p=28

no hcs, I have not tested. anyway if you want to force the xma1 header for this test it's enough that you substituite the reference to the xma2_header function in fsbext.c with xma1_header (it's already implemented) let me know if you get a result in which case I will add an option to let the user t...

with fsbext the extraction is correct, the problem is xmaencode that it's not able to decode the obtained files. the difference between these files and the one in your first link is that they are xma2 while that one is xma1 and no, if youdo an "injection" job (like putting the data content...

if it's developed by the same people of Transformer 1 then this script should do the job:
http://aluigi.org/papers/bms/ttgames.bms

otherwise you must upload an archive or a part of it

the 'x' operator has been introduced in version 0.3.15 so you are using an old version or, if you downloaded it, you got the file from your browser's cache.

be sure to have ollydbg installed and that it's set as "Just-in-time debugger": select "Options->Just-in-time debugging" click on "Make Ollydbg just-in-time debugger" open hge.dll with a hex editor (make a backup before) go at offset 0x42a9 place the byte 0xcc there sa...

this is an extractor, editing the content is totally unrelated to my job
same for the "repacking", I work only on extractors.

while for the 2gb file it's not needed because I fixed the bug

yeah I see but the steps remain the same said before

I have seen that there are these "padding" files that should not be extracted but I have decided to extract them too: # script for QuickBMS http://aluigi.org/papers.htm#quickbms get DUMMY long get NAMES long get INFO_OFF long get NAME_BLAH long get ALIGN long log MEMORY_FILE 0x64 INFO_OFF ...

uhmmm depends by what you want to do and "how" you do because I have already worked with various hashes without problems but I guess you refer to something else, so show me an example.

with manual debugging I mean just using ollydbg and the usual steps: - bp CreateFileW - bp ReadFile - hw bp on the read memory - following all the instructions performed on the memory and if they are done by one single function (good for ripping it) recstudio could be useful only in the last stage o...