Ultimate Amiga

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Trying to find out all of TOME's commands via hex editing  (Read 4045 times)

0 Members and 2 Guests are viewing this topic.

skateblind

  • Important 'looking' person
  • Forum Mod
  • A2000
  • *****
  • Karma: 668
  • Offline Offline
  • Gender: Male
  • Posts: 509
Trying to find out all of TOME's commands via hex editing
« on: August 09, 2009, 10:14:57 AM »

I am mainly looking for help from Lonewolf10, since I have heard he is experienced at creating extensions or hex editing them.
I have had a look at AMOSPRO_TOME.LIB in a hex editor and I think I have figured out most of the commands, but I could not work out some of the symbols and syntax.

Any help on this would be appreciated. I have attached a text file with all the commands I could find, if you know a thing or two about hex editing assembly files, maybe you could double check the commands for me? I have also attached Lonewolf10's text guide on extension creation in case it helps.

There is one part starting at line 410 that describes how variables are defined in ASM and they can be seen when hex editing a function.
E.g.  map doI0,0   - 'map do' is the command, the first character afterwards tells AMOS what type of command it is and the rest define the parameters if there are any. So in this case it would be 'map do x,y', which is an instruction(I)
This is what I used from the text file to understand how the definitions work:
-----

   "I0,0t0,0" - First Character
                ===============

                I  represents instruction (with no result returned)
                0  represents command returns numeric result to variable
                1  represents command returns floating point number
                2  represents command returns a string. Any variables (if any)
                   that follow are contained in brackets.
                V  represents reserved variable. Must state type (int, float or string)

                Additional Characters
                =====================

                0  represents a numeric variable
                1  represents a floating point number
                2  represents a string variable
                ,  represents ","   (as in Command 3,5)
                t  represents "to"  (as in Command 3,5 TO 3,3)

----

I am hoping to get a scanned copy of the 80 page manual soon, but until then, this will have to do.
« Last Edit: August 09, 2009, 10:56:40 AM by skate »
Logged
What are you looking at?

Lonewolf10

  • AMOS Extensions Developer
  • AMOS Dev
  • A2000
  • *****
  • Karma: 3
  • Offline Offline
  • Gender: Male
  • Posts: 618
    • http://www.aliensrcooluk.com
Re: Trying to find out all of TOME's commands via hex editing
« Reply #1 on: August 14, 2009, 03:17:41 AM »


eek!

As if I didn't have enough projects going already...

yup, I'll take a look this weekend (assuming I don't forget).


Regards,
Lonewolf10

 
Logged

Lonewolf10

  • AMOS Extensions Developer
  • AMOS Dev
  • A2000
  • *****
  • Karma: 3
  • Offline Offline
  • Gender: Male
  • Posts: 618
    • http://www.aliensrcooluk.com
Re: Trying to find out all of TOME's commands via hex editing
« Reply #2 on: August 14, 2009, 10:12:13 PM »


You did very well Skate.

I have looked through the text file and made the necessary corrections. I have also added a few comments too. I have not checked any of the command names by running AMOS, so there may be minor errors.


Regards,
Lonewolf10

Logged

skateblind

  • Important 'looking' person
  • Forum Mod
  • A2000
  • *****
  • Karma: 668
  • Offline Offline
  • Gender: Male
  • Posts: 509
Re: Trying to find out all of TOME's commands via hex editing
« Reply #3 on: August 16, 2009, 05:09:36 AM »

Thanks mate!  :)
Logged
What are you looking at?
Pages: [1]   Go Up
 

TinyPortal 2.2.2 © 2005-2022