Planed features:
  -Interact with calcnet routines and such for handeling data
  -Offer data handlers that may be slow but will help prevent misfires
  -Anything else you want like things to manage connections and such
  -The mandatory splash screen for gcn (you can just add in the required image to your game if you want will explain in readme)

Issues:
 I can say now. L1 and L3 will suffer if you use calcnet nothing can be done about it it is where Kerm keeps the stuff CalcNet lives on

 The Key routines will mimic axe's but will  not be the same

anything else thats needed or wanted ask. I will also be using this thread for help on making axioms as some of it is like LOLWUT to me. but at least I get calcnet xD



Currently Accomplished:
 
 Command set:
   SetS Sets the ok to send flag
   ResS Resets the ok to send flag  note i see no applicable use other than to change data if the data in the buffer was not sent in a reasonable time
   SetR Sets the "you got data" flag, only applicable use is to block incoming messages
   ResR Resets the "You got data flah" Allows more data to come in
   
    GetS returns the send buffer flag
   GetR returns the recieve buffer flag


There is also a wrapper that sets up pointers for use.


Available for download here; http://www.cemetech.net/programs/index.php?mode=file&id=737

A Calcnet axiom would definitively be great. I believe Compynerd255 was making one before, but I haven't heard about him ever since.

Hmm, so why didn't he just put it all in one place? Is it so that it can work around DCS?

Yes, if its a static address.  If its a pointer to data that your Axiom has added, you don't even need it at all since its done automatically with AXM_DATA.

Also, you probably aren't using this, but if you want it to return pointer to axiom code that you want the programmer to jump to, you'd have to use a replacement with REP_NEXT, but that's an advanced feature.

Yeah, that's because it's a "new" token and is sent to the token hook in a special manner that Axe doesn't handle. I didn't add handling for it because I wasn't entirely sure how to account for it without introducing other problems on calculators with older OSes, but I think I've found a way to fix it now.

Also, I'll try to fix the issue where I stupidly forgot to account for the possibility that the Axiom name in the source code contains tokens that aren't equivalent to their ASCII values.

Oh no, A-Z and 0-9 are fine. That's why I didn't discover the bug myself. The issue is a-z.

EDIT: Forgot to answer your first question. Tokens after GarbageCollect are passed in a special manner. But I've added code to handle this and will give you my updated token hook once I fix the above problem as well.

so lets see how this works....open beta go?!?!?


everything needed is in the zip even the source. i just need someone to tell me if it works. i just cant understand axe...

have any questions pertaining to calcnet just ask. ill be more than willing to show you how it works if kerm's documentation is confusing you.

there is no guarentee that this works. and it is by no means even close to dont. this just has the basic api in it.


also read through the program in the wrapper i forgot to lable what they are. ill make a edit later with that info. they should be self explanatory tho ^^

warning these are screen stretchers

Hmm, so why didn't he just put it all in one place? Is it so that it can work around DCS?

Only 547 bytes in "L1" is actually for CALCnet.  The other 100-odd you only have to worry about if you're also using the Doors CS GUI API with CALCnet. Believe it or not, I actually use my brain when I design things.

Edit: Oh yes, and the L3 stuff for interrupts, of course, but that's nothing extraordinary.