You mean on-calc? I think that for that you'd need to analyse the hex code (headers).

The first two bytes of an assembly program (not counting the size bytes) are required to be $BB, $6D. That is how the OS determines whether or not a program is an assembly program.

That is super easy then Thanks too.

I was wondering this too, for the same purpose in fact. How would one go about testing this? I can use memkit to get the pointer to a program so what do i do to after that? EDIT: I guess i cant get the pointer with memkit. dim()r gives a bad symbol error

Ah i c that was easy thanks . I can use GetCalc with memkit (to list only basic or asm programs) but its a bit more code than dim()r would be.

#Axiom(MEMKIT)
Load()
While Next()
Print(L1)
"prgm"L1->A ;or something to that effect
GetCalc(A)->P
If {P}r=E6DBB or {P}r=E6CBB
Disp L1
Disp i
End
End
Is what i meant sorry lol

EDIT: It worked

Quote from: Xeda112358 on March 04, 2011, 03:27:49 pm

If it is BB6C, then it is an uncompressed assembly program.

Yes, I found this out too. (thanks to XXEdit)
I am now getting the headers for Ion, MOS and DCS with XXEdit.

Remember that shell headers can contain a description or icon. To make things easier for ya:

Ion headers

There are two types of Ion programs: those that can be run from the homescreen and those that can't. The difference is that if a program uses Ion-specific routines, it'd be pointless (and dangerous) to allow it to run from the homescreen, hence the two header formats:

Code: (Homescreen-runnable) [Select] BB 6D AF 30 XX DESCRIPTION 00

Code: (Shell only) [Select] BB 6D C9 30 XX DESCRIPTION 00

The only difference between the two versions is that one has an AF as the third byte, while the other has a C9.

DESCRIPTION is the description of the program in ASCII. It can be anywhere from 0 to 127 bytes long.

XX is the length of the DESCRIPTION plus one.

If you want to simply determine if a program is an Ion program, just know that it either starts with BB6DAF30 or BB6DC930.

MirageOS headers

There is only one version of the MirageOS header, one that is not compatible from the homescreen (hence why MOS prgms quit immediately when you try running them with Asm().

Code: (MirageOS) [Select] BB 6D C9 01 HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH HHHH DESCRIPTION 00

DESCRIPTION is the same as Ion's DESCRIPTION. The mass of Hs is the icon; it's 15x15 (with an extra zero padded to each row), so it's 30 bytes total.

All you need to know to determine if it's a MirageOS program is that a MirageOS program starts with BB6DC901.

DoorsCS headers

These get a bit complicated. It involves a lot of pointers, referencing, and calculating, so I won't post the full header here (it's at http://dcs.cemetech.net/index.php?title=ASM_Header if you're interested). But here's what you want to know:

To determine if a program is a DoorsCS program, check if it starts with BB6DAAC9.

That was really interesting for me, Deep.  Thank you!