Blizzard Installer Customisation

[stoneharry]

The addresses would be closer together. Also, it would not be logical at all, to display the address of anything: It is a void* = NULL. There is no more address than the position of the variable itself (on the stack) and the value NULL.

Okay. However I don't understand why it would have a value, if that is the case.

[schlumpf]

Try printf("zalloc:: %pn", stream.zalloc); instead of that debugger.

[stoneharry]

Try printf("zalloc:: %pn", stream.zalloc); instead of that debugger.

[schlumpf]

Well, I guess all values are wrong then.

[stoneharry]

Well, I guess all values are wrong then.

The pointers for all the variables set in the stream, not that it is particularly useful other than proving they have been set:



Still no idea why it does not work.

[stoneharry]

Attempted with a few different patches, they all produce the same results. I can see why -5 is being returned (because the other value becomes 0 after the first inflation) but I have no idea why this is happening or how you would go about debugging and fixing this.

Any suggestions?

[stoneharry]

Avoiding the extractor for now, the assembler appears to work.

Using the example_base I extracted for contents of the 3.3.5 to 3.3.5a patch and create a new MPQ from that.

I then am trying to assemble a new executable using this data and the example base, but the arguments required confuse me.

Code: [Select]

(arguments: <base> <output> <mpq> <exe> [<files...>])

Base    = example_base.exe
Output  = A new file? (I put test.exe)
MPQ     = the MPQ to be attached
exe     = ??? I put the original installer in here
<Files> = ??? Additional optional files to be included not in the MPQ?

Either way, the executable being produced (after no errors) does not run and throws a Windows error about it not being a valid windows application. So I assume I am getting the arguments wrong.

[schlumpf]

example_base.exe output.exe patch.mpq exe_extracted_from_original_installer.exe dlls_extracted_from_original_installer.dll

[stoneharry]

example_base.exe output.exe patch.mpq exe_extracted_from_original_installer.exe dlls_extracted_from_original_installer.dll

Ah, so the extractor needs to be functioning correctly first.

[schlumpf]

I don't see any reason, why it would not work, anyway. oO

[stoneharry]

Updated zlib to 1.2.7 and converted project to visual studio 2011/12 for a more up to date debugger.

Before inflation:


After inflation:


Key things to note is how inflateResult goes from uninitialised to -5. avail_out goes from a large value to 0.

The returned value of -5 signals a error, usually caused by avail_out or avail_in becoming 0, as it has in this case.

As to why it happens, I have had no idea.

I do remember when you posted in the shoutbox about it before you finding a typo. Has that been fixed in this version? I do not remember what it was.

[schlumpf]

Has that been fixed in this version?

How would I know which "version" you're using?!
Try doubling the size allocated for output.

[stoneharry]

Has that been fixed in this version?

How would I know which "version" you're using?!
Try doubling the size allocated for output.

I am using whatever version you gave me when I requested to start again a while ago. So I dunno'.

Avail_out starts at 6052592 and goes to 3026284.
Avail_in starts at 1499174 and goes to 0.

So now -5 is still being returned, but this time because avail_in is 0 rather than avail_out.

6052592 / 2 =
3026296 which is just bigger than the original value if not / 2:
3026284

[schlumpf]

If avail_in is 0, it worked?

[stoneharry]

If avail_in is 0, it worked?

No, because -5 is being returned it throws an error that inflation failed.