Stemming from my attempt in Grammer, I ported my automata generator to assembly. This version takes an input through Ans for the rule set (0 to 255)  and modifies the graph screen accordingly. it starts at the top of the screen and makes its way to the bottom. Oh, and the program 114 bytes


EDIT: I added a picture of rule 57 because it looks so cool!

Okay, this a program I made a while ago (two or three years ago) that may still be useful to folks. It is a cheat code program based off of a program called CODEM that I made for an RPG (about 5 years ago). What the original did was it would take two strings (the name of the codes and the actual codes). It would then let the user select codes to use through a fancy-shmancy menu and then it would perform the codes.
The drawbacks:
Names were 16 chars, codes were 8 chars-- always
The undrawbacks:
The menu was really nice o.o It let you scroll through large numbers of codes (the program I made this for had 89 codes or something like that)


So why is CODEM in any way something you might want? Imagine this scenario:
You make a great game
You spread said game around your friends/school/internet/world
Some said folks try to cheat by modifying source codes and/or savefiles if they can figure it out
Said folks fail
Said folks break program
Said folks make an face and flood you with questions on how to fix it


So you might want to make the codes for them... After a few years I learned about Celtic 3 and that was when I made CODEM4 (there were a few versions before). Codem4 was a project in itself because I made a file system, code editing screen, error handling of almost any possible error (there were a few I could not do). I made all the code compressed, easy to select. It wasn't a graphical wonder, but it did have a lot of neat features that a programmer would appreciate (if not a regular person). Plus, I made it spit out a program that had everything precalculated (instead of converting codes on the fly) so running the cheat code could be done quickly and seamlessly without modifying any other variables.

Anyways, features:
If there are no code databases found, you will be prompted to create one.
You can add a description to it
if the name is already taken, you will be prompted again for a name
If you select a database with no codes, you will be prompted to add codes or not (selecting yes will take you to the code input screen).
When you select your codes and finish, the program (locked) CODEM will be created.

Now to run your cheats, you can just run prgmCODEM upon a special keypress or what have you. Of course, it is necessary that your program allows CODEM4

Grammer 2



http://www.omnimaga.org/index.php?action=downloads;sa=view;down=773

You might be familiar with my avatar and the previous avatar, both of which make use of a neat effect. Pretty much, the screen falls and melts into a puddle. If you want to give it a try, here it is, the program I have used for these effects I tweaked it a little, so here is the setup:

The picture to liquefy is in Pic1. If Pic1 does not exist or is in archive, the graph screen is used instead. A horizontal line on the bottom row of pixels is drawn as a barrier. When converting the screen to particles, all of your remaining RAM is used. If you have less than 775 bytes of RAM left, though, it will not create a var and it uses AppBackUpScreen instead (holds 366 particles).

Press CLEAR to exit. Don't worry, you get your RAM back

If you have 12106 bytes of RAM left, you can convert the whole screen if it was all black. My logo didn't even use the 2048 byte buffer I assigned originally, though

A new game to add to your Grammer collection is here! I still need to better the animation, optimise some code out, and make a menu so users can select options (such as who is the AI). Anyways, for now, there is an AI that you can play against, so have fun

When you finish the game, press clear to exit, press Enter to play again.

Okay, I have been having a tough time with this, so I need help. I am trying to send data between two calculators and I can easily send a single bit or two bits, but nothing longer seems to work. The protocol idea that I was working with looked like this (this is an outline):
         ld b,8
Send:
         rlc c                ; get the next bit of C
         ccf                  ; inverts the c flag since writing to the port will be inverted
         adc a,a            ; rotate the bit into a
         scf                  ; sets the carry flag
         adc a,a            ; sets the first bit
         out (0),a          ; send it to the port
         dec b              ; decrements the counter
         ret z                ; ends if the counter hits 0
CheckLoop:
         in a,(0)            ; Check the port
         rra                  ; We test bit 0
         jr c,Send          ; Ready to send the next bit
         jp CheckLoop    ; Eh, keep checking
Receive:
         ld b,8
Loop:
         in a,(0)            ; check the port
         rra                  ; check the bit to see if the data was being sent
         jr c,$-3
         rra                  ; get the bit that was sent
         rl c                 ; rotate it into C
         out (0),a          ;since A is 0, this will set both bits in port 0 signaling that another bit can be sent
         djnz Loop
         ret
Actually, I just typed that up and is only vaguely like the codes I have come up with before. In any event, if I take out the counters and only send one bit, it works fine and I receive it, bit if I try to send all 8 bits, it freezes (I think the receiving end).

Thanks much! I'd love to figure this out

I am just learning Assembly for the 68K series and I was wondering if anybody could provide a breakdown of how certain things work. I have a TI-89 Titanium, I consider myself a decently experienced z80 programmer, and I understand math. I have difficulty learning mnemonics, so I will probably ask questions multiple times about how certain instructions work until I solidly understand it.

The assembler I am using is an on-calc assembler that seems to work beautifully. It is the only thing I could understand how to install because my computer skills are massively lacking. Anyways, I looked at the source for a "hello world" program and I was just absolutely confused. I think that move instructions move data between registers and RAM and I believe the stack and PC, but there are operators and whatnot that I am not following. The instructions used are all unfamiliar to me:

movem.l       d4/a5,-(a7)
I am assuming this writes using d4 and a5 to the address pointed to by a7? Does the negative mean it decrements A7 ? I saw somewhere that A7 was a stack register
move.l         HeapAllocPtr*4(a5),a0
I have no clue what this syntax means. I checked out the hex and that helped me realise that it is like a 2 byte instruction followed by 0288h (which is HeapAlloc*4). But what does it mean to be right before (a5) ?
jsr              (a0)
Is this some kind of relative jump?
pea.l           3840
Does the .l mean it is a "long" operation? The hex has a 32-bit value equal to 3840. But what does pea mean and what does it do?
tst.l            d4
I cannot even begin... "tst" looks like test, so is this some way to check if an event has happened with d4?
beq.s          nomem
I haven't a clue, but since nomem is a label, does this jump
move.l        #3840,(a7)
Does this push an immediate value to the stack?
pea.l          LCD_MEM
I've not a clue... LCD_MEM seems to have a value of 4C00h, but this seems to be different from the last pea.l instruction (the hex is 4079h as opposed to 4879h, so this tells me that it is just a flag difference or a slight difference in operation from my experience with z80 hex)

lea.l          12(a7),a7
I don't get the syntax
pea.l          Hello_World(pc)
again, I is slightly different from the first pea.l (the hex is 487A versus 4879). This tells me that it is the same style if it were like z80
clr.l            -(a7)
I am not sure what clr.l is...


Sorry for all of the questions tutorials don't generally help me much and I am still not understanding them yet, so this is why I turn to y'all. I am sure that, left to my own devices long enough, I could figure it all out on my own (I did that with z80), but I think it would be a lot neater if I could start programming soon. I am hoping that I can port some of my better known z80 attempts to 68K and  I also think this experience will be very helpful for understanding assembly on other processors. Thank you much in advance!