All you need to do is assemble and link a program with the Doors CS SDK, and see what the checksum is, then try to do the same with your program and see if the checksums match. If not, you'll know that you're doing something wrong. If so, you'll know you have it right.

wooooops, I forgot to put that in the last post. It is not returning the correct checksum.

Oh, ok. Remember when I told you the exact byte offsets between which you need to checksum; did you check that those are the offsets you're using? If so, I'll look a bit more closely at the Python code you posted.

According to this the checksum is the sum of all the bytes in the data section. According to the same page, the data section is:

Data section - consists of a number of variable entries (described below).

So, it's the program code (2101002323EF0745EF7249...).

However, I was not sure if 'BB6D' was part of this, so I decided to try my getCheckSum( function with both. However, neither returned the correct checksum.


Code:


My function also doesn't work for all strings:


Code:


Here's my function:


Code:

No offense, but I'm pretty sure we've answered that question two or three times previously.

Here's your fixed function:
Code:

Thanks Kerm! Now I'm using binpac8x though and I'd like to know how to do this:

I have some code in a string, as an example: ("BB6D210100EF0745C9").

I want to write that code in a file, a .bin file, a binary file.

I want to do it using bytearrays.

I can do this:


Code:


That works, but how can I do that to the string?


Code:


That would write it but I get a ValueError:


Code:


How to do it, then?
Thanks.

Are you using Python 2.x or 3.x? Are you trying to make it cross-compatible, or do you only care about either 2.x or 3.x?

I only care about 2.x.

It is important that you keep in mind that a python array of bytes ("bytes") is basically like a string, while a "bytearray" variable is a mutable array of actual bytes. You can't append more than a single element to an array; consider either using a loop, or finding out if bytearray has a join() function.

Code:


OK, I am now using binpac8x to create files and I created a binary file with this:


Code:


It's a binary file, not ASCII, but with that encoded on it (I'm sure the problem isn't the binary file).

Then I do:


Code:


binFileName is the name of my file.

And here's what I got as a 8xp file (in binary, not ASCII):


Code:


My reaction was immediate: "What the ?".

I really have no idea of what's causing this.

Any idea?

I'm not seeing what the problem is; what's wrong with that...?

The problem with that is that my code (in the .bin) isn't in the 8xp file, as simple as that.

Sure it is. At the very end I see "6339", which is the number 63 followed by 39, or in other words "C" "9". The bin file you're passing to BinPac8x is letters like "C9" instead of bytes like ($c9).

Then I'm writing a string, not bytes, I'll just use my old way of writing files, a bytearrays.

I just said that. Can you post the code that you're using to write into the files?

Code:


Never mind the filename variables, it's just a hack to avoid >8 names.

But that's my code.

This line:
Code:
just splits your ASCII into a sequence of two-letter chunks. It doesn't turn them from two-letter chunks to actual numbers. You need an int(programData[x+1],16) in there.

I'm using a new method now, and I still have a problem.

I created the following file: http://davidgom.co.cc/mylittle.bin

I think it's ok, it's code is the following:

BB6DEF4045210500
EF0745EF7249C9

Please download the file and check the binary file is ok.

And then the 8xp file created is here.

It crashes and it's code is very similar to the one desired (the .bin one) but it has some differences:


Code:


The code is more or less right, however some zeros were added to the code in random positions:


Code:


Here's my code to create the file:


Code:


Any idea of what I'm doing wrong?

In this function:
Code:
Can you add a print ints line right after the ints= line and tell us what it outputs?

Code:


Did you check the binary file? I just rechecked it and it also has weird 0s.