I am using Asm(prgmNAME.

Try changing the bcalls so they look like b_call(<bcall>). Also, try compiling it with Brass and see if it outputs an error.

Could you give me an example of bcall like that? I don't understand the format ('>','<')

Yeah, you should be using Brass instead of SPASM, it's much better. What error is occur
ring, exactly?

Where can I download BRASS?
The error in SPASM is: '83+ programs don't start with bytes BB 6D'
The error in WabbitEmu is INVALID in the line Asm(prgmNAME.

Use the Doors CS SDK, it includes the Brass assembler.

Exactly this, thanks Souvik. Please feel free to ask any questions if you're having trouble using the SDK.

Now my doubt is, again, creating .8xp files:


Code:


This is my code, it creates the file myData.8xp.

Note: This hexadecimal code was produced with binpac and brass (doorsCS sdk), it's just for testing creating 8xp files.

When I open that in WabbitEmu it says invalid format, any idea?

Edit by Kerm: added line breaks.

Once again, as I've tried explaining, hex in ASCII nibbles and hex as bytes are not the same. The byte $2A is not the same as the string '2A', which is two bytes: the character '2', and the character 'A'.

You will have to write the hex directly to the file, not the actual hex nibbles like Kerm said. Here is a link that may help you. http://bytes.com/topic/python/answers/43276-write-hexadecimal-file

I think the reason you're confused is because you've done hex programming on the calculator.

One thing you've got to understand is that when you did that, you weren't actually typing compiled data. You were just typing ASCII characters, which the calculator had to convert to pure data before it could be run.

As Kerm said, the string "2A" is very different from the byte $2A. $2A is a number, a byte of data. "2A" is two separate ASCII characters, each of which is represented by a byte ($32,$41).

Souvik, Deep Thought, thanks for your additions to my point, I agree entirely with both of you. Hopefully this makes sense to Scout now.

I am aware (and have been aware for a long time) that $2A != '2A'.

However, I was looking for a sample code to create a 8xp file, I guess I'll have to search deeper, thanks.

Did you check my link that I posted above?

Yes I did, they have the right code, but they don't say what kind of variable 'bytes' is.

That's the type. Bytes is the name of the type.

OH YEAH Like in the tokenizer thread (bytearray, append, etc).

I have one doubt though.

bytes.append($DE)

OR

bytes.append(DE)

Which one is correct?

Neither are correct. 0xDE is the form that Python uses to represent hexadecimal. DE is never correct, because that would be interpreted as the name of a variable (and what about $32? if append(DE) was correct, how would it distinguish append(32) as hex and append(32) as decimal?). Sadly, Python also does not use the $hex syntax.

Code:


I made a small engine to convert Hex data to Python-Readable Hex Data

Edit by Tanner: Added line breaks, that was all one line x.x

Err, you mean like this?

Code: